Hi, On Sat, Feb 07, 2026 at 11:35:03AM +0100, Salvatore Bonaccorso wrote: > Hi, > > On Fri, Feb 06, 2026 at 09:48:34PM +0000, Vicboom18 wrote: > > This bug has also been reported to Debian. You can track it here: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126149 (Debian Bug > > #1126149). > > Well yes, I know it is reported there in Debian. > > let me phrase it differently. I won't provide private support, that is > please *always* include the Debian BTS email address as well in the > replies, so others in the team are aware as well of the progress. > > > Both boot logs have attached, in both cases the computer were turned on > > with the keyboard connected, then it was disconnected and connected again. > > > > As it can bee seen in PC_boot.log I also went back to the 6.12 LTS kernel, > > as the 6.17 was installed in order to try to fix the issue on my own (with > > no success) > > Thank you. So I see in the one variant it seems to recocnize correctly > the keyboard. So we should still try to quirk before forwarding your > report to upstream. > > > When trying the official guide (from point 4.5.1 up to 4.5.2, skipping > > 4.5.1.1) it seems to fail in the $ debian/bin/test-patches command. > > I need here the full context. As > > set +e; QUILT_PC=.pc quilt unapplied --quiltrc - >/dev/null && echo 'Patch > series not fully applied'; test $? -eq 1 > Patch series not fully applied > > > I think you need to massage a bit the patch yet for context in > 6.12.63. I will see if I can provide you a test kernel to test it more > reasily.
here we go, can you please test it with the (unofficial!) kernel provided in https://people.debian.org/~carnil/tmp/linux/1126149/ and report back if that resolves the issue? Regards, Salvatore
