Date: Sun, 18 Feb 2018 18:58:04 -0500 From: Ian FREISLICH <ian.freislich@capeaugusta.com> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Current <current@freebsd.org>, Warner Losh <imp@freebsd.org> Subject: Re: r329501 devd doesn't find USB devices Message-ID: <8212a950-3d10-0ac6-f60a-f5dc8b6f10ae@capeaugusta.com> In-Reply-To: <CANCZdfpNLL=242ySMyhSg%2BeF7cNnCJ1APH6j1TGU7Cfr_ro9LQ@mail.gmail.com> References: <2c5d435c-54b1-fbd8-f695-de3dcc6259f1@capeaugusta.com> <CANCZdfqb82FhpRKB1934_a01mCtSCro4qXcKTAuGgfKyz_7BjA@mail.gmail.com> <edbd5ae4-89c6-74ca-9a8b-3c6ce9c467dd@capeaugusta.com> <CANCZdfpDRUgJ8x1i=TC7Qv8Lx0q48_%2Bi9JOFT3hXLAdvLmFscw@mail.gmail.com> <0a0f8471-87e4-0048-aebc-a84014a9faee@capeaugusta.com> <CANCZdfqFPP-x=e1FEimP6mwagwYkQCG_RoivikiraoNWO%2B0anQ@mail.gmail.com> <1fbaea27-a1ef-31f1-309f-1db99f951122@capeaugusta.com> <CANCZdfpNLL=242ySMyhSg%2BeF7cNnCJ1APH6j1TGU7Cfr_ro9LQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/18/18 18:49, Warner Losh wrote: > On Sun, Feb 18, 2018 at 4:45 PM, Ian FREISLICH > <ian.freislich@capeaugusta.com <mailto:ian.freislich@capeaugusta.com>> > wrote: > > On 02/18/18 18:17, Warner Losh wrote: >> On Sun, Feb 18, 2018 at 4:12 PM, Ian FREISLICH >> <ian.freislich@capeaugusta.com >> <mailto:ian.freislich@capeaugusta.com>> wrote: >> >> On 02/18/18 15:09, Warner Losh wrote: >>> On Sat, Feb 17, 2018 at 9:14 PM, Ian FREISLICH >>> <ian.freislich@capeaugusta.com >>> <mailto:ian.freislich@capeaugusta.com>> 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>> wrote: >>>> >>>> Hi >>>> >>>> Since devmatch some of my USB devices no longer get >>>> their drivers >>>> loaded.=C2=A0 It's not clear from UPDATING whether I >>>> needed to do anything >>>> beyond building and installing kernel and world as >>>> well as updating >>>> /etc.=C2=A0 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 >>> *.>=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. >>> >>> >>> There should be a lot of output... one line per device >>> that's attached...=C2=A0 Did you create /var/log/devd.log befor= e >>> reboot? Is your /dev/log persistent across boots? >> >> Lots of output after I changed the priority from 'notice' to >> 'debug' in syslogd.conf.=C2=A0 Might want to fix that in >> src/etc/syslogd.conf. >> >> 1. Startup: >> >> Feb 18 17:43:44 zen devd: Pushing table >> Feb 18 17:43:44 zen devd: Parsing /etc/devd.conf >> Feb 18 17:43:44 zen devd: Parsing files in /etc/devd >> Feb 18 17:43:44 zen devd: Parsing /etc/devd/devmatch.conf >> Feb 18 17:43:44 zen devd: Parsing /etc/devd/asus.conf >> Feb 18 17:43:44 zen devd: Parsing /etc/devd/hyperv.conf >> Feb 18 17:43:44 zen devd: Parsing /etc/devd/uath.conf >> Feb 18 17:43:44 zen devd: Parsing /etc/devd/ulpt.conf >> Feb 18 17:43:44 zen devd: Parsing /etc/devd/usb.conf >> Feb 18 17:43:44 zen devd: Parsing /etc/devd/zfs.conf >> Feb 18 17:43:44 zen devd: Parsing files in /usr/local/etc/devd >> Feb 18 17:43:44 zen devd: Parsing /usr/local/etc/devd/cups.conf >> Feb 18 17:43:44 zen devd: Parsing >> /usr/local/etc/devd/webcamd.co <http://webcamd.co>nf >> Feb 18 17:43:44 zen devd: Calling daemon >> >> >> 2. Inserting the USB-C NIC: >> >> Feb 18 18:05:53 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.6.0' >> Feb 18 18:05:53 zen devd: Pushing table >> Feb 18 18:05:53 zen devd: Processing notify event >> Feb 18 18:05:53 zen devd: Popping table >> Feb 18 18:05:53 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dugen0.6' >> Feb 18 18:05:53 zen devd: Pushing table >> Feb 18 18:05:53 zen devd: Processing notify event >> Feb 18 18:05:53 zen devd: Popping table >> Feb 18 18:05:53 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.6.1' >> Feb 18 18:05:53 zen devd: Pushing table >> Feb 18 18:05:53 zen devd: Processing notify event >> Feb 18 18:05:53 zen devd: Popping table >> Feb 18 18:05:53 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.6.2' >> Feb 18 18:05:53 zen devd: Pushing table >> Feb 18 18:05:53 zen devd: Processing notify event >> Feb 18 18:05:53 zen devd: Popping table >> Feb 18 18:05:53 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.6.3' >> Feb 18 18:05:53 zen devd: Pushing table >> Feb 18 18:05:53 zen devd: Processing notify event >> Feb 18 18:05:53 zen devd: Popping table >> Feb 18 18:05:53 zen devd: Processing event '!system=3DUSB >> subsystem=3DDEVICE type=3DATTACH ugen=3Dugen0.6 cdev=3Dugen0.6 >> vendor=3D0x0bda product=3D0x8153 devclass=3D0x00 devsubclass=3D0= x00 >> sernum=3D"000001" release=3D0x3000 mode=3Dhost port=3D13 parent= =3Dugen0.1' >> Feb 18 18:05:53 zen devd: Pushing table >> Feb 18 18:05:53 zen devd: Processing notify event >> Feb 18 18:05:53 zen devd: Popping table >> Feb 18 18:05:53 zen devd: Processing event '!system=3DUSB >> subsystem=3DINTERFACE type=3DATTACH ugen=3Dugen0.6 cdev=3Dugen0.= 6 >> vendor=3D0x0bda product=3D0x8153 devclass=3D0x00 devsubclass=3D0= x00 >> sernum=3D"000001" release=3D0x3000 mode=3Dhost interface=3D0 >> endpoints=3D3 intclass=3D0xff intsubclass=3D0xff intprotocol=3D0= x00' >> Feb 18 18:05:53 zen devd: Pushing table >> Feb 18 18:05:53 zen devd: Processing notify event >> Feb 18 18:05:53 zen devd: Executing >> '/usr/local/etc/rc.d/webcamd start ugen0.6' >> Feb 18 18:05:53 zen devd: Popping table >> Feb 18 18:05:53 zen devd: Processing event '? at bus=3D0 >> hubaddr=3D1 port=3D13 devaddr=3D6 interface=3D0 ugen=3Dugen0.6 >> vendor=3D0x0bda product=3D0x8153 devclass=3D0x00 devsubclass=3D0= x00 >> devproto=3D0x00 sernum=3D"000001" release=3D0x3000 mode=3Dhost >> intclass=3D0xff intsubclass=3D0xff intprotocol=3D0x00 on uhub0' >> Feb 18 18:05:53 zen devd: Pushing table >> Feb 18 18:05:53 zen devd: Processing nomatch event >> Feb 18 18:05:53 zen devd: Executing '/etc/rc.d/devmatch start >> '? at bus=3D0 hubaddr=3D1 port=3D13 devaddr=3D6 interface=3D0 >> ugen=3Dugen0.6 vendor=3D0x0bda product=3D0x8153 devclass=3D0x00 >> devsubclass=3D0x00 devproto=3D0x00 sernum=3D"000001" release=3D0= x3000 >> mode=3Dhost intclass=3D0xff intsubclass=3D0xff intprotocol=3D0x0= 0 on >> uhub0'' >> Feb 18 18:05:53 zen devd: Popping table >> >> >> 3. Insert USB-3 drive: >> >> Feb 18 18:09:38 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.6.0' >> Feb 18 18:09:38 zen devd: Pushing table >> Feb 18 18:09:38 zen devd: Processing notify event >> Feb 18 18:09:38 zen devd: Popping table >> Feb 18 18:09:38 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dugen0.6' >> Feb 18 18:09:38 zen devd: Pushing table >> Feb 18 18:09:38 zen devd: Processing notify event >> Feb 18 18:09:38 zen devd: Popping table >> Feb 18 18:09:38 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.6.1' >> Feb 18 18:09:38 zen devd: Pushing table >> Feb 18 18:09:38 zen devd: Processing notify event >> Feb 18 18:09:38 zen devd: Popping table >> Feb 18 18:09:38 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.6.2' >> Feb 18 18:09:38 zen devd: Pushing table >> Feb 18 18:09:38 zen devd: Processing notify event >> Feb 18 18:09:38 zen devd: Popping table >> Feb 18 18:09:38 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.6.3' >> Feb 18 18:09:38 zen devd: Pushing table >> Feb 18 18:09:38 zen devd: Processing notify event >> Feb 18 18:09:38 zen devd: Popping table >> Feb 18 18:09:38 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.6.4' >> Feb 18 18:09:38 zen devd: Pushing table >> Feb 18 18:09:38 zen devd: Processing notify event >> Feb 18 18:09:38 zen devd: Popping table >> Feb 18 18:09:40 zen devd: Processing event '!system=3DUSB >> subsystem=3DDEVICE type=3DATTACH ugen=3Dugen0.6 cdev=3Dugen0.6 >> vendor=3D0x0bc2 product=3D0xab24 devclass=3D0x00 devsubclass=3D0= x00 >> sernum=3D"NA7W30KM" release=3D0x0100 mode=3Dhost port=3D13 >> parent=3Dugen0.1' >> Feb 18 18:09:40 zen devd: Pushing table >> Feb 18 18:09:40 zen devd: Processing notify event >> Feb 18 18:09:40 zen devd: Popping table >> Feb 18 18:09:40 zen devd: Processing event '!system=3DUSB >> subsystem=3DINTERFACE type=3DATTACH ugen=3Dugen0.6 cdev=3Dugen0.= 6 >> vendor=3D0x0bc2 product=3D0xab24 devclass=3D0x00 devsubclass=3D0= x00 >> sernum=3D"NA7W30KM" release=3D0x0100 mode=3Dhost interface=3D0 >> endpoints=3D2 intclass=3D0x08 intsubclass=3D0x06 intprotocol=3D0= x50' >> Feb 18 18:09:40 zen devd: Pushing table >> Feb 18 18:09:40 zen devd: Processing notify event >> Feb 18 18:09:40 zen devd: Popping table >> Feb 18 18:09:40 zen devd: Processing event '? at bus=3D0 >> hubaddr=3D1 port=3D13 devaddr=3D6 interface=3D0 ugen=3Dugen0.6 >> vendor=3D0x0bc2 product=3D0xab24 devclass=3D0x00 devsubclass=3D0= x00 >> devproto=3D0x00 sernum=3D"NA7W30KM" release=3D0x0100 mode=3Dhost >> intclass=3D0x08 intsubclass=3D0x06 intprotocol=3D0x50 on uhub0' >> Feb 18 18:09:40 zen devd: Pushing table >> Feb 18 18:09:40 zen devd: Processing nomatch event >> Feb 18 18:09:40 zen devd: Executing '/etc/rc.d/devmatch start >> '? at bus=3D0 hubaddr=3D1 port=3D13 devaddr=3D6 interface=3D0 >> ugen=3Dugen0.6 vendor=3D0x0bc2 product=3D0xab24 devclass=3D0x00 >> devsubclass=3D0x00 devproto=3D0x00 sernum=3D"NA7W30KM" >> release=3D0x0100 mode=3Dhost intclass=3D0x08 intsubclass=3D0x06 >> intprotocol=3D0x50 on uhub0'' >> Feb 18 18:09:40 zen devd: Popping table >> >> >> 4. Inserting the keyboard/mouse: >> >> Feb 18 18:11:04 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.5.0' >> Feb 18 18:11:04 zen devd: Pushing table >> Feb 18 18:11:04 zen devd: Processing notify event >> Feb 18 18:11:04 zen devd: Popping table >> Feb 18 18:11:04 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dugen0.5' >> Feb 18 18:11:04 zen devd: Pushing table >> Feb 18 18:11:04 zen devd: Processing notify event >> Feb 18 18:11:04 zen devd: Popping table >> Feb 18 18:11:04 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.5.1' >> Feb 18 18:11:04 zen devd: Pushing table >> Feb 18 18:11:04 zen devd: Processing notify event >> Feb 18 18:11:04 zen devd: Popping table >> Feb 18 18:11:04 zen devd: Processing event '!system=3DDEVFS >> subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.5.2' >> Feb 18 18:11:04 zen devd: Pushing table >> Feb 18 18:11:04 zen devd: Processing notify event >> Feb 18 18:11:04 zen devd: Popping table >> Feb 18 18:11:04 zen devd: Processing event '!system=3DUSB >> subsystem=3DDEVICE type=3DATTACH ugen=3Dugen0.5 cdev=3Dugen0.5 >> vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 devsubclass=3D0= x00 >> sernum=3D"" release=3D0x1001 mode=3Dhost port=3D2 parent=3Dugen0= .1' >> Feb 18 18:11:04 zen devd: Pushing table >> Feb 18 18:11:04 zen devd: Processing notify event >> Feb 18 18:11:04 zen devd: Popping table >> Feb 18 18:11:04 zen devd: Processing event '!system=3DUSB >> subsystem=3DINTERFACE type=3DATTACH ugen=3Dugen0.5 cdev=3Dugen0.= 5 >> vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 devsubclass=3D0= x00 >> sernum=3D"" release=3D0x1001 mode=3Dhost interface=3D0 endpoints= =3D1 >> intclass=3D0x03 intsubclass=3D0x01 intprotocol=3D0x01' >> Feb 18 18:11:04 zen devd: Pushing table >> Feb 18 18:11:04 zen devd: Processing notify event >> Feb 18 18:11:04 zen devd: Popping table >> Feb 18 18:11:04 zen devd: Processing event '!system=3DUSB >> subsystem=3DINTERFACE type=3DATTACH ugen=3Dugen0.5 cdev=3Dugen0.= 5 >> vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 devsubclass=3D0= x00 >> sernum=3D"" release=3D0x1001 mode=3Dhost interface=3D1 endpoints= =3D1 >> intclass=3D0x03 intsubclass=3D0x01 intprotocol=3D0x02' >> Feb 18 18:11:04 zen devd: Pushing table >> Feb 18 18:11:04 zen devd: Processing notify event >> Feb 18 18:11:04 zen devd: Popping table >> Feb 18 18:11:04 zen devd: Processing event '? at bus=3D0 >> hubaddr=3D1 port=3D2 devaddr=3D5 interface=3D0 ugen=3Dugen0.5 >> vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 devsubclass=3D0= x00 >> devproto=3D0x00 sernum=3D"" release=3D0x1001 mode=3Dhost >> intclass=3D0x03 intsubclass=3D0x01 intprotocol=3D0x01 on uhub0' >> Feb 18 18:11:04 zen devd: Pushing table >> Feb 18 18:11:04 zen devd: Processing nomatch event >> Feb 18 18:11:04 zen devd: Executing '/etc/rc.d/devmatch start >> '? at bus=3D0 hubaddr=3D1 port=3D2 devaddr=3D5 interface=3D0 >> ugen=3Dugen0.5 vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 >> devsubclass=3D0x00 devproto=3D0x00 sernum=3D"" release=3D0x1001 >> mode=3Dhost intclass=3D0x03 intsubclass=3D0x01 intprotocol=3D0x0= 1 on >> uhub0'' >> Feb 18 18:11:04 zen devd: Popping table >> >> >> That's better... I think you might be hitting the same bug I've >> been hitting on my system... >> >> It looks like we're calling devmatch, but it isn't seeing the >> modules to load. There's still a mismatch between things in the >> USB code (likely my fault, I thought I'd fixed them all: either I >> missed one or broke something). Try running with=C2=A0r329538 (it's >> just a new devmatch, so all you need to do is install just it). > > No difference: > > Feb 18 18:34:33 zen devd: Processing event '!system=3DDEVFS > subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.5.0' > Feb 18 18:34:33 zen devd: Pushing table > Feb 18 18:34:33 zen devd: Processing notify event > Feb 18 18:34:33 zen devd: Popping table > Feb 18 18:34:33 zen devd: Processing event '!system=3DDEVFS > subsystem=3DCDEV type=3DCREATE cdev=3Dugen0.5' > Feb 18 18:34:33 zen devd: Pushing table > Feb 18 18:34:33 zen devd: Processing notify event > Feb 18 18:34:33 zen devd: Popping table > Feb 18 18:34:33 zen devd: Processing event '!system=3DDEVFS > subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.5.1' > Feb 18 18:34:33 zen devd: Pushing table > Feb 18 18:34:33 zen devd: Processing notify event > Feb 18 18:34:33 zen devd: Popping table > Feb 18 18:34:33 zen devd: Processing event '!system=3DDEVFS > subsystem=3DCDEV type=3DCREATE cdev=3Dusb/0.5.2' > Feb 18 18:34:33 zen devd: Pushing table > Feb 18 18:34:33 zen devd: Processing notify event > Feb 18 18:34:33 zen devd: Popping table > Feb 18 18:34:33 zen devd: Processing event '!system=3DUSB > subsystem=3DDEVICE type=3DATTACH ugen=3Dugen0.5 cdev=3Dugen0.5 > vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 devsubclass=3D0x00 > sernum=3D"" release=3D0x1001 mode=3Dhost port=3D2 parent=3Dugen0.1' > Feb 18 18:34:33 zen devd: Pushing table > Feb 18 18:34:33 zen devd: Processing notify event > Feb 18 18:34:33 zen devd: Popping table > Feb 18 18:34:33 zen devd: Processing event '!system=3DUSB > subsystem=3DINTERFACE type=3DATTACH ugen=3Dugen0.5 cdev=3Dugen0.5 > vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 devsubclass=3D0x00 > sernum=3D"" release=3D0x1001 mode=3Dhost interface=3D0 endpoints=3D1 > intclass=3D0x03 intsubclass=3D0x01 intprotocol=3D0x01' > Feb 18 18:34:33 zen devd: Pushing table > Feb 18 18:34:33 zen devd: Processing notify event > Feb 18 18:34:33 zen devd: Popping table > Feb 18 18:34:33 zen devd: Processing event '!system=3DUSB > subsystem=3DINTERFACE type=3DATTACH ugen=3Dugen0.5 cdev=3Dugen0.5 > vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 devsubclass=3D0x00 > sernum=3D"" release=3D0x1001 mode=3Dhost interface=3D1 endpoints=3D1 > intclass=3D0x03 intsubclass=3D0x01 intprotocol=3D0x02' > Feb 18 18:34:33 zen devd: Pushing table > Feb 18 18:34:33 zen devd: Processing notify event > Feb 18 18:34:33 zen devd: Popping table > Feb 18 18:34:33 zen devd: Processing event '? at bus=3D0 hubaddr=3D1 > port=3D2 devaddr=3D5 interface=3D0 ugen=3Dugen0.5 vendor=3D0x24ae > product=3D0x2000 devclass=3D0x00 devsubclass=3D0x00 devproto=3D0x00 > sernum=3D"" release=3D0x1001 mode=3Dhost intclass=3D0x03 intsubclass= =3D0x01 > intprotocol=3D0x01 on uhub0' > Feb 18 18:34:33 zen devd: Pushing table > Feb 18 18:34:33 zen devd: Processing nomatch event > Feb 18 18:34:33 zen devd: Executing '/etc/rc.d/devmatch start '? > at bus=3D0 hubaddr=3D1 port=3D2 devaddr=3D5 interface=3D0 ugen=3Dugen= 0.5 > vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 devsubclass=3D0x00 > devproto=3D0x00 sernum=3D"" release=3D0x1001 mode=3Dhost intclass=3D0= x03 > intsubclass=3D0x01 intprotocol=3D0x01 on uhub0'' > Feb 18 18:34:33 zen devd: Popping table > Feb 18 18:34:33 zen devd: Processing event '? at bus=3D0 hubaddr=3D1 > port=3D2 devaddr=3D5 interface=3D1 ugen=3Dugen0.5 vendor=3D0x24ae > product=3D0x2000 devclass=3D0x00 devsubclass=3D0x00 devproto=3D0x00 > sernum=3D"" release=3D0x1001 mode=3Dhost intclass=3D0x03 intsubclass= =3D0x01 > intprotocol=3D0x02 on uhub0' > Feb 18 18:34:33 zen devd: Pushing table > Feb 18 18:34:33 zen devd: Processing nomatch event > Feb 18 18:34:33 zen devd: Executing '/etc/rc.d/devmatch start '? > at bus=3D0 hubaddr=3D1 port=3D2 devaddr=3D5 interface=3D1 ugen=3Dugen= 0.5 > vendor=3D0x24ae product=3D0x2000 devclass=3D0x00 devsubclass=3D0x00 > devproto=3D0x00 sernum=3D"" release=3D0x1001 mode=3Dhost intclass=3D0= x03 > intsubclass=3D0x01 intprotocol=3D0x02 on uhub0'' > Feb 18 18:34:34 zen devd: Popping table > > FWIW, this laptop's USB works but is quirky in FreeBSD.=C2=A0 It has = 2 > thunderbolt ports both of which work under Windows.=C2=A0 Only one > works under BSD for HDMI out but doesn't work as USB so nothing > detects in it except the the power+hdmi+usb dongle that came with > it.=C2=A0 The USB-3 port works in the dongle though when connected to > this port.=C2=A0 USB+HDMI dongle doesn't work on the first thunderbol= t > port but USB devices plugged in this port work.=C2=A0 I can charge on > both thunderbolt ports. The third type-C port works as expected. > > > OK. I'll delve deeper tonight. > > Can you do a kldstat to see if the right .ko's got loaded? If so > that's one problem, if not it's a different problem. Thanks for your > patience as I iron out this new feature. No additional modules are loaded.=C2=A0 No worries about the issue - I have= a work around until it's fixed. Ian --=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8212a950-3d10-0ac6-f60a-f5dc8b6f10ae>