Yeah camorama only supports v4l1 and our driver uses v4l2. You will need to use libv4l with our driver to support v4l1 application. Its also needed with many v4l2 applications in order to do format conversion. Please read the README included with our driver
On Wed, Jan 7, 2009 at 9:32 PM, kihoma <[email protected]> wrote: > > Well, finally not so bad news. I mean, good news from DMESG. See > output below > > microdia: Microdia USB 2.0 webcam driver loaded > microdia: Microdia USB 2.0 Webcam - 0C45:6242 plugged-in. > microdia: Detected SN9C20X Bridge > microdia: Detected MT9M111 Sensor > microdia: Microdia USB 2.0 Webcam is now controlling video device /dev/ > video0 > usbcore: registered new interface driver usb_microdia_driver > microdia: v2008.11 : Microdia USB 2.0 Webcam Driver > sn9c20x: SN9C20X USB 2.0 webcam driver loaded > usbcore: registered new interface driver usb_sn9c20x_driver > sn9c20x: v2008.11 : SN9C20X USB 2.0 Webcam Driver > > So, finally the system las loaded the driver with no problems, nor > error. But when I open camorana it complains not to be able to open / > dev/video0 device > I have this simlink "webcam" to /dev/video0 wich is created by this > rule: > > KERNEL=="video*", SYSFS{idVendor}=="0c45", SYSFS{idProduct}=="6242", > SYMLINK+="webcam" > > And, of course, my /dev/video0 IS there. So, I don't know why camorama > complains about opening it. > I tried camorama -d=/dev/webcam but it also didn't work out. It also > complains it cannot open /dev/webcam > > ls -lah on /dev|grep video gives me this: > > crw-rw---- 1 root video 81, 0 2009-01-07 22:03 video0 > lrwxrwxrwx 1 root root 6 2009-01-07 22:03 webcam -> > video0 > > cat /etc/group|grep video gives this: > > video:x:44:my-user-name > > So, my-user-name IS in the video group. > > Any suggestion? > > > > On Jan 6, 2:05 pm, GWater <[email protected]> wrote: >> kihoma schrieb: >> >> >> >> > Hi there guys, >> > I recently bought 02 webcams (me and my sister) with this chip >> > microdia 0c45:6242> Below is the output form my lsusb: >> > Bus 002 Device 003: ID 0c45:6242 Microdia >> > Bus 002 Device 002: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 >> > USB-2.0 "TetraHub" >> > Bus 002 Device 001: ID 0000:0000 >> > Bus 001 Device 001: ID 0000:0000 >> >> > So, I tried the gspca module but didn't work. Then yesterday I went >> > to git clone git microdia and installed the microdia driver It kept >> > saying "could not find /dev/hda0" on camorama. Mplayer also couldn't >> > open the device. Xawtv also didn't work. >> > Now I have downloaded the latest sn9c20x and the dmsg output is as >> > follows: >> >> > sn9c102: V4L2 driver for SN9C1xx PC Camera Controllers v1:1.47 >> > usbcore: registered new interface driver sn9c102 >> > usbcore: deregistering interface driver sn9c102 >> > sn9c20x: SN9C20X USB 2.0 webcam driver loaded >> > sn9c20x: SN9C20X USB 2.0 Webcam - 0C45:6242 plugged-in. >> > sn9c20x: Write register failed index = 0x1000 >> > sn9c20x: Bridge Init Error (-71). line 0 >> > sn9c20x: Device Init failed (-71)! >> > usb_sn9c20x_driver: probe of 2-2:1.0 failed with error -71 >> > usbcore: registered new interface driver usb_sn9c20x_driver >> > sn9c20x: v2008.11 : SN9C20X USB 2.0 Webcam Driver >> > microdia: Microdia USB 2.0 webcam driver loaded >> > microdia: Microdia USB 2.0 Webcam - 0C45:6242 plugged-in. >> > microdia: Detected SN9C20X Bridge >> > microdia: Write register failed index = 0x1000 >> > microdia: Bridge Init Error (-71). line 0 >> > microdia: Device Init failed (-71)! >> > usb_microdia_driver: probe of 2-2:1.0 failed with error -71 >> >> > So I unloaded the driver sn9c20x >> >> > microdia: usb_microdia_exit: Microdia USB 2.0 webcam driver unloaded >> > usbcore: deregistering interface driver usb_microdia_driver >> >> > And the loaded it again sn9c20x: >> >> > sn9c20x: SN9C20X USB 2.0 webcam driver loaded >> > sn9c20x: SN9C20X USB 2.0 Webcam - 0C45:6242 plugged-in. >> > sn9c20x: Write register failed index = 0x1000 >> > sn9c20x: Bridge Init Error (-71). line 0 #error detecting the bridge >> > sn9c20x: Device Init failed (-71)! >> > usb_sn9c20x_driver: probe of 2-2:1.0 failed with error -71 >> > usbcore: registered new interface driver usb_sn9c20x_driver >> > sn9c20x: v2008.11 : SN9C20X USB 2.0 Webcam Driver >> >> > Then I unload it and load the first microdia driver, wich compialed to >> > microdia.ko and the DMESG output is as follows: >> >> > microdia: Microdia USB 2.0 webcam driver loaded >> > microdia: Microdia USB 2.0 Webcam - 0C45:6242 plugged-in. >> > microdia: Detected SN9C20X Bridge >> > microdia: Write register failed index = 0x1000 >> > microdia: Bridge Init Error (-71). line 0 >> > microdia: Device Init failed (-71)! >> > usb_microdia_driver: probe of 2-2:1.0 failed with error -71 >> > usbcore: registered new interface driver usb_microdia_driver >> > microdia: v2008.11 : Microdia USB 2.0 Webcam Driver >> >> > It seems that, the previous driver (microdia) fails on detecting the >> > sensor and the sn9c20x driver fails on detecting the bridge and the >> > sensor... Am I right? >> >> > Guys, I do need some help... >> >> And I'll try my best here: >> >> There is no problem detecting sensor or bridge. >> The error -71 has it's origin within the usb subsystem and our driver >> simply passes it on. -71 (very helpfully) means "protocol error". >> >> Of course the susbsystem is silent about the actual cause which may be a >> delayed impulse, a broken cable or a problem in your camera. No way of >> knowing. >> >> To test your webcam I advice to test it with another computer (and maybe >> a live cd capable of compiling kernels). >> >> Apart from that: >> Keep trying. Maybe it will work on a sunny day with a lot of solar >> flares (who knows ;) ). >> >> Good luck. >> GWater >> >> signature.asc >> < 1KViewDownload > > > --~--~---------~--~----~------------~-------~--~----~ Lets make microdia webcams plug'n play, (currently plug'n pray) To post to this group, send email to [email protected] Visit us online https://groups.google.com/group/microdia -~----------~----~----~----~------~----~------~--~---
