Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #61648 > unrolled thread
| Started by | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| First post | 2018-07-27 15:20 +0200 |
| Last post | 2018-07-27 16:00 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#903641: Preserve numlock state during cryptdisk boot password prompt in plymouth Ben Hutchings <ben@decadent.org.uk> - 2018-07-27 15:20 +0200
Processed: Re: Preserve numlock state during cryptdisk boot password prompt in plymouth "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-07-27 15:20 +0200
Bug#903641: Preserve numlock state during cryptdisk boot password prompt in plymouth Pascal Vibet - ADACIS <pvibet@gmail.com> - 2018-07-27 16:00 +0200
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2018-07-27 15:20 +0200 |
| Subject | Bug#903641: Preserve numlock state during cryptdisk boot password prompt in plymouth |
| Message-ID | <wgaOZ-9y-3@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Control: tag -1 moreinfo On Thu, 12 Jul 2018 15:02:20 +0200 Pascal Vibet - ADACIS <pvibet@gmail.com> wrote: > Package: cryptsetup-initramfs > Version: 2:2.0.2-1ubuntu1 > > Dear Maintainers, i propose you my fix to this problem. > > I'm using smartcard to decrypt luks disk, i'm using decrypt_opensc > script in /etc/crypttab. I want to preserve numlock state during > cryptdisk boot password prompt. > > I found this article: > https://superuser.com/questions/1062979/preserve-numlock-state-during-cryptdisk-boot-password-prompt-in-plymouth [...] If plymouth specifically changes Num Lock state, this may be a bug in plymouth. However, I don't think it does. I have a theory as to what might be happening: * Each Linux virtual terminal (VT) has an independent keyboard lock/LED state. When a different VT is activated, the driver will apply the lock/LED state for that VT. * If you boot Linux in BIOS mode, the default state of Num Lock is set acccording to what the BIOS says it should be. * If you boot Linux some other way, like UEFI, the default state is unknown and assumed to be off. * plymouth opens and activates a new VT. This applies the default state. Does this system boot using the BIOS or UEFI? If it boots using UEFI, you can test this theory by doing: 1. In the boot menu, edit the kernel command line to remove "splash" and add "break=premount". 2. At the initramfs shell prompt, enter "openvt" to create a new VT. 3. Press Alt-F2 to activate the new VT. Does Num Lock turn off? 4. Press Alt-F1 to activate the first VT. Does Num Lock turn on or off? Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2018-07-27 15:20 +0200 |
| Subject | Processed: Re: Preserve numlock state during cryptdisk boot password prompt in plymouth |
| Message-ID | <wgaOZ-9y-7@gated-at.bofh.it> |
| In reply to | #61648 |
Processing control commands: > tag -1 moreinfo Bug #903641 [initramfs-tools-core] initramfs-tools-core: 'keymap' scripts don't preserve numlock state Added tag(s) moreinfo. -- 903641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903641 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | Pascal Vibet - ADACIS <pvibet@gmail.com> |
|---|---|
| Date | 2018-07-27 16:00 +0200 |
| Message-ID | <wgbrH-na-5@gated-at.bofh.it> |
| In reply to | #61648 |
[Multipart message — attachments visible in raw view] — view raw
Hi, i will test your solutions. Regards 2018-07-27 15:13 GMT+02:00 Ben Hutchings <ben@decadent.org.uk>: > Control: tag -1 moreinfo > > On Thu, 12 Jul 2018 15:02:20 +0200 Pascal Vibet - ADACIS <pvibet@gmail.com> > wrote: > > Package: cryptsetup-initramfs > > Version: 2:2.0.2-1ubuntu1 > > > > Dear Maintainers, i propose you my fix to this problem. > > > > I'm using smartcard to decrypt luks disk, i'm using decrypt_opensc > > script in /etc/crypttab. I want to preserve numlock state during > > cryptdisk boot password prompt. > > > > I found this article: > > https://superuser.com/questions/1062979/preserve-numlock-state-during- > cryptdisk-boot-password-prompt-in-plymouth > [...] > > If plymouth specifically changes Num Lock state, this may be a bug in > plymouth. However, I don't think it does. > > I have a theory as to what might be happening: > > * Each Linux virtual terminal (VT) has an independent keyboard > lock/LED state. When a different VT is activated, the driver will > apply the lock/LED state for that VT. > * If you boot Linux in BIOS mode, the default state of Num Lock is set > acccording to what the BIOS says it should be. > * If you boot Linux some other way, like UEFI, the default state is > unknown and assumed to be off. > * plymouth opens and activates a new VT. This applies the default > > state. > > Does this system boot using the BIOS or UEFI? > > If it boots using UEFI, you can test this theory by doing: > > 1. In the boot menu, edit the kernel command line to remove "splash" > and add "break=premount". > 2. At the initramfs shell prompt, enter "openvt" to create a new VT. > 3. Press Alt-F2 to activate the new VT. Does Num Lock turn off? > 4. Press Alt-F1 to activate the first VT. Does Num Lock turn on or > off? > > Ben. > > -- > Ben Hutchings > Power corrupts. Absolute power is kind of neat. - John Lehman > >
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web