I am not a total Linux noob, but I do have some knowledge gaps (particularly when it comes to drivers) and I'm kind of at a loss for how to proceed. I tried posting this to the Raspberry Pi forum, but was told I should post this question here. I have an old TV Tuner model Hauppauge WinTV-HVR-950 (not Hauppauge WinTV-HVR-950Q which supposedly has drivers included in the kernel). I was able to successfully configure it on my Raspberry Pi 4, but I'm now trying to set it up my new Raspberry Pi 5. When I set it up on the 4, I followed some guides, but I really didn't know what I was doing. Now, following what I think was the same guide, I have not been able to get it to work and I'm finding conflicting information about what exactly I'm supposed to do. Here is the best source of information I've been able to find on getting this TV Tuner to work in Linux: Hauppauge_WinTV-HVR-950 . So far, I've extracted the firmware from the Windows drivers (per the guide) and copied it to /lib/firmware:

cp xc3028-v27.fw /lib/firmware

I have also verified that the device is connected and detected using lsusb. The next section of the LinuxTV guide says: > Drivers > > Use a recent snapshot of LinuxTV's v4l-dvb drivers > > Both analog and ATSC digital reception are supported Read the above mentioned Firmware section for details on installing the proper firmware. That brings me to this website, LinuxTV : The instructions become very vague at this point and the documentation on that site completely overwhelming without any specific instructions about what to do. A Google search brings up this guide: How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers . The method described under "Retrieving and Building/Compiling the Latest media drivers Source Code" doesn't work because the only thing at git://linuxtv.org/media_build.git is a README file which says the project has been abandoned. I was able to successfully follow the instructions starting at "Retrieving from the upstream development Kernel tree" until I get to "Installing the Compiled Driver Modules" and running this command:

sudo make modules_install install

Which give the following output with an error about unsupported initramfs version (which means nothing to me):

INSTALL [a whole bunch of stuff] ... run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.14.0-rc1-v8-16k+ /boot/vmlinuz-6.14.0-rc1-v8-16k+
update-initramfs: Generating /boot/initrd.img-6.14.0-rc1-v8-16k+
ERROR: Unsupported initramfs version (6.14.0-rc1-v8-16k+)
run-parts: executing /etc/kernel/postinst.d/z50-raspi-firmware 6.14.0-rc1-v8-16k+ /boot/vmlinuz-6.14.0-rc1-v8-16k+

And this command:

sudo make install

Which gives a similar output, but without all the INSTALL messages, still with the error:

INSTALL /boot
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.14.0-rc1-v8-16k+ /boot/vmlinuz-6.14.0-rc1-v8-16k+
update-initramfs: Generating /boot/initrd.img-6.14.0-rc1-v8-16k+
ERROR: Unsupported initramfs version (6.14.0-rc1-v8-16k+)
run-parts: executing /etc/kernel/postinst.d/z50-raspi-firmware 6.14.0-rc1-v8-16k+ /boot/vmlinuz-6.14.0-rc1-v8-16k+

Someone suggested running this command to solve the initramfs error:

apt-get auto-remove && apt-get clean && apt-get update && apt-get upgrade

Which gives:

Removing [a couple of things] ... 
E: Could not open lock file /var/cache/apt/archives/lock - open (13: Permission denied)
E: Unable to lock directory /var/cache/apt/archives/
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)

I'm really not sure what this command what meant to accomplish, but it doesn't solve the problem as I still get the same errors when running sudo make install. Now I'm totally stuck and have no idea how to proceed. In sum here is the process and what I've done as I understand it. - Extract firmware from windows driver - Install firmware to Raspberry Pi - Compile LinuxTV's v4l-dvb drivers - Install LinuxTV's v4l-dvb drivers (errors) Any help? Am I at least understanding the process and steps correctly? Some final notes. I've been able to gather that some other DVR/DVB/Media Center applications such as OSMC do not have drivers yet for Raspberry Pi 5, which may be a factor here, but I'm not sure. I've also considered trying to pull the driver from the Pi 4, but I wouldn't know where to look and also I expect that it wouldn't work given that it is on a much older kernel version, but again I'm not very knowledgeable about how drivers work in Linux. I also have a MyGica A681B USB TV tuner that works on Windows. It claims to have a Linux driver, but the instructions provided are not very clear and I've never seen a case of someone actually getting it to work on Linux. I've followed the instructions here: and installed the driver here: , but I have never been able to get it to work. In this post: Someone suggests that it won't work since the driver provided is not "suitable for Debian ARMHF". Someone else suggests that it should be possible since "they're kernel drivers they should all be platform agnostic". Either way, the post ends without any resolution and I was never able to get it working on the Pi 4, so I don't have a lot of hope here, but I'm open to suggestions on that device as well.

I can't get my Walkera Dvb-t2 dongle to work on Ubuntu 18.

shows

Semiconductor Corp. RTL2838 DVB-T.

There is also no /dev/dvb directory.
What should I do to make it work?
Update

sudo dmesg | grep dvb
[   45.943415] dvb_core: disagrees about version of symbol vb2_vmalloc_memops
[   45.943417] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22)
[   45.956252] dvb_core: disagrees about version of symbol vb2_vmalloc_memops
[   45.956253] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22)
[ 1033.304738] dvb_core: disagrees about version of symbol vb2_vmalloc_memops
[ 1033.304740] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22)
[ 1033.320396] dvb_core: disagrees about version of symbol vb2_vmalloc_memops
[ 1033.320399] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22)
[ 5795.005693] dvb_core: disagrees about version of symbol vb2_vmalloc_memops
[ 5795.005695] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22)
[ 5795.030806] dvb_core: disagrees about version of symbol vb2_vmalloc_memops
[ 5795.030808] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22)
[ 6396.612446] dvb_core: disagrees about version of symbol vb2_vmalloc_memops
[ 6396.612448] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22)
[ 6396.637432] dvb_core: disagrees about version of symbol vb2_vmalloc_memops
[ 6396.637437] dvb_core: Unknown symbol vb2_vmalloc_memops (err -22)

dmesg | grep "RTL"
[    0.935974] r8169 0000:09:00.0 eth0: RTL8105e at 0x        (ptrval), e0:db:55:87:98:0c, XID 00c00000 IRQ 25
[    1.596255] usb 2-1.2: Product: RTL2838UHIDIR
[ 1033.264648] usb 1-1.2: Product: RTL2838UHIDIR
[ 5794.959085] usb 2-1.2: Product: RTL2838UHIDIR
[ 6396.552519] usb 2-1.2: Product: RTL2838UHIDIR

Please, help I have a TV tuner on Windows, there are no problems with it - all frequencies are found and shown, but in Linux it cannot find all frequencies ( https://linuxtv.org/wiki/index.php/Astrometa_DVB-T2 with Sony CXD2837ER finds from 722000 frequencies to 778000, but from 786000 to 858000 writes - no signal DVB-С or tell me please where to write? I've never run into problems on Linux so I don't know where to write and where to create tickets. i try write email to media-workshop@linuxtv.org, pkg-vdr-dvb-devel@lists.alioth.debian.org but there was no answer (

$ uname -a

Linux hs0 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux



$ sudo w_scan -fc -S3 -Q1 -a /dev/dvb/adapter0/frontend1

w_scan -fc -S3 -Q1 -a /dev/dvb/adapter0/frontend1 

w_scan version 20170107 (compiled for DVB API 5.10)

WARNING: could not guess your country. Falling back to 'DE'

guessing country 'DE', use -c  to override

using settings for GERMANY

DVB cable

DVB-C

scan type CABLE, channellist 7

output format vdr-2.0

WARNING: could not guess your codepage. Falling back to 'UTF-8'

output charset 'UTF-8', use -C  to override

-_-_-_-_ Getting frontend capabilities-_-_-_-_ 

Using DVB API 5.11

frontend 'Sony CXD2837ER DVB-T/T2/C demodulator' supports

INVERSION_AUTO

QAM_AUTO

FEC_AUTO

FREQ (42.00MHz ... 1002.00MHz)

SRATE (0.870MSym/s ... 11.700MSym/s)

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 

73000: sr6956 (time: 00:00.219) 

81000: sr6956 (time: 00:05.063) 
.
.
.
714000: sr6956 (time: 04:37.661) 

722000: sr6956 (time: 04:42.289)         signal ok: QAM_AUTO f = 722000 kHz S6956C999  (0:0:0)

        QAM_AUTO f = 722000 kHz S6956C999  (0:0:0) : updating network_id -> (0:100:0)

        already known: (QAM_AUTO f = 722000 kHz S6956C999  (0:100:0)), but not found by pids

        QAM_AUTO f = 722000 kHz S6956C999  (0:100:0) : updating tp ids -> (100:100:25)

        updating transponder:

           (QAM_AUTO f = 722000 kHz S6956C999  (100:100:25)) 0x0000

        to (QAM_256  f = 722000 kHz S6956C0  (100:100:25)) 0x4044

        new transponder: (QAM_256  f = 730000 kHz S6956C0  (100:100:26)) 0x4044

        new transponder: (QAM_256  f = 738000 kHz S6956C0  (100:100:27)) 0x4044
.
.
.

        new transponder: (QAM_256  f = 850000 kHz S6956C0  (100:100:46)) 0x4044

        new transponder: (QAM_256  f = 858000 kHz S6956C0  (100:100:47)) 0x4044

730000: skipped (already known transponder)

738000: skipped (already known transponder)
.
.
.
810000: skipped (already known transponder)

818000: skipped (already known trans

Andry, [11.11.20 12:46]
ponder)

826000: skipped (already known transponder)

834000: skipped (already known transponder)

842000: skipped (already known transponder)

850000: skipped (already known transponder)

858000: skipped (already known transponder)

tune to: QAM_256  f = 722000 kHz S6956C0  (100:100:25) (time: 04:46.489) 

 service = 001) info (H)

 service = 002) Perviy (H)
.
.
.
 service = 013) Spas (H)

tune to: QAM_256  f = 730000 kHz S6956C0  (100:100:26) (time: 04:59.773) 

 service = 014) CTC (H)
.
.
 service = 023) Tv Mytishi (H)

tune to: QAM_256  f = 738000 kHz S6956C0  (100:100:27) (time: 05:12.769) 

 service = 024) YOU (H)
.
.
 service = 036) Shopping live (H)

tune to: QAM_256  f = 746000 kHz S6956C0  (100:100:29) (time: 05:25.769) 

 service = 037) Russkij illuzio (H)
.
.
 service = 048) 8 kanal (H)

tune to: QAM_256  f = 754000 kHz S6956C0  (100:100:30) (time: 05:38.781) 

 service = 049) Indiyskoe kino (H)
.
.

 service = 060) Detsky (H)

tune to: QAM_256  f = 762000 kHz S6956C0  (100:100:31) (time: 05:51.769) 

 service = 061) Ryzhiy (H)
.
.
 service = 072) Auto plus (H)

tune to: QAM_256  f = 770000 kHz S6956C0  (100:100:33) (time: 06:04.781) 

 service = 073) Viasat Sport (H)
.
.
 service = 084) Dikiy (H)

tune to: QAM_256  f = 778000 kHz S6956C0  (100:100:34) (time: 06:17.773) 

WARNING: received garbage data: crc = 0x04e7f1d2; expected crc = 0x9b1462c5

increasing filter timeout to 31 secs (pid:0 table_id:0 table_id_ext:-1).

 service = 085) CHE (H)
.
.
 service = 096) Doctor (H)

WARNING: received garbage data: crc = 0x776b71b8; expected crc = 0x643c495e

increasing filter timeout to 40 secs (pid:16 table_id:64 table_id_ext:-1).

tune t

Andry, [11.11.20 12:46]
o: QAM_256  f = 786000 kHz S6956C0  (100:100:35) (time: 06:31.781) 

----------no signal----------

tune to: QAM_AUTO f = 786000 kHz S6956C999  (100:100:35) (time: 06:42.329)  (no signal)

----------no signal----------

tune to: QAM_256  f = 794000 kHz S6956C0  (100:100:37) (time: 06:49.968) 

----------no signal----------

tune to: QAM_AUTO f = 794000 kHz S6956C999  (100:100:37) (time: 06:57.664)  (no signal)

----------no signal----------

tune to: QAM_256  f = 802000 kHz S6956C0  (100:100:38) (time: 07:05.316) 

----------no signal----------
.
.
.
----------no signal----------

tune to: QAM_256  f = 850000 kHz S6956C0  (100:100:46) (time: 08:37.192) 

----------no signal----------

tune to: QAM_AUTO f = 850000 kHz S6956C999  (100:100:46) (time: 08:44.840)  (no signal)

----------no signal----------

tune to: QAM_256  f = 858000 kHz S6956C0  (100:100:47) (time: 08:52.456) 

----------no signal----------

tune to: QAM_AUTO f = 858000 kHz S6956C999  (100:100:47) (time: 09:00.076)  (no signal)

----------no signal----------

(time: 09:07.744) dumping lists (96 services)

..

001) info;H:722000:M256:C:6956:663=27:664=rus@4:0:0:1:100:25:0

002) Perviy;H:722000:M256:C:6956:650=27:651=rus@3:652:0:2:100:25:0
.
.
.
096) Doctor;H:778000:M256:C:6956:572=2:573@3:0:0:96:100:34:0


Done, scan time: 09:07.744

dvb-fe-tool is able to list some device capabilities and delivery systems, but it does not seem to list the supported codecs by the hardware. I'd like to know if my tuner supports MPEG4 hardware decoding or not without looking for the chip specs on the web.

I've been trying to get my Raspberry Pi to work with one of two TV Cards that I have available on me. Unfortunately I live in Hong Kong where due to the digital broadcast standard, leaves me with few choices of devices. Neither of which seem to want to play ball. For obvious reasons, both are USB. I have "determined" that one uses a RTL2836U chipset. Whilst the other is using a LME 2510C with a Maxim 2165E tuner and 8G75-A1 demoduator. I had been focusing my efforts to efforts on the RTL2836U and I just compiled some drivers (with the VID/PID added) and Linux seemed to load the modules, but then unloaded it due to an error. dmesg dvb_hdhomerun: disagrees about version of symbol dvb_dmxdev_init dvb_hdhomerun: Unknown symbol dvb_dmxdev_init (err -22) dvb_hdhomerun: disagrees about version of symbol dvb_register_adapter dvb_hdhomerun: Unknown symbol dvb_register_adapter (err -22) dvb_hdhomerun: disagrees about version of symbol dvb_dmxdev_release dvb_hdhomerun: Unknown symbol dvb_dmxdev_release (err -22) dvb_hdhomerun: disagrees about version of symbol dvb_frontend_detach dvb_hdhomerun: Unknown symbol dvb_frontend_detach (err -22) dvb_hdhomerun: disagrees about version of symbol dvb_unregister_frontend dvb_hdhomerun: Unknown symbol dvb_unregister_frontend (err -22) dvb_hdhomerun: disagrees about version of symbol dvb_register_frontend dvb_hdhomerun: Unknown symbol dvb_register_frontend (err -22) dvb_hdhomerun: disagrees about version of symbol dvb_unregister_adapter dvb_hdhomerun: Unknown symbol dvb_unregister_adapter (err -22) bcm2708 watchdog, heartbeat=10 sec (nowayout=0) tail -f /var/log/kern.log Mar 1 03:14:06 raspbmc kernel: dvb_hdhomerun: Unknown symbol dvb_dmxdev_release (err -22) Mar 1 03:14:06 raspbmc kernel: dvb_hdhomerun: disagrees about version of symbol dvb_frontend_detach Mar 1 03:14:06 raspbmc kernel: dvb_hdhomerun: Unknown symbol dvb_frontend_detach (err -22) Mar 1 03:14:06 raspbmc kernel: dvb_hdhomerun: disagrees about version of symbol dvb_unregister_frontend Mar 1 03:14:06 raspbmc kernel: dvb_hdhomerun: Unknown symbol dvb_unregister_frontend (err -22) Mar 1 03:14:06 raspbmc kernel: dvb_hdhomerun: disagrees about version of symbol dvb_register_frontend Mar 1 03:14:06 raspbmc kernel: dvb_hdhomerun: Unknown symbol dvb_register_frontend (err -22) Mar 1 03:14:06 raspbmc kernel: dvb_hdhomerun: disagrees about version of symbol dvb_unregister_adapter Mar 1 03:14:06 raspbmc kernel: dvb_hdhomerun: Unknown symbol dvb_unregister_adapter (err -22) Mar 1 03:14:18 raspbmc kernel: bcm2708 watchdog, heartbeat=10 sec (nowayout=0) Then on insert of the dongle Mar 1 03:21:07 raspbmc kernel: usb 1-1.3: new high-speed USB device number 5 using dwc_otg Mar 1 03:21:07 raspbmc kernel: usb 1-1.3: New USB device found, idVendor=1f4d,idProduct=689b Mar 1 03:21:07 raspbmc kernel: usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 1 03:21:07 raspbmc kernel: usb 1-1.3: Product: USB Device Mar 1 03:21:07 raspbmc kernel: usb 1-1.3: Manufacturer: realtek Mar 1 03:21:07 raspbmc kernel: usb 1-1.3: SerialNumber: 00000005 Mar 1 03:21:07 raspbmc kernel: WARNING: You are using an experimental version of the media stack. Mar 1 03:21:07 raspbmc kernel: As the driver is backported to an olderkernel, it doesn't offer Mar 1 03:21:07 raspbmc kernel: enough quality for its usage in production. Mar 1 03:21:07 raspbmc kernel: Use it with care. Mar 1 03:21:07 raspbmc kernel: Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): Mar 1 03:21:07 raspbmc kernel: ed72d37a33fdf43dc47787fe220532cdec9da528 [media] media: Add 0x3009 USB PID to ttusb2 driver (fixed diff) Mar 1 03:21:07 raspbmc kernel: b9e2afff1e6b36d05a0e12b6114eb0aaf8949c09 [media] rtl28xxu: Add USB IDs for Compro VideoMate U620F Mar 1 03:21:07 raspbmc kernel: 676fa7d4c9fd141a31cba2870e592a597c0bb07f [media] em28xx: add usb id for terratec h5 rev. 3 Mar 1 03:21:07 raspbmc kernel: usb 1-1.3: dvb_usb_v2: found a 'MYGICA D690U' in warm state Mar 1 03:21:07 raspbmc kernel: usbcore: registered new interface driver dvb_usb_rtl28xxu Mar 1 03:21:10 raspbmc kernel: usb 1-1.3: dvb_usb_v2: 'MYGICA D690U' error while loading driver (-110) Mar 1 03:21:10 raspbmc kernel: usb 1-1.3: dvb_usb_v2: 'MYGICA D690U' successfully deinitialized and disconnected Aptitude is showing me these modules v linux-headers p linux-headers-2.6-mx5 p linux-headers-2.6-omap p linux-headers-3.2.0-4-all p linux-headers-3.2.0-4-all-armhf p linux-headers-3.2.0-4-common p linux-headers-3.2.0-4-rpi i linux-headers-generic p linux-headers-mx5 p linux-headers-omap p linux-headers-vexpress v linux-kernel-headers

I recently installed a skystar hd2 card in my box. I have drivers loaded, everything seems good to go but i cant tune. When I attempt to run w_scan (from apt-get, w_scan version 20130331, compiled for DVB API 5.10) I receive srate errors. Specifically: # w_scan -fs -s S93W1 US -k > a.conf w_scan version 20130331 (compiled for DVB API 5.10) using settings for 93.1 west Galaxy 25 scan type SATELLITE, channellist 111 output format kaffeine channels.dvb WARNING: could not guess your codepage. Falling back to 'UTF-8' output charset 'UTF-8', use -C to override Info: using DVB adapter auto detection. /dev/dvb/adapter0/frontend0 -> SATELLITE "STB0899 Multistandard": very good :-)) Using SATELLITE frontend (adapter /dev/dvb/adapter0/frontend0) -_-_-_-_ Getting frontend capabilities-_-_-_-_ Using DVB API 5.a frontend 'STB0899 Multistandard' supports INVERSION_AUTO DVB-S DVB-S2 FREQ (0.95GHz ... 2.15GHz) SRATE (5.000MSym/s ... 45.000MSym/s) using LNB "UNIVERSAL" -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ trying 'S f = 11780 kHz V SR = 30000 5/6 0,35 QPSK' (time: 00:01) trying 'S f = 11874 kHz H SR = 19510 3/4 0,35 QPSK' (time: 00:04) trying 'S f = 11890 kHz H SR = 3000 3/4 0,35 QPSK' (time: 00:08) skipped: (srate 3000000 unsupported by driver) initial_tune:2271: Setting frontend failed S f = 11890 kHz H SR = 3000 3/4 0,35 QPSK trying 'S f = 11915 kHz H SR = 4350 3/4 0,35 QPSK' (time: 00:08) skipped: (srate 4350000 unsupported by driver) initial_tune:2271: Setting frontend failed S f = 11915 kHz H SR = 4350 3/4 0,35 QPSK trying 'S f = 11996 kHz V SR = 3650 3/4 0,35 QPSK' (time: 00:09) skipped: (srate 3650000 unsupported by driver) initial_tune:2271: Setting frontend failed S f = 11996 kHz V SR = 3650 3/4 0,35 QPSK ERROR: Sorry - i couldn't get any working frequency/transponder Nothing to scan!! # Couldnt find a way to configure the srate for my card. When I run kaffeine to tune and scan for channels (I have it configured it to scan with the same satellite settings): kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" kaffeine(10272) DvbLinuxDevice::tune: ioctl FE_SET_FRONTEND failed for frontend "/dev/dvb/adapter0/frontend0" I have no idea why the frontend would fail. **SPECS** - I have a skystar HD2 installed in a pc running Ubuntu 14.04.3 LTS with kernel 3.19.0-25-generic. - I live in the US so I'm using the Galaxy 25 Satellite - I compiled the latest v4l-dvb source and rebooted to load its modules (followed the instructions here to the **T**), built installed dvb-apps and szap-s2. Some more diagnostics: # ls /dev/dvb adapter0 # ls /dev/dvb/adapter0 demux0 dvr0 frontend0 net0 # I just want to be able to tune and sniff some DVB-S channels w/o having to work on a Windows box

I'm trying to compile loadable kernel modules (.ko files) to support different USB DVB tuners on a Linux embedded system (a QNAP NAS specifically) with **kernel 4.2.8**. This system doesn't have udev (or better, it has, but basically you cannot touch it) so I need to build the kernel modules and then **insmod** them one after another. I've managed to build the .ko files which load correctly but I need to know which modules are needed for a specific DVB tuner **without having it** in hand. With some devices it's easy, for example Hauppauge `2040:7070 which uses dvb-usb-dib0700.ko` I can examine the module dependencies: [~] # modinfo dvb-usb-dib0700.ko | grep depends depends: dib7000m,dib9000,dibx000_common,dvb-usb,dib0090,dib0070,dib3000mc,rc-core and I can insmod all the different frontends like `dib7000m.ko`, etc. and the tuner is perfectly detected (reported by **dmesg**) with the **/dev/dvb** node created accordingly. Some other devices, instead, are more difficult and this raises my question. Consider for example Pinnacle PCTV DVB-S2 `2013:024c`: the dmesg log reported on [its LinuxTV page](https://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_DVB-S2_Stick_(460e)) suggests it may use **em28xx**, **a8293** and **TDA10071** but **modinfo** doesn't help in this case: # modinfo em28xx-dvb.ko | grep depends depends: em28xx # modinfo em28xx.ko | grep depends depends: As you can see, there are no references here to the frontends a8293 and TDA10071 (which exist on kernel 4.2.8 as loadable kernel modules), so how can I know without having the phisical device which tuners and frontends kernel modules it needs? I'm asking because a friend with that tuner tried to insmod `dvb-frontends/a8293.ko and dvb-frontends/tda10071.ko` but still dmesg doesn't say **Successfully loaded em28xx-dvb** and neither **/dev/dvb** is created, so I think another kernel module is missing. But what module? Kernel modules also change with kernel versions, so the LinuxTV page may not be correct for our kernel 4.2.8. When connecting an USB tuner to a Debian virtual machine, the system automatically loads the required kernel modules for tuners and frontends using **udev**. Where does the OS find this information about the tuner? If it's hardcoded somewhere, can I extract it to understand which are the correct kernel modules for a tuner by its lsusb ID? I would like to replicate on the embedded system the exact procedure that Debian does. EDIT: By continuing to search on the net, I found that **udev** may use **modalias** to match the available kernel modules and see if they're needed. But even if I have the tuner attached on the embedded system (which doesn't use udev) how can I "inspect" the different i2c aliases?

I'm trying to setup a dvb device on Slackware 14.2 bash-4.3# lsusb | grep YUAN Bus 001 Device 003: ID 1164:7efd YUAN High-Tech Development Co., Ltd bash-4.3# udevadm info --path=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 P: /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 N: bus/usb/001/003 E: BUSNUM=001 E: DEVNAME=/dev/bus/usb/001/003 E: DEVNUM=003 E: DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 E: DEVTYPE=usb_device E: DRIVER=usb E: ID_BUS=usb E: ID_MEDIA_PLAYER=zte_score E: ID_MODEL=STK7700D E: ID_MODEL_ENC=STK7700D E: ID_MODEL_ID=7efd E: ID_REVISION=0100 E: ID_SERIAL=YUANRD_STK7700D_0000000001 E: ID_SERIAL_SHORT=0000000001 E: ID_USB_INTERFACES=:ff0000: E: ID_VENDOR=YUANRD E: ID_VENDOR_ENC=YUANRD E: ID_VENDOR_FROM_DATABASE=YUAN High-Tech Development Co., Ltd E: ID_VENDOR_ID=1164 E: MAJOR=189 E: MINOR=2 E: PRODUCT=1164/7efd/100 E: SUBSYSTEM=usb E: TAGS=:udev-acl: E: TYPE=0/0/0 E: USEC_INITIALIZED=15164626 I created the following files (commented out line failed) bash-4.3# cat /etc/udev/rules.d/10-local.rules #ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd", RUN+="firmware --firmware=/lib/firmware/dvb-usb-dib0700-1.20.fw --devpath=$env{DEVPATH}" ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd", RUN+="/sbin/modprobe dvb-usb-dib0700" #KERNEL=="dvb0.dvr*", ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd", NAME="dvb/adapter0/dvr%n", SYMLINK+="dvb/adapter0/dvr%n" #KERNEL=="dvb0.demux*", ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd", NAME="dvb/adapter0/demux%n", SYMLINK+="dvb/adapter0/demux%n" #KERNEL=="dvb0.frontend*", ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd", NAME="dvb/adapter0/frontend%n", SYMLINK+="dvb/adapter0/frontend%n" #KERNEL=="dvb0.audio*", ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd", NAME="dvb/adapter0/audio%n", SYMLINK+="dvb/adapter0/audio%n" #KERNEL=="dvb0.ca*", ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd" NAME="dvb/adapter0/ca%n", SYMLINK+="dvb/adapter0/ca%n" #KERNEL=="dvb0.osd*", ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd", NAME="dvb/adapter0/osd%n", SYMLINK+="dvb/adapter0/osd%n" #KERNEL=="dvb0.net*", ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd", NAME="dvb/adapter0/net%n", SYMLINK+="dvb/adapter0/net%n" #KERNEL=="dvb0.video*", ATTRS{idVendor}=="1164", ATTRS{idProduct}=="7efd", NAME="dvb/adapter0/video%n", SYMLINK+="dvb/adapter0/video%n" bash-4.3# echo 1164 7efd > /sys/bus/usb/drivers/dvb_usb_dib0700/new_id bash-4.3# cat /etc/modprobe.d/dvb.conf options dvb-usb-dib0700 force_lna_activation=1 But I still have not got a /dev/dvb directory. Where do I go wrong?

**libdvbv5** has no option for KU-CIRCULAR LNB frequency (10750,10750,0), how to solve this? in the Ubuntu Yakkety Yak libdvbv5 are used as a back end for kaffeine 2.0, and in the kaffeine 2.0 program, doesn't exist any option for LNB with the parameters: high 10750, low 10750, swith 0 i.e. for so-called ku-circular standard of Russia satellite tv. I don't know, how to create a patch for libdvbv5, to solve this problem. I only found [this patch](https://www.mail-archive.com/kde-bugs-dist@kde.org/msg119521.html) but that isn't what i need.

I'm trying to use w_scan to scan the transponders from a satellite, on Debian 8.0 it worked, but on Debian 8.7 it doesn't work. At the same time, i can scan all the transponders by using Kaffeine (Version 1.2.2). I.e. all is almost good, but I really need to get w_scan to work as well. How to solve the problem? sudo w_scan -t2 -l 10750,10750,0 -o21 -fs -sS36E0 -v -v **Log:**

w_scan version 20161022 (compiled for DVB API 5.10)
using settings for 36.0 east Eutelsat 36A/36B
scan type SATELLITE, channellist 58
output format vdr-2.1
WARNING: could not guess your codepage. Falling back to 'UTF-8'
output charset 'UTF-8', use -C  to override
Info: using DVB adapter auto detection.
   check Conexant CX24116/CX24118:
           DVB-S2
           DVB-S
        /dev/dvb/adapter0/frontend0 -> SATELLITE "Conexant CX24116/CX24118": very good :-))

Using SATELLITE frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_ 
Using DVB API 5.10
frontend 'Conexant CX24116/CX24118' supports
INVERSION_AUTO
DVB-S
DVB-S2
FREQ (0.95GHz ... 2.15GHz)
SRATE (1.000MSym/s ... 45.000MSym/s)
using LNB "(null)"
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ 
   check Conexant CX24116/CX24118:
           DVB-S2
           DVB-S
trying 'S  f = 11109 kHz V SR =  3418  2/3 0,35  QPSK  (0:0:0)'
(time: 00:00.331)        skipped: (freq 0.36 unsupported by driver: min=0.95, max=2.15)

initial_tune:2722: Setting frontend failed S  f = 11109 kHz V SR =  3418  2/3 0,35  QPSK  (0:0:0)
trying 'S  f = 11439 kHz H SR =  8250  5/6 0,35  QPSK  (0:0:0)'
(time: 00:00.331)        skipped: (freq 0.69 unsupported by driver: min=0.95, max=2.15)

initial_tune:2722: Setting frontend failed S  f = 11439 kHz H SR =  8250  5/6 0,35  QPSK  (0:0:0)
trying 'S  f = 11644 kHz V SR =  2170  3/4 0,35  QPSK  (0:0:0)'
(time: 00:00.331)        skipped: (freq 0.89 unsupported by driver: min=0.95, max=2.15)

initial_tune:2722: Setting frontend failed S  f = 11644 kHz V SR =  2170  3/4 0,35  QPSK  (0:0:0)
trying 'S  f = 11648 kHz V SR =  3110  3/4 0,35  QPSK  (0:0:0)'
(time: 00:00.331)        skipped: (freq 0.90 unsupported by driver: min=0.95, max=2.15)

initial_tune:2722: Setting frontend failed S  f = 11648 kHz V SR =  3110  3/4 0,35  QPSK  (0:0:0)
trying 'S  f = 11652 kHz V SR =  3110  3/4 0,35  QPSK  (0:0:0)'
(time: 00:00.331)        skipped: (freq 0.90 unsupported by driver: min=0.95, max=2.15)

initial_tune:2722: Setting frontend failed S  f = 11652 kHz V SR =  3110  3/4 0,35  QPSK  (0:0:0)
trying 'S2 f = 11692 kHz V SR =  1555  5/6 0,AUTO  8PSK  (0:0:0)'
(time: 00:00.331)        skipped: (freq 0.94 unsupported by driver: min=0.95, max=2.15)

initial_tune:2722: Setting frontend failed S2 f = 11692 kHz V SR =  1555  5/6 0,AUTO  8PSK  (0:0:0)
trying 'S  f = 11727 kHz V SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:00.331) 
        (0.864sec): SC (0x3)
        (0.864sec) signal
        (0.916sec): S (0x1)
        (1.068sec): SC (0x3)
        (1.272sec): S (0x1)
        (1.320sec): SC (0x3)
        (1.472sec): S (0x1)
        (1.524sec): SC (0x3)
        (1.576sec): S (0x1)
        (1.676sec): SC (0x3)
        (1.728sec): S (0x1)
        (1.828sec): SC (0x3)
        (1.880sec): S (0x1)
        (1.928sec): SC (0x3)
        (1.980sec): S (0x1)
        (2.084sec): SC (0x3)
        (2.132sec): S (0x1)
        (2.284sec): SC (0x3)
        (2.436sec): S (0x1)
        (2.488sec): SC (0x3)
trying 'S  f = 11747 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:02.971) 
        (0.868sec): S (0x1)
        (0.868sec) signal
        (0.920sec): SC (0x3)
        (0.968sec): S (0x1)
        (1.324sec): SC (0x3)
        (1.376sec): S (0x1)
        (1.628sec): SC (0x3)
        (1.680sec): S (0x1)
        (1.732sec): SC (0x3)
        (1.984sec): S (0x1)
        (2.136sec): SC (0x3)
        (2.240sec): S (0x1)
        (2.492sec): SC (0x3)
        (2.544sec): S (0x1)
trying 'S  f = 11766 kHz V SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:05.615) 
        (0.864sec): SC (0x3)
        (0.864sec) signal
        (0.964sec): S (0x1)
        (1.168sec): SC (0x3)
        (1.220sec): S (0x1)
        (1.776sec): SC (0x3)
        (1.880sec): S (0x1)
        (2.032sec): SC (0x3)
        (2.132sec): S (0x1)
        (2.184sec): SC (0x3)
        (2.236sec): S (0x1)
        (2.436sec): SC (0x3)
        (2.488sec): S (0x1)
        (2.592sec): SC (0x3)
        (2.640sec): S (0x1)
trying 'S  f = 11785 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:08.255) 
        (0.864sec): S (0x1)
        (0.864sec) signal
        (0.916sec): SC (0x3)
        (0.964sec): S (0x1)
        (1.016sec): SC (0x3)
        (1.116sec): S (0x1)
        (1.168sec): SC (0x3)
        (1.220sec): S (0x1)
        (1.272sec): SC (0x3)
        (1.372sec): S (0x1)
        (1.472sec): SC (0x3)
        (1.624sec): S (0x1)
        (1.676sec): SC (0x3)
        (1.776sec): S (0x1)
        (2.388sec): SC (0x3)
        (2.436sec): S (0x1)
        (2.540sec): SC (0x3)
trying 'S  f = 11823 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:10.895) 
        (0.864sec): S (0x1)
        (0.864sec) signal
        (1.168sec): SC (0x3)
        (1.220sec): S (0x1)
        (1.272sec): SC (0x3)
        (1.320sec): S (0x1)
        (1.472sec): SC (0x3)
        (1.524sec): S (0x1)
        (1.676sec): SC (0x3)
        (1.728sec): S (0x1)
        (1.880sec): SC (0x3)
        (1.932sec): S (0x1)
        (2.388sec): SC (0x3)
        (2.436sec): S (0x1)
        (2.488sec): SC (0x3)
        (2.588sec): S (0x1)
trying 'S  f = 11843 kHz V SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:13.535) 
        (0.864sec): S (0x1)
        (0.864sec) signal
        (1.016sec): SC (0x3)
        (1.116sec): S (0x1)
        (1.624sec): SC (0x3)
        (1.676sec): S (0x1)
        (1.728sec): SC (0x3)
        (1.828sec): S (0x1)
        (1.928sec): SC (0x3)
        (2.032sec): S (0x1)
        (2.084sec): SC (0x3)
        (2.184sec): S (0x1)
        (2.284sec): SC (0x3)
        (2.336sec): S (0x1)
        (2.540sec): SC (0x3)
        (2.640sec): S (0x1)
trying 'S  f = 11862 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:16.175) 
        (0.852sec): S (0x1)
        (0.852sec) signal
        (1.052sec): SC (0x3)
        (1.104sec): S (0x1)
        (1.204sec): SC (0x3)
        (1.256sec): S (0x1)
        (1.460sec): SC (0x3)
        (1.512sec): S (0x1)
        (1.712sec): SC (0x3)
        (1.816sec): S (0x1)
        (1.864sec): SC (0x3)
        (1.916sec): S (0x1)
        (2.220sec): SC (0x3)
        (2.272sec): S (0x1)
        (2.524sec): SC (0x3)
        (2.576sec): S (0x1)
trying 'S  f = 11881 kHz V SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:18.802) 
        (0.848sec): S (0x1)
        (0.848sec) signal
        (1.560sec): SC (0x3)
        (1.712sec): S (0x1)
        (1.760sec): SC (0x3)
        (1.864sec): S (0x1)
        (1.964sec): SC (0x3)
        (2.016sec): S (0x1)
        (2.068sec): SC (0x3)
        (2.116sec): S (0x1)
        (2.220sec): SC (0x3)
        (2.372sec): S (0x1)
        (2.420sec): SC (0x3)
        (2.576sec): S (0x1)
trying 'S  f = 11900 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:21.426) 
        (0.848sec): S (0x1)
        (0.848sec) signal
        (1.356sec): SC (0x3)
        (1.408sec): S (0x1)
        (1.456sec): SC (0x3)
        (1.508sec): S (0x1)
        (1.660sec): SC (0x3)
        (1.812sec): S (0x1)
        (2.016sec): SC (0x3)
        (2.116sec): S (0x1)
        (2.320sec): SC (0x3)
        (2.372sec): S (0x1)
        (2.420sec): SC (0x3)
        (2.472sec): S (0x1)
        (2.524sec): SC (0x3)
        (2.576sec): S (0x1)
trying 'S  f = 11919 kHz V SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:24.050) 
        (0.864sec): SC (0x3)
        (0.864sec) signal
        (0.916sec): S (0x1)
        (1.016sec): SC (0x3)
        (1.168sec): S (0x1)
        (1.220sec): SC (0x3)
        (1.272sec): S (0x1)
        (1.320sec): SC (0x3)
        (1.372sec): S (0x1)
        (1.424sec): SC (0x3)
        (1.472sec): S (0x1)
        (1.576sec): SC (0x3)
        (1.624sec): S (0x1)
        (1.728sec): SC (0x3)
        (1.776sec): S (0x1)
        (1.828sec): SC (0x3)
        (1.932sec): S (0x1)
        (2.084sec): SC (0x3)
        (2.136sec): S (0x1)
        (2.236sec): SC (0x3)
        (2.440sec): S (0x1)
        (2.488sec): SC (0x3)
trying 'S  f = 11940 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:26.690) 
        (0.864sec): SC (0x3)
        (0.864sec) signal
        (0.916sec): S (0x1)
        (0.964sec): SC (0x3)
        (1.016sec): S (0x1)
        (1.424sec): SC (0x3)
        (1.472sec): S (0x1)
        (1.576sec): SC (0x3)
        (1.676sec): S (0x1)
        (1.828sec): SC (0x3)
        (1.932sec): S (0x1)
        (1.984sec): SC (0x3)
        (2.032sec): S (0x1)
        (2.132sec): SC (0x3)
        (2.284sec): S (0x1)
        (2.488sec): SC (0x3)
        (2.540sec): S (0x1)
trying 'S  f = 11958 kHz V SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:29.330) 
        (0.864sec): S (0x1)
        (0.864sec) signal
        (0.964sec): SC (0x3)
        (1.016sec): S (0x1)
        (1.068sec): SC (0x3)
        (1.120sec): S (0x1)
        (1.324sec): SC (0x3)
        (1.472sec): S (0x1)
        (1.628sec): SC (0x3)
        (1.676sec): S (0x1)
        (2.084sec): SC (0x3)
        (2.136sec): S (0x1)
        (2.184sec): SC (0x3)
        (2.284sec): S (0x1)
        (2.336sec): SC (0x3)
        (2.388sec): S (0x1)
        (2.488sec): SC (0x3)
        (2.540sec): S (0x1)
trying 'S  f = 11977 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:31.970) 
        (0.864sec): S (0x1)
        (0.864sec) signal
        (1.168sec): SC (0x3)
        (1.220sec): S (0x1)
        (1.272sec): SC (0x3)
        (1.476sec): S (0x1)
        (1.624sec): SC (0x3)
        (1.676sec): S (0x1)
        (1.728sec): SC (0x3)
        (1.780sec): S (0x1)
        (1.828sec): SC (0x3)
        (1.880sec): S (0x1)
        (1.932sec): SC (0x3)
        (1.984sec): S (0x1)
        (2.032sec): SC (0x3)
        (2.084sec): S (0x1)
        (2.588sec): SC (0x3)
        (2.640sec): S (0x1)
trying 'S  f = 11996 kHz V SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:34.609) 
        (0.880sec): S (0x1)
        (0.880sec) signal
        (0.980sec): SC (0x3)
        (1.032sec): S (0x1)
        (1.288sec): SC (0x3)
        (1.440sec): S (0x1)
        (1.848sec): SC (0x3)
        (1.896sec): S (0x1)
        (2.000sec): SC (0x3)
        (2.148sec): S (0x1)
        (2.504sec): SC (0x3)
        (2.608sec): S (0x1)
        (2.656sec): SC (0x3)
trying 'S  f = 12015 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:37.265) 
        (0.880sec): S (0x1)
        (0.880sec) signal
        (0.932sec): SC (0x3)
        (0.980sec): S (0x1)
        (1.084sec): SC (0x3)
        (1.184sec): S (0x1)
        (1.288sec): SC (0x3)
        (1.336sec): S (0x1)
        (1.388sec): SC (0x3)
        (1.540sec): S (0x1)
        (2.352sec): SC (0x3)
        (2.404sec): S (0x1)
        (2.452sec): SC (0x3)
        (2.556sec): S (0x1)
        (2.608sec): SC (0x3)
trying 'S  f = 12034 kHz V SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:39.925) 
        (0.876sec): S (0x1)
        (0.876sec) signal
        (0.928sec): SC (0x3)
        (0.980sec): S (0x1)
        (1.132sec): SC (0x3)
        (1.280sec): S (0x1)
        (1.336sec): SC (0x3)
        (1.384sec): S (0x1)
        (1.688sec): SC (0x3)
        (1.740sec): S (0x1)
        (2.044sec): SC (0x3)
        (2.096sec): S (0x1)
        (2.196sec): SC (0x3)
        (2.448sec): S (0x1)
        (2.500sec): SC (0x3)
        (2.600sec): S (0x1)
trying 'S  f = 12054 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:42.577) 
        (0.852sec): S (0x1)
        (0.852sec) signal
        (0.904sec): SC (0x3)
        (1.004sec): S (0x1)
        (1.308sec): SC (0x3)
        (1.356sec): S (0x1)
        (1.564sec): SC (0x3)
        (1.612sec): S (0x1)
        (1.816sec): SC (0x3)
        (1.864sec): S (0x1)
        (1.968sec): SC (0x3)
        (2.020sec): S (0x1)
        (2.068sec): SC (0x3)
        (2.220sec): S (0x1)
        (2.428sec): SC (0x3)
        (2.476sec): S (0x1)
        (2.528sec): SC (0x3)
        (2.580sec): S (0x1)
trying 'S  f = 12073 kHz V SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:45.205) 
        (0.848sec): S (0x1)
        (0.848sec) signal
        (1.000sec): SC (0x3)
        (1.052sec): S (0x1)
        (1.360sec): SC (0x3)
        (1.460sec): S (0x1)
        (1.764sec): SC (0x3)
        (1.864sec): S (0x1)
        (1.916sec): SC (0x3)
        (2.016sec): S (0x1)
        (2.220sec): SC (0x3)
        (2.268sec): S (0x1)
        (2.524sec): SC (0x3)
        (2.628sec): S (0x1)
trying 'S  f = 12245 kHz H SR = 27500  3/4 0,35  QPSK  (0:0:0)'
(time: 00:47.833) 
        (0.876sec): S (0x1)
        (0.876sec) signal
        (1.080sec): SC (0x3)
        (1.184sec): S (0x1)
        (1.284sec): SC (0x3)
        (1.336sec): S (0x1)
        (1.844sec): SC (0x3)
        (1.892sec): S (0x1)
        (2.044sec): SC (0x3)
        (2.148sec): S (0x1)
        (2.452sec): SC (0x3)
        (2.500sec): S (0x1)
trying 'S2 f = 12284 kHz H SR = 27500  3/4 0,AUTO  QPSK  (0:0:0)'
(time: 00:50.488) 
        (0.100sec): SC (0x3)
        (0.100sec) signal
        (0.152sec): S (0x1)
        (0.404sec): SC (0x3)
        (0.604sec): S (0x1)
        (0.708sec): SC (0x3)
        (0.756sec): S (0x1)
        (0.908sec): SC (0x3)
        (0.964sec): S (0x1)
        (1.112sec): SC (0x3)
        (1.216sec): S (0x1)
        (1.268sec): SC (0x3)
        (1.320sec): S (0x1)
        (1.368sec): SC (0x3)
        (1.420sec): S (0x1)
        (1.472sec): SC (0x3)
        (1.520sec): S (0x1)
        (1.624sec): SC (0x3)
        (1.724sec): S (0x1)
        (1.824sec): SC (0x3)
        (1.876sec): S (0x1)
trying 'S  f = 12437 kHz H SR = 23438  3/4 0,35  QPSK  (0:0:0)'
(time: 00:52.364) 
        (0.848sec): S (0x1)
        (0.848sec) signal
        (0.952sec): SC (0x3)
        (1.004sec): S (0x1)
        (1.104sec): SC (0x3)
        (1.156sec): S (0x1)
        (1.204sec): SC (0x3)
        (1.256sec): S (0x1)
        (1.456sec): SC (0x3)
        (1.560sec): S (0x1)
        (1.712sec): SC (0x3)
        (1.868sec): S (0x1)
        (1.968sec): SC (0x3)
        (2.020sec): S (0x1)
        (2.068sec): SC (0x3)
        (2.120sec): S (0x1)
        (2.172sec): SC (0x3)
        (2.272sec): S (0x1)
        (2.476sec): SC (0x3)
        (2.576sec): S (0x1)
trying 'S  f = 12508 kHz H SR =  2278  5/6 0,35  QPSK  (0:0:0)'
(time: 00:54.992) 
        (0.848sec): S (0x1)
        (0.848sec) signal
        (1.612sec): SC (0x3)
        (1.812sec): S (0x1)
trying 'S  f = 12512 kHz H SR =  4340  1/2 0,35  QPSK  (0:0:0)'
(time: 00:57.616) 
        (0.836sec): S (0x1)
        (0.836sec) signal
trying 'S  f = 12521 kHz H SR =  4340  1/2 0,35  QPSK  (0:0:0)'
(time: 01:00.228) 
        (0.836sec): S (0x1)
        (0.836sec) signal
trying 'S  f = 12542 kHz V SR =  2220  3/4 0,35  QPSK  (0:0:0)'
(time: 01:02.840) 
        (0.836sec): S (0x1)
        (0.836sec) signal
trying 'S  f = 12573 kHz V SR =  2170  3/4 0,35  QPSK  (0:0:0)'
(time: 01:05.456) 
        (0.836sec): S (0x1)
        (0.836sec) signal
        (1.800sec): SC (0x3)
        (1.952sec): S (0x1)
trying 'S  f = 12620 kHz V SR =  2894  3/4 0,35  QPSK  (0:0:0)'
(time: 01:08.067) 
        (0.836sec): S (0x1)
        (0.836sec) signal
trying 'S  f = 12626 kHz V SR =  2890  3/4 0,35  QPSK  (0:0:0)'
(time: 01:10.679) 
        (0.836sec): S (0x1)
        (0.836sec) signal
trying 'S  f = 12630 kHz H SR =  2238  5/6 0,35  QPSK  (0:0:0)'
(time: 01:13.291) 
        (0.836sec): S (0x1)
        (0.836sec) signal
        (1.952sec): SC (0x3)
        (2.104sec): S (0x1)

ERROR: Sorry - i couldn't get any working frequency/transponder
 Nothing to scan!!

A test with szap:

sudo szap  -H -r -c /var/lib/vdr/channels.conf -n 1 -x -l 10750,10750,0
reading channels from file '/var/lib/vdr/channels.conf'
zapping to 1 'KHL Channel;NTV+':
sat 0, frequency = 11785 MHz V, symbolrate 27500000, vpid = 0x0141, apid = 0x0191 sid = 0x0000
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
Version: 5.10    FE_CAN { DVB-S + DVB-S2 }
status 03 | signal  89% | snr   0% | ber 0 | unc 0 | 
status 03 | signal  89% | snr   0% | ber 0 | unc 0 | 
status 01 | signal  89% | snr   0% | ber 0 | unc 0 | 
status 01 | signal  89% | snr   0% | ber 0 | unc 0 | 
status 03 | signal  89% | snr   0% | ber 0 | unc 0 | 
status 03 | signal  89% | snr   0% | ber 0 | unc 0 | 
status 01 | signal  89% | snr   0% | ber 0 | unc 0 | 
status 03 | signal  89% | snr   0% | ber 0 | unc 0 | 
status 01 | signal  89% | snr   0% | ber 0 | unc 0 | 
status 01 | signal  89% | snr   0% | ber 0 | unc 0 |

Have not seen FE_HAS_LOCK

I'm not 100% sure whether this is the right site to ask, but I'll give it a shot. I have a Raspberry Pi with [OSMC](https://osmc.tv/) (f.k.a. RaspBMC, based on Raspbian) and [Pi-Hole](https://pi-hole.net/) on it and it has been working perfectly for a long time. Now I bought a DVB-C/T/T2 TV tuner (PCTV tripleStick 292e) which claims to work with Linux [](http://www.hauppauge.co.uk/site/products/data_292e.html) [](https://www.linuxtv.org/wiki/index.php/PCTV_Systems_tripleStick_T2_(292e)) because I want to run [Tvheadend](http://tvheadend.org/) . I put the stick in my Pi, but Tvheadend just detected a DVB-T device (which is useless in my case - I need DVB-C). I downloaded various firmware files and put them into /lib/firmware, but that didn't change anything despite the firmware files being used. I spent hours trying to get DVB-C to work, but I failed. Then I created another SD card with [OpenELEC](http://openelec.tv/) on it, installed Tvheadend, and checked the web UI. The stick was detected as two devices, DVB-T and DVB-C. That's what I expected from various videos I found. In general, I don't mind changing from OSMC to OpenELEC, but the problem is that I can't install Pi-Hole on an OpenELEC device because OpenELEC is so minimalistic that it doesn't event have a package manager. Unfortunately, it's the only Pi OS I know that works with my DVB-C stick. So does anyone have an idea how I can get my stick with OSMC/Raspbian to work? Or as an alternative: is it possible to combine Kodi, Tvheadend and Pi-Hole using another distribution, so it can be used as a media player "with extras" in the living room?

With kernels up to 3.19, all of my USB devices work perfectly. On upgrading to 4.0 or later, some of my USB devices stop working and the kernel produces errors like this: [ 3.369436] usb 9-1: device descriptor read/64, error -62 [ 3.593543] usb 9-1: new full-speed USB device number 4 using ohci-pci [ 3.997572] usb 9-1: device not accepting address 4, error -62 [ 4.120602] usb 9-1: new full-speed USB device number 5 using ohci-pci [ 4.524792] usb 9-1: device not accepting address 5, error -62 [ 4.524911] usb usb9-port1: unable to enumerate USB device [ 15.402105] usb 9-1: new full-speed USB device number 6 using ohci-pci [ 15.530135] usb 9-1: device descriptor read/64, error -62 [ 15.759224] usb 9-1: device descriptor read/64, error -62 [ 15.983312] usb 9-1: new full-speed USB device number 7 using ohci-pci [ 16.111309] usb 9-1: device descriptor read/64, error -62 [ 16.340398] usb 9-1: device descriptor read/64, error -62 [ 16.564378] usb 9-1: new full-speed USB device number 8 using ohci-pci [ 16.968454] usb 9-1: device not accepting address 8, error -62 [ 17.091555] usb 9-1: new full-speed USB device number 9 using ohci-pci [ 17.495570] usb 9-1: device not accepting address 9, error -62 [ 17.495603] usb usb9-port1: unable to enumerate USB device [ 17.673702] usb 9-1: new full-speed USB device number 10 using ohci-pci [ 17.801758] usb 9-1: device descriptor read/64, error -62 [ 18.030814] usb 9-1: device descriptor read/64, error -62 [ 18.254834] usb 9-1: new full-speed USB device number 11 using ohci-pci [ 18.382858] usb 9-1: device descriptor read/64, error -62 [ 18.611902] usb 9-1: device descriptor read/64, error -62 [ 18.835977] usb 9-1: new full-speed USB device number 12 using ohci-pci [ 19.240034] usb 9-1: device not accepting address 12, error -62 [ 19.363101] usb 9-1: new full-speed USB device number 13 using ohci-pci [ 19.767182] usb 9-1: device not accepting address 13, error -62 [ 19.767226] usb usb9-port1: unable to enumerate USB device That particular example was just a cheap USB memory card-reader....I don't really care about it. The more important issue to me is that the Quad DVB-T receiver on my mythtv backend box is also subject to the same problem, so I'm unable to upgrade that machine past 3.19 at the moment. This is a PCI-e card, that looks like it's some kind of pci-e to usb bridge, and the DVB tuners attached via usb. I'm not entirely sure but I think it might actually be a PCIe -> PCI -> USB card. Here are the card's details on a working 3.19 kernel: # lsusb | grep Leadtek Bus 010 Device 005: ID 0413:6680 Leadtek Research, Inc. Bus 010 Device 004: ID 0413:6680 Leadtek Research, Inc. Bus 010 Device 003: ID 0413:6680 Leadtek Research, Inc. Bus 010 Device 002: ID 0413:6680 Leadtek Research, Inc. # dmesg | grep -i DigitalNow| grep pci [ 9.405568] input: DigitalNow Quad DVB-T Receiver as /devices/pci0000:00/0000:00:0a.0/0000:04:00.0/0000:05:00.2/usb10/10-1/rc/rc1/input17 [ 9.405687] rc1: DigitalNow Quad DVB-T Receiver as /devices/pci0000:00/0000:00:0a.0/0000:04:00.0/0000:05:00.2/usb10/10-1/rc/rc1 [ 9.475939] input: DigitalNow Quad DVB-T Receiver as /devices/pci0000:00/0000:00:0a.0/0000:04:00.0/0000:05:00.2/usb10/10-2/rc/rc2/input22 [ 9.476049] rc2: DigitalNow Quad DVB-T Receiver as /devices/pci0000:00/0000:00:0a.0/0000:04:00.0/0000:05:00.2/usb10/10-2/rc/rc2 [ 9.542441] input: DigitalNow Quad DVB-T Receiver as /devices/pci0000:00/0000:00:0a.0/0000:04:00.0/0000:05:00.2/usb10/10-3/rc/rc3/input24 [ 9.542617] rc3: DigitalNow Quad DVB-T Receiver as /devices/pci0000:00/0000:00:0a.0/0000:04:00.0/0000:05:00.2/usb10/10-3/rc/rc3 [ 9.609134] input: DigitalNow Quad DVB-T Receiver as /devices/pci0000:00/0000:00:0a.0/0000:04:00.0/0000:05:00.2/usb10/10-4/rc/rc4/input26 [ 9.609289] rc4: DigitalNow Quad DVB-T Receiver as /devices/pci0000:00/0000:00:0a.0/0000:04:00.0/0000:05:00.2/usb10/10-4/rc/rc4 # lspci | grep '^0:' 04:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa) 05:00.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 62) 05:00.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 62) 05:00.2 USB controller: VIA Technologies, Inc. USB 2.0 (rev 65) # lspci -vv -s 05:00 05:00.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 62) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- ehci-hcd had to be loaded before ehci-pci. initramfs-tools has since been upgraded to handle that automatically, but i still have the commented out remnants of the workaround in my /etc/modules file: # make sure ehci-pci loads immediately after ehci-hcd for kernel 3.8 # (should be handled automagically by initramfs-tools 0.110 now) #ehci-hcd #ehci-pci **Is this a similar situation, that can be handled by loading drivers in a particular order or by blacklisting certain obsolete drivers?** --- Some more hardware and software details: This has occurred on several machines including: * Asus M4A89TD PRO USB3 motherboard with AMD Phenom II X6 1090T Processor (workstation) * Asus M5A97 with AMD Phenom II X6 1090T Processor (myth frontend) * Asus Sabertooth 990FX with AMD Phenom II X6 1090T Processor (workstation and server) * Asus Sabertooth 990FX with AMD FX(tm)-8150 Eight-Core Processor (myth backend) The last one, with the FX-8150 (which is what i had lying around when the previous motherboard died and i had to rebuild it), is the myth box with the DigitalNow Quad DVB-T Receiver. The first one, the M4A89TD Pro, is the machine with the cheap USB memory card-reader. All have at least 8GB RAM, and all have either nvidia GTX-750 (myth boxes) or GTX-560 or GTX-560Ti GPUs, using the proprietary nvidia driver. All are running Debian sid, with recent kernels (4.2.x on everything but the myth backend as that's the only one where USB is important for anything but HID - USB kbd and mouse and even a wacom tablet work fine, BTW, on 4.0+ kernels). All machines boot off 128-256GB SSDs in RAID-1 using XFS for / and ext4 for /boot. The mythtv backend is also running zfsonlinux for bulk storage. As is the combined workstation/server. I have tried debian stock kernels, liquorix kernels, and custom-compiled kernels. All with the same result: up to 3.19 is fine. 4.0 and later breaks my DVB-T receiver and my memory-card reader. --- Please note: I am not after general knowledge, or information that can be found in five minutes with google. I am after specific information about any known USB (or other possibly related) regressions in 4.0+ kernels and, with luck, a patch or workaround.

I have one dvb-t and one dvb-s card in my system which are in /dev/dvb/adapter0 and /dev/dvb/adapter1 Is there a way to find out which card is currently working? and which one isn't?

I am using a DVB Tuner, USB tuner. I have added driver to the kernel and it is being registered. But when the device is connected, it doesnt invoke the probe function. Is there anything I have to add? Like should the device driver be mapped to the device or something? and please explain how a driver is loaded, based on the type of usb device. The kernel I am using is linux 3.5.

I've tried to get a Techno Trend TT-connect CT2-4650 CI running under a Kali Linux, where I suppose the kernel is about the same as on a current Debian. The compilation ran just fine. The kernel module got loaded with no problems, but when I connect the device to my virtualbox I get the following messages in dmesg: [ 223.081774] usb 1-1: New USB device found, idVendor=0b48, idProduct=3012 [ 223.081780] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 223.081785] usb 1-1: Product: TechnoTrend USB2.0 [ 223.081789] usb 1-1: Manufacturer: CityCom GmbH [ 223.081792] usb 1-1: SerialNumber: 20130422 [ 223.335895] WARNING: You are using an experimental version of the media stack. [ 223.335895] As the driver is backported to an older kernel, it doesn't offer [ 223.335895] enough quality for its usage in production. [ 223.335895] Use it with care. [ 223.335895] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): [ 223.335895] a32f7d1ad3744914273c6907204c2ab3b5d496a0 Merge branch 'v4l_for_linus' into staging/for_v3.9 [ 223.335895] 6b9e50c463efc5c361496ae6a895cc966ff8025b [media] stv090x: On STV0903 do not set registers of the second path [ 223.335895] f67102c49a123b32a4469b28407feb52b37144f5 [media] mb86a20s: remove global BER/PER counters if per-layer counters vanish [ 223.354451] WARNING: You are using an experimental version of the media stack. [ 223.354451] As the driver is backported to an older kernel, it doesn't offer [ 223.354451] enough quality for its usage in production. [ 223.354451] Use it with care. [ 223.354451] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): [ 223.354451] a32f7d1ad3744914273c6907204c2ab3b5d496a0 Merge branch 'v4l_for_linus' into staging/for_v3.9 [ 223.354451] 6b9e50c463efc5c361496ae6a895cc966ff8025b [media] stv090x: On STV0903 do not set registers of the second path [ 223.354451] f67102c49a123b32a4469b28407feb52b37144f5 [media] mb86a20s: remove global BER/PER counters if per-layer counters vanish [ 223.395840] usbcore: registered new interface driver dvb_usb_ttv2 [ 223.396104] usb 1-1: dvb_usb_v2: found a 'TT-connect CT2-4650 CI' in warm state [ 223.396137] usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer [ 223.396158] DVB: registering new adapter (TT-connect CT2-4650 CI) [ 223.428521] tt_usb MAC address=bc:ea:2b:65:02:d4 [ 223.428529] usb 1-1: dvb_usb_v2: MAC address: bc:ea:2b:65:02:d4 [ 223.430036] tt_usb: tt_4650_attach, build on Jan 14 2014 09:46:32() [ 223.653935] usb 1-1: DVB: registering adapter 0 frontend 0 (Sit2 DVB-T2/C)... [ 225.716341] usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110 [ 227.836363] usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110 [ 227.892198] tt_usb: tt_ci_init() [ 229.908294] usb 1-1: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110 [ 229.908318] tt_usb: tt_ci_write_i2c: error, Reg=[0x00], Status=-110 [ 231.908252] usb 1-1: dvb_usb_v2: usb_bulk_msg() failed=-110 [ 231.908260] tt_usb: tt_ci_write_i2c: error, Reg=[0x1f], Status=-110 [ 233.908325] usb 1-1: dvb_usb_v2: usb_bulk_msg() failed=-110 [ 233.908332] tt_usb: tt_ci_write_i2c: error, Reg=[0x18], Status=-110 [ 233.908337] usb 1-1: dvb_usb_v2: 'TT-connect CT2-4650 CI' error while loading driver (-1) [ 233.909530] usb 1-1: dvb_usb_v2: 'TT-connect CT2-4650 CI' successfully deinitialized and disconnected 110 seems to be a Timeout issue, I can't quite see why though. Any ideas are greatly appreciated.

I'm using w_scan to get channel list for my DVB-T stick. But despite channels being found, channels.conf file is empty. I suspect Info: no data from PAT has something to do with this. I know the DVB-T stick is working, because if I enter the frequency into VLC player, I can watch the first channel (SLO1). Terminal output: [rok@rok-laptop ~]$ w_scan -c SI > channels.conf w_scan version 20120605 (compiled for DVB API 5.6) using settings for SLOVENIA 842000: (time: 03:54) 850000: (time: 03:59) 858000: (time: 04:03) tune to: QAM_64 f = 562000 kHz I999B8C23D0T8G4Y0 (time: 04:06) Info: no data from PAT service = SLO1 (RTV SLOVENIJA) service = SLO2 (RTV SLOVENIJA) service = SLO3 (RTV SLOVENIJA) service = POP TV (PROPLUS) service = KANAL A (PROPLUS) service = GOLICA TV (GOLICA TV) service = VAS KANAL (TV NOVO MESTO) service = TV PINK 3 (AGENCIJA MEDIAS) service = TV NAKUPI (DOMATES) dumping lists (0 services) Done.