From owner-freebsd-questions@freebsd.org Sun Apr 22 19:56:46 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74375FB9607 for ; Sun, 22 Apr 2018 19:56:46 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D003F69514 for ; Sun, 22 Apr 2018 19:56:45 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.45.149]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPA (Nemesis) id 0LzHnN-1eNzVf49OT-014UuV; Sun, 22 Apr 2018 21:51:19 +0200 Date: Sun, 22 Apr 2018 21:51:18 +0200 From: Polytropon To: Anton Shterenlikht 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> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:7KrHrdS1cttgatKUfQPgFm0goY9d250aGVArUHFAQm3CZXUn7kj b3OCUNjfmBAEBB1Y1WwgCrM4Sb7phFjw8qb+J8yQOVVnUUBcTJWWzX04eqzYvreG9w7DjYP GZ/zl3Lq/hIhfDCAGWiRCXSn+oEKx/cqrjTpr6gJpV5l6NXds3rnhrloNCfewZZ+HqZl2fS 4tuvdU3pQv0uw1LwPtGng== X-UI-Out-Filterresults: notjunk:1;V01:K0:Eo0vqiN9A0I=:qF24kFQ4KEQUcro6/Ye2NR FUqOe3QPAI3qUUpHYrAp2BmmmwLAVsA3G8PsuArM795xuaYBT4oZTbHE8Wa9enigEX1mHZc3M CsXEqgVubDH73McZb2M5zicnHIqGpHFL36ZqVh3VVf3YiFraty59pieorFrIyEYRhyObVfes7 az7i33TPZWtijqrUK23+kXRRN3WSX3qoWkuv3pkr9JA9q58GQly6n43KL8QERKxiXdhxsdd00 XddgeYor1NbAjL1fjFR+VzPlUp8vpOvrMdbcksCyHPOXjHXDU/HotEKXMQA6lN/FXvAvuUj6/ JMgdMeKuInqwFhZBLc3p3AvNMHkn4HWzY+mF6oE5iPIf8TR1cm4CVq2NnCihZQqn/2i+FaCkF akZ07/ymW7nzOsh0Hjr3Az8v2rx1Gfwtp7iylr7RiNhb1tfvBfEVG0nlNHPPb2fGlB18Y6fw9 vZ5bxnkvqv+OoRaks1K/TNrR//vAJ4RUQH7ZgbdJm/HFIkoYEcAZyxHlDfi0QGEhTP5WVNwjM vhpu8R2gvIM49Zt6BZJuXsgPyus2ZVEyO5U0FURm3g4OK3qXJAocJxkfoGU38piCyqIDBokrd BpFPN5HB1gs8TE/kQOPPLo1v7qH01/0Y96zzMjP6lxXTckRFaH/CNptd06DZfjRnRQrdI5WRl P8EgARLCrlIw7laj7NegYAfpKNtirQMuL/VlNnoCj+0M/0nLRA0rBm83PADRIXngqMgXDgfcJ +AyUvRQFG+iyOwmSbqWwtoPkilql/RrdupskUcgx/Y0mlFPlWh7nR9ctS2E= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Apr 2018 19:56:46 -0000 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_.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, ...