User Tools

Site Tools


troubleshooting

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
troubleshooting [2015/10/04 20:11]
neels [I can't use HackRF without sudo]
troubleshooting [2016/12/27 00:26] (current)
151.217.239.253 [I've connected the rad1o in Mass Storage Mode, but the filesystem is read only]
Line 30: Line 30:
 </​code>​ </​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]]. 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 ===== ===== I've connected the rad1o in Mass Storage Mode, but the filesystem is read only =====
  
Line 43: Line 45:
   ​   ​
 - run fsck on that partition - run fsck on that partition
-  ​fschk.vfat -v /dev/sdb+  ​fsck.vfat -v /dev/sdb
   ​   ​
 - follow the instructions of fsck - follow the instructions of fsck
Line 61: Line 63:
 ===== I can't use HackRF without sudo ===== ===== 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 you may need to do this+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.
- +
-To allow normal users to talk to the rad1o running HACKRF, you can add a udev rule and reload udev. On a debian linux: +
- +
-  $become_root +
-  echo '​ATTRS{idVendor}=="​1d50",​ ATTRS{idProduct}=="​cc15",​ GROUP="​plugdev",​ MODE="​0660"'​ \ +
-    > /​etc/​udev/​rules.d/​90-rad1o-hackrf.rules +
-  /​etc/​init.d/​udev restart +
- +
-Replug the device.+
  
-**Make sure the "​plugdev"​ group exists on your system, or pick one that does.**+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''​.
  
-**Make sure the idVendor and idProduct values are the ones shown in dmesg when plugging in the USB.**+gnuradio: <​todo>​
  
-**Tip:** Instead of installing the rule manually, you can install hackrf, which includes a set of udev rules. However, the file [[https://​github.com/​rad1o/​hackrf/​blob/​e612dfd8bf05343e27d7f9be3bbaed19d46bab42/​host/​misc/​udev/​53-hackrf.rules.in|53-hackrf.rules.in]] at some point contained ​the product ID "CC15", which should be "​cc15"​ instead, with lower case letters. At least on linuxcapital "​CC15"​ did not work for me. This may have been [[https://​github.com/​rad1o/​hackrf/​blob/​rad1o/​host/​misc/​udev/​53-hackrf.rules.in|fixed]] ​in the meantime, try to update hackrf, or fix manually.+Make sure 
 +  ​* the "plugdev" ​group exists ​on your systemor 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" ===== ===== pybombs install gnuradio => "make: target not found" =====
Line 110: Line 105:
   * audio connector   * audio connector
   * battery 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! 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 139: Line 135:
 Reason: usb-autosuspend. manually configured auto-suspend or you may have laptop-mode-tools or tlp (thinkpad powersaving tool) 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 ===== ===== display blinks if turned on, but quickly turns off afterwards. All fine on USB power =====
  
-Your battery is empty. The voltage might be even too low to be recharged. +Your battery is empty.
-Try to kickstart the loading process by connecting the read and black cables of the battery to a 3.7V source for about a minute. +
-Or if you have professional LiPo-charger complaining about voltage being too low, try NiMh mode, until you reach about 3.4V. Then continue loading normally or via a USB. +
-BE CAREFUL and ask an experienced friend to help you.+
  
 ===== on/off switch is not working ​ anymore ===== ===== on/off switch is not working ​ anymore =====
troubleshooting.1443982271.txt.gz · Last modified: 2015/10/04 20:11 by neels