Gentoo 历程（2）配置触摸板，低级错误导致“SynPS/2 Synaptics TouchPad: Synaptics driver unable to detect protoc”

最新推荐文章于 2025-06-30 14:03:05 发布
原创 最新推荐文章于 2025-06-30 14:03:05 发布 · 2.8k 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#文档 #input #keyboard #parallel #events #layout

本文记录了解决Gentoo系统中SynPS/2 Synaptics TouchPad驱动无法识别的问题。在尝试启用触摸板时遇到困难，通过修正xorg.conf配置文件中的错误并遵循详细的Gentoo文档，最终成功启用并获得良好手感的触摸板。使用synclient工具进行参数调整，简化了触摸板功能，满足日常使用需求。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

    我的xorg配置文件是用nvidia-xconfig自动生成的，本人比较喜欢用鼠标，为了防止触摸板干扰打字，所以一直禁用psmouse模块，今天鼠标没电了，想启动触摸板，没想到居然不能用……经过一番折腾，终于被一个很低级的失误给拦住了……


    Gentoo的文档真不是盖的，太详细了，根据这篇文档配置的话基本不会出问题，注意，是基本……

    在文档的X.org这一节，提到了要在xorg.conf中添加这一句：

InputDevice "TouchPad" "CorePointer"
同时，文档中还提到“If you use a mouse in parallel, you should only have one "CorePointer". For the other device put "SendCoreEvents". ”，如果你使用并口鼠标，你只能有一个CorePointer，另一个应该设置为SendCoreEvents。看到这一句的时候，或许是开小差了吧，想了想我的usb鼠标是universal serial bus，通用串行总线，显然不是并口，于是很闹残的在xorg.conf里直接添上了这个corepointer，变成了这样：

最低0.47元/天 解锁文章

200万优质内容无限畅学
Gentoo中关于笔记本触控板(Synaptics)的配置
beijing2008lm的专栏
02-09 3013
已开通新的博客，后续文字都会发到新博客 http://www.0xfree.top --- 这一篇主要介绍笔记本上的触摸板Synaptics的相关的配置，先来了解一点背景知识 背景知识： 1.在linux上，桌面只不过是一个基于内核之上的软件，可以自己添加，删除或者定制。在众多软件发展之中，为了定义统一的基于图形化linux的标准，便出现了X window系统，通常被缩写为X11或者X...
gentoo xfce桌面fn+f9关闭触摸板
u011500307的专栏
04-24 1863
在gentoo中，安装了xfce桌面，fn的
gentoo 关闭笔记本触摸板
qinshang007的专栏
12-22 754
许多笔记本touchpad设计不合理，触摸板很容易被碰到，影响正常的编辑。那能不能在在需要的时候打开触摸板，不需要的时候关闭它呢？答案是可以的。 首先修改xorg.conf文件 [root@xmpan ~]#vi /etc/X11/xorg.conf 找到synaptic这一段,添加两个东西，首先是共享内存控制，一个是初始化触摸板的状态。 Section “InputDevice”
(2025年7月1日)archlinux安装中文输入法fcitx5
最新发布
Demo
06-30 1130
2025年7月 archlinux 安装中文输入法fcit5
gentoo蓝牙，触控板，wifi
billvsme的专栏
05-02 1912
一：蓝牙 处了内核要选好，可能还要安装 emerge -a bluez emerge --ask net-wireless/blueman  链接蓝牙要用 hciconfig， 具体是先hcitool scan搜索 找到MAD地址 再 rfcomm bind /dev/tty30 6C:5D:63:20:59:05 cat >/dev
解决Ubuntu下的synaptics触摸板问题
XiaJing20060721的专栏
08-15 6221
   安装Ubuntu 9.10后，触摸板就没有反应。首先要确定触摸板的型号，因为有多个系统，很容易得到在xp下显示的型号为“Synaptics TouchPad V5.10 on PS/2 Port"。针对Synaptics和Ubuntu然后 google，这里Synaptics是触摸板厂家的名称，与synaptic package manager(spm)完全不是一回事。首先安装了gpointing-device-settings, (spm说这可以替代gsynaptics配置软件，“which is
Gentoo Linux 配置i2C触摸板
02-07
配置Gentoo Linux系统中的I2C触摸板涉及几个步骤，包括确保内核支持、安装必要的软件包以及正确的配置文件设置。 ### 内核配置 首先需要确认Linux内核已经启用了对I2C的支持及相关的驱动模块： 1. **启用 I2C ...
(.venv) root@lujh:/xhs-toolkit# /usr/bin/google-chrome [5740:5761:0625/221740.246042:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.248003:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.249531:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.250569:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.370044:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.415397:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5758:0625/221740.478293:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.523936:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.524261:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.648013:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5740:0625/221740.648556:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5761:0625/221740.649404:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.651613:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5740:0625/221740.666140:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5781:0625/221740.667402:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.691384:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5740:0625/221740.694212:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5777:0625/221740.695388:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.708898:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5778:0625/221740.709739:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.717343:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5778:0625/221740.718130:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.725801:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: WARNING: All log messages before absl::InitializeLog() is called are written to STDERR I0000 00:00:1750861062.663657 5758 voice_transcription.cc:58] Registering VoiceTranscriptionCapability [5740:5740:0625/221806.050232:ERROR:chrome/browser/ui/webui/new_tab_page/new_tab_page_handler.cc:1353] NewTabPage loaded into a non-browser-tab context
06-26
具体操作：步骤1：检查D-Bus服务状态在终端中运行：```bashsystemctlstatusdbus```如果服务没有运行，则启动它：```bashsudosystemctlstartdbus```步骤2：检查Chrome的D-Bus服务名称可以使用`dbus-send`或`d-feet`等...
gentoo-kernel-guide：在Gentoo Linux上配置和管理内核的更好方法
02-03
《Gentoo Linux上的内核配置与管理指南》是一份深度探讨如何在Gentoo Linux系统中优化和管理内核的资源。Gentoo Linux以其源代码编译的特性著称，用户可以自定义内核配置，从而实现高度定制化的系统。这份指南将帮助...
gentoo-portage-config：Gentoo Portage配置文件（尝试构建一个完全正常工作的LLVM + musl + Linux桌面）
02-16
在Linux世界中，Gentoo是一个著名的源代码型Linux发行版，它以其高度自定义性和灵活性而闻名。Portage是Gentoo的核心包管理器，它使用Ebuild脚本来编译和安装软件。这个“gentoo-portage-config”项目显然是针对...
Gentoo 安装日记 14 （配置内核 ：设备驱动）
weixin_30279671的博客
04-02 260
接：http://nvd11.blog.163.com/blog/static/200018312201272571544981/摘自 鸟哥的私房菜:進入『Device Drivers』這個是所有硬體裝置的驅動程式庫！哇！光是看到裡面這麼多內容，鳥哥頭都昏了～ 不過，為了你自己的主機好，建議你還是得要一個項目一個項目的去挑選挑選才行～ 這裡面的資料就與你主機的硬體有絕對的關係了！ 在...
触控板失灵的解决方法（synaptics驱动）
热门推荐
xioy98的博客
09-29 1万+
现象： 开机鼠标消失，触摸板失灵。 步骤： 1.到电脑官网下载原装触摸板驱动程序，我的为thinkpad，安装，上面显示这个驱动已安装。 2.下载联想驱动管理安装，安装失败。 3.下载360驱动卸载原驱动，在安装官网驱动，显示成功，重启后还是失灵。 4.找到触控板synaptics的原厂驱动，下载安装，重启后成功。 总结： 触控板的驱动有两个，一个是板子连接的驱动，一个是系统的驱动。通用的在于硬件坏的可能性很低，方向在于软件。 ...
联想装系统后触摸板无法设置双指手势
yudelian的博客
01-19 1102
经查询，需要去联想网站搜索驱动，下载了一个“Lenovo联想驱动管理”，更新了下触摸板驱动，我的一个电脑是联想小新air13，装Windows10系统后，没有找到设置触摸板手势的地方。就有了装置设定值这个选项，然后好像三指操作可以，但是而指头操作不行。然后win+R，输入regedit进行注册表。也没有“装置设定值”这个选项。
联想触摸板问题解决（多指操作失效）
嘟小嘴
09-07 1424
触摸板多指失效
解决kde 桌面环境，触摸板手指轻触无法使用的问题
qq_42731401的博客
04-11 3140
问题：触摸板设置中存在手指动作但无法选中。 sudo apt-get install xserver-xorg-input-synaptics 安装驱动 sudo apt-get install kde-config-touchpad 安装配置工具 安装完成后重启，可以在系统设置的触摸板中重新设置触摸动作 ...
tiny4412 Linux驱动Input子系统
weixin_44317448的博客
06-15 318
输入设备（如鼠标,键盘,触摸屏,拨码开关,按键,麦克风,游戏摇杆,游戏手柄等）是典型的字符设备。Linux为了方便统一管理这些设备,然后设计了输入子系统，在Linux中,输入子系统的驱动节点都是有固定的位置的: 在新内核中: /dev/input/event0 /dev/input/event1 ... /dev/input/mouse0 /dev/input/mouse1 ....
linux input节点,linux 下input/mouse 节点
weixin_39845825的博客
05-15 494
linux 下/dev/input/mouse* 节我知道一直是由mouse_handl也就是原代码/driver/input/mousedev.c生成的，但有时候有，有时候没有，今天细细研究了一下终于明了其中原由下面的驱动源代码是amimouse.c更改的#include #include #include #include #include #include #include #include...
linux 下input/mouse 节点
weed_hz的专栏
05-27 4850
linux 下/dev/input/mouse* 节我知道一直是由mouse_handl也就是原代码/driver/input/mousedev.c生成的，但有时候有，有时候没有，今天细细研究了一下终于明了其中原由下面的驱动源代码是amimouse.c更改的 #include #include #include #include #include #include #include
mouse鼠标命令
本人喜欢编程（c/c++/嵌入式/单片机硬件制作）、听音乐、偶尔看电影、看书、爱研究、有好奇心
11-09 425
mouse鼠标Linux命令
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值