> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/ask/flat/chapter-11-multimedia-and-external-devices/di-11.4-jie-ren-ji-shu-ru-she-bei.md). # 11.4 Human Input Devices FreeBSD natively supports touchpads with I²C and USB interfaces. This section describes how to disable a touchpad. ## Touchpad ### Disabling the Touchpad To disable the touchpad, first find the device identifier of the touchpad in the X Window system. The device name may differ across systems, but touchpad device names typically contain `Touchpad` or a similar identifier: ```sh $ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Windows pointer id=6 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Windows keyboard id=7 [slave keyboard (3)] ``` After finding the device ID corresponding to the touchpad (6 in the example), disable it as follows (where `1` means enable, `0` means disable): ```sh $ xinput set-prop 6 "Device Enabled" 0 # Disable input device with ID 6 ``` #### References * fygar256. FreeBSDタッチパッドをoffにする\[EB/OL]. Qiita, (2023-03-16)\[2026-03-25]. . A detailed introduction to disabling the FreeBSD touchpad using the xinput tool, providing practical command examples. ### Apple Magic Trackpad The Apple Magic Trackpad 2 provides a precise operating experience based on Force Touch pressure-sensing technology. On FreeBSD, when the Apple Magic Trackpad is connected via USB, modern versions (15.0 and above) automatically recognize and support it through the new HID driver stack (usbhid/hms), without the need to load additional kernel modules. This trackpad needs to be used with the `libinput` input library, and works under both X Window (via the xf86-input-libinput driver) and Wayland desktop environments. Bluetooth wireless usage is currently not supported. ## Appendix: Resolving Keyboard and Mouse Driver Issues in 15.0 and Later Versions If USB keyboards, mice, or touchpads worked properly in versions below 15.0 but experienced driver failures after updating the system to 15.0, refer to the following solution: Add the following line to the system boot configuration file **/boot/loader.conf.local**: ```ini hw.usb.usbhid.enable="0" ``` This configuration disables the usbhid driver stack to fall back to the legacy drivers, then restart the system. Problem analysis: The ums (USB Mouse) and ukbd (USB Keyboard) drivers are compiled into the kernel by default in the generic kernel for most architectures, and also exist as loadable modules (e.g., `ukbd_load="YES"`). After version 15.0, the usbhid driver became the default choice, with higher priority than the traditional ums and ukbd drivers. The usbhid driver first appeared in FreeBSD 15.0. [FreeBSD Code Review D45658](https://reviews.freebsd.org/D45658) added usbhid, hidbus, and hkbd to the GENERIC kernel configuration for all architectures, and added hms to the arm and powerpc architecture configurations, making the new HID stack driver available by default; the change that set the default value of `hw.usb.usbhid.enable` from 0 to 1 was proposed by [D45659](https://reviews.freebsd.org/D45659). usbhid has been the system default enabled driver since 15.0. Given that the project is gradually migrating to the new HID driver stack (hkbd/hms), this issue still requires further investigation into its root cause, and a bug report should be submitted to the FreeBSD project. For details, refer to the relevant report in FreeBSD Journal issue 2021/0708. ## Appendix: Fn Key Settings * David Schlachter. Adjusting acpi\_video brightness increments on FreeBSD\[EB/OL]. (2020-03-12)\[2026-03-25]. . Introduces specific methods for adjusting ACPI video brightness increments on FreeBSD, applicable to laptops such as ThinkPad. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://book.bsdcn.org/ask/flat/chapter-11-multimedia-and-external-devices/di-11.4-jie-ren-ji-shu-ru-she-bei.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.