On Sun, 9 Oct 2005, Brian wrote: >I followed, faithfully, the directions given on the ivtvdriver.org HOWTO >page. Despite 7.5 hours of constantly doing/redoing it, I'm still running >0.2.0 (rc3j), according to `modinfo ivtv`. (`ivtvctl -a` returns 'not an >ivtv driver device').
[snip build info] >running /sbin/modprobe ivtv as indicated on the HOWTO page, despite not >being able to (even forcefully!) rmmod ivtv ... produced no errors, >warnings, or output of any kind. It's possible that the newer drivers, now having the necessary lines, have caused depmod to modify modules.pcimap and consequently may try to load ivtv and related modules on bootup. If this is happening, you will need to rmmod or reboot, which you report having done (albeit unsucessfully). >modinfo ivtv >>> version: 0.2.0-68_rc3j.rhfc3.at There is, somewhere on the disk, the older .ko module. Find out where by first rmmod'ing ivtv (however may be required; lsmod must show it absent), then run "modprobe -v ivtv". This will print out the path of ivtv, and all dependant modules, as they load. Cheers, Phil _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
