On 4/16/06, Rick Sewill <rsewill@xxxxxxxxxxxx> wrote: > I have been able to use spca5xx-20060202 with FC5. > > I have a Dell Latitude D800. My device is a Logitech webcam. > Both spcaview and ekiga are happy. Both show me webcam images. > My particular device was Vendor=046d ProdID=0928 > > Michel Xhaard was very helpful and responsive when I asked for help. > My Logitech webcam was "new" and not yet supported by spca5xx. > Fortunately, spca5xx was not crashing or doing other bad things--the > webcam was just not working. > > I cannot blame Michel for not having access to every distro of Linux. > Companies I have worked for specifically state which versions of which > distros have been tested with their software. I believe having a > choice of distros is both a strength and a weakness, but on balance, > one of the reasons I prefer Linux to the well known desktop O. S. Sure, I can understand that. But his argument that he'll only look into issues with official kernel.org kernels fell flat when he didn't even respond to my emails once I had replicated the same problem with an official kernel.org kernel. It might very well be specific to a particular type of motherboard chipset. Mine was an nvidia NFORCE/MCP51. I'm prety sure that Dell isn't shipping anything like that. > > Question: Is there a way we can collect information that would be > helpful or useful for the people working on spca5xx? > > In spca5xx-20060202/README, there is a section, "What to do if your > cam doesn't work". The README suggests "load the module with debug=4 > and check syslog for some extremely verbose debug information;". The > verbose debug information may not mean anything to us...but might help > the people working on spca5xx. > > I guess one could do the following, "insmod spca5xx.ko debug=4", to > see what the driver thinks during initialization. The real problem > comes when a program tries to use the driver...I don't know what to > suggest for debugging that. One of the joys of Linux is we have the > source. How would people go about debugging a driver hang or crash > given people have the source? I'm reasonably confident that in this case, the problem is related in some way to the 2.6.16 kernel. I was also seeing the same problem with the latest FC4 2.6.16 kernel. > > -Rick > > On Sun, Apr 16, 2006 at 10:18:45AM -0700, Lonni J Friedman wrote: > > On 4/16/06, tiger <no-reply-gw@xxxxxxxxxxxxxxxxx> wrote: > > > 2.6.16-1.2080_FC5smp > > > gcc (GCC) 4.1.0 20060304 (Red Hat 4.1.0-3) > > > spca5xx-20060402 > > > > > > Compiles and installs fine. Modprobe spca5xx works fine. Here's the /var/log/messages output of doing a "modprobe spca5xx": > > > > > > Apr 16 12:18:39 electron kernel: Linux video capture interface: v1.00 > > > Apr 16 12:18:39 electron kernel: usbcore: registered new driver spca5xx > > > Apr 16 12:18:39 electron kernel: /root/spca5xx-20060402/drivers/usb/spca5xx.c: spca5xx driver 00.57.11 registered > > > > > > Next, I plug in the camera, and /var/log/messages gives: > > > > > > > > > Apr 16 12:20:33 electron kernel: usb 1-2: new full speed USB device using uhci_hcd and address 4 > > > Apr 16 12:20:33 electron kernel: usb 1-2: configuration #1 chosen from 1 choice > > > Apr 16 12:20:33 electron kernel: hub 1-2:1.0: USB hub found > > > Apr 16 12:20:33 electron kernel: hub 1-2:1.0: 4 ports detected > > > Apr 16 12:20:34 electron kernel: usb 1-2.4: new full speed USB device using uhci_hcd and address 5 > > > Apr 16 12:20:34 electron kernel: usb 1-2.4: configuration #1 chosen from 1 choice > > > Apr 16 12:20:34 electron kernel: /root/spca5xx-20060402/drivers/usb/spca5xx.c: USB SPCA5XX camera found. Type Creative Live! Zc301+Tas5130c > > > Apr 16 12:20:34 electron kernel: /root/spca5xx-20060402/drivers/usb/spca5xx.c: [spca5xx_probe:8301] Camera type JPEG > > > Apr 16 12:20:35 electron kernel: /root/spca5xx-20060402/drivers/usb/zc3xx.h: [zc3xx_config:530] Find Sensor HV7131R(c) > > > Apr 16 12:20:35 electron kernel: /root/spca5xx-20060402/drivers/usb/spca5xx.c: [spca5xx_getcapability:2198] maxw 640 maxh 480 minw 176 minh 144 > > > > > > But when I run spcaview, it freezes the machine. For obvious reasons I can't cut-n-paste the screen output. Any ideas? > > > > Same problem here with FC5 & spca5xx on a Biostar motherboard. I had > > a serial console setup, and saw some crazy kernel Oops everytime. I > > emailed the spca5xx maintainer and he blew me off initially stating > > that he only supports official kernel.org kernels. So I built an > > official 2.6.16.1 kernel, and saw the same exact Oops all over again > > (plus on my system it just spontaneously reboots, instead of hanging). > > Now the maintainer is just ignoring my emails, which leads me to > > believe that he doesn't know how to fix the problem. *sigh* -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@xxxxxxxxx LlamaLand http://netllama.linux-sxs.org
