On 16/10/14(Thu) 00:07, Carlin Bingham wrote: > On Tue, 14 Oct 2014, at 10:24 AM, Carlin Bingham wrote: > > On Tue, 14 Oct 2014, at 09:05 AM, Martin Pieuchot wrote: > > > On 14/10/14(Tue) 06:40, Carlin Bingham wrote: > > > > I have booted the latest (11/10/14) snapshot install56.fs from a USB > > > > drive and want to install it to an external USB drive but the drive (and > > > > other USB devices) are not being recognised. No kernel messages are > > > > being displayed when USB devices are added/removed, and if I run `sh > > > > MAKEDEV sd2` it gives "device not configured" when trying to mount it. > > > > > > > > In the installer with 5.5 release, it just works and kernel messages are > > > > displayed as expected. > > > > > > > > Has something changed that would cause this? Or is there something I > > > > need to do now to bring USB up? > > > > > > > > > > > > This is on a Lenovo T440p. > > > > > > > > dmesg for 5.5 and the snapshot (both from the install shell): > > > > > > [...] > > > > > > > OpenBSD 5.6-current (RAMDISK_CD) #380: Sat Oct 11 16:04:03 MDT 2014 > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > > > > [...] > > > > uhub2 at uhub0 port 1 "vendor 0x8087 product 0x8008" rev 2.00/0.04 addr > > > > 2 > > > > uhub3 at uhub1 port 1 "vendor 0x8087 product 0x8000" rev 2.00 > > > > SIZE 0.04 addr 2 > > > ^^^^ > > > This is really weird. Is it really what you're seeing? Apparently > > > you don't get any interrupt from your rate-matching hub. That would > > > explain why you don't see any new "blue lines" when connecting a > > > device. > > > > > > Do you have an option in your BIOS to toggle USB3 support? Does it make > > > any difference? > > > > In BIOS, USB 3.0 Mode was set to [AUTO], changing that to [DISABLED] > > fixed it and, as expected, changing it to [ENABLED] breaks it. > > > > Thanks for your help. > > > > Just out of curiosity, what would have changed that would cause USB 3.0 > Mode being set to [AUTO] no longer work when it did work fine in 5.5?
I've no idea, I don't know what the BIOS is doing and I don't have such hardware. If you want you can try to find which change introduced that, that might be useful... who knows. Martin
