Differences

This shows you the differences between two versions of the page.

--- troubleshooting [2015/08/18 15:13] – [rad1o usb disconnects every 5 seconds / not usable at all] mkie
+++ troubleshooting [2016/12/26 23:26] (current) – [I've connected the rad1o in Mass Storage Mode, but the filesystem is read only] 151.217.239.253
@@ Line 14: / Line 14: @@
 Another issue might simply be an empty battery, so have a try with recharging.
-If you soldered in the SMA connector, you might have shorted the left ground pad to a Vcc pad underneath. These two pads which are seperated only by a small margin must not b connected.
+If you soldered in the SMA connector, you might have shorted the left ground pad to a VCC pad underneath. These two pads which are separated only by a small margin must not be connected.
 ===== I have connected the rad1o, but it doesn't show up in dmesg or similar =====
@@ Line 30: / Line 30: @@
 </code>
 If you are running Arch Linux there might be a similar problem but of different origin. The solution is provided within the hackrf-github [[https://github.com/mossmann/hackrf/issues/208|Issue page]].
+Make sure that [[#rad1o_usb_disconnects_every_5_seconds_not_usable_at_all|USB autosuspend is disabled]], as the first contact with rad1o after resuming fails, and default autosuspend delay in Linux is pretty short (2 seconds).
 ===== I've connected the rad1o in Mass Storage Mode, but the filesystem is read only =====
@@ Line 43: / Line 45: @@
 - run fsck on that partition
-  fschk.vfat -v /dev/sdb
+  fsck.vfat -v /dev/sdb
 - follow the instructions of fsck
@@ Line 57: / Line 59: @@
   - If it is found and you still get the error above, try upgrading your gnuradio package or compile it from source yourself. The latter solved the problem for me.
   - Try to unload the hackrf kernel module ("rmmod hackrf") before starting gnuradio
+  - If ''sudo hackrf_info'' works but plain ''hackrf_info'' doesn't, see [[troubleshooting#i_can_t_use_hackrf_without_sudo|I can't use HackRF without sudo]] below, or run ''gksudo gnuradio'' (ugly).
+===== I can't use HackRF without sudo =====
+If you run HKRF-OLD (not HACKRF), the device registers as idProduct 6089, and you will probably not have this problem. If you're sure that you want to use HACKRF, idProduct is cc15, and both udev and gnuradio have to know about this ID.
+udev: move [[https://github.com/rad1o/hackrf/blob/rad1o/host/libhackrf/53-hackrf.rules|53-hackrf.rules]] to /etc/udev/rules.d and do ''/etc/init.d/udev restart''.
+gnuradio: <todo>
+Make sure
+  * the "plugdev" group exists on your system, or pick one that does.
+  * the idVendor and idProduct values are the ones shown in dmesg when plugging in the USB.
 ===== pybombs install gnuradio => "make: target not found" =====
 Make sure you did not turn on the generation of documentation, or install `doxygen` through your package manager.
 ===== How do I put the rad1o into HackRF mode? =====
@@ Line 89: / Line 105: @@
   * audio connector
   * battery connector
+  * IC402 (BGS12SL6) in rare cases (LCD/everything not working, TX too low)
 If you experience an error that may relate to any of these three, we recommend a close look at the solder pads of those parts. WARNING: Always unplug the battery when soldering, especially when soldering the battery connector!
@@ Line 95: / Line 112: @@
 Please have in mind that rad1o's internal antenna is tuned for about 2.4 GHz. **This means that it cannot perform eg. in the FM Band (87.5 to 108 MHz). Sorry - but that's physics.** If you need good performance, consider adding an SMA connector and an antenna that is optimized for the specific frequency.
+===== What's this big peak in the middle of the spectrum? =====
+see https://github.com/mossmann/hackrf/wiki/FAQ#what-is-this-big-spike-in-the-center-of-my-received-spectrum
 ===== If I rebuild the l0dables I get an error =====
@@ Line 114: / Line 135: @@
 Reason: usb-autosuspend. manually configured auto-suspend or you may have laptop-mode-tools or tlp (thinkpad powersaving tool)
-Solution: disable usb-autosuspend for id 1d50:6089
+Solution: disable usb-autosuspend for ids 1d50:cc15 and 1d50:6089
-(if your using tlp add USB_BLACKLIST="1d50:6089" to /etc/default/tlp)
+(if your using tlp add USB_BLACKLIST="1d50:cc15 1d50:6089" to /etc/default/tlp)
+===== display blinks if turned on, but quickly turns off afterwards. All fine on USB power =====
+Your battery is empty.
+===== on/off switch is not working  anymore =====
+perhaps you soldert together the two tiny smd resistors next to the lower right WS2812b led. In my case that disables the switch. When i removed the tin it works again.