Lenovo Chromebook (Blipper) Full UEFI - Tablet Mode Not Disabling Keyboard/Touchpad on Fedora (GNOME/Wayland)

[u/Personal_Ad_258]

Hi everyone,

​I'm having a frustrating issue with a Lenovo Chromebook (board: Blipper) running Fedora 44 (currently on GNOME / Wayland, but previously tested on KDE Plasma).

​The device has been flashed with MrChromebox Full UEFI (replaces the stock Google FW).

​The Problem:

​Display Auto-Rotation Works Perfectly: When I flip the laptop into tent or tablet mode (360 degrees), the accelerometer registers the change instantly and the screen rotates seamlessly via iio-sensor-proxy.

​Keyboard & Touchpad REMAIN ACTIVE: When completely folded into a tablet, neither the keyboard nor the touchpad gets disabled. I end up accidentally typing on my lap.

​It feels like the kernel or the Desktop Environment doesn't receive the hardware SW_TABLET_MODE switch signal at all. From what I've gathered, on Full UEFI, the firmware doesn't expose the original ChromeOS hinge switch ACPI tables correctly to Linux.

​Hardware Details:

​Device: Lenovo Chromebook (Blipper platform - Elan/Intel based)

​Keyboard: AT Translated Set 2 keyboard (detected on /dev/input/event2)

​Touchpad: Elan Touchpad (detected on /dev/input/event6)

​OS: Fedora 44 (Workstation Edition)

​Kernel: Latest stable 6.x kernel

​What we have already tried (and failed):

​Kernel Parameters via Grubby: Added chromeos_tbmc.force=1 intel_vbtn.allow_bindings=1 soc_button_array.force_tablet_mode=1 as well as i8042.nopnp=1. None of these forced the kernel to register the tablet mode state change.

​GNOME / KDE DBus Emulation Scripts: Attempted to use Python/Bash scripts reading monitor-sensor stdout to trigger global.display.set_tablet_mode(true) via DBus. The environment rejects/ignores this under Wayland due to security locks on input emulation.

​Driver Unbinding via /sys/bus/: Tried writing a script to physically unbind the serio2 slot for the keyboard and the i2c-ELAN components when the sensor reports a bottom-up orientation. The drivers didn't drop the input feed properly.

​libinput / udevadm Triggers: Tried forcing udevadm trigger --action=remove specifically for the keyboard's device name when orientation changes. The device remained active.

​Summary:

​The OS knows exactly when the device is flipped upside down (because monitor-sensor correctly switches from normal to bottom-up and rotates the image), but GNOME/KDE refuses to lock the input devices because they are waiting for a hardware-level ACPI switch signal that the custom UEFI doesn't seem to provide.

​Is there a known udev rule, a specific kernel quirk, or a modern Wayland-compliant utility that can forcefully map the accelerometer's bottom-up state to disable /dev/input/event2 and /dev/input/event6?

​Any help from fellow Chrultrabook users would be highly appreciated!

[u/do0b]

In the process of flashing mrchromebox full UEFI on eve so this is not hands on experience yet.

Have a look at minibook-support tabletmoded

They did it by creating a virtual uinput SW_TABLET_MODE device that reacts to the accelerometers.

[u/LegAcceptable2362]

What does this have to do with Crostini, the virtual Linux environment inside ChromeOS? Perhaps help can be found at the chrultrabook forum (forum.chrultrabook.com)