Eeepc-wmi
Version 6 (Sharon Hill, 06/07/2011 04:29 pm)
| 1 | 1 | Corentin Chary | h1. eeepc-wmi |
|---|---|---|---|
| 2 | 2 | Corentin Chary | |
| 3 | 2 | Corentin Chary | h2. Why a new eeepc platform driver ? |
| 4 | 2 | Corentin Chary | |
| 5 | 2 | Corentin Chary | The eeepc-laptop module use an "ACPI":http://en.wikipedia.org/wiki/ACPI device (ASUS010) which have usually the same interface in all eeepc. For example the WLDS will always control the wlan card. |
| 6 | 2 | Corentin Chary | |
| 7 | 2 | Corentin Chary | But on newer eeepc, Asus introduced Windows 7 support. |
| 8 | 2 | Corentin Chary | Models with windows 7 support have a new "WMI":http://en.wikipedia.org/wiki/Windows_Management_Instrumentation interface. |
| 9 | 2 | Corentin Chary | And when an OS is detected as Windows 7, the old ASUS010 interface is disabled. |
| 10 | 2 | Corentin Chary | |
| 11 | 2 | Corentin Chary | 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. |
| 12 | 2 | Corentin Chary | The Linux kernel returns true when OSI is invoked with any known Windows OS string. |
| 13 | 2 | Corentin Chary | |
| 14 | 2 | Corentin Chary | So, Linux is identified as Windows 7, ASUS010 device is disable, eeepc-laptop can't be loaded. |
| 15 | 2 | Corentin Chary | |
| 16 | 3 | Corentin Chary | h2. Why acpi blacklisting is not a solution ? (or acpi_osi="!Windows 2009") |
| 17 | 2 | Corentin Chary | |
| 18 | 3 | Corentin Chary | A quick workaround is to boot with acpi_osi="!Windows 2009" (and sometime acpi_osi="Linux") but: |
| 19 | 2 | Corentin Chary | |
| 20 | 2 | Corentin Chary | From Len Brown, maintainer of Linux ACPI subsystem |
| 21 | 2 | Corentin Chary | > Not necessarily the right fix. We have gone to a lot of trouble |
| 22 | 2 | Corentin Chary | > to discourage BIOS vendors from depending on the ill-defined OSI(Linux), |
| 23 | 2 | Corentin Chary | > so I hesitate to invoke it -- even for a workaround. |
| 24 | 2 | Corentin Chary | |
| 25 | 2 | Corentin Chary | 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. |
| 26 | 2 | Corentin Chary | |
| 27 | 2 | Corentin Chary | *The solution would be to write a new eeepc-wmi driver.* |
| 28 | 2 | Corentin Chary | |
| 29 | 2 | Corentin Chary | h2. What models are affected ? |
| 30 | 2 | Corentin Chary | |
| 31 | 2 | Corentin Chary | Basically, all models with "Windows 7 support" |
| 32 | 2 | Corentin Chary | |
| 33 | 2 | Corentin Chary | * 1101HA |
| 34 | 2 | Corentin Chary | * 1005HA |
| 35 | 2 | Corentin Chary | * 1005P |
| 36 | 2 | Corentin Chary | * 1201N |
| 37 | 2 | Corentin Chary | |
| 38 | 2 | Corentin Chary | h2. How can I help ? |
| 39 | 2 | Corentin Chary | |
| 40 | 4 | Corentin Chary | If you know how to write a driver, then add missing features to eeepc-wmi. |
| 41 | 2 | Corentin Chary | If you have hardware to give, and you live near Lyon (France), contact me. |
| 42 | 2 | Corentin Chary | 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. |
| 43 | 2 | Corentin Chary | |
| 44 | 2 | Corentin Chary | h2. Status |
| 45 | 2 | Corentin Chary | |
| 46 | 5 | Corentin Chary | Yong Wang started wrote a driver named eeepc-wmi. It's available in new kernels (>= 2.6.35). |
| 47 | 6 | Sharon Hill | |
| 48 | 6 | Sharon Hill | "Online Technical Support":https://www.techienow.com/ |