fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

Mike Rochefort :fedora:

Currently upgrading to @fedora 40 ahead of GA with updates-testing and RPM Fusion enabled... I'll set the flag myself by saying I expect everything to go fine! So much so I'm not even near my system for the next hour; I'm looking forward to going back upstairs and being greeted by a dormant login screen. And yes, an device is involved...

I did this going from F38 to F39 as well... But I still take a BTRFS snapshot ahead of time *just to be safe*.

I'm contemplating changing up my upgrade policy and sticking with just even numbered releases. No reason in particular but to just change things up.

But I do like new and shiny... 🫠

@omenos @fedora I was impatient, I didn't want to wait for KDE Plasma 6, so I upgraded to Fedora 40 on *all* my computers right after @kde made the 6.0 release and it landed in Fedora.

It's *awesome*! :crazy:🥳🤠

@scm @fedora @Conan_Kudo Hello from 40! Upgrade went 99% seamlessly, looks like the only issue was the exact same as when I upgraded to Fedora 39: the NVIDIA kmod built but was just a bit off somehow. Easy fix, though:

sudo akmods --akmod nvidia --kernels $(uname -r) --rebuild --force

After a quick reboot...

@scm @fedora @Conan_Kudo Even with the NVIDIA driver failure, the system gracefully fell back to and let me sign in to the graphical session with two out of three monitors, allowing me to resolve the issue without booting into an alternate kernel.

I'm not 100% sure where the driver issue comes from, but I'm assuming it's due to a short circuit of some sort during the end-of-transaction and first-boot period post-upgrade.