I never have. Just thinking about WiFi and Bluetooth drivers on random laptops still puts me into a full flashback state. (My first experience was back in 2002, I think?)
However, getting all of that stuff working was the best learning experience I ever had. At the time, I was just learning about IT security and WiFi pcap was all the rage back then.
I never have. Just thinking about WiFi and Bluetooth drivers on random laptops still puts me into a full flashback state. (My first experience was back in 2002, I think?)
Same, flashbacks to being in college trying to get Wi-Fi working in Fedora on my laptop and then struggling to get it to work with my uni's new Wi-Fi system. Frustrating, but a great learning experience as you said.
Even a decade ago it usually meant ticking a box that you also allowed nonfree drivers.
Even Debian allowed you to download the specific nonfree driver you needed and add it (without Internet) at imaging so post install you could connect with wifi and not just Ethernet.
It's come a long way. But doesn't anyone else remember when windows did not have drivers and you'd constantly be confronted with "have disk"?
I mean, the amount of drivers for old hardware I still have saved... Because before win10 nothing would reliability always fetch the driver you need from the net...
This reminds me of the big USB drive of drivers that we had at a PC repair shop. When Windows 7 failed to find drivers, we’d stick that in and give it a scan.
Ticking the non-free driver box was child's play. As late as like 2012 I remember needing to download NDISwrapper so I could make the windows drivers work through a compatibility layer
I recall jaunty jackalope being the Ubuntu version that became my full time os. It was that version that my IBM x31 had everything taken care of on install with the third party drivers checked. I feel like the LTS version following that was where you could buy a generation previous of any hardware and it'd work without much fuss.
The nvidia driver has had this bug for a year now, still unfixed. Games will randomly crash with an Xid 109 error in dmesg. Some people (including myself) are unable to play games like Cyberpunk, Resident Evil 2-3-4-7-8 and Metro Exodus. And it’s not linked to proton either, it sometimes also crashes xorg itself, forcing a reboot. I’m starting to think nvidia will never bother fixing it.
Having the device, I already tether the wifi. But it is indeed a compatibility issue: the old kernel drivers for the chip were janky and it’s doubtful how well they even worked the time. The code is apparently such a hot mess that the people who were working on it have stopped making progress. There is now skepticism that it will ever be fully functional.
There's this one Bluetooth speaker with a microphone that I have, that I had hoped to use for calls, that has just refused to work. Spent hours trying to get them to work but had to admit defeat. But yes, things have improved significantly.
It works great until you try to use Bluetooth anything and need to connect and disconnect regularly (it can literally freeze your entire system), and don't get me started with trying to get digital surround to work
Wi-Fi used to be a pretty common thing to not work out of the box or to break in updates. I kept a usb Wi-Fi dongle in a bag as a backup just because of this.
It's a really simple problem to avoid, and IMO has been for years. It's been at least 10 years since I've bought something without intel wifi so maybe I'm out of touch, but I'm kind of astounded there are so many upvotes to the meme.
My rule for a very long time has been: Get something with intel wifi, or even atheros wifi, and you will almost certainly not have a problem. Get broadcom wifi and your problem will directly relate to how much effort your distro has put into trying to make broadcom not be shit. Stay the fuck way from realtek and mediatek.
That's it. I literally can't recall a time since about 2010 when I had a wifi problem with Linux on any device I owned.
I keep two of these in my bag for instant wifi on any device I might happen to be working on that doesn't have it. Most recently popped one into an old desktop I picked up for my youngest son, and have used it previously as a workaround for someone who had a laptop where the onboard wifi worked but would not come back from sleep. (That was broadcom, IIRC)
Lemmy needs polls. The last time I had problems with WIFI drivers was... 15 years ago? On a laptop bought in a supermarket that originally came with Windows Vista. Oh, and the raspberry pi - fuck raspberry pis. They can't pick wifi module worth shit.
I mean it isn't Linux fault, but I wanted to install balenaos on my RaspberryPi and they don't support a WiFi chip in their kernel. Without WiFi the whole idea won't work for me. And I don't want to buy a new WiFi usb only because they don't want to add the drivers.
My attempts to add it to the kernel and build it myself failed so far.
I'm not faulting linux, I'm faulting the Raspberry Pi Foundation. Linux is their main operating system and they haven't picked a good WIFI hardware module for years. Dunno if the new raspberrypi 4 is better, but I'm not paying to find out.
All single board computers have driver problems because they require custom kernel forks that can't or don't get mainlined for whatever reason (usually laziness), but Raspberry PI is actually the best when it comes to that stuff.
So when you buy an SBC, you need to ask yourself: will the company continue to develop/update/patch their custom kernel fork now that they shipped? Or will they just abandon it and move on to the next product? 9 times out of 9.01, it's the latter.
Had problems about 3 years ago, got a new laptop from work and the WiFi hardware was too new and didn't have support in the kernel yet. Took a year or something, maybe less, until it worked.
Raspberry, seriously? What problems are you seeing?
I have a raspberry pi 3 acting as a 5GHz access point for as long as it's been on the market, I can remember one time I had to restart it because of some wonkiness. About a dozen others as clients, never had an issue there either, fast and stable enough.
All using the default os (raspbian first, raspberry os later).
After that, I gave up on WiFi on Raspberries and used LAN, but they are so underpowered... my nextcloud instance took ages to do anything, XBMC (now Kodi) was slow and couldn't render videos > 720p (it was struggling with 720p honestly), even a simple audio proxy over bluetooth (forward bluetooth audio from phone to speaker) barely functioned as the bluetooth cut out or it was janky as hell.
It's easier to put a old phone as a server than a raspberrypi.
There are some oddball cards out there that need the linux firmware xxx (insert manufacturer instead of xxx) binary blobs in order to work, but yes, those cards are rare nowadays and mostly older hardware uses that (as you mentioned, hardware from 10+ years ago).
Tell me you haven't used more than 2 or 3 pieces of hardware in the past 20 years without telling me you haven't used more than 2 or 3 pieces of hardware in the past 20 years.
I thought you thought about WiFi drivers because of the extra difficulty on not being able to search online, but I see now that this is just based on real experiences
My Intel Wireless AC 7265 on my Sony VAIO begs to differ. Certainly not brand-spanking new but it's AFAIK less than 10 years old. The speed would at some point drop under Void Linux.
If the card supports at least WPA2, it should support WPA2 Enterprise as well. Only cards manufactured in the last few years support WPA3. I doubt they would enforce WPA3 only.
This was true maybe 10 years ago, nowadays Linux has better driver support than Windows. Printers, networking, input devices, everything I've tried is plug n play with Linux, Windows you gotta driver hunt.
Absolutely not outdated. I had a horrible time getting my hands on a working driver for the WiFi card in my brand new laptop last year. Horrible enough to resort to Ubuntu and even that gave me the finger. When I finally had it working I had to manually rebuild the damned thing each kernel update because I couldn't convince DKMS to do it automatically. Had to wait two or three kernel releases for the card to be supported 'out of the box'.
So no, fuck WiFI drivers in Linux. If it is not in the kernel and the manufacturer doesn't provide one, don't expect fun times.
Situations like that aren’t very common these days. It usually happens when your hardware is very much new and drivers aren’t yet in the Linux kernel, or they are in the newest mainline, but your distro wont ship it for some more time.
For that matter, it’s always bad when the kernel doesn’t have the drivers built in and it always requires dealing with DKMS or akmod whether it’s wifi, webcam, bluetooth or GPU (that’s why NVIDIA tends to be problematic on some systems).
That being said, the meme only works for anecdotal cases.
Outdated for Linux Intel, still valid for Broadcom, probably not so bad for somewhat recent Realtek and AMD/Mediatek (last I've read is that Mediatek WiFi hardware sucks in general and disconnects happen on Windows, so the same happening on Linux would be the fault of the Linux driver).
I can absolutely confirm it's still valid for Realtek. I had one using the RTL8812AU chipset that basically no kernel version nor distro provided out of the box, so I constantly had to download a third-party driver from Github and manually patch it via dkms, or use a third-party repository containing the driver package... and then the driver broke so badly that it wouldn't let me update at all unless I uninstalled it, which left me without the internet I needed to actually update, effectively leaving me unable to update until I could buy another one from Mediatek that's compatible.
And said Mediatek wifi is really slow, so I just went from the frying pan into the fire...
I can absolutely confirm it’s still valid for Realtek. I had one using the RTL8812AU chipset
Yeah, and I was explicitly writing about recent chips. RTL8812AU isn't recent. The very latest Windows driver is from 2018, so the chip itself was released a good while before that.
I know exactly what you had to go through because I had to do the same with mine a couple of years ago but since then for newer chips Realtek started contributing to Linux itself:
Ahh I see, thanks for clarifying. It seems that where I live mostly only has the older Realtek chips for sale, so I likely mostly had bad luck.
I tried USB tethering, but it wouldn't work for some reason... I don't remember exactly what happened, but I think either the phone or my computer couldn't detect each other.
But was the cause the Linux driver or the hardware? If the fault is the hardware and the experience on Linux is the same as on Windows, it's feature parity.
If in doubt, get an Intel WiFi card. Even in otherwise not upgradeable notebooks those are usually not soldered on. Also whatever is in a Steam Deck OLED looks like a good pick.
Does Intel sell wifi cards that use USB rather than PCI slots? My motherboard doesn't have the slot for a wifi PCIe card, and I've only seen Intel sell those :/
I installed linux on a new pc 2 days ago, had no problem with the wifi drivers.
I don't know if it's the fact that the wifi is integrated on the motherboard, but it was up and running without any tweeking from me (unlike windows)
If it is not in the kernel and the manufacturer doesn’t provide one, don’t expect fun times.
This could be shorted to if your device has no driver it wont work which is obviously true.
If you have very recent hardware and you find it doesn't work out of the box on stable options the easiest thing to do is install a more recent kernel. Even current Ubuntu non-LTS is 2-4 releases behind.
It's even easier in arch/void where the latest kernel is already available.
Respectfully if DKMS wasn't automatically kicking in then you configured it incorrectly. It's a lot easier to just rely on a package that sets this up for you properly. If for some reason this can't be done the logical thing to do is script the process so that all operations are completed in the appropriate order that way you needn't remember to do one then the other.
This could be shorted to if your device has no driver it wont work which is obviously true.
What I tried to tell is that if you have to rely on community driver projects, don't expect fun times, at least not when it comes to Realtek in my recent experience.
If you have very recent hardware and you find it doesn't work out of the box on stable options the easiest thing to do is install a more recent kernel.
I already had the latest available kernel at the time, as in: the very latest officially released kernel by kernel.org. Ubuntu was just a last-ditch effort as it will sometimes have drivers included that other distros might not have, normally I wouldn't touch it with a ten-feet pole and go either Arch or Manjaro. The driver simply wasn't included in the kernel. How do I know? Because I stumbled upon some discussions that mentioned the lack of support and 3 kernel releases later support for my card was specifically mentioned in the changelog.
Respectfully if DKMS wasn't automatically kicking in then you configured it incorrectly. It's a lot easier to just rely on a package that sets this up for you properly.
Yes, like a Realtek-XXXX-dkms package, which simply didn't work. I've configured stuff for DKMS before, scripting stuff for Linux is part of my daily workload, so yeah, you don't need to tell me scripting beats doing stuff manually.
The fact that getting an f*cking wifi card to work takes this much effort is what I meant with 'not fun times' and for me validates the meme, anecdotal as it might be.
Resorting to other distros, configuring additional repos so you can install a different kernel version, having to try different community projects to see which gives you a working driver, having to deal with getting DKMS to work, this is all stuff which hampers Linux adoptment. And without more adoptment we won't have to expect more support from manufacturers for desktop related consumer hardware. So yeah, that does make me cry a bit. It's a catch-22 unfortunately.
I do occasionally fall for just buying shtuff without a quick google search to see if my kernel would be cool with it, but I have an even greater number of stories about good experiences with Windows shtuff driving me bonkers.
For example, the Brother ADS-1200 under WIndows beats anything SANE supported scanners can do hands down. Scan to PDF with excellent compression and top of the line OCR. The spousal unit needed a scanner and I found a good deal on an ADS-2100. Under Linux, scan results are totally comparable to the ADS-1200, so the hardware is fine. But the Windows software for this scanner is crap. JPEG and TIFF are identical to the Linux scans, but OCR and PDF compression are atrocious. I'm 100% sure that if I were to edit a table in the ADS-1200 software, it would happily apply the same excellent results to the ADS-2100. But I've had it with hacking Windows goop, been there, done that, got the t-shirt, so onto Craig's list the 2100 goes... Built in obsolescence, welcome to the Windows world.
With Linux, once the kernel accepts it, it's smooth sailign without too many vendor introduced hickups.
And even on Windows, if you need to use third party scan software like VueScan because your scanner happens to be older than your Windows. it'll work but it won't outperform SANE supported scanners.
I had a case where fingerprint sensor was working out of the box fortunately. Although I had a problem where cryptfs would stop authenticating successfully with fingerprint sensor after distro update
10-15 years ago, it was a problem dire enough to drive me back to windows until about the start of the pando, and I've not even thought about Wi-Fi drivers since coming back to Linux.
I did have issues with a cheap USB Wi-Fi dongle thing a few years back, but that was likely the fault of the dongle more than anything else, I know because it didn't really work under widows either.
It's not so bad if you're running a major distro kernel and they do some prerelease testing before cutting new kernel packages. But if you're using the latest release from the kernel.org stable tree WiFi driver regressions happen somewhat regularly.
The one I had was completely minor. The wifi on my NUC doesn't work if you use the proprietary driver but it does work with whatever the kernel for Mint 21.2 has in it.
I had a similar experience trying to install a m.2 drive in my win7 PC. It needed a hotfix to work but Microsoft had taken down the downloads so I ended up finding out it was in an update pack from I think Lenovo's website and pulled it out of that.
To get it to work in Windows I literally had to go to a website that was only Chinese, download a zip file, and extract a dll that would then work when pointed to.
It's called manual driver install in Windows... pretty common with older hardware.
Most of those just go over Windows Update now or work with a generic driver that comes with Windows. Only really obscure drivers need manual installation.
6 years ago, I was using a USB wifi adapter with my desktop (my friends next door paid for internet and we paid them half the bill to share).
I had picked this wifi adapter specifically because it had linux support, even though I used windows (I had an inkling I'd switch). So, I tried to switch but upon boot I couldn't wifi because the adapters module wasn't bundled by my distro so I had to instal 'dkms', but I couldn't do that without an internet connection...
I have a few wifi adapters from china who only work properly under Linux lmfao
Did Microsoft actually infiltrate Lemmy or something? I'm hearing of issues about Linux that haven't existed since the very first days of desktop Linux
I still have wifi woes on my old tablet. Works fine for a few minutes, then dies. Works fine in Windows. I'm about to reinstall on it. Maybe the next distro I try will work?
This is probably some sort of firmware power management bug that the windows driver is working around. Try and see if you can find any documentation on it
The wifi chipset on my new MSI mobo isn't supported on current LTS version of Mint - I had to install a more recent kernel, so there are still issues with newer hardware
Yeah, the Chinese stuff seems to work better under Linux... for some reason 😂. I one based on a Realtek chip (I think 🤔) and I couldn't get passed a few hundred KB in Windows. Linux fried that baby, it did 1.5MB 😂.
The last time I had an issue with Linux drivers was in 2002, trying to set up a pppoe connection. I had no smartphone and there were no YouTube, Reddit, wikis, forums etc.
Back in 2016 I helped install some wifi drivers on a friend's laptop in Ubuntu 16.04, which was not really a big deal.
I feel like these memes are made by Windows users :)
What killed my interest in Linux in highschool. Kept trying to get Ubuntu working but couldn't get the internet to work for anything. Given that every help guide boiled down to "Go to this website and download x" and I didn't have internet because... no wifi, I ended up getting frustrated enough to quit the whole thing. Maybe someday.
Hey, as long as I ignore the thousand of entries in the error log I get every day from the iwlwifi kernel module crashing and restarting every 10 minutes its fine.
That's different. Lenovo supports the kernel, but doesn't ship some laptops with Linux. Two of mine (P14s Gen 1 and Gen 4) don't. I always have to work for NixOS, as does my friend for Arch.
This is true today. Had you tried that back in 2005, you'd very likely be fiddling with drivers. I specifically remember making a disk that contained all the drivers I'd need if I had to reinstall for any reason. Without it and without a network, you'd have to have another computer available to grab drivers from the internet.
You had to do this with windows in 2005 too... In fact I've had to use a different computer to download drivers as recently as 2017 for a Windows 10 computer...
Well, yes. I wasn't really intending to make a comparison. I was just explaining the meme. There was a time when getting your wifi/network card going in Linux was somewhat of a hassle for many.
Installed Ubuntu on my first netbook and had to sit in the stairs to the second floor jacked into the single Ethernet cable we had for a few hours to troubleshoot it.
I haven't used every distro, but it seems like most of them are plug and play these days.
I just installed mint on a new laptop. The wifi surprisingly didn't work on the liveusb, but switching to the Edge release with a newer kernel worked fine.
Lots of people saying this is an old problem , but I have a new IdeaPad I bought a few months ago and any non-rolling release distro I find, the wifi hardware isn't detected.
Until just a few weeks ago I couldn't find any solution. Fortunately I finally found a way to build the drivers, but it still requires me to tether my phone to get internet long enough to download the source.
So the problem might be better but it's not the non-issue some people are pretending it is.
Try Windows. It regularly breaks drivers (not only WiFi) on some hardware (mostly HP). I've never had issues with WiFi on Linux on HP, Dell, Microsoft Surface and even a Macbook.
I didn't say I couldn't fix the issues, but the fact that some of those issues exist even since XP is pretty bad. Just search around online and you'll find many posts about these driver issues. And then there's all of the ui inconsistencies and issues. Most of those are small, but still annoying once you see them. Especially when using Windows on a tablet, even Microsoft's own Surface line.
For HP ZBooks for example there was an issue that completely prevented you from installing some updates like Windows 10 20H2 without any warning as to why it wouldn't install. It just failed at 61%. It turned out to be audio drivers for the audio chip in the dock. The only way to get it updated was to connect the dock, finding the audio device in device management and removing it. Then disconnect before Windows reinstalls the driver again.
The thing is, there's "iwd" and "wpa_supplicant". You use either one or the other, but not both. Sources like the Gentoo handbook will tell you that but, not all Wiki's do as good a job of pointing that out <...looking directly at you Arch...>.
I don't understand anything to do with network configuration, I just install a few packages (iwd and wpa_supplicant included), start a few services, run a few commands, and hope it magically works after rebooting
Funny that my brand new laptop just arrived today and its own wifi card wasn't recognized in Windows, so I had to use my phone via usb-tethering. It's a Lenovo Yoga Slim 7 (14APU8) by the way, Ryzen 7th gen, full AMD, OLED etc. It came without any OS (no way I'm paying for Windows lol) and my first Win11 experience on this laptop was "please choose a network to continue" and no networks were displayed at all, because wifi card had no drivers (Realtek btw). Windows setup wouldn't let me continue without a network, but there was no way to have a network. Funny Win11 moment right there. After some hours configuring everything I then installed my usual dual-boot Fedora and everything worked even in the live-usb. This meme is not valid for Linux anymore. Windows however, now thats a meme.
Trust me, it is. There is some obscure hardware out there. Plus, a lot of us still use hardware that was late XP time released and ndiswrapper was still around. So, for some of these cards, there is still no drivers for Linux (or buggy/unstable ones).
I understand, but seeing this post right after my experience today was the biggest coincidence ever and kinda funny that it worked right away in Linux while in Windows I had to manually go get the drivers for it. Linux used to be bad, but it evolved A LOT in terms of drivers support while windows just kinda stayed the same. I remember facing the same problem of booting a new Windows install and having the wifi option completely gone (no drivers) in Windows 8... many years ago. Windows 11 and the experience is still the same. And it's a modern Realtek card, not even close to being obscure. This post + this experience today was just a nice internet moment
Linux used to be bad, but it evolved A LOT in terms of drivers support while windows just kinda stayed the same.
Agree on that part. It has gotten a lot better.
Still, I was hoping that they'll eventually solve some of the problems with the WiFi hardware back in the ndiswrapper days. As it turns out, it's 50/50. Some of it has drivers, some don't. Sure I could go hunting for untested unreliable alpha stage drivers and compile them myself, but I was kinda hoping that we would be passed that on over 95, 96% of the hardware there is out there.
Well I myself have no patience at all to compile stuff myself, I can say I am half casual half linux nerd. I'm in the middle. Compiling stuff is too much, especially drivers and low level stuff like that. At that point I will just give up on the hardware or the OS/distro. That's mainly why I still dual boot. I have a SIM Racing setup and even with drivers that exist already and many awesome community made GUI tools (like Overdrive GUI) that get updated almost daily (which is impressive), it still is very hit or miss and most of the times it is either not detected at all or just half working. Even after using linux myself since the Ubuntu 7 and Gnome 2 days, I still dual boot Windows because well... sometimes life is just more peaceful when you can just reboot your pc and have funcional hardware again. I work under linux and play under windows. That's peace for me. Except nowadays I am staring to play non-Sim Racing stuff on linux too because Proton is amazing. But it still requires a lot of manual labor to make it work. And when I teach linux to other people I always teach the dual boot way and how they can easily jump back to what they are used to. In your case.... I think I would just get a different wifi card if possible. If its an embedded one, well... maybe I would just get a new motherboard/device anyway, or just use another OS and call it a day. Sometimes it's the better way. In your case probably the amount of people that need drivers for hardware like yours is diminishing day by day, so the probability of it ever getting fixed also diminishes. I found out that in the Linux world it's always better to stay with mainstream hardware as much as possible.
Possibly. Some XPS models (~9310) cheaped out on the WiFi chipset, which was really bad at reconnecting after sleep/suspend on Win 10/11 right out off the box.
Tried a live Linux install and it worked perfectly, so made the switch as there was no Win-only software that I needed.
The very evening I installed Linux for the first time (I think it was Ubuntu 12.04), my Wifi stick was the first major hurdle. I was a teenager, had no idea about package managers and such, but the drivers for my stick were only available in an uncompiled format, so I had to first learn what build utils and kernel dev packages were, download them and their dependencies onto the windows PC of my dad and copy them onto a CD.
After I had figured all that out (took me.a while), I learned how to compile on the fly.
After I had run ./configure and it finallyfinally ran through without error, the config script had this last line:
Configure done successfully. Now type 'make' and pray
Things have changed over the years, but they haven't changed enough.
Compiling starts to work rather well once you've done it a few times. Especially when you get more used to understanding what ./configure tries to tell you. You should really try to get behind that, since you Linux will
Yep, been in the same boat 😂. Was an LTS fan for a long long time till I realized... this shit ain't worth it 😂.
Everthing there is out there in 99% of the cases compiles against latest libraries. And well, LTS is just... lagging behind 🤷. So, you solve one lib dependcy and then, bam, another one pops up... OK, solved that one, bam, another one 😒... it just gets frustrating to compile stuff on LTS.
And then you get all sorts of errors from the package manager cuz you did the unthinkable - install latest libs on an LTS distro.
LTS is good for one thing only nowadays - servers.
I've only had problems with wifi drivers twice, immediately after clean-installing fedora 38 on two different devices. Plugging my device into ethernet and updating fixed it instantly.
Not sure about iPhones, but I've used an android phone a couple times to both USB tether with data and to act as a WiFi receiver to download drivers in a pinch.
Use a second computer or a friend's one to download the updates, get a USB ethernet adapter (a 100mbps one is like $5), put the system drive in a computer with lan, tether with another device via USB (phone, pi zero, etc) or use a different version/distro. I'm sure there are a bunch of other solutions.
I guess an ethernet to USB adapter might be your next best bet.
Alternatively, you could USB tether your phone if you have a good data plan
If you are in the unlikely event that you don’t have ethernet port to plug your device into, and no cell service, such as I was, you can use a spare wireless AP to get wifi if you’ve got one
My new laptop has a nvidia card in it. One time it stopped working after a update so I downgraded the drivers so I can wait entail the next update they do work. Besides that it have worked great. I am on fedora so rpmfusion is where the drivers are from.
It’s been so much better…but I’m steeling myself to track down a WiFi direct bug that keeps disconnecting due to a timeout after 10 seconds. Linus give me strength!
It's insane how I just had this problem today. Had to tear out my network card in my Asus VivoBook 16. The drivers aren't out for the MediaTek network card so I had to change it to an Intel one that I previously used.
I have a Retropie and I use wpa_supplicant to manage my connection there. It looks like this: the router is downstairs and I use a repeater in the room next to the Retropie to have better wifi coverage upstairs. The router itself is reachable, but the signal strength is worse. So, as a fallback, I put both the router and the repeater connection in my wpa_supplicant config file with the router having a lower priority. Still, sometimes my retropie clings onto the worse connection for some reason and there is no way to change it but to do a complete reboot. If I just restart the wifi with ifdown and ifup, it will either not reconnect to any wifi at all or reconnect to the shittier connection again, it's kinda a fifty-fifty. A reboot will always properly choose the best signal tho and I am very confused why this is happening. Any ideas?
Set your wpa_supplicant to use the BSSID of the repeater's access point and don't put the SSID in the conf file. Then it will connect to only the repeater.
If the repeater just re-transmits tho main AP's BSSID and packets, you need a better setup. Cheap WiFi extenders do this and almost always cause collisions, making the overall speed slow at all points.
The repeater uses a fixed channel (I think I set it to 7 or 8) and the router is set to automatic channel selection. Do you think fixing the router's channel would help?
See if they're overlapping, do a survey with your phone and WiFiAnalyzer (or another app). If they're close or overlapping, set the router to a fixed channel as well.
Please do not trust modified windows installs based on old (22H2) update packs, you're much better off debloating your fresh, up-to-date, already licensed install using some powershell wizardry...
Chris Titus has made a gui for this that you can access with a single powershell command. He also has made a guide on which settings he recommends to debloat a fresh install.
This way you aren't entrusting your OS, privacy and data to some random unsecure repack. I can find the link for you if you would like :)
Apologies for not having seen this until now, if you are still wondering and haven't found the tool yourself, you can launch it by opening a windows terminal as admin and typing
irm christitus.com/win | iex
as soon as chocolatey is installed a gui will launch allowing you to easily install common software, uninstall bloat, apply tweaks (such as disabling telemetry), and control windows updates.
It's a great one stop shop for setting up any fresh/existing windows install, and is continuously updated with reliable and transparent documentation.
It's the same problem that all the prepackaged modified Windows have when I go to try them out in a VM. They always seems to be way out of date and with all the security problems of Windows, I don't want to run an old version just to save the time of cleaning out the telemetry and bloatware. Powershell scripts are more robust for me.
If you want some irony, on a recent Ubuntu install I was able to access WiFi out of the box but the small windoze dual boot partition refused to connect to a WiFi 6 router. Tried upgrading driver, downgrading drivers, nothing... The computer came shipped with windows 10.
LPT: Swapping Wifi modules is (sometimes at least) stupidly easy to do. I had a shitty
::: spoiler Trigger Warning
Realtek wifi card
:::
and bought an Intel card to replace it for about 30 bucks. Begone random disconnects and packet drops. Note that this was on a laptop and it was still just an issue of removing a few screws and swapping modules.
Isn't the main problem that most of them are proprietary, so they can't be shipped automatically if you want to avoid shipping a distro with proprietary software?
Printer are worse. try to get a decade old brother to print more than a half page without completely freezing and needing a hard restart. driver is unmaintained unfortunately.
on Windows the printer works perfect though. which makes me quite unhappy :|
wifi on the other hand is not a problem i can remember. even on a 15 year old laptop, the AUR has a driver that it extracts from a ancient .deb and then patches it to make it work with modern kernels. lovely.
The driver shows up as "cups + gutenprint" and as far i can tell there is no other. so i guess that is already the one and only available driver.
and i have to correct myself, it is a Canon, not a Brother. Canon MX300 from 2007.
I mean it is not that big of a deal anyway. there is a single Windows machine left in this household that i can use for print jobs. and yeah, maybe i could use it as print server, that is actually a interesting idea lol.
Try searching online for cups filters. Maybe someone made a custom filter file for that printer that works... worth a shot 🤷. I've had luck hunting down custom filters for some obscure printers in the past.
Setting up a shared printer in Windows is (could be) a PITA though... not being able to choose SMB versions can make your Linux setups with SMB a pain 😔. That's why I prefer Linux with samba as the print server, you can fine tune almost everything to make it work with any Windows and Linux install.
Also, true story, LTSC 2019 can't see shares from LTSC 2021, but the opposite works without a problem 🤣. It was a bug, they eventually fixed it, but took them like a year or so (they threw the ball at users, not setting up the shares correctly 😒), and I already reinstalled all rigs with LTSC 2019, so... too late MS 🤷... I haven't used LTSC 2021 from that point on.
It's the newer Wi-Fi chips that have issues, those for which drivers aren't yet released. There always seems to be a year-long delay between the next gen laptops being released and the wifi drivers for them.
I specifically bought a Brother printer because they at least try to support Linux. My previous one Samsung was much worse, it had Google cloud print so I could still use it. But Google like always killed something people liked.
10 years ago was the turning point. I remember as late as 2010 -2012 having to use NDISwrapper to install the windows XP wifi drivers because there were no native drivers so you had to run the windows drivers through an emulation layer to get wifi to work. Even within the past 5 years I've had to compile my own fixes for realtek chips because the auto installed drivers were not working optimally
I still have issues with certain ASUS cards that simply crash the whole system when it gets too high a load or something. I've never been able to find a solution for it and I fear I never will.
They have a very very limited range. I have used them, but only if the AP is in the same room, otherwise, they crap out.
PS: Everything's built from reinforced concrete and cinderblocks/bricks around here (seismically active region), so we have trouble with all sorts of wireless signals, including WiFi and 3/4G. 5G is out of the question here. We do have the towers, but less than 1% of users actually use them.
But are you perhaps referencing to the situation with Broadcom just incrementing their chips and drivers for years, flooding the market with cheap but quirky chips? Do they still do that?
Mine just stopped working with brscan5 driver. It was a fast and quiet mobile scanner with high quality output. The new one is bigger, slower and louder and runs 90% of time in some photo mode. 🙁
Yeah, they came in later on and that's why I think they were "better"... learned from experience with the wifi drivers. And they weren't really better, most of them still use binary blobs.
I think it very depends on your hardware. I, personally, never had problems with it, on thinkpad which I use right now WiFi drivers were out of box even in Gentoo minimal ISO(It uses iwlwifi). But, every hardware that I have is about 10yo. And I think I haven't any non-intel WiFi-cards.
But also one of my friends had to compile drivers for his card manually from github, and second friend had issues with his WiFi constantly disconnecting which we couldn't solve.
That might also be a general network drivers vs. kernel version problem as well. I've had that on some Ubuntu falvors on various cards, it isn't specific to just wi-fi, it happened on lan as well (just disconnects for a few ms and then connects again).
And yeah, one of the many reasons why I usually buy second hand hardware as well. One, it's a lot cheaper, two, drivers for Linux are usually not a problem 😁.
Those have gotten a lot better in recent years. Last time I had an issue with WiFi drivers was in 2016.
Graphics drivers, on the other hand, especially Optimus...
Some of us are still recovering from the trauma
I never have. Just thinking about WiFi and Bluetooth drivers on random laptops still puts me into a full flashback state. (My first experience was back in 2002, I think?)
However, getting all of that stuff working was the best learning experience I ever had. At the time, I was just learning about IT security and WiFi pcap was all the rage back then.
Same, flashbacks to being in college trying to get Wi-Fi working in Fedora on my laptop and then struggling to get it to work with my uni's new Wi-Fi system. Frustrating, but a great learning experience as you said.
I still tell myself bluetooth is unnesessary and I'll fix it eventually or it'll just work iteself out..........
With you on that. I remember struggling in 2004 with WiFi drivers, ugh.
I sometimes still think about the time I was trying to print in 1996.
Iwlwifi firmware-a0-gf has not been detected… 😔
Even a decade ago it usually meant ticking a box that you also allowed nonfree drivers.
Even Debian allowed you to download the specific nonfree driver you needed and add it (without Internet) at imaging so post install you could connect with wifi and not just Ethernet.
It's come a long way. But doesn't anyone else remember when windows did not have drivers and you'd constantly be confronted with "have disk"?
I mean, the amount of drivers for old hardware I still have saved... Because before win10 nothing would reliability always fetch the driver you need from the net...
This reminds me of the big USB drive of drivers that we had at a PC repair shop. When Windows 7 failed to find drivers, we’d stick that in and give it a scan.
I remember that, but for Xp. Downloading a “driver pack”, pointing windows at the root of the folder, and praying.
Ticking the non-free driver box was child's play. As late as like 2012 I remember needing to download NDISwrapper so I could make the windows drivers work through a compatibility layer
I mean, if you buy broadcom you reap what you sow. And 2012 was 11 years ago. ;-)
When I bought my laptop i was using windows and didn't research Linux compatibility :(
And yup. A decade ago was when Linux turned a corner on the wifi driver front, 11 years ago was hell
I recall jaunty jackalope being the Ubuntu version that became my full time os. It was that version that my IBM x31 had everything taken care of on install with the third party drivers checked. I feel like the LTS version following that was where you could buy a generation previous of any hardware and it'd work without much fuss.
I apologize for my general grumpiness this morning. Totally reasonable. :-)
I lol'd. :-)
The nvidia driver has had this bug for a year now, still unfixed. Games will randomly crash with an Xid 109 error in dmesg. Some people (including myself) are unable to play games like Cyberpunk, Resident Evil 2-3-4-7-8 and Metro Exodus. And it’s not linked to proton either, it sometimes also crashes xorg itself, forcing a reboot. I’m starting to think nvidia will never bother fixing it.
3% desktop marketshare, it's stop to pick up money, not go out of your way money.
I just had to deal with nvidia breaking xwayland and making it unusable with an update
Please get this bad boy working well on rolling release, then:
https://gitlab.com/TuxThePenguin0/bes2600
Having the device, I already tether the wifi. But it is indeed a compatibility issue: the old kernel drivers for the chip were janky and it’s doubtful how well they even worked the time. The code is apparently such a hot mess that the people who were working on it have stopped making progress. There is now skepticism that it will ever be fully functional.
Have some respect for the classics
Yeah, you're too young to remember the glory days 😂.
All my Wi-Fi just works on any machine I have Linux on. But yeah years ago this was not the case.
Now you get to struggle with audio drivers!
Audio drivers have never really been a problem in my experience, but maybe you’re referring to pulseaudio? In which case, pipewire has been great!
There's this one Bluetooth speaker with a microphone that I have, that I had hoped to use for calls, that has just refused to work. Spent hours trying to get them to work but had to admit defeat. But yes, things have improved significantly.
It works great until you try to use Bluetooth anything and need to connect and disconnect regularly (it can literally freeze your entire system), and don't get me started with trying to get digital surround to work
Agreed 👍.
Am I supposed to have Wifi driver issues? My laptop's one always worked flawlessly without me having to even look at it
Wi-Fi used to be a pretty common thing to not work out of the box or to break in updates. I kept a usb Wi-Fi dongle in a bag as a backup just because of this.
It's a really simple problem to avoid, and IMO has been for years. It's been at least 10 years since I've bought something without intel wifi so maybe I'm out of touch, but I'm kind of astounded there are so many upvotes to the meme.
My rule for a very long time has been: Get something with intel wifi, or even atheros wifi, and you will almost certainly not have a problem. Get broadcom wifi and your problem will directly relate to how much effort your distro has put into trying to make broadcom not be shit. Stay the fuck way from realtek and mediatek.
That's it. I literally can't recall a time since about 2010 when I had a wifi problem with Linux on any device I owned.
I keep two of these in my bag for instant wifi on any device I might happen to be working on that doesn't have it. Most recently popped one into an old desktop I picked up for my youngest son, and have used it previously as a workaround for someone who had a laptop where the onboard wifi worked but would not come back from sleep. (That was broadcom, IIRC)
Trust me when I say this, that wasn't always the case 😔.
ndiswrapper flashbacks o_o
I thought I had completely erased this from my memory. Turns out I did not. I would thank you if it wasn't such a traumatic experience.
I am so sorry.
You are a bad person
I accept this.
Oh no. My broadcom laptop chip from 2005 was a major pain in the ass and this did not help 😆
Yeah those were some dark times.
Debían 3.0... good times.
BROADCOM .....
Amusingly enough, one of the HP laptops I used in that era actually worked better with ndiswrapper somehow.
It was the only one to do so though.
Miracles happen I suppose. :D
"It's a ndiswrapper miracle!" - a statement only uttered by the completely deranged.
Lemmy needs polls. The last time I had problems with WIFI drivers was... 15 years ago? On a laptop bought in a supermarket that originally came with Windows Vista. Oh, and the raspberry pi - fuck raspberry pis. They can't pick wifi module worth shit.
I mean it isn't Linux fault, but I wanted to install balenaos on my RaspberryPi and they don't support a WiFi chip in their kernel. Without WiFi the whole idea won't work for me. And I don't want to buy a new WiFi usb only because they don't want to add the drivers.
My attempts to add it to the kernel and build it myself failed so far.
I'm not faulting linux, I'm faulting the Raspberry Pi Foundation. Linux is their main operating system and they haven't picked a good WIFI hardware module for years. Dunno if the new raspberrypi 4 is better, but I'm not paying to find out.
Quick correction, the Pi5 is the new one
Thanks. I'm out of the loop.
All single board computers have driver problems because they require custom kernel forks that can't or don't get mainlined for whatever reason (usually laziness), but Raspberry PI is actually the best when it comes to that stuff.
So when you buy an SBC, you need to ask yourself: will the company continue to develop/update/patch their custom kernel fork now that they shipped? Or will they just abandon it and move on to the next product? 9 times out of 9.01, it's the latter.
I am running a pi 1. No WiFi included. The usb I have worked for everything so far
That's the only thing that worked for me too. The inbuilt WiFi is useless.
On pi 4 with raspbian no issues. Didn't try a different os on that yet
Try Void, maybe it has the adequate firmware binary blobs... worth a try 🤷.
Had problems about 3 years ago, got a new laptop from work and the WiFi hardware was too new and didn't have support in the kernel yet. Took a year or something, maybe less, until it worked.
For new hardware, it's no surprise when it doesn't work out of the box as most drivers are written for windows first. That's not a fault of linux.
Yep, just saying I had problems.
Raspberry, seriously? What problems are you seeing?
I have a raspberry pi 3 acting as a 5GHz access point for as long as it's been on the market, I can remember one time I had to restart it because of some wonkiness. About a dozen others as clients, never had an issue there either, fast and stable enough.
All using the default os (raspbian first, raspberry os later).
I've had 3 raspberry pis (1,2,3) and none have had stable WiFi. After an hour or two it would drop and the logs would get spammed with some error that I can't remember. Might be this issue wlan freezes in raspberry pi 3/PiZeroW (Not 3B+) . Similar issue Every two hours, like clockwork: "wpa_supplicant[313]: nl80211: kernel reports: key addition failed".
After that, I gave up on WiFi on Raspberries and used LAN, but they are so underpowered... my nextcloud instance took ages to do anything, XBMC (now Kodi) was slow and couldn't render videos > 720p (it was struggling with 720p honestly), even a simple audio proxy over bluetooth (forward bluetooth audio from phone to speaker) barely functioned as the bluetooth cut out or it was janky as hell.
It's easier to put a old phone as a server than a raspberrypi.
Might be some AP incompatibility maybe, I've never seen those.
XBMC didn't have drivers for video acceleration, but the raspberry pi 1 was able to play 1080p flawlessly if you used omxplayer.
Now kodi has the drivers included and the 4 can even play 4k up to certain bit rate.
The new ones are too expensive tho, a used NUC is a much better deal.
Lucky you. Tried 4 different routers --> same issue.
I gave up on RasPis long ago.
Welcome to 90% of all the anti-Windows arguments made on here by Linux users.
I'm not sure I follow... are you saying Linux users judge windows by very old problems?
There are some oddball cards out there that need the linux firmware xxx (insert manufacturer instead of xxx) binary blobs in order to work, but yes, those cards are rare nowadays and mostly older hardware uses that (as you mentioned, hardware from 10+ years ago).
To be fair most wifi device manufacturers are bastards and don't publicise manuals.
Fucking fuck realtek
Tell me you haven't used Linux in the past ~20 years without telling me you haven't used Linux in the past ~20 years
Tell me you haven't used more than 2 or 3 pieces of hardware in the past 20 years without telling me you haven't used more than 2 or 3 pieces of hardware in the past 20 years.
I thought you thought about WiFi drivers because of the extra difficulty on not being able to search online, but I see now that this is just based on real experiences
My Intel Wireless AC 7265 on my Sony VAIO begs to differ. Certainly not brand-spanking new but it's AFAIK less than 10 years old. The speed would at some point drop under Void Linux.
At least my notebook doesn't support the newer wifi standards, that I would need at the university eduroam network.
I always have to hook up my phone and use usb-tethering
WPA3?
I don't remember if it was WPA 3 or WPA 2 Enterprise.
If the card supports at least WPA2, it should support WPA2 Enterprise as well. Only cards manufactured in the last few years support WPA3. I doubt they would enforce WPA3 only.
Recently it started working, but only sometimes and for about 5 min's and I can't reproduce it at all.
Tried installing firmware packages?
Jesus Christ OP use trigger warnings
Broadcom
*shudders*
Broadcom looks good next to Realtek, and both of them stand head and shoulders above Mediatek.
WiFi be like that
🤣🤣🤣
This was true maybe 10 years ago, nowadays Linux has better driver support than Windows. Printers, networking, input devices, everything I've tried is plug n play with Linux, Windows you gotta driver hunt.
Extremely outdated, but would still work with fingerprint sensors or NFC readers
Absolutely not outdated. I had a horrible time getting my hands on a working driver for the WiFi card in my brand new laptop last year. Horrible enough to resort to Ubuntu and even that gave me the finger. When I finally had it working I had to manually rebuild the damned thing each kernel update because I couldn't convince DKMS to do it automatically. Had to wait two or three kernel releases for the card to be supported 'out of the box'.
So no, fuck WiFI drivers in Linux. If it is not in the kernel and the manufacturer doesn't provide one, don't expect fun times.
Situations like that aren’t very common these days. It usually happens when your hardware is very much new and drivers aren’t yet in the Linux kernel, or they are in the newest mainline, but your distro wont ship it for some more time. For that matter, it’s always bad when the kernel doesn’t have the drivers built in and it always requires dealing with DKMS or akmod whether it’s wifi, webcam, bluetooth or GPU (that’s why NVIDIA tends to be problematic on some systems).
That being said, the meme only works for anecdotal cases.
Outdated for
LinuxIntel, still valid for Broadcom, probably not so bad for somewhat recent Realtek and AMD/Mediatek (last I've read is that Mediatek WiFi hardware sucks in general and disconnects happen on Windows, so the same happening on Linux would be the fault of the Linux driver).EDIT: Accidentally wrote Linux instead of Intel.
I can absolutely confirm it's still valid for Realtek. I had one using the RTL8812AU chipset that basically no kernel version nor distro provided out of the box, so I constantly had to download a third-party driver from Github and manually patch it via dkms, or use a third-party repository containing the driver package... and then the driver broke so badly that it wouldn't let me update at all unless I uninstalled it, which left me without the internet I needed to actually update, effectively leaving me unable to update until I could buy another one from Mediatek that's compatible.
And said Mediatek wifi is really slow, so I just went from the frying pan into the fire...
Yeah, and I was explicitly writing about recent chips. RTL8812AU isn't recent. The very latest Windows driver is from 2018, so the chip itself was released a good while before that.
I know exactly what you had to go through because I had to do the same with mine a couple of years ago but since then for newer chips Realtek started contributing to Linux itself:
USB tethering your WiFi-connected phone would have worked as stop gap just as well. I had to do that a lot.
Ahh I see, thanks for clarifying. It seems that where I live mostly only has the older Realtek chips for sale, so I likely mostly had bad luck.
I tried USB tethering, but it wouldn't work for some reason... I don't remember exactly what happened, but I think either the phone or my computer couldn't detect each other.
USB tethering should look on the PC just like plugging an Ethernet cable.
In my cause it was actually a newer type of Realtek chip. 😞
But was the cause the Linux driver or the hardware? If the fault is the hardware and the experience on Linux is the same as on Windows, it's feature parity.
If in doubt, get an Intel WiFi card. Even in otherwise not upgradeable notebooks those are usually not soldered on. Also whatever is in a Steam Deck OLED looks like a good pick.
Does Intel sell wifi cards that use USB rather than PCI slots? My motherboard doesn't have the slot for a wifi PCIe card, and I've only seen Intel sell those :/
AFAIK the problem is that the chip itself was only developed with the PCI protocol in mind.
I see, that is a shame...
It was the driver, now that support is provided by the kernel it is rock-solid.
Realtek upstreamed their drivers in 2020 or 2021. I got rid of my last notebook with Realtek hardware for unrelated reasons.
I installed linux on a new pc 2 days ago, had no problem with the wifi drivers. I don't know if it's the fact that the wifi is integrated on the motherboard, but it was up and running without any tweeking from me (unlike windows)
This could be shorted to if your device has no driver it wont work which is obviously true.
If you have very recent hardware and you find it doesn't work out of the box on stable options the easiest thing to do is install a more recent kernel. Even current Ubuntu non-LTS is 2-4 releases behind.
https://learnubuntu.com/install-mainline-kernel/ alternatively you can use a third party kernel repo which has a recent build with extras https://xanmod.org/ I'm using the second option.
It's even easier in arch/void where the latest kernel is already available.
Respectfully if DKMS wasn't automatically kicking in then you configured it incorrectly. It's a lot easier to just rely on a package that sets this up for you properly. If for some reason this can't be done the logical thing to do is script the process so that all operations are completed in the appropriate order that way you needn't remember to do one then the other.
What I tried to tell is that if you have to rely on community driver projects, don't expect fun times, at least not when it comes to Realtek in my recent experience.
I already had the latest available kernel at the time, as in: the very latest officially released kernel by kernel.org. Ubuntu was just a last-ditch effort as it will sometimes have drivers included that other distros might not have, normally I wouldn't touch it with a ten-feet pole and go either Arch or Manjaro. The driver simply wasn't included in the kernel. How do I know? Because I stumbled upon some discussions that mentioned the lack of support and 3 kernel releases later support for my card was specifically mentioned in the changelog.
Yes, like a Realtek-XXXX-dkms package, which simply didn't work. I've configured stuff for DKMS before, scripting stuff for Linux is part of my daily workload, so yeah, you don't need to tell me scripting beats doing stuff manually.
The fact that getting an f*cking wifi card to work takes this much effort is what I meant with 'not fun times' and for me validates the meme, anecdotal as it might be.
Resorting to other distros, configuring additional repos so you can install a different kernel version, having to try different community projects to see which gives you a working driver, having to deal with getting DKMS to work, this is all stuff which hampers Linux adoptment. And without more adoptment we won't have to expect more support from manufacturers for desktop related consumer hardware. So yeah, that does make me cry a bit. It's a catch-22 unfortunately.
I do occasionally fall for just buying shtuff without a quick google search to see if my kernel would be cool with it, but I have an even greater number of stories about good experiences with Windows shtuff driving me bonkers.
For example, the Brother ADS-1200 under WIndows beats anything SANE supported scanners can do hands down. Scan to PDF with excellent compression and top of the line OCR. The spousal unit needed a scanner and I found a good deal on an ADS-2100. Under Linux, scan results are totally comparable to the ADS-1200, so the hardware is fine. But the Windows software for this scanner is crap. JPEG and TIFF are identical to the Linux scans, but OCR and PDF compression are atrocious. I'm 100% sure that if I were to edit a table in the ADS-1200 software, it would happily apply the same excellent results to the ADS-2100. But I've had it with hacking Windows goop, been there, done that, got the t-shirt, so onto Craig's list the 2100 goes... Built in obsolescence, welcome to the Windows world.
With Linux, once the kernel accepts it, it's smooth sailign without too many vendor introduced hickups.
And even on Windows, if you need to use third party scan software like VueScan because your scanner happens to be older than your Windows. it'll work but it won't outperform SANE supported scanners.
I had a case where fingerprint sensor was working out of the box fortunately. Although I had a problem where cryptfs would stop authenticating successfully with fingerprint sensor after distro update
What display manager do you use? I have not been able to get Howdy to work without also typing my password with SDDM
Am I the only person who doesn't have WiFi problems?
10-15 years ago, it was a problem dire enough to drive me back to windows until about the start of the pando, and I've not even thought about Wi-Fi drivers since coming back to Linux.
I did have issues with a cheap USB Wi-Fi dongle thing a few years back, but that was likely the fault of the dongle more than anything else, I know because it didn't really work under widows either.
It's not so bad if you're running a major distro kernel and they do some prerelease testing before cutting new kernel packages. But if you're using the latest release from the kernel.org stable tree WiFi driver regressions happen somewhat regularly.
Why tho
Ah, a very common use case.
The one I had was completely minor. The wifi on my NUC doesn't work if you use the proprietary driver but it does work with whatever the kernel for Mint 21.2 has in it.
I don't think I have for more than a decade and I'm kinda amazed at how many upvotes this meme got.
from when this shit comes from, 2000?
I had a similar experience trying to install a m.2 drive in my win7 PC. It needed a hotfix to work but Microsoft had taken down the downloads so I ended up finding out it was in an update pack from I think Lenovo's website and pulled it out of that.
It's called manual driver install in Windows... pretty common with older hardware.
Most of those just go over Windows Update now or work with a generic driver that comes with Windows. Only really obscure drivers need manual installation.
Agreed. Most drivers are found through Windows update.
I guess I just have old hardware 🤷. My latest hardware is 9 years old... well, apart from my phone 😂.
6 years ago, I was using a USB wifi adapter with my desktop (my friends next door paid for internet and we paid them half the bill to share).
I had picked this wifi adapter specifically because it had linux support, even though I used windows (I had an inkling I'd switch). So, I tried to switch but upon boot I couldn't wifi because the adapters module wasn't bundled by my distro so I had to instal 'dkms', but I couldn't do that without an internet connection...
So yeah, it can still bite you.
lol, could you realize your story would be the same if you just replaced relevant software names?
Windows shipped with said driver.
eh, next time pay linux owners and spare a reboot :D
Phew. For a second there I thought the book would be about Bluetooth in Linux.
This is the real problem.
15 years ago this was an issue on my laptop.
deleted by creator
I have a few wifi adapters from china who only work properly under Linux lmfao
Did Microsoft actually infiltrate Lemmy or something? I'm hearing of issues about Linux that haven't existed since the very first days of desktop Linux
I still have wifi woes on my old tablet. Works fine for a few minutes, then dies. Works fine in Windows. I'm about to reinstall on it. Maybe the next distro I try will work?
This is probably some sort of firmware power management bug that the windows driver is working around. Try and see if you can find any documentation on it
The wifi chipset on my new MSI mobo isn't supported on current LTS version of Mint - I had to install a more recent kernel, so there are still issues with newer hardware
Yeah, the Chinese stuff seems to work better under Linux... for some reason 😂. I one based on a Realtek chip (I think 🤔) and I couldn't get passed a few hundred KB in Windows. Linux fried that baby, it did 1.5MB 😂.
The last time I had an issue with Linux drivers was in 2002, trying to set up a pppoe connection. I had no smartphone and there were no YouTube, Reddit, wikis, forums etc.
Back in 2016 I helped install some wifi drivers on a friend's laptop in Ubuntu 16.04, which was not really a big deal.
I feel like these memes are made by Windows users :)
I just think you've had the luck of not having a lot of unsupported hardware on Linux 😂.
Yes, in general, things are OK driver wise, but remember when we had to resort to ndiswrapper to get wifi working... yeah, that was a pain 😔.
If you think that's bad, try wifi on FreeBSD
Or to get anything past wifi 4, or to use 5ghz
It's bullshit because there are many products on the market running freebsd with great wifi (PlayStation as one example)
Just goes to show you that permissive licenses are generally not a good thing 🤷.
Meh, I still generally prefer them. Not like everyone would be able to use the PlayStation wifi hardware anyway
Each to his own ☺️ 🤷.
Wait, what's past 5Ghz
6ghz (wifi 6e)
Wait, actually? I have WiFi 6 at home and its on 5Ghz
Yeah 6e (not 6) utilises 6ghz
Could you tell me how I could do that? I don't think FreeBSD jails support anything other than the linux compatibility layer
At least I found someone who likes Yorushika!
Cut her some slack, she's barely 21. At 21 I was a nugget of dung when it came to technicalities like this
What killed my interest in Linux in highschool. Kept trying to get Ubuntu working but couldn't get the internet to work for anything. Given that every help guide boiled down to "Go to this website and download x" and I didn't have internet because... no wifi, I ended up getting frustrated enough to quit the whole thing. Maybe someday.
How long ago was this?
This was back in 2007-2008 ish. I believe the Ubuntu version was feisty fox at the time, if that helps.
I had similar problems at the time. It's much better now.
Weakling, I had this issue in highschool as well when first learning Linux, I just didn't do any of my assignments
Hey, as long as I ignore the thousand of entries in the error log I get every day from the iwlwifi kernel module crashing and restarting every 10 minutes its fine.
One must imagine iwlwifi happy
You can buy a external AR9271 WiFi adapter for $20 thats fully free software/free firmware.
Not in 2006
Or switch wifi cards, have done that as well when there was no other option.
There are whole-ass companies selling laptops with Linux preinstalled now. They work. Even with Bluetooth.
That's different. Lenovo supports the kernel, but doesn't ship some laptops with Linux. Two of mine (P14s Gen 1 and Gen 4) don't. I always have to work for NixOS, as does my friend for Arch.
They're too expensive. Plus some people buy a lot of their IT equipment second hand.
Me struggling with Realtek on Linux 🤝 One of my partners struggling with Nvidia on Linux
At least I managed to get a Linux-compatbile wifi USB later on, but it was pricey to import it and it's still quite slow :/
When I had a Nvidia card in my computer years ago i had to use an Nvidia ppa for drivers. It was the only way I could get it to work.
Nvidia PPA help
New distros have all this built in. Just use endeavouros or something if u really want the good stuff
well endoevouros is just arch and the nvidia-dkms package just works for currently supported cards (I think 9 series and newer)
Endeavouros worked out of the box though, so for new users I'd recommend it over arch. It even worked with my Nvidia prime gpu
I put my comment there meaning like any arch based distro should just work
This is true today. Had you tried that back in 2005, you'd very likely be fiddling with drivers. I specifically remember making a disk that contained all the drivers I'd need if I had to reinstall for any reason. Without it and without a network, you'd have to have another computer available to grab drivers from the internet.
You had to do this with windows in 2005 too... In fact I've had to use a different computer to download drivers as recently as 2017 for a Windows 10 computer...
Well, yes. I wasn't really intending to make a comparison. I was just explaining the meme. There was a time when getting your wifi/network card going in Linux was somewhat of a hassle for many.
Windows 10 comes with generic drivers for network capabilities preinstalled. It isn't Windows 7 anymore.
This vibes with me, but fifteen years ago me.
Installed Ubuntu on my first netbook and had to sit in the stairs to the second floor jacked into the single Ethernet cable we had for a few hours to troubleshoot it.
I haven't used every distro, but it seems like most of them are plug and play these days.
That's why I keep a 20m ethernet cable handy at all times 😂.
I just keep Windows handy :p
(Yes, I'm trolling)
I just installed mint on a new laptop. The wifi surprisingly didn't work on the liveusb, but switching to the Edge release with a newer kernel worked fine.
Lots of people saying this is an old problem , but I have a new IdeaPad I bought a few months ago and any non-rolling release distro I find, the wifi hardware isn't detected.
Until just a few weeks ago I couldn't find any solution. Fortunately I finally found a way to build the drivers, but it still requires me to tether my phone to get internet long enough to download the source.
So the problem might be better but it's not the non-issue some people are pretending it is.
Swap the module for an Intel one.
Why not use LAN instead?
Try Windows. It regularly breaks drivers (not only WiFi) on some hardware (mostly HP). I've never had issues with WiFi on Linux on HP, Dell, Microsoft Surface and even a Macbook.
Damn, your knowledge of Windows must be subpar.
I didn't say I couldn't fix the issues, but the fact that some of those issues exist even since XP is pretty bad. Just search around online and you'll find many posts about these driver issues. And then there's all of the ui inconsistencies and issues. Most of those are small, but still annoying once you see them. Especially when using Windows on a tablet, even Microsoft's own Surface line.
For HP ZBooks for example there was an issue that completely prevented you from installing some updates like Windows 10 20H2 without any warning as to why it wouldn't install. It just failed at 61%. It turned out to be audio drivers for the audio chip in the dock. The only way to get it updated was to connect the dock, finding the audio device in device management and removing it. Then disconnect before Windows reinstalls the driver again.
This has happened for multiple versions.
The thing is, there's "iwd" and "wpa_supplicant". You use either one or the other, but not both. Sources like the Gentoo handbook will tell you that but, not all Wiki's do as good a job of pointing that out <...looking directly at you Arch...>.
...although, to be fair, a lot of distro's just kinda sort it out for you.
I use Void BTW 😁.
I don't understand anything to do with network configuration, I just install a few packages (iwd and wpa_supplicant included), start a few services, run a few commands, and hope it magically works after rebooting
Never had problems with WI-Fi, but Nvidia Optimus
Good lord Nvidia fucking optimus
Funny that my brand new laptop just arrived today and its own wifi card wasn't recognized in Windows, so I had to use my phone via usb-tethering. It's a Lenovo Yoga Slim 7 (14APU8) by the way, Ryzen 7th gen, full AMD, OLED etc. It came without any OS (no way I'm paying for Windows lol) and my first Win11 experience on this laptop was "please choose a network to continue" and no networks were displayed at all, because wifi card had no drivers (Realtek btw). Windows setup wouldn't let me continue without a network, but there was no way to have a network. Funny Win11 moment right there. After some hours configuring everything I then installed my usual dual-boot Fedora and everything worked even in the live-usb. This meme is not valid for Linux anymore. Windows however, now thats a meme.
Trust me, it is. There is some obscure hardware out there. Plus, a lot of us still use hardware that was late XP time released and ndiswrapper was still around. So, for some of these cards, there is still no drivers for Linux (or buggy/unstable ones).
I understand, but seeing this post right after my experience today was the biggest coincidence ever and kinda funny that it worked right away in Linux while in Windows I had to manually go get the drivers for it. Linux used to be bad, but it evolved A LOT in terms of drivers support while windows just kinda stayed the same. I remember facing the same problem of booting a new Windows install and having the wifi option completely gone (no drivers) in Windows 8... many years ago. Windows 11 and the experience is still the same. And it's a modern Realtek card, not even close to being obscure. This post + this experience today was just a nice internet moment
Agree on that part. It has gotten a lot better.
Still, I was hoping that they'll eventually solve some of the problems with the WiFi hardware back in the ndiswrapper days. As it turns out, it's 50/50. Some of it has drivers, some don't. Sure I could go hunting for untested unreliable alpha stage drivers and compile them myself, but I was kinda hoping that we would be passed that on over 95, 96% of the hardware there is out there.
Well I myself have no patience at all to compile stuff myself, I can say I am half casual half linux nerd. I'm in the middle. Compiling stuff is too much, especially drivers and low level stuff like that. At that point I will just give up on the hardware or the OS/distro. That's mainly why I still dual boot. I have a SIM Racing setup and even with drivers that exist already and many awesome community made GUI tools (like Overdrive GUI) that get updated almost daily (which is impressive), it still is very hit or miss and most of the times it is either not detected at all or just half working. Even after using linux myself since the Ubuntu 7 and Gnome 2 days, I still dual boot Windows because well... sometimes life is just more peaceful when you can just reboot your pc and have funcional hardware again. I work under linux and play under windows. That's peace for me. Except nowadays I am staring to play non-Sim Racing stuff on linux too because Proton is amazing. But it still requires a lot of manual labor to make it work. And when I teach linux to other people I always teach the dual boot way and how they can easily jump back to what they are used to. In your case.... I think I would just get a different wifi card if possible. If its an embedded one, well... maybe I would just get a new motherboard/device anyway, or just use another OS and call it a day. Sometimes it's the better way. In your case probably the amount of people that need drivers for hardware like yours is diminishing day by day, so the probability of it ever getting fixed also diminishes. I found out that in the Linux world it's always better to stay with mainstream hardware as much as possible.
This is definitely a meme for AntiqueMemesRoadshow lol
The good news: Broadcom got out of the labtop industry
Bad news: Broadcom is in the phone industry
Really? They don't do Wi-Fi and BT chips any more?
I think they still do some but its rare to find a Broadcom device
Try BSD
You win.
Strange. One of them main reasons I wiped my Dell XPS OEM Windows and installed Linux was for -better- WiFi behaviour.
I have installed Ubuntu, Pop!, or Mint as a fix for wifi issues on laptops probably about a dozen times over the past 20ish years.
I have never had a wifi issue with linux. My husband has had issues with Linux and wifi in 2007. But that was 2007.
That might be one of the very few cases.
Possibly. Some XPS models (~9310) cheaped out on the WiFi chipset, which was really bad at reconnecting after sleep/suspend on Win 10/11 right out off the box.
Tried a live Linux install and it worked perfectly, so made the switch as there was no Win-only software that I needed.
The first experience with anything can make a world of a difference ☺️. Good thing I'm stubborn 😂.
The very evening I installed Linux for the first time (I think it was Ubuntu 12.04), my Wifi stick was the first major hurdle. I was a teenager, had no idea about package managers and such, but the drivers for my stick were only available in an uncompiled format, so I had to first learn what build utils and kernel dev packages were, download them and their dependencies onto the windows PC of my dad and copy them onto a CD.
After I had figured all that out (took me.a while), I learned how to compile on the fly.
After I had run ./configure and it finallyfinally ran through without error, the config script had this last line:
Things have changed over the years, but they haven't changed enough.
Whenever I come across something I'd have to build myself, I just give up. No matter the instruction, there is always something wrong.
Compiling starts to work rather well once you've done it a few times. Especially when you get more used to understanding what ./configure tries to tell you. You should really try to get behind that, since you Linux will
https://youtu.be/dQw4w9WgXcQ?si=E9Ftjm4FfMg6F2IU
Here is an alternative Piped link(s):
https://piped.video/dQw4w9WgXcQ?si=E9Ftjm4FfMg6F2IU
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Allright. You've convinced me not to give up.
And that Rick Roll song perfectly sums up how I personally think of Linux. I will not be giving it up. And I will not be saying goodbye.
That is true on any LTS distro. Try rolling release, works without a glitch almost every time... well, at least on Void it does.
Interesting. I did not know about that. I'll be sure to give rolling a try then.
I read the previous comment and thought to myself "I bet there is some reply about LTS vs rolling release to this". I KNEW IT!
Yep, been in the same boat 😂. Was an LTS fan for a long long time till I realized... this shit ain't worth it 😂.
Everthing there is out there in 99% of the cases compiles against latest libraries. And well, LTS is just... lagging behind 🤷. So, you solve one lib dependcy and then, bam, another one pops up... OK, solved that one, bam, another one 😒... it just gets frustrating to compile stuff on LTS.
And then you get all sorts of errors from the package manager cuz you did the unthinkable - install latest libs on an LTS distro.
LTS is good for one thing only nowadays - servers.
This has to be the best script message I've ever seen 😂.
Netgear WiFi USB drivers. Weren't good for much, but this one message was true as fuck!
I've only had problems with wifi drivers twice, immediately after clean-installing fedora 38 on two different devices. Plugging my device into ethernet and updating fixed it instantly.
What do I do if my laptop doesn't have an ethernet port?
Not sure about iPhones, but I've used an android phone a couple times to both USB tether with data and to act as a WiFi receiver to download drivers in a pinch.
Use a second computer or a friend's one to download the updates, get a USB ethernet adapter (a 100mbps one is like $5), put the system drive in a computer with lan, tether with another device via USB (phone, pi zero, etc) or use a different version/distro. I'm sure there are a bunch of other solutions.
I guess an ethernet to USB adapter might be your next best bet.
Alternatively, you could USB tether your phone if you have a good data plan
If you are in the unlikely event that you don’t have ethernet port to plug your device into, and no cell service, such as I was, you can use a spare wireless AP to get wifi if you’ve got one
akmod and dkms to the rescue so you can watch as your kernel fights with the hardware in real time
I just do lspci and install the adequate firmware 😂.
Just wait for the nvidia drivers lol
My new laptop has a nvidia card in it. One time it stopped working after a update so I downgraded the drivers so I can wait entail the next update they do work. Besides that it have worked great. I am on fedora so rpmfusion is where the drivers are from.
Old meme
Remember ndiswrapper?
Don't remind me 😔...
No, that buried deep in the box with suppressed memories. So thank you for reminding me.
It’s been so much better…but I’m steeling myself to track down a WiFi direct bug that keeps disconnecting due to a timeout after 10 seconds. Linus give me strength!
Still using a super old wlan usb adapter and I'm like, it just works!
It's insane how I just had this problem today. Had to tear out my network card in my Asus VivoBook 16. The drivers aren't out for the MediaTek network card so I had to change it to an Intel one that I previously used.
Use that till the drivers get released... temporary solution, but there isn't a better one at the moment 🤷.
Capitalism at it's best...
This seems like a good thread to ask:
I have a Retropie and I use wpa_supplicant to manage my connection there. It looks like this: the router is downstairs and I use a repeater in the room next to the Retropie to have better wifi coverage upstairs. The router itself is reachable, but the signal strength is worse. So, as a fallback, I put both the router and the repeater connection in my wpa_supplicant config file with the router having a lower priority. Still, sometimes my retropie clings onto the worse connection for some reason and there is no way to change it but to do a complete reboot. If I just restart the wifi with ifdown and ifup, it will either not reconnect to any wifi at all or reconnect to the shittier connection again, it's kinda a fifty-fifty. A reboot will always properly choose the best signal tho and I am very confused why this is happening. Any ideas?
Set your wpa_supplicant to use the BSSID of the repeater's access point and don't put the SSID in the conf file. Then it will connect to only the repeater.
If the repeater just re-transmits tho main AP's BSSID and packets, you need a better setup. Cheap WiFi extenders do this and almost always cause collisions, making the overall speed slow at all points.
The best setup is to have multiple wired APs.
Have you checked what bands (channels) the repeater and the router use?
The repeater uses a fixed channel (I think I set it to 7 or 8) and the router is set to automatic channel selection. Do you think fixing the router's channel would help?
See if they're overlapping, do a survey with your phone and WiFiAnalyzer (or another app). If they're close or overlapping, set the router to a fixed channel as well.
Aight, I'll try that, thanks!
ReviOS for the Windows user. It's not a OS, but a collection of scripts which convert Windows in what it should have been.
Just use NTLite yourself
Thank you internet stranger, I'm getting a new computer soon and I will be trying this!
Is it smart enough to pull the activation code from the BIOS if I buy a computer that has that?
Please do not trust modified windows installs based on old (22H2) update packs, you're much better off debloating your fresh, up-to-date, already licensed install using some powershell wizardry...
Chris Titus has made a gui for this that you can access with a single powershell command. He also has made a guide on which settings he recommends to debloat a fresh install.
This way you aren't entrusting your OS, privacy and data to some random unsecure repack. I can find the link for you if you would like :)
Yeah, that occured to me. thank you.good looking out, friend. I accept your offer!
Apologies for not having seen this until now, if you are still wondering and haven't found the tool yourself, you can launch it by opening a windows terminal as admin and typing
as soon as chocolatey is installed a gui will launch allowing you to easily install common software, uninstall bloat, apply tweaks (such as disabling telemetry), and control windows updates. It's a great one stop shop for setting up any fresh/existing windows install, and is continuously updated with reliable and transparent documentation.
If you would prefer a video about the tool, the latest one is here: https://youtu.be/GQBRrVGgB_Q
Thank you kind internet stranger! ❤️
Here is an alternative Piped link(s):
https://piped.video/GQBRrVGgB_Q
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Works with 11 22H2. That's a year out of date.
It's the same problem that all the prepackaged modified Windows have when I go to try them out in a VM. They always seems to be way out of date and with all the security problems of Windows, I don't want to run an old version just to save the time of cleaning out the telemetry and bloatware. Powershell scripts are more robust for me.
If you want some irony, on a recent Ubuntu install I was able to access WiFi out of the box but the small windoze dual boot partition refused to connect to a WiFi 6 router. Tried upgrading driver, downgrading drivers, nothing... The computer came shipped with windows 10.
I only had issues with this when setting up Kali Linux for learning pen testing. Fedora it worked out of the box.
LPT: Swapping Wifi modules is (sometimes at least) stupidly easy to do. I had a shitty ::: spoiler Trigger Warning Realtek wifi card ::: and bought an Intel card to replace it for about 30 bucks. Begone random disconnects and packet drops. Note that this was on a laptop and it was still just an issue of removing a few screws and swapping modules.
LPT - Line Print Terminal? 🤨
Life Pro Tip
Gotta love notebooks and their weird and rarely wonderful Wifi-Chips attached via SDIO. Even the intel cards can have problems!
Now we’re in the realm of weird sound drivers from integrated chipsets. Thankfully sof-firmware exists
The state of coreboot on modern hardware
The security problems of Linux over Android
Isn't the main problem that most of them are proprietary, so they can't be shipped automatically if you want to avoid shipping a distro with proprietary software?
If you want to scream, try wifi drivers on BSD!
Printer are worse. try to get a decade old brother to print more than a half page without completely freezing and needing a hard restart. driver is unmaintained unfortunately.
on Windows the printer works perfect though. which makes me quite unhappy :|
wifi on the other hand is not a problem i can remember. even on a 15 year old laptop, the AUR has a driver that it extracts from a ancient .deb and then patches it to make it work with modern kernels. lovely.
What about cups, they have no driver for that printer there?
I have a LaserJet 1000, 20+ years old, only works Linux and Windows x86 😂... so I just set up a peint server and shared it 🤷.
The driver shows up as "cups + gutenprint" and as far i can tell there is no other. so i guess that is already the one and only available driver.
and i have to correct myself, it is a Canon, not a Brother. Canon MX300 from 2007.
I mean it is not that big of a deal anyway. there is a single Windows machine left in this household that i can use for print jobs. and yeah, maybe i could use it as print server, that is actually a interesting idea lol.
Try searching online for cups filters. Maybe someone made a custom filter file for that printer that works... worth a shot 🤷. I've had luck hunting down custom filters for some obscure printers in the past.
Setting up a shared printer in Windows is (could be) a PITA though... not being able to choose SMB versions can make your Linux setups with SMB a pain 😔. That's why I prefer Linux with samba as the print server, you can fine tune almost everything to make it work with any Windows and Linux install.
thanks for the tip, i will have a look!
and yeah, funny enough i had less problems getting SMB to work between linux and windows than windows and windows despite it being a Microsoft native.
Also, true story, LTSC 2019 can't see shares from LTSC 2021, but the opposite works without a problem 🤣. It was a bug, they eventually fixed it, but took them like a year or so (they threw the ball at users, not setting up the shares correctly 😒), and I already reinstalled all rigs with LTSC 2019, so... too late MS 🤷... I haven't used LTSC 2021 from that point on.
It's the newer Wi-Fi chips that have issues, those for which drivers aren't yet released. There always seems to be a year-long delay between the next gen laptops being released and the wifi drivers for them.
Well, now I've heard everything.
I specifically bought a Brother printer because they at least try to support Linux. My previous one Samsung was much worse, it had Google cloud print so I could still use it. But Google like always killed something people liked.
Every wireless adapter I've used in Linux for the last 10 years has worked flawlessly.
10 years ago was the turning point. I remember as late as 2010 -2012 having to use NDISwrapper to install the windows XP wifi drivers because there were no native drivers so you had to run the windows drivers through an emulation layer to get wifi to work. Even within the past 5 years I've had to compile my own fixes for realtek chips because the auto installed drivers were not working optimally
Yes, if it's on 5 to 10 year old hardware.
I haven't had any issues with new hardware, either.
I still have issues with certain ASUS cards that simply crash the whole system when it gets too high a load or something. I've never been able to find a solution for it and I fear I never will.
Chipset?
I just had a look. It's the Asus PCE-N10. From what I can find they have the Realtek RTL8188CE chipset.
Yeah, Realtek WiFi cards are known to be problematic in Linux. Lan as well, but not to that extent.
Just swap the card with another one, no need to pull hair over it, it will most probably never work like it should.
I've started using usb wifi adapters so I can easily swap them out if they don't work. Looks less neat to me but it is what it is.
They have a very very limited range. I have used them, but only if the AP is in the same room, otherwise, they crap out.
PS: Everything's built from reinforced concrete and cinderblocks/bricks around here (seismically active region), so we have trouble with all sorts of wireless signals, including WiFi and 3/4G. 5G is out of the question here. We do have the towers, but less than 1% of users actually use them.
Scanner drivers are worse.
But are you perhaps referencing to the situation with Broadcom just incrementing their chips and drivers for years, flooding the market with cheap but quirky chips? Do they still do that?
Have no idea to be honest, I stole the meme 😂. But yes, I have had problems with wifi drivers on Linux. Not a lot, but still.
And yes, I'm still trying to get an old Microtek scanner to work in Linux 😔.
Mine just stopped working with brscan5 driver. It was a fast and quiet mobile scanner with high quality output. The new one is bigger, slower and louder and runs 90% of time in some photo mode. 🙁
edit: clarified
Have no idea what that is to be honest 😂.
Yet the Bluetooth drivers are great. What gives?
Having coded against them, I'd argue that point. They're just as bad as Wi-Fi.
Yeah, they came in later on and that's why I think they were "better"... learned from experience with the wifi drivers. And they weren't really better, most of them still use binary blobs.
I think it very depends on your hardware. I, personally, never had problems with it, on thinkpad which I use right now WiFi drivers were out of box even in Gentoo minimal ISO(It uses iwlwifi). But, every hardware that I have is about 10yo. And I think I haven't any non-intel WiFi-cards.
But also one of my friends had to compile drivers for his card manually from github, and second friend had issues with his WiFi constantly disconnecting which we couldn't solve.
And also I never had nvidia chips, I have one very old from AMD, and other computers use just intel integrated graphic.
Yeah, I use whatever integrated I can get 😂. Don't game, 2 monitors is more than enough for me, so 🤷 😂.
That might also be a general network drivers vs. kernel version problem as well. I've had that on some Ubuntu falvors on various cards, it isn't specific to just wi-fi, it happened on lan as well (just disconnects for a few ms and then connects again).
And yeah, one of the many reasons why I usually buy second hand hardware as well. One, it's a lot cheaper, two, drivers for Linux are usually not a problem 😁.