Until the brightness Fn buttons work, I can highly recommend indicator-brightness. Works perfectly (you can use mouse scrollwheel when hovering the indicator).
http://codevanrohde.nl/wordpress/?p=128
I found a 'better' way to persist the palmdetection settings.
1. create a new file in /usr/share/X11/xorg.conf.d/ called '52-asus-zenbook-synaptics.conf'
2. Paste the following in it
3. save it, reboot, and you should have:Code:# Example xorg.conf.d snippet that assigns the touchpad driver # to all touchpads. See xorg.conf.d(5) for more information on # InputClass. # DO NOT EDIT THIS FILE, your distribution will likely overwrite # it when updating. Copy (and rename) this file into # /etc/X11/xorg.conf.d first. # Additional options may be added in the form of # Option "OptionName" "value" # Section "InputClass" Identifier "touchpad catchall" Driver "synaptics" MatchIsTouchpad "on" # This option is recommend on all Linux systems using evdev, but cannot be # enabled by default. See the following link for details: # http://who-t.blogspot.com/2010/11/how-to-ignore-configuration-errors.html MatchDevicePath "/dev/input/event*" Option "CircularScrolling" "on" Option "CircScrollTrigger" "0" Option "PalmDetect" "on" Option "PalmMinWidth" "4" Option "PalmMinZ" "1" EndSection Section "InputClass" Identifier "touchpad ignore duplicates" MatchIsTouchpad "on" MatchOS "Linux" MatchDevicePath "/dev/input/mouse*" Option "Ignore" "on" EndSection # This option enables the bottom right corner to be a right button on # non-synaptics clickpads. # This option is only interpreted by clickpads. Section "InputClass" Identifier "Default clickpad buttons" MatchDriver "synaptics" Option "SoftButtonAreas" "50% 0 82% 0 0 0 0 0" EndSection # This option disables software buttons on Apple touchpads. # This option is only interpreted by clickpads. Section "InputClass" Identifier "Disable clickpad buttons on Apple touchpads" MatchProduct "Apple|bcm5974" MatchDriver "synaptics" Option "SoftButtonAreas" "0 0 0 0 0 0 0 0" EndSection
* Palmdetection
* Circular scrolling (a personal preference of mine, google it
The script (and its updated version) fails with
Code:** (gsd-backlight-helper:3487): WARNING **: failed to find any devices ** (gsd-backlight-helper:3489): WARNING **: failed to find any devices Traceback (most recent call last): File "/usr/bin/indicator-brightness", line 93, in <module> create_menu(ind) File "/usr/bin/indicator-brightness", line 60, in create_menu curr_brightness = get_curr_brightness() File "/usr/bin/indicator-brightness", line 38, in get_curr_brightness curr_brightness = int(p.communicate()[0]) ValueError: invalid literal for int() with base 10: ''
Again no files (except 'version') in /sys/class/drm and the system won't boot properly (hangs on a purple screen) unless I start the recovery mode and then resume boot (which sometimes gives a 'swapper' related stacktrace.
Last edited by bambam23; July 18th, 2012 at 08:12 AM.
Warning: You might nog want to update when running quantal, doing so has removed my ability to change brightness
Something in quantal probably broke.
Edit: Suspend/resume is also defective, which always seems to happen in conjuction with brightness being defective. Using xorg-edgers makes no difference.
Last edited by peter rus; July 18th, 2012 at 02:58 PM.
This works pretty good, but for me the following works a bit better:synclient PalmDetect=1
xinput set-prop "ETPS/2 Elantech Touchpad" "Synaptics Palm Dimensions" 4 1
That mean's that all clicks are disabled for 1.7 seconds. Maybe the best setting is a combination of both.Code:killall syndaemon syndaemon -i 1.7 -d -t
Btw, I'm using kernel 3.4.4 (mainline-kernel).
@ Maroony, will try that later, but first:
I have tracked down the source of my system not booting and the kernel panics:
the asus-wmi patch (http://comments.gmane.org/gmane.linux.kernel/1315719)
When I boot, the process hangs forever in the dotted ubuntu splash. When I boot in recovery mode however, and then choose 'resume boot' everything works fine. This might have to do with some race condition occuring, but thats up to the programmers
When I booted through the recovery mode method the asus-wmi module works (I can use the functionbuttons) but for some reason this also prevents DRM from properly loading, and thus /sys/class/drm/ is not populated, which in turn means you can not use external monitors, waking from suspend does not work (screen stays black, with no way to turn it back on) and setting the brightness of the screen is not possible through the gnome-settings or xbacklight/xrandr. The intel_backlight utility hoewever still works.
I am booting from an SSD so people using the HDD as root might not have this problem. If you want to remove the patched asus-wmi module, run the following:
I added some entries to the wiki: https://help.ubuntu.com/community/As...ev2=28&rev1=27Code:sudo dkms remove asus-wmi/999.01 --all
Furthermore: also see my entry on nomodeset, when I boot using nomodeset I get exactly the same issues as described above. I also updated the wiki about it: https://help.ubuntu.com/community/As...ev2=29&rev1=28
Last edited by peter rus; July 19th, 2012 at 02:34 PM.
Bookmarks