[mythtv-users] HVR-950 and v4l-dvb-kernel issues

[R. G. Newbury]

Adam Propeck wrote:
> Bit-o-background:
> 
> Running Myth (SVN) successfully for quite some time. Have two PVR-150's up
> and running with myth and love it.
> 
> I'd like to add this new HVR-950 that I recently purchased. I've followed
> instructions for installing v4l-dvb-kernel and gotten linux to recognize
> this card. However... I had to "yum remove ivtv*" and "yum remove
> video4linux*" in order to get linux to see the card. Doing that, 
> resulted in
> the PVR-150's failing to tune to new channels at all and they were stuck on
> the same last channel they had been on. (Very frustrating when the Simpsons
> is starting in five minutes and you just realize this is the case...
> 
> I'm running FC5 and 2.6.18 kernel, so I've gone back to the yum ivtv and 
> v4l
> packages and performed a make rminstall on the v4l-dvb-kernel packages.
> 
> Does anyone know a way for me to get this device working without killing my
> pvr-150's tuning capabilities? Thanks in advance!
I asked whether the HVR-950 would work in mythtv, here a week or two ago 
and received no response. Since then I have picked one up and taken a 
look at the v4l-dvb-kernel site.

I have not started to play with this yet, but one thing you might want 
to check are the names of the modules which get loaded by each of these 
conflicting setups.

Long long ago on this list.... (HAH!, October last year!) one of the 
major problem threads involved getting ivtv and cx88-dvb to play 
nice...they both had a module called tveeprom.ko.  For a while the best 
way to get them working was to rename the ivtv version to 
tveeprom_ivtv.ko. After a while it became possible to use the dvb 
version module with ivtv, and the answer was to delete the ivtv version 
if it existed....Now all of that is ancient history...kernel 2.6.15 and 
ivtv 4.0...

I wonder whether the same sort of thing might be going on. All of these 
units have firmware in eeprom and I would not be surprised to learn that 
there is a tveeprom.ko in the v4l-dvb-kernel source tree. The fix *may* 
be as easy as renaming that to tveeprom_v4l.ko...(but I wouldn't bet on 
it!!!)

If you get a chance over the weekend, let us know what happens.
Geoff