this post was submitted on 02 Dec 2023
1365 points (94.1% liked)
linuxmemes
21607 readers
911 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Nah, I don't currently have any problems with my hardware. I just happen to have acces to a lot of old hardware (at work) and play with that when I have some free time.
Of course, I also (still) dual boot. Mostly because of software that just doesn't run in Wine... and for work. But other than that, I'm mostly on Linux.