Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
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
(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.
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
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.
This is how getting unsupported features work in linux feels
Like that time I got a random no-name action cam's webcam mode to work on Linux by manually mounting it within seconds of connecting it
Networking is wild. I've learned the Linux network stack by troubleshooting my Proxmox LXC + tailscale subnet router shit.
A different revision could be very different, it's likely not really the exact same.
As far as first problems with Linux go, that one's a classic! Congrats, LOL
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
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.
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.
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.
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.
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.
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 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
π time to build your Linux from source!
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.
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 bought a cheap wifi card and it worked instantly after installing it. Linux really fell off, huh?
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 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.
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.
inb4 Ubuntu added a kernel patch to improve support and didn't contribute it upstream.
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.
One of us
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
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:
[device]
wifi.backend=iwd