Further testing has confirmed that linux-firmware-20260309 is the culprit.
If I install linux-firmware-20260221, then boot kernel-6.19.7, THEN rebuild initrd by runing $ sudo dracut -f --regenerate-all and reboot, then iio-sensor-proxy.service WILL START using linux-firmware-20260221 and kernel-6.19.7.
@willowow try downgrading your linux-firmware and associated packages to 20260221, reboot and run $ sudo dracut -f --regenerate-all and reboot again.
Okay, good to know. My laptop is also a Lunar Lake, 288v, and they share a similar controller for the accelerometer. I’ll try and install base Fedora later since I’m on an atomic Fedora distro now, and changing firmware alone is tricky.
Please share your findings here 2389025 – Intel Lunar Lake Communication Controller Driver Missing or make a new bug report. This bug is still left open, and is from august, with a similar firmware issue for Lunar Lake. Redhat bugzilla is where the fedora devs see and react to reports.
Hi I’m on Fedora 43 now but I can’t get this to work, when i try to downgrade to that package it gives:
Problem: conflicting requests
nothing provides linux-firmware-whence = 20260221-1.fc43 needed by linux-firmware-20260221-1.fc43.noarch from @commandline
You can try to add to command line:
–skip-broken to skip uninstallable packages
What I did was go to the Fedora Koji archive (link: Making sure you're not a bot!) and download all of the linux-firmware-20260221 packages into a folder (30 packages), then open a terminal in that folder and run sudo dnf downgrade * and that worked perfect.
Thank you so much! It now works for me! Maybe update your solution post with the note of needing to download all and the dracut steps and all lunar lake owners can refer to this thread ^^
I’ve been in contact with one of the guys at Red Hat, running some tests for him, and have confirmed that it’s an issue with the way the kernel talks to the firmware packages.
There’s a patch coming soon to a kernel update that will resolve the issue.
Oh right you have an HP. A new bugzilla thread for yours might be the way to go. I’d suspect the root cause is similar but your firmware packages probably have a different maintainer.