ivtv after kernel upgrade

[archived]

Is there an ivtv package built for the new kernel 2.6.13-vanilla?  After rebooting my MD, it appears to have grabbed a new kernel, and now ivtv is not loaded.  Any help/suggestions besides building the modules myself?  I tried and tried last night and ran into one thing after another.....sorry do not have error msgs to post.

[archived]

Some paths didn't get changed so the new modules still went to 2.6.10. I.e. don't expect it to work under 2.6.10, if you upgraded, either since it has the 2.6.13 modules in it. I fixed it for the next release.

[archived]

Some paths didn't get changed so the new modules still went to 2.6.10. I.e. don't expect it to work under 2.6.10, if you upgraded, either since it has the 2.6.13 modules in it. I fixed it for the next release.

Hi,

can we in the mean time get some workaround possibility ?    Maybe to download them and where to put them.....


Thanks,

regards,

Rob.

[archived]

Well, if you must...

Code: [Select]

aptitude download <package_name> #pluto-ivtv-video-drivers or pluto-cx88
mkdir extract
cd extract
dpkg -x ../<package_file.deb> . # notice the dot
dpkg -e ../<package_file.deb> # there is no dot here

This will extract the package so you can see it's contents and control files. You'll get a structure similar to what you get when you install plus the directory "DEBIAN" that holds the control files.

In the extracted tree you'll see that the kernel is still called 2.6.10-whatever instead of 2.6.13-whatever (you get the full name from uname -r - 2.6.13.2-vanilla-pluto-1-686). In the DEBIAN directory there's a postinst script that moves the modules from extra/ to where they belong which you'll want to check. I don't remember right now where they go, but I guess it's just a cp or mv and a depmod in there.

Copy the .ko files where they should be and run depmod. That should be it.

[archived]

Well, if you must...

Code: [Select]

aptitude download <package_name> #pluto-ivtv-video-drivers or pluto-cx88
mkdir extract
cd extract
dpkg -x ../<package_file.deb> . # notice the dot
dpkg -e ../<package_file.deb> # there is no dot here

This will extract the package so you can see it's contents and control files. You'll get a structure similar to what you get when you install plus the directory "DEBIAN" that holds the control files.

In the extracted tree you'll see that the kernel is still called 2.6.10-whatever instead of 2.6.13-whatever (you get the full name from uname -r - 2.6.13.2-vanilla-pluto-1-686). In the DEBIAN directory there's a postinst script that moves the modules from extra/ to where they belong which you'll want to check. I don't remember right now where they go, but I guess it's just a cp or mv and a depmod in there.

Copy the .ko files where they should be and run depmod. That should be it.

I have followed the following instruction, but I am still getting the following errors.

modprobe ivtv
FATAL: Error inserting ivtv (/lib/modules/2.6.13.2-vanilla-pluto-1-686/extra/ivtv.ko): Invalid module format

dmesg gives the following:

ivtv: disagrees about version of symbol struct_module

can some build a new package and upload it so that we can get our IVTV cards up and running.

[archived]

Hmm.. I just looked at the modules in that package. The last reply was based on the assumption that the modules built for the old kernel still... Their vermagic is "2.6.10-1-686 preempt 686 gcc-3.3" according to modinfo. I'll have to look into it.

[archived]

I updated the ivtv driver from upstream just now to 0.2.0-rc3k.

While browsing through the download area I also got to a "new tuners" page with this comment on it:

Recently, Hauppauge--and other PC tuner card vendors--began using new tuners
for some of their cards.  The new tuners have different characteristics, and,
therefore, require new definitions to work with the Linux tuner module.
[...]
Many IvyTV users will find it unnecessary to update their tuner modules;
however, some users--especially those purchasing recently manufactured PVR-x50
cards--will find that the tuner on their card is not yet supported by their
tuner module.  See below to determine whether your tuner module supports your
card's tuner.

[archived]

I updated the ivtv driver from upstream just now to 0.2.0-rc3k.

Have they been posted?  I just downloaded fresh from here:  http://plutohome.com/support/index.php?section=packageDownload&pkid=336
but they are the same ones or have the same problem.

Thanks for looking into this for us!!

[archived]

Hi,

I'd just like to inform you on my experiences. I've compiled newest ivtv drivers and my trouble began....

I did this :

Code: [Select]

wget http://dl.ivtvdriver.org/ivtv/ivtv-0.3.8.tar.gz
tar -xzf ivtv-0.3.8.tar.gz
cd ivtv-0.3.8
make
make install
#5. unload any old drivers
modprobe -r ivtv

mv /lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/msp3400.ko /lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/msp3400.ko.HIDE
mv /lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/tda9887.ko /lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/tda9887.ko.HIDE
mv /lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/tuner.ko /lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/tuner.ko.HIDE
mv /lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/tveeprom.ko /lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/tveeprom.ko.HIDE

depmod -a

cd driver
cp  *.ko /lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/

depmod -a

cd ../..

#extracts ivtv-fw-enc.bin
 ./ivtvfwextract.pl pvr48wdm_1.8.22037.exe

modprobe ivtv

now I have all sorts of problems....

bttv module no longer loads

Code: [Select]

FATAL: Error inserting bttv (/lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/media/video/bttv.ko): Unknown symbol in module, or unknown parameter (see dmesg)

bttv: disagrees about version of symbol tveeprom_hauppauge_analog
bttv: Unknown symbol tveeprom_hauppauge_analog



Cause bttv doesn't load, ivtv gets on different /dev/video so doesn't work also and motion also crashes on startup :

Code: [Select]

[0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Unknown config option "always_changes": No such file or directory
[0] Processing config file /etc/motion/thread0.conf
[0] Processing config file /etc/motion/thread1.conf
[0] Processing config file /etc/motion/thread2.conf
[0] Processing config file /etc/motion/thread3.conf
[1] Thread is from /etc/motion/thread0.conf
[2] Thread is from /etc/motion/thread1.conf
[3] Thread is from /etc/motion/thread2.conf
[4] Thread is from /etc/motion/thread3.conf
[1] Thread started
[2] Thread started
[3] Thread started
[4] Thread started
[3] No mmap falling back on read
[3] V4L capturing using read is deprecated!
[3] Motion now only supports mmap.
[3] Motion Exits.


I guess this is because motion wants to deal with ivtv video device (cause bttv isn't on those devices)....

I guess I'll wait for new release to clean this mess.....

HTH,

Regards,

Rob.