Elantech touchpad improperly recognized as “ImPS/2 Logitech Wheel Mouse”

Good thanx, but I'm still not sure what the leds_asus_touchpad device is exactly. Maybe it's not the main device but some sort of ghost helper device.
It may be better to keep trying to configure the ImPS/2. If you do try that again you could check "synclient -l" and

Code:

---

xinput list-props 'ImPS/2 Logitech Wheel Mouse'

---

and make sure the touchpadoff=0 and the xinput deviceenabled=1

Code:

---

synclient touchpadoff=0
xinput set-int-prop 'ImPS/2 Logitech Wheel Mouse' 'Device Enabled' 8 1

---

and if those don't work then try modprobe using the verbose option so you can see what's happening:

Code:

---

sudo modprobe -v psmouse

---

and if you could lshal the device while it was loaded by hal you could see if hal was doing its job.

Code:

---

~$ xinput list-props 'ImPS/2 Logitech Wheel Mouse'
Device 'ImPS/2 Logitech Wheel Mouse':
    Device Enabled (93):    1
    Evdev Reopen Attempts (229):    10
    Evdev Axis Inversion (230):    0, 0
    Evdev Axis Calibration (231):   
    Evdev Axes Swap (232):    0
    Evdev Middle Button Emulation (233):    1
    Evdev Middle Button Timeout (234):    255
    Evdev Wheel Emulation (235):    1
    Evdev Wheel Emulation Axes (236):    0, 0, 4, 5
    Evdev Wheel Emulation Inertia (237):    10
    Evdev Wheel Emulation Timeout (238):    200
    Evdev Wheel Emulation Button (239):    4
    Evdev Drag Lock Buttons (240):    0

---

ive NEVER had synclient working or installed properly..

Code:

---

~$ synclient touchpadoff=0
Couldn't find synaptics properties. No synaptics driver loaded?

---

modprobe -v psmouse doesnt list anything..

Quote:

---

modprobe -v psmouse doesnt list anything..

---

Thats good it means it's already loaded.
Can you run:

Code:

---

lshal -u '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port_logicaldev_input'

---

while the touchpad is loaded through hal fdi? You could try unloading psmouse then loading it again.

Code:

---

modprobe -rv psmouse
modprobe -v psmouse

---

Code:

---

~$ lshal -u '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port_logicaldev_input'
udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port_logicaldev_input'
  info.capabilities = {'input', 'input.mouse'} (string list)
  info.category = 'input'  (string)
  info.parent = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port'  (string)
  info.product = 'ImPS/2 Logitech Wheel Mouse'  (string)
  info.subsystem = 'input'  (string)
  info.udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port_logicaldev_input'  (string)
  input.device = '/dev/input/event9'  (string)
  input.originating_device = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port'  (string)
  input.product = 'ImPS/2 Logitech Wheel Mouse'  (string)
  input.x11_driver = 'evdev'  (string)
  input.x11_options.SHMConfig = 'on'  (string)
  linux.device_file = '/dev/input/event9'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'input'  (string)
  linux.sysfs_path = '/sys/devices/platform/i8042/serio4/input/input9/event9'  (string)

---

How can i ensure its loaded via hal ?

and to make this easier on you, i can pass you my ICQ or MSN.. or im on #ubuntu @ irc.freenode.org (user name Quan-Time) if you wanna jump on irc.. But im more than happy with this forum thread, might help others later in the future with the same problem.

If the hal configuration was working correctly the following lines of the output would be changed as such:

Code:

---

info.capabilities = {'input', 'input.mouse', 'input.touchpad'} (string list)
input.x11_driver = synaptics

---

So there is probably something interfering with the hal policy being able to make the changes.
I would go on ICQ but I'm not set up for it right now and I have to go to bed soon anyway.

Quote:

---

How can i ensure its loaded via hal ?

---

The best way would probably be to save the whole xorg.conf as a backup:

Code:

---

sudo cp /etc/X11/xorg.conf /etc/X11/xorg.backup

---

then delete all the references to synaptics or ImPS/2 and then reboot to load the hal policy and then check lshal and if the changes are still not there then maybe it's not possible. Then the xorg.backup could be renamed again to xorg.conf.

ah ok.. so what options do i have ? and i guess ill hear from you tomorrow (i hope). Not quite sure where to go from here. This is all new to me. (touchpad config)

I would try this and make sure to have this fdi policy uncommented

Code:

---

<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
  <device>
    <match key="info.product" contains="ImPS/2 Logitech Wheel Mouse">
      <merge key="input.x11_options.SHMConfig" type="string">on</merge>
<merge key="input.x11_driver" type="string">synaptics</merge>
    </match>
  </device>
</deviceinfo>

---

and save the whole xorg.conf as a backup:

Code:

---

sudo cp /etc/X11/xorg.conf /etc/X11/xorg.backup

---

then delete all the references to synaptics or ImPS/2 in xorg.conf and then reboot to load the hal policy and then check lshal

Code:

---

lshal -u '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port_logicaldev_input'

---

and if the changes input.touchpad capability and synatpics drvier are still not there then maybe it's not possible. Then the xorg.backup could be renamed again to xorg.conf.

kk ill try that and post results tomorrow.. i gotta step out shortly. Cheers again !

I just came across this link:
http://wiki.debian.org/DebianEeePC/HowTo/ElantechTouchpad
It looks like It's necessary to patch the kernel to make it work. That sounds like an adventure. Other than that it looks like the only thing that will work is changing a few xinput settings.
The middle button could be disabled by:

Code:

---

xinput set-int-prop 'ImPS/2 Logitech Wheel Mouse' 'Evdev Middle Button Emulation' 8 0

---

I just upgraded to 10.4 and it was not fixed.
here are the 2 bug reports, please go there and add a comment with your machine etc.

https://bugs.launchpad.net/ubuntu/ha...ev/+bug/123775

https://bugs.launchpad.net/ubuntu/+s...ux/+bug/512192

I also post it on kernel-team mailing list:
https://lists.ubuntu.com/archives/ke...il/009826.html

go there and reply, tell the developers it's a real issue.

Also go to #ubuntu-kernel on irc and ask about it.