Few things:
Another thing to try is download Fedora LiveUSB and test it with that (it will be Wayland). If it works, then you know it’s a config issue with your distro.
Probably a permissions issue somewhere. Logs will be needed.
Sure seems like they have a Linux Appimage right here: https://www.nexusmods.com/app
When this happens, open a TTY by hitting ALT+F2, login, then run top to get a listing of what’s running on your machine. It should should what’s hitting the CPU at the top of the list.
It would also be good to get an idea of your memory situation, so also run free -m.
Start there and report back.
Check the section here that details disabling power management for the WiFi device: https://easylinuxtipsproject.blogspot.com/p/speed-mint.html?m=1#ID10
You also need to make sure you disable the internal card as well.
Fuck yeah! Good job, NYC 👍
Yeah, if you want to understand the dual-edged sword of Broadcom, just go look at the hardware support matrices of open source router platforms. NONE will support Broadcom, because they want to nab licensing for their drivers. You can’t install a working ddrt, tomato, opensense, openwrt…etc on ANY Broadcom hardware platforms, but the manufacturers using them still are many.
It’s finally starting to subside, but there was a decade where they ruled the wireless space. They refuse to capitulate on the open drivers issue though, it’s insane.
That’s less likely to be the chipset, and more likely to be crap hardware. The chipset wouldn’t cause PCIe disconnect/interrupt issues, but shitty power handling in a laptop would. Can I wager it happened when plugging/unplugging power or ramping up CPU or GPU util? That was a thing on those Lenovo convertibles for years, but they did throw that shoddy consumer hardware into the Thinkpad line which made it go downhill fast.
Secure Boot has nothing to do with, Broadcom keeps their drivers completely closed, and just doesn’t support this chipset anywhere except Windows.
USB dongles would work fine, but probably cost more than an internal module. It sounded from your post like you’re fine with opening the machine and navigating the internals, so swapping the WiFi module would only take 5m.
Just stay away from Broadcom in general. Intel has the best performing WiFi chipsets at current, but Atheros and Realtek work just fine as well.
Broadcom chipsets are notoriously lacking in any sort of open driver operation or collaboration. I’d honestly just replace it with a $25 Intel chipset, but if you want to fight through it: https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
You’ll notice that your specific chipset isn’t mentioned, but it might be different now, so I’d double check.
Edit: after digging some more, there is zero support for this chipset anywhere except Windows, and it’s a problematic chipset anyway. I’d just get an Intel (fully open drivers) and swap it.
What’s the model of the machine, or the the WiFi module?
HOW FUCKING EMBARRASSING.
Removed by mod
Honeybees generally stay away from human activity. If you have a lot of flowers in your area, and big open spaces, they’ll just stick to the flowers and away from your house. They’re also unlikely to sting you unless you go to the hive and start messing with it and they don’t recognize you.
Everyone with extra outdoor space to spare, call your local beekeepers and see if they will put a colony on your property. It helps the local plants and wildlife, and they’ll do all the work in maintaining them. They just need volunteers to offer up space.
Also, talk to your local government about reducing the types of pesticides available for non-commercial purposes.
Some people won’t read this, but I guess I’m glad it’s out there.
Not in the way you’re probably thinking, which I assume is like in a Windows-y kind of way.
Finding an exploitable escalation of privileges in Linux is rare, but unpatched machines get hacked all the time, but the world of worms, and such is kind of gone.
The way most end-user machines get compromised these days is by supply chain attacks, undiscovered zero-day exploits, user error, and social engineering. Groups that discover zero-days usually keep it close the vest, and they don’t get found for long periods of time after they’ve been out in the wild.
The way most corporate machines get attacked is social engineering, supply chain, and zero-days. Mostly crypto mining schemes and enterprise-level ransoms for data.
All the Windows botnets you hear about out there are largely unpatched machines exposed to the internet in various stupid ways that groups prey on to take control of.
Edit: Forgot about leaked secrets. Lots of companies get hit from plaintext secrets that get out in the wild via various stupid means.
Any one of these could be the issue, but if you don’t want to take steps to debug it, then just unplugging and replugging the cable will kick the monitor back up.