Quoting Bret Comstock Waldow <bwaldow@xxxxxxxxxxxxxx>: > Dmitri wrote: > > >There is no need to debug xawtv, it works just fine. Your problem (garbled > >image) originates in the driver, not somewhere else. > > I don't intend to suggest otherwise (I don't know enough) but it > provided lots of information, and those messages did say "Invalid". I > was hoping it would allow someone to quickly cut down the range of > possibilities. The debugging logs that you provided were very helpful. It's just they proved that xawtv is not at fault here :-) > >Load ultracam driver with option 'flags=8' and see what happens. You > >should see a stable group of white overlayed numbers on top of garbled > >image (as you had before). If this is what happens then the image decoder > >fails to decode the camera stream. > > This is what I see. The topmost number also has a horizontal bar > appearing next to it. The bar shows traveling red and grean narrow > vertical bars with blue between them alternating with apparent > transparency (I can see the garbled image there). Yes, I remember that :-) The bar shows the usbvideo queue status. This "picture" (numbers and the moving bars) is generated artificially inside the driver (in usbvideo, to be precise) and placed into the output buffer exactly as the v4l app requested. This means that your xawtv is working very well, and even the driver's v4l interface works well too. But the code that takes camera's datastream and converts it into the image - that code fails. You can grab images in xawtv with the 'G' key, BTW. A picture is worth of 1024 words :-) You can always mail it to interested parties, but not to the whole mailing list, of course :-) > When I modprobe, I receive this warning: > Warning: /lib/modules/2.4.16-4GB/kernel/drivers/usb/ultracam.o symbol > for parameter lighting not found > > Does anyone have an insight into this? It's a minor bug in ultracam, you can fix that if it bothers you: //static int lighting = 1; /* Medium */ MODULE_PARM(lighting, "i"); The parameter is declared but never allocated, so the loader complains. Just comment out the MODULE_PARM line and recompile the module. > If this isn't the place to discuss such, can you suggest another list or > forum? The author listed for this driver hasn't responded to my email yet. linux-usb-users is a good place. See http://www.linux-usb.org/ Thanks, Dmitri -- (I tried to get some documentation out of Digital on this, but as far as I can tell even _they_ don't have it ;-) (Linus Torvalds, in an article on a dnsserver)
Attachment:
pgprroTMrAluD.pgp
Description: PGP signature
