I am trying to install Fedora 40 again. However, after booting into Fedora, the keyboard doesnt input anything on the screen. I have installed Fedora in the past on the same PC, since then I did change my keyboard. The same happens when I boot into Debian. The keyboard works without any issue on Windows on the same PC. If I boot into Fedora on a different laptop, and connect the same keyboard, it works.
Sounds like a hardware problem with the keyboard.
Can you try with a different keyboard to see if that works?
2 Likes
just tested it with my last keyboard that has a few working key and it works!
But if I connect my main keyboard, which I mentioned in my first post, to a laptop it works without any issue. I still can avail the warranty of the keyboard but I wont be able to if it ends up working on the vendor’s PC.
What keyboard?
I have a CORSAIR RGB K70 keyboard and Harpoon RGB (both Pro and non-Pro) mouse and all 3 were notorious for holding-up boots due to some usbhid error, and not being available when the log-in screen finally appears. In this case, ckb-next recommends generating and using some boot kernel options.
I also found that using these devices behind a USB-C hub work consistently fine; it’s just when they’re plugged directly into my laptop that they’re sometimes an issue (without the boot options). This might explain why your main keyboard works fine on another computer.
I am using Zifriend ZA63, a Chinese brand that became popular here locally for its budgets options.
There might have been something like that when the boot device was tested during boot.
Thank you, I tried reading the repository and don’t think I understand that. I am just a novice at best.
I connected to my laptop directly.
I somehow tried this. Got some errors when I tried to do it during boot. Must have done something wrong.
error: ..//../grub-core/script/lexer.c:352:syntax error.
error: ..//../grub-core/script/lexer.c:352:Incorrect command.
error: ..//../grub-core/script/lexer.c:352:syntax error.
I tried it again on the terminal after boot, used KDEconnect and my phone to navigate. The terminal provided no output. Must have done something wrong there too.
The boot options should look something like usbhid.quirks=0x1b1c:0x1b20:0x20000408 and usbcore.quirks=1b1c:1b2e:gn, but the commands ckb-next provides generates those based on currently-connected devices with the CORSAIR vendor ID (1b1c). When I get Linux reinstalled I’ll try seeing what those look like with a single device.
Typing lsusb from a Terminal should report the ZA63 somewhere, and it should report a vendor ID for Zifriend or whatever company might show there.
If possible, can you copy/paste the results of lsusb, or just the section for the keyboard? It might look something like this (but probably less for a keyboard):
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 [unknown]
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 6.05
iManufacturer 3 Linux 6.5.11-300.fc39.x86_64 xhci-hcd
iProduct 2 xHCI Host Controller
iSerial 1 0000:00:14.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0019
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 [unknown]
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 13
bDescriptorType 41
nNbrPorts 16
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00 0x4f 0x00
PortPwrCtrlMask 0xff 0xff 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0103 power enable connect
Port 3: 0000.0100 power
Port 4: 0000.0503 highspeed power enable connect
Port 5: 0000.0100 power
Port 6: 0000.0100 power
Port 7: 0000.0100 power
Port 8: 0000.0100 power
Port 9: 0000.0100 power
Port 10: 0000.0100 power
Port 11: 0000.0100 power
Port 12: 0000.0100 power
Port 13: 0000.0100 power
Port 14: 0000.0107 power suspend enable connect
Port 15: 0000.0100 power
Port 16: 0000.0100 power
Device Status: 0x0001
Self Powered
do I have to do this during boot in the boot menu
or after boot?
After boot and in the OS (log-in and type lsusb from GNOME Terminal)
i just got this :
$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 002: ID 0781:5597 SanDisk Corp. SanDisk 3.2Gen1
ill take a look from the laptop as well.
this is from the laptop, same boot drive same keyboard connected externally:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 13d3:56ff IMC Networks Integrated Camera
Bus 003 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 003 Device 004: ID 5566:0008 ZXWMicroChip ZXW-KEYBOARD
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 0781:5597 SanDisk Corp. SanDisk 3.2Gen1```