6 ms·
I have had something similar bite me, although mine was easily fixed. I used swedish (åäö) characters for my disk encryption password. This worked fine, until I
by Johnny_Brahms 11y ago
I have had something similar bite me, although mine was easily fixed. I used swedish (åäö) characters for my disk encryption password. This worked fine, until I did a dist-upgrade and had my boot keyboard reset to US QWERTY (using a custom swedish version of capewell-dvorak).
The solution for me was to stick on LTS distros.
- Drakim 11y agoYou can still write åäö with the numpad if your keyboard has one. Alt + 134 = å
- Johnny_Brahms 11y agoI tried that. The LUKS password screen did not support it.
- cubitesystems 11y agoLUKS does not really have a password screen. It must have been your X-window session or terminal emulator that did not support it. LUKS can handle it!
- lwf 11y agoIt was actually neither, most probably. Rather, a prompt generated by https://wiki.freedesktop.org/www/Software/Plymouth/ https://wiki.freedesktop.org/www/Software/Plymouth/
- Johnny_Brahms 11y agoAh yes! Thanks for the correction.
- sbierwagen 11y agoIncorrect. Linux does not support alt codes. https://en.wikipedia.org/wiki/Alt_code https://en.wikipedia.org/wiki/Alt_code
- keithpeter 11y agoA quote from the Slackware README_CTYPT.txt "NOTE: if you use a non-US keyboard and need to enter a passphrase during boot, this may be problematic if the keyboard mapping is US while Slackware runs from the initrd filesystem. In this case, add support for your keyboard to the initrd image using this additional parameter to the 'mkinitrd' command above: "-l <language>". The string <language> is the same as the one you select in the installer when your keyboard is non-US. Example for a dutch keyboard: "-l nl"." Now I'm warned that other systems that use automated kernel updates may clobber the keyboard choice for the initrd.
- Johnny_Brahms 11y ago"May" as in "most certainly did", at least when you are lazy like me and use a GUI-centered distro. I ended up plugging the harddrive into another computer and fixing it from there. I never got that shit from slackware...
- notalaser 11y agoSlackware don't do shit. In fact, Slackware don't do anything unless it's told, which is not as bad a thing as it may seem.
- keithpeter 11y agoTook me some years to work it out but I have begun to appreciate Slackware since installing 14.1 summer before last.
- kuschku 11y agoI have to input a different keyboard when logging in through sddm vs. when using sudo, due to sddm refusing to accept non-US locales.
- keithpeter 11y agoI have that one when running init 4 but the encryption pass phrase is before that stage of the boot up the way my laptop is set up. I'll remember that though...
- moviuro 11y agoI'm pretty sure the standard US layout offers more than enough symbols to write an excellent password. I tend to prefer extremely long passwords/phrases over things that require stupid characters (had trouble with WiFi keys using the French "é" back in 2008, all my passwords are ASCII since)
- oneeyedpigeon 11y agoOf course, characters that I use in my everyday language aren't "stupid" to me.
- Johnny_Brahms 11y agoIt was a long password phrase. One of the words just happened to be in my mother tongue.
- creshal 11y agoEvery language that is not American English is "stupid"?
- umanwizard 11y agoNo diacritics in Latin, either!
- creshal 11y agoæ?
- rwmj 11y agoA similar problem is having a UK pound sign (£) or double quotes (") in your password. These are mapped differently in UK and US keyboards, and £ is sometimes not easily available at all.