Ubuntu
linux-source-2.6.17 package

IBM Thinkpad R40e special keys does not work with ACPI

Bug #68734 reported by Bjørn Ingmar Berg
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: linux-source-2.6.17

This is exactly the same as bug #53606. Upgrading from 6.06 to 6.10 has not taken care of it.

IBM Thinkpad R40e, type 2684-HRG
Ubuntu 6.10
kernel version 2.6.17-10-generic
all security pathes
ACPI version 0.09-1

When booting normally all power-related functions work. (Detection of main power / battery, battery charge indicator, etc.) Ubuntu is able to shut the computer completely off.
With a normal boot no special keys function.

When booting with the added parameters "NOAPIC ACPI=OFF" NO power-related functions work. (Detection of main power / battery, battery charge indicator, etc.) Ubuntu is NOT able to shut the computer completely off.
When booting with the added parameters "NOAPIC ACPI=OFF" special keys function as they should.

They keys affected are:
"Volume up"
"Volume down"
"Mute"
<FN> and all special functions invoked via the <FN> key.
"Previous page"
"Next page"

See original description
Bjørn Ingmar Berg (bergcube)
description: updated
Revision history for this message
Bjørn Ingmar Berg (bergcube) wrote :

I am anxiously awaiting a solution to this bug.

Is there anything at all I (as a user and non-programmer) can do to help speed up the bug-squatting process?

Revision history for this message
justplayin (paddyschwartz) wrote :

I can confirm this bug for my ThinkPad r40e, type 2684-54G. I have the latest bios version 1.38, released on 2005/11/28.
uname -r returns a "2.6.17-10-generic". I get the exact same behaviour as described in the first post.

I would like to know how to get the laptop to resume after a "suspend to ram". I have searched the net for quite a while and couldn't figure out how to do it. When trying to suspend to ram the laptop shuts down and the sleep button turns on, but doesn't blink. I think thats a correct behaviour. But when trying to press the power-on button, nothing happens and I have to take off the power cord and get the battery out to be able to start the laptop again. This is with acpi=on as boot-parameter.

With "acpi=off apm=on" as boot parameters the laptop doesn't try to go into suspend mode S3, but I think it goes to suspend mode S1. The screen becomes password protected and when typing in the password the desktop returns instantly. So this is not a real "suspend to ram"-mode.

Any help appreciated.

Revision history for this message
Bjørn Ingmar Berg (bergcube) wrote :

Just a small notice:

I no longer have the Thinkpad R40e laptop. I sold it to a friend. Now I have a slightly newer laptop, an IBM Thinkpad R40 type 2723-BAG. This is a Centrino-machine, and I'm glad to tell it has none of the problems reported in this bug.
As I don't have the hardware to reproduce this bug anymore I cannot keep track of the bug nor keep nagging about it. -But I hope someone can step up!

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Does it still happen with the latest release of Ubuntu ?

Changed in linux-source-2.6.17:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Matthias Haberle (matthias-haberle) wrote :

I installed the latest release (Ubuntu 7.04, Feisty Fawn, Kernel 2.6.20-16 generic) on my Thinkpad R40e (type 2684-54G, Celeron) yesterday and I still have the same problem.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Ok thank you Matthias Haberle, could you please add the following informations to bug #53606 (this bug is a duplicate of bug #53606 ) :

1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-source-2.6.17 (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.