OK, slowly getting this thing sorted out.... When I try running Kwintv I get this.... /dev/video: no overlay support Warning: kwintv: kv4lsetup had some trouble, trying to continue anyway. Warning: v4l1: VIDIOC_S_PICT in ::v4l1if Warning: v4l1: Video4Linux and DGA disagree about the framebuffer base Warning: v4l1: Video4Linux: 0x0, dga: 0xe2000000! Warning: v4l1: you probably want to insmod the bttv module with "vidmem=0xe20" Warning: v4l1: Video4Linux and DGA disagree about the color depth Warning: v4l1: Video4Linux: 0, DGA: 32. Warning: v4l1: Is kv4lsetup installed correctly? Warning: v4l1: Video4Linux and DGA disagree about the screen size Warning: v4l1: Video4Linux: 0x0x0, DGA: 800x600x0! Warning: v4l1: Is kv4lsetup installed correctly? when I type "lsmod" the BTTV module is not shown, not loaded, when I type "insmod bttv" I get this result... linux:~ # insmod bttv Using /lib/modules/2.2.18/misc/bttv.o /lib/modules/2.2.18/misc/bttv.o: unresolved symbol i2c_master_send /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_unregister_driver /lib/modules/2.2.18/misc/bttv.o: unresolved symbol i2c_bit_del_bus /lib/modules/2.2.18/misc/bttv.o: unresolved symbol i2c_bit_add_bus /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_register_driver /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_get_driver_data /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_enable_device /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_set_driver_data /lib/modules/2.2.18/misc/bttv.o: unresolved symbol i2c_master_recv I'm running Suse 7.1 These modules are supposed to be compiled into the Kernel are they not? Can anyone shed some light on this please....? Terry Menzies Queensland Australia ICQ Number 15981925
Terry Menzies wrote:
OK, slowly getting this thing sorted out....
When I try running Kwintv I get this....
/dev/video: no overlay support Warning: kwintv: kv4lsetup had some trouble, trying to continue anyway.
Warning: v4l1: VIDIOC_S_PICT in ::v4l1if Warning: v4l1: Video4Linux and DGA disagree about the framebuffer base Warning: v4l1: Video4Linux: 0x0, dga: 0xe2000000! Warning: v4l1: you probably want to insmod the bttv module with "vidmem=0xe20"
Warning: v4l1: Video4Linux and DGA disagree about the color depth Warning: v4l1: Video4Linux: 0, DGA: 32. Warning: v4l1: Is kv4lsetup installed correctly? Warning: v4l1: Video4Linux and DGA disagree about the screen size Warning: v4l1: Video4Linux: 0x0x0, DGA: 800x600x0! Warning: v4l1: Is kv4lsetup installed correctly?
when I type "lsmod" the BTTV module is not shown, not loaded, when I type "insmod bttv" I get this result...
linux:~ # insmod bttv Using /lib/modules/2.2.18/misc/bttv.o /lib/modules/2.2.18/misc/bttv.o: unresolved symbol i2c_master_send /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_unregister_driver /lib/modules/2.2.18/misc/bttv.o: unresolved symbol i2c_bit_del_bus /lib/modules/2.2.18/misc/bttv.o: unresolved symbol i2c_bit_add_bus /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_register_driver /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_get_driver_data /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_enable_device /lib/modules/2.2.18/misc/bttv.o: unresolved symbol pci_compat_set_driver_data /lib/modules/2.2.18/misc/bttv.o: unresolved symbol i2c_master_recv
I'm running Suse 7.1
These modules are supposed to be compiled into the Kernel are they not?
Can anyone shed some light on this please....?
Terry Menzies Queensland Australia ICQ Number 15981925
Unfortuantly, due to the nature of TV cards they could not be built directly into the kernel, purely and simply they are so many different cards, and even the same manufacturer may use different tuners even on the same card. So modules only I am afraid. You're using the 2.2 kernel, my memory is fading with that kernel...Let me give you my modules.conf (by the way getting those errors sometimes means you try to load the wright module at the wrong time, before other modules had been loaded). Here it is: options bttv pll=0 radio=1 card=56 options tuner type=17 options msp3400 once=1 simple=1 post-install bttv /sbin/modprobe "-k" tuner; /sbin/modprobe "-k" msp3400 alias char-major-81 bttv You will have to change some of the numbers around, like card=<insert number here> and type=<insert here>. These can be found under the kernel Documentation directory (hopefully). Matt
On Tuesday 31 July 2001 01:00, you wrote:
Unfortuantly, due to the nature of TV cards they could not be built directly into the kernel, purely and simply they are so many different cards, and even the same manufacturer may use different tuners even on the same card. So modules only I am afraid.
Yep, true.
You're using the 2.2 kernel, my memory is fading with that kernel...Let me give you my modules.conf (by the way getting those errors sometimes means you try to load the wright module at the wrong time, before other modules had been loaded).
The following is much the same as my setup... With Suse 7.0. it worked, with Suse 7.1 is doesn't.
options bttv pll=0 radio=1 card=56 options tuner type=17 options msp3400 once=1 simple=1
post-install bttv /sbin/modprobe "-k" tuner; /sbin/modprobe "-k" msp3400
alias char-major-81 bttv
You will have to change some of the numbers around, like card=<insert number here> and type=<insert here>. These can be found under the kernel Documentation directory (hopefully).
Matt
On Tue, Jul 31, 2001 at 09:24:24PM -0700, Terry Menzies wrote:
On Tuesday 31 July 2001 01:00, you wrote:
Unfortuantly, due to the nature of TV cards they could not be built directly into the kernel, purely and simply they are so many different cards, and even the same manufacturer may use different tuners even on the same card. So modules only I am afraid.
Yep, true.
You're using the 2.2 kernel, my memory is fading with that kernel...Let me give you my modules.conf (by the way getting those errors sometimes means you try to load the wright module at the wrong time, before other modules had been loaded).
The following is much the same as my setup... With Suse 7.0. it worked, with Suse 7.1 is doesn't.
I just double-checked my /etc/modules.conf and was surprised to see that I have only alias char-major-81 bttv there. Everything else got commented out as I upgraded from 6.4 to 7.1. I'm running kernel 2.4.2 and there are no problems using kwintv. THe card is avermedia, don't remember the exact model, but I can check that too. When at 6.4, it was quite a puzzle to figure out the correct setting for bttv options. In 7.1 it looks like it finds them automatically. -Kastus
options bttv pll=0 radio=1 card=56 options tuner type=17 options msp3400 once=1 simple=1
post-install bttv /sbin/modprobe "-k" tuner; /sbin/modprobe "-k" msp3400
alias char-major-81 bttv
You will have to change some of the numbers around, like card=<insert number here> and type=<insert here>. These can be found under the kernel Documentation directory (hopefully).
Matt
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
participants (3)
-
Konstantin (Kastus) Shchuka -
StarTux -
Terry Menzies