You are not logged in.
Hey guys,
I've done a bit of digging around the threads, and I've found a few posts with problems similar to mine, but their solutions didn't work for me.
I've got an encrypted root device and a usb keyboard. I've loaded the usbinput hook before my encrypt hook, and my keyboard appears to work, but the input isn't being captured by the password prompt.
I've even tried loading my keyboard modules (usb_hid, hid-microsoft, etc) in the modules section of mkinitcpio.conf, to no avail.
When I disable quiet loading from my kernel, I can see that the information for the keyboard being connected sometimes appears after the password prompt. Can I add a delay somehow? Are there any other suggestions?
Offline
More experimentation: the usbinput hook is required, but even dropping in a ten second delay between the usbinput and encrypt hooks (via the sleep hook) does nothing. Input is directed to the screen and not the unlocking tool.
Offline
Alright, an update:
I tried rewriting the section of the encrypt hook to handle luks key input better, but it's still not capturing anything. Unlike the other similar problems on this board, my keyboard is working.
I've even tried throwing in a ten second sleep hook between usbinput and encrypt to no avail. I've scraped the bottom of the barrel for ideas. Any help would be more than welcome.
Offline
So I bumped the delay timer up to 30 seconds, which still had no effect. I thought at first that it was a timing issue, where the encrypt hook was firing before the usb input modules had a chance to load, but that doesn't seem to be the case. I've also tried toggling some of the usb legacy settings in the bios. Ineffective.
There's no such problem booting from a recovery console or live image, but the encrypt hook just doesn't seem to be capturing any input.
Offline
Alright. I've tried to do a workaround where I store a keyfile on a usb key, but that seems to be a bit tempermental. At this stage, I've modified my syslinux.cfg to use a nonexistant cryptdevice, and then doing things manually when it quits to a recovery shell.
It's not a solution, it's a workaround. Anyone have any ideas?
Offline
I hate bumping posts. I feel like it's rude and breaks forum etiquette, but I still haven't found a solution to this problem, nor am I any closer to finding one myself.
Offline
You're not alone. I'm also working on this. I have a Microsoft keyboard too (a Natural Ergonomic Keyboard 4000 v1.0 precisely).
I'll give news if I ever find something.
EDIT : Have you rebuilt your initramfs ? I think yes, but it we can sometimes forget
Last edited by CPU Gastronomy (2011-09-18 02:13:37)
Offline