Entering passphrase on LUKS partition with USB
I've encrypted my root partition using LUKS.
I've built my initrd and added support for ext3 and USB for my keyboard and mouse, using the following command: Code:
mkinitrd -k 2.6.29 -m ext3:ehci_hcd:uhci_hcd:usbhid -f ext3 -r /dev/cryptvg/root -C /dev/hda2 -L I can still enter the password and the partition unlocks and boots perfectly. I know this is more of a cosmetic problem, but it would be nice if someone knew the answer. Any help appreciated, Mark. |
maybe you could add a short sleep to the init script in /boot/initrd-tree prior to the call to cryptsetup to allow your modules time to initialise. Once you've made your customisations you just have to re-run mkinitrd without any parameters and it'll rebuild the initrd.gz from the modified initrd-tree.
|
Hi GazL,
Would this be a case of adding something like: Code:
sleep 10 If so, whereabouts in the file should I add it? Many thanks, M. |
Yep, that's what I was getting at. The cryptsetup command is what't used to unlock the luks devices, so if you search for that and put your sleep on the line before it, hopefully that should do the trick.
Remember not to specify any options on the mkinitrd when you re-run it for the second time, or it may end up rebuilding your /boot/initrd-tree again and undoing your changes. I'd also suggest that whenever your playing with the initrd you make a copy of your old initrd.gz file and have a second lilo entry pointing to it, just incase you make a mistake with your edit and your new initrd.gz becomes unbootable. Normally, I'd be a little more helpful and provide you with an example, but I've just bought a new PC and I haven't got around to putting Slack on it yet and transfering my old system across. (I'm using Vista and Opera at the moment, and actually finding it isn't half as bad as people make out... I think I've lost my inner-penguin!) |
Hi GazL,
After a bit of trial and error, we have success. In /boot/initrd-tree/init I entered: Code:
sleep 5 Code:
# Load a custom keyboard mapping: Code:
if [ "$RESCUE" = "" ]; then M. |
I also experience the same thing, but it changes every time I compile a new kernel. Nowadays the prompt doesn't get messed up, who knows what will happen next time :).
|
Quote:
This sounds like a change that the Slackware Devs really ought to incorporate into the stock build. Anyone with a USB keyboard who chooses to use LUKS is likely to encounter this same issue. |
Yeah thanks, I'll take a look at them.
Take it easy, M. |
All times are GMT -5. The time now is 12:12 PM. |