Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #90585

Bug#1123985: It seems a keymap issue

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi Salvatore,

Thanks for your help.

It was indeed an issue outside of the kernel package and thanks to your things to try I figured it out.
Initially also though about the initramfs-tools package, would have been strange as it hasn't changed for a few months. 


As you recommended I installed the 6.18 kernel from experimental and noticed the following warning during the install:

  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-6.18-amd64
  setupcon is missing. Please install the 'console-setup' package.


As expected from this the issue was still there, had to use the US layout to enter the passphrase. After (re)installing 'console-setup' and reinstalling the kernel it works fine using my swiss french layout.

No idea how I managed to bork my system between the 6.17.11 and 6.17.12 kernels by accidentally uninstalling this package.

Now just need to regenerate all initramfs.

Thanks for your help again, sorry to have bothered you with a bug report that was just an error on my side. So issue closed.

Best regards,

Martin


Sent with Proton Mail secure email.

On Friday, December 26th, 2025 at 5:04 PM, Salvatore Bonaccorso <carnil@debian.org> wrote:

> Hi Martin,
> 

> On Fri, Dec 26, 2025 at 10:36:53AM +0000, Martin Herren wrote:
> 

> > Hello,
> > 

> > After further testing I can boot both 6.17.12 and 6.17.13 kernels by
> > typing the passphrase as on a US keyboard layout.
> > 

> > With the 6.17.11 and previous kernels I can type it with my usual
> > Swiss French keyboard layout.
> 

> 

> This is quite odd, and initially I suspected a change outside of the
> kernel. But would you be open to do a bisect experiment? But before
> diving into it, might you please as well install 6.18.2-1~exp1 from
> experimental and verify if the problem persists? There won't be any
> updates in the 6.17.y series.
> 

> If the problem persists in 6.18.2 then we might start with the bisect
> experiment in the 6.17.y series.
> 

> This would involve compiling and testing a couple of kernels, and the
> first step would indicate already if we would be still on the right
> track.
> 

> git clone --single-branch -b linux-6.17.y https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> cd linux-stable
> git checkout v6.17.11
> cp /boot/config-$(uname -r) .config
> yes '' | make localmodconfig
> make savedefconfig
> mv defconfig arch/x86/configs/my_defconfig
> 

> # test 6.17.11 to ensure this is "good"
> make my_defconfig
> make -j $(nproc) bindeb-pkg
> ... install the resulting .deb package and confirm it the problem does not exist.
> 

> This is actually an intersting step, I would be interested to see
> if any surrounding changes did influence that it does not work
> anymore with 6.17.11.
> 

> # test 6.17.12 to ensure this is "bad"
> git checkout v6.17.12
> make my_defconfig
> make -j $(nproc) bindeb-pkg
> ... install the resulting .deb package and confirm the problem exists.
> 

> Now if and only if that is confirmed, the bisection can start:
> 

> git bisect start
> git bisect good v6.17.11
> git bisect bad v6.17.12
> 

> In each bisection step git checks out a state between the oldest
> known-bad and the newest known-good commit. In each step test using:
> 

> make my_defconfig
> make -j $(nproc) bindeb-pkg
> ... install, try to boot / verify if problem exists
> 

> and if the problem is hit run:
> 

> git bisect bad
> 

> and if the problem doesn't trigger run:
> 

> git bisect good
> 

> . Please pay attention to always select the just built kernel for
> booting, it won't always be the default kernel picked up by grub.
> 

> Iterate until git announces to have identified the first bad commit.
> 

> Then provide the output of
> 

> git bisect log
> 

> In the course of the bisection you might have to uninstall previous
> kernels again to not exhaust the disk space in /boot. Also in the end
> uninstall all self-built kernels again.
> 

> Regards,
> Salvatore

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1123985: linux-image-6.17.12+deb14-amd64: LUKS passphrase never matches on 6.17.12 and 6.17.13. Works fine on 6.17.11. Martin Herren <sputnik@on-the-web.ch> - 2025-12-25 16:40 +0100
  Bug#1123985: It seems a keymap issue Martin Herren <sputnik@on-the-web.ch> - 2025-12-26 12:10 +0100
    Bug#1123985: It seems a keymap issue Salvatore Bonaccorso <carnil@debian.org> - 2025-12-26 18:10 +0100
      Bug#1123985: It seems a keymap issue Martin Herren <sputnik@on-the-web.ch> - 2025-12-26 20:10 +0100
  Bug#1123985: marked as done (linux-image-6.17.12+deb14-amd64:  LUKS passphrase never matches on 6.17.12 and 6.17.13. Works fine on  6.17.11.) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-12-26 20:50 +0100

csiph-web