Bug 2455132 - iio-sensor-proxy.service / Tablet mode not working after upgrading linux-firmware 20260309
Summary: iio-sensor-proxy.service / Tablet mode not working after upgrading linux-firm...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 43
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-04 21:28 UTC by helpmepls477
Modified: 2026-04-06 09:02 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description helpmepls477 2026-04-04 21:28:04 UTC
Auto rotate and the iio sensor used to work when I installed fedora, but broke with an update. iio-sensor-proxy.service does not run properly.

My laptop is
HP Omnibook Ultra Flip 14 with the Lunar Lake Ultra 9 288V processor.

This issue is similar to bug 2448048 experinced on a lenovo Lunar Lake laptop.
https://bugzilla.redhat.com/show_bug.cgi?id=2448048

Downgrading the firmware to version 20260221 like the user mentioned in that thread, fixes the issue. It is specifically the Intel Firmware that had a regression.
A fix was made for that laptop, but the issue presists for me.I am unsure what differences there are, as it should be the same gyroscope sensor present in all lunar lake chips.



Reproducible: Always

Steps to Reproduce:
1.Use tablet mode on a device running linux-firmware-20260221
2. Update system to linux-firmware-20260309
3. Observe that iio-sensor-proxy.service no longer runs and tablet mode doesn't work
Actual Results:
iio-sensor-proxy.service does not run

Expected Results:
iio-sensor-proxy.service runs and tablet mode and auto rotate works as intended when the screen of the laptop is flipped

Comment 1 Peter Robinson 2026-04-06 09:02:53 UTC
The fix for the Lenovo was a kernel fix to deal with different firmware versions. This likely needs a similar fix.


Note You need to log in before you can comment on or make changes to this bug.