Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to start from Raspberry PI 3 #1

Open
bousqi opened this issue Dec 14, 2016 · 2 comments
Open

Failed to start from Raspberry PI 3 #1

bousqi opened this issue Dec 14, 2016 · 2 comments

Comments

@bousqi
Copy link

bousqi commented Dec 14, 2016

Python interface refuses to start. Any hint to fix it ?

rpi-stable:/usr/local/src/rt2382 $ r820tweak
/usr/local/bin/r820tweak:258: wxPyDeprecationWarning: Using deprecated class PySimpleApp.
app = wx.PySimpleApp()
Traceback (most recent call last):
File "/usr/local/bin/r820tweak", line 266, in
main()
File "/usr/local/bin/r820tweak", line 260, in main
MyPanel(frame,-1)
File "/usr/local/bin/r820tweak", line 169, in init
value=self.device_list[0],
IndexError: list index out of range

@gat3way
Copy link
Owner

gat3way commented Dec 14, 2016

I just had a very similar mail, so I will repost my reply:

Hello,

I can think of two possible reasons for this:

  1. The modified librtlsdr.so was not loaded by any program - this means you haven't started any SDR software via r820tweak, e.g to run gqrx with the custom driver, you need to type "r820tweak gqrx". In this case, the GUI counterpart is unable to communicate with the modified driver and it will fail. Note that r820tweak can only modify the i2c registers of already initialized (opened) device, for a number of reasons, one of them is this is the only way to know the device has gone through a proper initialization. You cannot tweak registers of non-active devices, they have to be running and they have to be running the modified librtlsdr.so. Obviously, r820tweak needs to die in a more graceful manner in cases like that, with useful error messages, sorry for that, I guess that was confusing.

  2. It is also possible but not likely that this is a filesystem permissions issue - since it uses unix domain sockets in /var/tmp - if the directory is not writable or the sockets are owned by different user with no permissions to read/write by the user that runs the GUI, it would fail the same way.

Apparently error reporting needs to improve :)

Regards,
Milen

@sv1
Copy link

sv1 commented Dec 16, 2016

The answer is in the terminal:

......

Kernel driver is active, or device is claimed by second instance of librtlsdr.
In the first case, please either detach or blacklist the kernel module
(dvb_usb_rtl28xxu), or enable automatic detaching at compile time.
usb_claim_interface error -6
FATAL: Failed to open rtlsdr device.
......

use $ rmmod -f dvb_usb_rtl28xxu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants