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.
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.