Re: r329501 devd doesn't find USB devices

From: Ian FREISLICH <ian.freislich_at_capeaugusta.com>
Date: Sun, 18 Feb 2018 18:17:21 -0500
On 02/18/18 18:01, Ian FREISLICH wrote:
> On 02/18/18 14:59, Warner Losh wrote:
>> On Sun, Feb 18, 2018 at 6:32 AM, Ian FREISLICH
>> <ian.freislich_at_capeaugusta.com
>> <mailto:ian.freislich_at_capeaugusta.com>> wrote:
>>
>>     On 02/18/18 02:23, Hans Petter Selasky wrote:
>>     > On 02/18/18 05:14, Ian FREISLICH wrote:
>>     >> On 02/17/18 22:48, Warner Losh wrote:
>>     >>> On Feb 17, 2018 8:24 PM, "Ian FREISLICH"
>>     >>> <ian.freislich_at_capeaugusta.com
>>     <mailto:ian.freislich_at_capeaugusta.com>
>>     <mailto:ian.freislich_at_capeaugusta.com
>>     <mailto:ian.freislich_at_capeaugusta.com>>>
>>     >>> wrote:
>>     >>>
>>     >>>      Hi
>>     >>>
>>     >>>      Since devmatch some of my USB devices no longer get
>>     their drivers
>>     >>>      loaded.  It's not clear from UPDATING whether I needed to do
>>     >>> anything
>>     >>>      beyond building and installing kernel and world as well as
>>     >>> updating
>>     >>>      /etc.  There was reference to removing /etc/devd/usb.conf in
>>     >>> another
>>     >>>      thread but its presence or lack thereof makes no difference.
>>     >>>
>>     >>>
>>     >>> I assume you've fully updated including /etc.
>>     >>
>>     >> In as much as 'mergemaster -Ui' fully updates /etc
>>     >>
>>     >>> If you can uncomment the devd lines in syslog.conf, touch
>>     >>> /var/log/devd.log and reboot. Once you are up again, please
>>     send me
>>     >>> /var/log/devd.conf.
>>     >>
>>     >> Assuming you mean these lines:
>>     >>
>>     >> !devd
>>     >> *.>=notice                                      /var/log/devd.log
>>     >>
>>     >> devd produced zero logs on reboot and restart.
>>     >
>>     > Can you run:
>>     >
>>     > usbconfig show_ifdrv
>>     >
>>     > Maybe the wrong driver captured your device?
>>
>>     ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER
>>     (5.0Gbps) pwr=SAVE (0mA)
>>     ugen0.1.0: uhub0: <0x8086 XHCI root HUB, class 9/0, rev
>>     3.00/1.00, addr 1>
>>     ugen0.2: <AzureWave USB2.0 VGA UVC WebCam> at usbus0, cfg=0 md=HOST
>>     spd=HIGH (480Mbps) pwr=ON (500mA)
>>     ugen0.3: <vendor 0x8087 product 0x0a2b> at usbus0, cfg=0 md=HOST
>>     spd=FULL (12Mbps) pwr=ON (100mA)
>>     ugen0.3.0: ubt0: <vendor 0x8087 product 0x0a2b, class 224/1, rev
>>     2.00/0.10, addr 2>
>>     ugen0.4: <ELAN ELANFingerprint> at usbus0, cfg=0 md=HOST spd=FULL
>>     (12Mbps) pwr=ON (100mA)
>>     ugen0.5: <RAPOO RAPOO 2.4G Wireless Device> at usbus0, cfg=0 md=HOST
>>     spd=FULL (12Mbps) pwr=ON (100mA)
>>     ugen0.6: <CMI USB 101001000 LAN> at usbus0, cfg=0 md=HOST spd=SUPER
>>     (5.0Gbps) pwr=ON (72mA)
>>
>>     After loading ums and ukbd:
>>
>>     ugen0.5: <RAPOO RAPOO 2.4G Wireless Device> at usbus0, cfg=0 md=HOST
>>     spd=FULL (12Mbps) pwr=ON (100mA)
>>     ugen0.5.0: ukbd0: <RAPOO RAPOO 2.4G Wireless Device, class 0/0, rev
>>     1.10/10.01, addr 5>
>>     ugen0.5.1: ums0: <RAPOO RAPOO 2.4G Wireless Device, class 0/0, rev
>>     1.10/10.01, addr 5>
>>
>>
>> So what happens if you build these drivers into the kernel vs loading
>> them?

It just works, which is the fix I'm using for now.

Ian

-- 
Received on Sun Feb 18 2018 - 22:17:24 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:15 UTC