when i install zorin first my internal wifi detected and worked too. but after reboot it is disappeared or hidden and show no wifi adapter found. but show in lspci last i checked. it happen most linux os i have tested. another after that it worked little bit stuck, look like suspicious to me someone hacked or maleware but cant identify or confirmed using clamav. any suggestion?
What sounds most likely is that at point of install, you are using the Generic Drivers (which work).
After install, the specific drivers for your wifi card are activated and probed by the kernel - but there is a flaw with the driver, and so it does not work.
You could just remain on the generic driver though we do not know off-hand whether that will provide the full speed and performance that a specific driver would.
So you might try installing a new variant of the specific driver, first.
Can you start a new thread and detail your Wifi Card make and model, include the output of
sudo lshw -C network
and describe the trouble you have been having (You could link to your post above) so that members can help troubleshoot it?
Not only this but sometimes internal wifi detected but new wifi name and conf like dir-615 1 and so on. I am using external wiri adapter now.
any hardening technique or tools protect from any cyber attack. Thanks for your time.
In addition to starting a new thread on checking your Wifi cards and drivers, you might consider starting a new Discussion thread in Chat about Zorin covering hardening and security techniques. There are a great many.
This is a really really weird thing that never made sense to me, but be sure to disable "Fast Startup"[1] and "Hybrid Sleep" on Windows if you're dual-booting.
I never understood why and how Windows can break Networking on other operating systems like this, but the only way to fix it was to disable these two features. Yes, this will make Windows boot slower.[2]
Note that when I say "Fast Startup" I mean the option in Windows, NOT the one in your BIOS Configuration screen. ↩︎
but that's only because when these features are enabled your PC never really shuts down. It just saves everything to RAM and then goes to sleep, appearing to be turned off. ↩︎
Windows OS introduced a method of what Microsoft calls "Fast Startup" that gives the appearance of a quicker boot.
This is misleading, however. Windows OS does not boot, nor does it fully shut down.
Instead, it hibernates and when you "boot" the computer, it wakes from hibernation, giving the appearance of a faster "boot".
Since Windows OS is still running the entire time, it retains its lock on the essential hardware including Networking.
This is not a true hibernate setting and it is not made clear in Windows OS whether you are shutting down fully or just setting Windows OS into this hibernation state (it is automatically handled by Fast Boot); even grub can be fooled into thinking that Windows OS is down.
Windows Fast startup or Fast Boot is intended to give Windows OS the appearance of booting quickly. It is to their advantage that it hibernates, rather than a Full shutdown and Restart.
Otherwise, every restart would appear to suddenly boot slowly.
But you're right, it is trickier than just "Windows Hibernates every time."
When you click a shutdown option with Fast Startup enabled, Windows saves the kernel session and device drivers to the hiberfil.sys file. This is then loaded on startup so that Windows does not need to init from cold.
But when you reboot the computer, Windows OS is supposed to perform a full shutdown, then reinitialize all drivers and the kernel.
And it often does.
But... not always. I do not know why, either.
Sometimes it starts the process of a full shutdown, then switches to hibernate again part way through during a Restart.
