On board laptop keyboard not getting recognised.

[f33dm3bits]

This is what my device manager shows.

Now i'm confused as to what is going on lol

As @Condobloke already state, this is a PS/2 port.

PS/2 port - Wikipedia

en.wikipedia.org

I found some answers for you and for myself and I guess we both learned something new out of this.

Why does my laptop keyboard show up as Standard PS/2 Keyboard or HID Keyboard Device in Windows Device Manager, even though I don't have either?

Why does the Windows device manager show my laptop keyboard as a Standard PS/2 Keyboard on one laptop and as a HID Keyboard Device on the other, even though I already know that it is only connected...

superuser.com

But short it's this.

No, it’s absolutely correct. The information there is not talking about the physical connection, but the protocol being used to communicate with the device.
PS/2 and USB are protocols that mandate external connectors. That doesn't mean that they cannot use whatever connector they want inside a computer.

In your case you simply have one device that talks PS/2 at your keyboard, and another that uses USB instead. There is nothing more magical than that.

So the information shown by your device manager is correct, it shows that your laptop keyboard uses the PS/2 protocol.

 

[Exernite]

one of the problems is unfortunate, you purchased a make of machine we haven't heard of and so have no data on or experience with but we w ill keep trying, as its based on a dell registered product, may make things easier.

More bad news, the dell registered product is an external keyboard plugged in via USB... I think this means Linux isn't even acknowledging my my on board keyboards existence...

 

[Fanboi]

Check if you can find the device with lsusb (failing that, lspci -- depends on how the manufacturer configured the interface, usually internal keyboards show up as USB devices). To get a better overview, run sleep first so you would enter sleep 5; lsusb and pull the USB keyboard out and plug it back in after the output. See if any input devices appear. I had a keyboard issue when I bought a laptop on the verge of an upgrade. Luckily that fixed it so it wasn't a big pain. (Of course one of my buttons gave out so I'm now using a USB keyboard anyway -- define irony)

Notes: Windows (still?) treats generic keyboards as "PS/2", even internal/USB ones. So I wouldn't go by what Windows shows.

 

[Exernite]

Check if you can find the device with lsusb (failing that, lspci -- depends on how the manufacturer configured the interface, usually internal keyboards show up as USB devices). To get a better overview, run sleep first so you would enter sleep 5; lsusb and pull the USB keyboard out and plug it back in after the output. See if any input devices appear. I had a keyboard issue when I bought a laptop on the verge of an upgrade. Luckily that fixed it so it wasn't a big pain. (Of course one of my buttons gave out so I'm now using a USB keyboard anyway -- define irony)

Notes: Windows (still?) treats generic keyboards as "PS/2", even internal/USB ones. So I wouldn't go by what Windows shows.

As far as I can see, no USB devices...

P.S Sorry to hear about your keyboard :|

 

[dos2unix]

Every line that says "root hub" is a USB device.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 2b7e:c858 Kingcome FHD WebCam
Bus 001 Device 003: ID 13d3:3585 IMC Networks Wireless_Device
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 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 003: ID 0bda:0316 Realtek Semiconductor Corp. Card Reader
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 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 002: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub

I see four USB 3.0 ports, and four USB 2.0 ports.

 

[Fanboi]

As far as I can see, no USB devices...

P.S Sorry to hear about your keyboard :|

Seems the device isn't listed, so the only option I can think of immediately is maybe upgrade to a later kernel and just double check you have installed all firmware packages. Maybe try a couple of other distros live like Fedora and Manjaro because Mint and Ubuntu are from the Debian family, so it's not the best litmus test.

 

[f33dm3bits]

Seems the device isn't listed, so the only option I can think of immediately is maybe upgrade to a later kernel and just double check you have installed all firmware packages.

You can also try running the mainline kernel on Linux Mint.

GitHub - bkw777/mainline: Install mainline kernel packages from kernel.ubuntu.com

Install mainline kernel packages from kernel.ubuntu.com - bkw777/mainline

github.com

Mainline – Another Tool to Install Latest Kernel in Ubuntu / Linux Mint | UbuntuHandbook

 

[Exernite]

Yeah it doesn't seem to be working... I'll have a look at some other distro's at some point. It's a shame because I really like the look of Ubuntu... :/ Thanks for your time guys.

 

[wizardfromoz]

@Exernite - I can see from your xinput output (and thanks for that) that you are using Xorg, not Wayland, at startup.

Have you tried to see if the keyboard works on Wayland? You get it by choosing Ubuntu from the cog at login

If no joy there - I have a worry for you that by trying a different distro, you may just encounter the same faults, and that can discourage you.

If you do try another distro, I would suggest a Linux Mint first, and if the problems are repeated, I may have a workaround that you could try.

HTH

Wizard

 

[Exernite]

Unfortunately setting it to wayland didn't fix it. I have already tried mint before I tried Ubuntu, same issue there. I guess my laptop just isn't compatible with Linux. Or maybe it's something that can be fixed but isn't a very specific issue, meaning it's hard to find the fix in question. Thank you anyways