it would be a mighty coincidence if we both had messed up USB systems giving the same error with the same webcam on the same OS (Ubuntu 9.04 64bit). My system is USB 2.0, I've installed the driver from git. If I leave the camera plugged in, dmesg is spammed with "sn9c20x: Read register failed 0x1005" messages. It doesn't happen if I connect the camera after the system is booted up, so maybe the error has something to do with device registration?
On Jul 12, 5:44 pm, Josua Grawitter <[email protected]> wrote: > Am Sonntag 12 Juli 2009 16:16:18 schrieb craigsn: > > > > > I used the method outlined here (http://groups.google.com/group/ > > microdia/web/testing-microdia-driver-draft?hl=en), and everything > > seemed to work fine until I got to the part about mplayer testing. It > > did not work as expected. > > > ++++++++ > > MPlayer 1.0rc2-4.3.3 (C) 2000-2007 MPlayer Team > > CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (Family: 15, > > Model: 35, Stepping: 2) > > CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1 > > Compiled with runtime CPU detection. > > mplayer: could not connect to socket > > mplayer: No such file or directory > > Failed to open LIRC support. You will not be able to use your remote > > control. > > > Playing tv://. > > TV file format detected. > > Selected driver: v4l2 > > name: Video 4 Linux 2 input > > author: Martin Olschewski <[email protected]> > > comment: first try, more to come ;-) > > v4l2: unable to open '/dev/video0': No such file or directory > > v4l2: ioctl set mute failed: Bad file descriptor > > v4l2: 0 frames successfully processed, 0 frames dropped. > > > Exiting... (End of file) > > ++++++++++ > > > I made the mistake of installing the microdia driver permanently, and > > now on dmesg I get a whole lot of repeating > > ++ > > [ 1437.710076] sn9c20x: SN9C20X USB 2.0 Webcam releases control of > > video device /dev/video0 > > [ 1437.710081] sn9c20x: Read register failed 0x1005 > > [ 1437.710083] sn9c20x: Read register failed 0x1005 > > [ 1437.710085] sn9c20x: Read register failed 0x1005 > > [ 1437.710087] sn9c20x: Read register failed 0x1005 > > [ 1437.710089] sn9c20x: Read register failed 0x1005 > > [ 1437.710091] sn9c20x: Read register failed 0x1005 > > [ 1437.710093] sn9c20x: Read register failed 0x1005 > > [ 1437.710095] sn9c20x: Read register failed 0x1005 > > [ 1437.710097] sn9c20x: Read register failed 0x1005 > > [ 1437.710098] sn9c20x: Read register failed 0x1005 > > [ 1437.710100] sn9c20x: Read register failed 0x1005 > > [ 1437.710102] sn9c20x: Read register failed 0x1005 > > [ 1437.710104] sn9c20x: Read register failed 0x1005 > > [ 1437.710106] sn9c20x: Read register failed 0x1005 > > [ 1437.710108] sn9c20x: Read register failed 0x1005 > > [ 1437.710110] sn9c20x: Read register failed 0x1005 > > [ 1437.710112] sn9c20x: Read register failed 0x1005 > > [ 1437.710114] sn9c20x: Read register failed 0x1005 > > [ 1437.710115] sn9c20x: Read register failed 0x1005 > > [ 1437.710117] sn9c20x: Read register failed 0x1005 > > ++ > > > What should I try to do to make this work? > > > Thanks > > Craig > > > > It seems your USB system is messed up. Are you using a USB hub, long cables or > anything else exotic? Maybe USB 1.0 or 1.1? > > That's the only explanation I can come up with from the dmesg output. > > 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 -~----------~----~----~----~------~----~------~--~---
