Date: Sun, 14 Mar 2021 13:16:53 +0100 From: "Hartmann, O." <o.hartmann@walstatt.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: "Hartmann, O." <ohartmann@walstatt.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: console: no USB keyboard! Message-ID: <20210314131653.1ac46909@hermann.fritz.box> In-Reply-To: <7719f608-f277-5ba9-903d-9da463b4c921@FreeBSD.org> References: <20210313200117.46db6706@hermann.fritz.box> <7719f608-f277-5ba9-903d-9da463b4c921@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/g39hJCZsBAXw6kcnWx9P5i. Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 14 Mar 2021 11:42:13 +0200 Andriy Gapon <avg@FreeBSD.org> wrote: > On 13/03/2021 21:01, Hartmann, O. wrote: > > Running 14-CURRENT on several boxes (i.e. FreeBSD 14.0-CURRENT #49 > > main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 2021 amd64) with cus= tom and/or > > GENERIC kernel and USB-only equipment (mouse if available, keyboard). > > In multiuser mode, there is no problem using the USB keyboard. On singl= e user console > > (for maintenance purposes), no USB keyboard is available. The same is t= rue while > > booting and the rc scripts are worked on. Usually, one can hit the ente= r key and > > inserts a newline, this doesn't work anymore until the box is completel= y up!=20 > >=20 > > I do not know when this problem as been introduced, the very same confi= g is used since > > 13-CURRENT in its earlier time and has been modified accordingly, but I= can't see > > obvios changes which would explain the wrecked behaviour now.=20 > >=20 > > I got aware of this problem, when a small mistake in /etc/fstab rendere= d a box > > unbootable, I had to head for the datacenter and wasn't even capable of= interrupting > > the stuck system. Checking on other boxes running recent 14-CURRENT rev= ealed the same > > problem. > >=20 > > The interesting part is, that as long as those boxes are with the loade= r present (all > > boxes are UEFI booting!), the USB keyboard works as expected and I'm ab= le to select > > kernel/kernel.old and so on. > >=20 > > How to fix this? =20 >=20 > Can't help with fixing the problem, but here's some info. > When you are at the loader prompt, BIOS provides emulation of a standard / > legacy keyboard for the USB keyboard. That's why loader can work even th= ough it > doesn't know much about USB. > When a FreeBSD driver for the USB controller takes over then the BIOS emu= lation > stops. Until a FreeBSD peripheral driver like ukbd attaches, it's not po= ssible > to use the keyboad, unfortunately. You can check your dmesg to see when = that > happens. >=20 > Personally, I try to avoid "legacy free" solutions and always have a PS/2 > keyboard (even if it's a really a USB one using PS/2 <-> USB adapter). >=20 > Of course, it would be great to reduce the dead window for USB keyboards = and I > think that it is doable. >=20 >=20 Hello, thank you very much for the explanation. For usual, I compile all necessary= module staticlly into the kernel, the USB mouse, massstorage, keyboard. There was = a message about some changes with uhid/hid, I tried all variants coming to my mind, s= tarting from GENERIC up to add-ons statically compiled in. The systems in question I obs= erved this the first time are quite old (Z77/IvyBridge era) and do have PS/2 sockets, = but others (KabyLake) doesn't. Most KVM we use today in the datacenters are VGA/USB ba= sed, so there is no chance to attach PS/2 equipment :-( Kind regards, oh=20 --Sig_/g39hJCZsBAXw6kcnWx9P5i. Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCYE3+tQAKCRA4N1ZZPba5 R88RAP0TTYjxpFs1elfhFnbF4vTH5S3GvGsmjvDgNEheIgn9jgD/Q851tL4mKv0F Ceqn1LDLHDuwJ4AtMkpCU1wK8H+9nAk= =z4/9 -----END PGP SIGNATURE----- --Sig_/g39hJCZsBAXw6kcnWx9P5i.--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210314131653.1ac46909>