You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Log is provided in link below please don't skip this! The
Bought a new external USB 3.0 enclosure for SMB. Installed 2TB drive in said enclosure, hooked it up and cannot get it to be recognized when plugged into the USB 3.0 port on my Asus AC68U. It does work on the 2.0 port. And it does work on 3.0 port if i use a 2.0 hub. strange indeed! also note that the USB 3.0 port does correctly identify and mount 2 other 3.0 drives I have.
I did try editing /etc/modules.d/usb-storage to add quirks=VID:PID:u after usb-storage (on the same line). VID/PID must be of your UAS device. kmod-usb-storage-uas should be installed. Reboot for the changes to take effect.
But this this not work.
output of lsusb:
root@AC68U-43B8:~# lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux 5.4.143 ohci_hcd Generic Platform OHCI controller
Bus 004 Device 002: ID 174c:55aa RSH-339 ASM1153E
Bus 004 Device 001: ID 1d6b:0003 Linux 5.4.143 xhci-hcd xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux 5.4.143 ehci_hcd EHCI Host Controller
Bus 003 Device 001: ID 1d6b:0002 Linux 5.4.143 xhci-hcd xHCI Host Controller
the device in question is this ID 174c:55aa RSH-339 ASM1153E
root@AC68U-43B8:~# lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=, Driver=, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/0p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/2p, 480M
Keep in mind this device works on my USB 2.0 port as it should, but not the 3.0 port. However if I flash Tomato firmware to my AC68U then this drive has no issues being mounted while plugged into the USB 3.0 port. If I go back to OpenWRT, as I am now, it once again refuses to mount when plugged into the 3.0 port.
The text was updated successfully, but these errors were encountered:
Make WiFi Great Again:
Log is provided in link below please don't skip this! The
Bought a new external USB 3.0 enclosure for SMB. Installed 2TB drive in said enclosure, hooked it up and cannot get it to be recognized when plugged into the USB 3.0 port on my Asus AC68U. It does work on the 2.0 port. And it does work on 3.0 port if i use a 2.0 hub. strange indeed! also note that the USB 3.0 port does correctly identify and mount 2 other 3.0 drives I have.
See here for more info: https://forum.openwrt.org/t/openwrt-21-02-asus-ac68u-unable-to-see-usb-3-0-drives/107161/5
and here: https://bugs.openwrt.org/index.php?do=details&task_id=1862
I did try editing /etc/modules.d/usb-storage to add quirks=VID:PID:u after usb-storage (on the same line). VID/PID must be of your UAS device. kmod-usb-storage-uas should be installed. Reboot for the changes to take effect.
But this this not work.
output of lsusb:
root@AC68U-43B8:~# lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux 5.4.143 ohci_hcd Generic Platform OHCI controller
Bus 004 Device 002: ID 174c:55aa RSH-339 ASM1153E
Bus 004 Device 001: ID 1d6b:0003 Linux 5.4.143 xhci-hcd xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux 5.4.143 ehci_hcd EHCI Host Controller
Bus 003 Device 001: ID 1d6b:0002 Linux 5.4.143 xhci-hcd xHCI Host Controller
the device in question is this ID 174c:55aa RSH-339 ASM1153E
root@AC68U-43B8:~# lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=, Driver=, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/0p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/2p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/2p, 480M
Keep in mind this device works on my USB 2.0 port as it should, but not the 3.0 port. However if I flash Tomato firmware to my AC68U then this drive has no issues being mounted while plugged into the USB 3.0 port. If I go back to OpenWRT, as I am now, it once again refuses to mount when plugged into the 3.0 port.
The text was updated successfully, but these errors were encountered: