On Mon, 2009-02-02 at 20:11 -0500, John Bickel wrote: > I've had some success getting the HVR-1600 to work on the 8.10 version of > Mythbuntu. Currently, my issue is that I can't change it off of analog > channel 4 coming from the Time/Warner [Ohio] cable - no box. I have good > video quality and good audio, but only one channel, even though MythTV > says it can find all the other channels. > > I've attached the output from a dmesg. > > I downloaded and tried 'make'ing the "cx18: Remove an unused spinlock" > from http://linuxtv.org/hg/~awalls/cx18/summary, but got an error: > CC [M] /home/mymythtv/v4l-dvb/v4l/tvmixer.o > /home/mymythtv/v4l-dvb/v4l/tvmixer.c:226: error: 'I2C_DRIVERID_TVMIXER' > undeclared here (not in a function) > make[3]: *** [/home/mymythtv/v4l-dvb/v4l/tvmixer.o] Error 1 > make[2]: *** [_module_/home/mymythtv/v4l-dvb/v4l] Error 2 > make[2]: Leaving directory `/usr/src/linux-headers-2.6.27-11-generic' > make[1]: *** [default] Error 2 > make[1]: Leaving directory `/home/mymythtv/v4l-dvb/v4l' > make: *** [all] Error 2
Argh. Ubuntu can be problematic with the way they package the kernel development stuff. Or I've based that repo on a snapshot that has a breakage in it for older kernels. Every cx18 change in that repo should be non-critical. You should pull from the main v4l-dvb repo and try to use that. > Any help or guidance would be appreciated. Thanks. Well, everything looked fine in dmesg until 5 seconds after the cx18 module had loaded all it's firmware on to devices (meaning it was done), this happened: [ 52.601011] tuner-simple 1-0061: destroying instance [ 52.654019] tuner 1-0061: chip found @ 0xc2 (cx18 i2c driver #0-1) [ 61.143690] tuner 1-0061: tuner type not set [ 61.173427] tuner 1-0061: tuner type not set I'm not sure what's going on, but the cx18 module wouldn't try to unload the tuner module out from under itself. Something on your system is prompting this or recent changes to tuner and tuner-simple are doing this. You should add options tuner-simple debug=7 options tuner debug=7 to your /etc/modprobe.conf to see if you get more messages emitted into /var/log/messages as to what's going on. (I'm just guessing at the number 7 and the exact modprobe.conf syntax - feel free to check the ource for the actual debug level supported and the manpage for modprobe.conf) Regards, Andy _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
