ESC Key not works anymore to display boot up sequences in F42 |what could be the issue

Ask Fedora
,
1

In other DE’s I still can use ESC to interrupt the Boot image, to see the boot sequences (F42).

Is this a side effect of some changes in Gnome (Global shortcuts as an example)?

I tested on Xfce rawhide in a VM and there it still works.

2

It is not the DE that handles the ESC to show boot messages.
It is plymouth, and plymouth is used on all Fedora editions.

4

ESC works for me on the systems that I have not disabled plymouth on.
I like to see the boot messages, so plymouth is disabled on most of my systems.

5

I saw this (fresh install before I had removed the rhgb quiet from the kernel command-line) at boot time with a old Apple keyboard – plugging in a newer Dell keyboard the escape key worked.

1 Like
6

I used a K230 Keyboard & M585 mouse with the dongle below and get the described issue

      # Unifiing Receiver
      Summary:             Miniaturised USB wireless receiver
      Current version:    RQR24.11_B0036
      Bootloader Version: BOT03.02_B0009
      Vendor:               Logitech, Inc. (USB:0x046D, HIDRAW:0x046D)

I checked also with a MK270/M15 combo wireless keyboard/mouse and still can not use the ESC button for the task mentioned above.

Last check I will do is with a usb cable keyboard to see if this changes something.

7

Does the keyboard work to enter the BIOS?
I wonder if it takes time for the keyboard to activate.

Does ESC work on a wired keyboard?

8

Keyboard with a usb cable works :bluethumb:

I also charged the batteries from the keyboard and tried again. Without any real sucess.

F42 Boot iso works too.

Kernel 6.14.5 works partialy. I have to hit several times. And it displays not so early.

On Grub level it still works.

9

Some Jounal messages:

journalctl --no-tail --no-hostname -S "today" |grep "logitech"

mai 27 08:37:11 kernel: clocksource: Switched to clocksource tsc
mai 27 08:37:11 kernel: usb 4-1.6: new full-speed USB device number 3 using ehci-pci
mai 27 08:37:11 kernel: usb 4-1.6: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=24.11
mai 27 08:37:11 kernel: usb 4-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
mai 27 08:37:11 kernel: usb 4-1.6: Product: USB Receiver
mai 27 08:37:11 kernel: usb 4-1.6: Manufacturer: Logitech
mai 27 08:37:11 kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.0/0003:046D:C52B.0001/input/input6
mai 27 08:37:11 kernel: hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.0-1.6/input0
mai 27 08:37:11 kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.1/0003:046D:C52B.0002/input/input7
mai 27 08:37:11 kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.1/0003:046D:C52B.0002/input/input8
mai 27 08:37:11 kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.1/0003:046D:C52B.0002/input/input9
mai 27 08:37:11 kernel: hid-generic 0003:046D:C52B.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-1.6/input1
mai 27 08:37:11 kernel: hid-generic 0003:046D:C52B.0003: hiddev97,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1.6/input2
mai 27 08:37:11 kernel: usb 2-1.3: New USB device found, idVendor=13d3, idProduct=3331, bcdDevice=52.76
mai 27 08:37:11 kernel: usb 2-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0


mai 27 08:37:12 kernel: logitech-djreceiver 0003:046D:C52B.0003: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1.6/input2
mai 27 08:37:12 systemd[1]: systemd-vconsole-setup.service: Deactivated successfully.
mai 27 08:37:12 systemd[1]: Stopped systemd-vconsole-setup.service - Virtual Console Setup.
mai 27 08:37:12 systemd[1]: Stopping systemd-vconsole-setup.service - Virtual Console Setup...
mai 27 08:37:12 systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup...
mai 27 08:37:12 kernel: input: Logitech Wireless Device PID:400d Keyboard as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.6/4-1.6:1.2/0003:046D:C52B.0003/0003:046D:400D.0004/input/input11
mai 27 08:37:12 systemd[1]: Mounted sysroot.mount - /sysroot.
mai 27 08:37:12 systemd[1]: Reached target initrd-root-fs.target - Initrd Root File System.
mai 27 08:37:12 systemd[1]: Starting initrd-parse-etc.service - Mountpoints Configured in the Real Root...
mai 27 08:37:12 kernel: hid-generic 0003:046D:400D.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Wireless Device PID:400d] on usb-0000:00:1d.0-1.6/input2:1
10

You can use your wired keyboard when debugging your system.
I doubt it will be considered an issue that the wireless keyboard turns up late in the boot process.