Hi Hugo, On Thu, 30 Jan 2003, Hugo Ortega H. wrote: > Hi list, > > I have a Matrox Meteor II multichanel framegrabber. My > problem is that I cannot make work it. I downloaded > and installed completes version of V4L2 > (videodevX-20020330.tgz), as well as drivers of the > card > (http://www.emlix.com/en/opensource/meteor2/download.html) > ... I assume you got v1.0? > well, I compiled the V4L2, and load the module: > > [root@movil root]# insmod videodevX > Using > /lib/modules/2.4.19-16mdk/kernel/drivers/media/video/videodevX.o > > well... actually, I'm newbie installing and compiling > new modules for the linux kernel... but, if I use the > lsmod command, I can see the module active: > > [root@movil root]# lsmod > Module Size Used by Not tainted > videodevX 15336 0 <---- is it??.... :-) yes > lp 6720 0 > parport_pc 21672 1 > parport 23936 1 [lp parport_pc] > snd-seq-midi 3680 0 (autoclean) (unused) > snd-emu10k1-synth 4220 0 (autoclean) (unused) > snd-emux-synth 25532 0 (autoclean) > [snd-emu10k1-synth] > > well... after that, I compiled and installed the > matrox meteor II driver, but when I try to probe it, I > receive this message: > > [root@movil root]# modprobe meteor2 > /lib/modules/2.4.19-16mdk/kernel/drivers/media/video/meteor2.o: > init_module: Operation not permitted > Hint: insmod errors can be caused by incorrect module > parameters, including invalid IO or IRQ parameters. > You may find more information in syslog or the > output from dmesg > modprobe: insmod > /lib/modules/2.4.19-16mdk/kernel/drivers/media/video/meteor2.o > failed > modprobe: insmod meteor2 failed > > hmmm... I used the dmesg command, and obtain the next > output (these are only some lines) : > > root@movil root]# dmesg > ... > Video for Linux One (2.2.16). Major device: 81 > Video for Linux Two (V0.20). Major device: 81 > meteor2[via_module_init]: loading driver (dmask: 0x0) > meteor2[via_get_hwinfo]: Unknown JPEG/RAM config ^^^^^^^^^^^^^^^^^^^^^^^ This is the cause of the failure. I haven't seen this before. What card variant do you have _exactly_? Do you have JPEG module installed? Can you provide serial-# from the card stickers? > V4L2: meteor2 (#0) initialize method failed > ... > > as far I know, the framegraber needs an area of > memory, which is reserved in the lilo.conf file. I'm > using the next configuration for that: > > [root@movil root]# cat /etc/lilo.conf > boot=/dev/hda > map=/boot/map > vga=normal > default=linux > keytable=/boot/us-latin1.klt > prompt > nowarn > timeout=100 > message=/boot/message > menu-scheme=wb:bw:wb:bw > image=/boot/vmlinuz > label=linux > root=/dev/hda6 > initrd=/boot/initrd.img > append="mem=500M" <--- I have 512M of RAM That's fine. > vga=normal > read-only > other=/dev/hda1 > label=windows > table=/dev/hda > > and well... I'm not sure if there is a problem with > the IRQ's, but just in case, this is my configuration > of PCI devices: > [..] > (note that the ethernet controler has the same IRQ, > but I don't know if that is a problem for V4L2) no problem, the meteor2 can handle this. > and my problem, how you can see, is that it don't > works!! :( ... I'm using mandrake distribution with > kernel 2.4.19-16mdk. The system is and HP Vectra P4 > 1.7GHz 512Mb RAM (with win98, the meteor2 is OK, so, > it isn't a hardware compatibility problem, I > think...) I need more infos on your card as said above. Does it work with IntelliCam? Cord Seele -- dr. cord seele, emlix gmbh, http://www.emlix.com, mailto:cs@xxxxxxxxx fon +49 551 37000-37, fax -38, friedländer weg 7, 37085 göttingen, germany emlix - your embedded linux partner
