Date: Sun, 18 Feb 2018 18:17:21 -0500 From: Ian FREISLICH <ian.freislich@capeaugusta.com> To: Warner Losh <imp@bsdimp.com> Cc: Hans Petter Selasky <hps@selasky.org>, FreeBSD Current <current@freebsd.org>, Warner Losh <imp@freebsd.org> Subject: Re: r329501 devd doesn't find USB devices Message-ID: <80b6155f-fd24-950d-8b52-6c935fcbee25@capeaugusta.com> In-Reply-To: <56798d16-ddc7-6abd-40df-8a8f552140c6@capeaugusta.com> References: <2c5d435c-54b1-fbd8-f695-de3dcc6259f1@capeaugusta.com> <CANCZdfqb82FhpRKB1934_a01mCtSCro4qXcKTAuGgfKyz_7BjA@mail.gmail.com> <edbd5ae4-89c6-74ca-9a8b-3c6ce9c467dd@capeaugusta.com> <d69f4565-768d-c08b-286b-987e16507516@selasky.org> <514d3c3f-996d-6299-396a-ae161e6f730b@capeaugusta.com> <CANCZdfruMPwc5zRYPey2qhnZNYb69wPCs_1G_70uvWV1fqfbaQ@mail.gmail.com> <56798d16-ddc7-6abd-40df-8a8f552140c6@capeaugusta.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@capeaugusta.com >> <mailto:ian.freislich@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@capeaugusta.com >> <mailto:ian.freislich@capeaugusta.com> >> <mailto:ian.freislich@capeaugusta.com >> <mailto:ian.freislich@capeaugusta.com>>> >> >>> wrote: >> >>> >> >>> =C2=A0=C2=A0=C2=A0=C2=A0 Hi >> >>> >> >>> =C2=A0=C2=A0=C2=A0=C2=A0 Since devmatch some of my USB devices n= o longer get >> their drivers >> >>> =C2=A0=C2=A0=C2=A0=C2=A0 loaded.=C2=A0 It's not clear from UPDAT= ING whether I needed to do >> >>> anything >> >>> =C2=A0=C2=A0=C2=A0=C2=A0 beyond building and installing kernel a= nd world as well as >> >>> updating >> >>> =C2=A0=C2=A0=C2=A0=C2=A0 /etc.=C2=A0 There was reference to remo= ving /etc/devd/usb.conf in >> >>> another >> >>> =C2=A0=C2=A0=C2=A0=C2=A0 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 >> >> *.>=3Dnotice=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 /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=3D0 md=3DHOST spd=3DS= UPER >> (5.0Gbps) pwr=3DSAVE (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=3D0 md=3DH= OST >> spd=3DHIGH (480Mbps) pwr=3DON (500mA) >> ugen0.3: <vendor 0x8087 product 0x0a2b> at usbus0, cfg=3D0 md=3DHOST >> spd=3DFULL (12Mbps) pwr=3DON (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=3D0 md=3DHOST spd=3DF= ULL >> (12Mbps) pwr=3DON (100mA) >> ugen0.5: <RAPOO RAPOO 2.4G Wireless Device> at usbus0, cfg=3D0 md=3D= HOST >> spd=3DFULL (12Mbps) pwr=3DON (100mA) >> ugen0.6: <CMI USB 101001000 LAN> at usbus0, cfg=3D0 md=3DHOST spd=3D= SUPER >> (5.0Gbps) pwr=3DON (72mA) >> >> After loading ums and ukbd: >> >> ugen0.5: <RAPOO RAPOO 2.4G Wireless Device> at usbus0, cfg=3D0 md=3D= HOST >> spd=3DFULL (12Mbps) pwr=3DON (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 --=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80b6155f-fd24-950d-8b52-6c935fcbee25>