Tvheadend doesn’t work since update 9.2.2.
Seems there is conflict with TBS crazycat drivers / Hauppauge USB wintv dual-HD and Tvh.
Here’s log : http://ix.io/2hQL
Here’s dmesg : http://ix.io/2hQO
Tvh is starting with CE default drivers. But then, my Hauppauge dual tuners doesn’t work properly.
Let me know if you want some log or testing …
My config : odroid N2, TBS crazycat driver enabled for my USB Hauppage wintv dual HD DVB-T/T2
I just upgraded GT King firmware to latest available (909P0), Coreelec to 9.2.2 (ng) but the DVBT adapter is not found by TVHeadEnd.
I tried to change to other two settings for module drivers but I got same behaviour.
DVBT usb is Hauppauge Win TV-DualHD
Works well
GT King Pro +CoreELEC 9.2.2 + TBS5520SE + Crazycats Driver module
Is it being detected in the usb ports? Can you run lsusb in an ssh session?
CoreELEC:~ # lsusb
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1915:1025 Nordic Semiconductor ASA
Bus 001 Device 005: ID 734c:5521 TBS Technologies China
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and lsmod
CoreELEC:~ # lsmod
Module Size Used by
hci_uart 86016 1
btbcm 16384 1 hci_uart
btqca 16384 1 hci_uart
btintel 20480 1 hci_uart
bluetooth 405504 25 hci_uart,btintel,btqca,btbcm
ir_rc6_decoder 16384 0
ir_nec_decoder 16384 0
dhd 1171456 0
si2157 16384 1
av201x 16384 2
si2183 24576 1
joydev 24576 0
dvb_usb_tbs5520se 20480 18
dvb_usb 40960 1 dvb_usb_tbs5520se
dvb_core 151552 1 dvb_usb
videobuf2_vmalloc 16384 1 dvb_core
mali_kbase 499712 3
ir_lirc_codec 16384 0
lirc_dev 24576 1 ir_lirc_codec
meson_ir 16384 0
rc_core 36864 7 ir_rc6_decoder,ir_nec_decoder,ir_lirc_codec,meson_ir,dvb_usb,lirc_dev
wireguard 143360 0
ip6_udp_tunnel 16384 1 wireguard
udp_tunnel 16384 1 wireguard
wifi_dummy 16384 0
vpu 53248 0
encoder 57344 0
amvdec_vp9 126976 0
amvdec_vc1 65536 0
amvdec_real 45056 0
amvdec_ports 200704 0
v4l2_common 20480 1 amvdec_ports
videobuf2_dma_contig 20480 1 amvdec_ports
videobuf2_memops 16384 2 videobuf2_dma_contig,videobuf2_vmalloc
v4l2_mem2mem 36864 1 amvdec_ports
videobuf2_v4l2 32768 2 amvdec_ports,v4l2_mem2mem
videobuf2_common 69632 4 amvdec_ports,dvb_core,v4l2_mem2mem,videobuf2_v4l2
amvdec_mpeg4 65536 0
amvdec_mpeg12 106496 0
amvdec_mmpeg4 40960 0
amvdec_mmpeg12 45056 0
amvdec_mmjpeg 32768 0
amvdec_mjpeg 40960 0
amvdec_mh264 163840 0
amvdec_h265 155648 0
amvdec_h264mvc 61440 0
amvdec_h264 147456 0
amvdec_avs 69632 0
amvdec_avs2 212992 0
stream_input 192512 13 amvdec_h265,amvdec_mh264,amvdec_h264mvc,amvdec_ports,amvdec_real,amvdec_vp9,amvdec_h264,amvdec_avs2,amvdec_mpeg12,amvdec_avs,amvdec_mmpeg12
decoder_common 184320 18 amvdec_h265,amvdec_mjpeg,amvdec_mh264,amvdec_mmpeg4,amvdec_h264mvc,amvdec_mmjpeg,amvdec_ports,amvdec_real,stream_input,amvdec_vp9,amvdec_h264,encoder,amvdec_avs2,amvdec_mpeg12,amvdec_avs,amvdec_vc1,amvdec_mmpeg12,amvdec_mpeg4
firmware 28672 18 amvdec_h265,amvdec_mjpeg,amvdec_mh264,amvdec_mmpeg4,amvdec_h264mvc,amvdec_mmjpeg,decoder_common,amvdec_real,stream_input,amvdec_vp9,amvdec_h264,encoder,amvdec_avs2,amvdec_mpeg12,amvdec_avs,amvdec_vc1,amvdec_mmpeg12,amvdec_mpeg4
media_clock 45056 13 amvdec_h265,amvdec_mh264,decoder_common,vpu,amvdec_ports,firmware,stream_input,amvdec_vp9,amvdec_h264,encoder,amvdec_avs2,amvdec_mpeg12,amvdec_avs
amlvideodri 24576 1
videobuf_res 16384 1 amlvideodri
videobuf_core 32768 2 amlvideodri,videobuf_res
videodev 307200 7 amlvideodri,v4l2_common,videobuf2_common,amvdec_ports,v4l2_mem2mem,videobuf2_v4l2
mc 53248 7 videobuf2_common,videodev,dvb_core,dvb_usb,v4l2_mem2mem,videobuf2_v4l2,si2157
quota_v2 16384 0
quota_tree 20480 1 quota_v2
fbcon 61440 0
bitblit 16384 1 fbcon
softcursor 16384 1 bitblit
font 20480 1 fbcon
@anon88919003 Yes. It worked from last summer.
Here is lsusb: https://pastebin.com/pihB566d
and dmesg: https://pastebin.com/DiNKcXiS
Also: http://ix.io/2hXC
It seems that tvheadend does not start. I can’t contact it by http://IP:9981/ as usual
Thanks for your support
Have you updated the Android firmware on your device?
@anon88919003 Yes, to 909P0 version. After upgrading Android firmware ethernet is working, but not the usb dvb. In dmesg I read:
[ 2.204418@2] usb 1-2: New USB device found, idVendor=2040, idProduct=8265
[ 2.204420@2] usb 1-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 2.204422@2] usb 1-2: Product: dualHD
[ 2.204423@2] usb 1-2: Manufacturer: HCW
[ 2.204424@2] usb 1-2: SerialNumber: 0014099763
[ 2.204840@2] usb 1-2: Unsupported device
There’s another user in forum who opened a thread with same usb dvb device and same error in dmesg (9.2.2 DVB tbs driver / Hauppauge USB wintv dual HD / Tvheadend conflict).
Furthermore, on 9.2.1 I was using firewall set to “Off” and I was able to get into TVHeadEnd at http://IP:9981/. Now I can not any more, but I just switched firewall settings to “Home” and now I can again. TVHeadEnd can’t see the USB, so it is not working anymore… After a reboot I can’t access TVHeadEnd again…
Can I send you something more?
Thanks
You should still be able to access TVH even without any adaptor being detected.
Nobody reported any issues in the nightly release so this will not get fixed in 9.2.2 now as the release is already done.
We can try to resolve any issues for the next version though but there is no guarantees as the main dvb developer is afk.
@anon88919003 Don’t worry. I can revert to 9.2.1 by coping KERNEL/SYSTEM files. I did it yesterday.
Now I want to make a test: I want to use a new blank SD to install a test system to check if any problems are due to the upgrade path.
Do you want to know any results?
Reverting is exactly how we get into this mess of devices not being supported properly.
@anon88919003 Sorry. I’ll try a fresh install on a new uSD, but yesterday, just after coreelec upgraded to 9.2.2 and Android upgraded to 909P0 I got same behaviour…
I’ll reply in an hour.
Try to enable crazycat and see if it helps, if not then try media_build/dvb-latest.
@crazyturk The problem here is not that TVHeadEnd does not work. The problem here is that the Hauppauge DualTV usb adapter is not detected by TVHeadEnd.
@anon88919003 Resume of tests:
By using default dvb drivers: Hauppauge is not detected and I can access to TVHeadEnd web interface
By using latest and Crazycat dvb drivers: I cannot access to TVHeadEnd web interface. Entering Live TV in Kodi shows the message: “PVR Backend is starting” (I translated from the italian message).
I will have a look at it and see if I can reproduce.
Drivers recognize the usb tuner. There may be another problem. For example, like a power adapter. I’ve had such a problem before. The ampere of the adapter can be insufficient.
CoreELEC:~ # lsusb
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1915:1025 Nordic Semiconductor ASA
Bus 001 Device 003: ID 734c:5521 TBS Technologies China
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
CoreELEC:~ #
About | FAQ | Terms of Service | Privacy Policy | Legal Notice
