Dear Oliver, I'm not really sure what happened, but now USB appears to be working perfectly well... In the meantime, since my last checks, I simply updated Tumbleweed and entered the command below as root (I rebooted twice since then: USB still working!). I didn't find anything relevant in the Tumbleweed updates, only this one is related to USB, but the only commit doesn't seem to be fixing anything at runtime: ==== usb_modeswitch ==== Subpackages: usb_modeswitch-data - Avoid a race in make install, which lead to packaging a truncated usb_modeswitch_dispatcher script. Fixes boo#998641 But I dont think the command below is still active after a reboot (is it?) and it seems just to activate some more debugging, so I really don't understand how this happened! Sorry, this must be a quite frustrating report... Cheers, Pierre. Le lundi 19 septembre 2016, 11:22:52 NZST Oliver Neukum a écrit : > On Sun, 2016-09-18 at 19:48 +1200, Pierre de Villemereuil wrote: > > Dear kernel devs, > > > > I'm using openSUSE Tumbleweed (kernel 4.7.2-2-default) on an ASUS Vivobook > > Flip TP301UA-C4028T, see here for specs: > > https://www.asus.com/Notebooks/ASUS-VivoBook-Flip-TP301UA/specifications/ > > > > Since my install in July, USB hot-plug (a.k.a. plug'n'play) is not > > working. To make any USB device working (I tested many USB keys, a > > slideshow remote control and a mouse), it has to be plugged on boot up or > > wake up from suspend. Using the following command also make the system > > aware that USB is connected: udevadm trigger > > > > More information can be found on the following thread on the openSUSE > > forums: > > https://forums.opensuse.org/showthread.php/519926-No-USB-device-detected > Basically dmesg should show a hotplug. What happens if you unload and > reload the xhci_hcd modules? > > And please do > > echo "module xhci_hcd +mpf" > /sys/kernel/debug/dynamic_debug/control > > (as root) and check dmesg again. > > Regards > Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
