Group Actions
Engagement
  • Author Author: clem57
  • Date Created: Date Created
  • Views 669 views
  • Likes 3 likes
  • Comments 5 comments
Related
Recommended

Projects using Pi 3

clem57

First usage of Pi 3

 

I installed the Piaware software to feed ADS-B into FlightAware. At first I had problem with Dongle in use:

 

Found 1 device(s):

0: Generic RTL2832U

  Using device 0: Generic RTL2832U

  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
Failed to open rtlsdr device #0.

 

Luckily a solution is pretty straightforward. In /etc/modprobe.d create a file called blacklist.conf with the following:

 

blacklist dvb_usb_rtl28xxu
blacklist rtl2832
blacklist rtl2830

 

Apparently the upgrade incorporates a new Linux kernel which includes a DVB driver for the dongle as a TV receiver.  Since the device is already in use by this driver, usage fails by anything else. Next:

 

sudo reboot

 

Problem gone. Software works great on Pi 3.

 

Cheers,

Clem

Parents

  • The default driver for the DVB dongle is obviously the DVB one in almost all  the distros both for the RPI and for other devices so the possible/probable requirement to Blacklist or remove the DVB driver is a common one.

     

    You can have say one DVB dongle and another for SDR use by having both drivers but either forcing them to the correct devices via comman line options or UDev configurations based on say the device S/N rather than just the USB  ID

Comment

  • The default driver for the DVB dongle is obviously the DVB one in almost all  the distros both for the RPI and for other devices so the possible/probable requirement to Blacklist or remove the DVB driver is a common one.

     

    You can have say one DVB dongle and another for SDR use by having both drivers but either forcing them to the correct devices via comman line options or UDev configurations based on say the device S/N rather than just the USB  ID

Children
No Data