[NEWS] Fedora 41 is out!

[markr87]

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.

I agree in your assessment that it appears to be related to petitboot/grub.cfg.  Is there a help page somewhere that shows the proper way to recreate grub.cfg?

[sharkcz]

It should be matter of running

Code: [Select]

grub2-mkconfig --output=/boot/grub2/grub.cfgfrom some kind of rescue environment, eg. after booting Fedora installer ISO with the rescue parameter. IIRC there are versions of petitboot that do not support BLS directly and versions that do support it. So knowing the details about the initrd load failure would be useful. The usual "make backups, etc." applies before doing any changes :-)

[sharkcz]

And the easiest thing should be to check how the boot entry looks like and possibly fix the errors from petitboot by using the "Edit" option.

[markr87]

All three hard drives/OS's have a different version of Grub2.  All three are dated the same day I upgraded Fedora 40 to 41. 

[sharkcz]

for the record, PowerNV aka bare metal systems only use the grub.cfg (or a config file from another bootloader), not the actual grub2 bootloader

[MPC7500]

From the Wiki:

... If you're booting a 64KiB kernel, you may need to blacklist the Nouveau driver to prevent a kernel oops (observed in Fedora 41).

[markr87]

Does anybody know what this is?

None CALLOUT_DEVICE_PATH=/sys/devices/platform/gpio-fsi/fsi0/slave@00:00/raw
CALLOUT_ERRNO=0
_PID=25760

I have 200 of these events all logged on the morning of Nov. 5th.

[tle]

Does anybody know what this is?

None CALLOUT_DEVICE_PATH=/sys/devices/platform/gpio-fsi/fsi0/slave@00:00/raw
CALLOUT_ERRNO=0
_PID=25760

I have 200 of these events all logged on the morning of Nov. 5th.

I wish I could help but this is too my first time seeing this kind of error