hi,
having problems with USB storage.
here is the modules loaded
sd_mod 10956 0 (unused)
scsi_mod 84200 4 [sg scsimon usb-storage sd_mod]
the device is created paritially.
/dev/scsi/host0/bus0/target0/lun0/
but no part1
when I loaded the sg (scsi generic) module as suggested on a couple of web
sites a
/dev/scsi/host0/bus0/target0/lun0/generic file was created. still couldn't
mount this though.
in proc I get
/proc/scsi/usb-storage-0
Host scsi0: usb-storage
Vendor: Unknown
Product: USB Mass Storage Device
Serial Number: None
Protocol: Transparent SCSI
Transport: Bulk
GUID: 0c4510600000000000000000
Attached: Yes
/proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: USB Model: STORAGE Rev: 1.1
Type: Direct-Access ANSI SCSI revision: 02
I've enabled debuging in the kernel for usb-storage and I get...
Feb 7 16:27:11 coastlinux syslog.info klogd: usb.c: registered new driver
usbdevfs
Feb 7 16:27:11 coastlinux syslog.info klogd: usb.c: registered new driver
hub
Feb 7 16:27:11 coastlinux syslog.info klogd: usb.c: registered new driver
hiddev
Feb 7 16:27:11 coastlinux syslog.info klogd: usb.c: registered new driver
hid
Feb 7 16:27:11 coastlinux syslog.info klogd: hid-core.c: v1.8.1 Andreas
Gal, Vojtech Pavlik <[EMAIL PROTECTED]>
Feb 7 16:27:11 coastlinux syslog.info klogd: hid-core.c: USB HID support
drivers
Feb 7 16:27:11 coastlinux syslog.info klogd: mice: PS/2 mouse device common
for all mice
Feb 7 16:27:11 coastlinux syslog.info klogd: c: $Revision: 1.275 $ time
02:03:20 Feb 10 2004
Feb 7 16:27:11 coastlinux syslog.info klogd: usb-uhci.c: High bandwidth
mode enabled
Feb 7 16:27:11 coastlinux syslog.info klogd: PCI: Found IRQ 11 for device
00:1f.2
Feb 7 16:27:11 coastlinux syslog.debug klogd: PCI: Setting latency timer of
device 00:1f.2 to 64
Feb 7 16:27:11 coastlinux syslog.info klogd: usb-uhci.c: USB UHCI at I/O
0x1820, IRQ 11
Feb 7 16:27:11 coastlinux syslog.warn klogd: usb-uhci.c: Detected 2 ports
Feb 7 16:27:11 coastlinux syslog.info klogd: usb.c: new USB bus registered,
assigned bus number 1
Feb 7 16:27:11 coastlinux syslog.info klogd: hub.c: USB hub found
Feb 7 16:27:11 coastlinux syslog.info klogd: hub.c: 2 ports detected
Feb 7 16:27:11 coastlinux syslog.info klogd: usb-uhci.c: v1.275:USB
Universal Host Controller Interface driver
Feb 7 16:27:11 coastlinux syslog.info klogd: SCSI subsystem driver
Revision: 1.00
Feb 7 16:27:11 coastlinux syslog.info klogd: Initializing USB Mass Storage
driver...
Feb 7 16:27:11 coastlinux syslog.info klogd: usb.c: registered new driver
usb-storage
Feb 7 16:27:11 coastlinux syslog.info klogd: USB Mass Storage support
registered.
Feb 7 16:27:11 coastlinux syslog.info klogd: usb.c: registered new driver
usblp
Feb 7 16:27:11 coastlinux syslog.info klogd: printer.c: v0.11: USB Printer
Device Class driver
Feb 7 16:27:11 coastlinux syslog.notice klogd: udf: registering filesystem
Feb 7 16:27:11 coastlinux syslog.info klogd: inserting floppy driver for
2.4.24
Feb 7 16:27:11 coastlinux syslog.info klogd: Floppy drive(s): fd0 is 1.44M
Feb 7 16:27:11 coastlinux syslog.info klogd: FDC 0 is a National
Semiconductor PC87306
Feb 7 16:27:11 coastlinux syslog.warn klogd: hdc: attached ide-cdrom
driver.
Feb 7 16:27:11 coastlinux syslog.info klogd: hdc: ATAPI 32X CD-ROM drive,
128kB Cache
Feb 7 16:27:11 coastlinux syslog.info klogd: Uniform CD-ROM driver
Revision: 3.12
Feb 7 16:27:11 coastlinux syslog.info klogd: Journalled Block Device driver
loaded
Feb 7 16:27:11 coastlinux syslog.info klogd: hub.c: new USB device
00:1f.2-1, assigned address 2
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: act_altsettting
is 0
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: id_index
calculated to be: 103
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Array length
appears to be: 105
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: USB Mass Storage
device detected
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Endpoints: In:
0xd2f296e0 Out: 0xd2f296f4 Int: 0x00000000 (Period 0)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: New GUID
0c4510600000000000000000
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: GetMaxLUN
command result is 1, data is 0
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Transport: Bulk
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Protocol:
Transparent SCSI
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.info klogd: scsi0 : SCSI emulation for USB
Mass Storage devices
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: queuecommand()
called
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
awakened.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Command INQUIRY
(6 bytes)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: 12 00 00 00 ff
00 00 00 b5 01 00 00
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bulk command S
0x43425355 T 0x1 Trg 0 LUN 0 L 255 F 128 CL 6
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bulk command
transfer result=0
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage:
usb_stor_transfer_partial(): xfer 255 bytes
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage:
usb_stor_bulk_msg() returned 0 xferred 35/255
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bulk data
transfer result 0x1
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Attempting to
get CSW...
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bulk status
result = 0
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bulk status Sig
0x53425355 T 0x1 R 219 Stat 0x0
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: scsi cmd done,
result=0x0
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.warn klogd: Vendor: USB Model:
STORAGE Rev: 1.1
Feb 7 16:27:11 coastlinux syslog.warn klogd: Type: Direct-Access
ANSI SCSI revision: 02
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: queuecommand()
called
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
awakened.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bad LUN (0/1)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: queuecommand()
called
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
awakened.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bad target
number (1/0)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: queuecommand()
called
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
awakened.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bad target
number (2/0)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: queuecommand()
called
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
awakened.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bad target
number (3/0)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: queuecommand()
called
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
awakened.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bad target
number (4/0)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: queuecommand()
called
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
awakened.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bad target
number (5/0)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: queuecommand()
called
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
awakened.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bad target
number (6/0)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: queuecommand()
called
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
awakened.
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: Bad target
number (7/0)
Feb 7 16:27:11 coastlinux syslog.debug klogd: usb-storage: *** thread
sleeping.
Feb 7 16:27:11 coastlinux syslog.warn klogd: Unable to get major 65 for
SCSI disk
Feb 7 16:27:11 coastlinux syslog.debug klogd: WARNING: USB Mass Storage
data integrity not assured
Feb 7 16:27:11 coastlinux syslog.debug klogd: USB Mass Storage device found
at 2
So it seems to be falling over at above. Something to do with a Bad LUN
(0/1)
On my Mandrake 9.2 the device works correctly, and it creates a
/dev/scsi/host0/bus0/target0/lun0/part1. Supermount is on Mandrake as well
so I don't think thats causing a problem. It isn't even creating the part1
on thinstation.
I've tried adding in scsimon module but that makes no difference. I've
tried re-ordering the modules, and loading them manually. Still no
difference.
So, I've exhaused all my ideas & searched on the net for solutions. Help
:o)
Cheers
Miles
-----Original Message-----
From: Paul Whittaker [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 3 February 2004 02:11 p.m.
To: Thinstation-Developer (E-mail)
Subject: Re: [Thinstation-developer] RE: [Thinstation-general] USB
storage devices
Mike Eriksen wrote:
> Wouldn't it be safer just to sym link /dev/scsi/host0/bus0/target0/lun0
> and /dev/sda1? /dev/sda1 may appear in many places.
/dev/sda* simply refers to the first detected SCSI device.
/dev/scsi/host0/bus0/target0/lun0 is a hardware address pathname that will
often be the same thing as /dev/sda. Unless you have a particular reason
to tie down your references to a specific hardware address, using the
"floating" device name (/dev/sda*) is usually better.
Don't link /dev/sda1 to
/dev/scsi/host0/bus0/target0/lun0, as the latter isn't a partition, it's an
entire device. /dev/scsi/host0/bus0/target0/lun0/part1 is the equivalent
of /dev/sda1.
> If I read Robbo's replies correctly, he actually didn't change anything in
> TS-2.0b3? In that case I can report I do *not* see anything appearing in
> /dev/scsi once I plug my keyring in. It works well as sda1 on the same pc
> if I boot the pc on the HD with Red Hat 9 (TS is booting from CD).
Your USB key device won't be autodetected when you insert it. You need
hotplug for that (which RH9 has).
If I recall correctly, to detect the key device you must load the
usb-storage module *after* the device is plugged in. It only probes the
"SCSI bus" at module load-time. The sd_mod module is robust enough to
create and remove partition devices on the fly, though, so the device can
be unplugged and replugged *after first detection* (filesystem mounting
issues notwithstanding).
Linux hotplug basically maps USB and PCI vendor and product identifiers to
Linux modules, and thereby insertion/removal events to insmod/rmmod events.
At the moment I'm still weighing up the cost-benefit of this WRT
embedded environments. I may integrate it into DIET-PC.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Thinstation-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/thinstation-developer
==================================================
Attention:
The information contained in this message and/or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by person or entities other than the intended recipient
is prohibited. If you receive this in error, please contact the sender and delete the
material from your system and destroy any copies.
===================================================
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users