[NEWS] Fedora 41 is out!

[atomicdog]

The scp command needs the -o option.
Someone recently on this forum had that problem, it has something to do with new default settings in scp.

[jcsiblesei]

The scp command needs the -o option.
Someone recently on this forum had that problem, it has something to do with new default settings in scp.

Note: Uppercase -O, not lowercase -o. And I think it was this post:

the scp transfer worked after I added the option -O, I found that on a forum: "it an issue with OpenSSH client. Since OpenSSH 9.0, the client uses SFTP protocol by default. To use the legacy protocol, the -O option must be specified."

[markr87]

Thank you @atomicdog and jcsiblesei for the help.  Yes it is an uppercase oh  (O).  My other operating systems are working again, sadly my original Fedora 40 is not booting still.  The drive is not corrupted and is readable so I can get all my data off of it.
The thing I don't understand is pnor was still showing version 2.3.  The only clue it had downgraded was the linux version had reverted to 4.19.  To upgrade the pnor you have to ssh in from another computer and enter passwords, it then deletes the existing and writes the new version.  How did upgrading from Fedora 40 to 41 change my pnor?

[rheaplex]

Chromium is running stably on the latest dnf update on my T2/AMD box. 

[atomicdog]

I don't see how (or why) a Fedora install would change the pnor. There is a write protect switch on the motherboard that will prevent the BMC from writing to the FLASH chips.

[power9mm]

I don't see how (or why) a Fedora install would change the pnor. There is a write protect switch on the motherboard that will prevent the BMC from writing to the FLASH chips.

it doesn't have a WP range by default so afaik flipping the dip switch as it is out of the box won't do anything..

[atomicdog]

Oh, so (after reading the datasheet) the FLASH chip hardware WP isn't enabled by default. It would need to be configured by the BMC or external programmer.

[atomicdog]

A PreRelease of Fedora 42 is available here:
https://kojipkgs.fedoraproject.org//packages/Fedora-KDE-Desktop-Live/42/20250302.n.0/images/Fedora-KDE-Desktop-Live-42-20250302.n.0.ppc64le.iso

[Hasturtium]

Is it likely that I can jump from 40 to 42 without incident? I gave 41 a pass.

[ClassicHasClass]

Probably, but it's always cleaner if you minimize the update delta. 41 has been working OK for me so far. That said, you could upgrade to 41 after 42 comes out, and then immediately upgrade to 42.

[tle]

Fedora 42 is still a bit rough, the whole GCC15's new C23 has introduced quite a number of breaking changes / regressions in many softwares. I am still in the progress of going through all softwares that I am actually using to see if I could get them properly working before the final release day. I greatly welcome extra hands from the community in beta testing

[Hasturtium]

Now I’ve been bitten by the gdm Xorg snafu in F41. Managed to squirm into Gnome Classic, switched the display manager to lightdm, rebooted, and the system now only lets me into the onboard video via Gnome Classic and Wayland. What’s the solution here? I’m about this close to just switching to RHEL 10 when it lands.

[ClassicHasClass]

I realize this sounds like a non-solution, but the solution for me is to textboot and bring up X11 (or, if I'm feeling masochistic, Wayland) manually -- no display manager at all.

[Hasturtium]

I realize this sounds like a non-solution, but the solution for me is to textboot and bring up X11 (or, if I'm feeling masochistic, Wayland) manually -- no display manager at all.

Honestly, that sounds fine. In days of yore (read: Slackware on x86) I'd just change the runlevel at boot; what's the approved methodology in systemd-land?

[ClassicHasClass]

Point the symlink /etc/systemd/system/default.target to /lib/systemd/system/multi-user.target and reboot, and it should come up with a text console login. Log in, do a startx (assuming your .xinitrc is configured) and away you go.