Skip to contentSkip to conversation

"i8042.c: No controller found" -> no keyboard when I type in BIOS

DISCUSSION Tomasz Chmielewski 1 participant 3 messages May 14, 2009 KVM

lore
Share & tools
lore
#0 lore raw

Sometimes, when I type any keys in BIOS, my Linux guests boot without keyboard - I'm not able to type in VNC console, guest's dmesg says:

i8042.c: No controller found.

Rebooting the guest doesn't fix the problem; only stopping/starting the guest helps (i.e. new kvm process is started).

Which is a bit strange - usually, the keyboard is there when I boot:

serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0

The keyboard is not present after I reboot the guest and usually type before Linux is started. It does not happen always.

Observed with kvm-83, kvm-84, kvm-85 on multiple KVM hosts (different hardware).

Anyone else seeing this? If you're not sure, do something like:

grep i8042 /var/log/kern*

(or grep "i8042.c: No controller found" /var/log/kern*)

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#1 lore raw
Quoted 5 lines · Tomasz Chmielewski

The keyboard is not present after I reboot the guest and usually type before Linux is started. It does not happen always.

Observed with kvm-83, kvm-84, kvm-85 on multiple KVM hosts (different hardware).

Anyone else seeing this? If you're not sure, do something like:

Looks I'm not alone here with this issue:

http://osdir.com/ml/fedora-virt/2009-04/msg00066.html

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org
#2 lore raw
Quoted 11 lines · Tomasz Chmielewski
Quoted 5 lines · Tomasz Chmielewski

The keyboard is not present after I reboot the guest and usually type before Linux is started. It does not happen always.

Observed with kvm-83, kvm-84, kvm-85 on multiple KVM hosts (different hardware).

Anyone else seeing this? If you're not sure, do something like:

Looks I'm not alone here with this issue:

http://osdir.com/ml/fedora-virt/2009-04/msg00066.html

Seems to be qemu-related problem (I found more confirmations in the internet); reposting question to qemu-devel list.

Signature · 2 lines
Tomasz Chmielewski
http://wpkg.org