* usb interface to Toshiba PDR-M4 cam hasn't worked since 2.4.5
@ 2001-10-24 18:24 erik-lkml
2001-10-24 19:24 ` Johannes Erdfelt
0 siblings, 1 reply; 2+ messages in thread
From: erik-lkml @ 2001-10-24 18:24 UTC (permalink / raw)
To: linux-kernel
If there's a usb list this would be more appropriate in, please let me
know.
I have a Toshiba PDR-M4 digital camera with USB interface, which
appeared as
a scsi device attached with usb-storage in linux-2.4.5, but hasn't
worked in
any kernel since then. Here's a snippet from dmesg from 2.4.5, with a
successful negotiation with the camera (and its 128MB smart media card).
The
usbcore, usb-uhci, usb-storage, and sd modules are already loaded at
this point.
usb-uhci.c: v1.251 Georg Acher, Deti Fliegl, Thomas Sailer, Roman
Weissgaerber
usb-uhci.c: USB Universal Host Controller Interface driver
hub.c: USB new device connect on bus1/1, assigned device number 2
usb.c: USB device 2 (vend/prod 0x1132/0x4331) is not claimed by any
active driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
usb-uhci.c: interrupt, status 2, frame# 1366
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: TOSHIBA Model: PDR Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: Write Protect is off
/dev/scsi/host0/bus0/target0/lun0: p1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
And here's dmesg output from the same operation with 2.4.13:
* turn camera to 'data' mode *
hub.c: port 2 connection change
hub.c: port 2, portstatus 101, change 1, 12 Mb/s
hub.c: port 2, portstatus 103, change 0, 12 Mb/s
hub.c: USB new device connect on bus1/2, assigned device number 6
* 4-second pause *
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=6 (error=-110)
hub.c: port 2, portstatus 103, change 0, 12 Mb/s
hub.c: USB new device connect on bus1/2, assigned device number 7
* 4-second pause *
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=7 (error=-110)
And no more messages until I turn off or disconnect the camera. It
never
procedes to initialize usb-storage on this device.
The same errors ("usb_control/bulk_msg: timeout" and "USB device not
accepting
new address=7 (error=-110)") have occurred with every kernel since 2.4.6
when
I attempt to attach this camera. I don't believe it ever worked with
2.2.18/.19
either, but it did work with 2.2.17 with Alan's usb patches.
-Erik Schorr
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: usb interface to Toshiba PDR-M4 cam hasn't worked since 2.4.5
2001-10-24 18:24 usb interface to Toshiba PDR-M4 cam hasn't worked since 2.4.5 erik-lkml
@ 2001-10-24 19:24 ` Johannes Erdfelt
0 siblings, 0 replies; 2+ messages in thread
From: Johannes Erdfelt @ 2001-10-24 19:24 UTC (permalink / raw)
To: erik-lkml; +Cc: linux-kernel
On Wed, Oct 24, 2001, erik-lkml@arpa.org <erik-lkml@arpa.org> wrote:
> If there's a usb list this would be more appropriate in, please let me
> know.
linux-usb-devel@lists.sourceforge.net
I thought we did a good job advertising it. Where did you look?
> I have a Toshiba PDR-M4 digital camera with USB interface, which
> appeared as a scsi device attached with usb-storage in linux-2.4.5, but
> hasn't worked in any kernel since then. Here's a snippet from dmesg from
> 2.4.5, with a successful negotiation with the camera (and its 128MB smart
> media card). The usbcore, usb-uhci, usb-storage, and sd modules are
> already loaded at this point.
>
> usb-uhci.c: v1.251 Georg Acher, Deti Fliegl, Thomas Sailer, Roman
> Weissgaerber
> usb-uhci.c: USB Universal Host Controller Interface driver
> hub.c: USB new device connect on bus1/1, assigned device number 2
> usb.c: USB device 2 (vend/prod 0x1132/0x4331) is not claimed by any
> active driver.
> Initializing USB Mass Storage driver...
> usb.c: registered new driver usb-storage
> usb-uhci.c: interrupt, status 2, frame# 1366
> scsi0 : SCSI emulation for USB Mass Storage devices
> Vendor: TOSHIBA Model: PDR Rev: 1.00
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi removable disk sda at scsi0, channel 0, id 0, lun 0
> SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
> sda: Write Protect is off
> /dev/scsi/host0/bus0/target0/lun0: p1
> WARNING: USB Mass Storage data integrity not assured
> USB Mass Storage device found at 2
> USB Mass Storage support registered.
>
> And here's dmesg output from the same operation with 2.4.13:
>
> * turn camera to 'data' mode *
> hub.c: port 2 connection change
> hub.c: port 2, portstatus 101, change 1, 12 Mb/s
> hub.c: port 2, portstatus 103, change 0, 12 Mb/s
> hub.c: USB new device connect on bus1/2, assigned device number 6
> * 4-second pause *
> usb_control/bulk_msg: timeout
> usb.c: USB device not accepting new address=6 (error=-110)
> hub.c: port 2, portstatus 103, change 0, 12 Mb/s
> hub.c: USB new device connect on bus1/2, assigned device number 7
> * 4-second pause *
> usb_control/bulk_msg: timeout
> usb.c: USB device not accepting new address=7 (error=-110)
>
> And no more messages until I turn off or disconnect the camera. It
> never procedes to initialize usb-storage on this device.
>
> The same errors ("usb_control/bulk_msg: timeout" and "USB device not
> accepting new address=7 (error=-110)") have occurred with every kernel
> since 2.4.6 when I attempt to attach this camera. I don't believe it
> ever worked with 2.2.18/.19 either, but it did work with 2.2.17 with
> Alan's usb patches.
Have you tried using the alternate UHCI driver?
JE
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-10-24 19:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-10-24 18:24 usb interface to Toshiba PDR-M4 cam hasn't worked since 2.4.5 erik-lkml
2001-10-24 19:24 ` Johannes Erdfelt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox