[SOLVED] Mageia x86-64 GNOME install on Acer Aspire One 725.

[globetrotterdk]

No luck, the touchpad is still AWOL and interestingly, when I try pressing "Fn - F7" the touchpad system symbol does not show that the touchpad is first "off" and then "on" or vice versa, but only shows "off". I have tried both placing the command (in the Mageia Control Center) after "quiet" in the boot sequence and at the very end after "resume=UUID=1x1x1x..." No change in behavior. I ran

Code: Select all

$ dmesg

but am none the wiser as to what is going on.

[martinw]

Unfortunately there seem to be a lot of different mechanisms for enabling/disabling the touchpad. Finding out which one is broken in your case is going to take a bit of detective work.

First, can you install the xinput package, and then in a terminal (as a normal user) type

Code: Select all

xinput --list


You should get something like this:

Code: Select all

% xinput --list
⎡ Virtual core pointer                       id=2   [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                 id=4   [slave  pointer  (2)]
⎜   ↳ PS/2 Generic Mouse                         id=13   [slave  pointer  (2)]
⎜   ↳ Logitech Optical USB Mouse                 id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard                      id=3   [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                id=5   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard               id=12   [slave  keyboard (3)]


Because I've set psmouse.proto=imps (to match what you have done), the touchpad is being treated as a PS/2 generic mouse (id=13) - the other pointer device is an external USB mouse I've got plugged in. If you now type

Code: Select all

xinput list-props 13


replacing 13 with the id number you see on your system, you should get a number of lines of information, starting with

Code: Select all

% xinput list-props 13
Device 'PS/2 Generic Mouse':
   Device Enabled (144):   1


If you instead see Device Enabled set to 0, try typing

Code: Select all

xinput set-prop 13 "Device Enabled" 1


(again replacing 13 with the correct id number). I found I also had to toggle the Fn key that enables/disables the touchpad after doing this.

Next, I'm assuming from the title of this thread that you are using the GNOME desktop. Does the touchpad work at the login screen before you log in? If so, could you try another desktop environment (e.g. LXDE) to see if the problem is also present there. Also try creating a new user, in case it is something in your user settings.

One more thought - do you also have a USB mouse plugged in? I believe some laptops will automatically disable the touchpad if a USB mouse is detected.

[globetrotterdk]

OK, there is no difference with regards to the trackpad performance, between the login, a guest user account, or my default account. As far as I can see, everything looks fine with the output from xinput: Here it is:

Code: Select all

$ xinput --list
⎡ Virtual core pointer                       id=2   [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                 id=4   [slave  pointer  (2)]
⎜   ↳ USB Optical Mouse                          id=10   [slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad                   id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard                      id=3   [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                id=5   [slave  keyboard (3)]
    ↳ Power Button                               id=6   [slave  keyboard (3)]
    ↳ Video Bus                                  id=7   [slave  keyboard (3)]
    ↳ Power Button                               id=8   [slave  keyboard (3)]
    ↳ Sleep Button                               id=9   [slave  keyboard (3)]
    ↳ HD WebCam                                  id=11   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard               id=12   [slave  keyboard (3)]
    ↳ Acer WMI hotkeys                           id=14   [slave  keyboard (3)]

Code: Select all

$ xinput list-props 13
Device 'ETPS/2 Elantech Touchpad':
   Device Enabled (148):   1
   Coordinate Transformation Matrix (150):   1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
   Device Accel Profile (271):   1
   Device Accel Constant Deceleration (272):   2.500000
   Device Accel Adaptive Deceleration (273):   1.000000
   Device Accel Velocity Scaling (274):   12.500000
   Synaptics Edges (292):   97, 2339, 56, 988
   Synaptics Finger (293):   25, 30, 256
   Synaptics Tap Time (294):   180
   Synaptics Tap Move (295):   116
   Synaptics Tap Durations (296):   180, 180, 100
   Synaptics Tap FastTap (297):   0
   Synaptics Middle Button Timeout (298):   75
   Synaptics Two-Finger Pressure (299):   282
   Synaptics Two-Finger Width (300):   7
   Synaptics Scrolling Distance (301):   53, 53
   Synaptics Edge Scrolling (302):   1, 0, 0
   Synaptics Two-Finger Scrolling (303):   0, 0
   Synaptics Move Speed (304):   1.000000, 1.750000, 0.075472, 40.000000
   Synaptics Edge Motion Pressure (305):   30, 160
   Synaptics Edge Motion Speed (306):   1, 212
   Synaptics Edge Motion Always (307):   0
   Synaptics Off (308):   0
   Synaptics Locked Drags (309):   0
   Synaptics Locked Drags Timeout (310):   5000
   Synaptics Tap Action (311):   0, 0, 0, 0, 0, 0, 0
   Synaptics Click Action (312):   1, 1, 1
   Synaptics Circular Scrolling (313):   0
   Synaptics Circular Scrolling Distance (314):   0.100000
   Synaptics Circular Scrolling Trigger (315):   0
   Synaptics Circular Pad (316):   0
   Synaptics Palm Detection (317):   0
   Synaptics Palm Dimensions (318):   10, 200
   Synaptics Coasting Speed (319):   20.000000, 50.000000
   Synaptics Pressure Motion (320):   30, 160
   Synaptics Pressure Motion Factor (321):   1.000000, 1.000000
   Synaptics Grab Event Device (322):   1
   Synaptics Gestures (323):   1
   Synaptics Capabilities (324):   1, 0, 1, 1, 1, 1, 1
   Synaptics Pad Resolution (325):   1, 1
   Synaptics Area (326):   0, 0, 0, 0
   Synaptics Noise Cancellation (327):   13, 13
   Device Product ID (267):   2, 14
   Device Node (268):   "/dev/input/event1"

[globetrotterdk]

Hmmm. I just discovered that what I thought was the touchpad indicator on the computer (not the os "on-off" indicator) actually is the mains and battery charging indicator. Acer needs to do a better job with their icons.

[martinw]

Did you remove the psmouse.proto=imps from your kernel boot options? If not, the output from 'xinput --list' indicates it's not been recognised.

The output from 'xinput list-props' shows that the touchpad is enabled in two of the places it could be disabled. I think that just leaves whatever mechanism is used by the Fn key. I've not managed to track down what that is - but as a stab in the dark, could you try rebooting with the kernel option "acpi=off" to see if that makes a difference.

Could you also try the other things I suggested (rebooting without the USB mouse attached, using a different desktop environment).

[globetrotterdk]

Weird. The touchpad started working after I installed Openbox. Now it works in both Openbox and Gnome. Is there a way to purge Openbox from the command line to see if the touchpad will continue to work?

Edit: There is one continuing issue, which is that I have to press Fn - F7 at login with every startup to get the touchpad to work.

[martinw]

Weird. The touchpad started working after I installed Openbox. Now it works in both Openbox and Gnome. Is there a way to purge Openbox from the command line to see if the touchpad will continue to work?

As root,

Code: Select all

urpme openbox

although I would be inclined to leave well alone now it's working!

[globetrotterdk]

Thanks. I thought I would mention that suspend definitely doesn't work as intended, but maybe I should start a separate thread?

[martinw]

Yes, I would recommend starting a new thread specifically about the suspend problem - more chance of attracting the attention of someone with more knowledge than me in that area.

[doktor5000]

So please mark this thread as [SOLVED].