On 9/23/05, Keith C <[EMAIL PROTECTED]> wrote: > >> > >> Do you use any options to any of the modules in modprobe.conf? You > >> shouldn't need to. Make absolutely sure you're not getting any > >> modules from > >> the kernel. Weird problems are often caused by that. > >> > > > > dragonfly ~ # cat /etc/modules.autoload.d/kernel-2.6 > > # /etc/modules.autoload.d/kernel-2.6: kernel modules to load when > > system boots. > > <SNIP> > > sbp2 > > intel_agp > > agpgart > > drm > > i915 > > ivtv > > I meant checking each module from the ivtv driver set with : /sbin/ > modinfo and verifying that it comes back with the ivtv version > instead of the kernel version. For example : > > [EMAIL PROTECTED] ivtv]# /sbin/modinfo msp3400 > filename: /lib/modules/2.6.12-1.1447_FC4/ivtv/msp3400.ko > > Is using the ivtv version of msp3400. While : > > [EMAIL PROTECTED] ivtv]# /sbin/modinfo tveeprom > filename: /lib/modules/2.6.12-1.1447_FC4/kernel/drivers/media/ > video/tveeprom.ko > > Is using the tveeprom module from the kernel (I don't recommend this > - I only have it to make my HD-3000 happy). You should check every > module compiled by ivtv (don't run modinfo from inside a directory > that contains the modules, or it will give you the info on those > instead of what is loaded). > > > I'm using both a 150 and a 250. Is your setup similar? > > > > Not anymore. My 250 overheated and now I just have a PVR500 and > HD-3000. > > Keith C >
Keith, Thanks for clarifying. That's helpful. Right now my modinfo command is not giving me the filename parameter that yours does. I looked for some command line options but I didn't see them. Anyway: dragonfly ~ # /sbin/modinfo msp3400 parmtype: probe:array of short parm: probe:List of adapter,address pairs to scan additionally parmtype: probe_range:array of short parm: probe_range:List of adapter,start-addr,end-addr triples to scan additionally parmtype: ignore:array of short parm: ignore:List of adapter,address pairs not to scan parmtype: ignore_range:array of short parm: ignore_range:List of adapter,start-addr,end-addr triples not to scan parmtype: force:array of short parm: force:List of adapter,address pairs to boldly assume to be present parmtype: once:int parmtype: debug:int parmtype: simple:int parmtype: simpler:int parmtype: stereo_threshold:int parmtype: standard:int parmtype: amsound:int parmtype: dolby:int description: device driver for msp34xx TV sound processor author: Gerd Knorr license: GPL vermagic: 2.6.12-gentoo-r6 preempt PENTIUM4 gcc-3.3 depends: i2c-core dragonfly ~ # As a sort of manual work-around to see if there are others on the system I did this: dragonfly ~ # slocate msp3400 | grep lib | grep 2.6.12| grep ko /lib/modules/2.6.12-gentoo-r6/ivtv/msp3400.ko dragonfly ~ # slocate saa7115 | grep lib | grep 2.6.12| grep ko /lib/modules/2.6.12-gentoo-r6/ivtv/saa7115.ko dragonfly ~ # slocate tda9887 | grep lib | grep 2.6.12| grep ko /lib/modules/2.6.12-gentoo-r6/ivtv/tda9887.ko dragonfly ~ # slocate wm8775 | grep lib | grep 2.6.12| grep ko /lib/modules/2.6.12-gentoo-r6/ivtv/wm8775.ko dragonfly ~ # slocate cx25840 | grep lib | grep 2.6.12| grep ko /lib/modules/2.6.12-gentoo-r6/ivtv/cx25840.ko dragonfly ~ # slocate tuner | grep lib | grep 2.6.12| grep ko /lib/modules/2.6.12-gentoo-r6/ivtv/tuner.ko dragonfly ~ # slocate tveeprom | grep lib | grep 2.6.12| grep ko /lib/modules/2.6.12-gentoo-r6/ivtv/tveeprom.ko dragonfly ~ # slocate ivtv | grep lib | grep 2.6.12| grep ko /lib/modules/2.6.12-gentoo-r6/ivtv/cx25840.ko /lib/modules/2.6.12-gentoo-r6/ivtv/ivtv-fb.ko /lib/modules/2.6.12-gentoo-r6/ivtv/ivtv.ko /lib/modules/2.6.12-gentoo-r6/ivtv/msp3400.ko /lib/modules/2.6.12-gentoo-r6/ivtv/saa7115.ko /lib/modules/2.6.12-gentoo-r6/ivtv/saa7127.ko /lib/modules/2.6.12-gentoo-r6/ivtv/tda9887.ko /lib/modules/2.6.12-gentoo-r6/ivtv/tuner.ko /lib/modules/2.6.12-gentoo-r6/ivtv/tveeprom.ko /lib/modules/2.6.12-gentoo-r6/ivtv/wm8775.ko /lib/modules/2.6.12-gentoo-r6/ivtv/cs53l32a.ko dragonfly ~ # So it looks pretty clean to me assuming the search path is truly under lib/modules/2.6.12. At this point I'm suspicious that the IO bound/ENC problems are possibly caused by the speed at which my networking interface is moving data. I ran hdparm on the Pundit-R's SATA drive and throughput is low compared to my other systems: myth14 ~ # hdparm -tT /dev/hdc /dev/hdc: Timing cached reads: 1508 MB in 2.00 seconds = 752.23 MB/sec Timing buffered disk reads: 46 MB in 3.11 seconds = 14.79 MB/sec myth14 ~ # uname -a Linux myth14 2.6.12-gentoo-r6 #2 Tue Aug 2 16:31:31 PDT 2005 i686 Intel(R) Celeron(R) CPU 2.26GHz GenuineIntel GNU/Linux myth14 ~ # Possibly sub-15MB/S is just not enough for 2 recordings + 1 mythcomflag job? I'm running a test using the local hard drive to see if that works better. If it does then possibly it's not really an ivtv issue at all. (I think!) Thanks very much for your help. I really appreciate it. Cheers, Mark ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
