[opensuse-kernel] incomplete kernel sources in 10.3
Hello, Trying to set up my Askey/BestBuy BT Easy TV BT878, i manage it working for the current session. After a PC restart, the configuration has to be redone every time. I then installed the sources of the kernel and went thru menuconfig of the kernel. It is to verify that the module BTTV seems not to be implemented : "-----------" is the option on that item. Trying to compile the BTTV module (from bytesex.org), whatever the version i try, i cannot compile (no "./configure", just direct "make" which fails). Attached, the .txt results of the make order on the version bttv-0.9.15 In 10.2 i did'nt have any problem with my TV card. A hint ? BRgds to all.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 linux@tele2.be wrote:
Hello,
Trying to set up my Askey/BestBuy BT Easy TV BT878, i manage it working for the current session.
After a PC restart, the configuration has to be redone every time.
I then installed the sources of the kernel and went thru menuconfig of the kernel.
It is to verify that the module BTTV seems not to be implemented : "-----------" is the option on that item.
Trying to compile the BTTV module (from bytesex.org), whatever the version i try, i cannot compile (no "./configure", just direct "make" which fails).
Attached, the .txt results of the make order on the version bttv-0.9.15 In 10.2 i did'nt have any problem with my TV card.
A hint ?
I don't think the issue is "incomplete sources" since we don't filter anything out. It's the complete source. I expect the problem is that bttv is expecting something that's changed between 2.6.18 and 2.6.22. - -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 iD8DBQFHkjQLLPWxlyuTD7IRAksCAJ9RU44We03esxC1gyETiEcNhO3DiACePfXQ RdC7+lTaEumWZhJ1PUzM6DU= =1+6M -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
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.
linux@tele2.be wrote:
Hello,
Trying to set up my Askey/BestBuy BT Easy TV BT878, i manage it working for the current session.
After a PC restart, the configuration has to be redone every time.
I then installed the sources of the kernel and went thru menuconfig of the kernel.
It is to verify that the module BTTV seems not to be implemented : "-----------" is the option on that item.
Trying to compile the BTTV module (from bytesex.org), whatever the version i try, i cannot compile (no "./configure", just direct "make" which fails).
Attached, the .txt results of the make order on the version bttv-0.9.15 In 10.2 i did'nt have any problem with my TV card.
A hint ?
I don't think the issue is "incomplete sources" since we don't filter anything out. It's the complete source. I expect the problem is that bttv is expecting something that's changed between 2.6.18 and 2.6.22.
-Jeff
-- Jeff Mahoney SUSE Labs
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
-----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
Thanks the tip, Jeff.
I've tried it. Nevertheless, it didn't work.
I point out nevertheless that even if i don't mention card=62 but
just "modprobe bttv", it provisionnally makes the job too. A "modprobe -v
bttv" just that it loads all the bttv relationned modules and, automatically,
the card 62.
as the following line shows :
unit0:~ # modprobe -v bttv
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/media/video/v4l1-compat.ko
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/media/video/v4l2-common.ko
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/media/video/videodev.ko
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/media/video/tveeprom.ko
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/media/video/btcx-risc.ko
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/i2c/algos/i2c-algo-bit.ko
bit_test=1
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/media/video/compat_ioctl32.ko
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/media/common/ir-common.ko
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/base/firmware_class.ko
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/media/video/video-buf.ko
insmod /lib/modules/2.6.22.13-0.3-default/kernel/drivers/media/video/bt8xx/bttv.ko
card=62
/etc/modprobe.d/tv is configured as follows (even before i issue the above
mentionned "modprobe bttv") :
alias char-major-81 videodev
options i2c-algo-bit bit_test=1
options bttv card=62
# YaST configured TV card
# lgGW.bJ31E5obFa9:Askey CPH061/ BESTBUY Easy TV (bt878)
alias char-major-81-0 bttv
alias char-major-81-1 off
alias char-major-81-2 off
alias char-major-81-3 off
I guess thus that the new file /etc/modrobe.d/bttv doesn't add anything to it.
Finally, this is the /etc/modprobe.conf file, before i apply "modprobe bttv".
After i apply it, the file remains unchanged.
#
# Copyright (c) 1996-2002 SuSE Linux AG Nuernberg, Germany.
# All rights reserved.
#
# Author: Hubert Mantel
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
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (2)
-
Jeff Mahoney
-
linux@tele2.be