Yep, this is apparently what is happening:

# JumpDrive Elite 256MB
[EMAIL PROTECTED] root]# sg_inq /dev/sg0
standard INQUIRY:
  PQual=0  Device_type=0  RMB=1  [ANSI_version=2]  version=0x02
  [AERC=0]  [TrmTsk=0]  NormACA=0  HiSUP=0  Resp_data_format=0
  SCCS=0  ACC=0  TGPS=0  3PC=0  Protect=0
  BQue=0  EncServ=0  MultiP=0  MChngr=0  [ACKREQQ=0]  Addr16=0
  [RelAdr=0]  WBus16=0  Sync=0  Linked=0  [TranDis=0]  CmdQue=0
    length=36 (0x24)   Peripheral device type: disk
 Vendor identification: Generic
 Product identification: STORAGE DEVICE
 Product revision level: 1.25

# JumpDrive Sport 512MB
[EMAIL PROTECTED] root]# sg_inq /dev/sg0
standard INQUIRY:
  PQual=0  Device_type=0  RMB=1  [ANSI_version=2]  version=0x02
  [AERC=0]  [TrmTsk=0]  NormACA=0  HiSUP=0  Resp_data_format=1
  SCCS=0  ACC=1  TGPS=1  3PC=0  Protect=1
  BQue=0  EncServ=1  MultiP=0  MChngr=1  [ACKREQQ=1]  Addr16=1
  [RelAdr=0]  WBus16=0  Sync=0  Linked=1  [TranDis=0]  CmdQue=0
    length=36 (0x24)   Peripheral device type: disk
 Vendor identification: LEXAR
 Product identification: JUMPDRIVE SPORT
 Product revision level: 2000
 Product serial number: x

Any idea why the heck the "Linked" bit (among others---I admit I have next
to no knowledge about SCSI, just trying to apply some "common sense" :-)
is not set for the two other jumpdrives?

Cheers!!
Spiros

> Hello!
>
> I have three JumpDrives and on two of these, usb-storage sets the SCSI
> vendor/model strings to "Generic / STORAGE DEVICE" with the result that
> updfstab fails to create the relevant /mnt/flash entries.  Of course,
> manually mounting the devices always worked fine.
>
> Actually, today I got my third JumpDrive and I'm happy to say that I just
> plugged it in and everything worked.  I'm running FC2 with kernel
> 2.6.6-1.435.2.3.
>
> Any idea why the usb-storage driver does not like the two other
> JumpDrives?  Quickly glancing the kernel source, it seems that this should
> be happening in fill_inquiry_response(), if the driver thinks the device
> is not connected.
>
> I've attached /proc/scsi/scsi and lspci -v outputs.  I'd be happy to
> provide any further info to resolve this.
>
> In the meantime, is there any "user-space" workaround for this, e.g., to
> force the SCSI drivers to (re)do the bus inquiries?  Any suggestions would
> be appreciated.
>
> Thanks!
> Spiros




-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to