GRUB_DEFAULT=saved is indeed in /etc/default/grub. The line GRUB_SAVEDEFAULT=true is not. As far as I understand, this does not automatically change the default kernel to the newest version after installation, correct? That is the behaviour I would expect, based on earlier experience with distros as openSUSE and Debian. Are you saying that this is not the expected behavior on Fedora?
SAVEFEAULT is the value that will retain the last used. It is indeed not set by default so you will need to add if if you want that behaviour.
OOTB behaviour should be to select the most recently installed kernel based on the kernel package script trigger when installed from dnf. My guess is this failed or didn’t run or you downgraded a kernel at somepoint.
Right, that confirms that my FW is not showing expected behaviour. It’s a fresh F39 install on a new AMD Framework, so I don’t know why it doesn’t work. I’ll pay more attention to the log on the next kernel update to see if there’s anything going wrong. For now I’ll just set it manually.
Thanks for the help!
1 Like
Same here; I just updated kernel to 6.6.2-201.fc39 which just hit testing, so now I have these installed:
6.5.11-300.fc39
6.5.12-300.fc39
6.6.2-201.fc39
grub was still defaulting to 6.5.12-300.fc39 on reboot (and when that was installed to 6.5.11-300.fc39 and so on).
$ cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_SAVEDEFAULT=true
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.luks.uuid=... rhgb quiet amdgpu.sg_display=0"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
This being my first clean Fedora install in ~ 2 years, I can’t remember if there’s some other step I need to take to bring back the “default to newly installed kernel” behavior.
1 Like
What is the output of grubby --default-index ?
and what is the output of : sudo ls /boot | grep vmlinuz
?
Reference: Working with the GRUB 2 Boot Loader :: Fedora Docs
IIRC scripts just enumerate based on the numerical versioning of vmlinuz entiries.
Grubby is the supported tool in Fedora for manipulating things (although I kinda give it a wide berth because I’ve had issues with it in the past).
The config for wether new kernel-pkgs should become the default is at /etc/sysconfig/kernel
Hmm, that file didn’t exist. I created it with contents as shown in the doc you linked:
# UPDATEDEFAULT specifies if new-kernel-pkg should make
# new kernels the default
UPDATEDEFAULT=yes
# DEFAULTKERNEL specifies the default kernel package type
DEFAULTKERNEL=kernel-core
I can’t say I remember having to manually create that config file before in the 10 or so years I’ve used Fedora, is it a known recent change?
2 Likes
That’s the same I noticed in my first posts in this topic: /etc/sysconfig/kernel is completely missing. Have also manually created it now; let’s see if that resolves the issue.
Can confirm that restoring the /etc/sysconfig/kernel file as above resolves the issue of the default kernel not updating after upgrade. 
1 Like
Odd this happened, delighted it’s resolved.
Hey all. Just to say the installation was very smooth on AMD 13, and it was surprising not to do any tweak or anything to have everything working. I followed just this page Fedora 39 Installation on the Framework Laptop 13 - Framework Guides and this one https://github.com/FrameworkComputer/linux-docs/blob/main/Fedora39-amd-fw13.md
There is just one thing slightly confusing on the Github page @Matt_Hartley is that it is hinted that activating the fractional scaling is password protected here https://github.com/FrameworkComputer/linux-docs/blob/main/Fedora39-amd-fw13.md#step-2---if-you-want-to-enable-fractional-scaling-on-wayland I quote, « * Then press the enter key, user password, enter key.» In my experience, the command line just worked without any password and there was then a dropdown of scaling in my screen configuration screen.
Another thing slightly confusing is in battery saving instructions, it’s clearly said «don’t use TLP and use PPD for AMD» but it isn’t said what is is PPD and how to use it. As I understand it, it’s just the default energy deamon already installed, you have nothing to do except go on the upper right corner and chose your energy profile.
Oh, yes, four bugs:
- I had yersterday a graphical weird glitch coming back from sleep, the whole desktop was unusable, white patches and lines on parts of GNOME interface, I had to reboot. Hope it doesn’t come back.
- blurrry apps with fractional scaling at 125% (really noticeable on electron apps like Slack)
- The automatic brightness adjustement keeps doing adjustments and it’s quite annoying. It’s like I’m not moving, there isn’t any change of luminosity in the room, and it goes up and down. Not constantly, but enough so it annoys me, because each level change is very noticeable, it goes by quite huge steps I find.
- the keyboard layout cannot be shown if you go in the upper right corner, click on keyboard layouts, and then on «display keyboard layout» (like, show the image of it).
Likely this is a feature of them using XWayland by default. Have a look here: How to run Electron apps under Linux's Wayland session like a pro - DEV Community
Jep, that was the same for me and it irritated me enough to disable it (Settings → Power → Automatic Screen Brightness)
This works for me:
Probably because I’m using a weird layout : Bépo (afnor version) – it’s the French equivalent of Dvorak keyboard. It was proposed out of the box during the installation process, but can’t show the layout if I have a doubt about a key. Not really important. First time I hit the button, there was an error message that said there was an automatic report done, and now nothing shows.
In fact my main doubt about keyboard layout (I ordered the clear keyboard without any marking) is not about the usual keys, but about the Framework function keys (volume, brightness, scroll up and down, screen capture, etc).
Dont worry. its enabled by default. You could check service status by
sudo systemctl status power-profiles-daemon.service
this might help you
sudo grubby --update-kernel=ALL --args=“amdgpu.sg_display=0”
Also if you have 64gb ram, try switch in bios uma_auto to uma_gameoptimized
Just got my Batch 11 AMD 7840U in yesterday, installing Fedora 39 from the Framework instructions couldn’t have been easier 
Didn’t change anything related to battery or sleep, and suspended it overnight by closing the lid. Battery dropped just 4%, from 90% to 86%. Never had this much out-of-the-box success with Linux suspend before. Great work to everyone involved!
1 Like
Something else I’m not sure I should do, is using RPM Fusion to swap drivers.
I’ve followed the instructions here Howto/Multimedia - RPM Fusion
Including this:
sudo dnf swap mesa-va-drivers mesa-va-drivers-freeworld
sudo dnf swap mesa-vdpau-drivers mesa-vdpau-drivers-freeworld
I think if this is necesary to correctly use hardware and video acceleration, it should be included in Framework guides. I find it unfortunate that we have to resolve to hacks and external repositories to have video codecs and video acceleration working, just because of a single country (the USA), this has been resolved for a while in Ubuntu and Debian, but well…
4 Likes
I wish I could say this worked for me, but unfortunately GRUB still seems to be defaulting to the oldest kernel for me.
$ rpm -qa kernel
kernel-6.5.6-300.fc39.x86_64
kernel-6.6.4-200.fc39.x86_64
kernel-6.6.6-200.fc39.x86_64
$ uname -r
6.5.6-300.fc39.x86_64
$ cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=“$(sed ‘s, release .*$,g’ /etc/system-release)”
GRUB_SAVEDEFAULT=true
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT=“console”
GRUB_CMDLINE_LINUX=“rhgb quiet”
GRUB_DISABLE_RECOVERY=“true”
GRUB_ENABLE_BLSCFG=true
$ cat /etc/sysconfig/kernel
UPDATEDEFAULT=yes
DEFAULTKERNEL=kernel-core
/etc/sysconfig/kernel also did not exist for me, so I had to create it as above, but I’m still booting to 6.5.6 by default, despite the fact that 6.6.6 is installed. Any help?
Next time the kernel is updated the default kernel should be set to the latest installed one. As far as I understand, the sysconfig file is only used when updating your system, so I think you just need some patience . In the meantime you can manually change the default using grub-set-default.
Also, welcome to the community! 
1 Like
Thanks, I appreciate that! Unfortunately, it seems grub-set-default doesn’t work for me. I’m getting sudo: grub-set-default: command not found
That’s right. It’s grub2-set-default now, my bad 
sudo grub2-set-default 0
worked! thank you so much!
1 Like