Date: Sun, 19 Feb 2017 03:10:12 -0700 From: Jan Peterson <jan.l.peterson@gmail.com> To: Hans Petter Selasky <hps@selasky.org> Cc: freebsd-usb@freebsd.org Subject: Re: device not attaching at boot Message-ID: <d11234a8-192b-4c88-bb58-28e102ddf4be@typeapp.com> In-Reply-To: <cf317c70-0cf8-7628-bc4c-6a4e7df9e013@selasky.org> References: <68a36048-dae3-dc3b-b9f4-e63450c54045@gmail.com> <cf317c70-0cf8-7628-bc4c-6a4e7df9e013@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Hans, I have not tried a -STABLE kernel=2E My kernel is -p2, with a= -p7 userland=2E I will give -STABLE a try in the morning=2E There are no = relevant USB options in the BIOS=2E The only settings are to disable specif= ic ports (for security purposes)=2E I looked for any legacy options, but th= ere were none=2E I will let the list know how it goes with -STABLE=2E Tha= nks! =C2=A0 -jan- -- =E2=81=A3Jan L=2E Peterson http://www=2Epeterson-tec= h=2Ecom/~jlp/ Sent from TypeApp =E2=80=8B On Feb 19, 2017, 02:52, at 02:5= 2, Hans Petter Selasky <hps@selasky=2Eorg> wrote: >On 02/19/17 10:04, Jan L= =2E Peterson wrote: >> Hi, folks, >> >> I have a weird problem=2E=2E=2E >> = >> Hardware is an HP dc7900 small form factor PC=2E OS is FreeBSD >> 11=2E= 0-RELEASE-p7=2E I am running the GENERIC kernel=2E >> >> I have a USB ethe= rnet adapter that contains a Realtek chip=2E=2E=2E the >vendor >> ID is 0x0= bda and the product ID is 0x8153=2E >> >> If I plug this device into the ma= chine while the system is already up >> and running, it is detected and att= ached as ue0 on cdce0 (it appears >as >> ugen3=2E2, no matter which of the = several USB ports on the machine I >plug >> it into)=2E >> >> If the device= is plugged into the machine when it boots up, nothing I >> can do (short o= f unplugging it and replugging it) will make the >machine >> recognize that= it is there=2E >> >> I have tried the following: >> >> 1=2E played with h= w=2Eusb=2Etimings=2E* values >> 2=2E usbconfig -d 3=2E1 set_config 255; us= bconfig -d 3=2E1 set_config 0 >> (which deactivates the hub that the device= is connected to and then >> reactivates it) >> 3=2E did the same (set_con= fig 255; set_config 0) on *all* of the usb >hubs >> (ugen*=2E1) >> 4=2E tu= rned on various hw=2Eusb=2E*=2Edebug options (which produced copious >> deb= ug info, but nothing containing the strings 8153, 0bda, or >Realtek) >> 5= =2E tried various devctl rescan options (including pci0) >> 6=2E googled = frantically for something similar to this problem to no >> avail (well, I d= id come across some people with similar problems, but >> their problems all= seemed to be around the device coming up with the >> wrong config and need= ing a SET_CFG_1 quirk set, which appears to >already >> be in the kernel as= of 2015 or so) >> >> I've looked for ways to force the USB bus to rescan (= hence the >usbconfig >> stuff in number 2 above) but nothing I have tried s= eems to work=2E >> >> Again, the device works fine if I unplug it from the = machine and then >> plug it back in=2E It is detected, probes, and attache= s just fine and >> dandy=2E The problem is that the machine is destined to= be locked in a >> cabinet at a remote location where there won't be anyone= available to >go >> unplug and replug it any time the machine needs a rebo= ot=2E >> >> To clarify=2E=2E=2E when I have the device plugged into the mac= hine and I >> reboot, the device is not detected or noticed by the OS in an= y way=2E >> There is nothing relevant in dmesg or /var/log/messages=2E usb= config >and >> devinfo do not see it at all=2E If I unplug the device and = plug it >back >> in, it is recognized immediately and works fine=2E >> >> A= ny ideas? >> > >Hi, > >Have you tried a 11-stable kernel? > >Have you tried= disabling USB in the BIOS? > >--HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d11234a8-192b-4c88-bb58-28e102ddf4be>