https://paste.c-net.org/FenceBoiling
The package wpa_supplicant is installed, the iwd package too (I don't remember when, maybe some very old attempt), but the iwd.service is inactive and disabled, whereas connman.service is active and enabled, so I think the answer is yes/yes.
04:00.0 Network controller [0280]: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
Subsystem: Intel Corporation Dual Band Wireless-AC 8265 [8086:1010]
Kernel modules: iwlwifiDevice is there, also in
?
Edit: https://wiki.archlinux.org/title/ConnMan#Wi-Fi
Last edited by seth (2026-06-12 14:07:25)
It looks like it isn't?
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether e0:d5:5e:2d:ee:05 brd ff:ff:ff:ff:ff:ff
altname enxe0d55e2dee05
inet 192.168.1.12/24 brd 192.168.1.255 scope global enp5s0
valid_lft forever preferred_lft forever
inet6 fe80::e2d5:5eff:fe2d:ee05/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
What about the rfkill part of that command?
Post a complete system journal
sudo journalctl -b | curl -F 'file=@-' https://paste.c-net.org/Random guess, you never installed linux-firmware-intel on this machine?
Last edited by V1del (2026-06-12 17:55:30)
V1del wrote:
What about the rfkill part of that command?
Ops, I forgot:
ID TYPE DEVICE SOFT HARD
4 bluetooth hci0 blocked unblockedV1del wrote:
Post a complete system journal
sudo journalctl -b | curl -F 'file=@-' https://paste.c-net.org/
https://paste.c-net.org/FrancoInvaded
V1del wrote:
Random guess, you never installed linux-firmware-intel on this machine?
Not since mid 2021, that's how old my bash shell history is.
The firmware split happened last year: https://archlinux.org/news/linux-firmwa … ervention/ -- you will have gotten a list of firmware packages as optional new ones to install. And the journal confirms it your iwlwifi doesn't find it's firmware, so install that and reboot and retry.
Weird... That was 2026/06/13, and here's what my shell history contains:
$ history | grep linux-firm
17959 27/06/25 12:16:42 pacman -Rdd linux-firmware # pacman -Syu linux-firmware
17960 27/06/25 12:16:54 sudo pacman -Rdd linux-firmwareSo I didn't miss the news, but I messed it 
Jun 11 23:52:46 greywarden kernel: iwlwifi 0000:04:00.0: no suitable firmware found!pacman -Qs firmware # lacks intelPlease always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
That worked! Yes, I'll do, but there's another weirdness now. If I connect to WiFi, something goes wrong with the "display". It turns out, problem and solution are both described at https://wiki.archlinux.org/title/ConnMa … e_hostname
I suppose it's still relevant: if I have SingleConnectedTechnology=false, which according to the wiki should allow being connected simultaneously via Eth and WiFi, then why "scan wifi" errors with "Error /net/connman/technology/wifi: Not supported"? I don't think §4.1 applies, because 1. I don't get that error if I SingleConnectedTechnology=true, and 2.
$ rfkill list
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: noLast edited by Enrico1989 (2026-06-12 22:23:24)
Are you using iwd and is that connection active when trying to scan (and SingleConnectedTechnology=false but not connected when using SingleConnectedTechnology=true)?
Compare "ip a" w/ either condition and check/track the journal for scanning failures.
Mmm, I think some reboot was needed at some point.
After a new boot, and after I've used connmanctl to connect to the wifi, "ip a" gives this:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether e0:d5:5e:2d:ee:05 brd ff:ff:ff:ff:ff:ff
altname enxe0d55e2dee05
inet 192.168.1.12/24 brd 192.168.1.255 scope global enp5s0
valid_lft forever preferred_lft forever
inet6 fe80::e2d5:5eff:fe2d:ee05/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
4: wlan0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether f8:34:41:da:f7:3c brd ff:ff:ff:ff:ff:ff
inet 192.168.1.10/24 brd 192.168.1.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::fa34:41ff:feda:f73c/64 scope link proto kernel_ll
valid_lft forever preferred_lft foreverand I could successfully SSH into both 192.168.1.12 and 192.168.1.10, for instance.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。