Thanks for confirming I am not going crazy (: I've been googling around to see if USB is a non-free firmware element and from what I can tell since loading firmware via USB seems to be the recommended way to load non-free drivers I doubt this is a licensing issue. From what I've read it appears intel and a few others gave USB 100% license free. Sooo is this just an overlooked driver from the release?

Cheers,
Mike


On 06/14/2018 02:15 AM, Stefan Krusche wrote:
Am Donnerstag 14 Juni 2018 schrieb Michael McConnell:
Hello All,
I've run this test both on Hyper-V VM install and a dedicated hardware install 
using a Dell R210ii, and the results are the same. If I do a new install using 
ASCII and use the default full disk encryption with LVM option - everything 
goes good, until the initial first boot. Upon boot up no matter what I do key 
presses don't register and no way to unlock the disk. I am using a USB 
keyboard, and I’ve tried a couple different models and the keyboard and configs 
i’m using have been fine going as far back as Ubuntu 12.04.
I will try this with a legacy PS2 device if I can track one down this week, but 
my guess is no USB support from the busybox side.
Cheers,
Mike

--
Michael McConnell
WINK Streaming;
email: mich...@winkstreaming.com
toll free: 877-GO-4-WINK x 7400
direct: +1 312 281-5434
cell: +506 8706-2389
skype: wink-michael
web: http://winkstreaming.com


Hello Michael,

I had this very same phenomenon. The reason in my case was, that the USB driver 
(general or for the keyboard I don't know) wasn't included in the initrd as I 
had used an old PS2 keyboard during installation.

When the installer was about to generate initrd and asked wether to create a 
"generic" ramdisk or to use only the necessary drivers, I chose the latter.

When later I restarted the machine with my plugged in shiny USB keyboard it 
wouldn't work as you described.

With the old keyboard again I could enter crypt passphrase etc. and start the 
machine. I Plugged in the USB keyboard and recreated the initrd which solved 
the issue for me.

Hope this helps,
Stefan

_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to