Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Apr 2024 16:29:29 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 278668] atkbdc: No keyboard on HP Elitebook 845 G10
Message-ID:  <bug-278668-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278668

            Bug ID: 278668
           Summary: atkbdc: No keyboard on HP Elitebook 845 G10
           Product: Base System
           Version: 15.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: klimanov625@outlook.com

Created attachment 250308
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D250308&action=
=3Dedit
FreeBSD 15-CURRENT dmesg

Hi All,

I'm trying to get FreeBSD running on my personal laptop, but keyboard does =
not
seem to be working (but is recognized). The same behavior is exhibited on
14-RELEASE (memstick) and 15-CURRENT (memstick snapshot from 2024-04-25).

I am not aware of any quirks related to my specific model, neither in Linux,
nor in FreeBSD, nor am I aware of how to try them out and which.

The keyboard in question is attached internally via an i8042-compatible
controller (likely emulated in acpi?), so PS/2. Nothing else, that I'm awar=
e of
is connected in such manner, and only keyboard is affected.

Relevant dmesg lines are:

atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
ioapic0: Changing polarity for pin 1 to high
atkbd0: <AT Keyboard> irq 1 on atkbdc0
atkbd: the current kbd controller command byte 0067
atkbd: keyboard ID 0x41ab (2)
kbdc: RESET_KBD return code:00fa
kbdc: RESET_KBD status:00aa
kbd0 at atkbd0
kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000
ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 14 vector 50
atkbd0: [GIANT-LOCKED]
psm0: unable to allocate IRQ

But atkbd0 grabs IRQ1(?) (vmstat -i):

interrupt                          total       rate
irq1: atkbd0                           2          0
irq9: acpi0                          523          5
irq10: ig4iic0                        42          0
cpu0:timer                          2366         21
cpu1:timer                           998          9
cpu2:timer                          1606         15
cpu3:timer                          1044          9
cpu4:timer                          2250         20
cpu5:timer                          1525         14
cpu6:timer                          1232         11
cpu7:timer                          1102         10
cpu8:timer                          1026          9
cpu9:timer                          1494         14
cpu10:timer                         1056         10
cpu11:timer                          868          8
cpu12:timer                         1483         13
cpu13:timer                         1265         11
cpu14:timer                          932          8
cpu15:timer                         1595         14
irq59: nvme0:admin                    24          0
irq65: nvme0:io5                      74          1
irq66: nvme0:io6                      75          1
irq78: hdac0                           5          0
irq79: xhci0                       14504        132
irq80: xhci1                          46          0
irq81: hdac1                           9          0
irq83: xhci3                        2880         26
Total                              40026        364

Also, full dmesg (also attached as file):
https://hastebin.com/share/avukayobob.yaml
pciconf -lv: https://hastebin.com/share/izehegiyen.java
dmesg on linux: https://hastebin.com/share/aliroqiwil.yaml
and, hw-probe (from linux): https://linux-hardware.org/?probe=3D8fa3424cce

I am willing to probe more and will try patches, but am out of ideas

And I'm not entirely sure on policy with external file hosts, so, if desira=
ble,
will upload here, just don't want to unnecessarily bump my own report

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-278668-227>