Proxmox 8 Intermittent TV Card Loss

Adam86

Active Member
Jul 11, 2018
19
1
43
Good Evening,

At a little bit of a loss with this one, so hoping someone can help.

I'm an enthusiast user and have two PowerEdge R720's in two seperate homes. Both run as our main server with a few VM's and Containers for various roles.

Recently upgraded to Proxmox 8 and both servers have been intermittently losing access to the TV card both have installed - both have a PCIe WinTV-quadHD card, which look to be based use a cx23885. I use a LXC container and passthrough /dev/dvb to this for TVHeadend.

I'm feeling like this could possibly be a kernel issue and have currently pinned kernel 5.15.108-1-pve using "pve-efiboot-tool kernel pin 5.15.108-1-pve" command, I only did this today, so might be too early to tell yet. We never had any problems when using Proxmox 7. Rebooting the server usually resolves it, but then the problem may return on next startup.

I've looked at the dmesg & can see there clearly is something being highlighted:

[ 13.421927] tveeprom: Huh, no eeprom present (err=-5)? [ 13.421938] tveeprom: Encountered bad packet header [00]. Corrupt or not a Hauppauge eeprom. [ 13.421942] cx23885: cx23885[0]: warning: unknown hauppauge model #0 [ 13.421945] cx23885: cx23885[0]: hauppauge eeprom: model=0 [ 13.421950] cx23885: cx23885_dvb_register() allocating 1 frontend(s) [ 13.421954] cx23885: cx23885[0]: cx23885 based dvb card [ 13.421963] cx23885: dvb_register(): board=60 port=1 [ 13.435284] si2168 1-0064: probe failed = -5 [ 13.435297] si2168: probe of 1-0064 failed with error -5 [ 13.435321] cx23885: cx23885_dvb_register() dvb_register failed err = -22 [ 13.435376] cx23885: cx23885_dev_setup() Failed to register dvb adapters on VID_B [ 13.435414] cx23885: cx23885_dvb_register() allocating 1 frontend(s) [ 13.435418] cx23885: cx23885[0]: cx23885 based dvb card [ 13.435422] cx23885: dvb_register(): board=60 port=2 [ 13.443831] si2168 1-0066: probe failed = -5 [ 13.443849] si2168: probe of 1-0066 failed with error -5 [ 13.443862] cx23885: cx23885_dvb_register() dvb_register failed err = -22 [ 13.443905] cx23885: cx23885_dev_setup() Failed to register dvb on VID_C [ 13.443940] cx23885: cx23885_dev_checkrevision() Hardware revision = 0xa5 [ 13.443948] cx23885: cx23885[0]/0: found at 0000:43:00.0, rev: 4, irq: 62, latency: 0, mmio: 0xd4000000 [ 13.445657] cx23885: CORE cx23885[1]: subsystem: 0070:6b28, board: Hauppauge WinTV-QuadHD-DVB(885) [card=60,autodetected] [ 13.769922] tveeprom: Huh, no eeprom present (err=-5)? [ 13.769931] tveeprom: Encountered bad packet header [00]. Corrupt or not a Hauppauge eeprom. [ 13.769934] cx23885: cx23885[1]: warning: unknown hauppauge model #0 [ 13.769937] cx23885: cx23885[1]: hauppauge eeprom: model=0 [ 13.769941] cx23885: cx23885_dvb_register() allocating 1 frontend(s) [ 13.769945] cx23885: cx23885[1]: cx23885 based dvb card [ 13.769950] cx23885: dvb_register(): board=60 port=1 [ 13.778410] si2168 4-0064: probe failed = -5 [ 13.778428] si2168: probe of 4-0064 failed with error -5 [ 13.778442] cx23885: cx23885_dvb_register() dvb_register failed err = -22 [ 13.778488] cx23885: cx23885_dev_setup() Failed to register dvb adapters on VID_B [ 13.778525] cx23885: cx23885_dvb_register() allocating 1 frontend(s) [ 13.778529] cx23885: cx23885[1]: cx23885 based dvb card [ 13.778534] cx23885: dvb_register(): board=60 port=2 [ 13.786866] si2168 4-0066: probe failed = -5 [ 13.786884] si2168: probe of 4-0066 failed with error -5 [ 13.786897] cx23885: cx23885_dvb_register() dvb_register failed err = -22 [ 13.786947] cx23885: cx23885_dev_setup() Failed to register dvb on VID_C [ 13.786996] cx23885: cx23885_dev_checkrevision() Hardware revision = 0xa5 [ 13.787002] cx23885: cx23885[1]/0: found at 0000:44:00.0, rev: 4, irq: 63, latency: 0, mmio: 0xd4200000

I've attached the full dmesg for a none working boot & a working boot. FIngers crossed someone can look and advise.

Many Thanks
 

Attachments

  • dmesg-noneworking.txt
    102.1 KB · Views: 1
  • dmesg-working.txt
    108 KB · Views: 1
Hello! Sadly I have no solution to this, but I have a very similar problem with my setup. I have a "WinTV Dual" which was working just fine until some point a few weeks ago. I don't know when it stopped working because I am rarely using the tuner, the only thing I did was some updates with apt. The DVB tuner just does not work, even after several reboots: the /dev/dvb folder simply refuses to exist. I am currently using kernel 6.2.16-12-pve.

Here is the dmesg output:
Code:
[  640.003023] usb 3-1: new high-speed USB device number 7 using xhci_hcd
[  640.151595] usb 3-1: New USB device found, idVendor=2040, idProduct=8265, bcdDevice= 1.00
[  640.151620] usb 3-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[  640.151621] usb 3-1: Product: dualHD
[  640.151623] usb 3-1: Manufacturer: HCW
[  640.151624] usb 3-1: SerialNumber: 0014328858
[  640.152212] em28xx 3-1:1.0: New device HCW dualHD @ 480 Mbps (2040:8265, interface 0, class 0)
[  640.152216] em28xx 3-1:1.0: DVB interface 0 found: bulk
[  640.211105] em28xx 3-1:1.0: chip ID is em28174
[  641.429628] em28xx 3-1:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xd1e8c64c
[  641.429634] em28xx 3-1:1.0: EEPROM info:
[  641.429635] em28xx 3-1:1.0:  microcode start address = 0x0004, boot configuration = 0x01
[  641.436034] em28xx 3-1:1.0:  AC97 audio (5 sample rates)
[  641.436043] em28xx 3-1:1.0:  500mA max power
[  641.436047] em28xx 3-1:1.0:  Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
[  641.494955] em28xx 3-1:1.0: Identified as Hauppauge WinTV-dualHD DVB (card=99)
[  641.497990] tveeprom: Hauppauge model 204209, rev C3I6, serial# 14328858
[  641.497994] tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
[  641.497996] tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[  641.497998] tveeprom: audio processor is None (idx 0)
[  641.497999] tveeprom: has no radio, has IR receiver, has no IR transmitter
[  641.498002] em28xx 3-1:1.0: We currently don't support analog TV or stream capture on dual tuners.
[  641.498027] em28xx 3-1:1.0: dvb set to bulk mode.
[  641.559071] em28xx 3-1:1.0: chip ID is em28174
[  642.773698] em28xx 3-1:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xd1e8c64c
[  642.773712] em28xx 3-1:1.0: EEPROM info:
[  642.773716] em28xx 3-1:1.0:  microcode start address = 0x0004, boot configuration = 0x01
[  642.780084] em28xx 3-1:1.0:  AC97 audio (5 sample rates)
[  642.780093] em28xx 3-1:1.0:  500mA max power
[  642.780097] em28xx 3-1:1.0:  Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
[  642.838951] em28xx 3-1:1.0: Identified as Hauppauge WinTV-dualHD DVB (card=99)
[  642.841993] tveeprom: Hauppauge model 204209, rev C3I6, serial# 14328858
[  642.841996] tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
[  642.841998] tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[  642.842000] tveeprom: audio processor is None (idx 0)
[  642.842001] tveeprom: has no radio, has IR receiver, has no IR transmitter
[  642.842004] em28xx 3-1:1.0: dvb ts2 set to bulk mode.
[  643.040488] em28xx 3-1:1.0: Binding DVB extension
[  643.043739] si2168 3-0064: probe failed = -6
[  643.043936] em28xx 3-1:1.0: Binding DVB extension
[  643.046675] si2168 5-0067: probe failed = -6
[  643.046875] em28xx 3-1:1.0: Registering input extension
[  643.047008] Registered IR keymap rc-hauppauge
[  643.047170] rc rc0: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/rc/rc0
[  643.047221] rc rc0: lirc_dev: driver em28xx registered at minor = 0, scancode receiver, no transmitter
[  643.047283] input: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/rc/rc0/input5
[  643.047329] em28xx 3-1:1.0: Input extension successfully initialized
[  643.047332] em28xx 3-1:1.0: Remote control support is not available for this card.
 
Hello! Sadly I have no solution to this, but I have a very similar problem with my setup. I have a "WinTV Dual" which was working just fine until some point a few weeks ago. I don't know when it stopped working because I am rarely using the tuner, the only thing I did was some updates with apt. The DVB tuner just does not work, even after several reboots: the /dev/dvb folder simply refuses to exist. I am currently using kernel 6.2.16-12-pve.

Here is the dmesg output:
Code:
[  640.003023] usb 3-1: new high-speed USB device number 7 using xhci_hcd
[  640.151595] usb 3-1: New USB device found, idVendor=2040, idProduct=8265, bcdDevice= 1.00
[  640.151620] usb 3-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[  640.151621] usb 3-1: Product: dualHD
[  640.151623] usb 3-1: Manufacturer: HCW
[  640.151624] usb 3-1: SerialNumber: 0014328858
[  640.152212] em28xx 3-1:1.0: New device HCW dualHD @ 480 Mbps (2040:8265, interface 0, class 0)
[  640.152216] em28xx 3-1:1.0: DVB interface 0 found: bulk
[  640.211105] em28xx 3-1:1.0: chip ID is em28174
[  641.429628] em28xx 3-1:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xd1e8c64c
[  641.429634] em28xx 3-1:1.0: EEPROM info:
[  641.429635] em28xx 3-1:1.0:  microcode start address = 0x0004, boot configuration = 0x01
[  641.436034] em28xx 3-1:1.0:  AC97 audio (5 sample rates)
[  641.436043] em28xx 3-1:1.0:  500mA max power
[  641.436047] em28xx 3-1:1.0:  Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
[  641.494955] em28xx 3-1:1.0: Identified as Hauppauge WinTV-dualHD DVB (card=99)
[  641.497990] tveeprom: Hauppauge model 204209, rev C3I6, serial# 14328858
[  641.497994] tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
[  641.497996] tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[  641.497998] tveeprom: audio processor is None (idx 0)
[  641.497999] tveeprom: has no radio, has IR receiver, has no IR transmitter
[  641.498002] em28xx 3-1:1.0: We currently don't support analog TV or stream capture on dual tuners.
[  641.498027] em28xx 3-1:1.0: dvb set to bulk mode.
[  641.559071] em28xx 3-1:1.0: chip ID is em28174
[  642.773698] em28xx 3-1:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xd1e8c64c
[  642.773712] em28xx 3-1:1.0: EEPROM info:
[  642.773716] em28xx 3-1:1.0:  microcode start address = 0x0004, boot configuration = 0x01
[  642.780084] em28xx 3-1:1.0:  AC97 audio (5 sample rates)
[  642.780093] em28xx 3-1:1.0:  500mA max power
[  642.780097] em28xx 3-1:1.0:  Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
[  642.838951] em28xx 3-1:1.0: Identified as Hauppauge WinTV-dualHD DVB (card=99)
[  642.841993] tveeprom: Hauppauge model 204209, rev C3I6, serial# 14328858
[  642.841996] tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
[  642.841998] tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[  642.842000] tveeprom: audio processor is None (idx 0)
[  642.842001] tveeprom: has no radio, has IR receiver, has no IR transmitter
[  642.842004] em28xx 3-1:1.0: dvb ts2 set to bulk mode.
[  643.040488] em28xx 3-1:1.0: Binding DVB extension
[  643.043739] si2168 3-0064: probe failed = -6
[  643.043936] em28xx 3-1:1.0: Binding DVB extension
[  643.046675] si2168 5-0067: probe failed = -6
[  643.046875] em28xx 3-1:1.0: Registering input extension
[  643.047008] Registered IR keymap rc-hauppauge
[  643.047170] rc rc0: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/rc/rc0
[  643.047221] rc rc0: lirc_dev: driver em28xx registered at minor = 0, scancode receiver, no transmitter
[  643.047283] input: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/rc/rc0/input5
[  643.047329] em28xx 3-1:1.0: Input extension successfully initialized
[  643.047332] em28xx 3-1:1.0: Remote control support is not available for this card.
Just checking back with the "solution": It turned out the USB Tuner had a hardware defect. It was still within warranty and I got an RMA replacement. Now everything works as expected.
 
Just checking back with the "solution": It turned out the USB Tuner had a hardware defect. It was still within warranty and I got an RMA replacement. Now everything works as expected.
Pleased to hear that your problem turned out to be a hardware issue.

I can certainly confirm 100% in my case that my issue is kernel related. Unpinned kernel 5.15.108-1-pve last night and the system used 6.2.16-15-pve and after a reboot the problem returned straight away.

I'll attach the latest dmesg contents whilst booted in this newer kernel, but for now I've pinned back to 5.15.108-1-pve.

Really hoping someone can look into this and resolve this.

Cheers
 

Attachments

  • dmesg.txt
    100.8 KB · Views: 2
Just bumping this, in the hope that someone can assist so I can start using the new kernel at some point.

Thanks
 
I will take a look at kernel 6.5.

How would I go about checking for a new firmware blob?
I assumed you needed to download some Windows driver and extract the Hauppauge firmware somehow (or maybe it's downloadable separately,) as they are not shipped with Linux. Those for my WinTV-dualHD USB came from here. Where did you get it? Maybe there's a new version?
 
I assumed you needed to download some Windows driver and extract the Hauppauge firmware somehow (or maybe it's downloadable separately,) as they are not shipped with Linux. Those for my WinTV-dualHD USB came from here. Where did you get it? Maybe there's a new version?
In the whole time I've ran Proxmox with the WinTV-quadHD I've never had to do anything to make them work, they've always just worked "out of the box".

I'll try kernel 6.5 in the meantime though.
 
Good news fingers crossed, kernel 6.5 seems to be stable with my TV Cards & so far haven't had any problems.

This morning have updated all hosts to PVE 8.1 & so now they're all running kernel 6.5, so will continue to monitor.
 
  • Like
Reactions: leesteken

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!