I did a fresh install of Suse 9.1 on my Dell Latitude D600. Everything was great until I turned it off and then turned it back on.

I have no keyboard when the laptop boots back up. It boots into the graphical login screen, and I actually have a working mouse, but the keyboard doesnt respond. I have to reboot again while the computer is on to get it to work.

Ive been looking through google all day, and scanning the SUSE boards. People seem to have the same problem, but no one posts a fix. One guy told me to just reboot till it works, and that seems like a lame fix to me. Another person said just use a USB keyboard...Again, a lame fix as I actually want to use the laptop keyboard.

Does anyone actually have a solution to this problem?

- Mike (mike.waldner _a_t_ gmail.com

I also cant find an entry in the bios for "USB Legacy Support"...I read somewhere if you disable that, it should work. But I can find that option in my bios.

-m

So from this, presumably the keyboard works after one or more reboots ?

What happens if you press F2 at bootup (to enable verbose mode), or boot into rescue mode, leaving you with just a login prompt, no X.

Cheers,

mj

i have this same problem with my asus L3 laptop,except my keyboard wasn't coming on at all... what i did was put on a 2.4 kernel from SUSE 9.0 and the keyboard worked but then LAN and sound was broken so i guess the only solution is to compile a 2.4 kernel for urself which is beyond me right now

I've read reports when an attached USB device blocked the keyboard somehow. After detaching the USB device, the keyboard was recognised normally.

But there was no other solution than detaching...

False ACPI routing was one idea, but no solution provided. Maybe it works with passing pci=noacpi to the kernel.

Well, to update my problem. When I boot into SUSE, I type console when it first boots up. This takes me into Init 3 I beleive. During the bootup, the keyboard doesnt work. But when I finally boot to a login prompt, the keyboard starts to work after about 5 seconds or so?

Heres some dmesg output of some errors Im getting related to the keyboard...Anyone know what they might mean?

mice: PS/2 mouse device common for all mice
input: PC Speaker
serio: i8042 AUX port at 0x60,0x64 irq 12
input: PS/2 Generic Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
atkbd.c: Unknown key pressed (translated set 0, code 0x3a on isa0060/serio0).
atkbd.c: Use 'setkeycodes 3a <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 0, code 0x3a on isa0060/serio0).
atkbd.c: Use 'setkeycodes 3a <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 0, code 0x3a on isa0060/serio0).
atkbd.c: Use 'setkeycodes 3a <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 0, code 0x3a on isa0060/serio0).
atkbd.c: Use 'setkeycodes 3a <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 0, code 0x3a on isa0060/serio0).
atkbd.c: Use 'setkeycodes 3a <keycode>' to make it known.
atkbd.c: Unknown key pressed (translated set 0, code 0x3c on isa0060/serio0).
atkbd.c: Use 'setkeycodes 3c <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 0, code 0x3a on isa0060/serio0).
atkbd.c: Use 'setkeycodes 3a <keycode>' to make it known.
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2

Could that atkbd.c file be screwed up?

- M

ur lucky that error has to do with keyboard layout , that means its seeing it..but for me its not even seeing the keyboard