Keyboard not working

farzammag · 2023-08-06 14:09:24

Laptop: Legion Y540-17IRH-PG0 Laptop (Lenovo) - Type 81T3
Kernel: 6.4.8

Last week, I neglected to update my laptop for about a week, sticking with kernel version 6.4.4. Upon booting and running my system update (comprising various packages, with noted issues on other Lenovo laptops after the new kernel), I restarted the laptop as usual using the keyboard.

Once in sddm, keyboard input was unresponsive. I suspected an Xorg problem, but testing outside of Xorg yielded the same result. It's worth noting the keyboard worked in GRUB. I also attempted the LTS kernel without success. Subsequently, I reverted to a snapshot pre-update (kernel 6.4.4), followed by another update attempt, to no avail.

Testing in Live USB, BIOS, and a Windows ISO still showed keyboard malfunction. Notably, brightness control and keyboard backlight adjustments remained functional, perplexingly. This contradictory behavior puzzled me, as it suggests both hardware failure and partial keyboard functionality.

I contemplated the possibility of the update causing damage to the keyboard, though this is improbable, given the laptop was untouched. It's pertinent to mention that I had previously replaced the entire keyboard due to water damage two years ago.

Ultimately, I am seeking assistance, as it seems a keyboard replacement is in order. I'm sharing this experience for others encountering similar issues. Thank you.

Last edited by farzammag (2023-08-07 09:10:14)

twelveeighty · 2023-08-07 01:28:30

farzammag wrote:

So anyways, not actually asking for help

This forum is not a blog, please restate your post as a question and provide factual information, not feelings such as 'crazy', 'hope', 'busy', 'confused', etc.

Last edited by twelveeighty (2023-08-07 01:29:26)

seth · 2023-08-07 06:11:01

If it's not the hardware (where I'd expect the alternative functions of the brightness etc. to work), I'd bet on a firmware (UEFI) update - or maybe some stuck Fn key/lock

But yes, the OP currently is hardly more than "ode to my lost keyboard" and of little use to anyone.

farzammag · 2023-08-07 09:07:53

twelveeighty wrote:

farzammag wrote:
So anyways, not actually asking for help
This forum is not a blog, please restate your post as a question and provide factual information, not feelings such as 'crazy', 'hope', 'busy', 'confused', etc.

Hello,

sorry for my bad post, should i edit it here or post a new one?
what kind of information would be useful? im not really familiar with this kind of issue, any blogs i checked usually the problem was fixed with a downgrade.

farzammag · 2023-08-07 09:09:09

seth wrote:

If it's not the hardware (where I'd expect the alternative functions of the brightness etc. to work), I'd bet on a firmware (UEFI) update - or maybe some stuck Fn key/lock
But yes, the OP currently is hardly more than "ode to my lost keyboard" and of little use to anyone.

Hi,

i will try to drain the battery today and do the trick with holding the power button for 30 seconds (solution of lenovo)

id be extremely grateful if you could tell me what else i could do to fix this, its a horror to do all my work with a cheap external keyboard...

seth · 2023-08-07 12:37:11

usually the problem was fixed with a downgrade

Since the problem isn't limited tothe OS, that's not gonna help…

Did you recently update the firmware?
Since at least some Fn keys seem still to work, check the BIOS for Fn-key related settigns and the manual on what the Fn lock (Fn+Esc?) is and whether it does anything.

farzammag · 2023-08-07 12:49:56

seth wrote:

usually the problem was fixed with a downgrade
Since the problem isn't limited tothe OS, that's not gonna help…
Did you recently update the firmware?
Since at least some Fn keys seem still to work, check the BIOS for Fn-key related settigns and the manual on what the Fn lock (Fn+Esc?) is and whether it does anything.

yes i have noticed, i downgraded as soon as i realized the problem happened, but didnt help, i just had a snapshot before update so it wasnt that complicated to downgrade.

Thank you for the tip, i actually remember a setting called fool proof fn key or similar, i will try to play with that and drain the battery, worst case scenario i have a second nvme and i try to install a windows and update my bios, as it was not possible in linux and last time i had windows was at least 5 years ago.

ill let you know more.

again i didnt know what exactly to share from my system because the problem wasnt OS limited, i looked into journalctl, and xorg log, i couldnt think of any other log file that would give me any useful information.

farzammag · 2023-08-07 17:36:43

So I disconnected the battery: had to open the latop, drained the battery and booted, then it worked in grub, and in the sddm and kde plasma desktop using kernel .8, it worked, in order to make sure i rebooted...,

here is usb devices:
~ ❯❯❯ sleep 3 && lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
Bus 001 Device 011: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

here is journalctl -b after the failed boot:

https://drive.google.com/file/d/1yDE42S … drive_link

and then no more keys were working again beside fn - space (backlight) and fn f5 and f6 for background light.

Aug 06 19:46:02 thunderkeg kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20230331/dswload2-326)
Aug 06 19:46:02 thunderkeg kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230331/psobject-220)

this kind of stands out.

Last edited by farzammag (2023-08-07 17:58:56)

farzammag · 2023-08-07 18:36:28

So i noticed a random thing now: when i hold power button and go directly into bios, laptop keyboard works in bios, but when i click bios settings in grub, in doesnt, after around 20 times of rebooting and holding power button for 30 seconds, suddenly it works now with kernel .8, so now here is the journal of a working boot and a lsub:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
**Bus 001 Device 005: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910)**
Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
Bus 001 Device 007: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

So its not even detected!, I mean now it is

journal: https://drive.google.com/file/d/1ob439S … drive_link

farzammag · 2023-08-07 18:42:00

i noticed the following pattern only exists in the successfull boot: ITE Device
~ ❯❯❯ cat journalctl-b2 | grep "ITE Device"
Aug 07 20:31:47 thunderkeg kernel: usb 1-9: Product: ITE Device(8910)
Aug 07 20:31:52 thunderkeg kernel: input: ITE Tech. Inc. ITE Device(8910) Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:048D:C100.0002/input/input18
Aug 07 20:31:52 thunderkeg kernel: hid-generic 0003:048D:C100.0002: input,hiddev96,hidraw1: USB HID v1.10 Keyboard [ITE Tech. Inc. ITE Device(8910)] on usb-0000:00:14.0-9/input0
Aug 07 20:31:52 thunderkeg systemd-logind[660]: Watching system buttons on /dev/input/event14 (ITE Tech. Inc. ITE Device(8910) Keyboard)

So the kernel just doesnt detect it in 29 of 30 boots? or am i just shooting a random thing here?

but the question is, why does the state even continue even tho i reboot into uefi.

Last edited by farzammag (2023-08-07 18:43:56)

seth · 2023-08-07 19:16:15

when i hold power button and go directly into bios, laptop keyboard works in bios, but when i click bios settings in grub, in doesnt

Check the BIOS/UEFI for any setting related to usb/xhci handoff.

farzammag · 2023-08-07 19:20:29

seth wrote:

when i hold power button and go directly into bios, laptop keyboard works in bios, but when i click bios settings in grub, in doesnt
Check the BIOS/UEFI for any setting related to usb/xhci handoff.

before i do so is there anything useful you might need from this boot? or i can look into? because if i reboot chances of me getting a good boot again are very very very small.

farzammag · 2023-08-07 19:27:09

seth wrote:

when i hold power button and go directly into bios, laptop keyboard works in bios, but when i click bios settings in grub, in doesnt
Check the BIOS/UEFI for any setting related to usb/xhci handoff.

Nah it is a pretty simple supermicro laptop motherboard, nothing like that, the only usb related setting is always on USB, which was disabled, should i enable it? i dont see the relevance

seth · 2023-08-07 19:28:14

The journal is gonna remain and we've one of each boot already.

Aug 07 19:46:02 thunderkeg kernel: usb 1-9: new full-speed USB device number 5 using xhci_hcd
Aug 07 19:46:02 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 19:46:03 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 19:46:03 thunderkeg kernel: usb 1-9: new full-speed USB device number 6 using xhci_hcd
Aug 07 19:46:03 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 19:46:03 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 19:46:07 thunderkeg kernel: usb 1-9: new full-speed USB device number 8 using xhci_hcd
Aug 07 19:46:07 thunderkeg kernel: usb 1-9: Device not responding to setup address.
Aug 07 19:46:07 thunderkeg kernel: usb 1-9: Device not responding to setup address.
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: device not accepting address 8, error -71
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: new full-speed USB device number 9 using xhci_hcd
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: Device not responding to setup address.
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: Device not responding to setup address.
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: device not accepting address 9, error -71

This is (most likely) your failing keyboard.

always on USB, which was disabled, should i enable it?

You've not much to lose and some usb device doesn't respond.

Last edited by seth (2023-08-07 19:30:36)

farzammag · 2023-08-07 19:37:54

seth wrote:

The journal is gonna remain and we've one of each boot already.
Aug 07 19:46:02 thunderkeg kernel: usb 1-9: new full-speed USB device number 5 using xhci_hcd
Aug 07 19:46:02 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 19:46:03 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 19:46:03 thunderkeg kernel: usb 1-9: new full-speed USB device number 6 using xhci_hcd
Aug 07 19:46:03 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 19:46:03 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 19:46:07 thunderkeg kernel: usb 1-9: new full-speed USB device number 8 using xhci_hcd
Aug 07 19:46:07 thunderkeg kernel: usb 1-9: Device not responding to setup address.
Aug 07 19:46:07 thunderkeg kernel: usb 1-9: Device not responding to setup address.
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: device not accepting address 8, error -71
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: new full-speed USB device number 9 using xhci_hcd
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: Device not responding to setup address.
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: Device not responding to setup address.
Aug 07 19:46:08 thunderkeg kernel: usb 1-9: device not accepting address 9, error -71
This is (most likely) your failing keyboard.
So just to mention, while booting (successfully) i had a cheap chinese keyboard and a mouse and keyboard also attached, maybe thats where its comming from
Also i dont think keyboard is failing is true because when i shutdown fully, and imidiately launch into bios, things are fine, if we could actually have a proof that its the keyboard, thats also fine.
always on USB, which was disabled, should i enable it?
You've not much to lose and some usb device doesn't respond.

seth · 2023-08-07 19:41:15

Boot the system w/o any external devices attached, reboot (attacha usb keyboard much later if you have to) and post the journal.
There's an AT2 keyboard via i8042 which is a far more common bus for laptop keyboards.

farzammag · 2023-08-07 19:48:00

seth wrote:

Boot the system w/o any external devices attached, reboot (attacha usb keyboard much later if you have to) and post the journal.
There's an AT2 keyboard via i8042 which is a far more common bus for laptop keyboards.

So i loaded the default BIOS settings
laptop keyboard worked in bios:
https://drive.google.com/file/d/1XA6qvU … sp=sharing

I dont find the laptop keyboard under lsusb.

Sorry, i connected the whole hub, that must be a bit confusing, ill redo this.

Last edited by farzammag (2023-08-07 19:50:44)

farzammag · 2023-08-07 19:57:29

https://drive.google.com/file/d/14UYqe1 … drive_link
Updated*

farzammag · 2023-08-07 20:00:21

https://drive.google.com/file/d/1HMMufw … drive_link

every usb device connected that i usually use:

farzammag · 2023-08-07 20:02:29

Two things:

so when i totally shut the pc down by holding down the power button, keyboard works until i boot.

another question: would you think it would be worth it to try to update the bios or am i just shooting something in the darkness?

seth · 2023-08-07 20:05:13

Aug 07 21:54:15 thunderkeg kernel: usb 1-9: new full-speed USB device number 3 using xhci_hcd
Aug 07 21:54:15 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 21:54:15 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71

Troublesome USB device that showed up as

Aug 07 20:31:47 thunderkeg kernel: usb 1-9: new full-speed USB device number 5 using xhci_hcd
Aug 07 20:31:47 thunderkeg kernel: usb 1-9: New USB device found, idVendor=048d, idProduct=c100, bcdDevice= 0.44
Aug 07 20:31:47 thunderkeg kernel: usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 07 20:31:47 thunderkeg kernel: usb 1-9: Product: ITE Device(8910)
Aug 07 20:31:47 thunderkeg kernel: usb 1-9: Manufacturer: ITE Tech. Inc.

is still there, google says it's "048d:c100=HID Device"

Other than that only the

Aug 07 21:54:15 thunderkeg kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Aug 07 21:54:15 thunderkeg kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Aug 07 21:54:15 thunderkeg kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Aug 07 21:54:15 thunderkeg kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3

Was the internal keyboard working in the #18 journal?

You can btw. make this way simpler for everyone by using 0x0.st or ix.io, 1st link below.

farzammag · 2023-08-07 20:11:03

seth wrote:

Aug 07 21:54:15 thunderkeg kernel: usb 1-9: new full-speed USB device number 3 using xhci_hcd
Aug 07 21:54:15 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71
Aug 07 21:54:15 thunderkeg kernel: usb 1-9: device descriptor read/64, error -71

Troublesome USB device that showed up as

Aug 07 20:31:47 thunderkeg kernel: usb 1-9: new full-speed USB device number 5 using xhci_hcd
Aug 07 20:31:47 thunderkeg kernel: usb 1-9: New USB device found, idVendor=048d, idProduct=c100, bcdDevice= 0.44
Aug 07 20:31:47 thunderkeg kernel: usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 07 20:31:47 thunderkeg kernel: usb 1-9: Product: ITE Device(8910)
Aug 07 20:31:47 thunderkeg kernel: usb 1-9: Manufacturer: ITE Tech. Inc.

is still there, google says it's "048d:c100=HID Device"

Other than that only the

Aug 07 21:54:15 thunderkeg kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Aug 07 21:54:15 thunderkeg kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Aug 07 21:54:15 thunderkeg kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Aug 07 21:54:15 thunderkeg kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3

Was the internal keyboard working in the #18 journal?

You can btw. make this way simpler for everyone by using 0x0.st or ix.io, 1st link below.

Sorry, i do not understand what i should catch from the info you summarized, but if im understanding this correctly this is actually caused by bios or the hardware is gone bad

I also sadly dont get what you mean by #18 Journal

I will try to make use of the guide you provided thanks

seth · 2023-08-07 20:18:39

You posted a journal in … post #18, did the internal keyboard work during that boot (21:54:15 your time)?
We're trying to identify the non-working keyboard and whether it's the ITE USB device or the i8042 keyboard (which could also just be the power button)

Btw

would you think it would be worth it to try to update the bios

If there's a BIOS update, it's probably a good idea to test that - not sure whether you ever answered whether you maybe did update the BIOS before this all started.

farzammag · 2023-08-07 20:25:30

seth wrote:

You posted a journal in … post #18, did the internal keyboard work during that boot (21:54:15 your time)?
We're trying to identify the non-working keyboard and whether it's the ITE USB device or the i8042 keyboard (which could also just be the power button)
Btw
would you think it would be worth it to try to update the bios
If there's a BIOS update, it's probably a good idea to test that - not sure whether you ever answered whether you maybe did update the BIOS before this all started.

No, keyboard didnt work on Post 18,

No i didnt do a BIOS update, because until 20 minutes before it really looked like a hardware failure, so now ill be trying to make a windows image and update bios.

So anyways, thank you for your help, i will update my BIOS and let you know

I really appreciate you man. thank you

Last edited by farzammag (2023-08-07 20:30:11)

farzammag · 2023-08-07 21:40:33

seth wrote:

You posted a journal in … post #18, did the internal keyboard work during that boot (21:54:15 your time)?
We're trying to identify the non-working keyboard and whether it's the ITE USB device or the i8042 keyboard (which could also just be the power button)
Btw
would you think it would be worth it to try to update the bios
If there's a BIOS update, it's probably a good idea to test that - not sure whether you ever answered whether you maybe did update the BIOS before this all started.

There was no BIOS update, i just checked, its already on the newest version.

Arch Linux

#1 2023-08-06 14:09:24

Keyboard not working

#2 2023-08-07 01:28:30

Re: Keyboard not working

#3 2023-08-07 06:11:01

Re: Keyboard not working

#4 2023-08-07 09:07:53

Re: Keyboard not working

#5 2023-08-07 09:09:09

Re: Keyboard not working

#6 2023-08-07 12:37:11

Re: Keyboard not working

#7 2023-08-07 12:49:56

Re: Keyboard not working

#8 2023-08-07 17:36:43

Re: Keyboard not working

#9 2023-08-07 18:36:28

Re: Keyboard not working

#10 2023-08-07 18:42:00

Re: Keyboard not working

#11 2023-08-07 19:16:15

Re: Keyboard not working

#12 2023-08-07 19:20:29

Re: Keyboard not working

#13 2023-08-07 19:27:09

Re: Keyboard not working

#14 2023-08-07 19:28:14

Re: Keyboard not working

#15 2023-08-07 19:37:54

Re: Keyboard not working

#16 2023-08-07 19:41:15

Re: Keyboard not working

#17 2023-08-07 19:48:00

Re: Keyboard not working

#18 2023-08-07 19:57:29

Re: Keyboard not working

#19 2023-08-07 20:00:21

Re: Keyboard not working

#20 2023-08-07 20:02:29

Re: Keyboard not working

#21 2023-08-07 20:05:13

Re: Keyboard not working

#22 2023-08-07 20:11:03

Re: Keyboard not working

#23 2023-08-07 20:18:39

Re: Keyboard not working

#24 2023-08-07 20:25:30

Re: Keyboard not working

#25 2023-08-07 21:40:33

Re: Keyboard not working

Board footer