You are not logged in.
Pages: 1
(I should have probably asked this question before Guidance in migrating from Connman to iwd+impala for ethernet+wifi.)
I installed connman when I initially set up this system 8 years ago or so, and the service is enabled and therefore has been running everytime I used this system, and I haven't used it to switch to WiFi for 7 years or so.
Then I didn't need it anymore, years have passed, and now it looks like connman is only aware of bluetooth and ethernet:
$ connmanctl
connmanctl> services
*AO Wired ethernet_e0d55e2dee05_cable
connmanctl> technologies
/net/connman/technology/bluetooth
Name = Bluetooth
Type = bluetooth
Powered = False
Connected = False
Tethering = False
TetheringFreq = 2412
/net/connman/technology/ethernet
Name = Wired
Type = ethernet
Powered = True
Connected = True
Tethering = False
TetheringFreq = 0I must have caused a breakage during these years without realizing it.
In the meanwhile I've changed ISP and router, but this should have nothing to do with the fact that my system has WiFi. Unless my mobo's wifi support broke at a hardware level?
Last edited by Enrico1989 (Yesterday 22:18:34)
Offline
lspci -knnhttps://wiki.archlinux.org/title/ConnMa … supplicant - do you still have wpa_supplicant installed/in use?
Offline
lspci -knn
https://paste.c-net.org/FenceBoiling
https://wiki.archlinux.org/title/ConnMa … supplicant - do you still have wpa_supplicant installed/in use?
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.
Offline
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
rfkill; ip a?
Edit: https://wiki.archlinux.org/title/ConnMan#Wi-Fi
Last edited by seth (Yesterday 14:07:25)
Offline
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 foreverOffline
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 (Yesterday 17:55:30)
Offline
What about the rfkill part of that command?
Ops, I forgot:
ID TYPE DEVICE SOFT HARD
4 bluetooth hci0 blocked unblockedPost a complete system journal
sudo journalctl -b | curl -F 'file=@-' https://paste.c-net.org/
https://paste.c-net.org/FrancoInvaded
Random guess, you never installed linux-firmware-intel on this machine?
Not since mid 2021, that's how old my bash shell history is.
Offline
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.
Offline
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 ![]()
Offline
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.
Offline
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
Offline
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 (Yesterday 22:23:24)
Offline
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.
Offline
Pages: 1