[Debian-eeepc-devel] eeepc-acpi-scripts bits for testing

Santi Béjar santi at agolina.net
Wed May 27 21:31:00 UTC 2009

2009/5/27 Darren Salt <linux at youmustbejoking.demon.co.uk>:
> I demand that Santi Béjar may or may not have written...
>> 2009/5/27 Santi Béjar <santi at agolina.net>:
>>> 2009/5/25 Darren Salt <linux at youmustbejoking.demon.co.uk>:
>>>> We have two branches in eeepc-acpi-scripts.git which need a few quick
>>>> tests.
>>> [...]
>>>> "shengine": only for those who are running Linux 2.6.30-rc7 (or have
>>>> applied the ACPI patch which is merged into -rc7). You'll need to edit
>>>> /etc/default/eeepc-acpi-scripts to assign "handle_shengine" to a key; I
>>>> suggest the "task manager" key (Fn-F6 or Fn-F9).
>> So now I've tested it, and it works somehow. The problem is that I cannot
>> set cpufv=2, it is stuck at cpufv=1 so it doesn't cycle between the three
>> (or two) values. (I can change it from 0 to 1 with the key).
> Hmm. That sounds like the BIOS and/or hardware only supports two states; what
> hardware? (I'm guessing one of the Celeron-based ones, since all three states
> are useable on my 901.)

701 4G with the lastest BIOS, 1302.

> (Incidentally, your build failure doesn't happen here.)

I don't know, what I can say is that I use unstable.


More information about the Debian-eeepc-devel mailing list