01010003 Keyboard not detected issue

owlion · 09-23-2020, 06:44 AM

Hi, I updated my system last night [kubuntu 20.04] and while everything was fine when booting it this morning, suddenly the keyboard stopped working. I restarted and got an error '01010003 keyboard not detected' on the boot screen, and now the keyboard doesn't work at all. I was wondering if there was a way to fix this, or if there's a way to reinstall the os without needing a keyboard during the boot.

Thanks for any help, sorry if this is the wrong place!

dc.901 · 09-23-2020, 07:43 AM

If you boot with the same USB media you used to install Kubuntu, does the installer detect the keyboard?

owlion · 09-23-2020, 07:54 AM

Hi, unfortunately I don't have it set to automatically boot from the usb and, as no key inputs are working, I can't open any menus during the boot.

dc.901 · 09-23-2020, 08:36 AM

Quote:

Originally Posted by owlion

no key inputs are working, I can't open any menus during the boot.

Have you tried unplugging and re-plugin the keyboard? Perhaps different USB port, or try keyboard on another computer?

owlion · 09-23-2020, 08:46 AM

I'm using a laptop, so unfortunately I'm not able to unplug it. It's a Lenovo V155 if that's any help? The touchpad is fine and everything else seems functional (I'm using a virtual keyboard on it).

michaelk · 09-23-2020, 09:07 AM

A quick search found some information but nothing conclusive. I believe the 01010003 is a BIOS boot error and not associated with the operating system which means a reinstall will not help. It could be due to a stuck key or a hardware fault. I assume you did not spill any liquid recently on the laptop? Have you tried a USB keyboard?

owlion · 09-23-2020, 09:41 AM

Thanks very much! I haven't damaged the keyboard in any way, as far as I'm aware. I don't have a usb keyboard, but I've arranged to take it for repairs tomorrow, so I'll update with what happens.

EDIT: It turns out there was something stuck under one of the keys, which made the laptop no longer recognise the keyboard, but it's fixed now - thanks for the help!