[Nov 16] Arch Linux mainline XFCE (20181104) / NetBSD ([201811111550Z) - 1080P Pinebook |[Nov 13] Slackware Aarch64 Miniroot & XFCE (20181101) / NextCloudPi (11-04-18) / Armbian Debian Stretch Desktop & Armbian Ubuntu Bionic (5.65) - Rock64 |[Nov 12] Q4OS ( 2.4-r5) - 1080P Pinebook / Pinebook |[Nov 09] KDE Neon ( 20181104-1500) - 1080P Pinebook / Pinebook /Arch Linux (20181104) - Pinebook

Project Inspiration | Get Started | IRC Logs | Forum Rules/Policy


External hard drive problem
#1
I just got my ROCK 64 with the jessie-openmediavault-rock64-0.6.25-193-arm64.img image from https://github.com/ayufan-rock64/linux-b...tag/0.6.25 

But the external hard (http://en.sharkoon.com/product/1685/10394#specs) drive isnt recognized.

What is going on? The hard drive works fine with Openmediavault on raspberry pi & OdroidXU4.

Code:
[email protected]:~# sudo fdisk -l

Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mtdblock0: 4 MiB, 4161536 bytes, 8128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mtdblock1: 256 KiB, 262144 bytes, 512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
GPT PMBR size mismatch (4458495 != 15359999) will be corrected by w(rite).

Disk /dev/mmcblk1: 7.3 GiB, 7864320000 bytes, 15360000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 824DA7D1-B7E7-49CA-A273-69A1E8B9785F

Device          Start      End  Sectors  Size Type
/dev/mmcblk1p1     64     8063     8000  3.9M Linux filesystem
/dev/mmcblk1p2   8064     8191      128   64K Linux filesystem
/dev/mmcblk1p3   8192    16383     8192    4M Linux filesystem
/dev/mmcblk1p4  16384    24575     8192    4M Linux filesystem
/dev/mmcblk1p5  24576    32767     8192    4M Linux filesystem
/dev/mmcblk1p6  32768   262143   229376  112M Microsoft basic data
/dev/mmcblk1p7 262144 15359966 15097823  7.2G Linux filesystem


At around 900 seconds I powered off and on the HD...

Code:
[email protected]:~# dmesg | grep usb
[    0.614193] usbcore: registered new interface driver usbfs
[    0.614793] usbcore: registered new interface driver hub
[    0.615433] usbcore: registered new device driver usb
[    1.161801] phy phy-ff450000.syscon:[email protected]: Looking up phy-supply from device tree
[    1.161918] vcc_host1_5v: could not add device link phy-ff450000.syscon:[email protected] err -2
[    1.162519] phy phy-ff450000.syscon:[email protected]: Looking up phy-supply from device tree
[    1.162629] vcc_host1_5v: could not add device link phy-ff450000.syscon:[email protected] err -2
[    1.163102] rockchip-usb2phy ff450000.syscon:[email protected]: GPIO lookup for consumer otg-vbus
[    1.163120] rockchip-usb2phy ff450000.syscon:[email protected]: using device tree for GPIO lookup
[    1.163139] of_get_named_gpiod_flags: can't parse 'otg-vbus-gpios' property of node '/[email protected]/[email protected][0]'
[    1.163155] of_get_named_gpiod_flags: can't parse 'otg-vbus-gpio' property of node '/[email protected]/[email protected][0]'
[    1.163171] rockchip-usb2phy ff450000.syscon:[email protected]: using lookup tables for GPIO lookup
[    1.163186] rockchip-usb2phy ff450000.syscon:[email protected]: lookup for GPIO otg-vbus failed
[    1.163201] rockchip-usb2phy ff450000.syscon:[email protected]: vbus_drv is not assigned
[    1.164774] rockchip-u3phy ff470000.usb3-phy: GPIO lookup for consumer vbus-drv
[    1.164793] rockchip-u3phy ff470000.usb3-phy: using device tree for GPIO lookup
[    1.164811] of_get_named_gpiod_flags: can't parse 'vbus-drv-gpios' property of node '/[email protected][0]'
[    1.164829] of_get_named_gpiod_flags: can't parse 'vbus-drv-gpio' property of node '/[email protected][0]'
[    1.164843] rockchip-u3phy ff470000.usb3-phy: using lookup tables for GPIO lookup
[    1.164858] rockchip-u3phy ff470000.usb3-phy: lookup for GPIO vbus-drv failed
[    1.164872] rockchip-u3phy ff470000.usb3-phy: vbus_drv is not assigned
[    1.165945] phy phy-ff470000.usb3-phy.2: Looking up phy-supply from device tree
[    1.165965] phy phy-ff470000.usb3-phy.2: Looking up phy-supply property in node /[email protected]/[email protected] failed
[    1.166405] phy phy-ff470000.usb3-phy.3: Looking up phy-supply from device tree
[    1.166427] phy phy-ff470000.usb3-phy.3: Looking up phy-supply property in node /[email protected]/[email protected] failed
[    1.168184] rockchip-u3phy ff470000.usb3-phy: Rockchip u3phy initialized successfully
[    1.601869] usbcore: registered new interface driver udl
[    2.252837] usbcore: registered new interface driver cdc_ether
[    2.252900] usbcore: registered new interface driver rndis_host
[    2.255119] phy phy-ff470000.usb3-phy.2: u3phy u2 power on
[    2.255145] phy phy-ff470000.usb3-phy.3: u3phy u3 power on
[    2.256290] dwc2 ff580000.usb: Looking up vusb_d-supply from device tree
[    2.256303] dwc2 ff580000.usb: Looking up vusb_d-supply property in node /[email protected] failed
[    2.256318] ff580000.usb supply vusb_d not found, using dummy regulator
[    2.256418] dwc2 ff580000.usb: Looking up vusb_a-supply from device tree
[    2.256429] dwc2 ff580000.usb: Looking up vusb_a-supply property in node /[email protected] failed
[    2.256438] ff580000.usb supply vusb_a not found, using dummy regulator
[    2.269039] dwc2 ff580000.usb: DWC OTG Controller
[    2.269106] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1
[    2.269153] dwc2 ff580000.usb: irq 43, io mem 0xff580000
[    2.269451] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.269461] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.269469] usb usb1: Product: DWC OTG Controller
[    2.269477] usb usb1: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 dwc2_hsotg
[    2.269485] usb usb1: SerialNumber: ff580000.usb
[    2.339882] ehci-platform ff5c0000.usb: EHCI Host Controller
[    2.340258] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 2
[    2.340412] ehci-platform ff5c0000.usb: irq 44, io mem 0xff5c0000
[    2.346124] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00
[    2.346421] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    2.346432] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.346440] usb usb2: Product: EHCI Host Controller
[    2.346448] usb usb2: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 ehci_hcd
[    2.346455] usb usb2: SerialNumber: ff5c0000.usb
[    2.348661] ohci-platform ff5d0000.usb: Generic Platform OHCI controller
[    2.348982] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3
[    2.349160] ohci-platform ff5d0000.usb: irq 45, io mem 0xff5d0000
[    2.404377] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    2.404387] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.404395] usb usb3: Product: Generic Platform OHCI controller
[    2.404404] usb usb3: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 ohci_hcd
[    2.404411] usb usb3: SerialNumber: ff5d0000.usb
[    2.407569] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[    2.407579] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.407587] usb usb4: Product: xHCI Host Controller
[    2.407595] usb usb4: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 xhci-hcd
[    2.407603] usb usb4: SerialNumber: xhci-hcd.9.auto
[    2.409479] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.409661] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
[    2.409672] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.409680] usb usb5: Product: xHCI Host Controller
[    2.409688] usb usb5: Manufacturer: Linux 4.4.114-rockchip-ayufan-193 xhci-hcd
[    2.409696] usb usb5: SerialNumber: xhci-hcd.9.auto
[    2.412820] usbcore: registered new interface driver iforce
[    2.412930] usbcore: registered new interface driver xpad
[    2.413499] usbcore: registered new interface driver usbtouchscreen
[    2.460412] usbcore: registered new interface driver uvcvideo
[    2.467045] usbcore: registered new interface driver bfusb
[    2.467181] usbcore: registered new interface driver btusb
[    2.519667] of_get_named_gpiod_flags: parsed 'gpios' property of node '/switches/usb-switch[0]' - status (0)
[    2.520720] usbcore: registered new interface driver usbhid
[    2.520723] usbhid: USB HID core driver
[    2.523452] usbcore: registered new interface driver snd-usb-audio
[   13.435160] usb 5-1: device not accepting address 2, error -62
[   24.283144] usb 5-1: device not accepting address 3, error -62
[   24.320263] usb usb5-port1: attempt power cycle
[   25.360147] usb usb5-port1: cannot disable (err = -32)
[   25.394161] usb usb5-port1: cannot disable (err = -32)
[  889.555166] usb 5-1: device not accepting address 5, error -62
[  900.419178] usb 5-1: device not accepting address 6, error -62
[  900.464160] usb usb5-port1: attempt power cycle
[  901.502224] usb usb5-port1: cannot disable (err = -32)
[  901.549246] usb usb5-port1: cannot disable (err = -32)
Reply
#2
Same problem also with the "jessie-openmediavault-rock64-0.6.25-193-armhf.img" image btw...
Reply
#3
For starters, perhaps try the release image of OMV instead of pre-release.
  If you manage to click this link you'll join in the IRC channel
Reply
#4
Same result. 

https://github.com/ayufan-rock64/linux-b...ses/latest  --> 
jessie-openmediavault-rock64-0.5.15-136-armhf.img 

Is there a problem with the chipset?  ASMedia ASM1053

Code:
[email protected]:~# dmesg | grep usb
[    0.588101] usbcore: registered new interface driver usbfs
[    0.588706] usbcore: registered new interface driver hub
[    0.589315] usbcore: registered new device driver usb
[    1.107739] phy phy-ff450000.syscon:[email protected]: Looking up phy-supply from device tree
[    1.107760] phy phy-ff450000.syscon:[email protected]: Looking up phy-supply property in node /[email protected]/[email protected]/host-port failed
[    1.108395] phy phy-ff450000.syscon:[email protected]: Looking up phy-supply from device tree
[    1.108415] phy phy-ff450000.syscon:[email protected]: Looking up phy-supply property in node /[email protected]/[email protected]/otg-port failed
[    1.108832] rockchip-usb2phy ff450000.syscon:[email protected]: GPIO lookup for consumer otg-vbus
[    1.108848] rockchip-usb2phy ff450000.syscon:[email protected]: using device tree for GPIO lookup
[    1.108889] of_get_named_gpiod_flags: parsed 'otg-vbus-gpios' property of node '/[email protected]/[email protected][0]' - status (0)
[    1.109627] rockchip-u3phy ff470000.usb3-phy: GPIO lookup for consumer vbus-drv
[    1.109643] rockchip-u3phy ff470000.usb3-phy: using device tree for GPIO lookup
[    1.109675] of_get_named_gpiod_flags: parsed 'vbus-drv-gpios' property of node '/[email protected][0]' - status (0)
[    1.110073] phy phy-ff470000.usb3-phy.2: Looking up phy-supply from device tree
[    1.110091] phy phy-ff470000.usb3-phy.2: Looking up phy-supply property in node /[email protected]/[email protected] failed
[    1.110616] phy phy-ff470000.usb3-phy.3: Looking up phy-supply from device tree
[    1.110635] phy phy-ff470000.usb3-phy.3: Looking up phy-supply property in node /[email protected]/[email protected] failed
[    1.112207] rockchip-u3phy ff470000.usb3-phy: Rockchip u3phy initialized successfully
[    1.618779] usbcore: registered new interface driver cdc_ether
[    1.619676] usbcore: registered new interface driver rndis_host
[    1.622431] phy phy-ff470000.usb3-phy.2: u3phy u2 power on
[    1.623213] phy phy-ff470000.usb3-phy.3: u3phy u3 power on
[    1.624895] dwc2 ff580000.usb: Looking up vusb_d-supply from device tree
[    1.624915] dwc2 ff580000.usb: Looking up vusb_d-supply property in node /[email protected] failed
[    1.624933] ff580000.usb supply vusb_d not found, using dummy regulator
[    1.625948] dwc2 ff580000.usb: Looking up vusb_a-supply from device tree
[    1.625966] dwc2 ff580000.usb: Looking up vusb_a-supply property in node /[email protected] failed
[    1.625981] ff580000.usb supply vusb_a not found, using dummy regulator
[    1.782396] dwc2 ff580000.usb: DWC OTG Controller
[    1.783052] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1
[    1.794720] dwc2 ff580000.usb: irq 40, io mem 0x00000000
[    1.806352] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.817899] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.829376] usb usb1: Product: DWC OTG Controller
[    1.840537] usb usb1: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 dwc2_hsotg
[    1.852021] usb usb1: SerialNumber: ff580000.usb
[    1.924423] ehci-platform ff5c0000.usb: EHCI Host Controller
[    1.935841] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 2
[    1.947351] ehci-platform ff5c0000.usb: irq 41, io mem 0xff5c0000
[    1.964182] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00
[    1.975431] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    1.986415] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.997293] usb usb2: Product: EHCI Host Controller
[    2.007844] usb usb2: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 ehci_hcd
[    2.018626] usb usb2: SerialNumber: ff5c0000.usb
[    2.072398] ohci-platform ff5d0000.usb: Generic Platform OHCI controller
[    2.082934] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3
[    2.093459] ohci-platform ff5d0000.usb: irq 42, io mem 0xff5d0000
[    2.158419] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    2.168795] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.179236] usb usb3: Product: Generic Platform OHCI controller
[    2.189540] usb usb3: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 ohci_hcd
[    2.199964] usb usb3: SerialNumber: ff5d0000.usb
[    2.275864] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[    2.286667] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.297596] usb usb4: Product: xHCI Host Controller
[    2.308371] usb usb4: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 xhci-hcd
[    2.319431] usb usb4: SerialNumber: xhci-hcd.8.auto
[    2.376856] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.388508] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
[    2.400005] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.411566] usb usb5: Product: xHCI Host Controller
[    2.422872] usb usb5: Manufacturer: Linux 4.4.77-rockchip-ayufan-136 xhci-hcd
[    2.434506] usb usb5: SerialNumber: xhci-hcd.8.auto
[    2.472223] usbcore: registered new interface driver usbtouchscreen
[    2.719678] usbcore: registered new interface driver uvcvideo
[    2.841823] usbcore: registered new interface driver bfusb
[    2.853276] usbcore: registered new interface driver btusb
[    3.068897] of_get_named_gpiod_flags: parsed 'gpios' property of node '/switches/usb-switch[0]' - status (0)
[    3.084684] usbcore: registered new interface driver usbhid
[    3.092108] usbhid: USB HID core driver
[    3.099617] usbcore: registered new interface driver snd-usb-audio
[   13.319225] usb 5-1: device not accepting address 2, error -62
[   24.167216] usb 5-1: device not accepting address 3, error -62
[   35.015184] usb 5-1: device not accepting address 4, error -62
[   45.863209] usb 5-1: device not accepting address 5, error -62
[   45.901328] usb usb5-port1: unable to enumerate USB device
Reply
#5
Do a dmesg -wH when the drive is disconnected, and then capture the results when you plug in/power on the drive... shoulve give a better idea what the kernel and drivers think of it.
Reply
#6
Discussion also on: https://github.com/ayufan-rock64/linux-build/issues/140

Only powering off and on the external hard drive a few times seems to make it work. But it doesnt work by default when (re)booting.
Reply
#7
Anyone any ideas? 

It seems to be reproducible by turning on and off the external hard drive a few times:


Code:
[  +0.006130] usb usb5-port1: cannot disable (err = -32)
[  +1.222895] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.007061] usb usb5-port1: cannot disable (err = -32)
[  +1.301986] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.006539] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:26] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.006334] usb usb5-port1: cannot disable (err = -32)
[ +22.915402] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000997] usb usb5-port1: cannot disable (err = -32)
[ +25.746442] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000975] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:27] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000993] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:28] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000994] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:29] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000973] usb usb5-port1: cannot disable (err = -32)
[ +19.414341] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000826] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:30] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000975] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:31] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000989] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:33] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000625] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:34] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000662] usb usb5-port1: cannot disable (err = -32)
[ +41.853443] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001120] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:35] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001126] usb usb5-port1: cannot disable (err = -32)
[ +29.718343] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.000927] usb usb5-port1: cannot disable (err = -32)
[  +1.204267] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001954] usb usb5-port1: cannot disable (err = -32)
[  +9.059169] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001089] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:36] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001125] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:37] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001346] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:38] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001323] usb usb5-port1: cannot disable (err = -32)
[  +1.196744] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001487] usb usb5-port1: cannot disable (err = -32)
[ +38.355296] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001314] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:40] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001371] usb usb5-port1: cannot disable (err = -32)
[ +29.995103] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001101] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:41] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001330] usb usb5-port1: cannot disable (err = -32)
[ +19.989129] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001335] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:42] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.001341] usb usb5-port1: cannot disable (err = -32)
[  +1.202664] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.018718] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:44] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.019053] usb usb5-port1: cannot disable (err = -32)
[ +40.660799] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.018685] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:46] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.019019] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:47] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.006564] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:48] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.018923] usb usb5-port1: cannot disable (err = -32)
[Mar27 20:49] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.019101] usb usb5-port1: cannot disable (err = -32)
[ +16.277967] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.006342] usb usb5-port1: cannot disable (err = -32)
[Mar27 21:30] xhci-hcd xhci-hcd.8.auto: port 0 resume PLC timeout
[  +5.742867] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +5.232322] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +0.218864] usb 5-1: device not accepting address 2, error -62
[Mar27 21:31] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +5.232182] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +0.207003] usb 5-1: device not accepting address 3, error -62
[  +5.409325] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +0.207016] usb 5-1: Device not responding to setup address.
[  +0.206919] usb 5-1: device not accepting address 4, error -71
[  +0.006232] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.006210] usb usb5-port1: cannot disable (err = -32)
[  +5.365865] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +5.216288] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +0.207000] usb 5-1: device not accepting address 5, error -62
[  +0.027109] usb usb5-port1: unable to enumerate USB device
[ +18.534735] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +5.216250] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +0.206943] usb 5-1: device not accepting address 6, error -62
[  +5.395727] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +5.229836] xhci-hcd xhci-hcd.8.auto: Timeout while waiting for setup device command
[  +0.218966] usb 5-1: device not accepting address 7, error -62
[  +0.018411] xhci-hcd xhci-hcd.8.auto: Cannot set link state.
[  +0.018858] usb usb5-port1: cannot disable (err = -32)
[Mar27 21:32] usb 5-1: new SuperSpeed USB device number 8 using xhci-hcd
[  +0.029930] usb 5-1: New USB device found, idVendor=174c, idProduct=55aa
[  +0.018513] usb 5-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  +0.013358] usb 5-1: Product: External HDD
[  +0.006015] usb 5-1: Manufacturer: 01234567890123456789012345678901234567890123
[  +0.006308] usb 5-1: SerialNumber: 201308070213
[  +0.059266] usb-storage 5-1:1.0: USB Mass Storage device detected
[  +0.007795] usb-storage 5-1:1.0: Quirks match for vid 174c pid 55aa: 400000
[  +0.006389] scsi host0: usb-storage 5-1:1.0
[  +0.006746] usbcore: registered new interface driver usb-storage
[  +0.010794] usbcore: registered new interface driver uas
[  +6.364552] scsi 0:0:0:0: Direct-Access     WDC WD32 01ABYS-01B9A0    13.0 PQ: 0 ANSI: 5
[  +0.007974] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[  +0.007000] sd 0:0:0:0: [sda] Write Protect is off
[  +0.006170] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[  +0.000435] sd 0:0:0:0: [sda] No Caching mode page found
[  +0.006158] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  +0.080574]  sda: sda1
[  +0.007636] sd 0:0:0:0: [sda] Attached SCSI disk
[  +1.791350] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl
[Mar27 21:33] ip6_tables: (C) 2000-2006 Netfilter Core Team
Reply
#8
I bought another external HD (WD Elements Desktop) but there seems the be the same problem.

So it isnt a problem with this specific external HD.


Any help?

As is this post: https://forum.pine64.org/showthread.php?...3#pid34403

With the stretch-minimal-rock64-0.6.28-197-arm64.img image the usb harddrive seems to be working without problems.
Reply
#9
Are you connecting the drive via USB3?

Try connecting it to the USB2 ports and see what results you get. I've found the USB3 implementation on Linux/OVM to be very temperamental. The only thing I have found to work without an issue is my ORICO drive enclosure.

I just tried a Seagate Expansion Desktop Drive (2TB version). This is not recognise at boot, but if I flip the power off and on again to the drive, it is then recognised, can be mounted and works without issue, I do get one error thrown to the logs as follows....
Code:
[   48.758215] usb 5-1: new SuperSpeed USB device number 2 using xhci-hcd
[   48.770282] usb 5-1: New USB device found, idVendor=0bc2, idProduct=3321
[   48.770311] usb 5-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[   48.770332] usb 5-1: Product: Expansion Desk
[   48.770352] usb 5-1: Manufacturer: Seagate
[   48.770371] usb 5-1: SerialNumber: NA4KN4P8
[   48.879816] usbcore: registered new interface driver usb-storage
[   48.901411] scsi host0: uas
[   48.901830] usbcore: registered new interface driver uas
[   48.905890] scsi 0:0:0:0: Direct-Access     Seagate  Expansion Desk   0604 PQ: 0 ANSI: 6
[   48.907634] sd 0:0:0:0: [sda] Spinning up disk...
[   49.908061] .......ready
[   55.914183] sd 0:0:0:0: [sda] 488378645 4096-byte logical blocks: (2.00 TB/1.82 TiB)
[   55.914209] sd 0:0:0:0: [sda] 16384-byte physical blocks
[   55.932960] sd 0:0:0:0: [sda] Write Protect is off
[   55.932997] sd 0:0:0:0: [sda] Mode Sense: 4f 00 00 00
[   55.933465] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   55.933658] xhci-hcd xhci-hcd.8.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[   55.935075] xhci-hcd xhci-hcd.8.auto: @00000000f3866720 00000000 00000000 1b000000 01038001
[   55.962435]  sda: sda1
[   55.965923] sd 0:0:0:0: [sda] Attached SCSI disk

When I plug it into the USB2 ports, it recognised as boot and is immediately available with no error thrown.

I have another drive enclosure which is recognised but throws lots of "xhci-hcd xhci-hcd.8.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring" errors, but I made this behave by adding a quirks option for the kernel module "options usb-storage quirks=0480:b202:u" I'm no kernel or device driver expert, but this option forces the USB driver to set the device class to "usb-storage" for USB device 0480:b202. I read a post on here suggesting you blacklist the UAS kernel module, but it did not fix the problem with that enclosure.

I'll play around a bit more with the Seagate drive over the following days to see if I can get anywhere with it.
Reply
#10
Blacklisting UAS for WD and Seagate of the shelf enclosures usually fixes a lot of issues with USB3, current models seem to contain USB3/SATA bridges that need quirks to work with Linux's XHCI driver and UAS.
Come have a chat in the Pine A64 IRC channel >>
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Problem with time in rock64 gedas07 2 172 11-12-2018, 12:07 PM
Last Post: gedas07
  WiFi on Armbian problem scalextrix 14 502 09-08-2018, 01:13 AM
Last Post: scalextrix
  xrdp problem with Rock64 cenicero 2 218 08-07-2018, 12:42 PM
Last Post: cenicero
  ROCK64 NAS problem wjburl 5 534 07-17-2018, 11:51 AM
Last Post: KeithJohnAlger
Sad Rock64 crash randomly during usb 3 copy with RAID1 drive phalae 23 4,093 05-30-2018, 06:20 AM
Last Post: AnythingIsFine
  [PROBLEM SOLVED] Distcc Help cooker 2 198 05-01-2018, 05:35 AM
Last Post: cooker
  boot emmc, trying to access SD Drive E.G 0 189 04-13-2018, 09:05 PM
Last Post: E.G
  Help pls~Desktop (xfce4/lxde/gnome/i3) installation problem. Install_desktop.sh faild yours_david 0 299 04-10-2018, 11:41 PM
Last Post: yours_david
  bionic 4.4.120-rockchip-aynfan-209 scp problem on large file edwinbmiller 0 134 04-05-2018, 01:00 PM
Last Post: edwinbmiller
  Read-only problem mikedhoore 4 239 04-04-2018, 11:53 PM
Last Post: mikedhoore

Forum Jump:


Users browsing this thread: 1 Guest(s)