Linux Input/HID development
 help / color / mirror / Atom feed
From: Heiko Brey <cico0815@gmx.de>
To: linux-input@vger.kernel.org
Subject: i8042: Fujitsu LIFEBOOK U7410 needs i8042.nomux (keyboard and touchpad dead)
Date: Sat, 19 Sep 2026 11:52:19 +0200	[thread overview]
Message-ID: <89f36f3f5e4c2d07b9ff72bc0b355875c336e498.camel@gmx.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

Hi,

On a Fujitsu LIFEBOOK U7410 the internal keyboard and touchpad are dead
after boot with the default i8042 settings. Both work in BIOS and GRUB.
The kernel registers the devices (AT Translated Set 2 keyboard, and the
Elan touchpad 04F3:3092 via I2C-HID), but evtest shows no events on
either.

System:
  Kernel:          7.0.0-31-generic (Linux Mint 22.3)
  sys_vendor:      FUJITSU CLIENT COMPUTING LIMITED
  product_name:    LIFEBOOK U7410
  board_name:      FJNB2D4
  BIOS:            Version 2.12, 06/23/2020

With default parameters, dmesg reports:

  i8042: Detected active multiplexing controller, rev 1.1
  atkbd serio0: Spurious ACK on isa0060/serio0 (repeated)
  atkbd serio0: Unknown key pressed (translated set 2, code 0x0)

What I tried:
  - i8042.nopnp i8042.reset: no change
  - i8042.nomux=1 i8042.reset: keyboard and touchpad work, on warm and
    cold boot. The multiplexing message and the Spurious ACK messages
    no longer appear.
  (I have not tested i8042.nomux=1 without i8042.reset.)

Could a DMI quirk with nomux be added for this model?

Thanks,

Heiko
-- 
Heiko Brey

GPG-Fingerprint: C8A4 ABA2 B404 407D 83F1 46FC 0A66 455F CA5A 1277
Info zu verschlüsselten Emails: https://emailselfdefense.fsf.org/de/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2026-09-19  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19  9:52 Heiko Brey [this message]
2026-09-19 18:29 ` i8042: Fujitsu LIFEBOOK U7410 needs i8042.nomux (keyboard and touchpad dead) Lovekesh Solanki
2026-09-20  8:03   ` Heiko Brey
2026-09-20 11:18     ` Lovekesh Solanki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89f36f3f5e4c2d07b9ff72bc0b355875c336e498.camel@gmx.de \
    --to=cico0815@gmx.de \
    --cc=heiko.brey@gmx.de \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox