> Date: Mon, 22 May 2017 11:10:43 +0200
> From: =?UTF-8?Q?Sol=C3=A8ne_Rapenne?= <[email protected]>
>
> Je 2017-05-17 21:12, Stuart Henderson skribis:
> > On 2017/05/17 21:04, Solene Rapenne wrote:
> >> Once bsd.rd boot, the keyboard isn't usable. I can't type on it,
> >> nothing happens. I can use an usb keyboard. No network interface
> >> is found within the installer nor ifconfig outputs finds a network
> >> interface, so the wifi isn't even found. The computer is a laptop Asus
> >> L200HA-FD0093T.
> >
> > This is your wireless adapter:
> >
> >> vendor "Atheros", unknown product 0x0042 (class network subclass
> >> miscellaneous, rev 0x31) at pci1 dev 0 function 0 not configured
> >
> > Looks like it is an ath10k device (probably QCA9337), unsupported.
>
> I understand that the wireless isn't supported, I can still use an usb
> wifi.
>
> Any idea for the not working keyboard ?
Judging from the dmesg, this machine has an i2c keyboard:
dwiic1 at acpi0: I2C1 addr 0x91632000/0x1000 irq 32
iic1 at dwiic1
ihidev0 at iic1 addr 0x68 irq 0, vendor 0xb05 product 0x8585, PDEC3393
ihidev0: 9 report ids
ikbd0 at ihidev0 reportid 1: 8 variable keys, 6 key codes
wskbd0 at ikbd0 mux 1
hid at ihidev0 reportid 3 not configured
hid at ihidev0 reportid 6 not configured
hid at ihidev0 reportid 9 not configured
The "irq 0" is supicious here. That probably means the keyboard
interrupt doesn't work properly. If you boot with the -a option (type
boot -a at the bootloader prompt), does the keyboard work when the
kernel asks for the root disk?
Looking at the ACPI DSDT, it seems that the interrupt should be
provided by a gpio:
GpioInt (Level, ActiveLow, Shared, PullNone, 0x0000,
"\\_SB.GPO0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x005D
}
The problem here is probably that the dwiic1 anc chvgpio0 devices
appear out of order. I think I had a raw diff for that at some point.
Let's see if I can dust that one off...
