debian wifi but not arch hardblocked by systemd-rfkill
by hilltownboy from LinuxQuestions.org on (#59A0F)
The internet has many discussions about wifi being hardblocked by rfkill, but I haven't found a fundamental explanation that would account for my debian10 being hardblocked while my arch linux on the same old commputer (HPCompaq6910p) is not.
Following suggestions, I can boot debian to a working wifi after removing the battery and unplugging and replugging the power cord. This rigmarole is not needed to boot arch to a working wifi.
The hardblocking is controlled by a blue-lighted switch at the top of the keyboard and by systemd-rfkill.service. The latter stores the rfkill switch state in /var/lib/systemd/rfkill/ as follows (same for both debian and arch):
Code:-rw-r--r-- 1 root root 2 Jun 7 16:38 pci-0000:00:1a.0-usb-0:1:1.0:bluetooth
-rw-r--r-- 1 root root 2 Oct 4 10:25 pci-0000:10:00.0:wlan
-rw-r--r-- 1 root root 2 Jun 7 16:38 platform-hp-wmi:bluetooth
-rw-r--r-- 1 root root 2 Jun 7 16:38 platform-hp-wmi:wlanThe second line apparently defines the current unblocked state. There does not seem to be a systemd-rfkill command for adjusting the state.
This debian behavior began a few days ago when being connected to my town's newly-constructed fiber optic high speed line. Ant thoughts?
Following suggestions, I can boot debian to a working wifi after removing the battery and unplugging and replugging the power cord. This rigmarole is not needed to boot arch to a working wifi.
The hardblocking is controlled by a blue-lighted switch at the top of the keyboard and by systemd-rfkill.service. The latter stores the rfkill switch state in /var/lib/systemd/rfkill/ as follows (same for both debian and arch):
Code:-rw-r--r-- 1 root root 2 Jun 7 16:38 pci-0000:00:1a.0-usb-0:1:1.0:bluetooth
-rw-r--r-- 1 root root 2 Oct 4 10:25 pci-0000:10:00.0:wlan
-rw-r--r-- 1 root root 2 Jun 7 16:38 platform-hp-wmi:bluetooth
-rw-r--r-- 1 root root 2 Jun 7 16:38 platform-hp-wmi:wlanThe second line apparently defines the current unblocked state. There does not seem to be a systemd-rfkill command for adjusting the state.
This debian behavior began a few days ago when being connected to my town's newly-constructed fiber optic high speed line. Ant thoughts?