On 2017-07-19 17:32, Stefan Sperling wrote:
On Wed, Jul 19, 2017 at 12:02:39PM -0500, Abel Abraham Camarillo Ojeda
wrote:
On Wed, Jul 19, 2017 at 11:52 AM, Stefan Sperling <[email protected]>
wrote:
> On Wed, Jul 19, 2017 at 11:48:39AM -0500, Abel Abraham Camarillo Ojeda wrote:
>> On Wed, Jul 19, 2017 at 11:28 AM, Stefan Sperling <[email protected]> wrote:
>> > On Wed, Jul 19, 2017 at 11:21:09AM -0500, Abel Abraham Camarillo Ojeda
wrote:
>> >> urtwn0: timeout waiting for firmware readiness
>> >> urtwn0: timeout waiting for firmware readiness
>> >> urtwn0: timeout waiting for firmware readiness
>> >
>> > I have the same RTL8188EU adapter you use, and it works for me.
>> > Since the same adapter also works for you in another machine,
>> > I suspect there is a USB support issue with your affected machine.
>> > Perhaps the device is not getting sufficient power to operate?
>>
>> That would be OpeBSD + machine specific?
>
> Yes, perhaps. OpenBSD and Windows do not use the same device drivers.
Any Idea about how to debug/get more info on this?
No, sorry. I am not an expert on USB.
If I understood you right, there are situations when you have an USB
device plugged in when you power on your computer, and what happens is
that the device is not detected whatsoever by OpenBSD on boot (it's not
mentioned in the dmesg), and to work around the problem you unplug the
USB device and then re-plug it, and at first then it's taken in use by
OpenBSD (and listed in the dmesg):
If so, these two posts from mpi@ discussing the use and debugging of the
XHCI/USB stack could be useful to you, these are suggestions for how to
debug the XHCI/USB stack so that you can contribute useful debug data to
the mailing list:
http://marc.info/?t=149640729500001&r=1&w=2
https://marc.info/?l=openbsd-misc&m=149658807922576&w=2 ()
http://marc.info/?t=149636206700001&r=1&w=2
I stumbled into this when I suffered the anomaly that USB NIC:s that had
been plugged in since power-on, not were identified by OpenBSD at boot
in certain circumstances. In particular, if I would plugin two USB NIC:s
(say an AXEN and a CDCE RTL8153) on the USB3 plugs on my Asrock Xeon
motherboard, it would not be unusual that only one of them were
identified at boot. I think my temporary workaround was to switch over
to use USB2 only. It's still on my TODO to debug the problem further -
mpi@ needed XHCI_DEBUG and/or UHUB_DEBUG debug output data to be able to
get to any conclusions.
Tinker
