[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: usb storage problems



Am Sonntag, 18. September 2005 12.32 schrieb Hendrik Sattler:
> > I continue to be stumped by USB storage devices in KDE...
>
> That's how I currently do this (Debian Etch with X and KDE from Sid):
> $ cat /proc/partitions
> [...]
>    8     0     256000 sda
>    8     1     255984 sda1

Thank you for this tip, Hendrik. I get: 

theo@tbox:~$ cat /proc/partitions
major minor  #blocks  name

   8     0    1048575 sda    (this cannot be correct)
   3     0    6297480 hda
   3     1     305203 hda1
   3     2    5992245 hda2

Only *10 minutes later* did sda1 show up:

major minor  #blocks  name

   8     0      31360 sda
   8     1      31280 sda1
   3     0    6297480 hda
   3     1     305203 hda1
   3     2    5992245 hda2


> $ pmount /dev/sda1

theo@tbox:~$ pmount -d /dev/sda1
resolved /dev/sda1 to device /dev/sda1
mount point to be used: /media/sda1
no iocharset given, current locale encoding is ISO-8859-15
Cleaning lock directory /var/lock/pmount/_dev_sda1
device_whitelist: checking /etc/pmount.allow...
device_whitlisted(): nothing matched, returning 0
find_sysfs_device: looking for sysfs directory for device 8:1
Fehler: konnte sysfs-Verzeichnis nicht erfragen

There is absolutely nothing in my folder /sys.

...
> Instead, you can also look at the dmesg output.

hub.c: new USB device 00:02.2-1, assigned address 2
usb.c: USB device 2 (vend/prod 0xd7d/0x240) is not claimed by any active 
driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi1 : SCSI emulation for USB Mass Storage devices
  Vendor:           Model: USB Card Reader   Rev: 1.05
  Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
Current sd00:00: sense key Not Ready
Additional sense indicates Medium not present
sda : block size assumed to be 512 bytes, disk size 1GB.
 sda: I/O error: dev 08:00, sector 0
 I/O error: dev 08:00, sector 0
ldm_validate_partition_table(): Disk read failed.
 I/O error: dev 08:00, sector 0
 unable to read partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
SCSI device sda: 62720 512-byte hdwr sectors (32 MB)
sda: Write Protect is off
 sda: sda1


> Or you become root and look at:
> sg_scan -i

/dev/sg0: scsi0 channel=0 id=0 lun=0 [em]
       LG     CD-ROM CRD-8322B  1.07 [rmb=1 cmdq=0 pqual=0 pdev=0x5]
/dev/sg1: scsi1 channel=0 id=0 lun=0 [em]
              USB Card Reader   1.05 [rmb=1 cmdq=0 pqual=0 pdev=0x0]

The card itself simply does not show up.

> sg_map -sd

/dev/sg0
/dev/sg1  /dev/sda

ditto.
...

Am Sonntag, 18. September 2005 11.11 schrieb David Pastern:
...
> > method to mount my camera, SD-cards, and external USB drive...
...
> My advice is to be running (as root):
>
> tail -n 50 /var/log/messages
>
> and then plug the usb device in.  It should show, and show the
> device ;-)

Thanks, David.

Could the uhci problems below be part of my problems?

Sep 18 09:50:58 tbox pci.agent[543]:      eepro100: already loaded
Sep 18 09:50:58 tbox pci.agent[543]:      e100: can't be loaded
Sep 18 09:50:59 tbox pci.agent[543]: missing kernel or user mode driver e100
Sep 18 09:50:59 tbox pci.agent[543]:      usb-uhci: blacklisted
Sep 18 09:50:59 tbox kernel: uhci.c: USB Universal Host Controller Interface 
driver v1.1
Sep 18 09:50:59 tbox pci.agent[543]:      uhci: can't be loaded
Sep 18 09:50:59 tbox pci.agent[543]: missing kernel or user mode driver uhci
Sep 18 09:51:03 tbox usb.agent[632]:      usbcore: already loaded

The rest of the output is similar to the dmesg output at the beginning of this 
mail.

Thanks also for the messages indicating that with the newest kernel my 
problems will be over. I live in hope! (I'm still using 2.4.20-xfs because 
I'm wary of replacing the kernel, having had problems with this in the past.)

Theo Schmidt



Reply to: