Buffalo WBMR-HP-G300H (lantiq/xway): can't see USB sticks

Hello, I have a Buffalo WBMR-HP-G300H running the latest LEDE SNAPSHOT
r4357-acc5ab6 / LuCI branch (git-17.152.82962-a9e8376).

My problem: I am not able to use a USB stick with it. When I plug the stick, no
/dev/sda* appears.

$ ls /dev/sd*
ls: /dev/sd*: No such file or directory

I think I have installed at least the low level packages: kmod-usb-storage
kmod-scsi-generic block-mount kmod-fs-ext4 kmod-fs-vfat e2fsprogs.

I also have installed a couple kmod-fs- : vfat and ext4 (the stick is in fat32
format, but I will gladly reformat it as ext3 once I can see it).

Here is an excerpt of relevant lines in the syslog:

Thu Jun  8 17:52:32 2017 kern.info kernel: [    0.223371] usbcore: registered new interface driver usbfs
Thu Jun  8 17:52:32 2017 kern.info kernel: [    0.228943] usbcore: registered new interface driver hub
Thu Jun  8 17:52:32 2017 kern.info kernel: [    0.234310] usbcore: registered new device driver usb
Thu Jun  8 17:52:32 2017 kern.info kernel: [    5.293316] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Thu Jun  8 17:52:32 2017 kern.notice kernel: [    5.312007] SCSI subsystem initialized
Thu Jun  8 17:52:32 2017 kern.info kernel: [    5.333377] usbcore: registered new interface driver usb-storage
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.694841] usbcore: registered new interface driver ums-alauda
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.711456] usbcore: registered new interface driver ums-cypress
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.723925] usbcore: registered new interface driver ums-datafab
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.732313] usbcore: registered new interface driver ums-freecom
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.741053] usbcore: registered new interface driver ums-isd200
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.749930] usbcore: registered new interface driver ums-jumpshot
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.758475] usbcore: registered new interface driver ums-karma
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.768073] usbcore: registered new interface driver ums-sddr09
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.776840] usbcore: registered new interface driver ums-sddr55
Thu Jun  8 17:52:32 2017 kern.info kernel: [  157.786154] usbcore: registered new interface driver ums-usbat
Thu Jun  8 17:53:41 2017 daemon.notice procd: /etc/rc.d/S96led: setting up led led_usb

I tried inserting the stick after boot, or booting with the stick in. It makes no difference.

Apparently, there are some problems with libusb:

$ lsusb
unable to initialize libusb: -99

Would anyone have any idea of what I can try? I'm willing to do any necessary tests.

as this tutorial suggests install USB 2.0 Support (https://medium.com/openwrt-iot/lede-openwrt-setting-up-usb-storage-support-adec9c0d484e)

opkg update
opkg install kmod-usb2
insmod ehci-hcd
opkg install usbutils

If it still does not work Show us output of this command "dmesg"

Other then this, i know it's silly but make sure your USB stick works.

Thanks for your reply, matemana!

The USB stick does work; I'd had the same doubt.
I've followed many tutorials to the letter - including the one you suggested - without success for nearly one week.

Just today I solved the problem because I found some buried post mentioning kmod-usb-dwc-otg. I have no idea what it does, but it can't hurt, right? But I didn't find that package in menuconfig. I did find a similarly named package: kmod-usb-dwc2. I compiled it into my kernel (couldn't opkg/insmod it for some reason) and voila, it works.

I was notified about your reply just while I was thinking I should edit my thread for future reference :slight_smile:

Thank you again!

TL;DR kmod-usb-dwc2 is needed too.

Nice to see that you fixed your issue. I searched and turns out dwc2 is a new implementation of otg.
I think stuff like this should be preinstalled on routers that have USB2 support.

Agreed. I filed an issue here: https://bugs.lede-project.org/index.php?do=details&task_id=838 . Maybe it'll get fixed.