Elantech Touchpad support?

Dave MacFarlane driusan at gmail.com
Tue Jul 19 16:28:09 PDT 2016

As far as I know, most trackpads are over the PS/2 "port", and boot up
emulating a PS/2 mouse then switch to a richer packet format which
includes the multitouch/pressure/etc information after receiving a
magic command sequence.

I've attached dmesg from both OpenBSD and Dragonfly. Note that pms0 is
identified as "Elantech Clickpad, version 4, firmware 0x38af0a" in the
OpenBSD version but just "Generic PS/2 mouse" under DFlyBSD.

(I'm not sure if it's the kernel or X server's job to negotiate the
protocol, but even if it's X then I don't think the right
configuration is getting loaded since it's being misreported as a
generic mouse.)

On Sun, Jul 17, 2016 at 5:15 PM, Matthew Dillon <dillon at backplane.com> wrote:
> I don't know re: the trackpad.  Is it a USB device?  What physical interface
> is OpenBSD detecting it as using?
> -Matt
> On Sat, Jul 16, 2016 at 12:18 PM, Dave MacFarlane <driusan at gmail.com> wrote:
>> Hello,
>> I've been meaning to try DragonflyBSD for a while, and I've finally
>> gotten around to figuring out how to get it to multiboot with UEFI on
>> my laptop (an Asus TransformerBook TP300L). The only issue I'm having
>> is that my trackpad is only being detected as a Generic PS/2 mouse and
>> doesn't seem to have any synaptics support, even after installing
>> xf86-input-synaptics.  Is there any support for elantech firmware v4
>> trackpads (as OpenBSD detects it..)? (Actually, the touchscreen also
>> isn't working, but that's less surprising and not much of an issue for
>> me..)
>> To get it working with UEFI, I basically followed the manual install
>> instructions with this caveat:
>> http://lists.dragonflybsd.org/pipermail/users/2016-July/270759.html
>> and then followed the rest of the manual install instructions in
>> /README, and used gpt create partitions for the other OSes I wanted
>> while I was at it. (The BIOS lets me hit escape and choose which one I
>> want at boot time..)
>> The only issue was that there's no fstab.example for hammer. This is
>> what my fstab ended up looking like in the end, for anyone trying to
>> follow a similar setup:
>> # $DragonFly: src/nrelease/root/etc/fstab.example,v 1.1 2003/12/01
>> 21:14:03 dillon Exp $
>> # Example fstab based on /README.
>> #
>> # Device Mountpoint FStype Options Dump Pass#
>> /dev/da0s2d / hammer rw 2 0
>> /dev/da0s1 /boot ufs rw 1 1
>> /dev/da0s2b none swap sw 0 0
>> /pfs/var /var null rw 2 0
>> /pfs/tmp /tmp null rw 2 0
>> /pfs/usr /usr null rw 2 0
>> /pfs/home /home null rw 2 0
>> /pfs/var.crash /var/crash null rw 2 0
>> /pfs/usr.obj /usr/obj null rw 2 0
>> proc /proc procfs rw 0 0
>> # example MFS remount (for a pristine MFS filesystem do not use -C)
>> #swap /mnt mfs rw,-C,-s=4000 0 0
>> - Dave

- Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.dfly
Type: application/octet-stream
Size: 9179 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20160719/c2f41eea/attachment-0018.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.openbsd
Type: application/octet-stream
Size: 8095 bytes
Desc: not available
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20160719/c2f41eea/attachment-0019.obj>

More information about the Users mailing list