-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 linux@tele2.be wrote:
Le Saturday 19 January 2008 18:31:55 Jeff Mahoney, vous avez écrit :
I wonder if the module self is guilty : whether with the 2.6.22.5 whether with the 2.6.22.13 kernel, a "modprobe bttv card=62" bash command has the TV running again.
What happens is that if i do it thru Yast, in the 2.6.22.5 kernel, Yast activates the image of the TV, if i do it thru Yast in the 2.6.22.13 kernel nothing happens.
Nevertheless, in both cases, the root/bash command "modprobe bttv card=62" (or simply "modprobe bttv") makes it.
Nevertheless again, after a reboot, the process has to be rerun, and, of course, this is lastening, ...
BRgds to all and Jeff.
Thanks for the feedback. The key here is that you need to specify the card=62 parameter. Can you file a bug against the YaST component for this? They'll probably want a bit more information about your hardware that won't really advance anything on this list. It'd be nice if the driver would autodetect, but that should happen upstream. In the interim, you can make this permanent by creating a file named /etc/modprobe.d/bttv with "options bttv card=62" in it. That will cause modprobe to use that option whenever you load the module. The actual name of the file isn't important, but it does need to be in that directory. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHkvdnLPWxlyuTD7IRAkdfAKCDu+VDn/Hog63tVwqA1cbNDb8asQCeOQry gei81CaKde9boEEl/irSN2I= =+zjC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org