Via Labs USB 3.0 Hub - USB 3.0 Device Not Recognized in Slackware 13.1

Hi All,

I am trying to connect some USB 3.0 HDD's up to a Via Labs USB 3.0 Hub. When I type 'lsusb', it only lists the hub and not the devices. If I plug in a USB 2.0 device to the hub, it can be recognized. If I plug the USB 3.0 device directly into the system, it is also recognized.

In further investigating, I typed 'lsusb -v' and found that the USB 3.0 part of the hub has an error - under where the Hub Descriptor information is supposed to be, it says "** UNRECOGNIZED: 06 30 00 00 02 00 can't get hub descriptor: Broken Pipe"

So that explains why the drive can't be recognized. My question is: Is this a Linux problem or a Via Labs problem? I am running Slackware 13.1.  BTW - The same hub works fine under Windows.

Is there somewhere on the system I can make Linux recognize this properly?

Thanks and best regards,
Equinn
LVL 1
Elena QuinnAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TobiasHolmCommented:
Hi!

Have you tried an external powered USB-hub?

If your present USB-hub already have external power, have you tried another USB-hub model?

Regards, Tobias
0
Elena QuinnAuthor Commented:
Hi Tobias,

The hub is powered.  Also, I tried to go out and get a couple of other hubs (Bytecc & Buffalo) to try, but it turned out both were based on the same VIA chipset, so I'm back to square one.

Thanks,
Elena Quinn
0
Elena QuinnAuthor Commented:
I thought it might help if I posted the actual output from 'lsusb -v':

This is from the USB 2.0 side of the hub:

Bus 006 Device 003: ID 2109:3431 Via Labs USB 2.0 Hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x2109 Via Labs
  idProduct          0x3431 USB 2.0 Hub
  bcdDevice            2.74
  iManufacturer           0 
  iProduct                1 USB2.0 Hub
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              12
Hub Descriptor:
  bLength               9
  bDescriptorType      41
  nNbrPorts             4
  wHubCharacteristic 0x00e9
    Per-port power switching
    Per-port overcurrent protection
    TT think time 32 FS bits
    Port indicators
  bPwrOn2PwrGood       50 * 2 milli seconds
  bHubContrCurrent    100 milli Ampere
  DeviceRemovable    0x00
  PortPwrCtrlMask    0xff
 Hub Port Status:
   Port 1: 0000.0100 power
   Port 2: 0000.0100 power
   Port 3: 0000.0100 power
   Port 4: 0000.0100 power
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         0 Full speed (or root) hub
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

Open in new window


And this is from the USB 3.0 side.  The error is at the bottom::

Bus 006 Device 002: ID 2109:0810 Via Labs 4 Port USB 3.0 Hub
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         3 
  bMaxPacketSize0         9
  idVendor           0x2109 Via Labs
  idProduct          0x0810 4 Port USB 3.0 Hub
  bcdDevice            3.74
  iManufacturer           1 VIA Labs, Inc.
  iProduct                2 4-Port USB 3.0 Hub
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           31
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes           19
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Feedback
        wMaxPacketSize     0x0002  1x 2 bytes
        bInterval              16
        ** UNRECOGNIZED:  06 30 00 00 02 00
Device Status:     0x0001
  Self Powered

Open in new window


Hope that helps.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

TobiasHolmCommented:
USB 3.0 support are included from the 2.6.31 Linux kernel, so it should be included in Slackware 13.1.

A quick test can be to download an Ubuntu CD and boot your computer into this, then test the HUB/drives. If it works in Ubuntu 10.10 it can be your kernel that needs an upgrade. It can also be the BIOS in your motherboard that needs an upgrade.

Also see this post for some more USB 3.0 troubleshooting tips: http://askubuntu.com/questions/24556/why-wont-usb-3-0-external-hard-drive-run-at-usb-3-0-speeds

Regards, Tobias
0
Duncan RoeSoftware DeveloperCommented:
I too use Slackware 13.1. make xconfig shows the driver xHCI HCD (USB 3.0) support (EXPERIMENTAL) (USB_XHCI_HCD) is disabled. You can confirm this for your kernel by the commands below:
21:59:57$ zcat /proc/config.gz |grep USB_XHCI_HCD
# CONFIG_USB_XHCI_HCD is not set
22:00:10$ 

Open in new window

If you see the above, you need to enable the driver. In make xconfig. ensure that under General setup, Prompt for development and/or incomplete code/drivers is ticked (mine is, but maybe I did that - I usually do). Now under Device Drivers/USB support configure xHCI HCD (USB 3.0) support (EXPERIMENTAL) (USB_XHCI_HCD) to compile as a module (large dot rather than a tick) (this saves the need to build a new kernel). Save the new config and exit. Now issue make modules followed by (as root) make modules_install. You may like to next edit /etc/rc.d/rc.modules to always load xhci-hcd
0
Duncan RoeSoftware DeveloperCommented:
Actually I see I forgot to upgrade the kernel from Slackware 13.0. Possibly you do have the driver then, but the test above will tell you for sure.
0
Elena QuinnAuthor Commented:
@duncan,

Thanks for your reply.  Here is what was returned from the zcat command:

CONFIG_USB_XHCI_HCD=y
#CONFIG_USB_XHCI_HCD_DEBUGGING is not set

Open in new window


I assume that means the driver is enabled.  I think it is enabled, though because the system can recognize USB 3.0 devices plugged directly into the expansion card.  It just can't recognize them if they are plugged into the hub (which is plugged into the expansion card).

BTW - how do I launch 'make config' ?  I tried typing it at the prompt, but it gave me an error:

make: *** No rule to make target 'xconfig'. Stop.

Open in new window


Should I try to update the kernel to the latest stable version?  If so, can you point me to a "Kernel Updating for Dummies" version.  I am very new at Linux and have definitely never done that before.
0
Duncan RoeSoftware DeveloperCommented:
Yes you have the driver enabled. lsusb should confirm that it is loaded.
make xconfig has to be run from the top-level Linux source directory, but we're not there yet.
We need to establish which driver handles the hub when it's first plugged in and which driver handles devices plugged in to it subsequently. First make sure that USB messages are being logged. Insert a device, wait a few seconds, then remove it. cd /var/log and verify that one of the log files has just been written to (e.g. with ls -ltr). tail that file to verify you see USB activity, something like:
Apr 12 08:17:06 dimstar kernel: usb 1-5: new high speed USB device using ehci_hcd and address 3
Apr 12 08:17:06 dimstar kernel: usb 1-5: New USB device found, idVendor=0951, idProduct=1624
Apr 12 08:17:06 dimstar kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 12 08:17:06 dimstar kernel: usb 1-5: Product: DataTraveler G2
Apr 12 08:17:06 dimstar kernel: usb 1-5: Manufacturer: Kingston
Apr 12 08:17:06 dimstar kernel: usb 1-5: SerialNumber: 0013728A7896BA71761E00F5
Apr 12 08:17:06 dimstar kernel: usb 1-5: configuration #1 chosen from 1 choice
Apr 12 08:17:06 dimstar kernel: scsi8 : SCSI emulation for USB Mass Storage devices
Apr 12 08:17:06 dimstar kernel: usb-storage: device found at 3
Apr 12 08:17:06 dimstar kernel: usb-storage: waiting for device to settle before scanning
Apr 12 08:17:11 dimstar kernel: scsi 8:0:0:0: Direct-Access     Kingston DataTraveler G2  PMAP PQ: 0 ANSI: 0 CCS
Apr 12 08:17:11 dimstar kernel: sd 8:0:0:0: Attached scsi generic sg5 type 0
Apr 12 08:17:11 dimstar kernel: usb-storage: device scan complete
Apr 12 08:17:13 dimstar kernel: sd 8:0:0:0: [sdb] 15646720 512-byte logical blocks: (8.01 GB/7.46 GiB)
Apr 12 08:17:13 dimstar kernel: sd 8:0:0:0: [sdb] Write Protect is off
Apr 12 08:17:13 dimstar kernel: sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
Apr 12 08:17:13 dimstar kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Apr 12 08:17:13 dimstar kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Apr 12 08:17:13 dimstar kernel:  sdb: sdb1
Apr 12 08:17:13 dimstar kernel: sd 8:0:0:0: [sdb] Assuming drive cache: write through
Apr 12 08:17:13 dimstar kernel: sd 8:0:0:0: [sdb] Attached SCSI removable disk
Apr 12 08:17:42 dimstar kernel: usb 1-5: USB disconnect, address 3

Open in new window

Note using ehci_hcd - that tells us it's the USB2 driver for fast devices. Post what you get when you try:
1. Insert USB3 device directly
2. Insert USB3 Hub
3. Insert USB3 device into USB3 Hub

If you didn't see the messages in any file in /var/log, then you need to configure log_debug in /etc/syslog.conf I have:
# Everything is logged here.
*.debug                                         -/var/log/debug

Open in new window

If we can establish that xhci_hcd is being used, then it will only help to upgrade the kernel if the driver has been improved. Please post the output from uname -r so I can do a comparison.
0
Elena QuinnAuthor Commented:
Hi Duncan,

Thank you for your help.

OK - Here is the output of the message file:

This is when the USB 3.0 HDD is plugged directly into the expansion card:

Apr 12 09:46:39 darkstar kernel: usb 6-2: new SuperSpeed USB device using xhci_hcd and address 2
Apr 12 09:46:39 darkstar kernel: usb 6-2: New USB device found, idVendor=0480, idProduct=a006
Apr 12 09:46:39 darkstar kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 12 09:46:39 darkstar kernel: usb 6-2: Product: External USB 3.0
Apr 12 09:46:39 darkstar kernel: usb 6-2: Manufacturer: Toshiba
Apr 12 09:46:39 darkstar kernel: usb 6-2: SerialNumber: 2011030800001
Apr 12 09:46:39 darkstar kernel: scsi8 : usb-storage 6-2:1.0
Apr 12 09:46:44 darkstar kernel: scsi 8:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 0001 PQ: 0 ANSI: 6
Apr 12 09:46:44 darkstar kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Apr 12 09:46:44 darkstar kernel: sd 8:0:0:0: [sdc] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
Apr 12 09:46:44 darkstar kernel: sd 8:0:0:0: [sdc] Write Protect is off
Apr 12 09:46:44 darkstar kernel:  sdc: unknown partition table
Apr 12 09:46:44 darkstar kernel: sd 8:0:0:0: [sdc] Attached SCSI disk

Open in new window


And this is when the drive is unplugged:

Apr 12 09:47:09 darkstar kernel: usb 6-2: USB disconnect, address 2

Open in new window


And this is when the hub is plugged into the expansion card:

Apr 12 09:47:38 darkstar kernel: usb 6-2: new SuperSpeed USB device using xhci_hcd and address 2
Apr 12 09:47:38 darkstar kernel: usb 6-2: New USB device found, idVendor=2109, idProduct=0810
Apr 12 09:47:38 darkstar kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 12 09:47:38 darkstar kernel: usb 6-2: Product: 4-Port USB 3.0 Hub
Apr 12 09:47:38 darkstar kernel: usb 6-2: Manufacturer: VIA Labs, Inc.
Apr 12 09:47:38 darkstar kernel: hub 6-2:1.0: USB hub found
Apr 12 09:47:38 darkstar kernel: usb 6-4: new high speed USB device using xhci_hcd and address 0
Apr 12 09:47:38 darkstar kernel: usb 6-4: New USB device found, idVendor=2109, idProduct=3431
Apr 12 09:47:38 darkstar kernel: usb 6-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Apr 12 09:47:38 darkstar kernel: usb 6-4: Product: USB2.0 Hub
Apr 12 09:47:38 darkstar kernel: hub 6-4:1.0: USB hub found
Apr 12 09:47:38 darkstar kernel: hub 6-4:1.0: 4 ports detected

Open in new window


Nothing at all happens when the drive is plugged into the hub!

And here is when the hub is unplugged:

Apr 12 09:50:01 darkstar kernel: usb 6-4: USB disconnect, address 3
Apr 12 09:50:01 darkstar kernel: usb 6-2: USB disconnect, address 2

Open in new window


I also checked the system log, and it has some interesting tid-bits, I think.  When the hub is plugged in:

Apr 12 09:47:38 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep
Apr 12 09:47:38 darkstar last message repeated 2 times
Apr 12 09:47:38 darkstar kernel: usb 6-2: ep 0x81 - rounding interval to 32768 microframes
Apr 12 09:47:38 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: Stalled endpoint
Apr 12 09:47:38 darkstar last message repeated 2 times
Apr 12 09:47:38 darkstar kernel: hub 6-2:1.0: config failed, can't read hub descriptor (err -22)
Apr 12 09:47:38 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep
Apr 12 09:47:38 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep
Apr 12 09:47:38 darkstar kernel: usb 6-4: ep 0x81 - rounding interval to 2048 microframes
Apr 12 09:47:38 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep

Open in new window


The output from uname -r:

2.6.33.4-smp

Open in new window


All the best,
Elena

0
Duncan RoeSoftware DeveloperCommented:
Because they all have the same time stamp, what we need here is to see all the messages in the same log file. That's what *.debug -/var/log/debug does. It logs everything debug priority and higher. The minus sign before the file name tells syslogd not to sync on every message (which it would do otherwise). Specify a different name if you already have /var/log/debug. After you edit /etc/syslog.conf, tell syslogd to re-read it by e.g. pkill -SIGHUP syslogd
At a guess I would say that the hub may not be fully compliant with the USB3 standard. Did you plug your USB3 drive into the hub or your USB2 drive?
When you purchased the hub, did it come with a Windows driver?
0
Elena QuinnAuthor Commented:
Hi Duncan,

I changed the syslog.conf file as you suggested.  However, I noted that the '-' was already there for both messages and syslog.

Contents of syslog.conf after I changed it:

# /etc/syslog.conf
# For info about the format of this file, see "man syslog.conf"
# and /usr/doc/sysklogd/README.linux.  Note the '-' prefixing some
# of these entries;  this omits syncing the file after every logging.
# In the event of a crash, some log information might be lost, so
# if this is a concern to you then you might want to remove the '-'.
# Be advised this will cause a performation loss if you're using
# programs that do heavy logging.

# Uncomment this to see kernel messages on the console.
#kern.*							/dev/console

# Log anything 'info' or higher, but lower than 'warn'.
# Exclude authpriv, cron, mail, and news.  These are logged elsewhere.
*.info;*.!warn;\
	authpriv.none;cron.none;mail.none;news.none	-/var/log/messages

# Log anything 'warn' or higher.
# Exclude authpriv, cron, mail, and news.  These are logged elsewhere.
*.warn;\
	authpriv.none;cron.none;mail.none;news.none	-/var/log/syslog

# Debugging information is logged here.
*.=debug						-/var/log/debug2

# Private authentication message logging:
authpriv.*						-/var/log/secure

# Cron related logs:
cron.*							-/var/log/cron

# Mail related logs:
mail.*							-/var/log/maillog

# Emergency level messages go to all users:
*.emerg							*

# This log is for news and uucp errors:
uucp,news.crit						-/var/log/spooler

# Uncomment these if you'd like INN to keep logs on everything.
# You won't need this if you don't run INN (the InterNetNews daemon).
#news.=crit					-/var/log/news/news.crit
#news.=err					-/var/log/news/news.err
#news.notice					-/var/log/news/news.notice

Open in new window


The debug2 file really didn't show much, just one line when I plugged in the HDD to the expansion card.  And one line when I plugged in the hub.

Apr 13 03:19:27 darkstar kernel: sd 9:0:0:0: [sdb] Mode Sense: 23 00 00 00
Apr 13 03:24:48 darkstar kernel: sd 10:0:0:0: [sdb] Mode Sense: 00 00 00 00

Open in new window


I plugged in the USB 3.0 drive to the hub.  If I plug in a USB 2.0 drive to the hub , it is recognized, but I assume that's because it's using the USB 2.0 side of the hub at that point.

The hub I'm using is one we had made for us by our ODM, but the two others that I bought via retail with the same chipset (Bytecc and Buffalo), both came with Windows drivers.  However, the drivers were not necessary to get the hubs to work on Windows.  Once the driver for the expansion card was installed on Windows, everything worked OK from there.

I am also having our ODM contact VIA to see if they can fix it on their side.  And, I am going to attempt to update to the latest kernel, just for grins.  I'm taking the shotgun approach.
0
Duncan RoeSoftware DeveloperCommented:
You didn't do it right! All you've done is rename debug to debug2. I meant for you to leave the debug line alone and add
*.debug                                       -/var/log/debug2

Open in new window

The minus sign is just for efficiency. The effect of the equals sign in =debug is that you get debug messages only. Without the equals sign, you would get everything from debug up.
0
Duncan RoeSoftware DeveloperCommented:
I asked about Windows drivers because I suspected that perhaps they circumvent some standards non-compliance or perhaps Windows itself does that. On the other hand, the Linux driver is experimental, and may not be perfect (yet :)
0
Duncan RoeSoftware DeveloperCommented:
I don't know what's going on, but I can't connect to any sites for kernel source this morning. Have to leave it for now ... good luck
0
Elena QuinnAuthor Commented:
Duncan,

Thanks for looking.  I did some digging yesterday, just looking at the kernel.org changelogs and didn't find anything specific to this issue, but the driver has been updated.  So now I am attempting to update the kernel to 2.6.38.2.  It hasn't been easy for me, since I've never done it before.  I've started over 3 times.  That's one of the downfalls in Newbieville, I guess.

Anyway, before my last attempt, I got the debug file to work and here is what was in there.  


Apr 13 08:45:27 darkstar syslogd 1.4.1: restart.

Open in new window



8:46:02 - Plugged in the USB 3.0 HDD to the system expansion card

Apr 13 08:46:02 darkstar kernel: usb 6-2: new SuperSpeed USB device using xhci_hcd and address 2
Apr 13 08:46:02 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep
Apr 13 08:46:02 darkstar last message repeated 3 times
Apr 13 08:46:02 darkstar kernel: usb 6-2: New USB device found, idVendor=0480, idProduct=a006
Apr 13 08:46:02 darkstar kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 13 08:46:02 darkstar kernel: usb 6-2: Product: External USB 3.0
Apr 13 08:46:02 darkstar kernel: usb 6-2: Manufacturer: Toshiba
Apr 13 08:46:02 darkstar kernel: usb 6-2: SerialNumber: 2011030800001
Apr 13 08:46:02 darkstar kernel: scsi6 : usb-storage 6-2:1.0
Apr 13 08:46:07 darkstar kernel: scsi 6:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 0001 PQ: 0 ANSI: 6
Apr 13 08:46:07 darkstar kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
Apr 13 08:46:07 darkstar kernel: sd 6:0:0:0: [sdb] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
Apr 13 08:46:07 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: Stalled endpoint
Apr 13 08:46:07 darkstar kernel: sd 6:0:0:0: [sdb] Write Protect is off
Apr 13 08:46:07 darkstar kernel: sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
Apr 13 08:46:07 darkstar kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 13 08:46:07 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: Stalled endpoint
Apr 13 08:46:07 darkstar kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 13 08:46:07 darkstar kernel:  sdb: unknown partition table
Apr 13 08:46:07 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: Stalled endpoint
Apr 13 08:46:07 darkstar kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 13 08:46:07 darkstar kernel: sd 6:0:0:0: [sdb] Attached SCSI disk

Open in new window


8:46:45 - Unplug the drive

Apr 13 08:46:45 darkstar kernel: usb 6-2: USB disconnect, address 2

Open in new window


8:48:25 - Plug in the hub

Apr 13 08:47:01 darkstar crond[2321]: FILE /var/spool/cron/crontabs/root USER root PID 2688 /usr/bin/run-parts /etc/cron.hourly 1> /dev/null 
Apr 13 08:48:25 darkstar kernel: usb 6-4: new high speed USB device using xhci_hcd and address 0
Apr 13 08:48:25 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep
Apr 13 08:48:25 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep
Apr 13 08:48:25 darkstar kernel: usb 6-4: New USB device found, idVendor=2109, idProduct=3431
Apr 13 08:48:25 darkstar kernel: usb 6-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Apr 13 08:48:25 darkstar kernel: usb 6-4: Product: USB2.0 Hub
Apr 13 08:48:25 darkstar kernel: usb 6-4: ep 0x81 - rounding interval to 2048 microframes
Apr 13 08:48:25 darkstar kernel: hub 6-4:1.0: USB hub found
Apr 13 08:48:25 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep
Apr 13 08:48:25 darkstar kernel: hub 6-4:1.0: 4 ports detected
Apr 13 08:48:25 darkstar kernel: usb 6-2: new SuperSpeed USB device using xhci_hcd and address 3
Apr 13 08:48:25 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep
Apr 13 08:48:25 darkstar last message repeated 2 times
Apr 13 08:48:25 darkstar kernel: usb 6-2: New USB device found, idVendor=2109, idProduct=0810
Apr 13 08:48:25 darkstar kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 13 08:48:25 darkstar kernel: usb 6-2: Product: 4-Port USB 3.0 Hub
Apr 13 08:48:25 darkstar kernel: usb 6-2: Manufacturer: VIA Labs, Inc.
Apr 13 08:48:25 darkstar kernel: usb 6-2: ep 0x81 - rounding interval to 32768 microframes
Apr 13 08:48:25 darkstar kernel: hub 6-2:1.0: USB hub found
Apr 13 08:48:25 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: Stalled endpoint
Apr 13 08:48:25 darkstar last message repeated 2 times
Apr 13 08:48:25 darkstar kernel: hub 6-2:1.0: config failed, can't read hub descriptor (err -22)

Open in new window


Again, nothing happened when I plugged in the USB 3.0 drive to the hub
8:50:11 - Plugged in a USB 2.0 HDD to the hub

Apr 13 08:50:11 darkstar kernel: usb 6-4.4: new high speed USB device using xhci_hcd and address 0
Apr 13 08:50:11 darkstar kernel: xhci_hcd 0000:01:00.0: WARN: short transfer on control ep
Apr 13 08:50:11 darkstar last message repeated 3 times
Apr 13 08:50:11 darkstar kernel: usb 6-4.4: New USB device found, idVendor=0480, idProduct=a001
Apr 13 08:50:11 darkstar kernel: usb 6-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 13 08:50:11 darkstar kernel: usb 6-4.4: Product: External USB HDD
Apr 13 08:50:11 darkstar kernel: usb 6-4.4: Manufacturer: Toshiba 
Apr 13 08:50:11 darkstar kernel: usb 6-4.4: SerialNumber: 58384D3150355A4854202020
Apr 13 08:50:11 darkstar kernel: scsi7 : usb-storage 6-4.4:1.0
Apr 13 08:50:16 darkstar kernel: scsi 7:0:0:0: Direct-Access     Toshiba  External USB HDD 1.04 PQ: 0 ANSI: 4
Apr 13 08:50:16 darkstar kernel: sd 7:0:0:0: Attached scsi generic sg2 type 0
Apr 13 08:50:16 darkstar kernel: sd 7:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
Apr 13 08:50:16 darkstar kernel: sd 7:0:0:0: [sdb] Write Protect is off
Apr 13 08:50:16 darkstar kernel: sd 7:0:0:0: [sdb] Mode Sense: 23 00 00 00
Apr 13 08:50:16 darkstar kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
Apr 13 08:50:16 darkstar kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
Apr 13 08:50:16 darkstar kernel:  sdb: unknown partition table
Apr 13 08:50:16 darkstar kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
Apr 13 08:50:16 darkstar kernel: sd 7:0:0:0: [sdb] Attached SCSI disk

Open in new window


8:50:59 - Unplugged USB 2.0 HDD.

Apr 13 08:50:59 darkstar kernel: usb 6-4.4: USB disconnect, address 4

Open in new window


8:51:49 - Unplug hub

Apr 13 08:51:49 darkstar kernel: usb 6-4: USB disconnect, address 2
Apr 13 08:51:49 darkstar kernel: usb 6-2: USB disconnect, address 3

Open in new window



0
Duncan RoeSoftware DeveloperCommented:
I posted some random advice in reply to another Q which might help you a bit getting the kernel built. I've got the source now, will have a look
0
Duncan RoeSoftware DeveloperCommented:
At least linux-2.6.38.2/drivers/usb/host/xhci-hub.c has had a huge amount of code added since 2.6.33.4. Well worth a try - post any questions you may have about the build process
0
Elena QuinnAuthor Commented:
Hi Duncan,

Well somehow I managed to update the kernel to 2.6.38.2 (and boy does my head hurt now!).  It made a bit of a difference, though it didn't solve the issue completely.  It seems that it still can't get the hub descriptor for the USB 3.0 side.  Before, nothing happened when a USB 3.0 drive was plugged in.  Now, it seems to be able to downgrade it to USB 2.0 and at least recognize the drive.  While that's a small improvement, it doesn't help me (much) because I need it to run at USB 3 speed.

I'm still working the Via Labs angle, so I'll post back what I find.

Thanks,
Elena
0
Duncan RoeSoftware DeveloperCommented:
Well it is an experimental driver. I expect the developer would be interested to hear of your experiences, now that you are running the latest kernel. The author of xhci-hup is Sarah Sharp <sarah.a.sharp@linux.intel.com> and I suggest you contact her.
0
Elena QuinnAuthor Commented:
Hi Duncan,

Well, I did as you suggested and contacted Sarah Sharp.  She was kind enough to email me back quickly and told me the following:


USB 3.0 hub support wasn't merged into the Linux kernel until 2.6.39.  Only the USB 2.0 part of the USB 3.0 hub will be working in kernels before that version.  You should update to the latest release candidate (currently 2.6.39-rc3) and see if your hub works with that.

and


The adapter card should work fine with the xHCI driver that's included in the Linux kernel, and all USB 3.0 hubs should work with the 2.6.39 kernel.

So, I downloaded and installed the 2.6.39-rc3 kernel (Got it right on the first try, too - Yay for me!).  Anyway, it worked!  Everything is being seen properly and running at USB 3 speed.  Yay again!

Thank you so much for all your help in getting me to this point.

Best regards,
Elena Quinn
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Elena QuinnAuthor Commented:
The solution was to update to the 2.6.39-rc3 kernel.  However the points should really go to the expert that helped me get to that point.  That was Duncan_Roe.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux OS Dev

From novice to tech pro — start learning today.