You are not logged in.
I just ran pacman -Syu today, after having done the last update on Feb 04. This upgraded (among many other things), the kernel from 3.2.2-1 to 3.2.4-1.
After the reboot, the passphrase for my LUKS-encrypted disk was not accepted. I very nearly died from a heart attack, but it turned out to be just a keymap problem. Something had reverted the system back to the US keymap instead of the German keymap it's supposed to use.
The system booted, though with an error pertaining to /etc/rc.d/functions (don't remember what it was exactly).
I checked my rc.conf and found that all the entries in the LOCALIZATION section had gone blank. According to the file's ctime, it hasn't been touched since Jan 29. This is kind of impossible, since I'm sure I have rebooted at least twice since Jan 29 and never had problems with the keymap.
I fixed rc.conf, rebooted, but still the keymap was set to US when I entered the LUKS passphrase. No errors regarding /etc/rc.d/functions this time. After booting, the keymap in a tty is German as it should be.
Any ideas what's going on here?
EDIT:
That was quick. I saw that linux 3.2.5 was available, upgraded, and everything is back to normal. I'd still be curious about what happened to my rc.conf though.
Last edited by ulke (2012-02-08 10:34:13)
Offline
Have you properly merged pacnew files? Doing this the wrong way could result in getting the stock rc.conf http://projects.archlinux.org/initscrip … ee/rc.conf or e.g. a partially merged one (i.e. with some options blank).
Offline
I think I have. I've been using Arch for over a year and have merged pacnew files multiple times. Anyhow, wouldn't an incorrectly merged pacnew have created problems from the time it was last edited, in my case January 29?
Or is the LOCALIZATION session only read when mkinitpcio is run? That would explain it.
Offline
It's enough to reboot, no need to rebuild the kernel image after you've made some changes to the rc.conf.
I'm out of ideas.
Offline