Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different sets of modules are possible #31

Open
nponeccop opened this issue Dec 10, 2014 · 0 comments
Open

Different sets of modules are possible #31

nponeccop opened this issue Dec 10, 2014 · 0 comments

Comments

@nponeccop
Copy link

I found acpi-eeepc-generic almost unusable in default kernel configuration. So the need for different kernel modules should at least be documented.

The code expects eeepc-laptop module to be loaded, which is not always the case. To load eeepc-laptop the kernel boot option acpi_osi=Linux must be set, at least on my combination of EEE model and BIOS.

If the option is not set, the kernel loads wmi, asus-wmi and eeepc-wmi modules are loaded instead.

Interestingly asus-laptop and asus-nb-wmi modules cannot be loaded with both kernel option settings.

To investigate which modules cause which effects, it's better to test them one by one if it's not prohibited by dependencies. Processor, AC and battery events in acpi_listen are generated by processor, ac and battery kernel modules.

Apparently, readable event names only work with new *wmi modules, and existing acpi-eeepc-generic config only works with old stack based of sparse-map and eeepc-laptop modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant