this post was submitted on 28 Aug 2025
773 points (99.2% liked)
linuxmemes
26991 readers
1441 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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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
sudo in Windows.
- No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. ๐ฌ๐ง Language/ัะทัะบ/Sprache
- This is primarily an English-speaking community. ๐ฌ๐ง๐ฆ๐บ๐บ๐ธ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
- Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
ย
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
This was also my first issue in Linux but it turned out my duel boot was somehow screwing things up. Windows broke WiFi for Linux, then when I booted into Windows it was broken there too. I blame Windows because it was right after a series of updates, but I have no idea why it'd impact other independent OS on other drives.
Unfortunately I forgot the solution. It was probably since bios impacting thing, like how they often say to disable fast boot and junk.
Devices are configurable via software. If windows managed to โflip a switchโ on the WiFi chip, it would affect Linux as well if it didnโt reset it on boot.
This. Way back in the day, I had a sound card that would absolutely not work in one OS unless I'd already booted into a different one and "activated" it with the driver there.
It might have been Win9x and WinNT, but it could just as easily have been Win9x and some early-ish version of RedHat.
But anyway, it would not surprise me to learn that the same sort of thing still happens with some hardware.
Ahh, ok that makes sense. Reading other posts, pretty sure my wifi chip is the same as OP.
Disable fast boot in your BIOS, else when you reboot, hardware is not re-initialized so if Windows loaded a custom firmware in the chip or set some stuff here and there, it may be incompatible with linux. If you dual boot, always disable FastBoot in the BIOS.
and at this point it's also worth noting that this is a setting in the UEFI setup, and this is different to the fast startup setting in windows that also needs to be turned off for other reasons.
Ohhh. Great PSA to some of us who start out.
I had this issue and it was a fast boot issue. I'd shut down windows and boot Linux and WiFi wouldn't work. A restart would fix it. With fast boot, windows doesn't actually shut down, it's more like a hibernate state. So the driver or whatever it's called was being held by the widows partition and wouldn't respond to another kernal.
I think windows does shut down, but the hardware in your computer does not, and so when booting linux, the hardware does not start with a fresh slate. It's not reinitialized, keeping configuration and possibly custom firmware from the other OS.
interestingly, it also means malware could also escape a reboot this way.. and for the network adapter, maybe it doesn't even need to be compatible with linux to work.
what you mean though is the fast startup setting of windows. that does hibernate the computer as you say, after it logs out the user.
You are correct. Fast startup used to be called fast boot, hence my confusion. And it looks like the current state of windows is saved in nonvolatile for fast startup, which I would consider not being fully shutdown, but that's probably semantics at that point.