Skip to contentSkip to conversation

keyboard dead after resuming from S3

PM Karol Kozimor 2 participants 5 messages Sep 29, 2003 – Oct 7, 2003

lore
Share & tools
lore
#0 lore raw

Hi,
As far as I remember, my keyboard (a standard laptop AT keyboard) never worked after resuming from S3. In older kernels, I was able to get away with this by reloading atkbd.ko. However, for newer ones (2.6.0-test5-mm4, specifically), I can't do that, as the following appears:

atkbd: Unknown symbol dump_i8042_history

A similar warning is issued at depmod stage.

How are your plans to add suspend / resume support to the serio core (I thought I saw some Synaptics patches a while ago)?

Best regards,

Signature · 2 lines
Karol 'sziwan' Kozimor
[email protected]
#1 lore raw
Quoted 8 lines · Karol Kozimor

As far as I remember, my keyboard (a standard laptop AT keyboard) never worked after resuming from S3. In older kernels, I was able to get away with this by reloading atkbd.ko. However, for newer ones (2.6.0-test5-mm4, specifically), I can't do that, as the following appears:

atkbd: Unknown symbol dump_i8042_history

A similar warning is issued at depmod stage.

You probably have the atkbd module from a different kernel version. Rebuild your atkbd module.

Quoted 2 lines

How are your plans to add suspend / resume support to the serio core (I thought I saw some Synaptics patches a while ago)?

Yes, I'm working on that.

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#2 lore raw

Thus wrote Vojtech Pavlik:

Quoted 8 lines
Quoted 6 lines

with this by reloading atkbd.ko. However, for newer ones (2.6.0-test5-mm4, specifically), I can't do that, as the following appears:

atkbd: Unknown symbol dump_i8042_history

A similar warning is issued at depmod stage.

You probably have the atkbd module from a different kernel version. Rebuild your atkbd module.

Definitely not, and I've just done a make mrproper to ensure that. Will try with a different version, though.
Best regards,

Signature · 2 lines
Karol 'sziwan' Kozimor
[email protected]
#3 lore raw
Quoted 6 lines · Karol Kozimor

Thus wrote Vojtech Pavlik:

Quoted 5 lines
Quoted 5 lines

with this by reloading atkbd.ko. However, for newer ones (2.6.0-test5-mm4, specifically), I can't do that, as the following appears:

atkbd: Unknown symbol dump_i8042_history

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

A similar warning is issued at depmod stage.

You probably have the atkbd module from a different kernel version. Rebuild your atkbd module.

Definitely not, and I've just done a make mrproper to ensure that. Will try with a different version, though.
Best regards,

Ok, then it's some patch that's in -mm4 and isn't in -test6 and -bk* trees.

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#4 lore raw

Thus wrote Vojtech Pavlik:

Quoted 7 lines
Quoted 6 lines
Quoted 3 lines
Quoted 1 line

A similar warning is issued at depmod stage.

You probably have the atkbd module from a different kernel version. Rebuild your atkbd module.

Definitely not, and I've just done a make mrproper to ensure that. Will try with a different version, though.
Best regards,

Ok, then it's some patch that's in -mm4 and isn't in -test6 and -bk* trees.

Indeed. 2.6.0-test6-vanilla is OK with atkbd.ko and rmmod atkbd; echo 3 > /proc/acpi/sleep; modprobe atkbd works as expected.
Best regards,

Signature · 2 lines
Karol 'sziwan' Kozimor
[email protected]