this post was submitted on 02 Sep 2023
2092 points (96.0% liked)
Memes
45751 readers
2217 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ah yes, windows where I have to somehow figure out how to install the drivers for my network adapter before I can actually connect to the internet, on top of having to go to a different website for each device that needs a driver to find the correct one, download it and install it.
Vs Linux, where network (and most essential) drivers are baked into the kernel, and all other drivers (for peripherals, etc) can be had via a package manager, where you can often find free and open source solutions. Also, video drivers are automatically installed with the OS (provided you are using a distro with a proper graphical installer for ease of use, cough use Endeavour cough), and automatically updated when the system is updated.
Sounds like you clearly haven't used Windows in over a decade, or even close to two.
I haven't had to install a network driver since Windows XP. Even then it had drivers for most cards built in.
I haven’t tried to use Linux for desktop in a while, probably as long as they haven’t used windows. Because in my mind what they said is 100% backwards.
Seems like both have matured quite a bit
And Windows update takes care of 99.9% of missing drivers automatically.
You're right about the network drivers, but on things like serial drivers, Windows is a fucking nightmare. Hell, I can't use some devices because FTDI drivers will brick the device if it decides its a knockoff of their chip. Getting anything working that isn't consumer grade is a shit show.
Serial drivers? Are we talking rs232? (Checks what tf ftdi is)
Ah yes. We really are talking about very old school stuff. It brings back memories.
This week I learned we have a waterslide connected through rs232 to a pi in our network. How's that for a IOT discovery. Working for a medium sized municipality really shows you all the bonkers solutions (and implementations) out there. If you can think a IT horror up, chances are good somebody really has created it and is using it commercially.
Back to your issue, which is more a Ftdi issue then a windows issue since they themselves create the crashing drivers. And I can see how an old school serial port, connected to a modern pc can result in all kinds of havoc when done wrong.
I see FTDI also have usb to rs232 solutions. That should work... Mostly. (as long as the solution doesn't go looking for an irq or other horror from the past.)
I'm really getting curious for what use case you're still using rs232. Most network gear these days is perfectly managed without it.
USB to serial converters are what use these drivers and they're used all day long for IOT stuff
Make that 2 decades I gather. Maybe even 3. This sounds like nt4 territory. Maybe barelu6 win2k.
I was a windows user up until about a year and a half ago, and had this issue as recently as Windows 10. I had to use my phone as a tether to go download the drivers for my TP-Link Archer T6E. Also had the issue with my MSI z97m Gaming where I had to go find drivers for the built-in wired network adapter, again using my phone as a tether, on Windows 8.1
Idk, I just built a PC with Realtek mobo integrated wifi, we couldn't even install the OS because it didn't detect the NIC and Windows forced us to sign in before it would continue the installation.
Had to lug the machine to a router to get anywhere, and still had to download the Asus mobo software to get the wireless going. Wasn't convenient in the least.
So.... You didn't check your installation requirements. Is that what you're saying?
And this wouldn't have happened with Linux?
Nope. Because Realtek commit their drivers directly to the Linux kernel, they may be a bit slower getting the driver to the consumer depending on their internal team that's developing/handling the driver and how long the code review takes on the kernel maintainer side but even then you can generally get the driver early e.g. before it's merged into the kernel via a dkms a.k.a out-of-tree driver (easily found in something like the AUR). Once the Realtek WiFi driver is merged you don't have to worry about it because it'll be in every distro with the following kernel release.
We had a USB prepared with drivers in advance, but that's useless when you can't get to a desktop. I admittedly didn't realize you couldn't even install Windows 11 without an active network.
Linux would at least let me install the base system and configure the drivers after. Funny enough that USB mentioned is my ventoy and we did experiment with Linux Mint before we started on Windows. It found the NIC and network on the live ISO with no effort, I honestly thought it would be smooth sailing after that experiment.
I would have just gone with mint personally but wasn't my system, was just helping a friend.
For in the future, I suggest using USB tethering via your smartphone to get WiFi to the device.
That's big brain stuff, will keep that in mind next time
This doesn't happen in windows anymore. Over 95% of all drivers auto install.
Yeah the last time I had to install drivers for a network card on Windows was over a decade ago
I had to install a network adapter driver the other day. Had to use my wife's computer to download into a flash drive and bring it over to my computer with zero network connectivity.
Granted, this only happened because my network card was broken.
In my old tech bin there's a bag of usb WiFi dongles and a thumb drive with all the drivers.
I work in a Win-centric PC shop. USB dongle (WiFi or Ethernet adapter) is by far the best way. Virtually all drivers download automatically with rare exceptions (specifically GPU drivers or weird import components).
I just installed Windows on my daughter’s new [to her] computer last night and this did not happen. Don’t get me wrong, I loathe Windows, but c’mon.
Yeah I've installed Windows about ten times in the last ten years for various people and I've never encountered any of this. It is as close to flawless as I can ask for.
I had the ethernet in my desktop mobo not work when I tried upgrading to win11. Worked fine in 10 but no internet on 11.
I also had a very difficult time getting a Xbox wireless controller adapter working on win 10 without spending about 2 hours searching.
Windows usually works but sometimes it just fucking doesn't. Linux isn't perfect either but I usually don't have issues with my Ethernet ports not working.
What kind of weird or shitty NIC you're using that needs a specific driver for Windows?
Lenovo IdeaPad Pro 5 Gen 8 Notebook comes with a MEDIATEK MT7922. Windows 11 does not want to install unless you circumvent the requirement for Internet or supply it with a manually downloaded driver.
Linux? Just works.
TP-Link Archer T6E, one of the most popular on the market
The wireless kind, presumably. Those always need their own firmware and therefore their own driver.
I tend to have driver issues more so with Linux than windows in my experience. Both seem to be capable at the very least of automatically installing a lot of the drivers without user intervention.
You'd have more driver issues with Windows if you used hardware that wasn't already being sold with Windows pre-installed by OEMs/system integrators. Comparatively Linux supports a wider verity of hardware for much longer, Windows on the other hand only really supports consumer grade hardware that's likely to have it pre-installed anyway with a limited (and often predestined) EOL.
If manufacturers treated Linux desktop as first class like with Windows or Linux on Servers then there'd be a very small amount of unsupported & likely obsolete hardware.
I'm not sure how any of the different hardware components I bought to build my system had Windows pre-installed, considering I had to install Windows myself.
Sir, do you know what OEMs/system integrators mean?
You're very likely using hardware components OEMs/system integrators use in their consumer products (in fact I'd bet on it), in which incentivizes hardware manufacturers to write & maintain proper Windows drivers for said components, because of money and contracts; that is until the hardware goes EOL and the development and maintenance ceases to continue from that point.
That's where Linux is different; it may not be able to support all consumer hardware from day one (if at all in some cases; tho this is getting better with time), since all the (in-tree) drivers are open source there isn't a true EOL and the driver can receive proper maintenance, improvements, security patches, etc. long after the support has gone EOL on Windows.
This very thing is why Linux is so good at reviving hardware that Windows doesn't or can't support anymore.
In fact Linux probably officially supports more consumer grade hardware then Windows 11 specifically because of the TPM tomfoolery that blocks hardware from installing it in the Microsoft approved fashion (even though the hardware is easily supported through unofficial means).
I've only ever had to search for NIC drivers on Linux.
Windows usually packages most drivers into the update process automatically and the device manager page can find whatever drivers you need for whatever hardware it can detect.
When I first tried Windows XP, I had to figure out how to install storage drivers in order to install the OS.
And back at that time if you installed any flavor of Linux you were lucky if the OS install didn't fuck itself over, also God help you find drivers, assuming that they even existed. At least xp would function.
As of windows 10, windows will always function on pretty much any hardware out of the box. Some obscure Chinese WiFi dongles might have some issues, but main board drivers are always right there.
Linux users have this weird echo chamber where they seem to think that Linux just works. It can but it's a 50/50 chance that it won't and you'll spend hours troubleshooting. Also os updates on Linux have a high probability of borking the entire os.
Windows, for all of it's many many faults, generally does "just work". It might not be perfect, but it will function.
I was using Linux religiously back then, and this is false. As long as there's a driver for all of your hardware, it generally worked fine.
But that “as long as” is doing some heavy lifting. The usual suspects were pretty much the same as now: Broadcom, NeoMagic, and NVIDIA. Some cheap printers and modems were problematic as well, but if you paid for good hardware, it would probably work.
And that's the rub. You have to very specifically choose your hardware for Linux. Or at least you had to back then. It's not quite so bad now, but back then it was a real showstopper. Especially broadcom. That caused me no end of issues back in the day.
If you want to have some fun install Windows 10 on a hard drive. Disk usage will go to 100%. It doesn't do this on SSDs except maybe very rarely. I'm pretty sure this is not a bug, but intentional so that people will buy a new PC. Windows 7 will run flawlessly on the same hardware. Although Linux is starting to demand higher hardware specs than it deserves.
Do you realize WINXP is TWENTY FOUR years old now???
I do now. Was blissfully unaware of that particular milestone in making my feel my years until you mentioned it, however.
The Rust based Cosmic DE is looking awesome.
I can't wait to try it when it releases.
I had a similar situation with my ryzen 1600 motherboard, except it was the sound card. Everytime windows updated it would dump the driver I installed and try another one that was broken. I had to keep my sound drivers on the desktop so I could reinstall them. This occurred even after I reinstalled windows 10 on a different ssd.
Nowadays it's more of a fight against the update-provided drivers though.