Nothing here looks encouraging. Like I said, the datafab transport does a lot of trickery....
Honestly, I think your best bet is to get the windows driver disk out and take a look at what's on it. Matt On Fri, Feb 22, 2002 at 10:29:09PM -0500, Keith Adamson wrote: > Shit. Is any of this encouraging; I also get in > /proc/scsi/usb-storage-0/1; > > Host scsi1: usb-storage > Vendor: Digit@lway, Inc. > Product: Digit@lway Digital Audio Player > Serial Number: None > Protocol: Transparent SCSI > Transport: Datafab Bulk-Only > GUID: 273500010000000000000000 > Attached: 1 > > The MPIO MP3 player has internal memory plus a slot for a SmartMedia > card. BTW in Windows it looks like two file systems ... one for > internal memory and one for the SmartCard. You can only copy to/from > one at a time. I figure they are different LUN because I can do 'echo > "scsi add-single-device 1 0 0 1" > /proc/scsi/scsi' and get in > /var/log/messages; > > kernel: scsi singledevice 1 0 0 1 > kernel: Vendor: Digital Model: Digital Audio Pl Rev: 0100 > kernel: Type: Direct-Access ANSI SCSI revision: > 02 > > and in /proc/scsi/scsi; > > Host: scsi1 Channel: 00 Id: 00 Lun: 00 > Vendor: Digital Model: Digital Audio Pl Rev: 0100 > Type: Direct-Access ANSI SCSI revision: 02 > Host: scsi1 Channel: 00 Id: 00 Lun: 01 > Vendor: Digital Model: Digital Audio Pl Rev: 0100 > Type: Direct-Access ANSI SCSI revision: 02 > > However, maybe this isn't talking to the device either. The info with > the device isn't much help. It's a recent design which is very popular > in Japan. > > When I use "US_SC_SCSI, US_PR_BULK," in unusual_devs.h I get; > > kernel: hub.c: USB new device connect on bus1/2/1, assigned device > number 3 > kernel: usb.c: USB device 3 (vend/prod 0x2735/0x1) is not claimed by any > active driver. > kernel: Initializing USB Mass Storage driver... > kernel: usb.c: registered new driver usb-storage > kernel: usb-uhci.c: interrupt, status 2, frame# 1146 > kernel: usb-uhci.c: interrupt, status 3, frame# 1148 > kernel: scsi1 : SCSI emulation for USB Mass Storage devices > kernel: usb-uhci.c: interrupt, status 3, frame# 771 > kernel: scsi: device set offline - not ready or command retry failed > after bus reset: host 1 channel 0 id 0 lun 0 > kernel: USB Mass Storage support registered. > > When I use "US_SC_SCSI, US_PR_CB," in unusual_devs.h I get; > > kernel: hub.c: USB new device connect on bus1/2/1, assigned device > number 4 > kernel: usb.c: USB device 4 (vend/prod 0x2735/0x1) is not claimed by any > active driver. > kernel: Initializing USB Mass Storage driver... > kernel: usb.c: registered new driver usb-storage > kernel: scsi1 : SCSI emulation for USB Mass Storage devices > kernel: usb-uhci.c: interrupt, status 3, frame# 902 > kernel: usb-uhci.c: interrupt, status 3, frame# 907 > kernel: usb_control/bulk_msg: timeout > kernel: usb-uhci.c: interrupt, status 3, frame# 1826 > kernel: usb-uhci.c: interrupt, status 3, frame# 1831 > kernel: usb_control/bulk_msg: timeout > kernel: usb-uhci.c: interrupt, status 3, frame# 702 > kernel: usb-uhci.c: interrupt, status 3, frame# 707 > kernel: usb_control/bulk_msg: timeout > kernel: USB Mass Storage support registered. > > Any of this give you any ideas or should I just keep pounding away? > > Thanks, Keith > > > On Fri, 2002-02-22 at 21:12, Matthew Dharm wrote: > > Umm... not to burst your bubble, but US_PR_DATAFAB invokes a great deal of > > "command trickery"... so far, you haven't actually communicated with the > > device yet. > > > > Matt > > > > > > _______________________________________________ > [EMAIL PROTECTED] > To unsubscribe, use the last form field at: > https://lists.sourceforge.net/lists/listinfo/linux-usb-users -- Matthew Dharm Home: [EMAIL PROTECTED] Maintainer, Linux USB Mass Storage Driver Ye gods! I have feet??! -- Dust Puppy User Friendly, 12/4/1997
msg02718/pgp00000.pgp
Description: PGP signature
