Grub frequently does not recognise keyboard

[lsemmens]

This has been happening on and off for quite some time, and only on my office computer. I have a dual boot system and, often when I wish to boot into that "other" operating system I select reboot and the system restarts into Grub where I've st the default to load Linux after 20 seconds. Problem is my keyboard is completely unrecognised on may occasions. I can't even say that there appears to be any pattern to it. If I hit ESC whilst BIOS is loading I can boot into UEFI mode, from there I can boot the alternate, but that is a nuisance. I've even tried a cold boot, and, mostly, that solves the issue, but not always. I've just tried a half a dozen times using various parameters to no avail.

Is it likely to be hardware related? (I don't think so as the keyboard behaves fine when in an operating system or in BIOS.

Any ideas as to where I can look? Please?

Code: Select all

officelinux@officelinux-HP-Compaq-8200-Elite-SFF-PC:~$ inxi -Fxxxz
System:
  Kernel: 5.4.0-126-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 
  Desktop: Cinnamon 5.2.7 wm: muffin 5.2.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Compaq 8200 Elite SFF PC 
  v: N/A serial: <filter> Chassis: type: 6 serial: <filter> 
  Mobo: Hewlett-Packard model: 1495 serial: <filter> UEFI: Hewlett-Packard 
  v: J01 v02.01 date: 04/06/2011 
CPU:
  Topology: Quad Core model: Intel Core i5-2400 bits: 64 type: MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 6144 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24748 
  Speed: 1596 MHz min/max: 1600/3100 MHz Core speeds (MHz): 1: 1597 2: 1597 
  3: 1597 4: 1597 
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
  vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:0102 
  Display: x11 server: X.Org 1.20.13 driver: modesetting 
  unloaded: fbdev,vesa resolution: 1360x768~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1) 
  v: 3.3 Mesa 21.2.6 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:1c20 
  Device-2: Logitech QuickCam Messenger type: USB 
  driver: STV06xx,snd-usb-audio bus ID: 1-1.3:4 chip ID: 046d:08f0 
  Sound Server: ALSA v: k5.4.0-126-generic 
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard 
  driver: e1000e v: 3.2.6-k port: f080 bus ID: 00:19.0 chip ID: 8086:1502 
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 2.08 TiB used: 1.33 TiB (64.0%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 850 PRO 128GB size: 119.24 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT 
  ID-2: /dev/sdb vendor: Western Digital model: WD10EADS-00M2B0 
  size: 931.51 GiB speed: 3.0 Gb/s serial: <filter> rev: 0A01 scheme: MBR 
  ID-3: /dev/sdc type: USB vendor: Western Digital model: WD10EADS-11M2B2 
  size: 931.51 GiB serial: <filter> rev: 2002 scheme: MBR 
  ID-4: /dev/sdd type: USB vendor: Hitachi model: HTS541616J9SA00 
  size: 149.05 GiB serial: <filter> rev: 1.14 scheme: MBR 
Partition:
  ID-1: / size: 45.84 GiB used: 13.71 GiB (29.9%) fs: ext4 dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 236 Uptime: 2m Memory: 13.56 GiB used: 1.02 GiB (7.6%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

[hglee]

I have a dual boot system and, often when I wish to boot into that "other" operating system I select reboot and the system restarts...

Next time you power-up, detour into the BIOS and disable Secure Boot, because it's known to interfere with device drivers & firmware. Microsoft admits it's problematic.

More important: Disable Windows Fast Startup, otherwise it can leave your PC hardware in a zombie state at any time. I disable Hibernation, which also disables Fast Startup, plus prevents Windows Update from surreptitiously re-enabling Fast Startup.

When you switch from Windows to Linux, do a full Shutdown, not just a Restart. The beast must be rendered lifeless.

These changes alone could remedy your woes.

[lsemmens]

Thanks mate, will double check all of those as I should have done it when last I re-loaded the machine.

[DisturbedDragon]

I had this same problem not long ago. Computer worked fine in every way, except boot selection in grub. Re-installed grub but nothing changed.Thought I had a failing motherboard but it turned out to be a RAM issue. Replaced it and no more issues in grub.

[lsemmens]

Not solved the settings are all correct in Windows and Linux as far as I can tell. BIOS has be modified and re-modified and modified again, On a cold boot it is hit and miss as to if the ESC key works to enable access to BIOS. Once I do finally get into Windows or Linux all works as intended.

I've set up my lappy as dual boot and have no issues at all with that.

[all41]

I had this same problem not long ago. Computer worked fine in every way, except boot selection in grub. Re-installed grub but nothing changed.Thought I had a failing motherboard but it turned out to be a RAM issue. Replaced it and no more issues in grub.

Intermittent ram can drive one bananas.
Doesn't always show up in stress tests

But back to the keyboard issue. Is it a usb device

[all41]

Is this a wireless usb keyboard? wireless kb/mouse combo? bluetooth?
Say more about this hardware.
Maybe not an uncommon issue with older pc bios

[lsemmens]

Usung an HP USB keyboard and Logitech ps/2 trackman. A USB wireless mouse (microsoft) makes no difference.

[cfb]

You could try connecting the keyboard to another USB port.
It may be that the current port is not powered until later in the boot sequence.
Just a shot in the dark.

[lsemmens]

Good suggestion, however, already tried that.

[DisturbedDragon]

I still say run memtest or yank a stick of ram out a time to see if this resolves it.

[lsemmens]

I just found a 4 port USB hub in the circuit that I'd forgotten about. The only thing plugged into it was the keyboard..........................
Looks like it has solved the problem. We shall see!