[Hackrf-dev] hackrf_open() failed: HACKRF_ERROR_LIBUSB

[Rick "Zero_Chaos" Farina]

On 03/21/15 04:59, Dominic Spill wrote:
> On 21 March 2015 at 03:06, Rick "Zero_Chaos" Farina
> <zerochaos at gentoo.org> wrote:
>> On 03/19/15 06:34, Paul Connolly wrote:
>>> The kernel modules (RX only) for new  SDR devices was known to be
>>> arriving for the HackRF in 3.18 for a while.
>>> http://palosaari.fi/linux/
>>> ... snip ...
>>> AirSpy SDR driver (airspy)
>>> * Kernel 3.17
>>>
>>> HackRF SDR driver (hackrf)
>>> * Kernel 3.18
>>> * only RX
>>> ... snip ...
>>>
>> Is this stuff known bad or what?  Should everyone be avoiding the in
>> kernel drivers?
> 
> I'm not aware of any software that interacts with it and it claims the
> hardware as soon as you plug it in, so I think we should all be
> blacklisting it by default.  We may need to look at the possibility of
> installing a blacklist file in to /etc/modprobe.d when we install the
> HackRF tools as this will break for every user when they run 3.18.

I believe I'll start doing this immediately.  I can try to help you
figure out how to safely do this later but from a distro package
perspective I can try to handle it cleanly and learn how.
> 
> I'm not sure why kernel developers feel that it's acceptable to break
> the official library/tools associated with the hardware without first
> getting in contact to discuss it.  Maybe in time we'll start using the
> kernel driver, but I don't see that it provides any benefit at this
> stage and using it would remove our ability to make changes to the
> host / firmware interface.

<facepalm>Ugh, that hurts, that hurts just so bad.  What a fabulous
display of the exact opposite of what this community is supposed to
represent.  I'm sorry that the kernel developers are this stupid, and an
email from gsg should likely begin "Why exactly do you feel it's
appropriate to break my hardware with non-functional drivers without
even asking for help?"  Yet again, the kernel devs are happy to show
just how anti-social they are, as if reading the mailing lists didn't
show that enough.</facepalm>

-Zero_Chaos
> 
> Dominic
> 
>>> On 19/03/2015 06:15, Tom wrote:
>>>> I got this error when I updated from kali 3.14 to 3.18.
>>>>
>>>> Works fine on 3.14
>>>> _______________________________________________
>>>> HackRF-dev mailing list
>>>> HackRF-dev at greatscottgadgets.com
>>>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> HackRF-dev mailing list
>>> HackRF-dev at greatscottgadgets.com
>>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>>
>>
>>
>>
>> _______________________________________________
>> HackRF-dev mailing list
>> HackRF-dev at greatscottgadgets.com
>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://pairlist9.pair.net/pipermail/hackrf-dev/attachments/20150321/cf281b2d/attachment.pgp>