Troubleshooting iwctl / networking , unable to start on arch linux (wlan)

Question

I am unable to start iwdctl on newly installed arch linux. I have both wireless and wired connection. But i want to make sure the wired one is properly working. Prior to this, I had an unusual setup?

Here is what i found,

[plasma@narayana ~]$ systemctl start iwd Job for iwd.service failed because the control process exited with error code. See "systemctl status iwd.service" and "journalctl -xeu iwd.service" for details.

× iwd.service - Wireless service Loaded: loaded (/usr/lib/systemd/system/iwd.service; enabled; preset: disabled) Active: failed (Result: exit-code) since Wed 2025-09-03 00:08:12 WIB; 15s ago Invocation: 78609c40c3bd4acabd0e789d81a2336c Docs: man:iwd(8) man:iwd.config(5) man:iwd.network(5) man:iwd.ap(5) Process: 1788 ExecStart=/usr/lib/iwd/iwd (code=exited, status=1/FAILURE) Main PID: 1788 (code=exited, status=1/FAILURE)
   the output from `systemd-analyze blame` :

333ms dev-nvme0n1p1.device
214ms iwd.service
171ms [email protected]
161ms systemd-networkd.service
134ms systemd-udev-trigger.service
123ms udisks2.service
 90ms upower.service
 76ms systemd-journald.service
 74ms systemd-tmpfiles-setup.service
 54ms systemd-resolved.service
 52ms systemd-tmpfiles-setup-dev-early.service
 44ms systemd-udevd.service
 43ms systemd-journal-flush.service
 40ms accounts-daemon.service
 37ms polkit.service
 36ms systemd-logind.service
 36ms plymouth-read-write.service
 34ms plymouth-start.service
 34ms systemd-tmpfiles-setup-dev.service
 28ms dbus-broker.service
 25ms plymouth-quit-wait.service
 25ms efi.mount
 24ms systemd-vconsole-setup.service
 24ms plymouth-quit.service
 22ms home.mount
 21ms systemd-fsck@dev-disk-by\x2duuid-759f6fc2\x2d0535\x2d4342\x2d9f93\x2d5f6bb1486fb3.service
 20ms systemd-remount-fs.service
 19ms [email protected]
 19ms systemd-update-utmp.service
 19ms systemd-networkd-persistent-storage.service
 19ms systemd-userdbd.service
 14ms dev-hugepages.mount
 14ms dev-mqueue.mount
 13ms sys-kernel-debug.mount
 13ms sys-kernel-tracing.mount
 12ms tmp.mount
 12ms [email protected]
 11ms modprobe@dm_mod.service
 11ms [email protected]
 11ms [email protected]
 11ms [email protected]
  9ms systemd-modules-load.service
  8ms systemd-sysctl.service
  8ms systemd-network-generator.service
  8ms rtkit-daemon.service
  7ms systemd-udev-load-credentials.service
  5ms systemd-random-seed.service
  5ms systemd-user-sessions.service
  3ms sys-fs-fuse-connections.mount
  3ms sys-kernel-config.mount

When trying to look up via journalctl I am unable to find any usefull log.

333ms dev-nvme0n1p1.device
214ms iwd.service
171ms [email protected]
161ms systemd-networkd.service
134ms systemd-udev-trigger.service
123ms udisks2.service
 90ms upower.service
 76ms systemd-journald.service
 74ms systemd-tmpfiles-setup.service
 54ms systemd-resolved.service
 52ms systemd-tmpfiles-setup-dev-early.service
 44ms systemd-udevd.service
 43ms systemd-journal-flush.service
 40ms accounts-daemon.service
 37ms polkit.service
 36ms systemd-logind.service
 36ms plymouth-read-write.service
 34ms plymouth-start.service
 34ms systemd-tmpfiles-setup-dev.service
 28ms dbus-broker.service
 25ms plymouth-quit-wait.service
 25ms efi.mount
 24ms systemd-vconsole-setup.service
 24ms plymouth-quit.service
 22ms home.mount
 21ms systemd-fsck@dev-disk-by\x2duuid-759f6fc2\x2d0535\x2d4342\x2d9f93\x2d5f6bb1486fb3.service
 20ms systemd-remount-fs.service
 19ms [email protected]
 19ms systemd-update-utmp.service
 19ms systemd-networkd-persistent-storage.service
 19ms systemd-userdbd.service
 14ms dev-hugepages.mount
 14ms dev-mqueue.mount
 13ms sys-kernel-debug.mount
 13ms sys-kernel-tracing.mount
 12ms tmp.mount
 12ms [email protected]
 11ms modprobe@dm_mod.service
 11ms [email protected]
 11ms [email protected]
 11ms [email protected]
  9ms systemd-modules-load.service
  8ms systemd-sysctl.service
  8ms systemd-network-generator.service
  8ms rtkit-daemon.service
  7ms systemd-udev-load-credentials.service
  5ms systemd-random-seed.service
  5ms systemd-user-sessions.service
  3ms sys-fs-fuse-connections.mount
  3ms sys-kernel-config.mount

output from journalctl -xeu

Sep 30 19:30:00 narayana.search systemd[1]: Starting Wireless service...
░░ Subject: A start job for unit iwd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit iwd.service has begun execution.
░░
░░ The job identifier is 861.
Sep 30 19:30:00 narayana.search iwd[615]: No HMAC(SHA1) support found
Sep 30 19:30:00 narayana.search iwd[615]: No HMAC(MD5) support found
Sep 30 19:30:00 narayana.search iwd[615]: No CMAC(AES) support found
Sep 30 19:30:00 narayana.search iwd[615]: No HMAC(SHA256) support not found
Sep 30 19:30:00 narayana.search iwd[615]: No HMAC(SHA512) support found, certain TLS connections might fail
Sep 30 19:30:00 narayana.search iwd[615]: DES support not found
Sep 30 19:30:00 narayana.search iwd[615]: AES support not found
Sep 30 19:30:00 narayana.search iwd[615]: No CBC(DES3_EDE) support found, certain TLS connections might fail
Sep 30 19:30:00 narayana.search iwd[615]: No CBC(AES) support found, WPS will not be available
Sep 30 19:30:00 narayana.search iwd[615]: The following options are missing in the kernel:
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_USER_API_HASH
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_USER_API_SKCIPHER
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_ECB
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_MD5
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_CBC
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_SHA256
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_AES
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_DES
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_CMAC
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_HMAC
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_SHA512
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_SHA1
Sep 30 19:30:00 narayana.search iwd[615]: The following optimized implementations might be available:
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_SHA1_SSSE3
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_AES_NI_INTEL
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_SHA512_SSSE3
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_AES_X86_64
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_DES3_EDE_X86_64
Sep 30 19:30:00 narayana.search iwd[615]:         CONFIG_CRYPTO_SHA256_SSSE3
Sep 30 19:30:00 narayana.search systemd[1]: iwd.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit iwd.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Sep 30 19:30:00 narayana.search systemd[1]: iwd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit iwd.service has entered the 'failed' state with result 'exit-code'.
Sep 30 19:30:00 narayana.search systemd[1]: Failed to start Wireless service.
░░ Subject: A start job for unit iwd.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit iwd.service has finished with a failure.
░░
░░ The job identifier is 861 and the job result is failed.
Sep 30 19:30:00 narayana.search systemd[1]: iwd.service: Scheduled restart job, restart counter is at 4.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit iwd.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Sep 30 19:30:00 narayana.search systemd[1]: Starting Wireless service...
░░ Subject: A start job for unit iwd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit iwd.service has begun execution.

I have tried tips for

Verbose TLS debugging

This can be useful, if you have trouble setting up MSCHAPv2 or TTLS. You can set the following environment variable via a drop-in snippet:

/etc/systemd/system/iwd.service.d/tls-debug.conf [Service] Environment=IWD_TLS_DEBUG=TRUE Check the iwd logs afterwards by running journalctl -u iwd.service as root.

[Service] ExecStartPre=ip link set wlan0 up Wireless device is not renamed by udev Since version 1.0, iwd disables network interface renaming to predictable network interface names. It installs the following systemd.link(5) configuration file which prevents udev from renaming the interface to a predictable, stable name (e.g. wlp#s#):

but the problem is persist.

as the error yield about cryptographic support, I install a package from (crypto)[https://archlinux.org/packages/extra/x86_64/crypto++/] manually. but it do not solve the problem.

i try boot with old kernel i found:

lspci: Unable to load libkmod resources: error -2

As Mr Tom Yan asked :

Installed kernel is linux 6.15.9.arch1-1, uname -r gives 6.15.3-arch1-1 .

It seems that there are logs but you didn't paste most of them. What is shown above the "CONFIG_CRYPTO_AES_NI_INTEL" line? — grawity
– grawity, Commented Sep 29 at 8:39
It's turned out already asked on Arch forum but not yet has an answered. But i am pretty sure I already reboot after kernel upgrade. bbs.archlinux.org/viewtopic.php?id=282026 — Adi Prasetyo
– Adi Prasetyo, Commented Sep 30 at 23:37
Have you checked pacman -Q linux (or the kernel variant you use) vs uname -r? — Tom Yan
– Tom Yan, Commented Oct 1 at 10:32
Yeah, it has a mismatch; perhaps it was caused by a previous problem when trying to mount ntfs partition. — Adi Prasetyo
– Adi Prasetyo, Commented Oct 1 at 15:53

Adi Prasetyo · Accepted Answer · 2025-11-16 19:51:22Z

1

Start the network manager service bro:

sudo systemctl start NetworkManager

answered Nov 16 at 19:51

Adi Prasetyo

1711 silver badge12 bronze badges

Add a comment |

Stack Exchange Network

Troubleshooting iwctl / networking , unable to start on arch linux (wlan)

Verbose TLS debugging

i try boot with old kernel i found:

As Mr Tom Yan asked :

1 Answer 1

You must log in to answer this question.

Linked

Hot Network Questions

Troubleshooting iwctl / networking , unable to start on arch linux (wlan)

Verbose TLS debugging

i try boot with old kernel i found:

As Mr Tom Yan asked :

1 Answer 1

You must log in to answer this question.

Linked

Related

Hot Network Questions