Menu
▾
▴
m560x-driver-support — For user support
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(2) |
Aug
(5) |
Sep
(6) |
Oct
(10) |
Nov
(11) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(3) |
Feb
(4) |
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
(23) |
Aug
(23) |
Sep
(17) |
Oct
|
Nov
(20) |
Dec
(27) |
| 2009 |
Jan
(11) |
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
(4) |
Aug
(3) |
Sep
|
Oct
(3) |
Nov
(4) |
Dec
(1) |
| 2010 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2018 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ivan V. <iv...@gm...> - 2007-11-03 11:49:04
|
I think that much is sufficient, however if you hope to use the camera in any application other than livecam or xawtv, I can tell you to drop your hopes -- driver is heavy in development. However, for testing, use an m5602 branch - m5602-ov9650 or m5602-ov9650-2. I have an 5603, and I haven't had too much luck getting it to work (I had some but not much) so I'm just giving you hints. If someone more competent is watching this list ... :) ------------ Ivan Vucica On Sat, 3 Nov 2007, mr.care wrote: > hello, > > i have a Lenovo 3000 v200 laptop with integrated video camera and i am > using ubuntu 7.10. > > lsusb shows: > Bus 007 Device 003: ID 0402:5602 ALi Corp. > > what other things do i need to know about my system to try to compile > the driver and which branch should i use? > > thank you for the support. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > M560x-driver-support mailing list > M56...@li... > https://lists.sourceforge.net/lists/listinfo/m560x-driver-support > |
|
From: Andrea M. <and...@fa...> - 2007-11-03 10:50:02
|
Hi, what is the status regarding the Ali 5602 WebCam with the mt9v111 sensor ? (my configuration) The new version of the driver on Sourceforge is unable to detect my sensor: this is the kernel log when I ssue the insmod km506x.ko /home/andrea/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: No supported sensor detected m560x: probe of 5-7:1.0 failed with error -524 and the capture program is not working, whereas with the old version of the drriver (the last one before moving to sourceforge) I have the following log /home/downloads/m560x/trunk/km_m560x/m560x_core.c: usb_m560x_init - M560x-based WebCam driver startup /home/downloads/m560x/trunk/km_m560x/m560x_core.c: m560x_probe - M560x-based Web Cam connected /home/downloads/m560x/trunk/km_m560x/m560x_core.c: Ali M5602-based WebCam found. /home/downloads/m560x/trunk/km_m560x/m5602_mt9v111.c: [m5602_probe_mt9v111:189] probe mt9v111 sensor id 14 59 /home/downloads/m560x/trunk/km_m560x/m5602_mt9v111.c: [m5602_probe_mt9v111:192] detected mt9v111 sensor /home/downloads/m560x/trunk/km_m560x/m560x_core.c: m560x_probe - Ali_M560x WebCa m driver is now controlling video device 0 usbcore: registered new interface driver m560x /home/downloads/m560x/trunk/km_m560x/m560x_core.c: 0.4.0:Ali M560x Webcam Driver /home/downloads/m560x/trunk/km_m560x/m560x_core.c: m560x open and the capture program gives me pictures (albeit very dark...). If some support is required, I will be glad to contribute again (Wilelm should remember well me...). Artu72 |
|
From: mr.care <ca...@fr...> - 2007-11-02 22:09:57
|
hello, i have a Lenovo 3000 v200 laptop with integrated video camera and i am using ubuntu 7.10. lsusb shows: Bus 007 Device 003: ID 0402:5602 ALi Corp. what other things do i need to know about my system to try to compile the driver and which branch should i use? thank you for the support. |
|
From: <da...@sm...> - 2007-10-22 06:07:04
|
Hi, I have from lsusb Bus 002 Device 003: ID 0402:5602 ALi Corp. I want to test the driver coded in m560x/branches/m5602-ov9650-2/ How do I could change Makefile/code in m560x/trunk/km_m560x for include the code in that branch ? Thanks, Daniele. |
|
From: Robert W. <rob...@ap...> - 2007-10-21 22:24:51
|
Not sure whether anyone's out there, but just in case, here's so more info... Now managed to compile the latest svn snapshot. There's a power button for the device on my laptop and when you activate it, the camera appears in /dev as /dev/video0 which is a link to /dev/v4l/video0 I was quite excited by this, ;-), but it's not quite right. I installed xawtv as somewhere I read this works with the cam. When you hit the power button an xawtv icon appears on the desktop, just like it did with my Logitech device and a different program when I got the Berlios driver going. However, the hard drive chugs away and nothing happens. aMSN doesn't recognise it at all and the testprogram for m5602 now works, but the bitmap it produces is just all black. Definite progress here though, so to whoever is doing the code, it looks like it's going in the right direction. :~) |
|
From: Robert W. <rob...@ap...> - 2007-10-14 10:06:48
|
Sorry for the delay on this. The testprogram in m5602 subdirectory runs, but will not produce a picture. It spits out all that text I included in my last post. The programs will not run at all. The program is obviously talking to the cam, because if I try running it without the cam powered up (there's a button on the laptop to switch it on and off) then it says hardware not detected. Once it's powered up it runs, but show produces no image. How often should I download code and retry it? Is here a notification system for updated code? Many thanks. |
|
From: <da...@sm...> - 2007-10-11 10:45:23
|
I compiled what in trunk
make
make install
i got dmesg:
[ 4117.656980] /home/daniele/m560x-driver/m560x-driver/m560x/branches/m5602-ov9650-2/m5602.c: m5602 release resources video device 0
[ 4117.657690] /home/daniele/m560x-driver/m560x-driver/m560x/branches/m5602-ov9650-2/m5602.c: m5602_disconnect- M560x-based WebCam disconnected
[ 4118.828345] /home/daniele/m560x-driver/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: usb_m560x_exit - M560x-based WebCam driver shutdown
[ 4118.828353] usbcore: deregistering interface driver m560x
[ 4136.879310] /home/daniele/m560x-driver/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: usb_m560x_init - M560x-based WebCam driver startup
[ 4136.879958] /home/daniele/m560x-driver/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: m560x_probe - M560x-based WebCam connected
[ 4136.996416] /home/daniele/m560x-driver/m560x-driver/m560x/trunk/km_m560x/m5602_mt9v111.c: [m5602_probe_mt9v111:189] probe mt9v111 sensor id ff ff
[ 4136.998414] /home/daniele/m560x-driver/m560x-driver/m560x/trunk/km_m560x/m5602_ov9650.c: [m5602_probe_ov9650:190] probe ov9650 sensor id ff ff
[ 4137.000413] /home/daniele/m560x-driver/m560x-driver/m560x/trunk/km_m560x/m5602_ov7640.c: [m5602_probe_ov7640:190] probe ov7640 sensor id ff ff
[ 4137.000418] /home/daniele/m560x-driver/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: No supported sensor detected
[ 4137.000675] m560x: probe of 2-6:1.0 failed with error -524
[ 4137.000751] usbcore: registered new interface driver m560x
[ 4137.000814] /home/daniele/m560x-driver/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: 0.4.0:Ali M560x Webcam Driver
lsusb -v
Bus 002 Device 003: ID 0402:5602 ALi Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0402 ALi Corp.
idProduct 0x5602
bcdDevice 1.00
iManufacturer 0
iProduct 1 USB2.0 Camera
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 101
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1400 3x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1380 3x 896 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1300 3x 768 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
|
|
From: <da...@sm...> - 2007-10-11 10:37:05
|
|
From: Robert W. <rob...@ap...> - 2007-10-07 20:44:40
|
OK, that compiles and produces an executable. I have run this and piped it to a text file which I've attached. (I assume that's the purpose of the program.) I should add that the program doesn't terminate itself, I have to do that with CTL-C. Cheers! Jérémy Lal wrote: > Robert Wood a écrit : >> Merci pour la répsonse rapide! >> >> I am pretty sure I have compiled against the correct headers, it >> installs the module in the same source headers as the kernel I am >> running. Also it seems to put the driver in the relevant /lib/source >> subdirectory. >> >> I am afraid to say I totally missed that INSTALL text file! It >> doesn't help too much though. >> >> I've tried: >> >> modprobe firmware_class >> modprobe videodev >> modprobe v4l1-compat >> >> it seems to happily install videodev and v4l1-compat, but I don't >> have firmware_class; I'll do a bit of digging to find how to get that >> on my system. >> >> The testprograms won't install at all. I get: >> >> gcc -g -Wall -c m560x_test.c >> In file included from m560x_test.c:30: >> pusb-linux.h:5:23: error: linux/usb.h: No such file or directory >> m560x_test.c: In function ‘main’: >> m560x_test.c:142: warning: implicit declaration of function ‘get_frame’ >> make: *** [m560x_test.o] Error 1 >> >> It's the same for any of those testprograms. > add > -I/path/to/your/kernel/headers/include/ > to the first line of the Makefile, like this : > CCOPTS= -g -Wall -I/usr/src/linux-headers-2.6.22-2/include/ > > next, if you still have errors, replace pusb-linux.h with that one : > > #define __KERNEL__ > #include <linux/types.h> > #include <linux/mod_devicetable.h> > #undef __KERNEL__ > #include <linux/usb.h> > #include <linux/usbdevice_fs.h> > > #define USBDEVFS_URB_QUEUE_BULK 0x10 > > > > recompile again... > it should work, but i guess some experimented programmer should > correct me. > > > >> >> Cheers, >> >> Rob >> >> Jérémy Lal wrote: >>> Robert Wood a écrit : >>>> I have a Zepto Znote 6625WD with a built in web cam. I'm running >>>> Mandriva 2008 RC2. I've downloaded the source via SVN. I went to the >>>> >>>> installpath/m560x-driver/m560x/trunk/km_m560x >>>> >>>> and did: >>>> >>>> make >>>> >>>> make install >>>> >>>> modprobe m560x >>>> >>>> However, I get the error: >>>> >>>> Error inserting m560x >>>> (/lib/modules/2.6.22.6-server-3mdv/kernel/drivers/usb/media/m560x.ko): >>>> Invalid module format >>>> >>>> Anyone know: >>>> >>>> a. Have I compiled the correct part of the download? >>>> >>> yes, but not guaranteed to work ! >>> try to compile testprograms if it doesn't. >>>> b. What would cause the above error? (I appreciate that might be >>>> impossible to answer.) >>>> >>> you compiled against the wrong kernel headers, or you didn't >>> modprobe other modules before (see INSTALL) >>>> my lsusb gives: >>>> >>>> Bus 007 Device 003: ID 0402:5602 ALi Corp. >>>> >>>> >>>> Which pointed me towards this site after some searching on Google. >>>> >>>> Many thanks, >>>> >>>> Rob >>>> >>>> ------------------------------------------------------------------------- >>>> >>>> This SF.net email is sponsored by: Splunk Inc. >>>> Still grepping through log files to find problems? Stop. >>>> Now Search log events and configuration files using AJAX and a >>>> browser. >>>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>>> _______________________________________________ >>>> M560x-driver-support mailing list >>>> M56...@li... >>>> https://lists.sourceforge.net/lists/listinfo/m560x-driver-support >>>> >>>> >>> >>> >>> >> >> > > > |
|
From: <jer...@m4...> - 2007-10-07 18:42:07
|
Robert Wood a écrit : > Merci pour la répsonse rapide! > > I am pretty sure I have compiled against the correct headers, it > installs the module in the same source headers as the kernel I am > running. Also it seems to put the driver in the relevant /lib/source > subdirectory. > > I am afraid to say I totally missed that INSTALL text file! It doesn't > help too much though. > > I've tried: > > modprobe firmware_class > modprobe videodev > modprobe v4l1-compat > > it seems to happily install videodev and v4l1-compat, but I don't have > firmware_class; I'll do a bit of digging to find how to get that on my > system. > > The testprograms won't install at all. I get: > > gcc -g -Wall -c m560x_test.c > In file included from m560x_test.c:30: > pusb-linux.h:5:23: error: linux/usb.h: No such file or directory > m560x_test.c: In function ‘main’: > m560x_test.c:142: warning: implicit declaration of function ‘get_frame’ > make: *** [m560x_test.o] Error 1 > > It's the same for any of those testprograms. add -I/path/to/your/kernel/headers/include/ to the first line of the Makefile, like this : CCOPTS= -g -Wall -I/usr/src/linux-headers-2.6.22-2/include/ next, if you still have errors, replace pusb-linux.h with that one : #define __KERNEL__ #include <linux/types.h> #include <linux/mod_devicetable.h> #undef __KERNEL__ #include <linux/usb.h> #include <linux/usbdevice_fs.h> #define USBDEVFS_URB_QUEUE_BULK 0x10 recompile again... it should work, but i guess some experimented programmer should correct me. > > Cheers, > > Rob > > Jérémy Lal wrote: >> Robert Wood a écrit : >>> I have a Zepto Znote 6625WD with a built in web cam. I'm running >>> Mandriva 2008 RC2. I've downloaded the source via SVN. I went to the >>> >>> installpath/m560x-driver/m560x/trunk/km_m560x >>> >>> and did: >>> >>> make >>> >>> make install >>> >>> modprobe m560x >>> >>> However, I get the error: >>> >>> Error inserting m560x >>> (/lib/modules/2.6.22.6-server-3mdv/kernel/drivers/usb/media/m560x.ko): >>> Invalid module format >>> >>> Anyone know: >>> >>> a. Have I compiled the correct part of the download? >>> >> yes, but not guaranteed to work ! >> try to compile testprograms if it doesn't. >>> b. What would cause the above error? (I appreciate that might be >>> impossible to answer.) >>> >> you compiled against the wrong kernel headers, or you didn't modprobe >> other modules before (see INSTALL) >>> my lsusb gives: >>> >>> Bus 007 Device 003: ID 0402:5602 ALi Corp. >>> >>> >>> Which pointed me towards this site after some searching on Google. >>> >>> Many thanks, >>> >>> Rob >>> >>> ------------------------------------------------------------------------- >>> >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> M560x-driver-support mailing list >>> M56...@li... >>> https://lists.sourceforge.net/lists/listinfo/m560x-driver-support >>> >>> >> >> >> > > |
|
From: Robert W. <rob...@ap...> - 2007-10-07 17:10:31
|
Merci pour la répsonse rapide! I am pretty sure I have compiled against the correct headers, it installs the module in the same source headers as the kernel I am running. Also it seems to put the driver in the relevant /lib/source subdirectory. I am afraid to say I totally missed that INSTALL text file! It doesn't help too much though. I've tried: modprobe firmware_class modprobe videodev modprobe v4l1-compat it seems to happily install videodev and v4l1-compat, but I don't have firmware_class; I'll do a bit of digging to find how to get that on my system. The testprograms won't install at all. I get: gcc -g -Wall -c m560x_test.c In file included from m560x_test.c:30: pusb-linux.h:5:23: error: linux/usb.h: No such file or directory m560x_test.c: In function ‘main’: m560x_test.c:142: warning: implicit declaration of function ‘get_frame’ make: *** [m560x_test.o] Error 1 It's the same for any of those testprograms. Cheers, Rob Jérémy Lal wrote: > Robert Wood a écrit : >> I have a Zepto Znote 6625WD with a built in web cam. I'm running >> Mandriva 2008 RC2. I've downloaded the source via SVN. I went to the >> >> installpath/m560x-driver/m560x/trunk/km_m560x >> >> and did: >> >> make >> >> make install >> >> modprobe m560x >> >> However, I get the error: >> >> Error inserting m560x >> (/lib/modules/2.6.22.6-server-3mdv/kernel/drivers/usb/media/m560x.ko): >> Invalid module format >> >> Anyone know: >> >> a. Have I compiled the correct part of the download? >> > yes, but not guaranteed to work ! > try to compile testprograms if it doesn't. >> b. What would cause the above error? (I appreciate that might be >> impossible to answer.) >> > you compiled against the wrong kernel headers, or you didn't modprobe > other modules before (see INSTALL) >> my lsusb gives: >> >> Bus 007 Device 003: ID 0402:5602 ALi Corp. >> >> >> Which pointed me towards this site after some searching on Google. >> >> Many thanks, >> >> Rob >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> M560x-driver-support mailing list >> M56...@li... >> https://lists.sourceforge.net/lists/listinfo/m560x-driver-support >> >> > > > |
|
From: <jer...@m4...> - 2007-10-07 16:56:28
|
Robert Wood a écrit : > I have a Zepto Znote 6625WD with a built in web cam. I'm running > Mandriva 2008 RC2. I've downloaded the source via SVN. I went to the > > installpath/m560x-driver/m560x/trunk/km_m560x > > and did: > > make > > make install > > modprobe m560x > > However, I get the error: > > Error inserting m560x > (/lib/modules/2.6.22.6-server-3mdv/kernel/drivers/usb/media/m560x.ko): > Invalid module format > > Anyone know: > > a. Have I compiled the correct part of the download? > yes, but not guaranteed to work ! try to compile testprograms if it doesn't. > b. What would cause the above error? (I appreciate that might be > impossible to answer.) > you compiled against the wrong kernel headers, or you didn't modprobe other modules before (see INSTALL) > my lsusb gives: > > Bus 007 Device 003: ID 0402:5602 ALi Corp. > > > Which pointed me towards this site after some searching on Google. > > Many thanks, > > Rob > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > M560x-driver-support mailing list > M56...@li... > https://lists.sourceforge.net/lists/listinfo/m560x-driver-support > > |
|
From: Robert W. <rob...@ap...> - 2007-10-07 16:51:43
|
I have a Zepto Znote 6625WD with a built in web cam. I'm running Mandriva 2008 RC2. I've downloaded the source via SVN. I went to the installpath/m560x-driver/m560x/trunk/km_m560x and did: make make install modprobe m560x However, I get the error: Error inserting m560x (/lib/modules/2.6.22.6-server-3mdv/kernel/drivers/usb/media/m560x.ko): Invalid module format Anyone know: a. Have I compiled the correct part of the download? b. What would cause the above error? (I appreciate that might be impossible to answer.) my lsusb gives: Bus 007 Device 003: ID 0402:5602 ALi Corp. Which pointed me towards this site after some searching on Google. Many thanks, Rob |
|
From: Guido S. <san...@gm...> - 2007-09-28 02:40:37
|
Hi. I have updated to the current release of the driver. I compiled the new version, then I did modprobe firmware_class modprobe videodev modprobe v4l1-compat insmod ./m560x.ko debug=16 lsusb output: Bus 003 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0402:5602 ALi Corp. Video Camera Controller Bus 002 Device 001: ID 0000:0000 Bus 001 Device 003: ID 0458:002e KYE Systems Corp. (Mouse Systems) Bus 001 Device 001: ID 0000:0000 dmesg output: # start of dmesg output Linux video capture interface: v2.00 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: usb_m560x_init - M560x-based WebCam driver startup /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: m560x_probe - M560x-based WebCam connected /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [usb_m560x_probe:2738] cam ffff81001aafa000 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:971] initialize_m5602_camera /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1024] 0x0ff9 13 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_camera:1126] Correctly initialized_m560x_camera /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m5602_mt9v111.c: [m5602_probe_mt9v111:189] probe mt9v111 sensor id ff ff /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m5602_ov9650.c: [m5602_probe_ov9650:190] probe ov9650 sensor id ff ff /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m5602_ov7640.c: [m5602_probe_ov7640:190] probe ov7640 sensor id ff ff /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: No supported sensor detected m560x: probe of 3-4:1.0 failed with error -524 usbcore: registered new interface driver m560x /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: 0.4.0:Ali M560x Webcam Driver # end of dmesg output Hope it helps someone. Greetings Guido -- Never make any mistaeks. |
|
From: <m56...@ro...> - 2007-09-26 17:36:11
|
lo Guys,
Finally, I am able to modprobe the driver without it segfaulting on me
after the last svn update. (revision 99 I am told). However, still
don't have a working webcam :P
I now get this:
-- CUT --
Linux video capture interface: v2.00
/usr/src/svn/m560x-driver/m560x/trunk/km_m560x/m560x_core.c:
usb_m560x_init - M560x-based WebCam driver startup
/usr/src/svn/m560x-driver/m560x/trunk/km_m560x/m560x_core.c:
m560x_probe - M560x-based WebCam connected
/usr/src/svn/m560x-driver/m560x/trunk/km_m560x/m5602_mt9v111.c:
[m5602_probe_mt9v111:189] probe mt9v111 sensor id ff ff
/usr/src/svn/m560x-driver/m560x/trunk/km_m560x/m5602_ov9650.c:
[m5602_probe_ov9650:190] probe ov9650 sensor id ff ff
/usr/src/svn/m560x-driver/m560x/trunk/km_m560x/m5602_ov7640.c:
[m5602_probe_ov7640:190] probe ov7640 sensor id ff ff
/usr/src/svn/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: No
supported sensor detected
m560x: probe of 1-6:1.0 failed with error -524
usbcore: registered new interface driver m560x
/usr/src/svn/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: 0.4.0:Ali
M560x Webcam Driver
--CUT --
and no /dev/videoX devices are created.
So this is the integrated webcam on a Acer 9301WMSi which declare
itself as:
-- CUT --
Bus 001 Device 002: ID 0402:5602 ALi Corp. Video Camera Controller
-- CUT --
or
-- CUT --
Bus 001 Device 002: ID 0402:5602 ALi Corp. Video Camera Controller
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0402 ALi Corp.
idProduct 0x5602 Video Camera Controller
bcdDevice 1.00
iManufacturer 0
iProduct 1 USB2.0 Camera
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 101
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1400 3x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1380 3x 896 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1300 3x 768 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 4
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
-- CUT--
So, is there anything I can help with to narrow down the type of
sensor it is looking for or are we still resorting to usbsnoop to find
these things out? ;)
Let me know so I can contribute.
Cheers,
Don.
--
==
D Alexander
|
|
From: Ivan V. <iv...@gm...> - 2007-09-25 15:19:10
|
Hi! You have come to the right place - m560x is the driver you're looking for. The driver development for your chip is going steadily, but it is all in alpha phase. You may want to try to test it, but from what I've tested on my 5603c, only some programs such as xawtv or livetv can display image. Your chip is being mentioned on the m560x-driver-devel list lately, you may want to subscribe to that list, too, to track the discussions. And just one note: when using mailing lists, please click on Reply to all, so that your message is delivered to the mailing list too, and not only the author of the message you're replying to, since authors do not always know how to help to you (I'm for example very unexperienced with this driver, but I'm hanging around hoping to help some day). Good luck! Try compiling and running the driver, then ask more specific questions if you run into trouble :) --- Ivan On Monday 24 September 2007, Patrik Karlsson wrote: > Yay! =) > > lsusb gives the following: > > Bus 007 Device 003: ID 0402:5602 ALi Corp. > Bus 007 Device 001: ID 0000:0000 > Bus 006 Device 001: ID 0000:0000 > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 001: ID 0000:0000 > Bus 005 Device 001: ID 0000:0000 > Bus 004 Device 002: ID 046d:c016 Logitech, Inc. M-UV69a Optical Wheel Mouse > Bus 004 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 > > A quite non descriptive description of the unit... *rolleyes* > > Thanks for helping! =) > > / Patrik > > On 9/24/07, Ivan Vucica <iv...@gm...> wrote: > > It's live alright, and since nobody responded to you yet, I might try to > > help. > > > > Can you punch this into the console (or a terminal)? > > $ lsusb > > > > Please tell us what's the output. > > > > ------------ > > Ivan Vucica > > > > On Fri, 21 Sep 2007, Patrik Karlsson wrote: > > > Hello all! > > > > > > First of all: Is this project still running? > > > > > > Second: I'm not really sure tat it is even this driver that I'm about > > > to use, but I do have a ALi Corp. USB2 webcam. However, from the > > > laptop manufacturer, I got to know that it is this shipset that is > > > built into the webcam: > > > http://www.ovt.com/products/part_detail.asp?id=26 > > > I have no idea what to make out of this, though - I know nothing about > > > programming, unfortunately. > > > > > > So, any life here? =) > > > > > > Best regards > > > Patrik > > > > > > ----------------------------------------------------------------------- > > >-- This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > _______________________________________________ > > > M560x-driver-support mailing list > > > M56...@li... > > > https://lists.sourceforge.net/lists/listinfo/m560x-driver-support |
|
From: Ivan V. <iv...@gm...> - 2007-09-24 07:09:12
|
It's live alright, and since nobody responded to you yet, I might try to help. Can you punch this into the console (or a terminal)? $ lsusb Please tell us what's the output. ------------ Ivan Vucica On Fri, 21 Sep 2007, Patrik Karlsson wrote: > Hello all! > > First of all: Is this project still running? > > Second: I'm not really sure tat it is even this driver that I'm about > to use, but I do have a ALi Corp. USB2 webcam. However, from the > laptop manufacturer, I got to know that it is this shipset that is > built into the webcam: > http://www.ovt.com/products/part_detail.asp?id=26 > I have no idea what to make out of this, though - I know nothing about > programming, unfortunately. > > So, any life here? =) > > Best regards > Patrik > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > M560x-driver-support mailing list > M56...@li... > https://lists.sourceforge.net/lists/listinfo/m560x-driver-support > |
|
From: Patrik K. <tav...@gm...> - 2007-09-21 10:26:41
|
Hello all! First of all: Is this project still running? Second: I'm not really sure tat it is even this driver that I'm about to use, but I do have a ALi Corp. USB2 webcam. However, from the laptop manufacturer, I got to know that it is this shipset that is built into the webcam: http://www.ovt.com/products/part_detail.asp?id=26 I have no idea what to make out of this, though - I know nothing about programming, unfortunately. So, any life here? =) Best regards Patrik |
|
From: <jer...@po...> - 2007-09-13 16:37:16
|
Hello, i have a clevo m55n laptop, with an internal usb webcam ALi m560x On kernel 2.6.18, it showed up on lsusb, and the driver (i believe it was the branche ot driver) did create /dev/video0 besides that it didn't work. Since kernel 2.6.21, lsusb doesn't show the ALi webcam. It's as if it wasn't connected. I tested the trunk and branch modules, they load but don't complain and lsusb doesn't show the webcam. No device file is created, of course. Any idea why lsusb wouldn't show the internal usb webcam any more ? could it be in relation with acpi ? |
|
From: Ivan V. <iv...@gm...> - 2007-08-31 22:48:30
|
Thanks for the response!
Here are some of the notes from my experiences with that branch. I'm sorry
for being ignorant on how to produce patches that might be easier for
you to use.
1) Kernel 2.6.22 no longer includes file linux/usb_ch9.h, now it's called
linux/usb/ch9.h.
I changed the include appropriately.
2) Changed the device definitions as here:
////////CUT
static struct usb_device_id m5603c_table[] = {
{USB_DEVICE(0x0458, 0x7020)},
{USB_DEVICE(0x041e, 0x4038)},
{USB_DEVICE(0x0402, 0x5603)},
{}
};
static char* m5603c_name[4] = {
"Genius Slim 321C",
"Creative WebCam Live! Pro",
"Sweex",
NULL
};
/////////CUT
I did not study the code below, but is the name in the m5603c_name array
supposed to match whatever the device reports? (Currently, lsusb seems to
be playing tricks on me, and /proc/bus/usb/devices seems to report name of
"For demo only", which seems right to me since I saw that somewhere, too,
but not in the lsusb listing).
3) Test program for sweex 5603 needs modification in pusb-linux.h. At
beginning add:
///// CUT
#define BITS_PER_LONG 32
#include <linux/types.h>
///// CUT
Looks like they added an #ifdef __KERNEL__, that's why this is needed.
4) Same test program, pusb-linux.c in line 285 change ctrl.bRequesttype
into ctrl.bRequestType. In Makefile, in line 8, remove -DFC5.
Images that were generated seem to have only 0x0a0a0a color. When I ran it
later on, it appears to have frozen somewhere.
5) Driver only generates blank picture, too.
6) $ insmod m5603c DBUG=16
m5603c: Unknown parameter `DBUG'
I also tried with DBG and DEBUG.
7) I did experience some null pointer related errors, but they appear to
be gone now. (I don't know what I did, I'll inform you if they
resurface.)
Hopefully some of this helps!
------------
Ivan Vucica
On Thu, 30 Aug 2007, Willem Duinker wrote:
>
> You can use the m5603c-mtv011 branch (under branches in the svn). Add the
> sweex id to the device-table (line 38 in m5603c.c)
>
> and it should work with the LiveCam program (see sourceforge). The is was
> made with a similar camera.
>
> Do not forget to put the firmware in the right directory
>
> The main trunk should also work (with the firmware and start-up scripts in
> right place, check with dmesg after loading the driver with DBUG=16) for the
> sweex. It only does always start (a bug in the start-up code)
> You should be able to compare with the above-mentioned branch.
>
> Willem
>
|
|
From: Willem D. <wdu...@xs...> - 2007-08-30 04:56:11
|
Ivan Vucica wrote: >Hi, > >I'm wondering what do the current driver developers use as their >development software configuration, since it might be the key to my lack >of success in getting the Sweex cam to work. It's the 0402:5603 piece of >hardware. The driver detects mt9v001 sensor and mentions ID 82 32, however > > You can use the m5603c-mtv011 branch (under branches in the svn). Add the sweex id to the device-table (line 38 in m5603c.c) and it should work with the LiveCam program (see sourceforge). The is was made with a similar camera. Do not forget to put the firmware in the right directory The main trunk should also work (with the firmware and start-up scripts in right place, check with dmesg after loading the driver with DBUG=16) for the sweex. It only does always start (a bug in the start-up code) You should be able to compare with the above-mentioned branch. Willem >no program is able to get any kind of picture from the camera, including >"xawtv" with -f option, as suggested in the documentation. > >With "hasciicam", I get "error in VIDIOCGCAP: invalid argument". I have >tried specifying the image size manually (with -s 640x480). Most other >programs have similar problems. > >Is Debian GNU/Linux, kernel 2.6.22 supported, or at least 2.6.21? I have >been unable to get image with any of these two kernels. > >Any help would be appreciated. Shell access to my laptop can be >arranged (to a limited amount of time, however, since I am on dialup). If >necessary, VNC access can be set up, too. If you supply what information I >should submit, I will give it out. Since I have "some" programming >experience, with proper directions I might try to fix the bug, but since I >am not familiar with the API I do not know where to start. > >If possible, I'd appreciate some response to acknowledge this message. > >------------ >Ivan Vucica > > > >------------------------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >M560x-driver-support mailing list >M56...@li... >https://lists.sourceforge.net/lists/listinfo/m560x-driver-support > > > > |
|
From: Ivan V. <iv...@gm...> - 2007-08-29 20:00:37
|
Hi, I'm wondering what do the current driver developers use as their development software configuration, since it might be the key to my lack of success in getting the Sweex cam to work. It's the 0402:5603 piece of hardware. The driver detects mt9v001 sensor and mentions ID 82 32, however no program is able to get any kind of picture from the camera, including "xawtv" with -f option, as suggested in the documentation. With "hasciicam", I get "error in VIDIOCGCAP: invalid argument". I have tried specifying the image size manually (with -s 640x480). Most other programs have similar problems. Is Debian GNU/Linux, kernel 2.6.22 supported, or at least 2.6.21? I have been unable to get image with any of these two kernels. Any help would be appreciated. Shell access to my laptop can be arranged (to a limited amount of time, however, since I am on dialup). If necessary, VNC access can be set up, too. If you supply what information I should submit, I will give it out. Since I have "some" programming experience, with proper directions I might try to fix the bug, but since I am not familiar with the API I do not know where to start. If possible, I'd appreciate some response to acknowledge this message. ------------ Ivan Vucica |
|
From: Guido S. <san...@gm...> - 2007-08-18 17:35:14
|
Hi. Recently I have tried to install m560x.ko and I got this dmesg output. I am using debian testing. First I modprobed videodev and v4l1-compat, then I copied the firmware files in fw to /lib/firmware. The output of dmesg is this, hope it is useful. Linux video capture interface: v2.00 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: usb_m560x_init - M560x-based WebCam driver startup /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: m560x_probe - M560x-based WebCam connected /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m5602_mt9v111.c: [m5602_probe_mt9v111:189] probe mt9v111 sensor id ff ff /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m5602_ov9650.c: [m5602_probe_ov9650:190] probe ov9650 sensor id ff ff /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m5602_ov7640.c: [m5602_probe_ov7640:190] probe ov7640 sensor id ff ff Unable to handle kernel NULL pointer dereference at 0000000000000068 RIP: [<ffffffff884aeee1>] :m560x:usb_m560x_probe+0x37e/0x682 PGD 33af067 PUD 2cae067 PMD 0 Oops: 0000 [1] SMP CPU 0 Modules linked in: m560x videodev v4l2_common v4l1_compat usbhid hid fglrx(P) binfmt_misc rfcomm l2cap bluetooth ppdev parport_pc lp parport button ac battery ipv6 cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand dm_crypt dm_snapshot dm_mirror dm_mod powernow_k8 freq_table cpufreq_userspace loop pcmcia firmware_class wlan_scan_sta snd_hda_intel ath_rate_sample i2c_piix4 snd_hda_codec joydev snd_pcm_oss snd_mixer_oss tsdev sdhci ath_pci i2c_core mmc_core yenta_socket rsrc_nonstatic shpchp wlan snd_pcm pcmcia_core pci_hotplug ath_hal(P) snd_timer pcspkr psmouse k8temp serio_raw snd soundcore snd_page_alloc evdev ext3 jbd mbcache ide_cd cdrom sd_mod ata_generic sata_sil libata scsi_mod atiixp 8139too generic 8139cp mii ide_core ehci_hcd ohci_hcd thermal processor fan Pid: 11872, comm: insmod Tainted: P 2.6.21-2-amd64 #1 RIP: 0010:[<ffffffff884aeee1>] [<ffffffff884aeee1>] :m560x:usb_m560x_probe+0x37e/0x682 RSP: 0018:ffff810002a0fc98 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff810002a16000 RCX: ffff8100026e55b8 RDX: ffff8100026e5238 RSI: ffff8100026e5190 RDI: ffff810002a16000 RBP: 0000000000000003 R08: 0000000000000124 R09: 0000000000000000 R10: 00000000047c8b30 R11: ffffffff8026c234 R12: ffffffff884b5e00 R13: ffff8100379dc000 R14: 0000000000000000 R15: ffff81003595b000 FS: 00002b373886e6e0(0000) GS:ffffffff804d7000(0000) knlGS:00000000f75eda20 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000068 CR3: 0000000002e7b000 CR4: 00000000000006e0 Process insmod (pid: 11872, threadinfo ffff810002a0e000, task ffff810027f158d0) Stack: 0000000000000282 ffff81003595b5d0 ffff81003595b088 ffff8100379dc000 0000000000000001 ffff810002a17dd0 ffff81003595b000 ffff81003595b088 0000000000000001 ffff8100379dc020 0000000000000000 ffffffff884b5e00 Call Trace: [<ffffffff8037ef6b>] usb_probe_interface+0xa7/0xde [<ffffffff803716e0>] really_probe+0xc5/0x14a [<ffffffff80371899>] __driver_attach+0x0/0x93 [<ffffffff803718f3>] __driver_attach+0x5a/0x93 [<ffffffff80370bd4>] bus_for_each_dev+0x43/0x6e [<ffffffff80370f16>] bus_add_driver+0x6b/0x18d [<ffffffff8037ea78>] usb_register_driver+0x7e/0xe4 [<ffffffff8801d030>] :m560x:usb_m560x_init+0x30/0x66 [<ffffffff802947c4>] sys_init_module+0x1656/0x17b9 [<ffffffff8020ca90>] dput+0x32/0x150 [<ffffffff8025511e>] system_call+0x7e/0x83 Code: 41 ff 56 68 f6 05 14 e2 00 00 10 74 39 41 b9 44 00 00 00 41 RIP [<ffffffff884aeee1>] :m560x:usb_m560x_probe+0x37e/0x682 RSP <ffff810002a0fc98> CR2: 0000000000000068 /home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: m560x open Greetings, Guido Sanchez -- Never make any mistaeks. |
|
From: Ludovic L. <lud...@ne...> - 2007-08-18 14:08:36
|
Hi every body First i'm french so excuse my poor english. I tried to compile this module for my asuslaptop A7D from the svn sources in the driver and branches directory. I give you the output from 'make' in /branches/m5602-ov9650 because is shortly : > make -C /lib/modules/2.6.22.3-ccj53-default/build > SUBDIRS=/home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650 > modules > make[1]: Entering directory > `/usr/src/linux-2.6.22.3-ccj53-obj/i386/default' > make -C ../../../linux-2.6.22.3-ccj53 > O=../linux-2.6.22.3-ccj53-obj/i386/default modules > CC [M] > /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.o > /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c: > In function ‘ov9650_i2c_write’: > /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:28: > error: implicit declaration of function ‘write_m5602_sensor_register’ > /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c: > In function ‘ov9650_set_ctrl’: > /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:64: > warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from > integer without a cast > /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:65: > warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from > integer without a cast > /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:68: > warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from > integer without a cast > /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:71: > warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from > integer without a cast > /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:74: > warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from > integer without a cast > make[4]: *** > [/home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.o] > Error 1 > make[3]: *** > [_module_/home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650] > Error 2 > make[2]: *** [modules] Error 2 > make[1]: *** [modules] Error 2 > make[1]: Leaving directory > `/usr/src/linux-2.6.22.3-ccj53-obj/i386/default' > make: *** [all] Error 2 I'm using opensuse 10.2 whith kernel 2.6.22.3 with kernel sources installed and linux-kernel-headers 2.6.22.10 Thanks a lot for you help Regards Ludo |
|
From: Kunszt A. <ku...@fr...> - 2007-07-20 14:20:16
|
Hi! I have an Acer 5112 notebook. I'm running Gentoo on it (AMD64). I get the source from SVN and build the trunk. After insmod ./m560x debug=16 I get this into the dmesg: Linux video capture interface: v2.00 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: usb_m560x_init - M560x-based WebCam driver startup /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: m560x_probe - M560x-based WebCam connected /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [usb_m560x_probe:2732] cam ffff810027b08000 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:967] initialize_m5602_camera /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: [initialize_m5602_camera:1020] 0x0ff9 13 /root/m560x-driver/m560x/trunk/km_m560x/m5602_mt9v111.c: [m5602_probe_mt9v111:189] probe mt9v111 sensor id ff ff /root/m560x-driver/m560x/trunk/km_m560x/m5602_ov9650.c: [m5602_probe_ov9650:190] probe ov9650 sensor id ff ff /root/m560x-driver/m560x/trunk/km_m560x/m5602_ov7640.c: [m5602_probe_ov7640:190] probe ov7640 sensor id ff ff Unable to handle kernel NULL pointer dereference at 0000000000000068 RIP: [<ffffffff884facd5>] :m560x:usb_m560x_probe+0x3b5/0x6c0 PGD 2fd5c067 PUD 2f165067 PMD 0 Oops: 0000 [1] PREEMPT SMP CPU 1 Modules linked in: m560x firmware_class videodev v4l2_common v4l1_compat tun vboxdrv fglrx(P) ipv6 wlan_scan_sta ath_rate_sample(F) psmouse sdhci mmc_core yenta_socket rsrc_nonstatic pcmcia_core r8169 bitrev crc32 ath_pci(F) wlan ath_hal(P) snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore snd_page_alloc sr_mod cdrom k8temp hwmon evdev sg reiserfs ext2 sbp2 ohci1394 ieee1394 usbhid ohci_hcd usb_storage ehci_hcd usbcore Pid: 7890, comm: insmod Tainted: PF 2.6.20-gentoo-r8-syrius #3 RIP: 0010:[<ffffffff884facd5>] [<ffffffff884facd5>] :m560x:usb_m560x_probe+0x3b5/0x6c0 RSP: 0018:ffff81002fd97db8 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff810027b08000 RCX: ffff81002cf155b8 RDX: ffff81002cf15508 RSI: 0000000000000000 RDI: ffff810027b08000 RBP: 0000000000000000 R08: 0000000000000000 R09: ffff81002cf154b0 R10: ffffffff804f3740 R11: 000000000000000c R12: ffffffff88501f00 R13: ffffffff885019e0 R14: ffff81003f1ddd78 R15: ffff81003f1ddc00 FS: 00002b6d17defae0(0000) GS:ffff810037e1d4c0(0000) knlGS:00000000f7deb6b0 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000068 CR3: 000000002c72a000 CR4: 00000000000006e0 Process insmod (pid: 7890, threadinfo ffff81002fd96000, task ffff81003d0297a0) Stack: 000000000000a1ff ffffffff802e12c9 0000000000000202 ffff810027b09d98 ffffffff80446c54 00000000fffffff4 ffff81002fd366e0 ffff81003f1ddc20 ffffffff88501a40 ffff81003f1ddc00 ffffffff885019e0 ffff81003f1ddd78 Call Trace: [<ffffffff802e12c9>] sysfs_make_dirent+0x29/0xb0 [<ffffffff88008c6e>] :usbcore:usb_probe_interface+0x8e/0xd0 [<ffffffff8035e33a>] really_probe+0x9a/0x140 [<ffffffff8035e560>] __driver_attach+0x0/0xb0 [<ffffffff8035e5c2>] __driver_attach+0x62/0xb0 [<ffffffff8035d679>] bus_for_each_dev+0x49/0x80 [<ffffffff8035da1e>] bus_add_driver+0x7e/0x1e0 [<ffffffff880086a4>] :usbcore:usb_register_driver+0x84/0x110 [<ffffffff8815f029>] :m560x:usb_m560x_init+0x29/0x5f [<ffffffff8029db22>] sys_init_module+0xc2/0x1a0 [<ffffffff8025ef2e>] system_call+0x7e/0x83 Code: ff 55 68 f6 05 61 d5 00 00 10 90 74 39 41 b9 44 00 00 00 41 RIP [<ffffffff884facd5>] :m560x:usb_m560x_probe+0x3b5/0x6c0 RSP <ffff81002fd97db8> CR2: 0000000000000068 Do you have any idea? Thanks. Arpad |