Working with a new laptop, Asus s16 s5606. I replaced the Win 11 install with F42 Mate/Compiz spin.
I can get the WiFi interface to connect to my network but only with manual intervention. The interface card is an Intel BE201. There is no wired ethernet interface.
I have been unable to have the WiFi interface active at boot.
I see no "bios" setting to change nor is there a keyboard kill switch.
I'm using Network Manager but I've tried systemd-networkd and iwd as alternatives.
Upon logging in, I can do one of three things, click on the NM applet and "enable WiFi" or from the command line use "nmcli radio wifi on" or some rfkill command, the syntax I've forgotten, to turn the radio on.
Any suggestions as to how to get the wifi card active and connecting during boot?
Am 16.05.2025 um 00:31:13 Uhr schrieb Jon LaBadie:
I can get the WiFi interface to connect to my network but only with manual intervention. The interface card is an Intel BE201. There is no wired ethernet interface.
Describe the steps you do to make it work.
Any suggestions as to how to get the wifi card active and connecting during boot?
First give system info:
sudo journalctl --dmesg rfkill list nmcli
Open terminal and run 'nm-connection-editor'.Check your wifi connection in General it is box for connect automatically with priority 0 tick On Fri, 2025-05-16 at 00:31 -0400, Jon LaBadie wrote:
Working with a new laptop, Asus s16 s5606. I replaced the Win 11 install with F42 Mate/Compiz spin.
I can get the WiFi interface to connect to my network but only with manual intervention. The interface card is an Intel BE201. There is no wired ethernet interface.
I have been unable to have the WiFi interface active at boot.
I see no "bios" setting to change nor is there a keyboard kill switch.
I'm using Network Manager but I've tried systemd-networkd and iwd as alternatives.
Upon logging in, I can do one of three things, click on the NM applet and "enable WiFi" or from the command line use "nmcli radio wifi on" or some rfkill command, the syntax I've forgotten, to turn the radio on.
Any suggestions as to how to get the wifi card active and connecting during boot?
-- Jon H. LaBadie jonfu@jgcomp.com
On Fri, May 16, 2025 at 06:42:04AM +0200, Marco Moock wrote:
Am 16.05.2025 um 00:31:13 Uhr schrieb Jon LaBadie:
I can get the WiFi interface to connect to my network but only with manual intervention. The interface card is an Intel BE201. There is no wired ethernet interface.
Describe the steps you do to make it work.
After graphical login, right click NetworkManager applet icon. From menu select "enable WiFi".
OR
At command line, Virtual Terminal (no graphics) or terminal emulator (Mate environment) type "nmcli r{adio} wifi on".
Any suggestions as to how to get the wifi card active and connecting during boot?
First give system info:
sudo journalctl --dmesg
What, all 1200 lines? On assumption the interface card messages are wanted, here is a grep for "iwl" of the output just after boot. (WiFi is not functioning)
<time> <host> kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) <time> <host> kernel: iwlwifi 0000:00:14.3: Detected crf-id 0x2001910, cnv-id 0x80930 wfpm id 0x80005b20 <time> <host> kernel: iwlwifi 0000:00:14.3: PCI dev 7740/00e4, rev=0x461, rfid=0x20112200 <time> <host> kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 7 BE201 320MHz <time> <host> kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.4.196 <time> <host> kernel: iwlwifi 0000:00:14.3: loaded firmware version 96.44729d4e.0 bz-b0-fm-c0-96.ucode op_mode iwlmvm <time> <host> kernel: iwlwifi 0000:00:14.3: Detected RF FM, rfid=0x20112200 <time> <host> kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4 <time> <host> kernel: iwlwifi 0000:00:14.3: loaded PNVM version 752be616 <time> <host> kernel: iwlwifi 0000:00:14.3: base HW address: 88:f4:da:74:44:74 <time> <host> kernel: iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
rfkill list
$ rfkill list 0: asus-wlan: Wireless LAN Soft blocked: yes Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no
WiFi is functioning but the output is the same before I activated wifi
nmcli
$ nmcli wlo1: connected to jgLAKEx "Intel Wi-Fi" wifi (iwlwifi), 86:59:57:78:47:1E, sw disabled, hw, mtu 1500 ip4 default, ip6 default inet4 10.0.0.29/8 route4 default via 10.0.0.1 metric 600 route4 10.0.0.0/8 metric 600 inet6 2601:5cf:8500:dd30::b155/128 inet6 2601:5cf:8500:dd30:68e4:9496:68e:83d0/64 inet6 2600:4040:401f:c100:fd0a:83aa:83c9:8eab/64 inet6 fe80::c0b4:e539:c621:1089/64 route6 2601:5cf:8500:dd30::b155/128 metric 600 route6 fe80::/64 metric 1024 route6 2601:5cf:8500:dd30::/64 metric 600 route6 default via fe80::8e6a:8dff:fe4e:a32a metric 600 route6 2600:4040:401f:c100::/64 metric 600 route6 2600:4040:401f:c100::/56 via fe80::3ebd:c5ff:fe66:d32d metric 600 route6 default via fe80::3ebd:c5ff:fe66:d32d metric 600
lo: disconnected "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
p2p-dev-wlo1: disconnected "p2p-dev-wlo1" wifi-p2p, sw disabled, hw
DNS configuration: servers: 10.0.0.12 10.0.0.1 8.8.8.8 domains: labadie.us jgcomp.com jgcomp.org interface: wlo1
Obviously this is after WiFi was manually activated.
Here is output immediately after boot from a Virtual Terminal
$ nmcli lo: disconnected "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
wlo1: unavailable "Intel Wi-Fi" wifi (iwlwifi), CE:F1:7C:61:56:E1, sw disabled, hw, mtu 1500
Use "nmcli device show" to get complete information about known devices and "nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
On Fri, May 16, 2025 at 03:54:43PM +1000, Igor Bezrodnik wrote:
Open terminal and run 'nm-connection-editor'.Check your wifi connection in General it is box for connect automatically with priority 0 tick
The settings are the same as you show.
Jon
On Fri, 2025-05-16 at 00:31 -0400, Jon LaBadie wrote:
Working with a new laptop, Asus s16 s5606. I replaced the Win 11 install with F42 Mate/Compiz spin.
I can get the WiFi interface to connect to my network but only with manual intervention. The interface card is an Intel BE201. There is no wired ethernet interface.
I have been unable to have the WiFi interface active at boot.
I see no "bios" setting to change nor is there a keyboard kill switch.
I'm using Network Manager but I've tried systemd-networkd and iwd as alternatives.
Upon logging in, I can do one of three things, click on the NM applet and "enable WiFi" or from the command line use "nmcli radio wifi on" or some rfkill command, the syntax I've forgotten, to turn the radio on.
Any suggestions as to how to get the wifi card active and connecting during boot?
End of included message <<<
On 5/15/25 11:10 PM, Jon LaBadie wrote:
$ rfkill list 0: asus-wlan: Wireless LAN Soft blocked: yes Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no
That asus one is suspicious. Does "lsmod | grep asus" show anything? If it does, do "modprobe -r the_module_name" and see if the "rfkill list" output changes. If it does, then do "echo blacklist the_module_name > /etc/modprobe.d/asus.conf" and reboot. You could possibly lose the use of some special keys, but see if it fixes the wifi.
Am 16.05.2025 um 02:10:54 Uhr schrieb Jon LaBadie:
On Fri, May 16, 2025 at 06:42:04AM +0200, Marco Moock wrote:
Am 16.05.2025 um 00:31:13 Uhr schrieb Jon LaBadie:
I can get the WiFi interface to connect to my network but only with manual intervention. The interface card is an Intel BE201. There is no wired ethernet interface.
Describe the steps you do to make it work.
After graphical login, right click NetworkManager applet icon. From menu select "enable WiFi".
ORAt command line, Virtual Terminal (no graphics) or terminal emulator (Mate environment) type "nmcli r{adio} wifi on".
rfkill list
$ rfkill list 0: asus-wlan: Wireless LAN Soft blocked: yes Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no
$ nmcli lo: disconnected "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
wlo1: unavailable "Intel Wi-Fi" wifi (iwlwifi), CE:F1:7C:61:56:E1, sw disabled, hw, mtu 1500
That means something disables Wifi all the time in soft blocked mode.
Maybe give us the entire dmesg in an attachment.
On Fri, May 16, 2025 at 2:11 AM Jon LaBadie jonfu@jgcomp.com wrote:
On Fri, May 16, 2025 at 06:42:04AM +0200, Marco Moock wrote:
Am 16.05.2025 um 00:31:13 Uhr schrieb Jon LaBadie:
I can get the WiFi interface to connect to my network but only with manual intervention. The interface card is an Intel BE201. There is no wired ethernet interface.
Describe the steps you do to make it work.
After graphical login, right click NetworkManager applet icon. From menu select "enable WiFi".
ORAt command line, Virtual Terminal (no graphics) or terminal emulator (Mate environment) type "nmcli r{adio} wifi on".
Any suggestions as to how to get the wifi card active and connecting during boot?
First give system info:
sudo journalctl --dmesg
What, all 1200 lines? On assumption the interface card messages are wanted, here is a grep for "iwl" of the output just after boot. (WiFi is not functioning)
<time> <host> kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) <time> <host> kernel: iwlwifi 0000:00:14.3: Detected crf-id 0x2001910, cnv-id 0x80930 wfpm id 0x80005b20 <time> <host> kernel: iwlwifi 0000:00:14.3: PCI dev 7740/00e4, rev=0x461, rfid=0x20112200 <time> <host> kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 7 BE201 320MHz <time> <host> kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.4.196 <time> <host> kernel: iwlwifi 0000:00:14.3: loaded firmware version 96.44729d4e.0 bz-b0-fm-c0-96.ucode op_mode iwlmvm <time> <host> kernel: iwlwifi 0000:00:14.3: Detected RF FM, rfid=0x20112200 <time> <host> kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4 <time> <host> kernel: iwlwifi 0000:00:14.3: loaded PNVM version 752be616 <time> <host> kernel: iwlwifi 0000:00:14.3: base HW address: 88:f4:da:74:44:74 <time> <host> kernel: iwlwifi 0000:00:14.3 wlo1: renamed from wlan0
rfkill list
$ rfkill list 0: asus-wlan: Wireless LAN Soft blocked: yes Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no
WiFi is functioning but the output is the same before I activated wifi
nmcli
$ nmcli wlo1: connected to jgLAKEx "Intel Wi-Fi" wifi (iwlwifi), 86:59:57:78:47:1E, sw disabled, hw, mtu 1500 ip4 default, ip6 default inet4 10.0.0.29/8 route4 default via 10.0.0.1 metric 600 route4 10.0.0.0/8 metric 600 inet6 2601:5cf:8500:dd30::b155/128 inet6 2601:5cf:8500:dd30:68e4:9496:68e:83d0/64 inet6 2600:4040:401f:c100:fd0a:83aa:83c9:8eab/64 inet6 fe80::c0b4:e539:c621:1089/64 route6 2601:5cf:8500:dd30::b155/128 metric 600 route6 fe80::/64 metric 1024 route6 2601:5cf:8500:dd30::/64 metric 600 route6 default via fe80::8e6a:8dff:fe4e:a32a metric 600 route6 2600:4040:401f:c100::/64 metric 600 route6 2600:4040:401f:c100::/56 via fe80::3ebd:c5ff:fe66:d32d metric 600 route6 default via fe80::3ebd:c5ff:fe66:d32d metric 600
lo: disconnected "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
p2p-dev-wlo1: disconnected "p2p-dev-wlo1" wifi-p2p, sw disabled, hw
DNS configuration: servers: 10.0.0.12 10.0.0.1 8.8.8.8 domains: labadie.us jgcomp.com jgcomp.org interface: wlo1
Obviously this is after WiFi was manually activated.
Here is output immediately after boot from a Virtual Terminal
$ nmcli lo: disconnected "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
wlo1: unavailable "Intel Wi-Fi" wifi (iwlwifi), CE:F1:7C:61:56:E1, sw disabled, hw, mtu 1500
Use "nmcli device show" to get complete information about known devices and "nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
Do you have iwlwifi-dvm-firmware or iwlwifi-mvm-firmware installed?
Also, you might consider updating the laptop's UEFI/BIOS to the latest version before going down a rabbit hole.
Jeff
On Fri, May 16, 2025 at 02:49:40AM -0400, Jeffrey Walton wrote:
On Fri, May 16, 2025 at 2:11 AM Jon LaBadie jonfu@jgcomp.com wrote:
...
Do you have iwlwifi-dvm-firmware or iwlwifi-mvm-firmware installed?
It is the iwlwifi-mvm-firmware package.
Also, you might consider updating the laptop's UEFI/BIOS to the latest version before going down a rabbit hole.
There was a bios update available about a month ago. I'll check if that was already applied (probably not) before I received my unit.
Got to get some bed time now (4AM local). It will be a while before I can do the update if needed.
Jeff
On Fri, May 16, 2025 at 04:02:02AM -0400, Jon LaBadie wrote:
On Fri, May 16, 2025 at 02:49:40AM -0400, Jeffrey Walton wrote:
Also, you might consider updating the laptop's UEFI/BIOS to the latest version before going down a rabbit hole.
There was a bios update available about a month ago. I'll check if that was already applied (probably not) before I received my unit.
Got to get some bed time now (4AM local). It will be a while before I can do the update if needed.
I've updated the UEFI/BIOS to the current version (305, dated 4/11, was 302). I've seen no change in the wifi cards behavior.
I noticed the card loads firmware from /lib/firmware, namely iwlwifi-bz-b0-gf-a0-96.ucode, while versions 97 and 98 are also present in the directory.
On a whim I installed the kernel from rawhide (6.15.0-0 vs 6.14.6-300) and rebooted. The card still does not activate on boot but the newer "98" firmware is loaded into the card. Looks like the problem will be present for a while to come.
On Thu, May 15, 2025 at 11:30:15PM -0700, Samuel Sieb wrote:
On 5/15/25 11:10 PM, Jon LaBadie wrote:
$ rfkill list 0: asus-wlan: Wireless LAN Soft blocked: yes Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no
That asus one is suspicious. Does "lsmod | grep asus" show anything? If it does, do "modprobe -r the_module_name" and see if the "rfkill list" output changes. If it does, then do "echo blacklist the_module_name > /etc/modprobe.d/asus.conf" and reboot. You could possibly lose the use of some special keys, but see if it fixes the wifi.
Good idea. The driver for "asus-wlan" is listed as "asus-nb-wmi". lsmod reported it as having no dependents and dependent on "asus-wmi".
Removal from the running system caused no apparent problems (after about 5 minutes) but the wifi was already up and running. I forgot to check rfkill.
But I did add a blacklist conf file to /etc/modprobe.d and rebooted. Now rfkill shows 2, not 4 devices. The asus- devices for wireless and bluetooth were gone. AND wifi was up and running automatically.
A look at lsmod showed that both asus-nb-wmi and asus-wmi were no longer being loaded even though I blacklisted only one.
That's a step in the right direction, thanks Samuel and all. Now to see if there are any negative impacts.
-
Igor Bezrodnik -
Jeffrey Walton -
Jon LaBadie -
Marco Moock -
Samuel Sieb