Installed base and kernel on a geli encrypted device /dev/ad4.eli whith /boot on USBpen /dev/da0 following Howto on http://www.wanda25.de/geli.html, aditionally using -B options to fdisk and bsdlabel commands. The Problem which is mentioned there with entering the passphrase appeared, so I followed the instructions with disabling kbdmux and making passphrase visible. Result: you have to press keys several times until the letters appear on the screen. (up to 10 times!) When passphrase is complete and after several 'return's the disc will be attached and everything works fine. On login every keystroke is accepted at once. I even tried to build a new kernel with disabled kbdmux, but the problen remains. Machine is laptop HP COMPAQ 6715b with new mainboard after repair. Some devices may have changed to original loptop. F.e. I needed an updated driver for NIC when trying to reinstall windoze to test if hardware is ok. So perhaps the error don't appear on same Laptops with original hardware. OTOH I read of several people with same problem since 6.x when trying to install on laptops. Fix: Make passphrase visible to see if keystroke is accepted by geli. Not a real fix. Patch attached with submission follows: How-To-Repeat: Install 7.1-RELEASE on geli encrypted laptop HD and try to enter passphrase.
Responsible Changed From-To: freebsd-bugs->freebsd-geom Over to maintainer(s).
What's the status on this? For me it accepts no keystrokes at all. The boot installer works with USB, and if I choose not to install geli during boot, the keyboard works as well. it's only during the geli prompt I have no recourse for an input mechanism since my motherboard does not support os/2 ports. As such, I am unable to use encryption (grrr). See attached screenshot
Created attachment 147936 [details] geli prompting I have two keyboards installed here. None of them will recognize my typing. I've tried several.
batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.