The touchpad PNP0C50 only works when waking from sleep mode.

judd · Aug 20, 2026

As the post title says, for the touchpad to work when logging in, I have to press Ctrl+Alt+T to open a terminal and use `sudo zzz` to enter sleep mode, wait a few seconds and press Enter to wake from sleep – only then does the touchpad start to move/work.

The device is I2C/SMBus. → Ryzen 5 3500U

Code:

$ uname -aU
FreeBSD freebsd 15.1-RELEASE-p2 FreeBSD 15.1-RELEASE-p2 releng/15.1-n283596-aadd58dddcbc GENERIC amd64 1501000

Code:

$ cat /usr/local/etc/X11/xorg.conf.d/touchpad.conf
Section "InputDevice"
 Identifier "Touchpad"
 Driver "libinput"
 Option "Device" "/dev/input/event*"
 Option "AutoServerLayout" "true"
 Option "Tapping" "on"
EndSection

Code:

$ cat /usr/local/etc/X11/xorg.conf.d/90-touchpad.conf
Section "InputClass"
        Identifier "touchpad"
        MatchIsTouchpad "on"
        Driver "libinput"
        Option "Tapping" "on"
EndSection

Code:

$ cat /boot/loader.conf
amdtemp_load="YES"

iicbus_load="YES"
iic_load="YES"
smbus_load="YES"
iichid_load="YES"
ietp_load="YES"
hw.usb.usbhid.enable="1"
alpm_load="YES"
ums_load="YES"
hms_load="YES"
ig4iic_load="YES"
snd_hda_load="YES"
hw.psm.elantech_support="1"
hw.psm.synaptics_support="0"

Code:

$ xinput
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
⎜   ↳ System mouse                                id=7    [slave  pointer  (2)]
⎜   ↳ PNP0C50:01 347D:C007 TouchPad               id=12    [slave  pointer  (2)]
⎜   ↳ KYE SYSTEMS CORP. Wired Mouse               id=14    [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard                 id=5    [slave  keyboard (3)]
    ↳ System keyboard multiplexer                 id=6    [slave  keyboard (3)]
    ↳ Power Button                                id=8    [slave  keyboard (3)]
    ↳ PNP0C50:01 347D:C007 Keyboard               id=10    [slave  keyboard (3)]
    ↳ AT keyboard                                 id=11    [slave  keyboard (3)]
    ↳ PNP0C50:01 347D:C007 Consumer Control       id=13    [slave  keyboard (3)]
∼ PNP0C50:01 347D:C007 Mouse                    id=9    [floating slave]

Code:

$ cat /etc/sysctl.conf

hw.psm.tap_timeout=0
kern.evdev.rcpt_mask=12

hw.snd.default_unit=1

Code:

$ dmesg
hmt0: <PNP0C50:01 347D:C007 TouchPad> on hidbus0
hconf0: <PNP0C50:01 347D:C007 Configuration> on hidbus0
hmt0: Multitouch touchpad with 2 external buttons, click-pad
hmt0: 5 contacts with [C] properties. Report range [0:0] - [1749:1038]
hcons0: <PNP0C50:01 347D:C007 Consumer Control> on hidbus0

Many thanks in advance!

judd · Tuesday at 4:49 PM

I’m still fiddling around with this Ryzen 5 3500U, and now with drm-612-kmod.
The touchpad works only partially, but it does work, whilst the sound doesn’t work at all.
Here’s the dmesg output when coming out of sleep mode to get the touchpad working:

Code:

rtwn0: detached
uhub0: detached
acpi0: cleared fixed power button status
drmn0: S3 suspend abort case, let's reset ASIC.
drmn0: MODE2 reset
[drm] PCIE GART of 1024M enabled.
[drm] PTB located at 0x000000F400A00000
drmn0: PSP is resuming...
drmn0: reserve 0x400000 from 0xf47fc00000 for PSP TMR
drmn0: RAS: optional ras ta ucode is not available
drmn0: RAP: optional rap ta ucode is not available
drmn0: SECUREDISPLAY: securedisplay ta ucode is not available
amdgpu: restore the fine grain parameters
[drm]  Will skip the CSB packet resubmit
[drm] kiq ring mec 2 pipe 1 q 0
drmn0: ring gfx uses VM inv eng 0 on hub 0
drmn0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
drmn0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
drmn0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
drmn0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
drmn0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
drmn0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
drmn0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
drmn0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
drmn0: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
drmn0: ring sdma0 uses VM inv eng 0 on hub 8
drmn0: ring vcn_dec uses VM inv eng 1 on hub 8
drmn0: ring vcn_enc0 uses VM inv eng 4 on hub 8
drmn0: ring vcn_enc1 uses VM inv eng 5 on hub 8
drmn0: ring jpeg_dec uses VM inv eng 6 on hub 8
uhub0 on usbus1
uhub0: <AMD XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1
uhub1 on usbus0
uhub1: <AMD XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
uhub0: 3 ports with 3 removable, self powered
uhub1: 8 ports with 8 removable, self powered
ugen1.2: <vendor 0x05e3 USB2.0 Hub> at usbus1
uhub2 on uhub0
uhub2: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/60.60, addr 1> on usbus1
uhub2: MTT enabled
ugen0.2: <HYGD-251126-H HY  HD 72M1  Camera> at usbus0
ugen0.3: <Realtek 802.11n WLAN NIC> at usbus0
rtwn0 on uhub1
rtwn0: <Realtek 802.11n WLAN NIC, class 0/0, rev 2.00/0.00, addr 2> on usbus0
uhub2: 4 ports with 1 removable, self powered
rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R
wlan0: Ethernet address: 1c:a0:d3:67:92:f4
ugen1.3: <Generic USB2.0-CRW> at usbus1
ugen1.4: <Realtek Bluetooth Radio> at usbus1
wlan0: link state changed to UP

I also edited the touchpad.conf file, without any success, and deleted the two files mentioned in the first post.

Code:

Section "InputClass"
    Identifier "libinput touchpad"
    MatchIsTouchpad "on"
    Driver "libinput"
    Option "Tapping" "on"
    Option "NaturalScrolling" "on"
    Option "ScrollMethod" "twofinger"
EndSection

Well, apart from that, everything else is working fine, apart from what I’ve already mentioned.

I’ll carry on troubleshooting with what little knowledge I have, to see how far I can get with this.

MG · Tuesday at 5:46 PM

Something is deactivating it?
Never had this device, but can you "raw" listen to any touch actions?
Throw device input data per byte to the console: stdbuf -o 0 cat <device name>
(end the terminal when it goes bad of control characters inside the stream)
I wonder if it stil sees something when that sleep mode is apparently blocking the input.

judd · Tuesday at 7:11 PM

MG said:
can you "raw" listen to any touch actions?

No, you can’t hear a thing.

Code:

$ dmesg | grep -i touchpad
hmt0: <PNP0C50:01 347D:C007 TouchPad> on hidbus0
hmt0: Multitouch touchpad with 2 external buttons, click-pad

Code:

$ stdbuf -o 0 cat NP0C50:01 347D:C007 TouchPad
cat: NP0C50:01: No such file or directory
cat: 347D:C007: No such file or directory
cat: TouchPad: No such file or directory

Code:

Log: xinput
⎡ Virtual core pointer                        id=2    [master pointer  (3)]
    Reporting 7 classes:
        Class originated from: 12. Type: XIButtonClass
        Buttons supported: 12
        Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None None None
        Button state:
        Class originated from: 12. Type: XIValuatorClass
        Detail for Valuator 0:
          Label: Rel X
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 12. Type: XIValuatorClass
        Detail for Valuator 1:
          Label: Rel Y
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 12. Type: XIValuatorClass
        Detail for Valuator 2:
          Label: Rel Horiz Scroll
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 12. Type: XIValuatorClass
        Detail for Valuator 3:
          Label: Rel Vert Scroll
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 12. Type: XIScrollClass
        Scroll info for Valuator 2
          type: 2 (horizontal)
          increment: 120.000000
          flags: 0x0
        Class originated from: 12. Type: XIScrollClass
        Scroll info for Valuator 3
          type: 1 (vertical)
          increment: 120.000000
          flags: 0x0

⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
    Reporting 3 classes:
        Class originated from: 4. Type: XIButtonClass
        Buttons supported: 10
        Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None
        Button state:
        Class originated from: 4. Type: XIValuatorClass
        Detail for Valuator 0:
          Label: Rel X
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 4. Type: XIValuatorClass
        Detail for Valuator 1:
          Label: Rel Y
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative

⎜   ↳ System mouse                                id=7    [slave  pointer  (2)]
    Reporting 7 classes:
        Class originated from: 7. Type: XIButtonClass
        Buttons supported: 12
        Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" None
        Button state:
        Class originated from: 7. Type: XIValuatorClass
        Detail for Valuator 0:
          Label: Rel X
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 7. Type: XIValuatorClass
        Detail for Valuator 1:
          Label: Rel Y
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 7. Type: XIValuatorClass
        Detail for Valuator 2:
          Label: Rel Horiz Scroll
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 7. Type: XIValuatorClass
        Detail for Valuator 3:
          Label: Rel Vert Scroll
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 7. Type: XIScrollClass
        Scroll info for Valuator 2
          type: 2 (horizontal)
          increment: 120.000000
          flags: 0x0
        Class originated from: 7. Type: XIScrollClass
        Scroll info for Valuator 3
          type: 1 (vertical)
          increment: 120.000000
          flags: 0x0

⎜   ↳ PNP0C50:01 347D:C007 TouchPad               id=12    [slave  pointer  (2)]
    Reporting 7 classes:
        Class originated from: 12. Type: XIButtonClass
        Buttons supported: 7
        Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
        Button state:
        Class originated from: 12. Type: XIValuatorClass
        Detail for Valuator 0:
          Label: Rel X
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 12. Type: XIValuatorClass
        Detail for Valuator 1:
          Label: Rel Y
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 12. Type: XIValuatorClass
        Detail for Valuator 2:
          Label: Rel Horiz Scroll
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 12. Type: XIValuatorClass
        Detail for Valuator 3:
          Label: Rel Vert Scroll
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 12. Type: XIScrollClass
        Scroll info for Valuator 2
          type: 2 (horizontal)
          increment: 120.000000
          flags: 0x0
        Class originated from: 12. Type: XIScrollClass
        Scroll info for Valuator 3
          type: 1 (vertical)
          increment: 120.000000
          flags: 0x0

⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
    Reporting 1 classes:
        Class originated from: 11. Type: XIKeyClass
        Keycodes supported: 248

    ↳ Virtual core XTEST keyboard                 id=5    [slave  keyboard (3)]
    Reporting 1 classes:
        Class originated from: 5. Type: XIKeyClass
        Keycodes supported: 248

    ↳ System keyboard multiplexer                 id=6    [slave  keyboard (3)]
    Reporting 1 classes:
        Class originated from: 6. Type: XIKeyClass
        Keycodes supported: 248

    ↳ Power Button                                id=8    [slave  keyboard (3)]
    Reporting 1 classes:
        Class originated from: 8. Type: XIKeyClass
        Keycodes supported: 248

    ↳ PNP0C50:01 347D:C007 Keyboard               id=10    [slave  keyboard (3)]
    Reporting 1 classes:
        Class originated from: 10. Type: XIKeyClass
        Keycodes supported: 248

    ↳ AT keyboard                                 id=11    [slave  keyboard (3)]
    Reporting 1 classes:
        Class originated from: 11. Type: XIKeyClass
        Keycodes supported: 248

    ↳ PNP0C50:01 347D:C007 Consumer Control       id=13    [slave  keyboard (3)]
    Reporting 1 classes:
        Class originated from: 13. Type: XIKeyClass
        Keycodes supported: 248

∼ PNP0C50:01 347D:C007 Mouse                  id=9    [floating slave]
    This device is disabled
    Reporting 7 classes:
        Class originated from: 9. Type: XIButtonClass
        Buttons supported: 7
        Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
        Button state:
        Class originated from: 9. Type: XIValuatorClass
        Detail for Valuator 0:
          Label: Rel X
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 9. Type: XIValuatorClass
        Detail for Valuator 1:
          Label: Rel Y
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 9. Type: XIValuatorClass
        Detail for Valuator 2:
          Label: Rel Horiz Scroll
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 9. Type: XIValuatorClass
        Detail for Valuator 3:
          Label: Rel Vert Scroll
          Range: -1.000000 - -1.000000
          Resolution: 0 units/m
          Mode: relative
        Class originated from: 9. Type: XIScrollClass
        Scroll info for Valuator 2
          type: 2 (horizontal)
          increment: 120.000000
          flags: 0x0
        Class originated from: 9. Type: XIScrollClass
        Scroll info for Valuator 3
          type: 1 (vertical)
          increment: 120.000000

MG · Tuesday at 7:15 PM

/dev/hid0 ?
It has no device that exists in /dev?

judd · Tuesday at 7:27 PM

MG said:
/dev/hid0 ?
It has no device that exists in /dev?

I’m not sure of the command to find it, but ‘dmesg | grep -i /dev/hid0’ doesn’t return anything.

judd · Tuesday at 7:36 PM

Code:

$ dmesg | grep -i PNP0C50:01
iichid0: <PNP0C50:01 347D:C007 I2C HID device> at addr 0x2c on iicbus1
hms0: <PNP0C50:01 347D:C007 Mouse> on hidbus0
hkbd0: <PNP0C50:01 347D:C007 Keyboard> on hidbus0
hmt0: <PNP0C50:01 347D:C007 TouchPad> on hidbus0
hconf0: <PNP0C50:01 347D:C007 Configuration> on hidbus0
hcons0: <PNP0C50:01 347D:C007 Consumer Control> on hidbus0

judd · Tuesday at 8:08 PM

MG said:
/dev/hid0 ?
It has no device that exists in /dev?

Code:

$ ls /dev
acpi        dri        input        pfil        ttyv9
ada0        drm        io        pts        ttyva
ada0p1        dsp0        kbd0        random        ttyvb
ada0p2        dsp1        kbd1        reroot        tun0
ada0p3        dsp2        kbd2        sndstat        ufssuspend
apm        dumpdev        kbdmux0        stderr        ugen0.1
apmctl        efi        klog        stdin        ugen0.2
atkbd0        fd        kmem        stdout        ugen0.3
audit        fido        log        sysmouse    ugen1.1
auditpipe    full        mdctl        tailscale0    ugen1.2
backlight    geom.ctl    mem        tcp_log        ugen1.3
bpf        hkbd0        mixer0        ttyv0        ugen1.4
bpf0        hpet0        mixer1        ttyv1        uinput
console        iic0        mixer2        ttyv2        urandom
consolectl    iic1        mlx5ctl        ttyv3        usb
ctty        iic2        netdump        ttyv4        usbctl
cuse        iic3        netmap        ttyv5        video0
devctl        iic4        null        ttyv6        video1
devctl2        iic5        pass0        ttyv7        xpt0
devstat        iic6        pci        ttyv8        zero

MG · Tuesday at 8:10 PM

/dev/iic? Lot of iic devices. I don't think that's normal unless you have something with 6 com channels or 6 iic devices.

judd · Tuesday at 8:11 PM

MG said:
/dev/iic?

Code:

$ ls /dev/iic
ls: /dev/iic: No such file or directory

MG · Tuesday at 8:17 PM

Your first ls shows iic0 to iic6 while iic only doesn't exist...
It looks like some initialization of the same is stacking up while there's only 1 iic device.

judd · Tuesday at 8:24 PM

MG said:
Your first ls shows iic0 to iic6 while iic only doesn't exist...
It looks like some initialization of the same is stacking up while there's only 1 iic device.

That’s beyond my knowledge. I’m sorry!

judd · Tuesday at 8:28 PM

MG said:
/dev/iic? Lot of iic devices. I don't think that's normal unless you have something with 6 com channels or 6 iic devices.

I really don’t know why there are so many.

MG · Tuesday at 8:34 PM

judd said:
That’s beyond my knowledge. I’m sorry!

That's a problem. You need to know how filename wildcards work.
/dev/iic? is all devices that start with iic + a 1-digit number or character but not only iic without anything else.
/dev/icc* is all files in /dev that start with iic. It can be followed up with any number, character or nothing.

I think the problem has to do with why 6 iic devices exist.

judd · Tuesday at 8:58 PM

MG said:
That's a problem. You need to know how filename wildcards work.
/dev/iic? is all devices that start with iic + a 1-digit number or character but not only iic without anything else.
/dev/icc* is all files in /dev that start with iic. It can be followed up with any number, character or nothing.

I think the problem has to do with why 6 iic devices exist.

I would like to thank you for your guidance; I must now take my leave due to the pain in my legs (paraparesis) and transverse myelitis.
My best regards and apologies.

judd · 2026-08-26T01:13:46+0100

MG said:
I think the problem has to do with why 6 iic devices exist.

I made some changes to /boot/loader.conf and /boot/device.hints, and there are no longer six iic files, but just one:

Code:

$ ls /dev*
acpi        devstat        kbd2        reroot        ttyvb
ada0        dri        kbdmux0        sndstat        tun0
ada0p1        drm        klog        stderr        ufssuspend
ada0p2        dsp0        kmem        stdin        ugen0.1
ada0p3        dsp1        log        stdout        ugen0.2
apm        dsp2        mdctl        sysmouse    ugen0.3
apmctl        dumpdev        mem        tailscale0    ugen0.4
atkbd0        efi        mixer0        tcp_log        ugen1.1
audit        fd        mixer1        ttyv0        ugen1.2
auditpipe    fido        mixer2        ttyv1        ugen1.3
backlight    full        mlx5ctl        ttyv2        ugen1.4
bpf        geom.ctl    netdump        ttyv3        uinput
bpf0        hkbd0        netmap        ttyv4        urandom
console        hpet0        null        ttyv5        usb
consolectl    iic0        pass0        ttyv6        usbctl
ctty        input        pci        ttyv7        video0
cuse        io        pfil        ttyv8        video1
devctl        kbd0        pts        ttyv9        xpt0
devctl2        kbd1        random        ttyva        zero

However, even after doing this, it still doesn’t work unless it’s in suspend mode.

siladi · 2026-08-26T04:13:19+0100

Something to try. Using xinput get the id for the touchpad ( ↳ PNP0C50:01 347D:C007 TouchPad id=12 [slave pointer (2)] ) then use "xinput list-props $touchpad_id" and check and get the "Device Enabled" and "Tapping Enabled" property id. Then see if you can flip them "xinput set-prop $touchpad_id $prop_id 1" . The id of the input device might change every session so get it dynamically from a script. But first confirm you can flip the properties for that input device.

judd · 2026-08-26T14:44:16+0100

siladi said:
Something to try. Using xinput get the id for the touchpad ( ↳ PNP0C50:01 347D:C007 TouchPad id=12 [slave pointer (2)] ) then use "xinput list-props $touchpad_id" and check and get the "Device Enabled" and "Tapping Enabled" property id. Then see if you can flip them "xinput set-prop $touchpad_id $prop_id 1" . The id of the input device might change every session so get it dynamically from a script. But first confirm you can flip the properties for that input device.

Yes, let’s give it a go, thank you!

Code:

$ xinput list-props $touchpad 12
Device 'PNP0C50:01 347D:C007 TouchPad':
    Device Enabled (169):    1
    Coordinate Transformation Matrix (170):    1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    libinput Tapping Enabled (332):    1
    libinput Tapping Enabled Default (333):    0
    libinput Tapping Drag Enabled (334):    1
    libinput Tapping Drag Enabled Default (335):    1
    libinput Tapping Drag Lock Enabled (336):    0
    libinput Tapping Drag Lock Enabled Default (337):    0
    libinput Tapping Button Mapping Enabled (338):    1, 0
    libinput Tapping Button Mapping Default (339):    1, 0
    libinput Natural Scrolling Enabled (303):    1
    libinput Natural Scrolling Enabled Default (304):    0
    libinput Disable While Typing Enabled (340):    1
    libinput Disable While Typing Enabled Default (341):    1
    libinput Scroll Methods Available (305):    1, 1, 0
    libinput Scroll Method Enabled (306):    1, 0, 0
    libinput Scroll Method Enabled Default (307):    1, 0, 0
    libinput Click Methods Available (342):    1, 1
    libinput Click Method Enabled (343):    1, 0
    libinput Click Method Enabled Default (344):    1, 0
    libinput Clickfinger Button Mapping Enabled (345):    1, 0
    libinput Clickfinger Button Mapping Default (346):    1, 0
    libinput Middle Emulation Enabled (312):    0
    libinput Middle Emulation Enabled Default (313):    0
    libinput Accel Speed (314):    0.000000
    libinput Accel Speed Default (315):    0.000000
    libinput Accel Profiles Available (316):    1, 1, 1
    libinput Accel Profile Enabled (317):    1, 0, 0
    libinput Accel Profile Enabled Default (318):    1, 0, 0
    libinput Accel Custom Fallback Points (319):    <no items>
    libinput Accel Custom Fallback Step (320):    0.000000
    libinput Accel Custom Motion Points (321):    <no items>
    libinput Accel Custom Motion Step (322):    0.000000
    libinput Accel Custom Scroll Points (323):    <no items>
    libinput Accel Custom Scroll Step (324):    0.000000
    libinput Left Handed Enabled (325):    0
    libinput Left Handed Enabled Default (326):    0
    libinput Send Events Modes Available (288):    1, 1
    libinput Send Events Mode Enabled (289):    0, 0
    libinput Send Events Mode Enabled Default (290):    0, 0
    Device Node (291):    "/dev/input/event7"
    Device Product ID (292):    13437, 49159
    libinput Drag Lock Buttons (327):    <no items>
    libinput Horizontal Scroll Enabled (328):    1
    libinput Scrolling Pixel Distance (329):    15
    libinput Scrolling Pixel Distance Default (330):    15
    libinput High Resolution Wheel Scroll Enabled (331):    1

Device Enabled (169): 1
Tapping Enabled (332): 1

Code:

 
$ xinput set-prop $touchpad_id $prop_id 1 
Usage: xinput set-prop <device> [--type=atom|float|int] [--format=8|16|32] <property> <val> [<val> ...]

¿How do I do it?

siladi · 2026-08-26T18:04:13+0100

So if your touchpad device id is 12 for this session , first see if you can flip it (enable/disable)

$ xinput set-prop 12 332 0 -- verify that tapping is disabled
$ xinput set-prop 12 169 0 -- verify that touchpad is disabled

Then re-enable with value 1 and verify that it works. You said touchpad only starts working after resume from suspend. So you have to do a test from fresh reboot and check the whole thing again and see what those device id properties look like. Maybe they are 0 for some reason. The device id might change so you need to determine that.

judd · 2026-08-26T20:36:28+0100

siladi said:
So if your touchpad device id is 12 for this session , first see if you can flip it (enable/disable)

$ xinput set-prop 12 332 0 -- verify that tapping is disabled
$ xinput set-prop 12 169 0 -- verify that touchpad is disabled

Then re-enable with value 1 and verify that it works. You said touchpad only starts working after resume from suspend. So you have to do a test from fresh reboot and check the whole thing again and see what those device id properties look like. Maybe they are 0 for some reason. The device id might change so you need to determine that.

Both during the session, after your reply, and following a clean restart, the touchpad ID remains 12, and the properties ‘Device Enabled’ (169) and ‘Tapping Enabled’ (332) – where 0 disables and 1 enables both – remain unchanged; however, this does not occur unless the system is woken from sleep.

siladi · 2026-08-26T21:31:40+0100

Question, why is hw.psm.synaptics_support set to 0 in loader.conf ? Does it get flipped to 1 by any change after resume from sleep ?

judd · 2026-08-26T21:38:03+0100

siladi said:
Question, why is hw.psm.synaptics_support set to 0 in loader.conf ?

It’s just that I didn’t edit it when I did it earlier.

Code:

$ cat /boot/loader.conf
amdtemp_load="YES"
hw.vga.textmode="0"
efi_max_resolution="1920x1080"
kern.vt.fb.default_mode="1920x1080"

#acpi_iichid_load="YES"
#iicbus_load="YES"
#iic_load="YES"
evdev_load="YES"
smbus_load="YES"
iichid_load="NO"
hid_load="YES"
hidbus_load="YES"
ietp_load="YES"
hw.usb.usbhid.enable="YES"
alpm_load="YES"
ums_load="YES"
usbhid_load="YES"
hms_load="YES"
#ig4iic_load="YES"
snd_uaudio_load="YES"
hw.psm.elantech_support="1"
hw.psm.synaptics_support="1"
hw.usb.no_shutdown_wait=1
hw.iommu.enable="0"

judd · 2026-08-26T21:43:58+0100

siladi said:
Does it get flipped to 1 by any change after resume from sleep ?

No, it doesn’t change anything. It stays at 0 or 1 depending on how you write it, and for no other reason.

siladi · 2026-08-26T21:51:10+0100

What laptop model is this? What does usbconfig show.? Has it behaved like this also in Fbsd 14?

Can you try to boot with a paired down loader.conf and make sure you have devd_enable="YES in rc.conf

amdtemp_load="YES"
hw.vga.textmode="0"
efi_max_resolution="1920x1080"
kern.vt.fb.default_mode="1920x1080"

judd · 2026-08-26T22:03:27+0100

I don’t understand what a ‘paired /boot/loader’ is?
Language barrier = I don’t speak English, I’m just translating this to reply...

devd_enable → position in rc.conf