Re: x60s: problems with brightness keys (again)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 01 Oct 2008, Paride Legovini wrote:
> I'm running an X60s with a vanilla 2.6.27-rc8 kernel (but I get the

Saved a copy of your e1000e EEPROM already?  

ethtool -e eth0 >my-e1000-eeprom.txt.

http://kerneltrap.org/mailarchive/linux-kernel/2008/10/2/3475814
http://bugzilla.kernel.org/show_bug.cgi?id=11382

You have an ICH7, but since nobody really knows what is destroying the NVM,
I'd recommend storing that EEPROM dump and patching e1000e *NOW*.

> And thats ok. And I get the hotkeys working! At a first sight even the
> brightness control seems to work, BUT, if (and only if) I reach the
> lowest level of brightness and I press the brightness-down key
> combination once again I get TWO acpi events from acpi_listen:
> 
> video LCD0 00000087 00000000
> ibm/hotkey HKEY 00000080 00005010
> 
> and the brightness control is messed up! Every change in brightness
> takes a long time to occur (almost a second), and this is very
> annoying. I get a double acpi event for every change in brightness,
> UNLESS I press the key combination too fast. In this case only
> the last event is double. Here's a series of brightness-up
> events:
> 
> video LCD0 00000086 00000000
> video LCD0 00000086 00000000
> video LCD0 00000086 00000000
> video LCD0 00000086 00000000
> video LCD0 00000086 00000000
> ibm/hotkey HKEY 00000080 00005010

That event suggests the BIOS is confused...

Please send me the output (gzipped) of dmidecode (remove UUID and serial numbers
first), and also the output (gzipped) of acpidump:

dmidecode > dmidecode.txt    (edit dmidecode.txt, remove UUID, S/N), gzip.
acpidump | gzip -9 > acpidump.txt.gz

> What happens then if I try to unload thinkpad_acpi? One thing I was
> partially not expecting: the ibm/hotkey acpi event disappears,
> but the brightness changes continue to be lagged! And the same

It is supposed to continue broken, since thinkpad-acpi is not supposed to be
affecting brightness at all, in any way.

> At the moment, at least for me, the most sane solution is not to
> load thinkpad_acpi (and renounce to the hotkeys). I can assure you
> that this lagging problem is really annoying!

Please test and report these conditions to make sure I understood things
correctly:

Does it break when:

1. You loaded thinkpad-acpi, unloaded it, then tried to reproduce

2. You NEVER loaded thinkpad-acpi, then tried to reproduce

3. You did (2) above, then loaded thinkpad-acpi and tried it again, what
happens?


-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel

[Index of Archives]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Photo]     [Yosemite Photos]     [Yosemite Advice]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux