[SOLVED] Entering passphrase on LUKS partition with USB
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Immediately after coming up with the prompt for entering the LUKS passphrase, I get the output for having found the USB mouse and keyboard. This makes a mess of the prompt.
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.
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.
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!)
# Load a custom keyboard mapping:
if [ -n "$KEYMAP" ]; then
echo "${INITRD}: Loading '$KEYMAP' keyboard mapping:"
tar xzOf /etc/keymaps.tar.gz ${KEYMAP}.bmap | loadkmap
fi
and:
Code:
if [ "$RESCUE" = "" ]; then
# Initialize RAID:
if [ -x /sbin/mdadm ]; then
/sbin/mdadm -E -s >/etc/mdadm.conf
/sbin/mdadm -A -s
fi
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 .
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.
Last edited by GazL; 04-20-2009 at 11:48 AM.
Reason: removed link to patches as they are nolonger hosted.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.