[NEWS] Fedora 37 has arrived!

[tle]

Source: https://fedoramagazine.org/announcing-fedora-37/

To me it is a great release because many annoying issues such as stuttering graphic performance with mutter is gone. Plus many packages are now more up-to-date which really helps with getting amdgpu driver running for RDNA2-based GPU.

Having said that it sucks to know that Fedora no longer enable hardware decoding for Mesa, I have to manually revert the patch to compile my custom RPMs.

[tle]

Another review from our beloved member https://www.talospace.com/2022/11/fedora-37.html

[tle]

Folks, if you want to revert the codec mesa change, here how you could do it

Code: [Select]

fedpkg clone -a mesa
cd mesa
git checkout origin/f37
git revert 94ef544
sudo dnf builddep mesa.spec
fedpkg local
If you use ffmpeg, please also re-compile to support HEVC/H.265 code:

Code: [Select]

# Install RPMFusion Free Repo first
sudo dnf install x265
fedpkg clone -a ffmpeg
cd ffmpeg
git checkout origin/f37
sudo dnf builddep ffmpeg.spec
fedpkg local --with x265

Alternatively, the better way is to use RPMFusion:

Code: [Select]

sudo dnf install https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm
sudo dnf install https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
sudo dnf swap ffmpeg-free ffmpeg --allowerasing
sudo dnf swap mesa-va-drivers mesa-va-drivers-freeworld
sudo dnf swap mesa-vdpau-drivers mesa-vdpau-drivers-freeworld


[sharkcz]

Or you can use mesa-freeworld from RPM Fusion. It should complement the reduced mesa from Fedora.

[MPC7500]

Why was hardware decoding removed as default, compatibility reasons?

[tle]

It is because of licensing. Anything that might pose legal issue to the project is likely being removed

[Hasturtium]

How can I ensure my latest installed kernel runs? I’ve installed updates through kernel 6.0.12, but it’s still booting to 6.0.7 with no other versions showing at the petitboot selection. I used grubby as a walkthrough dictated to change the default kernel but that doesn’t seem to have persuaded petitboot to play ball… and I don’t want hassles whenever they push through kernel 6.1. To say I’m eager to pair the Radeon RX 6600 I picked up with my Power9 is an understatement.

[MauryG5]

What I can tell you about Fedora is that unlike Debian and derivatives, you can't download the Kernel from the classic source and compile it because it necessarily requires its procedure and it necessarily wants its sources.  You must therefore necessarily download from Fedora sources and use their specific procedure.  One of the reasons that prompted me not to use Fedora anymore is precisely this, which represents a limitation for me.  In their sources you can only download the version they say and you can't even use the universal procedure because at a certain point it doesn't work anymore.

[Hasturtium]

I understand that’s an issue, but it isn’t the one I’m running into. dnf has installed multiple kernels, and grubby enumerates them, but only 6.0.7 is enumerated in petitboot, and using grubby to set it to the newest 6.0.12 does nothing. What procedure do I need to follow to get Fedora to enumerate my installed kernels in petitboot?

[DKnoto]

In order for petitboot to see the new kernels you must run the following commands after the update:

Code: [Select]

$ sudo grub2-mkconfig > /boot/grub2/grub.cfg

This situation is due to an error in the /usr/lib/kernel.d/99-grub-mkconfig.install script on lines 28 and 29.
The script expects the Pettitboot version in Num1.Num2.Num3 format and reads the values in CRC1-CRC2 format.

[ClassicHasClass]

What DKnoto said. Same thing bites me on every update. Oddly, though, only on the T2 -- the Blackbird doesn't seem affected.

[DKnoto]

This script gets the Petitboot version number from a file like this:

Code: [Select]

cat /sys/firmware/devicetree/base/ibm,firmware-versions/petitboot
and expects this string to be of the form, for example, 1.8.0 and gets something like this:

Code: [Select]

cat /sys/firmware/devicetree/base/ibm,firmware-versions/petitboot
0ed84c0-p94177c1


[ClassicHasClass]

Right, that's this bug, reported by yours truly: https://bugzilla.stage.redhat.com/show_bug.cgi?id=1921479

It should be fixed, but on the T2 at least, it doesn't seem to be.

[Hasturtium]

In order for petitboot to see the new kernels you must run the following commands after the update:

Code: [Select]

$ sudo grub2-mkconfig > /boot/grub2/grub.cfg

This situation is due to an error in the /usr/lib/kernel.d/99-grub-mkconfig.install script on lines 28 and 29.
The script expects the Pettitboot version in Num1.Num2.Num3 format and reads the values in CRC1-CRC2 format.

This worked a treat, thank you! Once I'm done with some holiday traveling, I will start writing down some of what I've learned in getting Fedora to go my way. Periodically it wants to take several minutes to shut down, and I haven't had any luck looking at console output to see what's making it spin its wheels... but if that's the only wrinkle I run into, I think I'm okay with it.

[ClassicHasClass]

And actually it did it on the Blackbird today when I tried to update it. So I think something regressed.