After some system updates, the keyboard and the mouse become unusable
(and the keyboard is not illuminated) during boot: I cannot access
BIOS and cannot select grub entries.
Then, once system started, both keyboard and mouse become usable.
Later, after other system updates, the the keyboard and the mouse are
working again during boot, and so on: the on/off cycle repeats.
I need to identify a package to fill a bug report and I need help for that.
On my laptop (Debian unstable) I'm using external illuminated keyboard and mouse connected to
- Dell dock connected via thunderbolt
or
- U2724de Dell monitor also connected via thunderbolt
After some system updates, the keyboard and the mouse become unusable (and the keyboard is not illuminated) during boot: I cannot access BIOS and cannot select grub entries.
Then, once system started, both keyboard and mouse become usable.
Later, after other system updates, the the keyboard and the mouse are working again during boot, and so on: the on/off cycle repeats.
Which package I need to fill into the bug report?
This may have nothing to do with Debian or any OS. It could be either firmware in
the motherboard
On 9 Jul 2025, at 17:30, Greg <[email protected]> wrote:
On 2025-07-09, Nicolas George <[email protected]> wrote:
Felix Miata (HE12025-07-09):
This may have nothing to do with Debian or any OS. It could be either firmware in
the motherboard
Nit: the firmware in the motherboard is an operating system.
Is the firmware in the motherboard otherwise referred to as the BIOS?
(I'm subscribed there. No need to Cc: me.)
Reply-To: [email protected]
https://lists.debian.org/debian-user/
does not deliver a page, although ping lists.debian.org works fine.
Are alternative archive URLs known ? E.g. to USENET linux.debian.user ?
Wolf wrote:
I don't think it's a firmware problem: both the keyboard and the mouse are working after boot.That's possibly because the Linux drivers perform some settings on
the hardware. The boot firmware (EFI ?) and GRUB obviously don't do
what is needed.
Hi,
please reply to the list [email protected] instead to
me in private. (I'm subscribed there. No need to Cc: me.)
Since i seem to be the only responder who send you a Cc: , i wanted
to point you to the other answers to your initial mail in the list
archives. But
https://lists.debian.org/debian-user/
does not deliver a page, although ping lists.debian.org works fine.
Are alternative archive URLs known ? E.g. to USENET linux.debian.user ?
The content of your in-private reply does not look like it is
confidential. So i quote from it publicly.
Wolf wrote:
I don't think it's a firmware problem: both the keyboard and the mouse are working after boot.
That's possibly because the Linux drivers perform some settings on
the hardware. The boot firmware (EFI ?) and GRUB obviously don't do
what is needed.
Recent history:
More than a month ago, keyboard become unusable after upgrade.
But, last week, an upgrade solved the problem: ---------------------------------------------------------------
Start-Date: 2025-07-04 07:41:06
Commandline: apt upgrade
Requested-By: g (1000)
Upgrade: libvirt-common:amd64 (11.3.0-2, 11.3.0-3), libperl5.40:amd64 (5.40.1-3, 5.40.1-5), libvirt-daemon-driver-storage-logical:amd64 (11.3.0-2,
11.3.0-3), libvirt-daemon-config-nwfilter:amd64 (11.3.0-2, 11.3.0-3), libvirt-daemon-driver-xen:amd64 (11.3.0-2, 11.3.0-3), perl:amd64 (5.40.1-3, 5.40.1-5), libvirt-daemon:amd64 (11.3.0-2, 11.3.0-3), ibus-gtk3:amd64 (1.5.32-1, 1.5.32-2), ibus-gtk4:amd64 (1.5.32-1, 1.5.32-2), firefox-nightly:amd64 (142.0a1~20250702212902, 142.0a1~20250703203803), python3-ibus-1.0:amd64 (1.5.32-1, 1.5.32-2), libvirt-daemon-driver-storage-disk:amd64 (11.3.0-2, 11.3.0-3), libvirt-daemon-plugin-lockd:amd64 (11.3.0-2, 11.3.0-3), libvirt-daemon-driver-storage-iscsi:amd64 (11.3.0-2, 11.3.0-3), libvirt-daemon-driver-nodedev:amd64 (11.3.0-2, 11.3.0-3), grub-efi-amd64-unsigned:amd64 (2.12-8, 2.12-9), libvirt-daemon-lock:amd64 (11.3.0-2, 11.3.0-3), libvirt0:amd64 (11.3.0-2, 11.3.0-3), grub-efi-amd64:amd64 (2.12-8, 2.12-9), libvirt-daemon-driver-nwfilter:amd64 (11.3.0-2, 11.3.0-3), libvirt-daemon-driver-vbox:amd64 (11.3.0-2, 11.3.0-3),
gir1.2-ibus-1.0:amd64 (1.5.32-1, 1.5.32-2), ibus-data:amd64 (1.5.32-1, 1.5.32-2), libvirt-daemon-driver-qemu:amd64 (11.3.0-2, 11.3.0-3), grub-efi-amd64-signed:amd64 (1+2.12+8, 1+2.12+9), libvirt-clients:amd64 (11.3.0-2, 11.3.0-3), libvirt-daemon-common:amd64 (11.3.0-2, 11.3.0-3), anydesk:amd64 (7.0.0, 7.0.1), libvirt-daemon-log:amd64 (11.3.0-2, 11.3.0-3),
libvirt-daemon-driver-secret:amd64 (11.3.0-2, 11.3.0-3), libvirt-daemon-config-network:amd64 (11.3.0-2, 11.3.0-3), libvirt-l10n:amd64
(11.3.0-2, 11.3.0-3), gnome-control-center-data:amd64 (1:48.2-2, 1:48.3-3), libvirt-daemon-driver-interface:amd64 (11.3.0-2, 11.3.0-3), grub-efi-amd64-bin:amd64 (2.12-8, 2.12-9), grub2-common:amd64 (2.12-8, 2.12-9), plasma-nm:amd64 (4:6.3.4-1, 4:6.3.4-2), perl-base:amd64 (5.40.1-3, 5.40.1-5), grub-common:amd64 (2.12-8, 2.12-9), libvirt-daemon-driver-network:amd64 (11.3.0-2, 11.3.0-3), ibus-gtk:amd64 (1.5.32-1, 1.5.32-2), gnome-control-center:amd64 (1:48.2-2, 1:48.3-3), ibus:amd64 (1.5.32-1, 1.5.32-2), libvirt-daemon-system:amd64 (11.3.0-2, 11.3.0-3), perl-modules-5.40:amd64 (5.40.1-3, 5.40.1-5), libvirt-daemon-driver-storage-mpath:amd64 (11.3.0-2, 11.3.0-3), libibus-1.0-5:amd64 (1.5.32-1, 1.5.32-2), libvirt-daemon-driver-storage-scsi:amd64 (11.3.0-2, 11.3.0-3), libvirt-daemon-driver-lxc:amd64 (11.3.0-2, 11.3.0-3)
End-Date: 2025-07-04 07:41:35 ---------------------------------------------------------------
The keyboard and the mouse worked well, but two days later, after the another upgrade ----------------------------------------------------------------------------
-----
Start-Date: 2025-07-06 09:27:29
Commandline: apt upgrade
Requested-By: g (1000)
Upgrade: firefox-nightly:amd64 (142.0a1~20250704212032, 142.0a1~20250705211551), firmware-sof-signed:amd64 (2025.01-1, 2025.05-1), mobile-broadband-provider-info:amd64 (20240407-1, 20250613-2)
End-Date: 2025-07-06 09:27:35 ----------------------------------------------------------------------------
-----
the keyboard and the mouse are, again, not available at boot.
Any thought about firmware-sof-signed package?
Debian's package info infrastructure is unresponsive too: https://packages.debian.org/unstable/firmware-sof-signed
So:
https://launchpad.net/ubuntu/plucky/+package/firmware-sof-signed
"Intel SOF firmware - signed
Provides the Intel SOF audio firmware and topology needed for audio functionality on some Intel system."
This does not look overly suspicious for sabotaging a keyboard.
Have a nice day :)
Thomas
Hi,
Wolf wrote:
My default settings in EFI was Thunderbolt security: OFF.
Today, I changed security from OFF to "User Authorization" and now keyboard is working.
I tested changing back from "User Authorization" to OFF and the keyboard
became unusable again.
I wrote:
(So Thunderbolt is off, not the security. {:)
Max Nikulin wrote:
Might it be related to requirement of physical presence as an attempt to protect against unauthorized changing of boot options? Depending on firmware
implementation it may trust some input devices more than others.
That's what i, too, fuzzily understand from "Thunderbolt security:".
The question is what manipulates this setting so that the keyboard is accepted or not accepted before Linux is up.
If it is indeed the upgrade of some Debian packages, then we only have
three candidates for disabling the keyboard: ----------------------------------------------------------------------- Start-Date: 2025-07-06 09:27:29
Commandline: apt upgrade
Requested-By: g (1000)
Upgrade: firefox-nightly:amd64 (142.0a1~20250704212032, 142.0a1~20250705211551), firmware-sof-signed:amd64 (2025.01-1, 2025.05-1), mobile-broadband-provider-info:amd64 (20240407-1, 20250613-2)
End-Date: 2025-07-06 09:27:35 -----------------------------------------------------------------------
I posted this in a quote from an inadvertedly private mail by Wolf: https://lists.debian.org/msgid-search/[email protected]
The list of suspects for enabling is in there too. But much longer.
The open problem is how to verify or disprove that above upgrade run
really causes the change in the EFI setting.
I would propose "apt-get install --reinstall" but have to confess that
i am too cowardish to test such a proposal before making it and that i
also don't know how much this resembles an "apt upgrade" which installs
the same packages.
Have a nice day :)
Thomas
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 165:33:05 |
| Calls: | 12,096 |
| Calls today: | 4 |
| Files: | 15,001 |
| Messages: | 6,517,806 |