Summary: | atkbdc: No keyboard on HP Elitebook 845 G10 | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Anton Klimanov <klimanov625> | ||||
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
Status: | New --- | ||||||
Severity: | Affects Only Me | CC: | klimanov625, michael.osipov | ||||
Priority: | --- | ||||||
Version: | 15.0-CURRENT | ||||||
Hardware: | amd64 | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Anton Klimanov
2024-04-30 16:29:29 UTC
Just tried 13.4-RELEASE and keyboard kind of works there, but each keystroke is buffered and delayed. They arrive at regular intervals of 1 second each. Still far from usable, but weird nonetheless. I don't see any significant changes in atkbdc between 13.4-RELEASE and 14.0-RELEASE that would produce such behavior... (In reply to Anton Klimanov from comment #1) Where did you obtain 13.4-RELEASE? (In reply to Michael Osipov from comment #2) Oh, sorry, my bad, 13.3-RELEASE is what I meant (latest of 13 major release). Must have mixed something up in my head. Okay, new development. Apparently no interrupts arrive per default, but if caps lock is toggled on, exactly one arrives. Should there be any buffered keys, they will arrive with consecutive caps lock toggles. Seems like poking the keyboard makes it do stuff. I really feel like it's awaiting some sort of acknowledgement from the interrupt handler, which happens in Linux and NetBSD, but not FreeBSD Did some poking in kernel and yes, no interrupts on IRQ1 are received. Curiously, there are two interrupts somewhere after driver initialization before radio silence. Both contain "0x1000000" (NOKEY?). Concerning my previous observation about stuff happening on caps lock off to on, controller seems to send 2 bytes per key, which also seems normal. There definitely is something fishy about keyboard initialization in atkbd, but I just can't quite figure out what |