pwc
[Top] [All Lists]

Re: [pwc] pwc driver in FC3 causes all kind of problems and kills keyboa

To: Philips Webcam Linux Driver <>
Subject: Re: [pwc] pwc driver in FC3 causes all kind of problems and kills keyboard
From: "" <>
Date: Wed, 8 Jun 2005 18:12:15 +0300
On Wed, Jun 08, 2005 at 04:49:16PM +0200, Luc Saillard wrote:
> On Tue, Jun 07, 2005 at 11:13:29PM +0300,  wrote:
> > How come switching to runlevel 3 fixes the pwc driver problem at least
> > "partly", meaning I can restart pwc-driver and video device?
>  
> Because i don't know what runlevel3 do on a fedora system. If you want to be
> sure (and i don't understand your bug report in bugzilla) that no other
> application is running, use at start init=/bin/sh, then mount all your
> filesystem, load pwc module, and launch your application that grab some

In Fedora, runlevel3 is everything but X (and gdm, GNOME, stuff over X)
runlevel 5 is then with X.

>From /etc/inittab:
# Default runlevel. The runlevels used by RHS are:
#   3 - Full multiuser mode
#   5 - X11

> video. But if the problem is in ps2+usb, i can't help. pwc is special because
> it's use some isochronous message on the usb bus. But any webcam uses
> this, so try to switch to another webcam ? If i fully understand, you lost

I have tried with two new webcams, but both were Logitech Quickcam 4000 Pros.
Also with two different USB controllers.

> some (too many) urb (packets), and the usb stack can't recover from error.
> Perhaps you PCI bus, usb (because you use bluetooth key, ...) use too much
> cpu times to transfer data in continous. If the kernel x.y.z works, try to

Maybe. 

> narrow down the bug to test every kernel until this bug is not working. Try

Yes, I will. The frustrating problem is, with some kernels also keyboard
and mouse stops working when pwc driver stops and it is hard to debug
after that. 

> each -rc, and bk to find the patch that have break the usb stack or the ps2
> stack .... I don't have your computer, so i can't do the test for you.
> Sorry for being to answer this,

No problem, I understand fully. But already now, I have got some new
ideas how to narrow down the problem, which I wouldn't have got if I
wouldn't have filed a bug report.

This could be a hardware problem, but yet I think even if it is, it also is 
a software bug, because the system in many cases becomes unusabe (DOS)
for reasons which are still unknown. It could be a Xorg Input-driver
problem. (at least nvidia and nv X-drivers behave the same)

// jouni

_______________________________________________
pwc mailing list

http://lists.saillard.org/mailman/listinfo/pwc

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU