(cant believe Im writing this but) ever since I switched to Arch all those years ago, my Linux hardware problems ended.

Turns out Linux is great when your kernel is relatively fresh by default.

This is how getting unsupported features work in linux feels

There's something special about WiFi, but it is better than it used to be. I think it depends on your hardware more than anything. Any chance you can connect up to Ethernet in the meantime? You may be able to plug directly into a switch/router.

This. Way back in the day, I had a sound card that would absolutely not work in one OS unless I'd already booted into a different one and "activated" it with the driver there.

It might have been Win9x and WinNT, but it could just as easily have been Win9x and some early-ish version of RedHat.

But anyway, it would not surprise me to learn that the same sort of thing still happens with some hardware.

Ahh, ok that makes sense. Reading other posts, pretty sure my wifi chip is the same as OP.

and at this point it's also worth noting that this is a setting in the UEFI setup, and this is different to the fast startup setting in windows that also needs to be turned off for other reasons.

Ohhh. Great PSA to some of us who start out.

I think windows does shut down, but the hardware in your computer does not, and so when booting linux, the hardware does not start with a fresh slate. It's not reinitialized, keeping configuration and possibly custom firmware from the other OS.
interestingly, it also means malware could also escape a reboot this way.. and for the network adapter, maybe it doesn't even need to be compatible with linux to work.

what you mean though is the fast startup setting of windows. that does hibernate the computer as you say, after it logs out the user.

This.

Don't expect the brand new gear to work on Linux. It takes a while for the neckbeards to get access and write the drivers.

Heck, even new gear from companies that contribute their own drivers can be shaky.

I'm sorry, but for desktop, Linux can't be relied on as stable for early gear adoption. Usually even the specs are in limbo still.

This is coming from a linux/bsd only user for many years.

Realtek is just ass in general. I avoid them like the plague.

They're OK in windows, but I have never had a good experience with them on Linux.

Not sure if you have the same problem or not, but I had intermittent jitter spikes (and/or complete package drops) every 60 seconds on my Realtek chipset, ran:

sudo iw dev wlan0 set power_save off

And it's been stable since (just had to make a udev rule to make it persistent across boot)

Is it a pretty new machine?

Realtek stuff tends to be junk in my experience (even outside of support which is terrible)

Yeah that's why I was wondering if their machine was fairly new. I've found consistently better driver support with time. I'm genuinely surprised that its an older machine and having these issue.

I've had good experience with them especially on OpenWRT

Basically yes.

But thankfully they are equal-opportunity ass and suck on all platforms, not just Linux. I'm on bazzite rn because I couldnt get the bluetooth on either fedora OR ubuntu to work at full speed. Granted, my machine is very new, but like. I'm still getting that occasional issue where a bt device connects and the whole system lags.

I did it once but I remember not being able to judge if I needed all the modules or what to flag on each line I saw. I tried to load the module this time after the upgrade but without success. Maybe I'll try someday if I get the time..

Same here..O have around 20 containers running on my potato server and I really enjoy using them..not enough time to debug this thing.

That's gonna be a good game. Like power wash simulator or viscera cleanup detail, but for structured cabling.

Yeah, probably. But as long as it works, I am fine with it

Had the same problem while dual booting. Was a realtek chipset. Had a script to wake it up on booting or on disconnect. A hack I cobbled from internet lost to multiple hardware changes and multiple accidental wiping the whole computer.

if you use windows too, I remember from way back that windows made my network card to go to sleep(or some powersave move) at the windows shutdown, that make linux have issue with it.

I don't remember what the exact issue was but I remember it was windows doing it at its shutdown to save power, because pcie network card can stay awake even with pc off so that computer can be woke up via network ('Shutdown Wake-On-Lan' or a 'Wake on Magic Packet') windows made the card go to sleep and linux didn't wake it up.

I had this exact issue with both my desktop and server. Anytime I put any sort of load on the outbound connection, the wifi would cut out. After switching to the iwd backend, I haven't had any issues.