Samsung N210plus Wifi bios switch disabled but works

some days ago i disabled my onboard wifi inside the bios to work completly offline.
After restart the computer i recognized, that there is a established wifi connection through onboardchip.
This is suprised but also it shocks, because it seems, that bios switch is not recognized by kernel.
For me it is a security risk.
How could i completely disable onboard wifi?
I thought, that during kernelboot my available hardware is checked. The result should be, that there is no onboardwifi.
This is always the result if running windows.

I`m running the newest tumbleweed kernel.


You could blacklist the driver, (as long as you don’t need to use any other wireless device relying on the same driver). Just a matter of creating a file eg /etc/modprobe.d/blacklist.conf,

blacklist <name-of-driver>

Another idea would be to prevent the device from being managed by the network manager. For this, you’ll need to edit /etc/NetworkManager/NetworkManager.conf, adding the following


You can get the MAC address (HW address) for the wireless device from

/usr/sbin/hwinfo --wlan

Thank you,
but i think, that the underlying problem is the following:
Why and how is the kernel detecting my onboard-wifi? i deactivated wifi in bios.

Any clues?


I know what you stated, but clearly whatever state it is in, the driver is able to initialise it (or power it up).

You’ll find that the chipset is still active (even if the radio is off), and it will be reported by the kernel

/sbin/lspci -nnk

The device status is reported by

rfkill list

Thank you for testing the weed kernel, bug report is always welcome lol!

thank you for clarification.

should i block the adapter during every kernel boot, or is the status saved over several bootprocesses?


is it a bug? i’m not familiar enough with programming to say that.


Hard-blocking is usually as a result of being disabled via a hardware switch (or key combination), and so cannot be enabled via the rfkill utility - it only lets you query the status. Soft-blocking can be changed, but on boot the wireless hardware is re-intialised, so soft-blocking does not survive the reboot (in my experience). If you really don’t want the card to be user-controlled by NM, then make it unmanaged as I suggested before.