Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Apr 2018 21:51:18 +0200
From:      Polytropon <freebsd@edvax.de>
To:        Anton Shterenlikht <as@cmplx.uk>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: touchpad mouse not working
Message-ID:  <20180422215118.7ed86c89.freebsd@edvax.de>
In-Reply-To: <20180422183200.GA42552@jail0199.vps.exonetric.net>
References:  <201804152038.w3FKcI5l097823@jail0199.vps.exonetric.net> <20180416002136.ea89f2ac.freebsd@edvax.de> <20180420190251.GA65091@jail0199.vps.exonetric.net> <20180422111659.bb8229e5.freebsd@edvax.de> <20180422183200.GA42552@jail0199.vps.exonetric.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 22 Apr 2018 18:32:00 +0000, Anton Shterenlikht wrote:
> On Sun, Apr 22, 2018 at 11:16:59AM +0200, Polytropon wrote:
> > 
> > > This is my pciconf -lv.
> > > Does it contain any hints?
> > 
> > No. You should check:
> > 
> > 	# dmesg | grep psm
> 
> empty
> 
> > 
> > and
> > 
> > 	# dmesg | grep ums
> 
> empty, until I plug in an external usb mouse

As expected: The internal touch device is _not_ accessible
by the OS in any way.



> > By the way, is there a /boot/kernel/acpi_<something>.ko
> > related to your hardware? If yes, try to load it - it might
> > enable "hidden hardware" that won't show up normally.
> 
> root@z:~ # ls /boot/kernel/acpi*ko
> /boot/kernel/acpi_asus.ko       /boot/kernel/acpi_hp.ko         /boot/kernel/acpi_toshiba.ko
> /boot/kernel/acpi_asus_wmi.ko   /boot/kernel/acpi_ibm.ko        /boot/kernel/acpi_video.ko
> /boot/kernel/acpi_dock.ko       /boot/kernel/acpi_panasonic.ko  /boot/kernel/acpi_wmi.ko
> /boot/kernel/acpi_fujitsu.ko    /boot/kernel/acpi_sony.ko
> 
> The laptop is DEll precision 3250,
> so not sure if any of these modules
> apply. Perhaps acpi_wmi?

You can try to load them one by one, and then check the
console messages (or dmesg output) if any new devices
appear. There is nothing specific that says "Dell", but
acpi_wmi doesn't sound convincing:

	The acpi_wmi driver provides an interface for
	vendor specific WMI implementations (e.g. HP
	and Acer laptops).  It creates /dev/wmistat,
	which can be read to get information about
	GUIDs found in the system.

Maybe still worth a try.



> > Also check if you have a "Synaptics Touchpad":
> > 
> > https://wiki.freebsd.org/SynapticsTouchpad
> > 
> > https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/x.html#idp59957608
> > 
> > https://forums.freebsd.org/threads/how-to-use-synaptics-driver-for-better-touchpad-features.54872/
> > 
> > Again, this assumes that some device entry is already present
> > for the touchpad (usually psm).
> 
> Yes, I've looked at these, but as you say,
> this is just making sure the touchpad device
> can be used with some extra capabilities.
> But I cannot even get the basics working.

It's quite strange that you have a BIOS setting that
doesn't seem to do anything...




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180422215118.7ed86c89.freebsd>