eeepc-wmi¶
Why a new eeepc platform driver ?¶
The eeepc-laptop module use an ACPI device (ASUS010) which have usually the same interface in all eeepc. For example the WLDS will always control the wlan card.
But on newer eeepc, Asus introduced Windows 7 support.
Models with windows 7 support have a new WMI interface.
And when an OS is detected as Windows 7, the old ASUS010 interface is disabled.
OSI is an ACPI method provided by the operating system that can be invoked by ACPI BIOS code. It is used by BIOS developers to detect which operating system is running.
The Linux kernel returns true when OSI is invoked with any known Windows OS string.
So, Linux is identified as Windows 7, ASUS010 device is disable, eeepc-laptop can't be loaded.
Why acpi blacklisting is not a solution ? (or acpi_osi="!Windows 2009")¶
A quick workaround is to boot with acpi_osi="!Windows 2009" (and sometime acpi_osi="Linux") but:
From Len Brown, maintainer of Linux ACPI subsystem
Not necessarily the right fix. We have gone to a lot of trouble
to discourage BIOS vendors from depending on the ill-defined OSI,
so I hesitate to invoke it -- even for a workaround.
Anyway, no that thw wmi interface is here, we can't bet that the old interface won't be maintained and won't expose all features.
The solution would be to write a new eeepc-wmi driver.
What models are affected ?¶
Basically, all models with "Windows 7 support"
- 1101HA
- 1005HA
- 1005P
- 1201N
How can I help ?¶
If you know how to write a driver, then add missing features to eeepc-wmi.
If you have hardware to give, and you live near Lyon (France), contact me.
Else, you can make a small donation to the acpi4asus project, as soon as there is enought money (~250 euros), I'll buy a 1005HA and write a driver for it.
Status¶
Yong Wang started wrote a driver named eeepc-wmi. It's available in new kernels (>= 2.6.35).