FS#63912 - [iwd] Restart of iwd.service necessary after boot
Attached to Project:
Community Packages
Opened by Daniel Holz (holzi) - Tuesday, 24 September 2019, 19:56 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 30 April 2023, 07:58 GMT
Opened by Daniel Holz (holzi) - Tuesday, 24 September 2019, 19:56 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 30 April 2023, 07:58 GMT
|
Details
When I boot up my computer after logging in I have to
restart iwd.service or wifi won't work. After that it works
mostly fine.
Attached is the status of iwd.service before restarting it. 
iwd.txt
(1.2 KiB)
|
This task depends upon
Closed by Andreas Radke (AndyRTR)
Sunday, 30 April 2023, 07:58 GMT
Reason for closing: Upstream
Additional comments about closing: https://wiki.archlinux.org/title/Iwd#Res tarting_iwd.service_after_boot
Sunday, 30 April 2023, 07:58 GMT
Reason for closing: Upstream
Additional comments about closing: https://wiki.archlinux.org/title/Iwd#Res tarting_iwd.service_after_boot
did you guys try to report this on #iwd in freenode? I am using iwd as well and I don't have such issues.
Are you using plain IWD or IWD+Networkmanager/Connman?
This looks like a interface race for me, something is interfering with iwd's `wlan0` creation. Did you modify the `/etc/iwd/main.conf` file? or did you setup something else that is owning the wifi device? Maybe another wpa_supplicant running?
More information would be nice here. Is your wifi card in-build or USB? etc
The "iwd too fast" theory sounds plausible as the only working workaround I found is "ExecStartPre=sleep 4" mentioned by Parker. No other method mentioned on Arch Wiki works.
I'll report it upstream when I find a moment (and try digging up the root cause).
I've reported the issue upstream: https://lists.01.org/hyperkitty/list/iwd%40lists.01.org/thread/L5OXQ52CQCO2WAYUKOSZZHH6QR4UMQKB/
Otherwise:
Please provide iwmon logs, driver, kernel and hw details..
There are some logs I provided. And as you can read there, the issue seems already brought to freenode #iwd.
I'm too working around the problem by adding ExecStartPre=sleep 2. So guess it's kinda race condition.
Are you planning to make another release including the commit soon?
Then I'll wait and try when it's available through pacman.
Otherwise, I'll try it by modifying an existing AUR or building new one by myself.
Thanks.
please checkout the iwd-git version in the AUR: https://aur.archlinux.org/packages/iwd-git/
I've updated the PKGBUILD. It should build iwd with the same features as in community now. I hope it will fix your issues. I am running iwd-git right now, works fine for me.
I tried your AUR and the commit Andrew mentioned above doesn't seem to work.
I'm reverting back to the community package and sleep 2 workaround.
the iwd devs need more input. Can you upload the output of `lspci -k` for me?
denkenz (one of the iwd devs) mentioned in IRC that the bug is not yet fixed for ath10k and ath9k drivers/chipsets.. maybe you are affected.
Attached please find the output from `lspci -k`.
thanks for your pcis file.
Your file meets my expectations.. you are using an ath10k card for wifi.
The bug still exists for ath9k and ath10k. I hope the iwd devs are going to fix this asap.
Denis noticed, based on the logs posted in the forum thread (https://bbs.archlinux.org/viewtopic.php?id=251432) that we're hitting a kernel bug where the NEW_WIPHY event is not emitted because it's too big specifically when using the ath10k driver, so we need to work around it in iwd. Ironically Denis has previously proposed a kernel patch to fix this but it was never accepted.
can you please try the iwd-git version again? Denkenz, one of the iwd devs, just pushed a possible fix and he needs somebody who tries it.
Would be cool if you could give some feedback.
Tested iwd-git and WiFi works after boot without having to restart iwd.
Hope this version will be in the community repo soon.
Edit: Maybe I should mention that I have a Intel AX200 WiFi card.
isn't Intel AX200 using iwlwifi? everything should be fine with iwlwifi..
Can you upload your output of `lspci`?
05:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
I was running Arch Budgie with NetworkManager and wpa_supplicant and everything was fine.
Decided to reinstall Arch and test Gnome with NetworkManager and iwd. Configured NM to use iwd backend, started iwd and nm services, at first I thought that I didn't configure nm correctly, noticed that iwd didn't list any devices so I knew that something else was wrong but I didn't realize that the service didn't start at boot before I saw this bug report so I restarted the service and WiFi was working. With git version it works on every boot as expected.
I tried iwd-git and it works perfectly. I've removed the sleep 2 workaround and rebooted several times. AND there was no single failure in detecting my wireless LAN device.
Thank you and the team working on iwd for the efforts.
I'll stay with iwd-git for the time being until the community package is released with the relevant fix.
I will ask the iwd devs for a new release.
I'm using iwd as networkmanager backend.
Dmesg and journalctl in attachment.
```
03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
```
Can you modify the iwd service file like this?
systemctl edit iwd.service
[Service]
ExecStart=
ExecStart=/usr/lib/iwd/iwd -d
This will turn on debug mode for iwd. And we can see more logs.
did you guys checkout iwd-1.5? I have just pushed it yesterday to community, it should fix the problems for people with brcmfmac or atheros chipsets. (Maybe for newer Intel cards, too).
I moved back to the community version and it works fine as expected.
I don't think that my case was specific, I guess that more Intel cards were affected too.
ip a looks like this:
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 40:a3:cc:21:92:2e brd ff:ff:ff:ff:ff:ff
(UP, no IP address assigned)
In NetwotkManager there's no wifi device visible
I am not sure if we are talking about the same issue here right now.
I have in general the feeling that this bug report is a collection of different problems:
1. problems with atheros devices
2. problems with new intel wifi cards
3. problem with bfmac devices
4. other interface race conditions
@lesf0 can you please provide more logs like:
1. kernel version
2. lspci output
3. iwd with debugging flag (edit your iwd.service file like mentioned in this bug report)
4. iwd devs might need a wifi pcap trace via iwmon
How are you going with iwd? Did you try it with kernel 5.6.2 yet? does this fix your issues?
iwd is working fine, but not as expected and need to be restarted after boot
- iwd version: 1.19
- my summary: https://bbs.archlinux.org/viewtopic.php?id=271705
- is it make sense:
i have noticed different `Memory:` size for `iwd`
- system boot: Memory: 1.9M
- service restart: Memory: 552.0K
[1] https://wiki.archlinux.org/title/Iwd#Restarting_iwd.service_after_boot