Bug 14865
Summary: | eeepc-laptop: touchpad led is inverted on Eee1001HAG | ||
---|---|---|---|
Product: | Drivers | Reporter: | Simeon Maryasin (kb.10.marsoft) |
Component: | Platform | Assignee: | Corentin Chary (corentin.chary) |
Status: | RESOLVED DOCUMENTED | ||
Severity: | normal | CC: | alan, perlovka, rui.zhang |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.33-rc1 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 56331 | ||
Attachments: |
simple patch which fixed problem for me
/proc/acpi/dsdt (I hope it is what you told about...) acpidump for 1005ha |
re-assign to Henrique. Sorry Zhang, but I don't take care of Eee-PC ;-) Maybe you wanted someone else? oops. re-assign to Corentin. :p Could you send me your dsdt ? Thanks Created attachment 24352 [details]
/proc/acpi/dsdt (I hope it is what you told about...)
Created attachment 24379 [details]
acpidump for 1005ha
Hum,(In reply to comment #6) > Created an attachment (id=24379) [details] > acpidump for 1005ha Thanks, the code for touchpad seems to be the same. Andrej, can you reproduce this bug on your 1005ha ? ping... close this bug as there is no response for more than 3 months. Which data is needed? Can I help? (I have not 1005ha...) Corentin, does the patch in comment #0 make sense? the dsdt of semen's laptop is attached in comment #5. (In reply to comment #11) > Corentin, > does the patch in comment #0 make sense? > the dsdt of semen's laptop is attached in comment #5. The patch make sense for this model, but I don't know if it won't break on over models with touchpad led, and I didn't get any answer about that (here, and on the mailing list). Maybe we should apply the patch and wait for a regression report, but I'm not sure that this is a really good practice ... Reproducable on 1005HA as well, patch from https://bugzilla.kernel.org/show_bug.cgi?id=14865#c0 fixed the problem (kernel-2.6.34.9). 1xxx models should not use eeepc-laptop, they should use eeepc-wmi instead. Please reopen this bug if a model below 1000 is affected or if eeepc-wmi is also affected. (In reply to comment #14) > 1xxx models should not use eeepc-laptop, they should use eeepc-wmi instead. I just tried to use eeepc-wmi, but couldn't load module: # modprobe eeepc-wmi FATAL: Error inserting eeepc_wmi (/lib/modules/3.6.38-gentoo/kernel/drivers/platform/x86/eeepc_wmi.ko): No such device # dmesg | tail <...> [ 5486.078107] wmi: Mapper loaded [ 6586.102116] eeepc_wmi: No known WMI GUID found My device is EeePC 1001 HAG. eeepc-laptop works fine (but with this led bug). Maybe WMI works only for newer models such as 1001PX?.. I guess 1001HA and 1001HAG are the same. if yes you probably need to update your bios. The latest bios update is BIOS 1401 - 2010.03.15. |
Created attachment 24264 [details] simple patch which fixed problem for me There is support for eeepc 1005 etc touchpad led. But on my EeePC 1001 HAG it behaves as: after boot /sys/devices/platform/eeepc/leds/eeepc::touchpad/brightness == 0 and led is off; when I do 'echo 1 > /sys/devices/platform/eeepc/leds/eeepc::touchpad/brightness', it becomes ==1, but led is still off; when I do 'echo 0 > /sys/devices/platform/eeepc/leds/eeepc::touchpad/brightness', it becomes ==0, and led is now on. Unfortunately I hadn't chance to test on EeePC 1005, maybe it is 1001's issue.