Which Linux distro are you using?
Fedora Workstation 44
Which kernel are you using?
Linux magnolia 7.0.13-200.fc44.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jun 19 22:51:30 UTC 2026 x86_64 GNU/Linux
Which BIOS version are you using?
Current (No updates available through CLI)
Which Framework Laptop 12 model are you using? (13th Gen Intel® Core™)
The I5
Hi Framework community,
Just got my Framework 12 Great machine <3 ! But I’m hitting a persistent screen rotation issue.
After logging into GDM, the display rotates 90° clockwise. The only workaround I’ve found is folding into tent mode and back to laptop mode.
This happens after a cold boot (when the lid was closed before powering on, then opened).
It also happens when resuming from a suspend, after I opened the lid prior. In this case, the lock screen is already rotated incorrectly.
System: Clean Fedora install, less than 24 hours old.
Has anyone else seen this? Any ideas on the root cause or a proper fix?
This sounds like the accelerometer/orientation service is reporting the wrong state when GNOME starts. I would check monitor-sensor from the iio-sensor-proxy package while you open/close the lid and rotate the machine; if it already says the wrong orientation before GNOME rotates, that narrows it to sensor/firmware rather than display settings. As a temporary workaround you can disable auto-rotation in GNOME, but I would still collect systemctl status iio-sensor-proxy and the monitor-sensor output for Framework support because the cold-boot-with-lid-closed detail is useful.
Here is my log file.
After booting, with the screen orientation wrong, i ran the status command.
Then i did a monitor to see the current state. The second monitor is when I moved to tent mode from laptop, and back to laptop mode. And, when moving back to laptop mode, the orientation is correct.
mirthe@magnolia:~$ systemctl status iio-sensor-proxy.service
● iio-sensor-proxy.service - IIO Sensor Proxy service
Loaded: loaded (/usr/lib/systemd/system/iio-sensor-proxy.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Tue 2026-06-30 13:17:17 CEST; 43s ago
Invocation: a36ba4af1f3f491cb27ee14d176e61d8
Main PID: 826 (iio-sensor-prox)
Tasks: 4 (limit: 9106)
Memory: 1.6M (peak: 3.9M)
CPU: 119ms
CGroup: /system.slice/iio-sensor-proxy.service
└─826 /usr/libexec/iio-sensor-proxy
jun 30 13:17:17 magnolia systemd[1]: Starting iio-sensor-proxy.service - IIO Sensor Proxy service>
jun 30 13:17:17 magnolia systemd[1]: Started iio-sensor-proxy.service - IIO Sensor Proxy service.
jun 30 13:17:17 magnolia iio-sensor-proxy[826]: Could not find trigger name associated with /sys/>
jun 30 13:17:18 magnolia iio-sensor-proxy[826]: Buffer '/dev/iio:device1' did not have data withi>
jun 30 13:17:18 magnolia iio-sensor-proxy[826]: Not a switch [/sys/devices/platform/FRMWC004:00/c>
jun 30 13:17:18 magnolia iio-sensor-proxy[826]: Invalid bitmask entry for /sys/devices/pci0000:00>
mirthe@magnolia:~$ monitor-sensor
Waiting for iio-sensor-proxy to appear
+++ iio-sensor-proxy appeared
=== Has accelerometer (orientation: normal, tilt: tilted-down)
=== No ambient light sensor
=== No proximity sensor
=== No compass
^C
mirthe@magnolia:~$ monitor-sensor
Waiting for iio-sensor-proxy to appear
+++ iio-sensor-proxy appeared
=== Has accelerometer (orientation: normal, tilt: tilted-down)
=== No ambient light sensor
=== No proximity sensor
=== No compass
Tilt changed: vertical
Accelerometer orientation changed: bottom-up
Tilt changed: tilted-down
Accelerometer orientation changed: normal
```
This is happening with my FW 12, running Fedora Silverblue 44, as well. I didn’t have the problem on 43. I’ll try to grab similar log outputs when I get a moment.