USB 3.0 OTG not switching to superspeed

DavidDavid New Member Posts: 30
Hi there,
i have a Problem with the USB 3.0 Port (i have a 3.0 OTG Cable to provide me with a Type A connector).
For testing, i plugged in an usb hard drive with 3.0 support.
Because i use gentoo, my kernel is hand made. I have support for xHCI compiled in.
When i connect the HDD everything works, but the device only goes up to 480M (high-speed, USB 2.0) and not 5000M (super-speed, USB 3.0). Have i something not compiled into the kernel which is needed? Usually this setup works fine, but i always tried only boards with real USB 3.0 and not OTG.

Here is the output from dmesg:
[    2.954773] ACPI: bus type USB registered
[    2.954853] usbcore: registered new interface driver usbfs
[    2.954881] usbcore: registered new interface driver hub
[    2.954925] usbcore: registered new device driver usb
[    2.963822] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[    2.965449] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.965456] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.965460] usb usb1: Product: xHCI Host Controller
[    2.965464] usb usb1: Manufacturer: Linux 4.4.6-gentoo xhci-hcd
[    2.965467] usb usb1: SerialNumber: 0000:00:14.0
[    2.965822] hub 1-0:1.0: USB hub found
[    2.966444] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[    2.966957] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    2.966963] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.966967] usb usb2: Product: xHCI Host Controller
[    2.966971] usb usb2: Manufacturer: Linux 4.4.6-gentoo xhci-hcd
[    2.966975] usb usb2: SerialNumber: 0000:00:14.0
[    2.967371] hub 2-0:1.0: USB hub found
[    3.318392] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    3.488082] usb 1-1: New USB device found, idVendor=174c, idProduct=55aa
[    3.488182] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    3.488190] usb 1-1: Product: USB 3.0 device
[    3.488237] usb 1-1: Manufacturer: Intenso
[    3.488242] usb 1-1: SerialNumber: 90900000000000003214

and here is the output of "lsusb -t"
up ~ # lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 480M

and here is the verbose output of the device:
Bus 001 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051 SATA 3Gb/s bridge
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x174c ASMedia Technology Inc.
  idProduct          0x55aa ASM1051 SATA 3Gb/s bridge
  bcdDevice            1.00
  iManufacturer           2 Intenso
  iProduct                3 USB 3.0 device
  iSerial                 1 90900000000000003214
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           85
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           4
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     98 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
        Data-in pipe (0x03)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
        Data-out pipe (0x04)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
        Status pipe (0x02)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
        Command pipe (0x01)
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength           22
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x0000f41e
      BESL Link Power Management (LPM) Supported
    BESL value     1024 us 
    Deep BESL value    61440 us 
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x000e
      Device can operate at Full Speed (12Mbps)
      Device can operate at High Speed (480Mbps)
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   1
      Lowest fully-functional device speed is Full Speed (12Mbps)
    bU1DevExitLat          10 micro seconds
    bU2DevExitLat        2047 micro seconds
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0001
  Self Powered

as you can see, the device really supports super-speed

(Device can operate at SuperSpeed (5Gbps))

Any advice?
«13

Comments

  • Henrikki MaattaHenrikki Maatta New Member Posts: 6
    +1 here.

    I tried Ubuntu and Ubilinux, several USB 3 SATA adapters. Even bought a brand new USB3 dock to make sure. Still only 480M.
    I would like to hear from the development team if they have seen SuperSpeed work on linux.
    Is there some wizardry to enable it?
  • Elie De BrauwerElie De Brauwer New Member Posts: 35
    I performed the following test with a Kingston DataTraveler USB stick:
    [ 5823.894068] usb 2-1: new SuperSpeed USB device number 18 using xhci_hcd
    [ 5823.906072] usb 2-1: New USB device found, idVendor=0951, idProduct=1666
    [ 5823.906081] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 5823.906088] usb 2-1: Product: DataTraveler 3.0
    [ 5823.906092] usb 2-1: Manufacturer: Kingston
    [ 5823.906096] usb 2-1: SerialNumber: 08606E6B66FBBE108710051D
    [ 5823.907251] usb-storage 2-1:1.0: USB Mass Storage device detected
    [ 5823.907492] scsi host1: usb-storage 2-1:1.0
    [ 5824.910821] scsi 1:0:0:0: Direct-Access     Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
    [ 5824.912202] sd 1:0:0:0: [sdb] 15360000 512-byte logical blocks: (7.86 GB/7.32 GiB)
    [ 5824.913667] sd 1:0:0:0: [sdb] Write Protect is off
    [ 5824.913677] sd 1:0:0:0: [sdb] Mode Sense: 2b 80 00 08
    [ 5824.914842] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    [ 5825.034679]  sdb: sdb1 sdb2
    [ 5825.038496] sd 1:0:0:0: [sdb] Attached SCSI removable disk
    

    Using a custom 4.6.0 kernel:
    [email protected]:~# lsusb -t
    /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
        |__ Port 1: Dev 18, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
    

    This with an el-cheapo cable bought on Amazon.
  • DavidDavid New Member Posts: 30
    Nice!
    Could you please upload your kernel-config?

    Thanks in advance!
  • Elie De BrauwerElie De Brauwer New Member Posts: 35
    Sure, my kernel config for 4.6.0 is attached. Do keep in mind:
    a) my kernel config is a monolithic but minimalistic kernel
    b) works with vanilla 4.6.0 (no upboard patches yet)
    c) eMMC module isn't working (haven't figured out why yet, any pointers welcome here)
    d) haven't worked with the 40-pin connector.

    But USB, CPU, GPU, ethernet and friends are behaving quite well.
  • DavidDavid New Member Posts: 30
    edited July 2016
    Thanks! I will try to find the differences, but maybe i simply have to switch to Kernel 4.6.x ;-)
    I am still running on a 4.4.6 Kernel (Gentoo Patched, but almost vanilla). My Goal is also to get a minimalistic kernel, but as i had so many problems (also with the eMMC) i have far too much options compiled in.

    If it helps, i can upload my config aswell. Should work straight forward for a vanilla 4.6 kernel.

    I think i remember, eMMC worked without alot adjustedments in PCI mode (switch this in the bios), but for ACPI-Mode i had to tick the following options (me thinks):

    CONFIG_MMC_SDHCI=y
    CONFIG_MMC_SDHCI_PCI=y
    CONFIG_MMC_SDHCI_ACPI=y

    CONFIG_SCSI=y
    CONFIG_SCSI_DMA=y
    CONFIG_SCSI_PROC_FS=y
    CONFIG_BLK_DEV_SD=y

    CONFIG_ATA_ACPI=y
  • Elie De BrauwerElie De Brauwer New Member Posts: 35
    That was an awesome pointer (and I can't imagine I overlooked it myself), in the config I posted earlier, I switched CONFIG_MMC_SDHCI_ACPI=y into CONFIG_MMC_SDHC_PCI=y and changed the settings in the BIOS announce the SDHC controller via PCI and it-just-worked. I got a bit on the wrong path since an Ubuntu 14.04 live image just detected the eMMC out of the box without BIOS changes. But this is fine as well.
  • MarcelloMarcello New Member Posts: 156
    edited August 2016
    David wrote:
    Hi there,
    i have a Problem with the USB 3.0 Port (i have a 3.0 OTG Cable to provide me with a Type A connector).
    For testing, i plugged in an usb hard drive with 3.0 support.
    Because i use gentoo, my kernel is hand made. I have support for xHCI compiled in.
    When i connect the HDD everything works, but the device only goes up to 480M (high-speed, USB 2.0) and not 5000M (super-speed, USB 3.0). Have i something not compiled into the kernel which is needed? Usually this setup works fine, but i always tried only boards with real USB 3.0 and not OTG.
    as you can see, the device really supports super-speed
    (Device can operate at SuperSpeed (5Gbps))
    Any advice?

    Did you ever manage to go superspeed?
  • DavidDavid New Member Posts: 30
    not yet.
    I compiled a new kernel, even switched to kernel 4.6.
    So i don't think it is a software problem. I will order another USB-OTG cable. Even though my current cable is a super speed cable, i want to check if it is a connection problem.
  • DCleriDCleri Administrator, AAEON Posts: 593 admin
    Hi David,

    ElieDeBrauwer got it working as you can see from the post above.
    I can confirm that it doesn't work on the 4.4 ubilinux kernel and we are looking into it soon. Hopefully it can be solved in the official distribution too (without switching to a newer kernel).
  • Henrikki MaattaHenrikki Maatta New Member Posts: 6
    Just having newer kernel does not help.
    I tried Debian with

    linux-image-4.6-4.dmz.3-liquorix-amd64.

    It has all USB-related options compiled.
    No luck.
    It must be some combination of kernel parameters Elie managed to get right.
  • DavidDavid New Member Posts: 30
    i also compiled the same kernel as ellie (used the config on a 4.6 kernel) but no luck. so i thought it might have something to do with the cable. i will report back, as soon as my new cable arrives.

    hopefully it is not a hardware issue on some of the up-boards.
  • MarcelloMarcello New Member Posts: 156
    I am worried with the silence of the official voices...
    did anyone EVER make it to work 100% for sure, with ANY OS...?
  • Elie De BrauwerElie De Brauwer New Member Posts: 35
    One update regarding usb 3.0 from my side, as stated earlier I did a test with USB 3.0 on the OTG port with a 4.6 kernel and those results are still accurate/correct.

    I did however at a certain point attempt to connect a high USB 3.0 camera and found out that when attempting to take that action, the USB 3.0 link become unstable, in a way that my Linux kernel would re-enumerate the USB device periodically (seemingly a disconnect). On that setup I tried: a) different camera's (only the frequency of the issue changed here) b) different cable combinations c) the same camera/cable on my laptop (worked stable) d) different up-boards. The only thing which worked was forcing the USB 3.0 port to operate at 2.0 speeds by plugging an USB 2.0 cable in between and this is now working stable (although at lower speed). (Note, I do believe it was switching to super speed at that point, but it had an issue staying there).

    Also while building multiple setups I ran into an issue at USB 2.0 (again using the OTG port) which was caused by a too long (was using a rolled usb micro cable from adafruit) cable.

    Bottomline, even at my side where a usb stick behaves fine there are still some other things wrong.
  • DCleriDCleri Administrator, AAEON Posts: 593 admin
    Hi All,

    After some more testing, I want to confirm that USB3.0 superspeed works on the UP Board if using either ubilinux or Ubuntu, at least while using a 4.4 kernel.

    All the tests and the findings on Google point at a generic USB3.0 sensing (detection) issue which is common also on Laptops, PC and other devices with USB3.0.
    You can find on Google and other search engines hundreds of topics about the issue.

    The issue is more difficult to present itself on a laptop for example because of the type-A port which is very handy when inserting a cable to it. If the connection is simple and quick enough the system detects the device as USB3.0 superspeed.
    On the other end, with the micro USB3.0 (OTG) socket on the UP Board, it is much more difficult to get a prompt and firm connection, so the system detect initially the device as USB2.0 and it doesn't re-enumerate after a full connection. You can try to insert a USB3.0 device slowly to your laptop USB3.0 port and you can easily experience the wrong detection of the device (USB2.0 instead of USB3.0 superspeed).

    To minimise the issue what we tried is to connect first a OTG adapter to the board (micro USB3.0) and then insert the USB type-A port on the storage device. This usually help the system to detect the device as USB3.0.
    Also if rebooting the system (or powering up) while the cables are connected, the storage device get enumerated as USB3.0 superspeed.

    Please let me know if you can confirm this behaviour or if you have still the issue.
  • DavidDavid New Member Posts: 30
    edited August 2016
    I cannot confirm this behaviour.
    I often reboot with all cables plugged in, i never get super speed.

    Today my alternative USB 3.0 OTG cable arrived, but like before, i can only achieve high speed.
    I can rule out pretty much a hardware issue for my devices (tested many of them, one being a Kingston DT Ultimate Pendrive, so low power), and after having tested two distinct OTG cables i don't know what to do next.
    I have a kernel that "should" work for 3.0 (also tested Elis' Kernel) and i tested with Ubuntu on a 4.4 kernel (using a Live prendrive). Nothing helps.
    Any other suggestions or tests, which i can perform on my end?

    Best regards,
    David
  • MarcelloMarcello New Member Posts: 156
    So far I tried with a mainstream USB 3 stick and with a more serious real ssd with a usb3 adaptor.
    No luck. Either it goes usb2 or it gets corrupted.
  • DCleriDCleri Administrator, AAEON Posts: 593 admin
    edited August 2016
    Please in your reply include the following information:
    - Board type (e.g. 2GB Ram 16GB eMMC)
    - BIOS Version (you can run from the terminal: cat /sys/devices/virtual/dmi/id/bios_version )
    - Operating system
    - kernel version (you can run from the terminal: uname -r )
    - cables and devices used for the tests
    - details of the performed tests

    thanks!
  • DavidDavid New Member Posts: 30
    edited August 2016
    Most of my tests were performed with the following setup:
    - Board type (e.g. 2GB Ram 16GB eMMC)
    4GB Ram / 32 GB eMMC
    - BIOS Version (you can run from the terminal: cat /sys/devices/virtual/dmi/id/bios_version )
    UPC1BM0R
    - Operating system
    Gentoo Linux
    - kernel version (you can run from the terminal: uname -r )
    4.4.6-gentoo
    - cables and devices used for the tests
    Devices: Kingston DT Ultimate G2, Intenso 6031513 external HDD 5TB (Controller: ASMedia Technology Inc. ASM1051 SATA 3Gb/s bridge);
    Cables: deleyCON [0,2m] USB 3.0 Super Speed OTG Adapter; and another one from BIGtec, not specified; both claim to be SS-capable. Maybe i should open them and count the wires?
    - details of the performed tests
    attach the devices like you described above, rebootet while still being connected etc. checked kernel output (dmesg) and usb-status (lsusb -t)
    i always get 480 instead of 5000 mbits

    some tests were also performed on a ubuntu version (also with a 4.4 kernel).
    FYI: i just ordered another cable, this time from hama with a higher price-tag.... in 5 days i will know if that helps...
  • MarcelloMarcello New Member Posts: 156
    I doubt that make will matter much on a 10cm cable
  • DavidDavid New Member Posts: 30
    MarcFinns wrote:
    I doubt that make will matter much on a 10cm cable
    i doubt it too, but well, maybe the cheapo cables are advertised as USB3.0 but only use 4 wires insted of 8 (or was it 10)?
  • MarcelloMarcello New Member Posts: 156
    David wrote:
    MarcFinns wrote:
    I doubt that make will matter much on a 10cm cable
    i doubt it too, but well, maybe the cheapo cables are advertised as USB3.0 but only use 4 wires insted of 8 (or was it 10)?

    Good point. I would be extremely glad to be proven wrong. Please do let me know!
  • MarcelloMarcello New Member Posts: 156
    edited August 2016
    UPDATE ON THE SUPERSPEED ISSUE - NOT GREAT

    I have 2 identical UP boards (4/32). I tried a few USB3 sticks and all of them are connecting as 480M.
    I also have a Kingston SSDNow mS200 mSATA mounted on a USB3 adaptor based on ASMedia Technology (ASMT) 2115.
    When connected to the USB2 port it works on both boards. When connected to the USB3 OTG port, it is recognised only by one of the two UP Boards. Actually, sometimes the board(s) do not even boot if the SSD is attached.
    Please note that boards have been purchased at the same time, are identical and are running the same stock Ubuntu 16.04 from a bootable USB stick.
    For the one that works, I see that the SSD is recognised as USB3.
    lsusb -vt
    /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
        |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
    /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M
        |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 4: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 4: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
        |__ Port 7: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 4: Dev 5, If 0, Class=Vendor Specific Class, Driver=, 480M
    

    The Kernel reports the following:
    [  167.818741] usb 2-1: reset SuperSpeed USB device number 3 using xhci_hcd
    [  167.837634] scsi host1: uas_eh_bus_reset_handler success
    [  175.660282] usb 2-1: USB disconnect, device number 3
    [  175.666180] sd 1:0:0:0: [sda] Synchronizing SCSI cache
    [  175.784191] sd 1:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
    [  193.402624] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
    [  193.419636] usb 2-1: New USB device found, idVendor=174c, idProduct=55aa
    [  193.419650] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
    [  193.419658] usb 2-1: Product: ASMT1051
    [  193.419667] usb 2-1: Manufacturer: asmedia
    [  193.419673] usb 2-1: SerialNumber: 1234567890AB
    [  193.426931] scsi host2: uas
    [  193.428022] scsi 2:0:0:0: Direct-Access     ASMT     2115             0    PQ: 0 ANSI: 6
    [  193.429209] sd 2:0:0:0: Attached scsi generic sg0 type 0
    [  193.619839] sd 2:0:0:0: [sda] 117231408 512-byte logical blocks: (60.0 GB/55.9 GiB)
    [  193.620397] sd 2:0:0:0: [sda] Write Protect is off
    [  193.620408] sd 2:0:0:0: [sda] Mode Sense: 43 00 00 00
    [  193.620719] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [  193.626767]  sda: sda1
    [  193.628758] sd 2:0:0:0: [sda] Attached SCSI disk
    [  193.843312] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
    
    HOWEVER... When I benchmark the drive using Gnome-disks:
    1) it often gives I/O error
    2) sometimes the whole board crashes with a white screen
    3) the few times it runs till the end I see that it is indeed fast but it repeatedly freezes every few seconds with transfer rate going to zero, see picture attached.

    AAEON: this can't be right... Any clue?
  • DavidDavid New Member Posts: 30
    Thanks Marc for the new info. I am still waiting for my new OTG Cable... should arrive tomorrow. i will report back.

    But seeing your issues: there seems to be definitely something wrong on the hardware side... something which might be compensated by firmware upgrades... more or less.

    I hope to hear back from AAEON on this matter :-)
  • William HenningWilliam Henning New Member Posts: 17
    I hope this is fixed soon, as my intent was to put an SSD with dual Windows/Linux installation on one of my up-board's
  • MarcelloMarcello New Member Posts: 156
    Can it be a hardware bug? After all, why would they sell a USB2 SATA shield if the USB3 port would work correctly? This would be a great differentiator compared to other boards.
    I hope to be wrong but I have a bad feeling about this.
  • William HenningWilliam Henning New Member Posts: 17
    It is more likely a kernel/BIOS issue (I HOPE!)

    The LeMaker Guitar had many USB3 issues which were eventually solved with specific USB 3 OTG/host cables and some software patches.
    MarcFinns wrote:
    Can it be a hardware bug? After all, why would they sell a USB2 SATA shield if the USB3 port would work correctly? This would be a great differentiator compared to other boards.
    I hope to be wrong but I have a bad feeling about this.
  • MarcelloMarcello New Member Posts: 156
    No official comments from UP?
  • DavidDavid New Member Posts: 30
    Well then, my third Superspeed USB OTG cable arrived today (it is the most expensive one).

    What can i say: USB 3.0 works. but not flawlessly and sometimes so badly it is even unusable.

    Here is my result from using my kingston pendrive
    [  452.763563] xhci_hcd 0000:00:14.0: port 0 resume PLC timeout
    [  457.859481] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
    [  457.871227] usb 2-1: New USB device found, idVendor=0951, idProduct=1656
    [  457.871245] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  457.871257] usb 2-1: Product: DT Ultimate G2
    [  457.871268] usb 2-1: Manufacturer: Kingston
    [  457.871279] usb 2-1: SerialNumber: 0018F30C9FDFBC20711D0087
    [  457.873218] usb-storage 2-1:1.0: USB Mass Storage device detected
    [  457.873583] scsi host3: usb-storage 2-1:1.0
    [  458.877329] scsi 3:0:0:0: Direct-Access     Kingston DT Ultimate G2   PMAP PQ: 0 ANSI: 0 CCS
    [  458.878455] sd 3:0:0:0: Attached scsi generic sg2 type 0
    [  458.879661] sd 3:0:0:0: [sdc] 62586880 512-byte logical blocks: (32.0 GB/29.8 GiB)
    [  458.880122] sd 3:0:0:0: [sdc] Write Protect is off
    [  458.880150] sd 3:0:0:0: [sdc] Mode Sense: 23 00 00 00
    [  458.880601] sd 3:0:0:0: [sdc] No Caching mode page found
    [  458.880623] sd 3:0:0:0: [sdc] Assuming drive cache: write through
    [  459.225038]  sdc: sdc1 sdc2 sdc3 < sdc5 sdc6 sdc7 >
    [  459.226617] sd 3:0:0:0: [sdc] Attached SCSI removable disk
    [  462.659738] usb 2-1: USB disconnect, device number 3
    [  462.875828] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
    [  462.887627] usb 2-1: New USB device found, idVendor=0951, idProduct=1656
    [  462.887649] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  462.887724] usb 2-1: Product: DT Ultimate G2
    [  462.887741] usb 2-1: Manufacturer: Kingston
    [  462.887755] usb 2-1: SerialNumber: 0018F30C9FDFBC20711D0087
    [  462.889584] usb-storage 2-1:1.0: USB Mass Storage device detected
    [  462.890054] scsi host4: usb-storage 2-1:1.0
    [  463.893633] scsi 4:0:0:0: Direct-Access     Kingston DT Ultimate G2   PMAP PQ: 0 ANSI: 0 CCS
    [  463.894837] sd 4:0:0:0: Attached scsi generic sg2 type 0
    [  463.896026] sd 4:0:0:0: [sdc] 62586880 512-byte logical blocks: (32.0 GB/29.8 GiB)
    [  463.896399] sd 4:0:0:0: [sdc] Write Protect is off
    [  463.896426] sd 4:0:0:0: [sdc] Mode Sense: 23 00 00 00
    [  463.896710] sd 4:0:0:0: [sdc] No Caching mode page found
    [  463.896730] sd 4:0:0:0: [sdc] Assuming drive cache: write through
    [  463.905751]  sdc: sdc1 sdc2 sdc3 < sdc5 sdc6 sdc7 >
    [  463.907720] sd 4:0:0:0: [sdc] Attached SCSI removable disk
    [  473.849511] usb 2-1: USB disconnect, device number 4
    [  474.069613] usb 2-1: new SuperSpeed USB device number 5 using xhci_hcd
    [  474.081218] usb 2-1: New USB device found, idVendor=0951, idProduct=1656
    [  474.081232] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  474.081243] usb 2-1: Product: DT Ultimate G2
    [  474.081252] usb 2-1: Manufacturer: Kingston
    [  474.081261] usb 2-1: SerialNumber: 0018F30C9FDFBC20711D0087
    [  474.084060] usb-storage 2-1:1.0: USB Mass Storage device detected
    [  474.084604] scsi host5: usb-storage 2-1:1.0
    [  475.087577] usb 2-1: USB disconnect, device number 5
    [  475.296699] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd
    [  475.308405] usb 2-1: New USB device found, idVendor=0951, idProduct=1656
    [  475.308423] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  475.308435] usb 2-1: Product: DT Ultimate G2
    [  475.308445] usb 2-1: Manufacturer: Kingston
    [  475.308455] usb 2-1: SerialNumber: 0018F30C9FDFBC20711D0087
    [  475.310322] usb-storage 2-1:1.0: USB Mass Storage device detected
    [  475.310762] scsi host6: usb-storage 2-1:1.0
    [  476.190676] usb 2-1: USB disconnect, device number 6
    [  476.397756] usb 2-1: new SuperSpeed USB device number 7 using xhci_hcd
    [  476.409552] usb 2-1: New USB device found, idVendor=0951, idProduct=1656
    [  476.409571] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  476.409583] usb 2-1: Product: DT Ultimate G2
    [  476.409593] usb 2-1: Manufacturer: Kingston
    [  476.409643] usb 2-1: SerialNumber: 0018F30C9FDFBC20711D0087
    [  476.411315] usb-storage 2-1:1.0: USB Mass Storage device detected
    [  476.412154] scsi host7: usb-storage 2-1:1.0
    [  477.414569] scsi 7:0:0:0: Direct-Access     Kingston DT Ultimate G2   PMAP PQ: 0 ANSI: 0 CCS
    [  477.415891] sd 7:0:0:0: Attached scsi generic sg2 type 0
    [  477.415961] sd 7:0:0:0: [sdc] 62586880 512-byte logical blocks: (32.0 GB/29.8 GiB)
    [  477.416351] sd 7:0:0:0: [sdc] Write Protect is off
    [  477.416394] sd 7:0:0:0: [sdc] Mode Sense: 23 00 00 00
    [  477.416709] sd 7:0:0:0: [sdc] No Caching mode page found
    [  477.416731] sd 7:0:0:0: [sdc] Assuming drive cache: write through
    [  477.427131]  sdc: sdc1 sdc2 sdc3 < sdc5 sdc6 sdc7 >
    [  477.428828] sd 7:0:0:0: [sdc] Attached SCSI removable disk
    [  486.203369] usb 2-1: USB disconnect, device number 7
    [  486.215511] udevd[4095]: inotify_add_watch(7, /dev/sdc, 10) failed: No such file or directory
    [  486.425466] usb 2-1: new SuperSpeed USB device number 8 using xhci_hcd
    [  486.437266] usb 2-1: New USB device found, idVendor=0951, idProduct=1656
    [  486.437285] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [  486.437299] usb 2-1: Product: DT Ultimate G2
    [  486.437350] usb 2-1: Manufacturer: Kingston
    [  486.437362] usb 2-1: SerialNumber: 0018F30C9FDFBC20711D0087
    [  486.439251] usb-storage 2-1:1.0: USB Mass Storage device detected
    [  486.439683] scsi host8: usb-storage 2-1:1.0
    [  487.443281] scsi 8:0:0:0: Direct-Access     Kingston DT Ultimate G2   PMAP PQ: 0 ANSI: 0 CCS
    [  487.444525] sd 8:0:0:0: [sdc] 62586880 512-byte logical blocks: (32.0 GB/29.8 GiB)
    [  487.444567] sd 8:0:0:0: Attached scsi generic sg2 type 0
    [  487.444914] sd 8:0:0:0: [sdc] Write Protect is off
    [  487.444935] sd 8:0:0:0: [sdc] Mode Sense: 23 00 00 00
    [  487.445179] sd 8:0:0:0: [sdc] No Caching mode page found
    [  487.445198] sd 8:0:0:0: [sdc] Assuming drive cache: write through
    [  487.451853]  sdc: sdc1 sdc2 sdc3 < sdc5 sdc6 sdc7 >
    [  487.456435] sd 8:0:0:0: [sdc] Attached SCSI removable disk
    

    as you can see, the device is finally recognized as usb 3.0 @superspeed. But it gets disconnected many times until it stays that way. running some benchmarks it really give better speed than USB 2.0 but sometimes errors are thrown.

    using the same cable and attaching my USB 3.0 HDD (with external power!) i get this:
    [  133.859844] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
    [  133.871924] usb 2-1: New USB device found, idVendor=174c, idProduct=55aa
    [  133.871949] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
    [  133.871965] usb 2-1: Product: USB 3.0 device
    [  133.871978] usb 2-1: Manufacturer: Intenso
    [  133.871991] usb 2-1: SerialNumber: 90900000000000003214
    [  133.878355] scsi host2: uas
    [  133.879348] scsi 2:0:0:0: Direct-Access     Intenso  USB 3.0 device   0    PQ: 0 ANSI: 6
    [  133.880340] sd 2:0:0:0: Attached scsi generic sg2 type 0
    [  133.880455] sd 2:0:0:0: [sdc] Spinning up disk...
    [  134.422820] usb 2-1: USB disconnect, device number 2
    
    
    [  135.001895] sd 2:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
    [  135.001925] sd 2:0:0:0: [sdc] Sense not available.
    [  135.091896] sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
    [  135.091924] sd 2:0:0:0: [sdc] Sense not available.
    

    the device is recognized @superspeed but disconnects immediatly. it never is coming back again and the kernel is receiving read errors. so it is pretty much useless for me.
    Running the disk @USB 2.0 works fine on the up board. operating this hdd on any other device works fine even with USB 3.0

    Even worse: trying to reboot with the HDD connected crashes the up-board before loading the bios/efi.

    so there is definitely something wrong with the up-board hardware.
    i assume it could have something to do with the power supplied on the OTG-Port. Really low-power devices _could_ work, others like my hdd (even when getting external powersupply) might want to drain some power from an USB 3.0 port (on boot or while transferring lot of data) which causes the link to become unstable. well, this is jsut an assumption.

    Nevertheless: @AEEON please respond to this issue.
  • MarcelloMarcello New Member Posts: 156
    Your findings are fully consistent with mine.. I am not convinced this is power related though. In my case USB3 sticks that require way less power than ssd are not recognised as such. The ssd itself works fine on USB2 ports and overall power consumption (board + ssd + wifi/BT dongle) never reaches 1.5A sustained (I measured a 2.1A spike once).
    Looks more like a hw issue, hoping that it can be addressed in firmware. AAEON???
  • DCleriDCleri Administrator, AAEON Posts: 593 admin
    Hi Guys,

    Thanks for all the information you are gathering from your tests. The UP Team is currently investigating the issue.

    Please be aware that there are some Errata shared by Intel which involves USB (both 2.0 and 3.0) issues.
    AAEON is working on a new BIOS which includes fixes for the items in the Errata list and we are going to evaluate if that is going to resolve the issue reported.
Sign In or Register to comment.