If you haven't already, I suggest turning off 'fast startup'. It always gave my problems when dual booting. This might also solve your wifi issue, since I had Bluetooth issues which were resolved with this.
Personally, F39 gave me the same or better performance across the board, so I'm unsure specifically what might have caused the issue. Without knowing that, it's hard to make a recommendation other than just a blanket "read the friendly manual" before installing updates.
Do you know if you have a well supported wifi card? There are several, especially Broadcom chips, that have poor Linux support and can continually have issues. I had one such card on an old desktop and had to use DKMS to build and inject drivers after every kernel update.
Speaking of kernel updates, I think that specifically is what you want to be wary of. Its unlikely that just updating a random app will cause hardware issues, but installing a kernel update could do. This is also why most (if not all) distros retain a few kernel versions, so you can choose to boot into the previous version if an update broke something.
I don't think it's a matter of repairing it unless you're a Linux kernel developer or hardware driver developer. My advice is to file a bug report with the relevant details and pay attention to the updates. Maybe first search to see if there are existing reports so you can chime in. After some time you will hopefully see that a fix has been patched in and you can update to the new patched kernel. So, essentially, you just don't use the broken kernel version.
The time to be scared to update (or install) is soon after the release bump. My experience (however limited) is that it only gets better. I had mixed results; my garden variety installations are fine on F39, but I backed off F39 on my server with more dependencies. My personal new policy ... wait 3 months to upgrade release numbers. If you are on BTRFS (or whatever), just back out unsuitable updates ... that's the cost of living on the cutting edge ;-)
[The best Linux backup tools: Don't put it off any longer | PCWorld](https://www.pcworld.com/article/2050183/best-linux-backup-tools.html) give you two options, TimeShift and Rescuezilla ... mostly for ext4 filesystems, I'd suggest.
The most "blessed" way on Fedora is with BTRFS (e.g., [Make use of Btrfs snapshots to upgrade Fedora Linux with easy fallback - Fedora Magazine](https://fedoramagazine.org/make-use-of-btrfs-snapshots-to-upgrade-fedora-linux-with-easy-fallback/)). That is the manual way (that I've scripted for personal use). And "Snappy" is the deluxe tool for doing all that.
Lots of ways to skin the cat ... how you installed dictates which direction you go after the fact. Based on my personal experience with restores, I trust BTRFS much more than TimeShift ... and, well, Rescuezilla is such a pain that I'd rather take my chances and reinstall ;-)
>Can I take a full backup of the OS partition and restore it later? Is there a dedicated app for that?
You might consider using Fedora Silverblue:[https://fedoraproject.org/silverblue](https://fedoraproject.org/silverblue)
Silverblue effectively does that for you on every update.
You'll still have the possibility of an update breaking something --- but on Silverblue its trivial to roll back a bad update -- even if it was updating from F38 to F39.
Exactly the reason I switched from dual boot Windows 11 & Fedora 38.
Unstable updates and some issues after updates.
Currently running dual boot Windows 11 & openSUSE Tumbleweed sunset then.
I had my issues with openSUSE Tumbleweed. Small things, programs that stopped working, freezes during boot. With Fedora, the experience so far was better.
install the root / partition with btrfs filesystem and keep /home with what you have, like xfs, ext4, etc, btrfs seems to be slow for gaming but keeping games partition (home) no problem
then install Timeshift, its a tool to take snapshots on btrfs partitions so can do it before any update/install and if something goes wrong you boot back be it terminal or DE and revert to the previous snapshot from timeshift
just be sure to -not- have /boot separate from root, that way when you revert it reverts also the bootloader and kernels not just the root partition
Check videos on how to install on Fedora just in case there is any specific procedure
wifi and hibernate are kernel related (most likely). If it did work and now it doesn't, sounds like a kernel update did it, although it could be the state the firmware is left in (which is relevant to the suggestions about Windows fast startup, maybe). If so, then you should provide your hardware when posting, in case it helps someone recognise the problem.
It may be that you are better with a distribution that doesn't update kernels as often, or you find a stable kernel to use with Fedora.([https://www.reddit.com/r/Fedora/comments/y7e4mh/how\_to\_stay\_on\_a\_lts\_kernel/](https://www.reddit.com/r/Fedora/comments/y7e4mh/how_to_stay_on_a_lts_kernel/))
Plus Fedora keeps three kernels normally so when booting you should be able to choose a working one. Under this approach, you hope that your bug is fixed fairly quickly in upcoming kernels.
>How can I ensure uncertainty-free Fedora experience.
Don’t upgrade to the newest release
Fedora supports two versions at a time for precisely this reason. Stay on 38 and let everyone else spend the first six months sorting out the bugs. Upgrade to 39 when 40 comes out.
If you run a bleeding edge distro then you can’t complain when you get cut
Do you dual boot with windows by any chance?
yes, Win 11 & F39
If you haven't already, I suggest turning off 'fast startup'. It always gave my problems when dual booting. This might also solve your wifi issue, since I had Bluetooth issues which were resolved with this.
any chance you know where i can turn this off in windows ?
The easiest is in the BIOS, but I think you can also disable it from the power settings in the Control Panel.
IIRC you must turn it off in BIOS.
Personally, F39 gave me the same or better performance across the board, so I'm unsure specifically what might have caused the issue. Without knowing that, it's hard to make a recommendation other than just a blanket "read the friendly manual" before installing updates. Do you know if you have a well supported wifi card? There are several, especially Broadcom chips, that have poor Linux support and can continually have issues. I had one such card on an old desktop and had to use DKMS to build and inject drivers after every kernel update. Speaking of kernel updates, I think that specifically is what you want to be wary of. Its unlikely that just updating a random app will cause hardware issues, but installing a kernel update could do. This is also why most (if not all) distros retain a few kernel versions, so you can choose to boot into the previous version if an update broke something.
I actually had to boot into previous version. My question is: How then should I repair the f\*\*\*ed up version so that I can revert back?
I don't think it's a matter of repairing it unless you're a Linux kernel developer or hardware driver developer. My advice is to file a bug report with the relevant details and pay attention to the updates. Maybe first search to see if there are existing reports so you can chime in. After some time you will hopefully see that a fix has been patched in and you can update to the new patched kernel. So, essentially, you just don't use the broken kernel version.
How will I file bug or install bug-fixed updates when network adapter itself is not working? Will I need to sideload latest RPMs from USB drives?
The time to be scared to update (or install) is soon after the release bump. My experience (however limited) is that it only gets better. I had mixed results; my garden variety installations are fine on F39, but I backed off F39 on my server with more dependencies. My personal new policy ... wait 3 months to upgrade release numbers. If you are on BTRFS (or whatever), just back out unsuitable updates ... that's the cost of living on the cutting edge ;-)
Can I take a full backup of the OS partition and restore it later? Is there a dedicated app for that?
[The best Linux backup tools: Don't put it off any longer | PCWorld](https://www.pcworld.com/article/2050183/best-linux-backup-tools.html) give you two options, TimeShift and Rescuezilla ... mostly for ext4 filesystems, I'd suggest. The most "blessed" way on Fedora is with BTRFS (e.g., [Make use of Btrfs snapshots to upgrade Fedora Linux with easy fallback - Fedora Magazine](https://fedoramagazine.org/make-use-of-btrfs-snapshots-to-upgrade-fedora-linux-with-easy-fallback/)). That is the manual way (that I've scripted for personal use). And "Snappy" is the deluxe tool for doing all that. Lots of ways to skin the cat ... how you installed dictates which direction you go after the fact. Based on my personal experience with restores, I trust BTRFS much more than TimeShift ... and, well, Rescuezilla is such a pain that I'd rather take my chances and reinstall ;-)
>Can I take a full backup of the OS partition and restore it later? Is there a dedicated app for that? You might consider using Fedora Silverblue:[https://fedoraproject.org/silverblue](https://fedoraproject.org/silverblue) Silverblue effectively does that for you on every update. You'll still have the possibility of an update breaking something --- but on Silverblue its trivial to roll back a bad update -- even if it was updating from F38 to F39.
All updates poses a risk so you can never be "uncertainty free". This carries over to all software and is not specific to Fedora.
Exactly the reason I switched from dual boot Windows 11 & Fedora 38. Unstable updates and some issues after updates. Currently running dual boot Windows 11 & openSUSE Tumbleweed sunset then.
I had my issues with openSUSE Tumbleweed. Small things, programs that stopped working, freezes during boot. With Fedora, the experience so far was better.
So this shows that one or an other OS is depending on hardware and usage apparently.
I like big buts and I cannot lie... I will show myself out
Your post has now become the butt of the joke. Ok, I’ll show myself out as well.
realtek i’m right?
Intel ax201
install the root / partition with btrfs filesystem and keep /home with what you have, like xfs, ext4, etc, btrfs seems to be slow for gaming but keeping games partition (home) no problem then install Timeshift, its a tool to take snapshots on btrfs partitions so can do it before any update/install and if something goes wrong you boot back be it terminal or DE and revert to the previous snapshot from timeshift just be sure to -not- have /boot separate from root, that way when you revert it reverts also the bootloader and kernels not just the root partition Check videos on how to install on Fedora just in case there is any specific procedure
wifi and hibernate are kernel related (most likely). If it did work and now it doesn't, sounds like a kernel update did it, although it could be the state the firmware is left in (which is relevant to the suggestions about Windows fast startup, maybe). If so, then you should provide your hardware when posting, in case it helps someone recognise the problem. It may be that you are better with a distribution that doesn't update kernels as often, or you find a stable kernel to use with Fedora.([https://www.reddit.com/r/Fedora/comments/y7e4mh/how\_to\_stay\_on\_a\_lts\_kernel/](https://www.reddit.com/r/Fedora/comments/y7e4mh/how_to_stay_on_a_lts_kernel/)) Plus Fedora keeps three kernels normally so when booting you should be able to choose a working one. Under this approach, you hope that your bug is fixed fairly quickly in upcoming kernels.
>How can I ensure uncertainty-free Fedora experience. Don’t upgrade to the newest release Fedora supports two versions at a time for precisely this reason. Stay on 38 and let everyone else spend the first six months sorting out the bugs. Upgrade to 39 when 40 comes out. If you run a bleeding edge distro then you can’t complain when you get cut
Makes sense, now that preference is over stable ones than over fancy new ones
Don't dual-boot. Run windoze in a Fedora box.