On Tuesday, October 26, 2010 10:35:42 am Alan Stern did opine: > On Mon, 25 Oct 2010, gene heskett wrote: > > On Monday, October 25, 2010 06:35:05 pm Alan Stern did opine: > > > On Mon, 25 Oct 2010, gene heskett wrote: > > > > Hi folks; > > > > > > > > I have an elderly labtec webcan, usb interface that can run > > > > (theoretically) in 640x480 as well as 320x240. Plugged directly > > > > into a motherboard breakout port, it runs well at 320x240, but if > > > > I select 640x480 in cheese, it only works for about 15% of a > > > > frame and errors out with hundreds of these lines in the terminal > > > > window I launched it from: > > > > > > > > libv4lconvert: Error decompressing JPEG: fill_nbits error: need 7 > > > > more bits libv4lconvert: Error decompressing JPEG: fill_nbits > > > > error: need 3 more bits libv4lconvert: Error decompressing JPEG: > > > > fill_nbits error: need 4 more bits libv4lconvert: Error > > > > decompressing JPEG: fill_nbits error: need 2 more bits > > > > > > > > The driver appears to be the (from lsmod) > > > > gspca_zc3xx 34210 0 > > > > gspca_main 17233 1 gspca_zc3xx > > > > > > > > From dmesg: > > > > [gene@coyote log]$ grep gspca dmesg > > > > gspca: main v2.10.0 registered > > > > gspca: probing 046d:08a2 > > > > gspca: video0 created > > > > > > > > I can make it work about 90% of the time when booted to 2.6.35.7, > > > > but its a 100% failure with 2.6.36 until I select 320x240. > > > > > > > > Is there anything I can do? > > > > > > Did you build the kernel with CONFIG_USB_DEBUG? > > > > No, the last time I did that, several kernel versions back I had a 2Gb > > messages file in 10 minutes. A bit much IMO. > > Well, maybe it's time to try again. > > > > Did you check the > > > dmesg log? > > > > Yes, more of the same I believe, but lemme check. > > All I can see ATM is megabytes of this: > > sd 10:0:0:3: __pm_runtime_resume() returns 1! > > sd 10:0:0:1: __pm_runtime_resume()! > > sd 10:0:0:1: __pm_runtime_resume() returns 1! > > sd 10:0:0:0: __pm_runtime_resume()! > > sd 10:0:0:0: __pm_runtime_resume() returns 1! > > scsi host4: __pm_runtime_resume()! > > scsi host4: __pm_runtime_resume() returns 1! > > scsi host4: __pm_runtime_resume()! > > scsi host4: __pm_runtime_resume() returns 1! > > scsi host4: __pm_runtime_resume()! > > You can get rid of those by disabling CONFIG_PM_VERBOSE I found this and turned it off. This I take it is not an error, just informational? > and > CONFIG_DEBUG_DRIVER. But this one doesn't grep. > > > > Did you post to the linux-media mailing list? > > > > I'm not subscribed. To me, it looks like a usb problem. > > Why? > > And if it is a USB problem, doesn't enabling CONFIG_USB_DEBUG seem > like a good idea? Done, building now. > Alan Stern > Thanks Alan. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) When confronted by a difficult problem, you can solve it more easily by reducing it to the question, "How would the Lone Ranger handle this?" -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
