[NEWS] Fedora 41 is out!

[tle]

"Fedora 41 features a number of package updates like going to LLVM 19, LXQt 2.0, Python 3.13, DNF5, RPM 4.20, PyTorch 2.4, AMD ROCm 6.2, GIMP 3.0 (near final form), replacing Redis with Valkey, and many others. Fedora 41 also features interesting features like self-encrypting drives support within the Anaconda installer, Intel IPU6 camera support for newer Intel Core laptops, Wayland-only GNOME Workstation media, NVIDIA driver support on Secure Boot systems, the new fedora-repoquery tool, a new alternative spin for Fedora Miracle, and more."

More details on changeset could be found at https://fedoraproject.org/wiki/Releases/41/ChangeSet

It's yet another great version from Fedora. Everything runs as expected for PPC64LE arch

[MauryG5]

I upgraded to 41 and boom, after having installed everything correctly, when booting from petit boot it tells me an initrd error and Fedora doesn't start anymore... It's incredible how an upgrade can actually break everything, it's never happened to me with anything. But unfortunately you have to expect anything from Fedora, luckily I switched to Debian a long time ago as my first choice because honestly Fedora always disappoints me, every time I use it it always has a thousand problems and now it's even completely broken after the upgrade, a real disgrace with all due respect!

[Hasturtium]

I look forward to the upgrade, pending any weird issues that crop up. I may defer to ClassicHasClass's probable writeup before taking the plunge.

[MauryG5]

Guys I confirm that currently Fedora 41, at least as far as I'm concerned, has a large system bug that does not even allow the start. After updating mine and lost it, I reformed everything and redo the installation from scratch. Well even by doing this, at the time of the start from Petit Boot, Initrd and end error does not start. So watch out for those who want to update ...

[ClassicHasClass]

What exactly appears on screen? If you boot it from the BMC web interface, what appears on the virtual serial port output?

[MauryG5]

Exactly what I wrote in the previous two posts... From petit boot, you select a version of Fedora 41 with any Kernel that is installed and it immediately writes "INITRD error and does not boot... I'm sure that it is not a Kernel problem since it does it with any you use and I had installed 3 other Kernels in addition to the last one that until the previous use with Fedora 40 worked perfectly. The problem is at startup, at boot...

[markr87]

I can confirm MauryG5's issue.  When trying to update from 40 to 41 via console it would not install due to a "watchman" issue.  After being pestered via notifications to update I decided to give "Software" a shot at the update.  It installed 41 but now NO version of Fedora will load.  "Error loading initrd" is the error given.  Even after rolling back via Timeshift I get the same error.  On a side note that may be related, my openSUSE will start but is very slow and will not fill windows.  For example if I open any file browser I get the window outline but it is filled with the desktop image and no radio gadgets.

[MauryG5]

Exactly, this time Fedora has outdone itself with a bug so big that it compromises the entire distro. I strongly advise you not to update because you will lose everything if you do not have another distro installed on another hard disk to be able to download all the files you may need... Be very careful!

[markr87]

What exactly appears on screen? If you boot it from the BMC web interface, what appears on the virtual serial port output?

[img/]https://ibb.co/mqy2ps8[/img]

[sharkcz]

Thanks for the screenshot. Can you enter the shell and inspect the system logs? Is only Fedora 41 initrd affected and F-40 would boot OK ? Is there a significant size difference between initrd sizes of F-40 and F-41?

[markr87]

All Fedora versions on sda and sdd as seen in the screen shot fault with initrd.  Since that screen shot was taken I have used Timeshift on sdd to rollback to before the F41 install.  Same results.  I wiped out sda and installed F41 from scratch, same result.  Then I tried to install F40 from scratch on sda.  The results of this endeavor are in this screen shot.


https://ibb.co/xfVBny3

I will try to get system logs later today.

[rheaplex]

On my T2 v/AMD graphics, I upgraded to F41 from the terminal in Gnome via the dnf plugin as described on the Fedora website.

After restarting, the screen went blank for more than five minutes, during which time the machine didn't show up on the network. From experience I knew not to restart. I played a game of chicken with myself regarding connecting to the BMC via ethernet, which I won.

Eventually the login manager appeared.

I don't know if this will help anyone else, but it was my experience. 

[markr87]

Not sure why my pics don't post directly, but I can't seem to attach files either.  I get this error.

"The upload folder is full. Please try a smaller file and/or contact an administrator."

My file is well under the limit.

[ClassicHasClass]

On my T2 v/AMD graphics, I upgraded to F41 from the terminal in Gnome via the dnf plugin as described on the Fedora website.

After restarting, the screen went blank for more than five minutes, during which time the machine didn't show up on the network. From experience I knew not to restart. I played a game of chicken with myself regarding connecting to the BMC via ethernet, which I won.

Eventually the login manager appeared.

I don't know if this will help anyone else, but it was my experience. 

That's typical and expected. You can tail the log by logging in as root on another VTY. I didn't get a chance to update the Blackbird yet, but I plan to do so no later than the Thanksgiving long weekend.

[sharkcz]

My upgrade from F-40 to F-41 on a bare metal IBM LC912 (aka Boston) went OK, no problems booting after the upgrade. But I spoke with a colleague today and he reminded me some old(er) issues that were related to grub.cfg not being compatible with the parser in petitboot or grub-mkconfig failing to run (depends on petitboot / firmware version). I think that's what we are seeing here. If that's true, then the fix should be to recreate grub.cfg.