Hi Randy,

Yep, this is still broke. I took your suggestion and submitted a detailed 
FEEDBACK to SuSE (btw they now have a cool web page for feedback == 
http://www.suse.de/cgi-bin/feedback.cgi ) .

The nub of the prob seems to be that a /dev/sdx entry is never created. doing 
a fdisk -l NEVER shows an entry for the USB device
Thanks for the interest, I'll post updates as they occur.
PeterB

On Thursday 11 July 2002 11:16, Randy.Dunlap wrote:
> Hi,
>
> Is this still an open question, or did Tim's (or Tom's ?)
> email help you out on this?
>
> I tested more at home last night, where I have a better
> variety of USB storage devices, including CD-RW, hard disk,
> floppy, & CF reader.  These all work for me on Linux 2.4.18.
>
> And you read the USB Guide for storage devices, right?
>   at http://www.linux-usb.org/USB-guide/x498.html
> It tells you what kernel CONFIG options should be used
> for USB storage.
>
> This is where I got a clue for how to mount my CD-R/RW
> drive, when I had trouble mounting it.
> It says to use /dev/scd0 as the device name to mount.
> (Note:  the '0' may change, depending on other devices
> in your particular system config.)
>
> This 'mount' is what worked for me for a USB CD-R/RW drive:
> [root@midway mnt]# mount -t iso9660 /dev/scd1  /mnt/disk
>
> For other USB storage media types (not CD-R), device names
> are usually /dev/sdXn, with 'n' being optional, depending
> on whether the device has partitions, and 'X' being a drive
> instance.
>
> Here is the 'mount' command output from my USB CD-drive
> mounted, and then my USB hard drive mounted at the same
> mount point (not simultaneously ;) :
>
> /dev/scd1 on /mnt/disk type iso9660 (ro)
>
> /dev/sdb1 on /mnt/disk type vfat (rw)
>
> (more below)
>
> On Wed, 10 Jul 2002, Peter B Van Campen wrote:
> | Here are the msgs from /var/log/messages:
> |
> | Jul 10 13:14:55 linux kernel: hub.c: USB new device connect on bus1/1,
> | assigned device number 5
> | Jul 10 13:14:55 linux kernel: WARNING: USB Mass Storage data integrity
> | not assured
> | Jul 10 13:14:55 linux kernel: USB Mass Storage device found at 5
> | Jul 10 13:14:55 linux modprobe: modprobe: Can't locate module
> | block-major-11 Jul 10 13:14:56 linux last message repeated 15 times
> | Jul 10 13:14:56 linux /etc/hotplug/usb.agent[5030]: Can't ignore signal
> | CHLD, forcing to default.
>
> Hm, no messages from SCSI cdrom 'module', like:
> sr1: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
>
> Does anyone know what the 'sr1' here refers to?
> Does this have anything to do with '/dev/scd1' being the mount
> device in this instance?
>
> | This 128MB dev works correctly on M$XP.
>
> [I don't find this bit of info very useful.  Not to blast you
> or anyone in particular, but M$ USB driver developers
> probably have much more device documentation available to them
> than Linux USB device driver developers do.]
>
> | Now after previous tries to resolve this prob we have focused on the
> | "block-major-11' which we think is 'scsi cdrom' support module but we
> | think it is built in to the kernel, not loaded as a mod.  modprobe sr_mod
> | does not work  fdisk -l shows no entry for the device.
> |
> | file:/proc/scsi/usb-storage-0 contains :
> |   Host scsi1: usb-storage
> |        Vendor:
> |       Product:        USB Storage Device
> | Serial Number: 0AEC301000001A00
> |      Protocol: Transparent SCSI
> |     Transport: Bulk
> |          GUID: 0aec50100aec301000001a00
> |      Attached: Yes
> |
> | file:/proc/scsi/scsi has this:
> | Attached devices:
> | Host: scsi0 Channel: 00 Id: 00 Lun: 00
> |   Vendor: WDIGTL   Model: WDE9100          Rev: 1.50
> |   Type:   Direct-Access                    ANSI SCSI revision: 02
> | Host: scsi0 Channel: 00 Id: 08 Lun: 00
> |   Vendor: WDIGTL   Model: WDE9100          Rev: 1.50
> |   Type:   Direct-Access                    ANSI SCSI revision: 02
> |
> | The modules show up ok:
> |  USB-Storage                 48416   0
> |  USB-uhci                      21998   0       (unused)
> |  USB-core                      57184   1       (usb-storage usb-uhci)
>
> I'm curious about the modules listed above.  Did you type
> these in, or cut-and-paste the list?
> or is some distro modifying the module names?
>
> Cut-and-paste is preferred.  I'm guessing that you typed this
> list, since my list (2.4.18) shows up as:
>
> [rddunlap@midway tmp]$ lsmod
> Module                  Size  Used by
> usb-storage            22304   1
> usb-uhci               21664   0 (unused)
> usbcore                53888   1 [usb-storage usb-uhci]
>
> | hwinfo --usb yeilds :
>
> What/where is 'hwinfo'?
> Oh, OK, part of SuSE distro.
>
> | 03: USB 101.0: 10a00 Hub
> |   [Created at usb.100]
> |   Unique ID: B3Fu.9Oj4wbcMyNA
> |   Hardware Class: hub
> |   Model: "USB UHCI Root Hub"
> |   Device: "USB UHCI Root Hub"
> |   Serial ID: "d400"
> |   USB GUID: 00000000000000000000d400
> |   USB Device status: driver active ("hub")
> |   Speed: 1.5 Mbps
>
> Speed looks incorrect.
>
> | 04: USB 105.0: 10600 Disk
> |   [Created at usb.100]
> |   Unique ID: B3Fu.o9+kZpz6ig0
> |   Hardware Class: disk
> |   Model: "USB Storage Device"
> |   Vendor: u0aec "?"
> |   Device: 5010 "?"
> |   SubVendor: ""
> |   SubDevice: "USB Storage Device"
> |   Revision: "1.00"
> |   Serial ID: "0AEC301000001A00"
> |   USB GUID: 0aec50100aec301000001a00
> |   USB Device status: driver active ("usb-storage")
> |   Speed: 1.5 Mbps
>
> Speed is questionable.
>
> |   Attached to: #3 (Hub)
> |
> | 05: USB 201.0: 10a00 Hub
> |   [Created at usb.100]
> |   Unique ID: B3Fu.DUvD_7MFcGF
> |   Hardware Class: hub
> |   Model: "USB UHCI Root Hub"
> |   Device: "USB UHCI Root Hub"
> |   Serial ID: "d800"
> |   USB GUID: 00000000000000000000d800
> |   USB Device status: driver active ("hub")
> |   Speed: 1.5 Mbps
>
> Speed looks incorrect.
>
> | thanks again ....................... PeterB
> |
> | On Wednesday 10 July 2002 13:03, Randy.Dunlap wrote:
> | > On Wed, 10 Jul 2002, Peter B Van Campen wrote:
> | > | I have SuSE 8.0 kernel 2.4.18-64gb-SMP . This sys recognises
> | > | attachment of an USB 128 MB 'Pen Drive" Mass Storage device, but an
> | > | entry in /dev/sdx is never created, so the device cannot be mounted
> | > | or otherwise manipulated.
> | > |
> | > | I have seen several reports of similar problems but have NOT seen
> | > | anyone report solving the problem. Has anyone on the list have a USB
> | > | Mass Storage device working on kernel 2.4.18 ?
> | >
> | > Yes, definitely.  I would suspect a distro difference or a
> | > device-specific problem.
> | >
> | > Can you post the kernel log file contents from when you attach
> | > the USB storage device?



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
PC Mods, Computing goodies, cases & more
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to