This sort of “bait and switch” is all to common. Hope you can return the card.
I once bought a couple PC’s from a major vendor’s standing offer list. The specs claimed Nvidia graphics (required by our software) but when delivered they did not have any dGPU cards. When I complained, the vendor told purchasing that I was being unreasonable – eventually, however the vendor had to pay a penalty and provided newer model PC’s with Nvidia dGPU’s. Our work was delayed by months and the penalty payment just went to general funds.
That is not fixing, that is ungracefully restarting the computer, you will get the same result but faster if you pressed the reset button (if you have one). It is not a “good enough workaround” because you will lose any unsaved work.
FYI many PCIe wifi cards are basically scams, Intel and mediatek make very small m.2 cards that are meant to be installed under the I/O shield (like mine was) or next to it, either by the user or the OEM. And then you would screw two cheap antennas on two eyelets in the I/O plate and connect those to the little card.
So many wifi PCIe cards (not all, mind you) are just an m.2 to PCIe adapter, with two antennas on the I/O plate. Which means that you are paying an extra for what is essentially, a cheap off-the-shelf card, and a 3€ adapter.
If you ever wish to change card this gives you two options: check if your MoBo has the dedicated m.2 slot (I don’t know if you can put it on the nvme one) or, if your card is actually an m.2 adapter, check if you can recycle the adapter in your “Mercusys card”.
Though from a quick I couldn’t tell if that’s the case for your card. Try to peek under the heatsink.
Ohhh thanks for pointing this out. I went ahead and did the same thing with my asrock motherboard. unsure if it fully worked since this issue has only happened after sitting in suspend for a little bit. Will report back later if it also worked for me.
Nope didn’t work for me unfortunately. It seems like my keyboard lights up my speakers click like the DAC connected to the PC but the screen just stays black no matter what I do. I also have to hold the power til it turns off and then turn it back on again.
I’ve been consistently getting it after updating to kernel 6.11 (no, using the old 6.10 did not resolve it).
To reproduce I simply need to leave Bluetooth on when going into suspend. Turning it off makes the suspend/wake function as normal.
I disabled the MT7922 card in BIOS (as I don’t use WiFi anyways), I also tried changing other parameters to no avail. Only Bluetooth is the culprit for me.
Additionally, turning it on/off in KDE has become very sloppy because sometimes it’s instant, sometimes it briefly turns on before turning off again. It also randomly doesn’t want to connect/disconnect before turning off by itself.
As soon as it connects though, it is very stable and doesn’t crash. The issue seems to be in software/firmware.
I have an AMD AM5 system with both CPU and GPU from AMD.
As far as I know I’m still having the issue as I have seen no proposed fixes or root causes in any of the bugs I’m following. However, one difference between you and me is that moving to the 6.10.12 kernel does eliminate the problem for me. I’m using the workaround of disabling bluetooth now.
I’m also using an AMD AM5 CPU (7950x) and GPU (7900XTX) on an ASUS ProArt 670e motherboard. It seems that many of us are seeing this on AMD systems. So it it somehow related to AMD, or is it just that AMD motherboards tend to use that Bluetooth/Wifi chip? I don’t even really know which component (except the whole kernel) to investigate.
I’m sill having this issue. I’m running a 7700x cpu and 7800xt gpu on an Asroc mother board.
I’m curious if you anyone having these issues as well uses a kvm switch? I have my pc hooked up to a KVM and haven’t tested connecting directly to the monitor yet. I’ll do that tonight though.
I also don’t have a KVM, I connect directly via Display Port. I’ve seen some threads suggesting to manually turn display off before suspending / turning it on before waking — this has no effect for me.
I will try using a motherboard port instead to bypass the GPU, but I doubt it will change things.
When waking the system, I get the KDE login screen with the latest time the system went into suspend (e.g. now is 10 pm and system suspended at 1 pm, I would see 1 pm). The screen is black without a usual background image and the time doesn’t update.
Trying to switch to TTY (using Ctrl+Alt+F keys) does nothing. System doesn’t react to anything.
No KVM here either. I got a large monitor connected through display port to an Nvidia RTX. The same monitor also connected through USB C to act as a hub.
Although fans spin, the computer is completely not awake. It doesn’t respond to SSH connection attempts.
I actually have been distro hopping the last couple weeks hoping to find a distro that didn’t have that problem. I found Popos didn’t have the issue but I didn’t like pop, so now I’m on opensuse which has the same problem if not worse. If that kernel is fixing things for you I may just hop back over to Fedora. It’s been my favorite distro by far
I have the same problem on a PC with AMD AM5 9700X and a Radeon 7800XT on an MSI B650 Tomahawk Wifi. The only workaround for me is to disable Bluetooth before suspending my PC otherwise I’d have to hard reboot it.