View previous topic :: View next topic |
Author |
Message |
BlueFusion Guru

Joined: 08 Mar 2006 Posts: 371
|
Posted: Sat Apr 19, 2014 10:35 pm Post subject: [SOLVED] Synaptics & xorg.conf.d |
|
|
Hey all,
I got myself a new laptop, an ASUS Q501LA which came with Windows 8. Before I even booted it up, I built a stage4 of Gentoo to install
I've had few issues with it, however one really annoying thing that I can not get configured the way I want it is the touchpad.
I am running it with no xorg.conf file and everything works out-of-the-box. The settings on the synaptics touchpad need tweaking since it is far too sensitive and doesn't scroll.
I made an /etc/X11/xorg.conf.d folder and put in a 50-synaptics.conf file in there, but Xorg never loads the file, according to Xorg.0.log. Also, the synaptics driver never gets loaded - Xorg is just using the evdev driver according to the logfile, and based on the failure of the synclient application.
Here is the configuration I am trying to run:
Quote: | zenith X11 # cat /etc/X11/xorg.conf.d/50-synaptics.conf
Section "InputClass"
Identifier "touchpad"
Driver "synaptics"
MatchIsTouchpad "on"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "VertEdgeScroll" "on"
Option "VertTwoFingerScroll" "on"
Option "HorizEdgeScroll" "on"
Option "HorizTwoFingerScroll" "on"
Option "CircularScrolling" "on"
Option "CircScrollTrigger" "2"
Option "EmulateTwoFingerMinZ" "40"
Option "EmulateTwoFingerMinW" "8"
Option "LeftEdge" "1700" # x coord left
Option "RightEdge" "5300" # x coord right
Option "TopEdge" "1700" # y coord top
Option "BottomEdge" "4200" # y coord bottom
Option "FingerLow" "25" # pressure below this level triggers release
Option "FingerHigh" "30" # pressure above this level triggers touch
Option "MaxTapTime" "180" # max time in ms for detecting tap
EndSection |
_________________ i7-940 2.93Ghz | ASUS P6T Deluxe (v.1) | 24GB Triple Channel RAM | nVidia GTX660
4x 4TB Seagate NAS HDD (Btrfs raid5) | 2x 120GB Samsung 850 EVO SSD (Btrfs raid1)
Last edited by BlueFusion on Sun Apr 20, 2014 1:15 am; edited 1 time in total |
|
Back to top |
|
 |
Chiitoo Administrator


Joined: 28 Feb 2010 Posts: 2223 Location: Here and Away Again
|
Posted: Sun Apr 20, 2014 12:07 am Post subject: ><)))°€ |
|
|
Teegrins, BlueFusion!
I'm not entirely sure if this can be of any help, as I haven't played with these particular configurations much, but on a laptop where I have static-dev, I have the following in the xorg.conf to have it use the synaptics driver (instead of the generic mouse driver, which I believe it used otherwise):
Code: | Section "InputDevice"
Identifier "Tapper"
Driver "synaptics"
EndSection |
I notice that you have InputClass section instead of InputDevice. I don't entirely understand their difference between them at this time, but looking at the manual page for synaptics, it does speak of InputDevice section, which leads me into thinking if that's something to think about.
It does mention in the manual that the class-section(s) is/are used for when a device are automagically added, in which case I could imagine it not being used. Alas, as I mentioned, I've not really played with these sections before, but I did try changing mine into 'class' just now, and synaptics wasn't used. Again though, not sure if my static-dev set-up could make any difference there. ^^;
I hope this can be of at least some help!
I know I learned a bit more. _________________ Kind regards,
Chiitoo.
You might remember me from Gentoo projects such as Forums, LXQt, Qt, and Wine. |
|
Back to top |
|
 |
BlueFusion Guru

Joined: 08 Mar 2006 Posts: 371
|
Posted: Sun Apr 20, 2014 12:47 am Post subject: |
|
|
Thank you very much for the guidance, Chiitoo!
I did try changing it to InputDevice (and commenting out the Match* lines as they were not compatible).
I can confirm that Xorg is reading the configuration file, as it does give errors when it has invalid syntax, but I am still unable to get Synaptics driver to be loaded instead of evdev.
Here's what I've done so far.
* Create /etc/X11/xorg.conf.d/50-synaptics.conf with above, and other various configurations from around the internet.
* Re-emerged xf86-input-synaptics driver
I confirmed that Synaptics support is in the kernel:
Quote: | CONFIG_MOUSE_PS2_SYNAPTICS=y
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_USB is not set |
Here's the part of the log that may be useful to a better trained eye:
Quote: | [ 89601.485] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event11)
[ 89601.485] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
[ 89601.485] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse'
[ 89601.485] (**) PS/2 Generic Mouse: always reports core events
[ 89601.485] (**) evdev: PS/2 Generic Mouse: Device: "/dev/input/event11"
[ 89601.485] (--) evdev: PS/2 Generic Mouse: Vendor 0x2 Product 0x1
[ 89601.485] (--) evdev: PS/2 Generic Mouse: Found 3 mouse buttons
[ 89601.485] (--) evdev: PS/2 Generic Mouse: Found relative axes
[ 89601.485] (--) evdev: PS/2 Generic Mouse: Found x and y relative axes
[ 89601.485] (II) evdev: PS/2 Generic Mouse: Configuring as mouse
[ 89601.485] (**) evdev: PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
[ 89601.485] (**) evdev: PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 89601.485] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input18/event11"
[ 89601.485] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 11)
[ 89601.485] (II) evdev: PS/2 Generic Mouse: initialized for relative axes.
[ 89601.485] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
[ 89601.485] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
[ 89601.485] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
[ 89601.485] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
[ 89601.485] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse0)
[ 89601.485] (II) No input driver specified, ignoring this device.
[ 89601.485] (II) This device may have been added with another device file. |
I should also note that there is no other mention of synaptics in any way in the log file (i.e. driver not able to be loaded). _________________ i7-940 2.93Ghz | ASUS P6T Deluxe (v.1) | 24GB Triple Channel RAM | nVidia GTX660
4x 4TB Seagate NAS HDD (Btrfs raid5) | 2x 120GB Samsung 850 EVO SSD (Btrfs raid1) |
|
Back to top |
|
 |
BlueFusion Guru

Joined: 08 Mar 2006 Posts: 371
|
Posted: Sun Apr 20, 2014 12:56 am Post subject: |
|
|
Additionally, here's a bit more information:
cat /proc/bus/input/devices
Quote: | I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input18
U: Uniq=
H: Handlers=mouse0 event11
B: PROP=0
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3 |
_________________ i7-940 2.93Ghz | ASUS P6T Deluxe (v.1) | 24GB Triple Channel RAM | nVidia GTX660
4x 4TB Seagate NAS HDD (Btrfs raid5) | 2x 120GB Samsung 850 EVO SSD (Btrfs raid1) |
|
Back to top |
|
 |
BlueFusion Guru

Joined: 08 Mar 2006 Posts: 371
|
Posted: Sun Apr 20, 2014 1:15 am Post subject: |
|
|
As usual, not long after posting my problem, I find a solution!
As you can see in the last post I made, the kernel was not identifying the touchpad as a touchpad.
It turns out that it is an Elantech touchpad which therefore needed a special PS/2 option set in the kernel. I set that and it works as expected now!
For anyone else who runs into this problem, the kernel setting is:
MOUSE_PS2_ELANTECH _________________ i7-940 2.93Ghz | ASUS P6T Deluxe (v.1) | 24GB Triple Channel RAM | nVidia GTX660
4x 4TB Seagate NAS HDD (Btrfs raid5) | 2x 120GB Samsung 850 EVO SSD (Btrfs raid1) |
|
Back to top |
|
 |
Chiitoo Administrator


Joined: 28 Feb 2010 Posts: 2223 Location: Here and Away Again
|
Posted: Sun Apr 20, 2014 1:29 am Post subject: |
|
|
Good to see!
I didn't have much hope for what I was suggesting since it does seem the class should work if auto-detection works (as far as I understand), and that's not the case in my set-up indeed. A poke in the dark, if you will.
While the only other path I could think of would have been to check the logs and kernel, I certainly wasn't sure what you'd need.
So I thank you!
I should remember this next time. ^^ _________________ Kind regards,
Chiitoo.
You might remember me from Gentoo projects such as Forums, LXQt, Qt, and Wine. |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|