The weird thing is that it seems to be working? Either I misdiagnosed the problem, or maybe my old one was just broken.
😂 time to build your Linux from source!
The Teacher in me has to ask,“So, what have we learned from all this?”
big exaggerated sigh
“…aaalways read the hardware specs, Mr. Bluewing, sir.”
Driver issues then. Find GPL coder and ask them to fix the driver
In a pinch you can tether your phone through USB and use its Wi-Fi.
If you have an old router lying around, you might be able to set it up as a repeater and then plug into it with Ethernet. That’s what I did for a while when my computer’s Wi-Fi was unreliable.
The modem chipset everywhere are a CPU in its own and a black box at that.
In your case it might go to sleep occasionally.
It did seem pretty consistent timing-wise. This is very possible.
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.
As someone that spent a lot of years sitting next to an IT help desk, I’m not sure any chipsets work well at all. A lot of times you just have to figure out what makes them happy and get used to it.
I’d hear things like “as long as I don’t close my laptop after I undock, i don’t have to reboot to fix the wifi” as the person waddled across the office propping their laptop open. And these were high end windows laptops.
If you want to save troubleshooting time, just skip straight to the blood sacrifice. Computers are happy when you bleed, for some reason.
This was also my first issue in Linux but it turned out my duel boot was somehow screwing things up. Windows broke WiFi for Linux, then when I booted into Windows it was broken there too. I blame Windows because it was right after a series of updates, but I have no idea why it’d impact other independent OS on other drives.
Unfortunately I forgot the solution. It was probably since bios impacting thing, like how they often say to disable fast boot and junk.
Disable fast boot in your BIOS, else when you reboot, hardware is not re-initialized so if Windows loaded a custom firmware in the chip or set some stuff here and there, it may be incompatible with linux. If you dual boot, always disable FastBoot in the BIOS.
Ohhh. Great PSA to some of us who start out.
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.
Devices are configurable via software. If windows managed to “flip a switch” on the WiFi chip, it would affect Linux as well if it didn’t reset it on boot.
Ahh, ok that makes sense. Reading other posts, pretty sure my wifi chip is the same as OP.
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.
I had this issue and it was a fast boot issue. I’d shut down windows and boot Linux and WiFi wouldn’t work. A restart would fix it. With fast boot, windows doesn’t actually shut down, it’s more like a hibernate state. So the driver or whatever it’s called was being held by the widows partition and wouldn’t respond to another kernal.
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.
You are correct. Fast startup used to be called fast boot, hence my confusion. And it looks like the current state of windows is saved in nonvolatile for fast startup, which I would consider not being fully shutdown, but that’s probably semantics at that point.
Be me and get a cheap MacBook Pro 2015 to run Linux Has Broadcom adapter Apparently the worst one 43602 chip Proceeds to install arch anyway Tries 3 drivers, no luck Tries many workarounds, no luck Cries to sleep Runs internet recovery to install macOS, fails
Guys, listen to the wiki and techstack sites. Don’t get broadcom
Does anyone know a good Wi-Fi 7 chipset that plays well with AMD? I saw the Qualcomm one and it looks promising, but I’ve heard its support for Linux is spotty.
With hwe kernels, I’m generally satisfied with my Qualcomm NCM825. It might fail to come back from sleep 1 time out of 100 but that may be fixed now that I think about it.
Wifi 7 is not a great choice with Linux as it is very new.
I would stick with Wifi 5 or 6
And my wish is granted! This is the dawn of a new golden age for Linux memes!
Tienes que poner el locale en español. Ese es el truco.
Esta es la solución.
Could be a new firmware in the fresh one
Or simply a newer kernel version could do the trick
(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.
mediatek?
I gave up on the built-in mediatek wifi chip in my motherboard and just pulled the dedicated wifi card from my old pc. I’m on ethernet now, but man troubleshooting that was not fun.
I even ordered a new chip, which, of course, never showed up.
I have a Mediatek MT7921K, it’s using the mt7921e driver, 3 years ago the chip was new I think and not well supported in linux (problem with init/sleep/resume) but a lot of people fixed it, and mediatek released new firmware, and the driver is rock solid for about 3 years now, I’m using it on my daily driver working PC 8h/day, 0 problem, and use a BLE keyboard and trackball too.
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.
Realtek. I was reading that many Realtek chipsets cause intermittent wifi drops, and that since they’re pretty inexpensive, it’s simpler to just get one that works. So, I went with another company that advertises as Linux compatible out of the box, plugged it in, checked it with ‘lsusb’, and saw the exact same Realtek chipset that my old one has.
Is it a pretty new machine?
No, very old. A lot of the hardware is from 2013.
Realtek only started to develop drivers in the upstream Linux kernel relatively recently, 5 years or so, and only for what was then the newest chipset. Something 88 and two letters but not 88 and other letters (I think CE).
Does Intel WIFI still exist? If so, that is what is probably the best supported chipset.
Realtek stuff tends to be junk in my experience (even outside of support which is terrible)
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 offAnd it’s been stable since (just had to make a udev rule to make it persistent across boot)
If I catch the new one doing it, this is going to be the first thing I try. Thanks
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.
It sounds like you’re not alone, and it’s what I was trying to do too! I just didn’t pay close enough attention to the specs on my new adapter, lol
Lesson learned.
Did the new adapter have the same problems? I know you said it read as the same.
So far… nope. I need to test it some more, but I’m just waiting for it to start happening again.
Realtek cards are trash on BSD too.
FreeNAS was my first experience with that…
After dealing with that for a month I swore I’ll never buy a nother PC with a realtek nic. I think I spent like $50-100 more on my latest mobo in order to get Intel + Marvell instead of Realtek.
Especially wired
Ask me how I know
Asus motherboard?
Are all mediatek’s horrible? I’ve got one in my desktop but it’s just terrible. Randomly crashes my whole pc after a while. And the only way to fix it is to cmos reset the motherboard. It’s forever disabled in the bios now, which also means no Bluetooth sadly. Just wondering if I had bad luck or to always avoid them.
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’ve had good experience with them especially on OpenWRT
Just curious but what distro are you using?
I might be able to help in my spare time
Pop OS. It seems to be working for now, but I think my next step if it happens again will be to just use ethernet and call it a day.
If Ethernet is an option, then it’s the best option.
Well, the PC is far from the router, but someone mentioned setting up a WiFi extender that has an ethernet port, and that doesn’t sound like too bad of an idea.
Hey I’m glad it’s working for you! Nice!👍
Totally fair.
Pop OS is based on Ubuntu LTS and uses a relatively old base system as a result. Try a live ISO like https://get.opensuse.org/tumbleweed/ and check if drivers have since improved.
Ethernet is the way.
As far as first problems with Linux go, that one’s a classic! Congrats, LOL
