On 12/05/26 at 04:41, Max Nikulin wrote:
On 12/05/2026 1:29 am, Franco Martelli wrote:
~$ sudo modinfo psmouse
…
1 = enabled, 0 = disabled (default). (bool)
parm:           resetafter:Reset device after so many bad packets (0 = never). (uint) parm:           resync_time:How long can mouse stay idle before forcing resync (in seconds, 0 = never). (uint)

It looks interesting, but I would not exclude an issue with the lower level i8042 rather than with generic psmouse. I am unsure if it is possible to unload it and load again (perhaps from a VT, not from GUI session).

Debug logging for the module might be tried, however it should be rather verbose. I have no idea if it is possible to dump internal module state to inspect it with debugger.


checking the documentation into the Linux kernel sources (version 6.12.85) for the i8042 driver are available the following kernel parameters:

        i8042.debug     [HW] Toggle i8042 debug mode
        i8042.unmask_kbd_data
[HW] Enable printing of interrupt data from the KBD port
                             (disabled by default, and as a pre-condition
                             requires that i8042.debug=1 be enabled)
        i8042.direct    [HW] Put keyboard port into non-translated mode
i8042.dumbkbd [HW] Pretend that controller can only read data from
                             keyboard and cannot control its state
                             (Don't attempt to blink the leds)
        i8042.noaux     [HW] Don't check for auxiliary (== mouse) port
        i8042.nokbd     [HW] Don't check/create keyboard port
        i8042.noloop    [HW] Disable the AUX Loopback command while probing
                             for the AUX port
        i8042.nomux     [HW] Don't check presence of an active multiplexing
                             controller
i8042.nopnp [HW] Don't use ACPIPnP / PnPBIOS to discover KBD/AUX
                             controllers
i8042.notimeout [HW] Ignore timeout condition signalled by controller
        i8042.reset     [HW] Reset the controller during init, cleanup and
                             suspend-to-ram transitions, only during s2r
                             transitions, or never reset
                        Format: { 1 | Y | y | 0 | N | n }
                        1, Y, y: always reset controller
                        0, N, n: don't ever reset controller
                        Default: only on s2r transitions on x86; most other
                        architectures force reset to be always executed
        i8042.unlock    [HW] Unlock (ignore) the keylock
        i8042.kbdreset  [HW] Reset device connected to KBD port
        i8042.probe_defer
                        [HW] Allow deferred probing upon i8042 probe errors

maybe changing in "/etc/default/grub" the line:

GRUB_CMDLINE_LINUX="i8042.debug=1 i8042.reset=0"

should provide further information hopeful useful, but I don't think that other parameters are useless.

A search with AI suggests to specify also "i8042.noloop i8042.nomux", HTH.

kind regards,
--
Franco Martelli

Reply via email to