The new vt system console looks really nice. But on hosts that have geli encrypted devices that prompt for the passphrase at boot, no keyboard input reaches geli. The keyboard doesn't appear to be dead, as the caps-lock and num-lock keys toggle; geli just doesn't receive any input. This is on 10-STABLE amd64 built from yesterday's sources. "hw.vga.textmode=1" doesn't make any difference. Has anyone else encountered this? -- Greg Rivers
On Fri, Apr 18, 2014 at 10:36:51AM -0500, Greg Rivers wrote:> The new vt system console looks really nice. But on hosts that have geli > encrypted devices that prompt for the passphrase at boot, no keyboard input > reaches geli. The keyboard doesn't appear to be dead, as the caps-lock and > num-lock keys toggle; geli just doesn't receive any input. This is on > 10-STABLE amd64 built from yesterday's sources. "hw.vga.textmode=1" doesn't > make any difference. > > Has anyone else encountered this? >No, and I have this exact setup. Is the keyboard USB, by chance? Glen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 834 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20140418/8cf20f11/attachment.sig>
Hi, On Fri, 18 Apr 2014 10:36:51 -0500 (CDT) Greg Rivers <gcr+freebsd-stable at tharned.org> wrote:> The new vt system console looks really nice. But on hosts that have > geli encrypted devices that prompt for the passphrase at boot, no > keyboard input reaches geli. The keyboard doesn't appear to be dead,do you have / encrypted? I use geli but have only /usr/home encrypted and no problems. You might have to load vt via loader.conf or put it into the kernel. Wait, is there a chicken-egg problem? Erich
On 04/18/2014 08:36, Greg Rivers wrote:> The new vt system console looks really nice. But on hosts that have > geli encrypted devices that prompt for the passphrase at boot, no > keyboard input reaches geli. The keyboard doesn't appear to be dead, > as the caps-lock and num-lock keys toggle; geli just doesn't receive > any input. This is on 10-STABLE amd64 built from yesterday's sources. > "hw.vga.textmode=1" doesn't make any difference. > > Has anyone else encountered this? >I run encrypted ZFS with vt(4) on -CURRENT right now and I've not had any issues with entering my passphrase. There might be a bug fix that ray@ hasn't had a chance to merge from current just yet.
On 2014/04/18, 11:36, Greg Rivers wrote:> The new vt system console looks really nice. But on hosts that > have geli encrypted devices that prompt for the passphrase at > boot, no keyboard input reaches geli. The keyboard doesn't > appear to be dead, as the caps-lock and num-lock keys toggle; > geli just doesn't receive any input. This is on 10-STABLE amd64 > built from yesterday's sources. "hw.vga.textmode=1" doesn't make > any difference. > > Has anyone else encountered this? >Yes, I have, on my FreeBSD workstation with a USB keyboard. It's running FreeBSD 10 with geli-encrypted ZFS root. This happened before I updated to vt, though. I managed to work around the problem, surprisingly enough, by mashing the keyboard when the system boots as soon as I see bold white kernel text. Then, when prompted for the passphrase (after all the USB devices finish probing / attaching), I hit enter to clear the buffer and then am able to enter the passphrase correctly. I'll be filing a PR for this, probably on Monday, should I not be able to find one that's similar. -- Chris Nehren