* NOTE: This is -mm2. I will be compiling 2.5.53 (-mm1) today and test this as
well.
Initial Power on of USB Device:
ehci-hcd 02:08.2: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT
hub 1-0:0: port 2, status 501, change 1, 480 Mb/s
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x501
hub 1-0:0: port 2 not reset yet, waiting 10ms
hub 1-0:0: port 2 not reset yet, waiting 10ms
hub 1-0:0: port 2 not reset yet, waiting 200ms
ehci-hcd 02:08.2: port 2 full speed --> companion
ehci-hcd 02:08.2: GetStatus port 2 status 003801 POWER OWNER sig=j CONNECT
drivers/usb/host/ehci-hcd.c: 02:08.2: free_config devnum 0
drivers/usb/host/ohci-hub.c: 02:08.1: GetStatus roothub.portstatus [1] =
0x00010101 CSC PPS CCS
hub 3-0:0: port 1, status 101, change 1, 12 Mb/s
hub 3-0:0: debounce: port 1: delay 100ms stable 4 status 0x101
drivers/usb/host/ohci-hub.c: 02:08.1: GetStatus roothub.portstatus [1] =
0x00100103 PRSC PPS PES CCS
hub 3-0:0: new USB device on port 1, assigned address 4
drivers/usb/core/usb.c: new device strings: Mfr=1, Product=2, SerialNumber=0
Product: JamC@m 2.? OR JamC@m 2.0 OR JamC@m 2.0__________ depending on
connection quality (?)
Manufacturer: KBGear Interactive
drivers/usb/core/usb.c: usb_new_device - registering 3-1:0
When attempting to configure device:
drivers/usb/core/usb.c: usbfs driver claimed interface d0447c80
drivers/usb/host/ohci-q.c: urb cf17e0c0 usb-02:08.1-1 ep-0-OUT cc 4 --> status
-32
usbfs: USBDEVFS_CONTROL failed dev 5 rqt 64 rq 165 len 0 ret -32
drivers/usb/host/ohci-q.c: urb cf17e0c0 usb-02:08.1-1 ep-1-IN cc 8 --> status
-75
usbfs: USBDEVFS_BULK failed dev 5 ep 0x81 len 12 ret -75
>From the Userland side we get errors and a failure 'Error Reading from port'
On Tue, Dec 24, 2002 at 03:33:21PM -0500, Shawn Starr wrote:
> * NOTE: This is -mm2. I will be compiling 2.5.53 (-mm1) today and test this as
> well.
Please let us know how 2.5.53 works, as there were a number of ehci
patches in it that might have helped.
thanks,
greg k-h
2.5.53-mm1 compiled w/ lm_sensors merged in:
Same error however new thing:
When a non-root user tries to configure the USB device the userland program
returns 'Unable to claim USB device'
When a root user tries to it reports the same errors as in the previous email.
Shawn.
On Tuesday 24 December 2002 3:40 pm, Greg KH wrote:
> On Tue, Dec 24, 2002 at 03:33:21PM -0500, Shawn Starr wrote:
> > * NOTE: This is -mm2. I will be compiling 2.5.53 (-mm1) today and test
> > this as well.
>
> Please let us know how 2.5.53 works, as there were a number of ehci
> patches in it that might have helped.
>
> thanks,
>
> greg k-h
With 2.5.52/2.5.53 (mm2 and mm1). I notice that my network connectivity drops.
I loose connectivity to the outside. This just started to happen while trying
to configure the USB device (in this case a cheap digital camera).
Odd.
Shawn.
On Tuesday 24 December 2002 4:52 pm, Shawn Starr wrote:
> 2.5.53-mm1 compiled w/ lm_sensors merged in:
>
> Same error however new thing:
>
> When a non-root user tries to configure the USB device the userland program
> returns 'Unable to claim USB device'
>
> When a root user tries to it reports the same errors as in the previous
> email.
>
> Shawn.
>
> On Tuesday 24 December 2002 3:40 pm, Greg KH wrote:
> > On Tue, Dec 24, 2002 at 03:33:21PM -0500, Shawn Starr wrote:
> > > * NOTE: This is -mm2. I will be compiling 2.5.53 (-mm1) today and test
> > > this as well.
> >
> > Please let us know how 2.5.53 works, as there were a number of ehci
> > patches in it that might have helped.
> >
> > thanks,
> >
> > greg k-h
On Tue, Dec 24, 2002 at 04:52:44PM -0500, Shawn Starr wrote:
> 2.5.53-mm1 compiled w/ lm_sensors merged in:
>
> Same error however new thing:
>
> When a non-root user tries to configure the USB device the userland program
> returns 'Unable to claim USB device'
So you are using usbfs? What program? Nothing changed with usbfs from
2.5.52 to 2.5.53, but some things did change from 2.5.50 to 2.5.51. Did
.50 work for you?
thanks,
greg k-h
mount reports:
usbfs on /proc/bus/usb type usbfs (rw)
/etc/fstab:
usbfs /proc/bus/usb usbfs defaults 0 0
well, KDE has a plugin that utilizes libusb, libgphoto2 to manipulate the
camera.
I never tried the USB on this machine in 2.5 or 2.4.
Shawn.
On Tuesday 24 December 2002 5:09 pm, Greg KH wrote:
> On Tue, Dec 24, 2002 at 04:52:44PM -0500, Shawn Starr wrote:
> > 2.5.53-mm1 compiled w/ lm_sensors merged in:
> >
> > Same error however new thing:
> >
> > When a non-root user tries to configure the USB device the userland
> > program returns 'Unable to claim USB device'
>
> So you are using usbfs? What program? Nothing changed with usbfs from
> 2.5.52 to 2.5.53, but some things did change from 2.5.50 to 2.5.51. Did
> .50 work for you?
>
> thanks,
>
> greg k-h
On Tue, Dec 24, 2002 at 05:25:15PM -0500, Shawn Starr wrote:
> mount reports:
> usbfs on /proc/bus/usb type usbfs (rw)
>
> /etc/fstab:
> usbfs /proc/bus/usb usbfs defaults 0 0
>
> well, KDE has a plugin that utilizes libusb, libgphoto2 to manipulate the
> camera.
And you are sure that this camera works with Linux?
> I never tried the USB on this machine in 2.5 or 2.4.
Have you tried this camera on any other Linux machine, with any other
kernel?
thanks,
greg k-h
Well, libgphoto2 reports that my camera is supported. It supports JamCam
versions 2.0 and 3.0.
I haven't tried it in any other Linux machine.
Shawn.
On Thursday 26 December 2002 12:51 pm, Greg KH wrote:
> On Tue, Dec 24, 2002 at 05:25:15PM -0500, Shawn Starr wrote:
> > mount reports:
> > usbfs on /proc/bus/usb type usbfs (rw)
> >
> > /etc/fstab:
> > usbfs /proc/bus/usb usbfs defaults 0 0
> >
> > well, KDE has a plugin that utilizes libusb, libgphoto2 to manipulate the
> > camera.
>
> And you are sure that this camera works with Linux?
>
> > I never tried the USB on this machine in 2.5 or 2.4.
>
> Have you tried this camera on any other Linux machine, with any other
> kernel?
>
> thanks,
>
> greg k-h
On Thu, Dec 26, 2002 at 02:33:15PM -0500, Shawn Starr wrote:
> Well, libgphoto2 reports that my camera is supported. It supports JamCam
> versions 2.0 and 3.0.
>
> I haven't tried it in any other Linux machine.
As there are no visible usb subsystem errors or failures here, I would
take it up with the gphoto people :)
Good luck,
greg k-h