> There's a manual on the asus site but, easy-peasy, take a look to the > picture from this link: http://notebookitalia.it/asus-eee-pc-1201nl- > atom-single-core-e-nvidia-ion-7391. On the upper left corner there is an > hardware button which gives the same code as the hotkey.
Ok, Does writing 1 or 0 in /sys/devices/platform/eeepc-wmi/touchpad do anything ? The DSDT doesn't seem to provide anything do control the led, but maybe they mixed up some bits, and this file control the led instead of the touchpad. Disabling the touchpad should be possible using some utility specific to your touchpad model (synclient for synaptic touchpads). >>If you installed modules from acpi4asus-dkms, you may have to load >>sparse-keymap by hand (modprobe sparse-keymap). > > Of course I've tried, but the sparse-keymap coming from standard > installation dislikes this quite too new kernel, and the compiling of > your sources does not give me a fresh one. So I'm stuck. How did you install 2.6.39 ? Because sparse-keymap should comes with it. > DSDT > I'm sending you a new copy because BIOS has been update din the autumn of > last year. If yours is still the one I sent you long ago, it could be > outdated. Thanks, eeepc-wmi and eeepc-laptop are calling (almost) exactly the same method for cpufv, so it's clearly a bug somewhere else. That'll be hard to fix without hardware. What we can try is to enable acpi debug features before writing into cpufv: See http://www.kernel.org/doc/Documentation/acpi/debug.txt echo 0xffffffff > /sys/module/acpi/parameters/debug_level echo 0xffffffff > /sys/module/acpi/parameters/debug_layer That should produce a lot of output in dmesg when doing anything related to ACPI. You should try it with X stopped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740636 Title: Asus 1201nl - hotkeys not working -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
