Aliases are fine, just place them in your .bashrc and make sure they aren’t going to conflict with any packages you have installed/will install. The only potential downside is if you install a package that adds an executable to your path with the same name as an alias, but you can just change the alias if that’s the case. Since dnf/yum aren’t installed in the atomic versions, you could even make an alias with one of those (and if you’re in a toolbox, just use the one you don’t have an alias for when installing packages). That guarantees you won’t have a conflicting executable name from newly installed packages, and I’d say it makes a bit more sense than sys, but as long as you can remember it, it shouldn’t realistically matter; just a suggestion.
Since kernel 6.6.8, I’ve been having suspend issues. Sometimes, a suspend request would result in the screen blanking, but the power LED remains lit. Other times, suspend would occur, but randomly, the system wakes itself (power LED is solid white), and eventually the fans turn on to full speed and the system gets very warm. A long press of the power button shuts it down, and it reboots normally. After a bit of experimenting, the bad suspend only occurs on lid close. Suspend works normally if a suspend is requested by pressing the power button. This behaviour has been confirmed by other Asus G14GA402 users, as well one Asus TUF Gaming A16 Advantage Edition FA617NS user. There was no issue with suspend on kernel 6.6.7 and lower. The issue has persisted through 6.6.8/9/11/13 and 6.7.2.
Then I encountered this second bug, which is totally reproducible.
Summary of QCNFA765 ath11k problems kernel-6.7.4
The current 6.7.x suspend crashes are intertwined with the long standing packet loss and latency problems we’ve been seeing with QCNFA765 Linux ath11k.
Kernel 6.4.12-6.6.14 all had the same problem where you need the iw dev wlp1s0 set power_save off workaround to prevent crippling packet losses and slow speeds. With the power_save workaround applied this wifi adapter was mostly tolerable.
Kernel-6.7.3 broke suspend.
Kernel-6.7.4 included a partial fix.
I think I have this issue since 2024-02-06 when this was published in stable.
Do you have a rough guide of how frequently you can hit this issue in a given timeframe, like over the course of a week?
I have the gen 2 version of this notebook (Cezanne) also with Fedora 39 + GNOME.
One quick thing; I know this is a recent issue for you, but just want to confirm that you have the proper system sleep mode selected in UEFI. I presume (but cannot confirm if) the same option is available on your platform, but you will find it by hitting Enter on boot, and then F1 when prompted. Once in UEFI head to > Power settings > Sleep mode.
Aside from that (and depending on how intermittent this), I’d try temporarily reverting the kernel for a few sessions via grub on boot
Late reply and I haven’t used the KDE spin, only Gnome so I can’t compare the two.
I also have a Nvidia GPU (3080) and Wayland support isn’t great for me unfortunately. Electron apps like VSCode and Steam have visual glitches when navigating menus and resizing the windows and fullscreen games flash in a way that could give someone an epilepsy attack. I’m also using X11 as a workaround and do worry about F40 dropping support.
Due to issues with the bootloaders, the best way to achieve this is to install fedora after installing windows. I’d suggest backing up your existing data, wiping the entire ssd, and reinstalling everything starting with Windows. Boot into Windows after installation and shrink your user disk, then repartition the ssd for Fedora and install it.
It sounds like a lot, but you’ll save yourself a bunch of heartache. Short cuts are the long way in this case.
It’s pretty tough to see RH’s recent moves lately. I’ve always looked at Fedora as a project of immense benefit to RH, and RH itself being of a tremendous benefit to humanity as a whole through its sponsorship of Fedora. The recent moves on RH’s part have been troubling so as to erode the trust of RH in general.
Well, nothing has changed on the Fedora front. We are intertwined with Red Hat, but we are still always going to do our own thing. If forced, Fedora community would splinter and fork probably.
Fedora Linux: It's your Operating System.
Hot