Hello,

I recently did a full install of slackware-current64 and ran into something I'm confused by.

when my computer boots it displays the normal

as soon as I type a few characters a message pops up where I'm entering my passphrase.

The device unlocks normal everything seems to work fine, but the message is a bit annoying. I also want to make sure it isn't caused by something more severe.

I tried the default cryptsetup options ( cryptsetup luksFormat /dev/sda2 ) and had the same problem. I didn't have this issue with my time on 14.1.

One thing that may be worth mentioning is after I rebooted my computer after making the initrd using mkinitrd_command_generator.sh my usb keyboard didn't work. I was able to get it working again by adding ohci-pci leaving me wondering if I'm missing any other modules.

I think that http://www.linuxquestions.org/questi...rd-4175539983/ may be a similar problem but no solution was given.

I spend a couple nights trying to figure this out and would appreciate any ideas!

Thanks

Hmm, it might work if you feed /dev/random before the cryptsetup work in /etc/rc.d/rc.S. Or you could disable kernel-messages appearing in the console, e.g. "dmesg --console-off" before cryptsetup stuff and "dmesg --console-on" to reenable afterwards, or set the console-level to something except "notice".

I installed Current on a virtual machine using another computer and had the normal luks prompt with out the message.

Looking at /etc/rc.d/rc.S on the virtual machine. I didn't see any references to /dev/random are you talking about /dev/random-seed?

Is this something that affect my disk encryption or something that can be safely ignored?

I assume that the message comes from the kernel's random generator telling you that it's initialized and that happens when it is used for the first time, and this would be with the use of cryptsetup (or maybe a keystroke for collecting entropy). My proposal was now to give the random-generator some food (some data into /dev/urandom or /dev/random) like at the end of the rc.S, to trigger that message earlier.
I don't know if that works however. Anyways, that message is just a notice, in no way harmful and nothing to worry about. You are either safe to ignore it or change the console-logging level. There are several ways to do so:
or
Maybe even some kernel-parameter.
I guess a simple
before, and
after the cryptsetup-stuff in rc.S should be sufficient if you are really bothered by the notice, to disable kernel-notices from appearing on the console.

Thanks you for the reply!

I'm not really familiar with how this all works. How would you recommend feeding random?

I looked over rc.S in current an 14.1 there didn't seems to be any relevant differences between them. I'm really curious about what changed and why I'm only getting this behavior on current. I tried some other ciphers and hashes as well with the same result. If anyone has any ideas. I'd love to hear them.

Like at the end of rc.S, basically writing data to /dev/urandom. You might move the "cat /etc/random-seed > /dev/urandom" part before any cryptsetup-stuff.
If you were using the stock kernel from 14.1 (3.10.17), there simply was no such message in the kernel yet.