debian wifi but not arch hardblocked by systemd-rfkill
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
debian wifi but not arch hardblocked by systemd-rfkill
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:wlan
The 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?
ondodo:
The commands that you referenced are posted herewith. I believe that all they tell is that the network is down because wifi is hardblocked by rfkill. These were from login of debian10, but they do not answer the question of what is fundamentally preventing rfkill from allowing radio.
(A different problem is also demonstrated, i. e. that the program keeps trying to connect enp0s25 even though no wired cabled is connected.)
Code:
uname -rv
4.19.0-11-686-pae #1 SMP Debian 4.19.146-1 (2020-09-17)
lspci -knn | grep -EiA2 net
00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit Network Connection [8086:1049] (rev 03)
Subsystem: Hewlett-Packard Company Compaq 6910p [103c:30c1]
Kernel driver in use: e1000e
--
10:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection [8086:4229] (rev 61)
Subsystem: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection [8086:1000]
Kernel driver in use: iwl4965
Kernel modules: iwl4965
sudo dmesg|grep -Ei 'wlan|firmw|dhc'
[ 0.372601] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.385131] pci 0000:02:06.0: MMC cards are now supported by standard SDHCI controller
[ 3.470878] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/R520_cp.bin
[ 3.476353] sdhci: Secure Digital Host Controller Interface driver
[ 3.476355] sdhci: Copyright(c) Pierre Ossman
[ 3.524994] sdhci-pci 0000:02:06.3: SDHCI controller found [1180:0822] (rev 20)
[ 3.525155] sdhci-pci 0000:02:06.3: Will use DMA mode even though HW doesn't fully claim to support it.
[ 3.525175] sdhci-pci 0000:02:06.3: Will use DMA mode even though HW doesn't fully claim to support it.
[ 3.525413] mmc0: SDHCI controller on PCI [0000:02:06.3] using DMA
[ 3.525856] sdhci-pci 0000:02:06.3: Will use DMA mode even though HW doesn't fully claim to support it.
[ 16.806003] iwl4965 0000:10:00.0: firmware: direct-loading firmware iwlwifi-4965-2.ucode
[ 16.806012] iwl4965 0000:10:00.0: loaded firmware version 228.61.2.24
[ 18.326977] iwl4965 0000:10:00.0 wlp16s0: renamed from wlan0
[ 30.099088] iwl4965 0000:10:00.0: On demand firmware reload
sudo cat /var/log/syslog | grep -Ei 'net|wpa|dhc'
Oct 21 12:42:53 debian dhclient[535]: DHCPDISCOVER on wlp16s0 to 255.255.255.255 port 67 interval 12
Oct 21 12:42:53 debian sh[438]: DHCPDISCOVER on wlp16s0 to 255.255.255.255 port 67 interval 12
Oct 21 12:42:53 debian sh[438]: send_packet: Network is down
Oct 21 12:42:53 debian sh[438]: dhclient.c:2445: Failed to send 300 byte long packet over wlp16s0 interface.
Oct 21 12:42:53 debian dhclient[535]: send_packet: Network is down
Oct 21 12:42:53 debian dhclient[535]: dhclient.c:2445: Failed to send 300 byte long packet over wlp16s0 interface.
Oct 21 12:42:54 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 12:42:54 debian ifup[437]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 12:43:03 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 11
Oct 21 12:43:03 debian ifup[437]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 11
Oct 21 12:43:05 debian dhclient[535]: DHCPDISCOVER on wlp16s0 to 255.255.255.255 port 67 interval 16
Oct 21 12:43:05 debian sh[438]: DHCPDISCOVER on wlp16s0 to 255.255.255.255 port 67 interval 16
Oct 21 12:43:05 debian sh[438]: send_packet: Network is down
Oct 21 12:43:05 debian sh[438]: dhclient.c:2445: Failed to send 300 byte long packet over wlp16s0 interface.
Oct 21 12:43:05 debian dhclient[535]: send_packet: Network is down
Oct 21 12:43:05 debian dhclient[535]: dhclient.c:2445: Failed to send 300 byte long packet over wlp16s0 interface.
Oct 21 12:43:14 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 12:43:14 debian ifup[437]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 12:43:21 debian dhclient[535]: DHCPDISCOVER on wlp16s0 to 255.255.255.255 port 67 interval 8
Oct 21 12:43:21 debian sh[438]: DHCPDISCOVER on wlp16s0 to 255.255.255.255 port 67 interval 8
Oct 21 12:43:21 debian sh[438]: send_packet: Network is down
Oct 21 12:43:21 debian sh[438]: dhclient.c:2445: Failed to send 300 byte long packet over wlp16s0 interface.
Oct 21 12:43:21 debian dhclient[535]: send_packet: Network is down
Oct 21 12:43:21 debian dhclient[535]: dhclient.c:2445: Failed to send 300 byte long packet over wlp16s0 interface.
Oct 21 12:43:23 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 10
Oct 21 12:43:23 debian ifup[437]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 10
Oct 21 12:43:29 debian dhclient[535]: DHCPDISCOVER on wlp16s0 to 255.255.255.255 port 67 interval 4
Oct 21 12:43:29 debian sh[438]: DHCPDISCOVER on wlp16s0 to 255.255.255.255 port 67 interval 4
Oct 21 12:43:29 debian sh[438]: send_packet: Network is down
Oct 21 12:43:29 debian sh[438]: dhclient.c:2445: Failed to send 300 byte long packet over wlp16s0 interface.
Oct 21 12:43:29 debian dhclient[535]: send_packet: Network is down
Oct 21 12:43:29 debian dhclient[535]: dhclient.c:2445: Failed to send 300 byte long packet over wlp16s0 interface.
Oct 21 12:43:33 debian dhclient[535]: No DHCPOFFERS received.
Oct 21 12:43:33 debian sh[438]: No DHCPOFFERS received.
Oct 21 12:43:33 debian dhclient[535]: No working leases in persistent database - sleeping.
Oct 21 12:43:33 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 12:43:33 debian ifup[437]: No DHCPOFFERS received.
Oct 21 12:43:33 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 12:43:33 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 12:43:33 debian sh[438]: run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2
Oct 21 12:43:34 debian wpa_supplicant[493]: nl80211: deinit ifname=wlp16s0 disabled_11b_rates=0
Oct 21 12:43:34 debian wpa_supplicant[493]: wlp16s0: CTRL-EVENT-TERMINATING
Oct 21 12:43:43 debian ifup[437]: /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d
Oct 21 12:43:43 debian ifup[437]: run-parts: executing /etc/network/if-up.d/avahi-autoipd
Oct 21 12:43:43 debian ifup[437]: run-parts: executing /etc/network/if-up.d/avahi-daemon
Oct 21 12:43:43 debian ifup[437]: run-parts: executing /etc/network/if-up.d/wpasupplicant
Oct 21 12:43:43 debian ifup[437]: /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d
Oct 21 12:43:43 debian ifup[437]: run-parts: executing /etc/network/if-up.d/avahi-autoipd
Oct 21 12:43:43 debian ifup[437]: run-parts: executing /etc/network/if-up.d/avahi-daemon
Oct 21 12:43:43 debian ifup[437]: run-parts: executing /etc/network/if-up.d/wpasupplicant
Oct 21 12:43:43 debian systemd[1]: Started Raise network interfaces.
Oct 21 12:43:43 debian systemd[1]: Reached target Network.
Oct 21 12:43:43 debian systemd[1]: Reached target Network is Online.
Oct 21 12:43:55 debian systemd[1018]: Listening on GnuPG network certificate management daemon.
Oct 21 12:50:56 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 3
Oct 21 12:50:59 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 3
Oct 21 12:51:02 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 8
Oct 21 12:51:10 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 21
Oct 21 12:51:31 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 15
Oct 21 12:51:47 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 8
Oct 21 12:51:54 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 3
Oct 21 12:51:57 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 12:51:57 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 12:51:57 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 12:58:35 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 7
Oct 21 12:58:42 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 14
Oct 21 12:58:56 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 17
Oct 21 12:59:13 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 12:59:22 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 14
Oct 21 12:59:36 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 12:59:36 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 12:59:36 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 13:03:28 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5
Oct 21 13:03:33 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 6
Oct 21 13:03:39 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 6
Oct 21 13:03:45 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 12
Oct 21 13:03:57 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 17
Oct 21 13:04:14 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 14
Oct 21 13:04:28 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 1
Oct 21 13:04:29 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 13:04:29 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 13:04:29 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 13:11:31 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 6
Oct 21 13:11:37 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 13
Oct 21 13:11:50 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 13:11:59 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 13
Oct 21 13:12:12 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 11
Oct 21 13:12:23 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 13:12:32 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 13:12:32 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 13:12:32 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 13:19:42 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 3
Oct 21 13:19:45 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 7
Oct 21 13:19:52 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 14
Oct 21 13:20:06 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 21
Oct 21 13:20:27 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 8
Oct 21 13:20:35 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 8
Oct 21 13:20:43 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 13:20:43 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 13:20:43 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 13:27:08 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 8
Oct 21 13:27:16 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 13
Oct 21 13:27:29 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 15
Oct 21 13:27:44 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 7
Oct 21 13:27:52 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 12
Oct 21 13:28:04 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5
Oct 21 13:28:09 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 13:28:09 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 13:28:10 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 13:33:11 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 4
Oct 21 13:33:15 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 13:33:24 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 13:33:33 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 16
Oct 21 13:33:49 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 10
Oct 21 13:33:59 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 13
Oct 21 13:34:12 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 13:34:12 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 13:34:12 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 13:40:58 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5
Oct 21 13:41:03 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 7
Oct 21 13:41:10 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 8
Oct 21 13:41:18 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 11
Oct 21 13:41:29 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 21
Oct 21 13:41:50 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 13:41:59 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 13:41:59 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 13:41:59 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 13:47:47 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 6
Oct 21 13:47:53 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 11
Oct 21 13:48:04 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 11
Oct 21 13:48:15 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 14
Oct 21 13:48:29 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 14
Oct 21 13:48:43 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5
Oct 21 13:48:48 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 13:48:48 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 13:48:48 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 13:56:06 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5
Oct 21 13:56:11 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 21 13:56:20 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 17
Oct 21 13:56:37 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 13
Oct 21 13:56:50 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 16
Oct 21 13:57:06 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 1
Oct 21 13:57:07 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 13:57:07 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 13:57:07 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Oct 21 14:04:14 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 3
Oct 21 14:04:17 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 3
Oct 21 14:04:20 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5
Oct 21 14:04:25 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 14
Oct 21 14:04:39 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 8
Oct 21 14:04:47 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 14
Oct 21 14:05:01 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 10
Oct 21 14:05:11 debian dhclient[496]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 4
Oct 21 14:05:15 debian dhclient[496]: No DHCPOFFERS received.
Oct 21 14:05:15 debian dhclient[496]: No working leases in persistent database - sleeping.
Oct 21 14:05:15 debian root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
sudo rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Good news first: your driver recognizes the hardware and assigns a driver to it.
I also think it's normal that the system tries to connect to a wired network if wireless fails, again and again.
let's try to remove that hardblock.
I made some searches and came up with options:
"Hard blocked" cannot be changed by software, look for a wifi toggle on your keyboard or edges of the laptop; the device can also be hard blocked if disabled in the bios. Addition: that "toggle switch" can also be a key combo like Fn+F2 etc.
ondoho, thanks for your cheerful interest and help.
I have seen that statement that "hardblocked" cannot be changed by software and I believe that it is inaccurate or out of context. It is true that the rfkill program (as for example <rfkill unblock all> does not unblock hard blocks. In the following excerpt from my booting journalclt:
Code:
Oct 22 14:17:08 debian kernel: iwl4965: Intel(R) Wireless WiFi 4965 driver for Linux, in-tree:
Oct 22 14:17:08 debian kernel: iwl4965: Copyright(c) 2003-2011 Intel Corporation
Oct 22 14:17:08 debian kernel: iwl4965 0000:10:00.0: can't disable ASPM; OS doesn't have ASPM control
Oct 22 14:17:08 debian kernel: iwl4965 0000:10:00.0: Detected Intel(R) Wireless WiFi Link 4965AGN, REV=0x4
Oct 22 14:17:08 debian kernel: iwl4965 0000:10:00.0: device EEPROM VER=0x36, CALIB=0x5
Oct 22 14:17:08 debian kernel: iwl4965 0000:10:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
Oct 22 14:17:08 debian kernel: iwl4965 0000:10:00.0: firmware: direct-loading firmware iwlwifi-4965-2.ucode
Oct 22 14:17:08 debian kernel: iwl4965 0000:10:00.0: loaded firmware version 228.61.2.24
Oct 22 14:17:10 debian kernel: iwl4965 0000:10:00.0 wlp16s0: renamed from wlan0
Oct 22 14:17:20 debian kernel: iwl4965 0000:10:00.0: RF_KILL bit toggled to disable radio.
Oct 22 14:17:20 debian kernel: iwl4965 0000:10:00.0: RF_KILL bit toggled to enable radio.
Oct 22 14:17:20 debian kernel: iwl4965 0000:10:00.0: On demand firmware reload
Oct 22 14:17:20 debian kernel: iwl4965 0000:10:00.0: RF_KILL bit toggled to disable radio.
Oct 22 14:17:20 debian kernel: iwl4965 0000:10:00.0: Timeout stopping DMA channel 1 [0xa5a5a5a0]
Oct 22 14:17:20 debian kernel: iwl4965 0000:10:00.0: Timeout stopping DMA channel 3 [0xa5a5a5a0]
Oct 22 14:17:20 debian kernel: iwl4965 0000:10:00.0: Timeout stopping DMA channel 4 [0xa5a5a5a0]
Oct 22 14:17:20 debian kernel: iwl4965 0000:10:00.0: Timeout stopping DMA channel 6 [0xa5a5a5a0]
the rfkill bit is seen being toggled off, on and off. A service called systemd-rfkill "loads and saves the RF kill switch state at boot and change", according to the typically enigmatic description in the man page.
It does not explain how to change it if it is not set right.
As mentioned in my original post, the non-sollution that works for me is similar to the one you cite for Fedora. But that is not needed for arch linux on the same computer and was not needed for debian10 in the past.
Replacing the iwl4965 module did allow wifi temporarily but did not correct the hardblock problem on reboot. I wonder whether the last four lines in the code above regarding timeout is the problem. Unfortunately I don't understand what they mean.
I note that you have not refered to trying any actual keys on your device, or the BIOS.
Quote:
Originally Posted by hilltownboy
the rfkill bit is seen being toggled off, on and off. A service called systemd-rfkill "loads and saves the RF kill switch state at boot and change", according to the typically enigmatic description in the man page.
That does not necessarily mean that it succeeded.
But, try the following:
Code:
$> systemctl cat systemd-rfkill.service
Locate the ExecStart= line, and execute that command as root.
Does it say anything? Does it succeed?
ondoho: booted debian10 twice today and both times it came up with wifi connected. I don't know why it works today, but the one change that I made was the reinstall of the module iwl4965 yesterday that you suggested. Maybe that did it, and indeed the journalctl now reads rfkill toggled off,off, on instead of off, on, off.
I say "maybe" because my computer is 13 years old, does not have keys or a bios section relating to wifi (other than the blue-lighted switch previously mentioned) and when in debian, seems often to run slowly. That could be explained by someunseen virus infection or faulty portion of software not present in my arch OS.
In any case, thank you, and when and if it next boots incorrectly I'll try the "ExecStart" line command and see what happens.
ondoho:Today debian10 was hardblocked on booting. In order to try your ExecStart as in post#7, I had to read it using arch linux. To do that I had to shutdown debian10 and then boot it after shutting down arch. In fact I booted debian10 three times, and each time there was no hardblocking and wifi was connected.
That leaves me as confused as ever, and very likely you must be bored by now with this problem. It seems amazing that no fundamental explanation of systemd-rfkill appears in the man pages or Google.
The systemctl [unit][service] is identical in both OS's, except that debian10 also
includes "systemd-remount-fs.service" at the end of the [unit] "After" line. Perhaps of no consequence.
One other symptom?: the boot journal shows that "a start job is running for Raise network interfaces". It takes 1 1/2 minutes.
With debian hardblocked today, I ran the ExecStart command that you suggested
Code:
sudo /lib/systemd/systemd-rfkill
There was no response, other than a few seconds wait before restoring the prompt.
So I ran it with strace and got 400-odd lines ending with "exit with 1". Somewhere I got the impression that "1" is systemd-rfkill's default status, presumably meaning the previously set status.
One of your original suggestions does the trick, i.e., removes the rfkill hardblock (if only in my case). Remove and replace the iwl4965 module and radio is restored.
Code:
Oct 25 16:15:12 debian kernel: iwl4965: Intel(R) Wireless WiFi 4965 driver for Linux, in-tree:
Oct 25 16:15:12 debian kernel: iwl4965: Copyright(c) 2003-2011 Intel Corporation
Oct 25 16:15:12 debian kernel: iwl4965 0000:10:00.0: can't disable ASPM; OS doesn't have ASPM control
Oct 25 16:15:12 debian kernel: iwl4965 0000:10:00.0: Detected Intel(R) Wireless WiFi Link 4965AGN, REV=0x4
Oct 25 16:15:12 debian kernel: iwl4965 0000:10:00.0: device EEPROM VER=0x36, CALIB=0x5
Oct 25 16:15:12 debian kernel: iwl4965 0000:10:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
Oct 25 16:15:13 debian kernel: iwl4965 0000:10:00.0: firmware: direct-loading firmware iwlwifi-4965-2.ucode
Oct 25 16:15:13 debian kernel: iwl4965 0000:10:00.0: loaded firmware version 228.61.2.24
Oct 25 16:15:14 debian kernel: iwl4965 0000:10:00.0 wlp16s0: renamed from wlan0
Oct 25 16:15:24 debian kernel: iwl4965 0000:10:00.0: RF_KILL bit toggled to disable radio.
Oct 25 16:15:24 debian kernel: iwl4965 0000:10:00.0: RF_KILL bit toggled to enable radio.
Oct 25 16:15:24 debian kernel: iwl4965 0000:10:00.0: On demand firmware reload
Oct 25 16:15:24 debian kernel: iwl4965 0000:10:00.0: RF_KILL bit toggled to disable radio.
Oct 25 16:15:24 debian kernel: iwl4965 0000:10:00.0: Timeout stopping DMA channel 1 [0xa5a5a5a0]
Oct 25 16:15:24 debian kernel: iwl4965 0000:10:00.0: Timeout stopping DMA channel 3 [0xa5a5a5a0]
Oct 25 16:15:24 debian kernel: iwl4965 0000:10:00.0: Timeout stopping DMA channel 4 [0xa5a5a5a0]
Oct 25 16:15:24 debian kernel: iwl4965 0000:10:00.0: Timeout stopping DMA channel 6 [0xa5a5a5a0]
Oct 25 16:17:28 debian sudo[1053]: norman : TTY=pts/0 ; PWD=/home/norman ; USER=root ; COMMAND=/sbin/rmmod iwl4965
Oct 25 16:17:40 debian sudo[1070]: norman : TTY=pts/0 ; PWD=/home/norman ; USER=root ; COMMAND=/sbin/modprobe iwl4965
Oct 25 16:17:40 debian kernel: iwl4965: Intel(R) Wireless WiFi 4965 driver for Linux, in-tree:
Oct 25 16:17:40 debian kernel: iwl4965: Copyright(c) 2003-2011 Intel Corporation
Oct 25 16:17:40 debian kernel: iwl4965 0000:10:00.0: can't disable ASPM; OS doesn't have ASPM control
Oct 25 16:17:40 debian kernel: iwl4965 0000:10:00.0: Detected Intel(R) Wireless WiFi Link 4965AGN, REV=0x4
Oct 25 16:17:40 debian kernel: iwl4965 0000:10:00.0: device EEPROM VER=0x36, CALIB=0x5
Oct 25 16:17:40 debian kernel: iwl4965 0000:10:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
Oct 25 16:17:40 debian kernel: iwl4965 0000:10:00.0: firmware: direct-loading firmware iwlwifi-4965-2.ucode
Oct 25 16:17:40 debian kernel: iwl4965 0000:10:00.0: loaded firmware version 228.61.2.24
Oct 25 16:17:40 debian kernel: iwl4965 0000:10:00.0 wlp16s0: renamed from wlan0
In the middle of that code from journalctl you can see where radio was left hardblocked, but the rmmod and modprobe of iwl4965 went through the process, after which there was no more hardblocking of wifi.
Now if only debian would leave it that way permanently!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
https://www.linuxquestions.org/questions/linux-software-2/debian-wifi-but-not-arch-hardblocked-by-systemd-rfkill-4175683958/
