Bug #740636 “Asus 1201nl - hotkeys not working” : Bugs : linux package : Ubuntu

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-03-23:

#1

AcpiTables.txt Edit (215.7 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (517 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (271 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (51.0 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (9.0 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.3.txt Edit (3.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (719 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (556 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (11.5 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (588 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.3 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (121 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (117.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (244.4 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (171.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Julian Wiedmann (jwiedmann) wrote on 2011-03-27:

#2

What happens if you boot without acpi_osi=Linux?

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-03-27:

#3

dmesgnoacpiosi.txt Edit (53.2 KiB, text/plain)

Good point. Here is what happens without "acpi_osi=Linux"

Worst: it does not create /sys/devices/platform/eeepc/cpufv. This prevents the use of SHE (super hybrid engine) and the relative energy consumption policies.

For what concerns hotkeys, here is the situation:

fn+F2: wlan toggle WORKS

fn+F7: screen on/off still doesn't work. Dmesg reported below.
    kbd_keycode: 6 callbacks suppressed
    keyboard: can't emulate rawmode for keycode 245
    keyboard: can't emulate rawmode for keycode 245

fn+F8: screen/monitor switch still does not work with no message reported in syslog.

Revision history for this message

Julian Wiedmann (jwiedmann) wrote on 2011-03-28:

#4

(CC'ing Corentin, as this is a eeepc related bug)

The kernel in -proposed adds support for some new hotkeys (such as wlan toggle) to the eeepc_wmi driver (see #689393) - Corentin, I guess eeepc_laptop doesn't like the fact that now there's suddenly two drivers trying to handle wlan toggle?

Revision history for this message

Corentin Chary (iksaif) wrote on 2011-03-28:

#5

There was a bug allowing eeepc-wmi to load with acpi_osi="Linux". It's fixed in recent kernels. BTW, acpi_osi="Linux" should not be used anymore.

Luca,

First, without acpi_osi=Linux, eeepc-wmi is loaded, and files are now in /sys/devices/platform/eeepc-wmi/.

Could you try this dkms package: http://git.iksaif.net/?p=acpi4asus-dkms.git;a=summary ? To build it you can either build the debian package and install it (use dpkg-buildpackage), or read http://dev.iksaif.net/projects/acpi4asus/wiki/Backport_module .

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-03-28:

#6

dmesg.txt Edit (54.7 KiB, text/plain)

Hi!
I did, but not succeed.

Fn+F2 (wlan toggle) works;
fn+F7 (screen on/off) fails with message "keyboard: can't emulate rawmode for keycode 244";
fn+F8 (screen/monitor switch) fails with no messages;
fn+F9 (touchpad disables) does not work and gives no messages.

Cpu state, took as superuser, reports: "cat: /sys/devices/platform/eeepc-wmi/cpufv: Errore di input/output"

and if I try to put some values with the terminal session with root privileges hangs and the cpu starts to blow hard and never stops. Command below;
$echo 1 > /sys/devices/platform/eeepc-wmi/cpufv

Here's what I did.
1) Started pc without "acpi_osi=Linux";

2) Download and compiled as in http://dev.iksaif.net/projects/acpi4asus/wiki/Backport_module;

3) Removed modules. Messages following:
FATAL: Module asus_nb_wmi not found.
FATAL: Module asus_wmi not found.
rmmod /lib/modules/2.6.35-28-generic/kernel/drivers/platform/x86/eeepc-wmi.ko
rmmod /lib/modules/2.6.35-28-generic/kernel/drivers/input/sparse-keymap.ko

4) Reloaded modules. Sparse keymap was missing, so I've reloaded it from the original position as it was in step3. Messages from the failed load where:

$ sudo insmod asus-wmi.ko
insmod: error inserting 'asus-wmi.ko': -1 Unknown symbol in module

$sudo insmod eeepc-wmi.ko
insmod: error inserting 'eeepc-wmi.ko': -1 Unknown symbol in module

$sudo insmod asus-laptop.ko
insmod: error inserting 'asus-laptop.ko': -1 Unknown symbol in module

[ 578.533222] asus_wmi: Unknown symbol sparse_keymap_free (err 0)
[ 578.538390] asus_wmi: Unknown symbol sparse_keymap_report_event (err 0)
[ 578.538695] asus_wmi: Unknown symbol sparse_keymap_setup (err 0)
[ 600.286585] eeepc_wmi: Unknown symbol asus_wmi_register_driver (err 0)
[ 600.287261] eeepc_wmi: Unknown symbol asus_wmi_unregister_driver (err 0)
[ 621.513524] asus_laptop: Unknown symbol sparse_keymap_free (err 0)
[ 621.519482] asus_laptop: Unknown symbol sparse_keymap_report_event (err 0)
[ 621.519957] asus_laptop: Unknown symbol sparse_keymap_setup (err 0)

4) After reloading sparse-keymap everything went fine and here below the dmesg:
[ 817.485146] asus_wmi: ASUS WMI generic driver loaded
[ 827.634257] asus_wmi: Initialization: 0x0
[ 827.634567] asus_wmi: BIOS WMI version: 0.7
[ 827.634956] asus_wmi: SFUN value: 0x0
[ 827.660861] input: eeepc-wmi/input0 as /devices/platform/eeepc-wmi/input/input9
[ 828.693258] asus_wmi: Backlight controlled by ACPI video driver
[ 860.612861] kbd_keycode: 6 callbacks suppressed
[ 860.612875] keyboard: can't emulate rawmode for keycode 244
[ 860.612931] keyboard: can't emulate rawmode for keycode 244

Hi!
I did, but not succeed.

Fn+F2 (wlan toggle) works;
fn+F7 (screen on/off) fails with message "keyboard: can't emulate rawmode for keycode 244";
fn+F8 (screen/monitor switch) fails with no messages;
fn+F9 (touchpad disables) does not work and gives no messages.

Cpu state, took as superuser, reports: "cat: /sys/devices/platform/eeepc-wmi/cpufv: Errore di input/output"

and if I try to put some values with the terminal session with root privileges hangs and the cpu starts to blow hard and never stops. Command below;
$echo 1 > /sys/devices/platform/eeepc-wmi/cpufv

Here's what I did.
1) Started pc without "acpi_osi=Linux";

2) Download and compiled as in http://dev.iksaif.net/projects/acpi4asus/wiki/Backport_module;

3) Removed modules. Messages following:
FATAL: Module asus_nb_wmi not found.
FATAL: Module asus_wmi not found.
rmmod /lib/modules/2.6.35-28-generic/kernel/drivers/platform/x86/eeepc-wmi.ko
rmmod /lib/modules/2.6.35-28-generic/kernel/drivers/input/sparse-keymap.ko

4) Reloaded modules. Sparse keymap was missing, so I've reloaded it from the original position as it was in step3. Messages from the failed load where:

$ sudo insmod asus-wmi.ko
insmod: error inserting 'asus-wmi.ko': -1 Unknown symbol in module

$sudo insmod eeepc-wmi.ko
insmod: error inserting 'eeepc-wmi.ko': -1 Unknown symbol in module

$sudo insmod asus-laptop.ko
insmod: error inserting 'asus-laptop.ko': -1 Unknown symbol in module

[  578.533222] asus_wmi: Unknown symbol sparse_keymap_free (err 0)
[  578.538390] asus_wmi: Unknown symbol sparse_keymap_report_event (err 0)
[  578.538695] asus_wmi: Unknown symbol sparse_keymap_setup (err 0)
[  600.286585] eeepc_wmi: Unknown symbol asus_wmi_register_driver (err 0)
[  600.287261] eeepc_wmi: Unknown symbol asus_wmi_unregister_driver (err 0)
[  621.513524] asus_laptop: Unknown symbol sparse_keymap_free (err 0)
[  621.519482] asus_laptop: Unknown symbol sparse_keymap_report_event (err 0)
[  621.519957] asus_laptop: Unknown symbol sparse_keymap_setup (err 0)

4) After reloading sparse-keymap everything went fine and here below the dmesg:
[  817.485146] asus_wmi: ASUS WMI generic driver loaded
[  827.634257] asus_wmi: Initialization: 0x0
[  827.634567] asus_wmi: BIOS WMI version: 0.7
[  827.634956] asus_wmi: SFUN value: 0x0
[  827.660861] input: eeepc-wmi/input0 as /devices/platform/eeepc-wmi/input/input9
[  828.693258] asus_wmi: Backlight controlled by ACPI video driver
[  860.612861] kbd_keycode: 6 callbacks suppressed
[  860.612875] keyboard: can't emulate rawmode for keycode 244
[  860.612931] keyboard: can't emulate rawmode for keycode 244

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-03-28:

#7

One more thing.
When the computer it's started WITHOUT acpi_osi=Linux there are no traces of cpufv file. Indeed, here's below the listing of directory.

It starts to exist only if I load your modules.

root@ubuntu6:/sys/devices/platform/eeepc-wmi# ls -l
totale 0
lrwxrwxrwx 1 root root 0 2011-03-29 01:52 driver -> ../../../bus/platform/drivers/eeepc-wmi
drwxr-xr-x 3 root root 0 2011-03-29 01:52 input
-r--r--r-- 1 root root 4096 2011-03-29 01:54 modalias
drwxr-xr-x 2 root root 0 2011-03-29 01:54 power
lrwxrwxrwx 1 root root 0 2011-03-29 01:52 subsystem -> ../../../bus/platform
-rw-r--r-- 1 root root 4096 2011-03-29 01:52 uevent

At disposition.
Luca

Revision history for this message

Corentin Chary (iksaif) wrote on 2011-03-29: Re: [Bug 740636] Re: Asus 1201nl - hotkeys not working

#8

On Tue, Mar 29, 2011 at 1:51 AM, Luca Aluffi <email address hidden> wrote:
> Hi!
> I did, but not succeed.
>
> Fn+F2 (wlan toggle) works;
> fn+F7 (screen on/off) fails with message "keyboard: can't emulate rawmode for keycode 244";
> fn+F8 (screen/monitor switch) fails with no messages;
> fn+F9 (touchpad disables) does not work and gives no messages.

As soon as dmesg doesn't contain "unknown key xxx" that means that the
key is successfully mapped and you can associate an action to it. It's
just a matter of configuration, and if you want these keys to work out
the box, you can create a new bug for each key.

> Cpu state, took as superuser, reports: "cat: /sys/devices/platform
> /eeepc-wmi/cpufv: Errore di input/output"

I't ok, there is no way for eeepc-wmi to guess the current value.

> and if I try to put some values with the terminal session with root privileges hangs and the cpu starts to blow hard and never stops. Command below;
> $echo 1 > /sys/devices/platform/eeepc-wmi/cpufv

Seems that your BIOS is bugged, is it up to date ?

Revision history for this message

Corentin Chary (iksaif) wrote on 2011-03-29:

#9

> One more thing.
> When the computer it's started WITHOUT acpi_osi=Linux there are no traces of cpufv file. Indeed, here's below the listing of directory.
> It starts to exist only if I load your modules.

On 2.6.38, eeepc-wmi didn't support cpufv.

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-03-29:

#10

Hi again.
Let's resume; in brief.

> On 2.6.38, eeepc-wmi didn't support cpufv.
I don't understand if I have to forget it or is just a matter of time and it will be supported again.
It sounds that cpu and voltage throttling is a good thing for battery life. Anyway I'm still stick to 2.6.35 coming from maverick and it should work, even without acpi_osi=Linux. Am I missing something?

Don't take it as a complaint: it's just I don't know enough about acpi to be able in judging whether cpufv is good or bad. It sounds good but, maybe, it's not.

> and if you want these keys to work out the box, you can create a new bug for each key.
I will, if it's the right way. Have I to file a bug against the kernel or there is a particular package? Just tell me and I will do.

>Seems that your BIOS is bugged, is it up to date ?
Sadly, yes. Is the last version available from ASUS website.
I remember I wrote you about similar problems almost one year ago, and I've tried to file some bugs to their support but they just told they not support linux. Same old story...

Hear you soon.
Luca

Revision history for this message

Corentin Chary (iksaif) wrote on 2011-03-30:

#11

On Wed, Mar 30, 2011 at 1:10 AM, Luca Aluffi <email address hidden> wrote:
> Hi again.
> Let's resume; in brief.
>
>> On 2.6.38, eeepc-wmi didn't support cpufv.
> I don't understand if I have to forget it or is just a matter of time and it will be supported again.
> It sounds that cpu and voltage throttling is a good thing for battery life. Anyway I'm still stick to 2.6.35 coming from maverick and it should work, even without acpi_osi=Linux. Am I missing something?
>
> Don't take it as a complaint: it's just I don't know enough about acpi
> to be able in judging whether cpufv is good or bad. It sounds good but,
> maybe, it's not.

On 2.6.35, eeepc-wmi didn't support a lot of features, including cpufv.
On 2.6.38, I was wrong, eeepc-wmi *did* support cpufv.
On 2.6.39 (and using acpi4asus-dkms tree, like you did), it also does.
The only thing is that cpufv is read-only.
You should be able to use acpi4asus-dkms with 2.6.35, but it's a good
idea to upgrade your kernel as soon as you can (Natty should be
released soon right ?).

>> and if you want these keys to work out the box, you can create a new bug for each key.
> I will, if it's the right way. Have I to file a bug against the kernel or there is a particular package? Just tell me and I will do.

No, the kernel is just in charge of sending keys. This is the
distribution role to make sure that these keys are handled
out-the-box. But most of the time, it's also your desktop environment
that take care of that. So you can probably file a bug against KDE or
Gnome. For example on gnome, g-p-m handle a lot of these keys. For
some keys, you should also be able to bind them to the right action
using your DE configuration interface.

>>Seems that your BIOS is bugged, is it up to date ?
> Sadly, yes. Is the last version available from ASUS website.
> I remember I wrote you about similar problems almost one year ago, and I've tried to file some bugs to their support but they just told they not support linux. Same old story...

So, let's try to fix the cpufv problem again.
Could you try:
- with different kernel versions (2.6.35, 2.6.38, 2.6.38+ ?)
- with and without acpi_osi=Linux

Note that:
- with acpi_osi=Linux you have to be sure that only eeepc-laptop is
loaded when you set acpi_osi, remove eeepc-wmi with rrmod
- when using 2.6.35 and eeepc-wmi, make sure that you use a the new
version of eeepc-wmi

And make a small table of working and non-working configurations ?

Thanks

On Wed, Mar 30, 2011 at 1:10 AM, Luca Aluffi <740636@bugs.launchpad.net> wrote:
> Hi again.
> Let's resume; in brief.
>
>> On 2.6.38, eeepc-wmi didn't support cpufv.
> I don't understand if I have to forget it or is just a matter of time and it will be supported again.
> It sounds that cpu and voltage throttling is a good thing for battery life. Anyway I'm still stick to 2.6.35 coming from maverick and it should work, even without acpi_osi=Linux. Am I missing something?
>
> Don't take it as a complaint: it's just I don't know enough about acpi
> to be able in judging whether cpufv is good or bad. It sounds good but,
> maybe, it's not.

On 2.6.35, eeepc-wmi didn't support a lot of features, including cpufv.
On 2.6.38, I was wrong, eeepc-wmi *did* support cpufv.
On 2.6.39 (and using acpi4asus-dkms tree, like you did), it also does.
The only thing is that cpufv is read-only.
You should be able to use acpi4asus-dkms with 2.6.35, but it's a good
idea to upgrade your kernel as soon as you can (Natty should be
released soon right ?).

>> and if you want these keys to work out the box, you can create a new bug for each key.
> I will, if it's the right way. Have I to file a bug against the kernel or there is a particular package? Just tell me and I will do.

No, the kernel is just in charge of sending keys. This is the
distribution role to make sure that these keys are handled
out-the-box. But most of the time, it's also your desktop environment
that take care of that. So you can probably file a bug against KDE or
Gnome. For example on gnome, g-p-m handle a lot of these keys. For
some keys, you should also be able to bind them to the right action
using your DE configuration interface.

>>Seems that your BIOS is bugged, is it up to date ?
> Sadly, yes. Is the last version available from ASUS website.
> I remember I wrote you about similar problems almost one year ago, and I've tried to file some bugs to their support but they just told they not support linux. Same old story...

So, let's try to fix the cpufv problem again.
Could you try:
- with different kernel versions (2.6.35, 2.6.38, 2.6.38+ ?)
- with and without acpi_osi=Linux

Note that:
- with acpi_osi=Linux you have to be sure that only eeepc-laptop is
loaded when you set acpi_osi, remove eeepc-wmi with rrmod
- when using 2.6.35 and eeepc-wmi, make sure that you use a the new
version of eeepc-wmi

And make a small table of working and non-working configurations ?

Thanks

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-03-31:

#12

compare_table.odt Edit (29.6 KiB, application/vnd.oasis.opendocument.text)

Ok.
It took a little while but I did. I've attached an openoffice document with the relative documentation.

2.6.39 is not well supported by nvidia yet so test has not been extensive. Anyway, from cpufv point of view, it was the kernel that supported better.

Anyway, the better combination seems to be acpi_osi+eeepc-laptop, rather than without acpi_osi.

Hear you soon.
Luca

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-03-31:

#13

Now it's too late. Tomorrow I will also file some bug against gnome for the screen toggle and screen switch-off hotkeys.

In a previous post you wrote me about g-p-m: what does it stand for? Gnome-power-management?

Revision history for this message

Corentin Chary (iksaif) wrote on 2011-03-31:

#14

On Thu, Mar 31, 2011 at 2:14 AM, Luca Aluffi <email address hidden> wrote:
> Now it's too late. Tomorrow I will also file some bug against gnome for
> the screen toggle and screen switch-off hotkeys.

If you do so, you should also send what "showkey" and "xev" report
when you're pressing the key.

> In a previous post you wrote me about g-p-m: what does it stand for?
> Gnome-power-management?

Yes,

--
Corentin Chary
http://xf.iksaif.net

Revision history for this message

Corentin Chary (iksaif) wrote on 2011-03-31:

#15

On Thu, Mar 31, 2011 at 2:11 AM, Luca Aluffi <email address hidden> wrote:
> Ok.
> It took a little while but I did. I've attached an openoffice document with the relative documentation.
>
> 2.6.39 is not well supported by nvidia yet so test has not been
> extensive. Anyway, from cpufv point of view, it was the kernel that
> supported better.
>
> Anyway, the better combination seems to be acpi_osi+eeepc-laptop, rather
> than without acpi_osi.

Some things about the document:

- "keyboard: can't emulate rawmode for keycode 245" is not really an
issue, just check that the key is reported with "xev" and/or
"showkey". If it is, then eeepc-{laptop|wmi} is doing its job
correctlu.
- without acpi_osi="Linux" eeepc-laptop can't load, with it eeepc-wmi
can't, that's fine.
- "Touchpad disable does not work and gives no message on keypress.
Oddly, led light is on;" you're talking about some touchpad led ?
- "cpufv file exists but it's not readable nor writable" by "nor
writable" you mean you can echo, but you it hangs ?
- 2.6.39 + eeepc-wmi "Can't load" : you can't load the driver ? why ?
anything in dmesg ?

Thanks for your tests !
--
Corentin Chary
http://xf.iksaif.net

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-03-31:

#16

Briefly.

- "Touchpad disable does not work and gives no message on keypress.
Oddly, led light is on;" you're talking about some touchpad led ?

Yes. If you have access to some picture of this netbook, you can see that in the upper left corner there is a button. It does the same job of the "disable touchpad" hotkey. It seems to me that I remember it usually switched off and, in MS windows it's toggle depending on the touchpad state. Now is always on, unregarding the touchpad or acpi_osi value.

- "cpufv file exists but it's not readable nor writable" by "nor writable" you mean you can echo, but you it hangs ?
Exactly. The commands stalls until I break with ctrl-c. After that I can't still read anything and computer's power behaviour does not change. Easy to check: with lower (x302 value) power mode, cpu fan audible lowers rotation and noise.

- 2.6.39 + eeepc-wmi "Can't load" : you can't load the driver ? why ? anything in dmesg ?
Sorry. I supposed you knew that.
If I boot without acpi_osi no eeepc-* modules are loaded. As soon as I try to load your modules they ask for sparse-keymap and it can't be loaded. I don't remember the message and I don't have that computer with me, now. Everything else falls behind as a consequence. I will furtherinvestigate this evening.

It's pretty strange: sparse-keymap is loaded along with acpi_osi=Linux but it refuses to, without acpi_osi. Module is always the same and it worked with all the other kernel's versions.

Revision history for this message

Corentin Chary (iksaif) wrote on 2011-03-31:

#17

On Thu, Mar 31, 2011 at 10:19 AM, Luca Aluffi <email address hidden> wrote:
> Briefly.
>
> - "Touchpad disable does not work and gives no message on keypress.
> Oddly, led light is on;" you're talking about some touchpad led ?
>
> Yes. If you have access to some picture of this netbook, you can see
> that in the upper left corner there is a button. It does the same job of
> the "disable touchpad" hotkey. It seems to me that I remember it usually
> switched off and, in MS windows it's toggle depending on the touchpad
> state. Now is always on, unregarding the touchpad or acpi_osi value.

Hum I didn't find the manual for this laptop. There is to button to
disable the touchpad (Fn+Fx) and another one with a led ?
I'll check your dsdt, but you may be able to control this led with
some file in /sys/class/led/

> - "cpufv file exists but it's not readable nor writable" by "nor writable" you mean you can echo, but you it hangs ?
> Exactly. The commands stalls until I break with ctrl-c. After that I can't still read anything and computer's power behaviour does not change. Easy to check: with lower (x302 value) power mode, cpu fan audible lowers rotation and noise.
>
> - 2.6.39 + eeepc-wmi "Can't load" : you can't load the driver ? why ? anything in dmesg ?
> Sorry. I supposed you knew that.
> If I boot without acpi_osi no eeepc-* modules are loaded. As soon as I try to load your modules they ask for sparse-keymap and it can't be loaded. I don't remember the message and I don't have that computer with me, now. Everything else falls behind as a consequence. I will furtherinvestigate this evening.
>
> It's pretty strange: sparse-keymap is loaded along with acpi_osi=Linux
> but it refuses to, without acpi_osi. Module is always the same and it
> worked with all the other kernel's versions.

If you installed modules from acpi4asus-dkms, you may have to load
sparse-keymap by hand (modprobe sparse-keymap).

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-04-01:

#18

dsdt_1201nl_bios0315.dmp.gz Edit (18.7 KiB, application/octet-stream)

>Hum I didn't find the manual for this laptop. There is to button to
>disable the touchpad (Fn+Fx) and another one with a led ?
>I'll check your dsdt, but you may be able to control this led with
>some file in /sys/class/led/

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.

>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.

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 and have a great weekend.
Luca

Revision history for this message

Corentin Chary (iksaif) wrote on 2011-04-03:

#19

> 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.

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-04-05:

#20

Hi! Back to the race!

Now...
I've restored the original partition from my good ol' archive ;) so now everything goes smooth as usual. Cpufv does'n works without acpi_osi whilst wireless toggle only works with it. Screen switch on/off is still abscondind and monitor toggle is in the large, yet.

That stinky blue light is off: why? Who knows? I just know I let windows 7 to have a spin.

> How did you install 2.6.39 ? Because sparse-keymap should comes with it.

I installed 2.36.9-rc1 by compiling it into packages and then installing them. To be clear:
$ fakeroot make-kpkg --initrd kernel_image kernel_headers
After copying old .config and the doing a "make oldconfig".

There where no trace of sparse keymap in libraries except in the old one. But it was late in the night so I will check it again.

> Does writing 1 or 0 in /sys/devices/platform/eeepc-wmi/touchpad do anything ?

This, along with other files you mentioned later, does not appear anywhere: now I'm stick to 2.6.35 kernel and guess I have to reinstall the other stuff to test the values you wrote.
So: do you preferer to test it under 2.6.38.2 or 2.6.39? I should more keen to test it under 2.6.38 because it's about to be released along with Ubuntu-Natty.

Revision history for this message

Corentin Chary (iksaif) wrote on 2011-04-05:

#21

>> Does writing 1 or 0 in /sys/devices/platform/eeepc-wmi/touchpad do
> anything ?
>
> This, along with other files you mentioned later, does not appear anywhere: now I'm stick to 2.6.35 kernel and guess I have to reinstall the other stuff to test the values you wrote.
> So: do you preferer to test it under 2.6.38.2 or 2.6.39? I should more keen to test it under 2.6.38 because it's about to be released along with Ubuntu-Natty.

Natty with have some 2.6.38 eeepc related patchs. So you can try to
use a natty kernel, or a 2.6.38 + acpi4asus-dkms.
Could you try to do that, and check:

- the touchpad file
- cpufv with acpi debugging enabled (see previous message)

Thanks,

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2011-04-07:

#22

Hi!
I'm still here. I'm not avoiding my task but I have some jobs to do in my spare time: just give me few days and I'll be back right here.

Thanks for your help.
Luca

Brad Figg (brad-figg) on 2011-05-04

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

AceLan Kao (acelankao) wrote on 2012-05-16:

#23

asus-wmi-dkms_1.0_all.deb Edit (32.6 KiB, application/x-debian-package)

Hi,

Are you still here and available to re-test the hotkey issues by using 12.04?
I'm prepared to submit a patch for "fn+F7: screen on/off" issue and would like to know if you have time to test it.

AceLan Kao (acelankao) on 2012-05-16

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2012-05-16:

#24

Sure, just let me go home and I'll try.

Hang on, I'll answer this evening.

Revision history for this message

Luca Aluffi (aluffilu) wrote on 2012-05-17:

#25

Hi!

It works almost everything except for the switch from the screen to monitor.

What information do you need?

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-07-25:

#26

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Gary M (garym) on 2012-07-25

Changed in linux (Ubuntu):
status:	Expired → Confirmed

penalvch (penalvch) on 2012-10-17

description:

updated

Revision history for this message

penalvch (penalvch) wrote on 2012-10-17:

#27

Luca Aluffi, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs