weird. yeah I’ve triple checked spelling, no idea why it wouldn’t work the same. hopefully someone knows.
1 Like
Is it showing up in your /etc/default/grub ? It should be on the line starting with GRUB_CMDLINE_LINUX= .
for me it says:
GRUB_CMDLINE_LINUX =“nomodeset rhgb quiet module_blacklist=hid_sensor_hub”
@junaruga It’s live; Fedora 37 Installation on the Framework Laptop - Framework Guides
Thanks!
4 Likes
Thanks! I updated the first comment with the guide like the Fedora 36 thread. Just in case as the first comment is a wiki, you can edit it too.
2 Likes
Is anyone else unable to launch the newest version of VS Code/Codium Insiders on Fedora 37? Upgraded to a new nightly build of Codium and then upgraded from 36 to 37, not quite sure which one is the culprit. Everything ran great previously. From Codium logs:
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Can we get this post pinned, as Fedora 37 is now the latest stable version of Fedora?
I have just gotten my framework laptop with a fresh install of fedora 37 workstation. I have followed the guide and thought I would gather some thoughts and tips for others to save a lot of googling.
General pains.
The constantly freezing and stuttering after waking from suspend has been discussed on these forums. I can confirm I have managed to fix it for me at least with the upgrade to 6.0.9 Kernel and disbaling i915 pcr, maybe with the new kernel the pcr no longer needs to be disabled. Ill test later.
Blurry text with fractional scaling
Like others, I have found 125% to be the ideal size however this makes many legacy apps have blurry text. This mainly affects electron apps I have found, and some legacy gtk apps like VLC. The solution is to run apps in wayland, This works for some electron apps or is not possible in some native apps.
Each app will have its own quirks, to name a few
Chrome wayland, no text scaling on menu items, requires legacy gtk for theme.
1password wayland, no window decorations, legacy theme, still sometimes blurs
Slack, wont start approximately half the time
A much better solution is to not force wayland but instead use the tweak tool to set font to 1.25 and leave the display scaling at 100%. This works for most situations except chrome.
If you however run chrome in X11 (Default) then the --force-device-scale-factor=1.25 launch param works and you get a good looking chrome.
Its worth noting that many apps “just work” particularly all the bundled software like Firefox
No hibernation?
I just switched over to Fedora recently and noticed there is no hibernation. This is kind of a big deal considering the Framework’s problems with suspending (at least on my Batch 3, i5 11 gen). Any suggestions for saving battery when I close the lid?
1 Like
I recommend looking at this
This as well, which I’ve been using from 35-36: Fedora 36 on the Framework Laptop - #38 by Michael_Wu
I haven’t upgraded to Fedora 37 yet so it’s untested there, though I plan to in a week or two.
Edit: upgraded to 37 and my hibernation setup still seems to work. I tried un-blacklisting intel_ish_ipc but that still seems to be an issue, so I added it back.
1 Like
If this is of any value to anyone:
Here’s what I ended up with. 11 hours suspend on each, no external monitors attached, no applications running at suspend.
Fedora 37 is 81%, TLP, (Gnome power profile disabled), 2 USB C, 1 hdmi, 1 DP. 12th Gen. s2idle deep.
Pop OS 24.04 at 61% system76-power 1 USB C, 1 hdmi, s2idle deep.
Ubuntu 22.04 at 89% TLP (Gnome power profile disabled), 1 USB C, 1 hdmi, s2idle deep.
4 Likes
Thanks for your work Matt.
Looks like kernel 6.0.9 has come down into the Fedora 37 normal updates channel, I just got it. Fingers crossed this version is a stability upgrade.
Just got my first hard freeze on Fedora 37 on kernel 6.0.9. I am not using enable_psr=0 . This is the first freeze I have had in over a week. It occured as it usually seems to for me while opening settings and using a bluetooth mouse.
Update: I was thinking about this and realized it always happens when the bluetooth mouse is coming out of a suspended state. Testing some additional changes in TLP to see if removing bluetooth devices from autosuspend will help. The reason I am gtrying this is because in all of my searching I am not seeing this issue on desktop processors using the iGPU. Desktops usually don’t use powersaving features, all the problems seem to be occurring on mobile chips and even that without real consistency. So perhaps this freezing is directly related to how an individual system has powersaving features implemented. Even PSR is a power saving feature. Anyway, I guess I will know the next time it hard freezes, if I am barking up the wrong tree. Also none of these freezes have happened on battery power where I don’t use bluetooth, and always have it disabled.
I just did a fresh install of Fedora 37 and noticed that there are duplicate entries when I look at the boot menu, is this normal?
Here is what I get from efibootmgr:
Boot0000* Fedora HD(1,GPT,869c52f0-6e68-47f8-96f4-a21272df116c,0x800,0x12c000)/File(\EFI\fedora\shim.efi) File(.䍒)
Boot0001* EFI USB Device (USB DISK 3.2) UsbWwid(13fe,6500,0,0700185D2CA32E0)/HD(2,GPT,18f1bb95-9d45-4961-bac6-fd546147cf9c,0xfa800,0x32000)RC
Boot0003* Fedora HD(1,GPT,869c52f0-6e68-47f8-96f4-a21272df116c,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
I have secure boot enabled, maybe related to that?
This is normal. Also look at the difference at the end of the line. They are not really duplicate entries.
It’s interesting because I previously had F36 installed and only had the single entry.
I can select either option using the F12 one time boot menu and they both boot successfully, so I tried deleting the first entry using efibootmgr -b 0000 -B and it was recreated at the following boot! So it looks like the shim.efi entry is auto created by the Framework firmware somehow, perhaps this is what the File(.䍒) signifies in my efibootmgr output?
Interestingly, I also noticed that the Fedora USB installer (created using Fedora Media Writer) now shows up as “linpus lite” on the Framework boot menu, so maybe some strange behaviour to do with a firmware upgrade? (last install of F36 was on v3.07, now on v3.10)
I created a small step-by-step guide how to enable hibernation with enabled secure boot and full disk encryption (luks) decrypting over TPM. Check here: Fedora 36 & 37: Hibernation with enabled secure boot and full disk encryption (fde) decrypting over tpm2
3 Likes