Same for me. It works on 43 but not on 44 still.
Same here. I just got past Monday my FW12, straight installed Fedora 44 and I think I got it working once. Since then, always from a fresh boot and no matter what I try, screen doesn’t rotate and on-screen keyboard doesn’t show up. Physical keyboard does disable though.
Which DE?
GNOME, sorry
1 Like
It worked for a while for me and then with an update, it didn’t anymore. A remedy is properly explained here:
The problem is apparently that the kernel module pinctrl_tigerlakegets loaded too late for the “lid flip sensor” to be picked up. Reloading the module responsible for detecting the lid flip sensor later does fix the problem:
sudo rmmod soc_button_array
sudo modprobe soc_button_array
I’m not sure if the loading order in fedora is down to luck (explaining why for some updates things worked out) or whether there was a proper fix in fedora that was subsequently broken again. It would be nice if a proper fix would be picked up and/or if someone would find a solution/workaround that persists through kernel updates.
3 Likes
I am not sure if that is the right expectation, but with Fedora being a supported distro I feel like FrameWork should take care of that.
3 Likes
I just checked and it is currently working for me again, lol.
Currently on 7.1.10-200.
I’ve never applied any special fixes. Honestly, I can’t say for sure when it started working again. I haven’t really tried to use tablet mode much in the last few months.
1 Like
I think that’s totally the right expectation.
If I buy a prebuilt with Fedora preinstalled I very much expect auto rotate and tablet mode to work out of the box without any tweaking whatsoever.
I’m pretty sure this will light a fire under both Framework and Fedora to fix the tablet mode issues in Fedora KDE. It’d be silly otherwise.
3 Likes
I tried to use tablet mode this morning. Auto rotate stopped working again. 
2 Likes
The 12 any time you think rotation is gonna work for more than a day:
1 Like
Hm, for the last couple of kernel updates (I am on 7.1.13-200.fc44 now) rotation has worked for me, so I had the impression the module load order was fixed more permanently now. But if people are having mixed results with the standard setup on the same kernel then it would seem the module load order might not be entirely deterministic.
A workaround would be to write a “SUID” script that reloads the soc_button_array module upon login to gnome. The execution upon login can be done by putting a .desktop file in .config/autostart that calls the “SUID” script. That just automates the reloading of the modules in the right order, without having to touch the core system startup configuration.
An alternative is documented elsewhere: instruct dracut to include the modules in the initramfs from which the kernel boots the first time.
I updated again last night and auto-rotate started working again. Honestly, I haven’t been tracking it super close. I don’t flip it into tablet mode that often. It seems like half the time I switch to tablet mode it doesn’t rotate, and the other half it does. It’s not a huge deal for me. I always want landscape mode anyway, so I just rotate the machine. The keyboard and trackpad still turn off, so it’s not a big issue for me. I just chuckle/roll my eyes at the fact that it really is like 50/50 if it will or won’t work.
I do appreciate the tips.
1 Like