The weird thing is that it seems to be working? Either I misdiagnosed the problem, or maybe my old one was just broken.
Check h-node next time ;).
starring this comment, amazing resource from the FSF - thank you!
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.
Driver issues then. Find GPL coder and ask them to fix the driver
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.
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.”
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
write us the driver to mount it within seconds of connecting it automatically.
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.
It’s too far from the router right now, but I have some options.
I needed to have the new adapter plugged in to use a tool from the manufacturer that is supposed to detect your adapter and install the most up to date driver for you, but of course you have to be online, so I was using the old semi-broken adapter and had both plugged in and connected to my router at the same time.
It seems jank, but it made me wonder what would happen if I just left both connected forever. Would it stay seamlessly connected as long as they both don’t drop at the same time? Lol
You remind me of when I moved to Argentina. I had a laptop whose fan suddenly froze but I was too broke to get a computer so I figured out that if I put it in JUST THE RIGHT spot next to a fan, it would get enough passive cooling to work. Then I did the silly and decided to upgrade, which made me have to plug in Ethernet. It took me ages to get the computer back in the right spot so that it wouldn’t power off due to overheating. All for WiFi…
Amazing. There’s a level of stubborn ingenuity that I can appreciate.
You can make Linux load balance over two network connectors, but usually it prioritizes one network adapter for all traffic based on a scoring algorithms (wired and high bandwidth gets most points).
You can manually set a priority too, or route specific traffic (based either on destination, protocol, or source program, etc) to a specific adapter. Some programs (like KTorrent) are capable of using multiple adapters without any specific config (which is why I was able to run torrents one time while literally nothing else worked with an old 3G internet dongle) .
This would be a really interesting rabbit hole to go down…
I did it once because I had an unstable cable connection, it was surprisingly easy***(for me) https://www.baeldung.com/linux/merge-several-internet-connections
Networking is wild. I’ve learned the Linux network stack by troubleshooting my Proxmox LXC + tailscale subnet router shit.
As far as first problems with Linux go, that one’s a classic! Congrats, LOL
A different revision could be very different, it’s likely not really the exact same.
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.
Hah, I’ve totally done that. I’m thinking about doing it again, because it worked way better than my desktops built-in wifi adapter that has no external antenna.
I’ve done that before, most reliable wifi connection I’ve ever had.
inb4 Ubuntu added a kernel patch to improve support and didn’t contribute it upstream.
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.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.
😂 time to build your Linux from source!
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.
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.
