synaptics driver for Xorg not working in TC16 x64

[nick65go]

@Juanito:Many thanks! I was just ready to abandon and assemble my "personal TinyCore-CachyOS" from pieces.
It is Sunday here and my wife asks for domestic things (walk in the park, etc).
I will try ASAP your new drivers. It will take some time, because TC starts virgin with Xfvdev, then I need to clean up my customization onboot etc. I will provide my feed back here.

I am also interested in testing wayland +libinput. But until now I did not know how to setup it (what to be in onboot.lst), because all TC apps were centered on Xfdev/Xorg+ fltk/flwm; so no compositors, login managers, desktop managers.
I will be happy to test what you propose, maybe someone could try to write a basic "tutorial" in TC wiki  about this, to be wide available for all. Thanks.

[Juanito]

I am also interested in testing wayland +libinput. But until now I did not know how to setup it.

Just read the info file for weston and follow the instructions.

To make things easier, you could make a one line script something like:

Code: [Select]

cat weston.sh
#!/bin/sh
sudo -- seatd -g staff -n /run/seatd.sock & XDG_RUNTIME_DIR=/run/user/$(id -u) weston
Then, from a console prompt load weston and run the script. Weston includes a terminal applet similar to aterm and, as from CorePure64-16.x, the tinycore fltk applets will work without requiring xwayland.

I imagine you will need to create a weston.ini file to get the required functionality from your touchpad - there are plenty of example out there.

Note that with labwc, you can load labwc-config and it will setup a right-click menu with the various tinycore applets and any other extensions loaded.

[nick65go]

OK, slowly, step by step. My first priority is a full functional touch-pad in Xorg.
Is annoying to use an external mouse + external USB-wifi rtl8xxxu (because rtw89_8852be internal Wifi random works depending when firmware loads),
No news for now; I just setup a virgin/pristine TC16_x64 grub menu, clean all my personal configuration (mydata.gz) and have a new minimum onboot.lst to have a REPRODUCIBLE and automated test environment. 
NO tcz files were changed, no adds, no deletions, for now. All *.so have proper dependencies.

Code: [Select]

tc@box:~$ cetc@box:/etc/sysconfig/tcedir$ cat onboot.lst
firmware-rtlwifi.tcz
firmware-wlan.tcz
firmware-i915.tcz
aterm.tcz
wbar.tcz
flwm.tcz
graphics-6.12.11-tinycore64.tcz
Xorg-7.7-3d.tcz
xf86-input-synaptics.tcz
xf86-input-evdev.tcz
tc@box:/etc/sysconfig/tcedir$

Code: [Select]

tc@box:~$ ls -al /usr/local/share/X11/xorg.conf.d/
total 0
drwxr-xr-x    2 root     root           120 May 25 09:05 ./
drwxr-xr-x    6 root     root           200 May 25 09:05 ../
lrwxrwxrwx    1 root     root            74 May 25 15:51 10-evdev.conf -> /tmp/tcloop/xf86-input-evdev/usr/local/share/X11/xorg.conf.d/10-evdev.conf
lrwxrwxrwx    1 root     root            70 May 25 15:51 10-quirks.conf -> /tmp/tcloop/xorg-server/usr/local/share/X11/xorg.conf.d/10-quirks.conf
lrwxrwxrwx    1 root     root            80 May 25 15:51 40-libinput.conf -> /tmp/tcloop/xf86-input-libinput/usr/local/share/X11/xorg.conf.d/40-libinput.conf
lrwxrwxrwx    1 root     root            82 May 25 15:51 70-synaptics.conf -> /tmp/tcloop/xf86-input-synaptics/usr/local/share/X11/xorg.conf.d/70-synaptics.conf
tc@box:~$

Code: [Select]

tc@box:~$ ls -al /usr/local/lib/xorg/modules/input/
total 0
drwxr-xr-x    2 root     root           120 May 25 09:05 ./
drwxr-xr-x    5 root     root           260 May 25 09:05 ../
lrwxrwxrwx    1 root     root            74 May 25 15:51 evdev_drv.so -> /tmp/tcloop/xf86-input-evdev/usr/local/lib/xorg/modules/input/evdev_drv.so
lrwxrwxrwx    1 root     root            73 May 25 15:51 inputtest_drv.so -> /tmp/tcloop/xorg-server/usr/local/lib/xorg/modules/input/inputtest_drv.so
lrwxrwxrwx    1 root     root            80 May 25 15:51 libinput_drv.so -> /tmp/tcloop/xf86-input-libinput/usr/local/lib/xorg/modules/input/libinput_drv.so
lrwxrwxrwx    1 root     root            82 May 25 15:51 synaptics_drv.so -> /tmp/tcloop/xf86-input-synaptics/usr/local/lib/xorg/modules/input/synaptics_drv.so
tc@box:~$ Of course libinput is useless, I will start removing libinput and change *.conf for edev + synaptics.

[nick65go]

Attached is the full Xorg.0.log.gz (8 kB) to prove that I have the same protocol error, even using new recompiled synaptics.

Code: [Select]

[  1544.538] (II) config/udev: Adding input device SYNA32E0:00 06CB:CE17 Mouse (/dev/input/event7)
[  1544.538] (**) SYNA32E0:00 06CB:CE17 Mouse: Applying InputClass "HP17 pointer"
[  1544.538] (**) SYNA32E0:00 06CB:CE17 Mouse: Applying InputClass "Default clickpad buttons"
[  1544.538] (II) LoadModule: "synaptics"
[  1544.538] (II) Loading /usr/local/lib/xorg/modules/input/synaptics_drv.so
[  1544.545] (II) Module synaptics: vendor="X.Org Foundation"
[  1544.545]     compiled for 1.21.1.16, module version = 1.10.0
[  1544.545]     Module class: X.Org XInput Driver
[  1544.545]     ABI class: X.Org XInput driver, version 24.4
[  1544.545] (II) Using input driver 'synaptics' for 'SYNA32E0:00 06CB:CE17 Mouse'
[  1544.545] (**) SYNA32E0:00 06CB:CE17 Mouse: always reports core events
[  1544.545] (**) Option "Device" "/dev/input/event7"
[  1544.626] (EE) synaptics: SYNA32E0:00 06CB:CE17 Mouse: Synaptics driver unable to detect protocol
[  1544.626] (EE) PreInit returned 11 for "SYNA32E0:00 06CB:CE17 Mouse"
[  1544.626] (II) UnloadModule: "synaptics"
[  1544.627] (II) config/udev: Adding input device SYNA32E0:00 06CB:CE17 Mouse (/dev/input/mouse1)
[  1544.627] (II) No input driver specified, ignoring this device.
[  1544.627] (II) This device may have been added with another device file.
[  1544.627] (II) config/udev: Adding input device SYNA32E0:00 06CB:CE17 Touchpad (/dev/input/event8)
[  1544.627] (**) SYNA32E0:00 06CB:CE17 Touchpad: Applying InputClass "HP17 touchscreen"
[  1544.627] (**) SYNA32E0:00 06CB:CE17 Touchpad: Applying InputClass "Default clickpad buttons"
[  1544.627] (II) Using input driver 'synaptics' for 'SYNA32E0:00 06CB:CE17 Touchpad'
[  1544.627] (**) SYNA32E0:00 06CB:CE17 Touchpad: always reports core events
[  1544.627] (**) Option "Device" "/dev/input/event8"
[  1544.680] (EE) synaptics: SYNA32E0:00 06CB:CE17 Touchpad: Synaptics driver unable to detect protocol
[  1544.680] (EE) PreInit returned 11 for "SYNA32E0:00 06CB:CE17 Touchpad"
[  1544.680] (II) UnloadModule: "synaptics"I did not have any libinput, and my changed 10-evdev,conf was:

Code: [Select]

Section "InputClass"
        Identifier "HP17 pointer"
        MatchIsPointer "on"
        MatchDevicePath "/dev/input/event*"
    MatchProduct "SYNA"
        Driver "synaptics"
EndSection

Section "InputClass"
        Identifier "HP17 touchpad"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
    MatchProduct "SYNA"
        Driver "synaptics"
EndSection

Section "InputClass"
        Identifier "HP17 touchscreen"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
    MatchProduct "SYNA"
        Driver "synaptics"
EndSection

Section "InputClass"
        Identifier "evdev pointer catchall"
        MatchIsPointer "on"
        MatchDevicePath "/dev/input/event*"
    NoMatchProduct "SYNA"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev keyboard catchall"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

[Juanito]

Did you manually edit the Xorg-7.7 dep file to remove xf86-input-libinput and add xf86-input-evdev?

[nick65go]

Did you manually edit the Xorg-7.7 dep file to remove xf86-input-libinput and add xf86-input-evdev?

No *.dep file edited; just delete the simlinks from:

Code: [Select]

/usr/local/lib/xorg/modules/input/libinput_drv.so
/usr/local/share/X11/xorg.conf.d/40-libinput.confso xorg will not find them, and then add my modified /usr/local/share/X11/xorg.conf.d/10-evdev.conf listed in my previous post. I also listed my onboot.lst used,
I tried to keep all as virgin as possible.

[nick65go]

I tried to unload all i2c* kernel drivers. when i2c_hid is removed the touch pad is dead.
after "sudo modprobe i2c_hid_acpi" it function again (as a pointer).
so i think my options are for xorg upgraded., or kernel drivers + parameters (if not them built inside), so I skim for parameters in /sys/modules (but blindly search for what?)it is crazy that my touchpad is seen by udev as touchscreen, so if firmware bug then I am toasted (but surviving).

Some old internet info, said something about kernel driver "psmouse":

Code: [Select]

tc@box:~$ sudo cat /sys/module/psmouse/parameters/synaptics_intertouch
-1
tc@box:~$

[nick65go]

Wayland +labwc: from Xorg I exit in console, load labwc-config + labwc + wayland, start the script,  All TC native apps are working. plus the xorg appls (ex: Xfe file manager).

I can NOT copy from terminal into firefox, so I run commands in terminal and save them in a text file to send here:

Code: [Select]

⎡ Virtual core pointer                        id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
⎜   ↳ xwayland-pointer:15                         id=6    [slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:15                id=7    [slave  pointer  (2)]
⎜   ↳ xwayland-pointer-gestures:15                id=8    [slave  pointer  (2)]
⎜   ↳ xwayland-touch:15                           id=10    [slave  pointer  (2)]
⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                 id=5    [slave  keyboard (3)]
    ↳ xwayland-keyboard:15                        id=9    [slave  keyboard (3)]

Code: [Select]

Device 'Virtual core pointer':
    Device Enabled (120):    1
    Coordinate Transformation Matrix (122):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

Device 'Virtual core keyboard':
    Device Enabled (120):    1
    Coordinate Transformation Matrix (122):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

Device 'Virtual core XTEST pointer':
    Device Enabled (120):    1
    Coordinate Transformation Matrix (122):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    XTEST Device (240):    1

Code: [Select]

Device 'xwayland-pointer:15':
    Device Enabled (120):    1
    Coordinate Transformation Matrix (122):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (246):    0
    Device Accel Constant Deceleration (247):    1.000000
    Device Accel Adaptive Deceleration (248):    1.000000
    Device Accel Velocity Scaling (249):    10.000000
Device 'xwayland-relative-pointer:15':
    Device Enabled (120):    1
    Coordinate Transformation Matrix (122):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (246):    0
    Device Accel Constant Deceleration (247):    1.000000
    Device Accel Adaptive Deceleration (248):    1.000000
    Device Accel Velocity Scaling (249):    10.000000

Code: [Select]

Device 'xwayland-pointer-gestures:15':
    Device Enabled (120):    1
    Coordinate Transformation Matrix (122):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (246):    0
    Device Accel Constant Deceleration (247):    1.000000
    Device Accel Adaptive Deceleration (248):    1.000000
    Device Accel Velocity Scaling (249):    10.000000

Device 'xwayland-keyboard:15':
    Device Enabled (120):    1
    Coordinate Transformation Matrix (122):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000

Device 'xwayland-touch:15':
    Device Enabled (120):    1
    Coordinate Transformation Matrix (122):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (246):    0
    Device Accel Constant Deceleration (247):    1.000000
    Device Accel Adaptive Deceleration (248):    1.000000
    Device Accel Velocity Scaling (249):    10.000000firefox is misleading that is no acceleration (but is still fast)

Code: [Select]

ompositing    WebRender
Font Visibility Debug Info    Linux Unknown - ID=tinyco
Asynchronous Pan/Zoom    wheel input enabled; touch input enabled; scrollbar drag enabled; keyboard enabled; autoscroll enabled; smooth pinch-zoom enabledDescription    Mesa Intel(R) Graphics (RPL-U)
Vendor ID    0x8086
Device ID    0xa7a1
Driver Vendor    mesa/iris
Driver Version    24.1.7.0Anyway, back to the main topic: no improvement for touchpad gestures.

[nick65go]

BTW, the onboot.lst for wayland + labcw was without Xorg (no file /var/log/xorg* shows up)

Code: [Select]

firmware-rtlwifi.tcz
firmware-wlan.tcz
firmware-i915.tcz
aterm.tcz
wbar.tcz
flwm.tcz
labwc-menu-generator.tcz
labwc-config.tcz
wayland-utils.tczOMG: all in incredible faster in wayland+labcw versus Xorg or Xfbdev; plus I discovered the "warm water" (waybar, swaybg, wlr-randr), I would put swaybg & waybar in onboot.lst to be equivalent to out-the-box TC.

[Juanito]

OMG: all in incredible faster in wayland+labcw versus Xorg or Xfbdev

That's my feeling using piCore - it definately seems faster to start - but it's not so obvious on pc hardware.

The downside, compared to Xvesa or Xfbdev is that many more extensions are required.

[nick65go]

I solved it by installing a new OS in another partition;

Code: [Select]

❯ uname -a
Linux cachyos-HP17 6.14.8-2-cachyos #1 SMP PREEMPT_DYNAMIC Fri, 23 May 2025 09:41:30 +0000 x86_64 GNU/Linux
❯ xinput
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
⎡ Virtual core pointer                        id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
⎜   ↳ xwayland-pointer:10                         id=6    [slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:10                id=7    [slave  pointer  (2)]
⎜   ↳ xwayland-pointer-gestures:10                id=8    [slave  pointer  (2)]
⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                 id=5    [slave  keyboard (3)]
    ↳ xwayland-keyboard:10                        id=9    [slave  keyboard (3)]Is not Xorg, but Wayland in KDE for now. And libinput works correctly by default (I just need to customize it).

Code: [Select]

❯ sudo libinput list-devices
..
Device:                  SYNA32E0:00 06CB:CE17 Mouse
Kernel:                  /dev/input/event7
Id:                      i2c:06cb:ce17
Group:                   6
Seat:                    seat0, default
Capabilities:            pointer
Tap-to-click:            n/a
Tap-and-drag:            n/a
Tap button map:          n/a
Tap drag lock:           n/a
Left-handed:             disabled
Nat.scrolling:           disabled
Middle emulation:        n/a
Calibration:             n/a
Scroll methods:          *button
Scroll button:           BTN_RIGHT
Scroll button lock:      disabled
Click methods:           none
Clickfinger button map:  n/a
Disable-w-typing:        n/a
Disable-w-trackpointing: n/a
Accel profiles:          flat *adaptive custom
Rotation:                n/a
Area rectangle:          n/a

Device:                  SYNA32E0:00 06CB:CE17 Touchpad
Kernel:                  /dev/input/event8
Id:                      i2c:06cb:ce17
Group:                   6
Seat:                    seat0, default
Size:                    111x69mm
Capabilities:            pointer gesture
Tap-to-click:            disabled
Tap-and-drag:            enabled
Tap button map:          left/right/middle
Tap drag lock:           disabled
Left-handed:             disabled
Nat.scrolling:           disabled
Middle emulation:        disabled
Calibration:             n/a
Scroll methods:          *two-finger edge
Scroll button:           n/a
Scroll button lock:      n/a
Click methods:           *button-areas clickfinger
Clickfinger button map:  left/right/middle
Disable-w-typing:        enabled
Disable-w-trackpointing: enabled
Accel profiles:          flat *adaptive custom
Rotation:                n/a
Area rectangle:          n/a

❯ sudo dmesg | grep -i input
[    3.341028] input: SYNA32E0:00 06CB:CE17 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-12/i2c-SYNA32E0:00/0018:06CB:CE17.0002/input/input7
[    3.341385] input: SYNA32E0:00 06CB:CE17 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-12/i2c-SYNA32E0:00/0018:06CB:CE17.0002/input/input8
[    3.341618] hid-generic 0018:06CB:CE17.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA32E0:00 06CB:CE17] on i2c-SYNA32E0:00So good news is that I do not have a firmware bug!
Maybe my hardware was in need for a better kernel (or modules not built-in) or updated mesa / Wayland etc. I realty do not know.
The "bad" news is that is nice but BLOATED. I do not complain too much -- I have RAM, SSD, APU resources. But I like simplicity and to understand how all assemble and work. With TC was much easy.I have  a lot on my plate now, because: fish shell, KDE appl, etc. I had a long time without "integrate environment"... to much info for what I need (like LibreOffice / gnumeric, firefox, 7zip, mpv, wim, etc).
Anyway, I can provide (on demand) some output if you need it, just say what commands to issue for touch-pad bugs in current TC.
Or else, you can mark the topic as closed.

[Rich]

Hi nick65go

...

Code: [Select]

----- Snip -----
❯ sudo dmesg | grep -i input
[    3.341028] input: SYNA32E0:00 06CB:CE17 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-12/i2c-SYNA32E0:00/0018:06CB:CE17.0002/input/input7
[    3.341385] input: SYNA32E0:00 06CB:CE17 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-12/i2c-SYNA32E0:00/0018:06CB:CE17.0002/input/input8
[    3.341618] hid-generic 0018:06CB:CE17.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA32E0:00 06CB:CE17] on i2c-SYNA32E0:00 ...

That's the same thing TC detected according to your original post:

...

Code: [Select]

tc@box:~$ dmesg | grep -i syn
[    1.199343] usbcore: registered new interface driver synaptics_usb
[  166.264675] input: SYNA32E0:00 06CB:CE17 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA32E0:00/0018:06CB:CE17.0002/input/input7
[  166.265428] input: SYNA32E0:00 06CB:CE17 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA32E0:00/0018:06CB:CE17.0002/input/input8
[  166.266197] hid-generic 0018:06CB:CE17.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA32E0:00 06CB:CE17] on i2c-SYNA32E0:00
tc@box:~$

[nick65go]

Hi Rich, I agree with your observation. MY remarks are that:
1. It did not worked with Xorg + synaptics (protocol error 11)
2. It did not worked with Wayland + labwc (libinput & xinput not very useful).
3. with the new combination Kernel 6.14 + Wayland +KDE works.

I started to read about my APU (CPU+GPU): Core i5 1335U [Device ID (linux) = 0xA7A1]; it is a Raptor Lake [U= low power, 15w]. The processor is connected to PCHs (Platform Controller Hub) using an OPIO 2.0 x8 interface, the processor and PCH are packaged together on a multi-chip package.

1. So firmware is very important to setup PCH. PCH replaced south bridge, the north bridge was assimilated in CPU. Practically ALL is integrated on chip: sound, thundrebolt4, Wifi 6E, graphic acceleration, USB3, HDMI etc.
2. And kernel drivers: if they are build as modules, then they can accept parameters for initialization.
3. And server:Xorg or Wayland, needs proper input modules. Maybe Xorg synaptic is out of love with Xorg. I bet on mature Xorg, considering Wayland as forever in development. Maybe is time to change my mind.

Summary: As I said, I do not know what is the bug in the chain firmware -kernel_modules -Xorg-input_modules. But, it is a bug (for my hardware) as long as it works with other combinations.
Even if I will identify the bug component (eventually, because I did not give up on TC distro), then what? Will TC team upgrade the kernel, or the Xorg, or Mesa, or Wayland, or.. I do not think so, sorry. TC is aimed for compatibility with OLD hardware even for x64 arch. Is the break out similar with windows_NT kernel versus Win95 based on MSDOS.

[Juanito]

Will TC team upgrade the kernel, or the Xorg, or Mesa, or Wayland, or.. I do not think so, sorry. TC is aimed for compatibility with OLD hardware even for x64 arch.

The many components of Xorg are barely maintained and the situation will get worse.

CorePure64 has a reasonably recent version of mesa, changes to the library structure have made me pause upgrades for the moment, but I don’t think it’s the cause of your problems.

Wayland is the latest version.

The tinycore kernel is updated every year.

You might want to check dmesg to see which versions of the relevant firmware your machine is searching for - an update to the firmware might help.

[Rich]

Hi nick65go

... 2. And kernel drivers: if they are build as modules, then they can accept parameters for initialization. ...

The kernel command line accepts module parameters regardless of whether
the module is built in or not:

Code: [Select]

vmlinuz quiet ... ModuleName.ParameterName=ParameterValue ...

Module parameters can be specified in two ways: via the kernel command line with a module name prefix, or via modprobe, e.g.:

(kernel command line) usbcore.blinkenlights=1
(modprobe command line) modprobe usbcore blinkenlights=1

Parameters for modules which are built into the kernel need to be specified on the kernel command line.

Found here:
https://github.com/torvalds/linux/blob/v6.12/Documentation/admin-guide/kernel-parameters.rst