No tuner found (even though device supposedly supported in kernel 2.6+)

Added by Patrick Weston about 7 years ago

Hi all,

I had a previous build with the same hardware I have now, but running OpenElec. For reasons I won't get into, I had to start fresh. I decided to go with Ubuntu Server for this install. Everything was going smoothly, but I can't seem to get tvheadend to detect my tuner. In Configuration > DVB Inputs > TV adapters nothing appears.

I'm using this device: https://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTVHD_Volar_(A868R) which is supposedly supported after kernel version 2.6. Obviously being on Ubuntu 17.04, I'm well beyond that.

dmesg returns the following:

[   17.820494] dvb-usb: found a 'AVerMedia AVerTVHD Volar (A868R)' in warm state.
[   19.831158] dvb-usb: bulk message failed: -110 (1/0)
[   19.832813] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[   19.833422] dvbdev: DVB: registering new adapter (AVerMedia AVerTVHD Volar (A868R))
[   22.327316] dvb-usb: bulk message failed: -110 (5/0)
[   22.328740] dvb-usb: no frontend was attached by 'AVerMedia AVerTVHD Volar (A868R)'
[   24.343204] dvb-usb: bulk message failed: -110 (1/0)
[   24.344602] dvb-usb: AVerMedia AVerTVHD Volar (A868R) successfully initialized and connected.
[   24.344683] usbcore: registered new interface driver dvb_usb_cxusb

The device also shows up with lsusb:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 07ca:a868 AVerMedia Technologies, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Also, I have the following structure at /dev/dvb/adapter0:

crw-rw---- 1 root video 212, 0 Aug 24 21:26 demux0
crw-rw---- 1 root video 212, 1 Aug 24 21:26 dvr0
crw-rw---- 1 root video 212, 2 Aug 24 21:26 net0

I've also tried starting and stopping tvheadend in case the device was loading after tvheadend initialized. Additionally, I've modified permissions to /dev/dvb/adapter0.

Any help would be greatly appreciated. Thanks!

Replies (2)

RE: No tuner found (even though device supposedly supported in kernel 2.6+) - Added by saen acro about 7 years ago

[   22.328740] dvb-usb: no frontend was attached by 'AVerMedia AVerTVHD Volar (A868R)'

this is a clear message that there is a problem

normal situation is something as this:

tree /dev/dvb
/dev/dvb
└── adapter0
    ├── demux0
    ├── dvr0
    ├── frontend0
    └── net0

1 directory, 4 files

Something is broken in kernel 4.9 - 4.10
https://bugzilla.kernel.org/show_bug.cgi?id=194861

RE: No tuner found (even though device supposedly supported in kernel 2.6+) - Added by Patrick Weston about 7 years ago

Thank you! I thought that wasn't a good sign.

Also, thank you for the link. I tried to upgrade my kernel to 4.12 but it still wasn't working there. I had to downgrade to 4.8.17 to get it to work. Everything is running smoothly now.

Here are the steps to downgrade if anyone is curious:

cd /tmp/
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.17/linux-headers-4.8.17-040817_4.8.17-040817.201701090438_all.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.17/linux-headers-4.8.17-040817-generic_4.8.17-040817.201701090438_amd64.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.17/linux-image-4.8.17-040817-generic_4.8.17-040817.201701090438_amd64.deb
sudo dpkg -i *.deb
sudo update-grub
sudo cp /etc/default/grub /etc/default/grub.bak
sudo vi /etc/default/grub

Change the GRUB_DEFAULT line to:

GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 4.8.17-040817-generic"

sudo update-grub
sudo reboot now

Obviously version and platform (amd64 vs i386) might need changed depending on one's specific use case.

Thanks again!

(1-2/2)

Project

General

Profile

Tvheadend