You've been formally invited to laugh at me troubleshooting my first issue in Linux.
The weird thing is that it seems to be working? Either I misdiagnosed the problem, or maybe my old one was just broken.
Could be a new firmware in the fresh one
Or simply a newer kernel version could do the trick
Could be flashed with a different microcode that works better with Linux. Just because it’s of the same model doesn’t mean it’s the same. Sometimes it’s as little as a flag that is set. Looking at you battleye
A different revision could be very different, it's likely not really the exact same.
You will learn SO MUCH about computers by just trying to make your wifi or some other thing work. And then you will never have trouble with that thing again. I remember having to do wrapping of drivers, but I don't know if that is still a thing.
This is my jam. I really enjoy having a steep hill to climb.
Networking is wild. I've learned the Linux network stack by troubleshooting my Proxmox LXC + tailscale subnet router shit.
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
As far as first problems with Linux go, that one's a classic! Congrats, LOL
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.
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.
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.
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.
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 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.
My first Linux issue was that it didn’t support the USB hub I had at the time that was just always plugged into the windows machine I was installing Linux onto. So in 2003, I took my bulky tower to a friends house and it booted on the first try after weeks of failures trying on my own at home.
I was both relieved, and incredibly annoyed.
After both the 4G modem and the wifi dongles didn't work I decided to flash an old TP-link router with OpenWRT (or was it DDWRT?) and using that in a bridge mode connected wifi and via ethernet to the PC. So yeah, then I got an Intel wifi 6 NIC and gave the router away.
I've done that before, most reliable wifi connection I've ever had.
mediatek?
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.
Realtek stuff tends to be junk in my experience (even outside of support which is terrible)
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.
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.
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.
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.
Similar thing happened to me a while back, though the new one was just as much of a pain. So anyway, there is now a new, RJ45-shaped, hole in my wall.
That was a perfectly reasonable response.
You could do a proper termination
Yeah, probably. But as long as it works, I am fine with it
My overactive imagination: They used a speargun designed to fire RJ-45 shaped bolts through walls, pulling high tensile strength networking cable with it.
That's gonna be a good game. Like power wash simulator or viscera cleanup detail, but for structured cabling.
Man that reminds me that I bought a Chinese motherboard to build my homelab and installed Debian. Great! One kernel upgrade later and my network card stopped working. Tried a lot of things but to preserve my mental health and to enjoy my jellyfin again, I just returned to the older kernel and voilá, everything worked again..so no updates for now ...or ever
Have you ever compiled your own kernel? Could be the upgraded version doesn't enable a module your motherboard needed or something. A fairly simple test would be to compile thw kernel with everything enabled as a module and use that
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 happened with me and a USB video capture card I bought specifically for Debian Linux compatibility. One kernel upgrade later… doesn't work. Try again on old kernel? Works. I'll probably try in a few months, but I can't be bothered now.
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.
Sounds like a rockchip board like orangepi haha. It's funny because they actually have some killer hardware, but documentation on kernel drivers and DTB boot chain is sketchy at best.
Intel WiFi. End of discussion.
@theq @ThePicardManeuver reminder that intel ax series does not work with ax and even ac normally in most regions
ath9k or bust
Oops no WAP mode either
I have a USB wifi adapter for that reason
Yep. Got an Intel AX210 Typhoon Peak in my (AMD) laptop. Never had a single issue. Their CPUs might be crap, but their wifi is the business.
Their WiFi cards were great until they "fixed" them to only work with recent Intel CPUs.
My work machine has an intel WiFi chip and it's given me nothing but trouble
Or Qualcomm or MediaTek
Some distros have crusty old kernels/firmware and thus lack optimal support to boot lol.
Anyway even with Qualcomm Wi-Fi 7, it was not great even a month back. 🙄
I had to rebase to Bazzite-Testing and back to Bazzite-Stable a few times..... Ended up pinning an older testing image for a while to keep working wifi while Fedora upstream fixed their crap.
The joy of Atmoic made that super simple and painless I'll say.
Rolling back updates on tradish distros can be painful to the point of reinstall sometimes lol.
I personally would avoid Wifi 7 or anything newer. It takes a while to develop kernel support and it will be a bad experience. Wifi 7 support was only finished in the last year or two and it is going to be buggy.
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.
yup, same problems with v4l and a kernel incongruency. NixOS to the rescue. Add a line to pin the kernel and everything keeps working like nothing ever happened.
One of us
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.
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.
These shit are so weird, breaks on windows works on Linux, doesn't work sometimes on boot and I have to restart my pc for it to work
modprobe, man
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.
Ethernet is the way.
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.
Hey I'm glad it's working for you! Nice!👍
Totally fair.
You could try switching your wifi backend to iwd instead of wpa_supplicant.
If you're using NetworkManager, then create the file /etc/NetworkManager/conf.d/wifi_backend.conf, and add the following configuration:
undefined
[device] wifi.backend=iwd
If it's periodically dropping, I doubt that it's going to be the userspace WiFi backend. I'd be more-inclined to blame either the driver or an (unlabeled) hardware variation.
I bought a cheap wifi card and it worked instantly after installing it. Linux really fell off, huh?
😂 time to build your Linux from source!
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
Tienes que poner el locale en español. Ese es el truco.