The content of the file instructs udev to look out for devices with Vendor ID and Product ID matching HackRF devices. Here is the content: ATTR="000c", SYMLINK+="hackrf-dfu-%k", MODE="660", GROUP="plugdev" To do that, you need to create a new rules file in the /etc/udev/rules.d folder. In particular, your distro may have a group named something other than plugdev for this purpose.) (The following things have been tested on Ubuntu and Gentoo and may need to be adapted to other Linux distributions.
![hackrf one linux hackrf one linux](https://cdn.sparkfun.com//assets/parts/9/9/5/3/13001-04.jpg)
To fix this issue, you can write a udev rule to instruct udev to set permissions for the device in a way that it can be accessed by any user on the system who is a member of a specific group. The first solution would be to run every command which tries to access the HackRF as root which is not recommended for daily usage, but at least shows you if your HackRF really works. Permission problemĪ normal user under Linux doesn't have the permissions to access arbitrary USB devices because of security reasons. If it is, then your other user is lacking permission. Then check to see if hackrf_info is successful when running as root. HackRF One, for example, is only supported by release 2014.04.1 or newer. Or: hackrf_open() failed: HACKRF_ERROR_LIBUSB (-1000)įirst make sure that you are running the latest version of libhackrf and hackrf-tools. When running hackrf_info or any other command which tries to communicate with the HackRF, I get the following error message, although the board seems to be enumerated properly by the Linux kernel: hackrf_open() failed: HACKRF_ERROR_NOT_FOUND (-5) I can't seem to access my HackRF under Linux Q: