LinuxQuestions.org - Portable USB enclosure not recognized

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Portable USB enclosure not recognized (https://www.linuxquestions.org/questions/slackware-14/portable-usb-enclosure-not-recognized-680939/)

Portable USB enclosure not recognized

Slackware 12.0, 2.6.21.5.
Seagate SATA drive, no-name generic powered USB enclosure.

Formatted NTFS right now, but had the same problem with a FAT32 format. Works fine in XP, including in VMware running on Slack. Problem exists on three different machines, albeit with the same kernel.

VFAT USB devices such as thumb drives, iPods and digital camera work fine, showing up as /dev/sdx.
No devices are being created in /dev with this enclosure.

dmesg output:

Code:

usb 1-4: new high speed USB device using ehci_hcd and address 8

usb 1-4: configuration #1 chosen from 1 choice

scsi4 : SCSI emulation for USB Mass Storage devices

usb-storage: device found at 8

usb-storage: waiting for device to settle before scanning

kobject_add failed for usb_storage with -EEXIST, don't try to register things wi

th the same name in the same directory.

 [<c03e86f7>] kobject_shadow_add+0x117/0x1a0

 [<c013fba4>] mod_sysfs_setup+0x24/0xb0

 [<c0141458>] sys_init_module+0x1648/0x1940

 [<c0102ae8>] syscall_call+0x7/0xb

 [<c0710000>] __mutex_lock_slowpath+0x40/0x90

 =======================

usb 1-4: reset high speed USB device using ehci_hcd and address 8

usb 1-4: device descriptor read/64, error -71

usb 1-4: device descriptor read/64, error -71

usb 1-4: reset high speed USB device using ehci_hcd and address 8

usb 1-4: device descriptor read/64, error -71

usb 1-4: device descriptor read/64, error -71

usb 1-4: reset high speed USB device using ehci_hcd and address 8

usb 1-4: device not accepting address 8, error -71

usb 1-4: reset high speed USB device using ehci_hcd and address 8

usb 1-4: device not accepting address 8, error -71

usb 1-4: USB disconnect, address 8

scsi 4:0:0:0: scsi: Device offlined - not ready after error recovery

usb-storage: device scan complete

usb 1-4: new high speed USB device using ehci_hcd and address 9

usb 1-4: device descriptor read/64, error -71

usb 1-4: device descriptor read/64, error -71

usb 1-4: new high speed USB device using ehci_hcd and address 10

usb 1-4: device descriptor read/64, error -71

usb 1-4: device descriptor read/64, error -71

usb 1-4: new high speed USB device using ehci_hcd and address 11

usb 1-4: device not accepting address 11, error -71

usb 1-4: new high speed USB device using ehci_hcd and address 12

usb 1-4: device not accepting address 12, error -71

The only Google results for the kobject error seemed to be from Slack users. Any ideas?

The kobject error likely means that you are using the huge-smp (or huge non-smp) kernel instead of the generic one. Although I would recommend using the generic-smp kernel, it probably is not affecting this specific problem. Nonetheless, from CHANGES_AND_HINTS.TXT:

Code:

Use one of the provided generic kernels for daily use.  Do not report

  bugs until/unless you have reproduced them using one of the stock 

  generic kernels.  You will need to create an initrd in order to boot

  the generic kernels - see /boot/README.initrd for instructions.



As stated earlier, it is recommended that you use one of the generic kernels

  rather than the huge kernels; the huge kernels are primarily intended as 

  "installer" and "emergency" kernels in case you forget to make an initrd.

  For most systems, you should use the generic SMP kernel if it will run, 

  even if your system is not SMP-capable.  Some newer hardware needs the 

  local APIC enabled in the SMP kernel, and theoretically there should not be

  a performance penalty with using the SMP-capable kernel on a uniprocessor 

  machine, as the SMP kernel tests for this and makes necessary adjustments.

  Furthermore, the kernel sources shipped with Slackware are configured for

  SMP usage, so you won't have to modify those to build external modules

  (such as NVidia or ATI proprietary drivers) if you use the SMP kernel.



  If you decide to use one of the non-SMP kernels, you will need to follow the

  instructions in /extra/linux-2.6.24.5-nosmp-sdk/README.TXT to modify your

  kernel sources for non-SMP usage.  Note that this only applies if you are

  using the Slackware-provided non-SMP kernel - if you build a custom kernel,

  the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the

  correct kernel source so long as you don't (re)move it.



  If you decide to use one of the huge kernels anyway, you will encounter 

  errors like this:

    kobject_add failed for uhci_hcd with -EEXIST, don't try to register

  These occur because the respective drivers are compiled statically into the

  huge kernels but udev tries to load them anyway.  These errors should be safe

  to ignore, but if you really don't want them to appear, you can blacklist the

  modules that try to load in /etc/modprobe.d/blacklist.  However, make sure you

  remove them from the blacklist if you ever decide to use the (recommended)

  generic kernels.

I'm not sure if this will help, but see this page for some possible reasons/solutions (read the whole page).

Thanks for the kobject error explanation. Indeed, I'm using the huge kernel, out of laziness.

AS for the USB drive, seems as though everything from bad cables to kernels were called out in that thread. Looks as though I have some testing to do.

I very much appreciate the reply.

Also out of curiosity, try removing the OHCI portion of the kernel. There was a bug reported that said that certain devices caused conflicts between the two drivers.

Good stuff, folks. Thank you. I have another Slack box running a 2.4.33.3 kernel (I know, more laziness) and got some encouraging messages back when I plugged in the device.

Code:

Initializing USB Mass Storage driver...

usb.c: registered new driver usb-storage

usb_control/bulk_msg: timeout

scsi1 : SCSI emulation for USB Mass Storage devices

  Vendor: ST310003  Model: 40AS              Rev:    

  Type:  Direct-Access                      ANSI SCSI revision: 02

Attached scsi disk sda at scsi1, channel 0, id 0, lun 0

SCSI device sda: 1953525168 512-byte hdwr sectors (1000205 MB)

 sda: sda1

WARNING: USB Mass Storage data integrity not assured

USB Mass Storage device found at 2

USB Mass Storage support registered.

usb.c: USB disconnect on device 00:03.3-4 address 2

ntfs-3g and fuse are not installed on the box, so I can't test fully, but you've given me the info I need to make it work. I'll post back with, assumedly, a successful conclusion.

OK, booted with the generic kernel and used the EHCI module.
Things look better in dmesg, but no device is being created.

Code:

usb 4-1: new high speed USB device using ehci_hcd and address 2

usb 4-1: configuration #1 chosen from 1 choice

Initializing USB Mass Storage driver...

scsi0 : SCSI emulation for USB Mass Storage devices

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usb-storage: device found at 2

usb-storage: waiting for device to settle before scanning

usb 4-1: reset high speed USB device using ehci_hcd and address 2

usb 4-1: device descriptor read/64, error -71

usb 4-1: device descriptor read/64, error -71

usb 4-1: reset high speed USB device using ehci_hcd and address 2

usb 4-1: device descriptor read/64, error -71

usb 4-1: device descriptor read/64, error -71

usb 4-1: reset high speed USB device using ehci_hcd and address 2

usb 4-1: device not accepting address 2, error -71

usb 4-1: reset high speed USB device using ehci_hcd and address 2

usb 4-1: device not accepting address 2, error -71

usb 4-1: USB disconnect, address 2

scsi 0:0:0:0: scsi: Device offlined - not ready after error recovery

usb-storage: device scan complete

usb 4-1: new high speed USB device using ehci_hcd and address 3

usb 4-1: device descriptor read/64, error -71

usb 4-1: device descriptor read/64, error -71

Ideas, please?