HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Do you want advice about what hardware to buy for use with MythTV? Ask here.

Moderator: Forum Moderators

Post Reply
plainfaceboy
Newcomer
Posts: 8
Joined: Tue May 05, 2015 10:06 am
Great Britain

HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by plainfaceboy » Mon Nov 11, 2019 8:18 pm

Hi - I've been running Ubuntu 16.04 with Mythtv 0.29 for some years all fine. Video card is the quad Hauppauge HVR4000.
DVB-S, DVB-S2 and DVB-T all good.
Never tried the analogue but recently wanted to transfer some old VHS so tried to set it up.
Couldn't get an image in via the s-video (but that might be related to my VHS only outputting composite) other than black and white, and sound was distorted. Resorted to trying to fix using TV Time but same issue, Then *suddenly* TVtime went from seeing inputs of;
TV, Composite and S-Video....to seeing inputs of;
Composite 1, 2, 3 and 4.
Now composite 3 worked fine with the image which was full colour, but there was now no sound.
Now when I went back to Mythtv I thought I'd re-add my cards to clean it up (as I'd previously added an analog V4L card to try and get the VHS), but the DVB-S and DVB-T were not recognised.

I thought I'd take the opportunity to try a fresh install of 18.04 and mythtv 30 but the same thing is happening - no DVB-S or DVB-T recognised in mythtv.
I'm not at computer at moment but generally;
cx88 shows up in lspci (a single line)
and dmesg has the line about no PCI subset ID so card can't be detected.
I add mprobe cx88 card=68. (68 is for Hauppauge HVR4000)
Do I need to do something for DVB-S and T?
I've tried the card in a different PCI slot. I'm confused as had assumed a fresh install of 18.04 would have picked up the card, as every other time it has done.
Is it a kernel issue?
Is it a card issue?
Can anyone help?

blm-ubunet
Senior
Posts: 101
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by blm-ubunet » Tue Nov 12, 2019 1:04 am

FWIU Your card is a hybrid tuner that can only operate as one kind at once (in linux).

What's in kernel boot log?
dmesg | grep cx88

dvb-fe-tool

You've added what to "/etc/modprobe.d/something.conf" ?
options cx88xx card=68
or similar?
(modinfo cx88xx for clues)

plainfaceboy
Newcomer
Posts: 8
Joined: Tue May 05, 2015 10:06 am
Great Britain

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by plainfaceboy » Tue Nov 12, 2019 9:15 pm

Thanks - yes,it is a hybrid, but I'd assumed I could have them all 'installed' but only have one working at any one time.
For example, I had DVB-S and DVB-S2 and DVB-T tuners setup in mythtv but could only use one at a time. I'd assumed I could also set up the analogue, but when using that obviously not use the others?

dmesg | grep cx88

[ 14.823465] cx88xx: Your board has no valid PCI Subsystem ID and thus can't
[ 14.823467] cx88xx: be autodetected. Please pass card=<n> insmod option to
[ 14.823468] cx88xx: workaround that. Redirect complaints to the vendor ofaccepting
[ 14.823469] cx88xx: the TV card
[ 14.823470] cx88xx: Here is a list of valid choices for the card=<n> insmod option:
[ 14.823471] cx88xx: card=0 -> UNKNOWN/GENERIC

.......list of cards in here.....

[ 14.823541] cx88xx: card=89 -> Leadtek TV2000 XP Global (SC4100)
[ 14.823542] cx88xx: card=90 -> Leadtek TV2000 XP Global (XC4100)
[ 14.823544] cx88xx: subsystem: 0000:0000, board: UNKNOWN/GENERIC [card=0,autodetected], frontend(s): 0
[ 14.991527] cx8800: found at 0000:01:07.0, rev: 5, irq: 19, latency: 32, mmio: 0xf9000000
[ 14.991659] cx8800: registered device video0 [v4l2]
[ 14.991686] cx8800: registered device vbi0

dvb-fe-tool
WARNING device dvb0.frontend0 not found

I've got;
options cx88xx card=68
in etc/modules.conf and tried it in etc/modprobe.d/options

Does that give any clues as to what's missing?
2 things confuse me;
Why did it suddenly change (albeit after a bit of messing with settings to try and get the analogue to work),
but if we assume I did something to mess it up....
why wouldn't a clean install pick the card up (like it has many times before)?

Thanks for any help!

blm-ubunet
Senior
Posts: 101
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by blm-ubunet » Tue Nov 12, 2019 9:38 pm

Message like "has no valid PCI Subsystem ID" does not sound good.
Find it hard to believe that is true because that card has had support for a long time.

Did you change PCI slots or MoBo or BIOS version/settings or anything other than *buntu OS?

lspci -nn

This probably reveals the root of it:
dmesg | grep -i ' pci'

But I don't know how to interpret that output/result.

The modprobe options need to be in "/etc/modprobe.d/something.conf" folder/file
And I think* you then have to rebuild initial ram image.
update-initramfs -u

* never found a 'straight up' unambiguious answer in 10+ yrs.

plainfaceboy
Newcomer
Posts: 8
Joined: Tue May 05, 2015 10:06 am
Great Britain

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by plainfaceboy » Wed Nov 13, 2019 9:05 pm

Thanks blm-ubunet
Well one day it was working - I then tried to get the analogue capture working through S-Video (using TVTime to test) - and it simply stopped working.
I tried a different PCI slot - same.
I tried a new version of ubuntu - same.
back to original slot again - same.

I also tried what you suggested to rebuild image - dmesg has changed/improved in that PCI Subsystem message has gone - so the card is registered I think - but card is still not recognised.
Below is;
dmesg | grep -i Hauppauge
2nd line below looks problematic?
Could this be hardware fault (though why after all these years)?

[ 15.060812] cx88xx: subsystem: 0000:0000, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68,insmod option], frontend(s): 2
[ 16.726187] tveeprom: Encountered bad packet header [00]. Corrupt or not a Hauppauge eeprom.
[ 16.726188] cx88xx: warning: unknown hauppauge model #0
[ 16.726188] cx88xx: hauppauge eeprom: model=0
[ 17.120943] Registered IR keymap rc-hauppauge
[ 17.632980] rc rc1: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:08.0/0000:01:06.0/rc/rc1
[ 17.633017] input: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:08.0/0000:01:06.0/rc/rc1/input9
[ 19.505888] Registered IR keymap rc-hauppauge
[ 19.505934] rc rc2: Hauppauge as /devices/pci0000:00/0000:00:08.0/0000:01:06.0/i2c-1/1-0018/rc/rc2
[ 19.505963] input: Hauppauge as /devices/pci0000:00/0000:00:08.0/0000:01:06.0/i2c-1/1-0018/rc/rc2/input18

plainfaceboy
Newcomer
Posts: 8
Joined: Tue May 05, 2015 10:06 am
Great Britain

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by plainfaceboy » Wed Nov 13, 2019 9:08 pm

...and in case it means anything to anyone;

dmesg | grep cx88
[ 15.060812] cx88xx: subsystem: 0000:0000, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68,insmod option], frontend(s): 2
[ 15.191299] cx88xx: i2c init: enabling analog demod on HVR1300/3000/4000 tuner
[ 16.726188] cx88xx: warning: unknown hauppauge model #0
[ 16.726188] cx88xx: hauppauge eeprom: model=0
[ 17.632980] rc rc1: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:08.0/0000:01:06.0/rc/rc1
[ 17.633017] input: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:08.0/0000:01:06.0/rc/rc1/input9
[ 17.633097] rc rc1: lirc_dev: driver cx88xx registered at minor = 1, raw IR receiver, no transmitter
[ 17.633133] cx8800: found at 0000:01:06.0, rev: 5, irq: 16, latency: 32, mmio: 0xf9000000
[ 19.468462] wm8775 1-001b: chip found @ 0x36 (cx88[0])
[ 19.480175] cx8800: registered device video0 [v4l2]
[ 19.480207] cx8800: registered device vbi0

plainfaceboy
Newcomer
Posts: 8
Joined: Tue May 05, 2015 10:06 am
Great Britain

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by plainfaceboy » Wed Nov 13, 2019 9:30 pm

....and also noticed that in TVTime my inputs have gone back (from composites 1-4) to Television, Composite 1 and S-Video
but still not recognised in Mythtv!

blm-ubunet
Senior
Posts: 101
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by blm-ubunet » Thu Nov 14, 2019 2:35 am

Your card is mentioned here but problem was missing firmware & not eeprom issue.
https://github.com/b-rad-NDi/Ubuntu-med ... /issues/71
You could ask their opinion?
Ask them to reprogram the eeprom.

Your problem seems like eeprom (I2C? -UART over PCI) is corrupted & that's why automatic detection fails.
So the card is junk because of a 20c IC.

Actual fairly common for serial eeproms to fail or get corrupted (Pioneer made car stereos is common one).
Some clever person could probably replace/reprogram it with the missing sub-system ID & serial number.

I'll try it in another mobo with *buntu 16.04 or using Haupauge PPA before consigning to the round file.

There are other debugging options for cx88xx driver but who knows how to make use..

plainfaceboy
Newcomer
Posts: 8
Joined: Tue May 05, 2015 10:06 am
Great Britain

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by plainfaceboy » Sat Nov 16, 2019 2:31 pm

The link above seems to help, as the card looks like it is registered, but I'm still getting the eeprom message and it's still not recognised in mythtv.
I tried it in a windows 10 desktop - I have an exclamation mark in device manager as a 'multimedia device', and the driver software says 'no compatible hardware found' and won't install.
Suggests hardware fault?

blm-ubunet
Senior
Posts: 101
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by blm-ubunet » Mon Nov 18, 2019 7:19 pm

If it does not work with windows then it is probably toast.

'setpci' could possibly be used to read/dump the eeprom.
Can also write the eeprom.
Maybe the Hauppauge people could provide the expected contents (part might be the card serial number) & a simple script.

What does this return? :-
# original slot
setpci -s 00:01:07.0 device_id vendor_id
# later slot
setpci -s 00:01:06.0 device_id vendor_id
setpci -s 00:01:06.0 SUBSYSTEM_VENDOR_ID SUBSYSTEM_ID

Then need find another HVR4000 card to dump the eeprom contents.
sudo lspci -s 00:01:06.0 -xxxx

plainfaceboy
Newcomer
Posts: 8
Joined: Tue May 05, 2015 10:06 am
Great Britain

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by plainfaceboy » Sat Nov 23, 2019 5:24 pm

Not that I know what any of this means (!)...but;

setpci -s 00:01:07.0 device_id vendor_id
gives;
setpci: Warning: No devices selected for "device_id".
setpci: Warning: No devices selected for "vendor_id".

setpci -s 00:01:06.0 device_id vendor_id
gives;
8800
14f1

setpci -s 00:01:06.0 SUBSYSTEM_VENDOR_ID SUBSYSTEM_ID
gives;
0000
0000

Not sure I'd be able to get another HVR4000,
I did contact Hauppauge help, and they just said if it's not working with Windows it's hardware fault (ie toast)!

I'm thinking I might just get a couple of second hand cards - eg PVR-150 for VHS capture and as cheap a DVB-S2 as I can find (I don't *need* the DVB-T as well, as was just a nice to have). The current equivalent of the HVR4000 is the HVR5525, which is pretty pricey.

One thing I'd still be interested to know is could I have done this myself by messing about with the analogue in? Just seems too much of a coincidence for it to work for years and then suddenly stop as I was for the first time trying to get the analogue working.
Just be good to know if I need to be careful in future or am I going to toast another card :-D

blm-ubunet
Senior
Posts: 101
Joined: Sun Jun 15, 2014 1:08 am
Cambodia

Re: HVR4000 TVcard - DVB-S and DVB-T suddenly not recognised - only analogue

Post by blm-ubunet » Sun Nov 24, 2019 7:22 pm

AFAIK The PCI eeprom & the card's generic firmware functions make 'plug-n-play' work.

Those sub sysytem ID numbers shouldn't be '0000' FWIU.
Those numbers identify the card & card's subsystems to the BIOS or OS.
The sub-systems are the individual configurable circuit blocks encoder/tuner/demodulator/etc.

I wouldn't waste any money on another HVR4000 or any hybrid tuner card.
Hybrid tuners seem very expensive for the overly constrained h/w & seem problematic to control with linux.
Hauppauge makes a cheap USB analog video capture toy (uses AC3 codec for audio).

Hard to believe that TvTime could corrupt the eeprom.
And can't see how user could corrupt the card without using correctly formatted 'setpci' command options.

I would guess the card f/w :-
- f/w bug that corrupted a read into a write (most eeproms require write enable opcode first).
- f/w rewrites info to eeprom on boot or shutdown ?
- re-wrote same address too many times (possible but not plausible.)
- very bad qty component.
- corrupted a write into a write to incorrect address.
- some other event killed card (ESD, lightning, power glitch, ??)

Post Reply