Hi All,
I recently went through a bit of an 'episode' after an upgrade to
0.4.0 that I thought I would relay in case it helps anyone else out.
1st: 0.4.0 installed to wrong directory
I run debian unstable/sid with the stock 2.6.12-1-686 kernel as such
ivtv should be installed to /lib/modules/2.6.12-1-686/ivtv however
make install installed ivtv to /lib/modules/2.6.12/ivtv. Figuring out
why my old 0.2.0 version of ivtv kept loading took a while ;-).
Copying the files from /lib/modules/2.6.12/ivtv to
/lib/modules/2.6.12-1-686/ivtv solved the problem. I had a quick look
at the driver/Makefile2.6 and didn't see an obvious reason why it
installed the modules to the wrong directory, but I know next to
nothing about Makefile syntax. uname -r returns the proper
2.6.12-1-686. Thinking back I recall this happening on at least one
other occassion with a 0.2.0 version.
2nd: Nothing but static on 2nd and 3rd encoders
My first encoder (PVR-250) worked fine, however my second and third
(both M179s) produced nothing but static. The output from the IVTV
loading showed the following error where the tuner information would
normally be:
card 1:
ivtv1 warning: i2c client addr: 0x00 not found for command 0x4004760f!
card 2:
ivtv2 warning: i2c client addr: 0x00 not found for command 0x40307603!
This lead me to the thread here:
http://www.mail-archive.com/ivtv-devel@lists.sourceforge.net/msg08472.html
I had already renamed the following stock kernel modules:
msp3400.ko.old
tda9887.ko.old
tuner.ko.old
tveeprom.ko.old
and had rebooted the machine (numerous times :-p) since the renaming
so these modules could not have been loaded but...
Just to humour myself I unloaded i2c_core, i2c_viapro, i2c_algo_bit,
msp3400, tda9887, saa7115, tveeprom, tuner, and ivtv and then reloaded
ivtv. This did the trick and the tuners on all three cards were
correctly loaded and I am now getting proper output from all three
cards.
I haven't had a chance to look into what the heck was going on and why
unloading/reloading the modules would make a difference, but I see I
had i2c-algo-bit, msp3400, saa7115, tuner listed in /etc/modules in
addition to ivtv which may have been the cause. I'll reboot at some
point to confirm whether this was the problem.
- Ben
--
A: Because it destroys the flow of conversation.
Q: Why is top posting dumb?
I recently went through a bit of an 'episode' after an upgrade to
0.4.0 that I thought I would relay in case it helps anyone else out.
1st: 0.4.0 installed to wrong directory
I run debian unstable/sid with the stock 2.6.12-1-686 kernel as such
ivtv should be installed to /lib/modules/2.6.12-1-686/ivtv however
make install installed ivtv to /lib/modules/2.6.12/ivtv. Figuring out
why my old 0.2.0 version of ivtv kept loading took a while ;-).
Copying the files from /lib/modules/2.6.12/ivtv to
/lib/modules/2.6.12-1-686/ivtv solved the problem. I had a quick look
at the driver/Makefile2.6 and didn't see an obvious reason why it
installed the modules to the wrong directory, but I know next to
nothing about Makefile syntax. uname -r returns the proper
2.6.12-1-686. Thinking back I recall this happening on at least one
other occassion with a 0.2.0 version.
2nd: Nothing but static on 2nd and 3rd encoders
My first encoder (PVR-250) worked fine, however my second and third
(both M179s) produced nothing but static. The output from the IVTV
loading showed the following error where the tuner information would
normally be:
card 1:
ivtv1 warning: i2c client addr: 0x00 not found for command 0x4004760f!
card 2:
ivtv2 warning: i2c client addr: 0x00 not found for command 0x40307603!
This lead me to the thread here:
http://www.mail-archive.com/ivtv-devel@lists.sourceforge.net/msg08472.html
I had already renamed the following stock kernel modules:
msp3400.ko.old
tda9887.ko.old
tuner.ko.old
tveeprom.ko.old
and had rebooted the machine (numerous times :-p) since the renaming
so these modules could not have been loaded but...
Just to humour myself I unloaded i2c_core, i2c_viapro, i2c_algo_bit,
msp3400, tda9887, saa7115, tveeprom, tuner, and ivtv and then reloaded
ivtv. This did the trick and the tuners on all three cards were
correctly loaded and I am now getting proper output from all three
cards.
I haven't had a chance to look into what the heck was going on and why
unloading/reloading the modules would make a difference, but I see I
had i2c-algo-bit, msp3400, saa7115, tuner listed in /etc/modules in
addition to ivtv which may have been the cause. I'll reboot at some
point to confirm whether this was the problem.
- Ben
--
A: Because it destroys the flow of conversation.
Q: Why is top posting dumb?