I recently upgraded my PC to a AM5 motherboard. My system runs KDE neon with full disk encryption.

I’m now facing the issue that when I want to enter my password in GRUB, each normal key press on my keyboard prints at least 5-10 letters on the screen. So if my password were “password”, it would look like “ppppppaaaaaasssssssssssswwwww…” and so on. I need at least 5 attempts with very quick reflexes to only press each key only once for a split second. It’s very annoying but once I make it past GRUB, everything works normally.

From what I’ve read so far the issue seems to have something to do with the USB port that the keyboard is plugged into and people seem to have fixed it by switching to a 2.0 port instead of a 3.0 port. My motherboard only has 3.0 and 3.2 ports though, so I was wondering if there is any way to change the “refresh rate” in GRUB, so to speak. Any help or advice would be greatly appreciated!

  • BigMikeInAustin@lemmy.worldEnglish
    7·
    1 month ago

    If your faster computer now requires you, yourself, to move faster, then relative to you, the new computer might run at the old speed, or slower. Hmm.

  • PseudoSpock@lemmy.dbzer0.com
    6·
    1 month ago

    That explains a lot of what I’ve been experiencing for quite some time now. Laptop’s internal keyboard types fine in grub, but usb keyboards the password is wrong more often than not.

  • bloodfart@lemmy.ml
    5·
    1 month ago

    Someone else said to get a usb2.0 hub. This fixes the problem.

    USB is a bad standard for a lot of reasons. The hid specification across versions is one of em.

  • MXX53@programming.dev
    4·
    1 month ago

    I am pulling this totally out of my ass, and I might be making assumptions to aren’t necessarily true or accurate. But, maybe you can run a powered USB 2.0 hub on one of those 3.0 ports. My assumption would be the chain would only be as strong as the weakest link (2.0 hub) that you might be able to get 2.0 performance on those 3.0 ports.

    This would at least possibly eliminate or confirm down stepping to 2.0 as a solution

    But I have not had this issue and could not tell you if it would work or not.

  • gnuhaut@lemmy.ml
    3·
    1 month ago

    I don’t think the problem is with GRUB.

    There are various different ways in which USB keyboards can encode keypresses. I’ve seen some BIOSes that just cannot deal with some keyboards due to this. The USB keyboard driver that will be in use during GRUB should be the BIOS/UEFI driver. So I would try updating the mainboard firmware/EFI or try a different keyboard maybe? Or disable the GRUB password if that’s an option.