Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Colemak layout at boot time
240 views
Skip to first unread message
piorunz
Sep 18, 2021, 7:10:05 AM9/18/21
to
Hi all,
I use Colemak layout instead of Qwerty, because it's so much better and
efficient.
Today I repositioned keys on my laptop too, so I have two computers with
Colemak.
However, my laptop uses full disk encryption (Debian 11).
At boot time, and in GRUB, I don't have Colemak, but default layout.
How to change to Colemak? I read few very old tutorials, not one solves
this problem in 2021. Not sure how I should proceed.
I already selected Colemak in KDE settings, and via sudo
dpkg-reconfigure keyboard-configuration. But this does not affect boot
time password question and GRUB editor. Also virtual consoles still use
default Qwerty.
My /etc/default/keyboard file:
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="gb"
XKBVARIANT="colemak"
XKBOPTIONS=""
BACKSPACE="guess"
Any tips appreciated!
--
With kindest regards, Piotr.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀
I use Colemak layout instead of Qwerty, because it's so much better and
efficient.
Today I repositioned keys on my laptop too, so I have two computers with
Colemak.
However, my laptop uses full disk encryption (Debian 11).
At boot time, and in GRUB, I don't have Colemak, but default layout.
How to change to Colemak? I read few very old tutorials, not one solves
this problem in 2021. Not sure how I should proceed.
I already selected Colemak in KDE settings, and via sudo
dpkg-reconfigure keyboard-configuration. But this does not affect boot
time password question and GRUB editor. Also virtual consoles still use
default Qwerty.
My /etc/default/keyboard file:
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
XKBMODEL="pc105"
XKBLAYOUT="gb"
XKBVARIANT="colemak"
XKBOPTIONS=""
BACKSPACE="guess"
Any tips appreciated!
--
With kindest regards, Piotr.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀
David Wright
Sep 18, 2021, 3:10:05 PM9/18/21
to
On Sat 18 Sep 2021 at 12:02:49 (+0100), piorunz wrote:
> I use Colemak layout instead of Qwerty, because it's so much better and
> efficient.
> Today I repositioned keys on my laptop too, so I have two computers with
> Colemak.
> However, my laptop uses full disk encryption (Debian 11).
> At boot time, and in GRUB, I don't have Colemak, but default layout.
> How to change to Colemak? I read few very old tutorials, not one solves
> this problem in 2021. Not sure how I should proceed.
>
> I already selected Colemak in KDE settings, and via sudo
> dpkg-reconfigure keyboard-configuration. But this does not affect boot
> time password question and GRUB editor. Also virtual consoles still use
> default Qwerty.
A lot of hits from googling grub colemak including
> I use Colemak layout instead of Qwerty, because it's so much better and
> efficient.
> Today I repositioned keys on my laptop too, so I have two computers with
> Colemak.
> However, my laptop uses full disk encryption (Debian 11).
> At boot time, and in GRUB, I don't have Colemak, but default layout.
> How to change to Colemak? I read few very old tutorials, not one solves
> this problem in 2021. Not sure how I should proceed.
>
> I already selected Colemak in KDE settings, and via sudo
> dpkg-reconfigure keyboard-configuration. But this does not affect boot
> time password question and GRUB editor. Also virtual consoles still use
> default Qwerty.
https://forums.debian.net//viewtopic.php?f=16&t=76833
which uses dvorak as an example.
I don't recall the definition of "boot time password". Does this
denote something that Grub asks, or is it when dmcrypt is running
from the initrd? — Which is a reminder: is your keyboard definition
in /etc/default/keyboard getting incorporated into the initrd or not?
Cheers,
David.
piorunz
Sep 18, 2021, 5:00:05 PM9/18/21
to
On 18/09/2021 20:00, David Wright wrote:
> A lot of hits from googling grub colemak including
> https://forums.debian.net//viewtopic.php?f=16&t=76833
> which uses dvorak as an example.
Thanks for your reply.
> A lot of hits from googling grub colemak including
> https://forums.debian.net//viewtopic.php?f=16&t=76833
> which uses dvorak as an example.
Yes I seen this page.
ckbcomp dvorak command outputs the layout details and everything.
However:
$ ckbcomp colemak
/usr/bin/ckbcomp: Can not find file "symbols/colemak" in any known directory
>
> I don't recall the definition of "boot time password". Does this
> denote something that Grub asks, or is it when dmcrypt is running
> from the initrd?
in Debian. I don't have Colemak there. I need to enter password in
Colemak. Yes, I think that's called dmcrypt.
>Which is a reminder: is your keyboard definition
> in /etc/default/keyboard getting incorporated into the initrd or not?
including virtual terminals (Ctrl+Alt+F keys) are Qwerty.
David Wright
Sep 19, 2021, 12:50:04 AM9/19/21
to
On Sat 18 Sep 2021 at 21:56:34 (+0100), piorunz wrote:
> On 18/09/2021 20:00, David Wright wrote:
>
> > A lot of hits from googling grub colemak including
> > https://forums.debian.net//viewtopic.php?f=16&t=76833
> > which uses dvorak as an example.
>
> Thanks for your reply.
> Yes I seen this page.
>
> ckbcomp dvorak command outputs the layout details and everything.
>
> However:
> $ ckbcomp colemak
> /usr/bin/ckbcomp: Can not find file "symbols/colemak" in any known directory
>
> >
> > I don't recall the definition of "boot time password". Does this
> > denote something that Grub asks, or is it when dmcrypt is running
> > from the initrd?
>
> By that I meant GRUB editor and Debian's standard whole disk encryption
> in Debian. I don't have Colemak there. I need to enter password in
> Colemak. Yes, I think that's called dmcrypt.
>
> > Which is a reminder: is your keyboard definition
> > in /etc/default/keyboard getting incorporated into the initrd or not?
>
> I don't know that. I only have Colemak in KDE. Everything else,
> including virtual terminals (Ctrl+Alt+F keys) are Qwerty.
How do you normally login, at a VC or in a Display Manager?
> On 18/09/2021 20:00, David Wright wrote:
>
> > A lot of hits from googling grub colemak including
> > https://forums.debian.net//viewtopic.php?f=16&t=76833
> > which uses dvorak as an example.
>
> Thanks for your reply.
> Yes I seen this page.
>
> ckbcomp dvorak command outputs the layout details and everything.
>
> However:
> $ ckbcomp colemak
> /usr/bin/ckbcomp: Can not find file "symbols/colemak" in any known directory
>
> >
> > I don't recall the definition of "boot time password". Does this
> > denote something that Grub asks, or is it when dmcrypt is running
> > from the initrd?
>
> By that I meant GRUB editor and Debian's standard whole disk encryption
> in Debian. I don't have Colemak there. I need to enter password in
> Colemak. Yes, I think that's called dmcrypt.
>
> > Which is a reminder: is your keyboard definition
> > in /etc/default/keyboard getting incorporated into the initrd or not?
>
> I don't know that. I only have Colemak in KDE. Everything else,
> including virtual terminals (Ctrl+Alt+F keys) are Qwerty.
Where did you run "sudo dpkg-reconfigure keyboard-configuration" from?
Have you seen this line:
update-initramfs: Generating /boot/initrd.img-4.19.0-17-amd64
since you changed /etc/default/keyboard and ran
sudo dpkg-reconfigure keyboard-configuration?
Checking your current initrd is a little tedious: you run
unmkinitramfs to unpack the initrd, and you zcat your
/etc/console-setup/cached_UTF-8_del.kmap.gz to, say, /tmp.
Then run, eg:
$ diff -u …/main/etc/console-setup/cached_UTF-8_del.kmap /tmp/cached_UTF-8_del.kmap
$
where they are the unpacked and decompressed files respectively.
Cheers,
David.
Gareth Evans
Sep 19, 2021, 1:20:04 AM9/19/21
to
piorunz
Sep 19, 2021, 4:40:05 AM9/19/21
to
On 19/09/2021 05:49, David Wright wrote:
> On Sat 18 Sep 2021 at 21:56:34 (+0100), piorunz wrote:
>> On 18/09/2021 20:00, David Wright wrote:
>>
>>> A lot of hits from googling grub colemak including
>>> https://forums.debian.net//viewtopic.php?f=16&t=76833
>>> which uses dvorak as an example.
>>
>> Thanks for your reply.
>> Yes I seen this page.
>>
>> ckbcomp dvorak command outputs the layout details and everything.
>>
>> However:
>> $ ckbcomp colemak
>> /usr/bin/ckbcomp: Can not find file "symbols/colemak" in any known directory
>>
>>>
>>> I don't recall the definition of "boot time password". Does this
>>> denote something that Grub asks, or is it when dmcrypt is running
>>> from the initrd?
>>
>> By that I meant GRUB editor and Debian's standard whole disk encryption
>> in Debian. I don't have Colemak there. I need to enter password in
>> Colemak. Yes, I think that's called dmcrypt.
>>
>>> Which is a reminder: is your keyboard definition
>>> in /etc/default/keyboard getting incorporated into the initrd or not?
>>
>> I don't know that. I only have Colemak in KDE. Everything else,
>> including virtual terminals (Ctrl+Alt+F keys) are Qwerty.
>
> How do you normally login, at a VC or in a Display Manager?
I login to KDE login screen. Actually I have clean Debian 11 with KDE.
> On Sat 18 Sep 2021 at 21:56:34 (+0100), piorunz wrote:
>> On 18/09/2021 20:00, David Wright wrote:
>>
>>> A lot of hits from googling grub colemak including
>>> https://forums.debian.net//viewtopic.php?f=16&t=76833
>>> which uses dvorak as an example.
>>
>> Thanks for your reply.
>> Yes I seen this page.
>>
>> ckbcomp dvorak command outputs the layout details and everything.
>>
>> However:
>> $ ckbcomp colemak
>> /usr/bin/ckbcomp: Can not find file "symbols/colemak" in any known directory
>>
>>>
>>> I don't recall the definition of "boot time password". Does this
>>> denote something that Grub asks, or is it when dmcrypt is running
>>> from the initrd?
>>
>> By that I meant GRUB editor and Debian's standard whole disk encryption
>> in Debian. I don't have Colemak there. I need to enter password in
>> Colemak. Yes, I think that's called dmcrypt.
>>
>>> Which is a reminder: is your keyboard definition
>>> in /etc/default/keyboard getting incorporated into the initrd or not?
>>
>> I don't know that. I only have Colemak in KDE. Everything else,
>> including virtual terminals (Ctrl+Alt+F keys) are Qwerty.
>
> How do you normally login, at a VC or in a Display Manager?
No modifications to system.
>
> Where did you run "sudo dpkg-reconfigure keyboard-configuration" from?
>
> Have you seen this line:
> update-initramfs: Generating /boot/initrd.img-4.19.0-17-amd64
> since you changed /etc/default/keyboard and ran
> sudo dpkg-reconfigure keyboard-configuration?
didn't generated any output in terminal. I actually run this command
several times now, with reboots, and no change. in
keyboard-configuration menu itself, Colemak is selected,
/etc/default/keyboard file also is all correct, but I don't have Colemak
at dm-crypt password time, nor in virtual consoles (Ctrl+Alt+F keys).
> Checking your current initrd is a little tedious: you run
> unmkinitramfs to unpack the initrd, and you zcat your
> /etc/console-setup/cached_UTF-8_del.kmap.gz to, say, /tmp.
unmkinitramfs /boot/initrd.img-$(uname -r) initramfs/
> Then run, eg:
>
> $ diff -u …/main/etc/console-setup/cached_UTF-8_del.kmap /tmp/cached_UTF-8_del.kmap
default fonts fstab ld.so.cache ld.so.conf ld.so.conf.d lvm mdadm
modprobe.d mtab nsswitch.conf os-release passwd plymouth udev
There is no console-setup folder in unpacked initramfs folder.
$ diff -u …/main/etc/console-setup/cached_UTF-8_del.kmap
/tmp/cached_UTF-8_del.kmap
directory
diff: /tmp/cached_UTF-8_del.kmap: No such file or directory
$ apt-file search cached_UTF-8_del.kmap
(no results here)
piorunz
Sep 19, 2021, 6:40:05 AM9/19/21
to
Got a step further.
when I do "sudo setupcon" in virtual console (Ctrl+Alt+F key), I have
Colemak there. But only after I log in there already (using Qwerty) and
issue the command, not before.
Tasks:
Made virtual consoles Colemak by default, without need for sudo
setupcon. Why aren't they preconfigured with my choice when console is
being opened?
Achieve Colemak in dm-crypt password question.
I use Debian Bullseye, KDE, clean install.
when I do "sudo setupcon" in virtual console (Ctrl+Alt+F key), I have
Colemak there. But only after I log in there already (using Qwerty) and
issue the command, not before.
Tasks:
Made virtual consoles Colemak by default, without need for sudo
setupcon. Why aren't they preconfigured with my choice when console is
being opened?
Achieve Colemak in dm-crypt password question.
I use Debian Bullseye, KDE, clean install.
Gareth Evans
Sep 19, 2021, 6:50:05 AM9/19/21
to
Adding the UK Colemak keyboard layout and promoting it to the top of the list in system settings > keyboard does not make it take effect in either the LUKS boot-time password or the graphical login - only after login to KDE.
Switching to UK layout for usage and then running in konsole
# dpkg-reconfigure keyboard-configuration
[choosing UK then Colemak then default for AltGr/special keys etc]
does not change the active keyboard layout, nor for the LUKS boot password or graphical login.
Out of interest, I thought I would try the instructions (section 5):
https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html
- but they fail at the third command:
# tar -C "$memdisk" -cf /boot/grub/memdisk.tar
tar: Cowardly refusing to create an empty archive
Try 'tar --help' or 'tar --usage' for more information
I lack much experience with ramdisks and all but the simplest of grub configuration, but I can't see either an obvious problem with the syntax suggested, or anything in 'tar --help' that helps.
Any suggestions?
Thanks
Gareth
Gareth Evans
Sep 19, 2021, 8:10:08 AM9/19/21
to
Gareth Evans
Sep 19, 2021, 8:30:05 AM9/19/21
to
man grub-mkimage doesn't list possibilities. Can anyone suggest a suitable alternative for a VM created with virt-manager/qemu-kvm?
Many thanks
Gareth
Curt
Sep 19, 2021, 8:40:05 AM9/19/21
to
On 2021-09-18, piorunz <pio...@gmx.com> wrote:
>
> I already selected Colemak in KDE settings, and via sudo
> dpkg-reconfigure keyboard-configuration. But this does not affect boot
> time password question and GRUB editor. Also virtual consoles still use
> default Qwerty.
>
Maybe something instructive here (or not):
>
> I already selected Colemak in KDE settings, and via sudo
> dpkg-reconfigure keyboard-configuration. But this does not affect boot
> time password question and GRUB editor. Also virtual consoles still use
> default Qwerty.
>
https://bbs.archlinux.org/viewtopic.php?id=246453
piorunz
Sep 19, 2021, 8:50:04 AM9/19/21
to
exist in Debian.
piorunz
Sep 19, 2021, 8:50:05 AM9/19/21
to
On 19/09/2021 13:26, Gareth Evans wrote:
> The commands appeared to succeed (with suitable alteration of variables) but my VM now boots into a grub prompt immediately - doesn't ask for LUKS password. I think this may be because I didn't change the "ahci" module to something else in step 3.
>
> man grub-mkimage doesn't list possibilities. Can anyone suggest a suitable alternative for a VM created with virt-manager/qemu-kvm?
Are you saying I could try this Section 5 method to have Colemak at GRUB
> The commands appeared to succeed (with suitable alteration of variables) but my VM now boots into a grub prompt immediately - doesn't ask for LUKS password. I think this may be because I didn't change the "ahci" module to something else in step 3.
>
> man grub-mkimage doesn't list possibilities. Can anyone suggest a suitable alternative for a VM created with virt-manager/qemu-kvm?
and LUKS password prompt? Not VM, but my laptop, real HW.
Gareth Evans
Sep 19, 2021, 9:10:05 AM9/19/21
to
On Sun 19 Sep 2021, at 13:43, piorunz <pio...@gmx.com> wrote:
> On 19/09/2021 13:26, Gareth Evans wrote:
>
> > The commands appeared to succeed (with suitable alteration of variables) but my VM now boots into a grub prompt immediately - doesn't ask for LUKS password. I think this may be because I didn't change the "ahci" module to something else in step 3.
> >
> > man grub-mkimage doesn't list possibilities. Can anyone suggest a suitable alternative for a VM created with virt-manager/qemu-kvm?
>
> Are you saying I could try this Section 5 method to have Colemak at GRUB
> and LUKS password prompt? Not VM, but my laptop, real HW.
Not yet. As things stand, those commands have only succeeded in breaking the VM I set up for the purpose, but I'm hoping someone can suggest the appropriate tweak, if the reason is what I think it is.
> On 19/09/2021 13:26, Gareth Evans wrote:
>
> > The commands appeared to succeed (with suitable alteration of variables) but my VM now boots into a grub prompt immediately - doesn't ask for LUKS password. I think this may be because I didn't change the "ahci" module to something else in step 3.
> >
> > man grub-mkimage doesn't list possibilities. Can anyone suggest a suitable alternative for a VM created with virt-manager/qemu-kvm?
>
> Are you saying I could try this Section 5 method to have Colemak at GRUB
> and LUKS password prompt? Not VM, but my laptop, real HW.
G
Curt
Sep 19, 2021, 9:20:04 AM9/19/21
to
On 2021-09-19, piorunz <pio...@gmx.com> wrote:
> On 19/09/2021 13:36, Curt wrote:
>> On 2021-09-18, piorunz <pio...@gmx.com> wrote:
>>>
>>> I already selected Colemak in KDE settings, and via sudo
>>> dpkg-reconfigure keyboard-configuration. But this does not affect boot
>>> time password question and GRUB editor. Also virtual consoles still use
>>> default Qwerty.
>>>
>>
>> Maybe something instructive here (or not):
>>
>> https://bbs.archlinux.org/viewtopic.php?id=246453
>>
>>
> Thanks, unfortunately, this is Arch only, vconsole.conf doesn't even
> exist in Debian.
>
Right, but I was alluding to the "solution" by rsolva further down (for
> On 19/09/2021 13:36, Curt wrote:
>> On 2021-09-18, piorunz <pio...@gmx.com> wrote:
>>>
>>> I already selected Colemak in KDE settings, and via sudo
>>> dpkg-reconfigure keyboard-configuration. But this does not affect boot
>>> time password question and GRUB editor. Also virtual consoles still use
>>> default Qwerty.
>>>
>>
>> Maybe something instructive here (or not):
>>
>> https://bbs.archlinux.org/viewtopic.php?id=246453
>>
>>
> Thanks, unfortunately, this is Arch only, vconsole.conf doesn't even
> exist in Debian.
>
the console), which might be practicable in Debian (more or less). Or
maybe not.
ckbcomp -layout no -variant colemak > no-colemak.map gzip
no-colemak.map sudo mv no-colemak.map.gz
/usr/share/kbd/keymaps/i386/colemak/
(For Norwegian colemak.)
I think you need 'console-data'.
> With kindest regards, Piotr.
>
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> ⠈⠳⣄⠀⠀⠀⠀
>
>
piorunz
Sep 19, 2021, 9:30:05 AM9/19/21
to
On 19/09/2021 14:07, Gareth Evans wrote:
>> Are you saying I could try this Section 5 method to have Colemak at GRUB
>> and LUKS password prompt? Not VM, but my laptop, real HW.
>
> Not yet. As things stand, those commands have only succeeded in breaking the VM I set up for the purpose, but I'm hoping someone can suggest the appropriate tweak, if the reason is what I think it is.
Thank you.
>> Are you saying I could try this Section 5 method to have Colemak at GRUB
>> and LUKS password prompt? Not VM, but my laptop, real HW.
>
> Not yet. As things stand, those commands have only succeeded in breaking the VM I set up for the purpose, but I'm hoping someone can suggest the appropriate tweak, if the reason is what I think it is.
To you think, that virtual consoles ignoring my layout setting are a bug?
Basically, doing:
sudo dpkg-reconfigure keyboard-configuration
sudo dpkg-reconfigure console-setup
and reboot
should force Colemak in virtual consoles (the ones in Ctrl+Alt+F keys),
but this is not happening. I have to do "sudo setupcon" (after logging
in with wrong layout) in the console to apply my settings, which are
correctly defined in /etc/default/keyboard file.
If this is correct, everyone else who uses any other layout than US
QWERTY is affected, and I think this could be reported as a bug.
piorunz
Sep 19, 2021, 3:00:06 PM9/19/21
to
On 19/09/2021 14:11, Curt wrote:
>> Thanks, unfortunately, this is Arch only, vconsole.conf doesn't even
>> exist in Debian.
>>
>
> Right, but I was alluding to the "solution" by rsolva further down (for
> the console), which might be practicable in Debian (more or less). Or
> maybe not.
>
> ckbcomp -layout no -variant colemak > no-colemak.map gzip
> no-colemak.map sudo mv no-colemak.map.gz
> /usr/share/kbd/keymaps/i386/colemak/
>
> (For Norwegian colemak.)
>
> I think you need 'console-data'.
Thanks. However,
>> Thanks, unfortunately, this is Arch only, vconsole.conf doesn't even
>> exist in Debian.
>>
>
> Right, but I was alluding to the "solution" by rsolva further down (for
> the console), which might be practicable in Debian (more or less). Or
> maybe not.
>
> ckbcomp -layout no -variant colemak > no-colemak.map gzip
> no-colemak.map sudo mv no-colemak.map.gz
> /usr/share/kbd/keymaps/i386/colemak/
>
> (For Norwegian colemak.)
>
> I think you need 'console-data'.
/usr/share/kbd/ folder doesn't exist on my computer.
Installing console-data doesn't change that.
--
David Wright
Sep 19, 2021, 3:40:04 PM9/19/21
to
everything else? Very relevant to the comment you added to this post.
> > Where did you run "sudo dpkg-reconfigure keyboard-configuration" from?
>
> I run it from Konsole.
spme (mumbling) is done, and this is reversed when you switch
back again. This might be why your changes aren't persisting.
When I configure the keyboard and console-setup, I always do it
before I start X, so I can use my 1988 British IBM clicky keyboard
to login.
However, I've made no attempt to configure Grub, as I know about
the odd punctuation keys that are swapped about with US/GB.
> > Have you seen this line:
> > update-initramfs: Generating /boot/initrd.img-4.19.0-17-amd64
> > since you changed /etc/default/keyboard and ran
> > sudo dpkg-reconfigure keyboard-configuration?
>
> No. sudo dpkg-reconfigure keyboard-configuration asked questions, and
> didn't generated any output in terminal. I actually run this command
> several times now, with reboots, and no change. in
> keyboard-configuration menu itself, Colemak is selected,
> /etc/default/keyboard file also is all correct, but I don't have Colemak
> at dm-crypt password time, nor in virtual consoles (Ctrl+Alt+F keys).
> > Checking your current initrd is a little tedious: you run
> > unmkinitramfs to unpack the initrd, and you zcat your
> > /etc/console-setup/cached_UTF-8_del.kmap.gz to, say, /tmp.
>
> Unpacked:
> unmkinitramfs /boot/initrd.img-$(uname -r) initramfs/
>
> > Then run, eg:
> >
> > $ diff -u …/main/etc/console-setup/cached_UTF-8_del.kmap /tmp/cached_UTF-8_del.kmap
>
> ~/initramfs/main/etc$ ls
> default fonts fstab ld.so.cache ld.so.conf ld.so.conf.d lvm mdadm
> modprobe.d mtab nsswitch.conf os-release passwd plymouth udev
>
> There is no console-setup folder in unpacked initramfs folder.
>
> $ diff -u …/main/etc/console-setup/cached_UTF-8_del.kmap
> /tmp/cached_UTF-8_del.kmap
> diff: …/main/etc/console-setup/cached_UTF-8_del.kmap: No such file or
> directory
> diff: /tmp/cached_UTF-8_del.kmap: No such file or directory
>
> $ apt-file search cached_UTF-8_del.kmap
> (no results here)
Cheers,
David.
Andrei POPESCU
Sep 19, 2021, 3:40:06 PM9/19/21
to
On Du, 19 sep 21, 14:26:34, piorunz wrote:
>
> Thank you.
> To you think, that virtual consoles ignoring my layout setting are a bug?
> Basically, doing:
> sudo dpkg-reconfigure keyboard-configuration
> sudo dpkg-reconfigure console-setup
> and reboot
This works for me, just switched from 'ro' to 'de' and back
>
> Thank you.
> To you think, that virtual consoles ignoring my layout setting are a bug?
> Basically, doing:
> sudo dpkg-reconfigure keyboard-configuration
> sudo dpkg-reconfigure console-setup
> and reboot
(`dpkg-reconfigure console-setup` was not necessary).
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
David Wright
Sep 19, 2021, 4:10:04 PM9/19/21
to
On Sun 19 Sep 2021 at 19:50:22 (+0100), piorunz wrote:
> On 19/09/2021 14:11, Curt wrote:
>
> > > Thanks, unfortunately, this is Arch only, vconsole.conf doesn't even
> > > exist in Debian.
> >
> > Right, but I was alluding to the "solution" by rsolva further down (for
> > the console), which might be practicable in Debian (more or less). Or
> > maybe not.
> >
> > ckbcomp -layout no -variant colemak > no-colemak.map gzip
> > no-colemak.map sudo mv no-colemak.map.gz
> > /usr/share/kbd/keymaps/i386/colemak/
> >
> > (For Norwegian colemak.)
> >
> > I think you need 'console-data'.
>
> Thanks. However,
> /usr/share/kbd/ folder doesn't exist on my computer.
> Installing console-data doesn't change that.
That looks like the way Debian used to handle the keyboard in
> On 19/09/2021 14:11, Curt wrote:
>
> > > Thanks, unfortunately, this is Arch only, vconsole.conf doesn't even
> > > exist in Debian.
> >
> > Right, but I was alluding to the "solution" by rsolva further down (for
> > the console), which might be practicable in Debian (more or less). Or
> > maybe not.
> >
> > ckbcomp -layout no -variant colemak > no-colemak.map gzip
> > no-colemak.map sudo mv no-colemak.map.gz
> > /usr/share/kbd/keymaps/i386/colemak/
> >
> > (For Norwegian colemak.)
> >
> > I think you need 'console-data'.
>
> Thanks. However,
> /usr/share/kbd/ folder doesn't exist on my computer.
> Installing console-data doesn't change that.
pre-squeeze days. For the last ten years, consoles have been
configured using the same files (ie under /usr/share/X11/xkb/)
as X uses.
Cheers,
David.
Curt
Sep 19, 2021, 4:20:05 PM9/19/21
to
>> Right, but I was alluding to the "solution" by rsolva further down (for
>> the console), which might be practicable in Debian (more or less). Or
>> maybe not.
>>
>> ckbcomp -layout no -variant colemak > no-colemak.map gzip
>> no-colemak.map sudo mv no-colemak.map.gz
>> /usr/share/kbd/keymaps/i386/colemak/
>>
>> (For Norwegian colemak.)
>>
>> I think you need 'console-data'.
>
> Thanks. However,
> /usr/share/kbd/ folder doesn't exist on my computer.
> Installing console-data doesn't change that.
Right, but I assumed you'd already understood that though the above
>> the console), which might be practicable in Debian (more or less). Or
>> maybe not.
>>
>> ckbcomp -layout no -variant colemak > no-colemak.map gzip
>> no-colemak.map sudo mv no-colemak.map.gz
>> /usr/share/kbd/keymaps/i386/colemak/
>>
>> (For Norwegian colemak.)
>>
>> I think you need 'console-data'.
>
> Thanks. However,
> /usr/share/kbd/ folder doesn't exist on my computer.
> Installing console-data doesn't change that.
"solution" might be practicable on Debian, it was written for Arch. The
console keymaps are stored in a different directory on Debian.
Installing console-data should provide you with that directory.
piorunz
Sep 19, 2021, 4:40:05 PM9/19/21
to
On 19/09/2021 21:34, piorunz wrote:
> For disclosure, I have full disk encryption on / but /boot and /boot/efi
> are not encrypted, no separate partitions.
I meant *on* separate partitions. Not encrypted. Only / is encrypted.
> For disclosure, I have full disk encryption on / but /boot and /boot/efi
> are not encrypted, no separate partitions.
I meant *on* separate partitions. Not encrypted. Only / is encrypted.
piorunz
Sep 19, 2021, 4:40:05 PM9/19/21
to
On 19/09/2021 20:32, Andrei POPESCU wrote:
> On Du, 19 sep 21, 14:26:34, piorunz wrote:
>>
>> Thank you.
>> To you think, that virtual consoles ignoring my layout setting are a bug?
>> Basically, doing:
>> sudo dpkg-reconfigure keyboard-configuration
>> sudo dpkg-reconfigure console-setup
>> and reboot
>
> This works for me, just switched from 'ro' to 'de' and back
> (`dpkg-reconfigure console-setup` was not necessary).
>
> Kind regards,
> Andrei
>
Did sudo dpkg-reconfigure keyboard-configuration triggerred initramfs
> On Du, 19 sep 21, 14:26:34, piorunz wrote:
>>
>> Thank you.
>> To you think, that virtual consoles ignoring my layout setting are a bug?
>> Basically, doing:
>> sudo dpkg-reconfigure keyboard-configuration
>> sudo dpkg-reconfigure console-setup
>> and reboot
>
> This works for me, just switched from 'ro' to 'de' and back
> (`dpkg-reconfigure console-setup` was not necessary).
>
> Kind regards,
> Andrei
>
update for you, when you did that command?
piorunz
Sep 19, 2021, 4:40:05 PM9/19/21
to
Yes that's right! Thank you. :)
sudo update-initramfs -u -k all
did the trick. I have now Colemak at dm-crypt! Also in virtual consoles.
GRUB editor still uses qwerty, but that's not a concern, dm-crypt
password prompt was most important.
sudo dpkg-reconfigure keyboard-configuration
sudo update-initramfs -u -k all
sudo reboot
probably not needed: sudo dpkg-reconfigure console-setup, but keeping it
in my notepad in case it's required after all in fresh install.
Problem with keyboard-configuration: should this be reported as a bug?
sudo dpkg-reconfigure keyboard-configuration should trigger
update-initramfs on it's own, automatically, otherwise effects of this
command are being ignored until new kernel arrives, computer is rebooted
with new kernel with new initramfs. Correct?
On 19/09/2021 20:36, David Wright wrote:
> Then I would rebuild my initramfs with update-initramfs.
sudo update-initramfs -u -k all
did the trick. I have now Colemak at dm-crypt! Also in virtual consoles.
GRUB editor still uses qwerty, but that's not a concern, dm-crypt
password prompt was most important.
For disclosure, I have full disk encryption on / but /boot and /boot/efi
are not encrypted, no separate partitions.
So, full instruction to achieve your keyboard layout of choice is:
are not encrypted, no separate partitions.
sudo dpkg-reconfigure keyboard-configuration
sudo update-initramfs -u -k all
sudo reboot
probably not needed: sudo dpkg-reconfigure console-setup, but keeping it
in my notepad in case it's required after all in fresh install.
Problem with keyboard-configuration: should this be reported as a bug?
sudo dpkg-reconfigure keyboard-configuration should trigger
update-initramfs on it's own, automatically, otherwise effects of this
command are being ignored until new kernel arrives, computer is rebooted
with new kernel with new initramfs. Correct?
On 19/09/2021 20:36, David Wright wrote:
> Then I would rebuild my initramfs with update-initramfs.
David Wright
Sep 19, 2021, 7:40:04 PM9/19/21
to
On Sun 19 Sep 2021 at 21:34:49 (+0100), piorunz wrote:
> On 19/09/2021 20:36, David Wright wrote:
>
> > Then I would rebuild my initramfs with update-initramfs.
>
> On 19/09/2021 20:36, David Wright wrote:
>
> > Then I would rebuild my initramfs with update-initramfs.
>
> sudo update-initramfs -u -k all
> did the trick. I have now Colemak at dm-crypt! Also in virtual consoles.
> GRUB editor still uses qwerty, but that's not a concern, dm-crypt
> password prompt was most important.
> For disclosure, I have full disk encryption on / but /boot and /boot/efi
> are not encrypted, [on] separate partitions.
> did the trick. I have now Colemak at dm-crypt! Also in virtual consoles.
> GRUB editor still uses qwerty, but that's not a concern, dm-crypt
> password prompt was most important.
> For disclosure, I have full disk encryption on / but /boot and /boot/efi
>
> So, full instruction to achieve your keyboard layout of choice is:
>
> sudo dpkg-reconfigure keyboard-configuration
> sudo update-initramfs -u -k all
> sudo reboot
>
> probably not needed: sudo dpkg-reconfigure console-setup, but keeping it
> in my notepad in case it's required after all in fresh install.
I usually run both, on the basis of "might as well while we're here".
> So, full instruction to achieve your keyboard layout of choice is:
>
> sudo dpkg-reconfigure keyboard-configuration
> sudo update-initramfs -u -k all
> sudo reboot
>
> probably not needed: sudo dpkg-reconfigure console-setup, but keeping it
> in my notepad in case it's required after all in fresh install.
Certainly the naming and placement of files for the two commands is
rather confusing.
> Problem with keyboard-configuration: should this be reported as a bug?
> sudo dpkg-reconfigure keyboard-configuration should trigger
> update-initramfs on it's own, automatically, otherwise effects of this
> command are being ignored until new kernel arrives, computer is rebooted
> with new kernel with new initramfs. Correct?
it several times while trying to find/optimise the best layout/whatever.
Perhaps a warning would suffice.
Cheers,
David.
David Wright
Sep 19, 2021, 7:40:04 PM9/19/21
to
On Sun 19 Sep 2021 at 21:35:52 (+0100), piorunz wrote:
> On 19/09/2021 20:32, Andrei POPESCU wrote:
> > On Du, 19 sep 21, 14:26:34, piorunz wrote:
> > >
> > > Thank you.
> > > To you think, that virtual consoles ignoring my layout setting are a bug?
> > > Basically, doing:
> > > sudo dpkg-reconfigure keyboard-configuration
> > > sudo dpkg-reconfigure console-setup
> > > and reboot
> >
> > This works for me, just switched from 'ro' to 'de' and back
> > (`dpkg-reconfigure console-setup` was not necessary).
>
> On 19/09/2021 20:32, Andrei POPESCU wrote:
> > On Du, 19 sep 21, 14:26:34, piorunz wrote:
> > >
> > > Thank you.
> > > To you think, that virtual consoles ignoring my layout setting are a bug?
> > > Basically, doing:
> > > sudo dpkg-reconfigure keyboard-configuration
> > > sudo dpkg-reconfigure console-setup
> > > and reboot
> >
> > This works for me, just switched from 'ro' to 'de' and back
> > (`dpkg-reconfigure console-setup` was not necessary).
>
> Did sudo dpkg-reconfigure keyboard-configuration triggerred initramfs
> update for you, when you did that command?
I didn't mean to imply that it *should*. Rather, that you have to
> update for you, when you did that command?
do it yourself if you want that reconfiguration to be immediately
available in the early stages of booting.
Cheers,
David.
piorunz
Sep 19, 2021, 8:40:04 PM9/19/21
to
On 20/09/2021 00:33, David Wright wrote:
>> Problem with keyboard-configuration: should this be reported as a bug?
>> sudo dpkg-reconfigure keyboard-configuration should trigger
>> update-initramfs on it's own, automatically, otherwise effects of this
>> command are being ignored until new kernel arrives, computer is rebooted
>> with new kernel with new initramfs. Correct?
>
> It would be rather tedious to automate this for someone who's running
> it several times while trying to find/optimise the best layout/whatever.
> Perhaps a warning would suffice.
Should I report it as wishlist bug against keyboard-configuration?
>> Problem with keyboard-configuration: should this be reported as a bug?
>> sudo dpkg-reconfigure keyboard-configuration should trigger
>> update-initramfs on it's own, automatically, otherwise effects of this
>> command are being ignored until new kernel arrives, computer is rebooted
>> with new kernel with new initramfs. Correct?
>
> It would be rather tedious to automate this for someone who's running
> it several times while trying to find/optimise the best layout/whatever.
> Perhaps a warning would suffice.
Andrei POPESCU
Sep 20, 2021, 1:00:05 AM9/20/21
to
On Lu, 20 sep 21, 01:35:14, piorunz wrote:
> On 20/09/2021 00:33, David Wright wrote:
>
> > > Problem with keyboard-configuration: should this be reported as a bug?
> > > sudo dpkg-reconfigure keyboard-configuration should trigger
> > > update-initramfs on it's own, automatically, otherwise effects of this
> > > command are being ignored until new kernel arrives, computer is rebooted
> > > with new kernel with new initramfs. Correct?
> >
> > It would be rather tedious to automate this for someone who's running
> > it several times while trying to find/optimise the best layout/whatever.
> > Perhaps a warning would suffice.
>
> Should I report it as wishlist bug against keyboard-configuration?
Yes, that would be a good idea in my opinion.
> On 20/09/2021 00:33, David Wright wrote:
>
> > > Problem with keyboard-configuration: should this be reported as a bug?
> > > sudo dpkg-reconfigure keyboard-configuration should trigger
> > > update-initramfs on it's own, automatically, otherwise effects of this
> > > command are being ignored until new kernel arrives, computer is rebooted
> > > with new kernel with new initramfs. Correct?
> >
> > It would be rather tedious to automate this for someone who's running
> > it several times while trying to find/optimise the best layout/whatever.
> > Perhaps a warning would suffice.
>
> Should I report it as wishlist bug against keyboard-configuration?
piorunz
Sep 20, 2021, 10:20:04 AM9/20/21
to
piorunz
Sep 20, 2021, 5:10:03 PM9/20/21
to
Just checked Trisquel GNU/Linux behaviour. Installed latest Triskel (KDE
variation) in VM, results:
$ sudo dpkg-reconfigure keyboard-configuration
[sudo] password for pioruns:
Your console font configuration will be updated the next time your system
boots. If you want to update it now, run 'setupcon' from a virtual console.
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130ubuntu3.13) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-156-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/trisquel--vg-swap_1)
I: Set the RESUME variable to override this
So they have update-initramfs after keyboard-configuration change, and
very informative message about what's going on.
Debian should have that too!
variation) in VM, results:
$ sudo dpkg-reconfigure keyboard-configuration
[sudo] password for pioruns:
Your console font configuration will be updated the next time your system
boots. If you want to update it now, run 'setupcon' from a virtual console.
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130ubuntu3.13) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-156-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/trisquel--vg-swap_1)
I: Set the RESUME variable to override this
So they have update-initramfs after keyboard-configuration change, and
very informative message about what's going on.
Debian should have that too!
0 new messages