* Re: iwd fails to create device
@ 2022-05-31 18:39 1148d778-20a8-4ab0-96b7-24572ddab965
0 siblings, 0 replies; 7+ messages in thread
From: 1148d778-20a8-4ab0-96b7-24572ddab965 @ 2022-05-31 18:39 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
> It would be great if you could get some iwmon logs when this happens.
> Hopefully it happens frequent enough you can get a capture. More info
> about how to do that can be found here:
>
> https://iwd.wiki.kernel.org/debugging
Sure, but it doesn't happen very frequently. I'm not sure about how to approach debugging for this, should I try to restart iwd when it happens? Maybe doing this the issue is not triggered. Having iwmon logging all time seems a bit too much, no?
I could try to reproduce it somehow because it's mostly after a reboot when it happens.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: iwd fails to create device
2023-01-17 18:30 ` James Prestwood
@ 2023-01-17 20:23 ` Kevin Boulain
0 siblings, 0 replies; 7+ messages in thread
From: Kevin Boulain @ 2023-01-17 20:23 UTC (permalink / raw)
To: James Prestwood; +Cc: iwd
Hey James,
On 2023-01-17 at 10:30 -08, James Prestwood <prestwoj@gmail.com> wrote:
> Would you be able to try the last two patches on the list? The archive
> link is:
>
> https://lore.kernel.org/iwd/20230117180343.1451626-1-prestwoj@gmail.com/T/#t
I'd say the results are pretty conclusive:
- without the patches the issue appeared in 3 boots of 5,
- with the patches I didn't encounter the issue after 10 boots.
Thanks!
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: iwd fails to create device
2023-01-15 15:53 ` Kevin Boulain
@ 2023-01-17 18:30 ` James Prestwood
2023-01-17 20:23 ` Kevin Boulain
0 siblings, 1 reply; 7+ messages in thread
From: James Prestwood @ 2023-01-17 18:30 UTC (permalink / raw)
To: Kevin Boulain, iwd
Hi Kevin,
On Sun, 2023-01-15 at 16:53 +0100, Kevin Boulain wrote:
> > This looks very familiar to an issue we fixed with dual-phy cards,
> > but
> > this isn't the case for you. Its as if your phy is being detected
> > twice.
>
> It doesn't look like the OP has followed up on this but it seems I have
> a very similar issue. It appears that when iwd (2.0) starts and the
> kernel (6.1.3) reports Bluetooth/iwlwifi stuff right after it, iwd will
> see the same interface twice and my wlan0 interface won't come up.
> Restarting iwd fixes the issue.
Would you be able to try the last two patches on the list? The archive
link is:
https://lore.kernel.org/iwd/20230117180343.1451626-1-prestwoj@gmail.com/T/#t
Hopefully this fixes the problem.
Thanks,
James
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: iwd fails to create device
2022-05-31 20:17 James Prestwood
@ 2023-01-15 15:53 ` Kevin Boulain
2023-01-17 18:30 ` James Prestwood
0 siblings, 1 reply; 7+ messages in thread
From: Kevin Boulain @ 2023-01-15 15:53 UTC (permalink / raw)
To: iwd
> This looks very familiar to an issue we fixed with dual-phy cards, but
> this isn't the case for you. Its as if your phy is being detected
> twice.
It doesn't look like the OP has followed up on this but it seems I have
a very similar issue. It appears that when iwd (2.0) starts and the
kernel (6.1.3) reports Bluetooth/iwlwifi stuff right after it, iwd will
see the same interface twice and my wlan0 interface won't come up.
Restarting iwd fixes the issue.
> More info about how to do that can be found here:
> https://iwd.wiki.kernel.org/debugging
> Maybe someone else has a better solution, but you could create a bash
> script (e.g. /usr/libexec/start-iwd.sh):
I'm not sure it will help because iwmon's capture appears to start a bit
too late (but that's the first time I try to debug something like this).
Journal entries are from the first to last iwd log and I anonymized all
the logs as described in the wiki but I can resend the complete files in
private.
Logs manifesting the issue:
journalctl https://pastebin.com/z7iCvYAP
iwmon https://pastebin.com/Va4XEEDs
And for comparison, when everything goes fine:
journalctl https://pastebin.com/DJAHgZYE
iwmon https://pastebin.com/iRHF9Wd8
I'm happy to try with the latest iwd commit or another kernel version if
it would help. It only takes a few reboots for the issue to happen.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: iwd fails to create device
@ 2022-05-31 20:17 James Prestwood
2023-01-15 15:53 ` Kevin Boulain
0 siblings, 1 reply; 7+ messages in thread
From: James Prestwood @ 2022-05-31 20:17 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
On Tue, 2022-05-31 at 18:39 +0000,
1148d778-20a8-4ab0-96b7-24572ddab965(a)simplelogin.co wrote:
> > It would be great if you could get some iwmon logs when this
> > happens.
> > Hopefully it happens frequent enough you can get a capture. More
> > info
> > about how to do that can be found here:
> >
> > https://iwd.wiki.kernel.org/debugging
>
> Sure, but it doesn't happen very frequently. I'm not sure about how
> to approach debugging for this, should I try to restart iwd when it
> happens? Maybe doing this the issue is not triggered. Having iwmon
> logging all time seems a bit too much, no?
It sounds like some kind of race condition in the kernel, which is why
its infrequent. And yes, running iwmon all the time is going to produce
a huge log...
Maybe someone else has a better solution, but you could create a bash
script (e.g. /usr/libexec/start-iwd.sh):
#!/bin/bash
timeout 60s iwmon --nortnl --noscan > /your/log/file &
iwd -d
And have your systemd unit file run this:
ExecStart=/usr/libexec/start-iwd.sh
Since this happens at startup running iwmon for 60 seconds should be
plenty to capture the wiphy dump. This of course assumes you're using
systemd.
Note: DO NOT use the --nowiphy. This disables the messages we need to
look at.
Thanks,
James
>
> I could try to reproduce it somehow because it's mostly after a
> reboot when it happens.
> _______________________________________________
> iwd mailing list -- iwd(a)lists.01.org
> To unsubscribe send an email to iwd-leave(a)lists.01.org
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: iwd fails to create device
@ 2022-05-31 16:06 James Prestwood
0 siblings, 0 replies; 7+ messages in thread
From: James Prestwood @ 2022-05-31 16:06 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 11367 bytes --]
Hi,
On Sat, 2022-05-28 at 19:24 +0000,
1148d778-20a8-4ab0-96b7-24572ddab965(a)simplelogin.co wrote:
> Hi,
>
> A few times I've already seen a strange behaviour right after
> rebooting. All of the sudden the wifi card is no longer available. To
> me it looks like iwd fails to detect and rename the device. Hopefully
> it happens very seldom.
>
> $ journalctl -b -1 | grep -i wifi
> may 27 12:02:52 kernel: Intel(R) Wireless WiFi driver for Linux
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: enabling device (0000 ->
> 0002)
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: Direct firmware load for
> iwlwifi-cc-a0-69.ucode failed with error -2
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: api flags index 2 larger
> than supported by driver
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ
> Version: 89.3.35.37
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: loaded firmware version
> 68.01d30b0c.0 cc-a0-68.ucode op_mode iwlmvm
> may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6
> AX200 160MHz, REV=0x340
> may 27 12:02:53 kernel: iwlwifi 0000:03:00.0: Detected RF HR B3,
> rfid=0x10a100
> may 27 12:02:53 kernel: iwlwifi 0000:03:00.0: base HW address:
> xx:xx:xx:xx:xx:xx
>
>
> $ journalctl -b -1 | grep -i iwd
> may 27 12:02:53 iwd[863]: Wireless daemon version 1.27
> may 27 12:02:53 iwd[863]: Loaded configuration from /etc/iwd/main.conf
> may 27 12:02:53 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
> ses=4294967295 msg='unit=iwd comm="systemd"
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
> res=success'
> may 27 12:02:53 iwd[863]: Wiphy: 0, Name: phy0
> may 27 12:02:53 iwd[863]: Permanent Address: xx:xx:xx:xx:xx:xx
> may 27 12:02:53 iwd[863]: 2.4Ghz Band:
> may 27 12:02:53 iwd[863]: Bitrates (non-HT):
> may 27 12:02:53 iwd[863]: 1.0 Mbps
> may 27 12:02:53 iwd[863]: 2.0 Mbps
> may 27 12:02:53 iwd[863]: 5.5 Mbps
> may 27 12:02:53 iwd[863]: 11.0 Mbps
> may 27 12:02:53 iwd[863]: 6.0 Mbps
> may 27 12:02:53 iwd[863]: 9.0 Mbps
> may 27 12:02:53 iwd[863]: 12.0 Mbps
> may 27 12:02:53 iwd[863]: 18.0 Mbps
> may 27 12:02:53 iwd[863]: 24.0 Mbps
> may 27 12:02:53 iwd[863]: 36.0 Mbps
> may 27 12:02:53 iwd[863]: 48.0 Mbps
> may 27 12:02:53 iwd[863]: 54.0 Mbps
> may 27 12:02:53 iwd[863]: HT Capabilities:
> may 27 12:02:53 iwd[863]: HT40
> may 27 12:02:53 iwd[863]: Short GI for 20Mhz
> may 27 12:02:53 iwd[863]: Short GI for 40Mhz
> may 27 12:02:53 iwd[863]: HT RX MCS indexes:
> may 27 12:02:53 iwd[863]: 0-15
> may 27 12:02:53 iwd[863]: 5Ghz Band:
> may 27 12:02:53 iwd[863]: Bitrates (non-HT):
> may 27 12:02:53 iwd[863]: 6.0 Mbps
> may 27 12:02:53 iwd[863]: 9.0 Mbps
> may 27 12:02:53 iwd[863]: 12.0 Mbps
> may 27 12:02:53 iwd[863]: 18.0 Mbps
> may 27 12:02:53 iwd[863]: 24.0 Mbps
> may 27 12:02:53 iwd[863]: 36.0 Mbps
> may 27 12:02:53 iwd[863]: 48.0 Mbps
> may 27 12:02:53 iwd[863]: 54.0 Mbps
> may 27 12:02:53 iwd[863]: HT Capabilities:
> may 27 12:02:53 iwd[863]: HT40
> may 27 12:02:53 iwd[863]: Short GI for 20Mhz
> may 27 12:02:53 iwd[863]: Short GI for 40Mhz
> may 27 12:02:53 iwd[863]: HT RX MCS indexes:
> may 27 12:02:53 iwd[863]: 0-15
> may 27 12:02:53 iwd[863]: VHT Capabilities:
> may 27 12:02:53 iwd[863]: 160 Mhz operation
> may 27 12:02:53 iwd[863]: Short GI for 80Mhz
> may 27 12:02:53 iwd[863]: Short GI for 160 and
> 80 + 80 Mhz
> may 27 12:02:53 iwd[863]: Max RX MCS: 0-9 for
> NSS: 2
> may 27 12:02:53 iwd[863]: Max TX MCS: 0-9 for
> NSS: 2
> may 27 12:02:53 iwd[863]: Ciphers: CCMP TKIP BIP
> may 27 12:02:53 iwd[863]: Supported iftypes: ad-hoc station ap
> p2p-client p2p-go p2p-device
> may 27 12:02:53 iwd[863]: Unable to add the net.connman.iwd.Adapter
> interface to /net/connman/iwd/0
> may 27 12:02:53 iwd[863]: Unable to add the
> org.freedesktop.DBus.Properties interface to /net/connman/iwd/0
> may 27 12:02:53 iwd[863]: Wiphy: 0, Name: phy0
> may 27 12:02:53 iwd[863]: Permanent Address: xx:xx:xx:xx:xx:xx
> may 27 12:02:53 iwd[863]: 2.4Ghz Band:
> may 27 12:02:53 iwd[863]: Bitrates (non-HT):
> may 27 12:02:53 iwd[863]: 1.0 Mbps
> may 27 12:02:53 iwd[863]: 2.0 Mbps
> may 27 12:02:53 iwd[863]: 5.5 Mbps
> may 27 12:02:53 iwd[863]: 11.0 Mbps
> may 27 12:02:53 iwd[863]: 6.0 Mbps
> may 27 12:02:53 iwd[863]: 9.0 Mbps
> may 27 12:02:53 iwd[863]: 12.0 Mbps
> may 27 12:02:53 iwd[863]: 18.0 Mbps
> may 27 12:02:53 iwd[863]: 24.0 Mbps
> may 27 12:02:53 iwd[863]: 36.0 Mbps
> may 27 12:02:53 iwd[863]: 48.0 Mbps
> may 27 12:02:53 iwd[863]: 54.0 Mbps
> may 27 12:02:53 iwd[863]: HT Capabilities:
> may 27 12:02:53 iwd[863]: HT40
> may 27 12:02:53 iwd[863]: Short GI for 20Mhz
> may 27 12:02:53 iwd[863]: Short GI for 40Mhz
> may 27 12:02:53 iwd[863]: HT RX MCS indexes:
> may 27 12:02:53 iwd[863]: 0-15
> may 27 12:02:53 iwd[863]: 5Ghz Band:
> may 27 12:02:53 iwd[863]: Bitrates (non-HT):
> may 27 12:02:53 iwd[863]: 6.0 Mbps
> may 27 12:02:53 iwd[863]: 9.0 Mbps
> may 27 12:02:53 iwd[863]: 12.0 Mbps
> may 27 12:02:53 iwd[863]: 18.0 Mbps
> may 27 12:02:53 iwd[863]: 24.0 Mbps
> may 27 12:02:53 iwd[863]: 36.0 Mbps
> may 27 12:02:53 iwd[863]: 48.0 Mbps
> may 27 12:02:53 iwd[863]: 54.0 Mbps
> may 27 12:02:53 iwd[863]: HT Capabilities:
> may 27 12:02:53 iwd[863]: HT40
> may 27 12:02:53 iwd[863]: Short GI for 20Mhz
> may 27 12:02:53 iwd[863]: Short GI for 40Mhz
> may 27 12:02:53 iwd[863]: HT RX MCS indexes:
> may 27 12:02:53 iwd[863]: 0-15
> may 27 12:02:53 iwd[863]: VHT Capabilities:
> may 27 12:02:53 iwd[863]: 160 Mhz operation
> may 27 12:02:53 iwd[863]: Short GI for 80Mhz
> may 27 12:02:53 iwd[863]: Short GI for 160 and
> 80 + 80 Mhz
> may 27 12:02:53 iwd[863]: Max RX MCS: 0-9 for
> NSS: 2
> may 27 12:02:53 iwd[863]: Max TX MCS: 0-9 for
> NSS: 2
> may 27 12:02:53 iwd[863]: Ciphers: CCMP TKIP BIP
> may 27 12:02:53 iwd[863]: Supported iftypes: ad-hoc station ap
> p2p-client p2p-go p2p-device
> may 27 12:02:53 iwd[863]: DEL_INTERFACE failed: No such device
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:02:53 iwd[863]: RTM_GETLINK error -19: No such device
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
> may 27 12:03:31 iwd[863]: D-Bus disconnected, quitting...
> may 27 12:03:32 iwd[863]: Terminate
> may 27 12:03:32 iwd[863]: Removing scan context for wdev 2
> may 27 12:03:33 systemd[1]: iwd.service: Deactivated successfully.
This looks very familiar to an issue we fixed with dual-phy cards, but
this isn't the case for you. Its as if your phy is being detected
twice.
It would be great if you could get some iwmon logs when this happens.
Hopefully it happens frequent enough you can get a capture. More info
about how to do that can be found here:
https://iwd.wiki.kernel.org/debugging
>
> Arch Linux wiki on iwd troubleshooting mentions two issues that look
> possible causes to me:
> - Low entropy pool
> - Wireless device not renamed by udev
>
> You can check it here:
> https://wiki.archlinux.org/title/Iwd#Troubleshooting
>
> Any help to fix this issue would be appreciated.
>
> Thanks!
> _______________________________________________
> iwd mailing list -- iwd(a)lists.01.org
> To unsubscribe send an email to iwd-leave(a)lists.01.org
^ permalink raw reply [flat|nested] 7+ messages in thread
* iwd fails to create device
@ 2022-05-28 19:24 1148d778-20a8-4ab0-96b7-24572ddab965
0 siblings, 0 replies; 7+ messages in thread
From: 1148d778-20a8-4ab0-96b7-24572ddab965 @ 2022-05-28 19:24 UTC (permalink / raw)
To: iwd
[-- Attachment #1: Type: text/plain, Size: 8478 bytes --]
Hi,
A few times I've already seen a strange behaviour right after rebooting. All of the sudden the wifi card is no longer available. To me it looks like iwd fails to detect and rename the device. Hopefully it happens very seldom.
$ journalctl -b -1 | grep -i wifi
may 27 12:02:52 kernel: Intel(R) Wireless WiFi driver for Linux
may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-69.ucode failed with error -2
may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver
may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: loaded firmware version 68.01d30b0c.0 cc-a0-68.ucode op_mode iwlmvm
may 27 12:02:52 kernel: iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
may 27 12:02:53 kernel: iwlwifi 0000:03:00.0: Detected RF HR B3, rfid=0x10a100
may 27 12:02:53 kernel: iwlwifi 0000:03:00.0: base HW address: xx:xx:xx:xx:xx:xx
$ journalctl -b -1 | grep -i iwd
may 27 12:02:53 iwd[863]: Wireless daemon version 1.27
may 27 12:02:53 iwd[863]: Loaded configuration from /etc/iwd/main.conf
may 27 12:02:53 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
may 27 12:02:53 iwd[863]: Wiphy: 0, Name: phy0
may 27 12:02:53 iwd[863]: Permanent Address: xx:xx:xx:xx:xx:xx
may 27 12:02:53 iwd[863]: 2.4Ghz Band:
may 27 12:02:53 iwd[863]: Bitrates (non-HT):
may 27 12:02:53 iwd[863]: 1.0 Mbps
may 27 12:02:53 iwd[863]: 2.0 Mbps
may 27 12:02:53 iwd[863]: 5.5 Mbps
may 27 12:02:53 iwd[863]: 11.0 Mbps
may 27 12:02:53 iwd[863]: 6.0 Mbps
may 27 12:02:53 iwd[863]: 9.0 Mbps
may 27 12:02:53 iwd[863]: 12.0 Mbps
may 27 12:02:53 iwd[863]: 18.0 Mbps
may 27 12:02:53 iwd[863]: 24.0 Mbps
may 27 12:02:53 iwd[863]: 36.0 Mbps
may 27 12:02:53 iwd[863]: 48.0 Mbps
may 27 12:02:53 iwd[863]: 54.0 Mbps
may 27 12:02:53 iwd[863]: HT Capabilities:
may 27 12:02:53 iwd[863]: HT40
may 27 12:02:53 iwd[863]: Short GI for 20Mhz
may 27 12:02:53 iwd[863]: Short GI for 40Mhz
may 27 12:02:53 iwd[863]: HT RX MCS indexes:
may 27 12:02:53 iwd[863]: 0-15
may 27 12:02:53 iwd[863]: 5Ghz Band:
may 27 12:02:53 iwd[863]: Bitrates (non-HT):
may 27 12:02:53 iwd[863]: 6.0 Mbps
may 27 12:02:53 iwd[863]: 9.0 Mbps
may 27 12:02:53 iwd[863]: 12.0 Mbps
may 27 12:02:53 iwd[863]: 18.0 Mbps
may 27 12:02:53 iwd[863]: 24.0 Mbps
may 27 12:02:53 iwd[863]: 36.0 Mbps
may 27 12:02:53 iwd[863]: 48.0 Mbps
may 27 12:02:53 iwd[863]: 54.0 Mbps
may 27 12:02:53 iwd[863]: HT Capabilities:
may 27 12:02:53 iwd[863]: HT40
may 27 12:02:53 iwd[863]: Short GI for 20Mhz
may 27 12:02:53 iwd[863]: Short GI for 40Mhz
may 27 12:02:53 iwd[863]: HT RX MCS indexes:
may 27 12:02:53 iwd[863]: 0-15
may 27 12:02:53 iwd[863]: VHT Capabilities:
may 27 12:02:53 iwd[863]: 160 Mhz operation
may 27 12:02:53 iwd[863]: Short GI for 80Mhz
may 27 12:02:53 iwd[863]: Short GI for 160 and 80 + 80 Mhz
may 27 12:02:53 iwd[863]: Max RX MCS: 0-9 for NSS: 2
may 27 12:02:53 iwd[863]: Max TX MCS: 0-9 for NSS: 2
may 27 12:02:53 iwd[863]: Ciphers: CCMP TKIP BIP
may 27 12:02:53 iwd[863]: Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
may 27 12:02:53 iwd[863]: Unable to add the net.connman.iwd.Adapter interface to /net/connman/iwd/0
may 27 12:02:53 iwd[863]: Unable to add the org.freedesktop.DBus.Properties interface to /net/connman/iwd/0
may 27 12:02:53 iwd[863]: Wiphy: 0, Name: phy0
may 27 12:02:53 iwd[863]: Permanent Address: xx:xx:xx:xx:xx:xx
may 27 12:02:53 iwd[863]: 2.4Ghz Band:
may 27 12:02:53 iwd[863]: Bitrates (non-HT):
may 27 12:02:53 iwd[863]: 1.0 Mbps
may 27 12:02:53 iwd[863]: 2.0 Mbps
may 27 12:02:53 iwd[863]: 5.5 Mbps
may 27 12:02:53 iwd[863]: 11.0 Mbps
may 27 12:02:53 iwd[863]: 6.0 Mbps
may 27 12:02:53 iwd[863]: 9.0 Mbps
may 27 12:02:53 iwd[863]: 12.0 Mbps
may 27 12:02:53 iwd[863]: 18.0 Mbps
may 27 12:02:53 iwd[863]: 24.0 Mbps
may 27 12:02:53 iwd[863]: 36.0 Mbps
may 27 12:02:53 iwd[863]: 48.0 Mbps
may 27 12:02:53 iwd[863]: 54.0 Mbps
may 27 12:02:53 iwd[863]: HT Capabilities:
may 27 12:02:53 iwd[863]: HT40
may 27 12:02:53 iwd[863]: Short GI for 20Mhz
may 27 12:02:53 iwd[863]: Short GI for 40Mhz
may 27 12:02:53 iwd[863]: HT RX MCS indexes:
may 27 12:02:53 iwd[863]: 0-15
may 27 12:02:53 iwd[863]: 5Ghz Band:
may 27 12:02:53 iwd[863]: Bitrates (non-HT):
may 27 12:02:53 iwd[863]: 6.0 Mbps
may 27 12:02:53 iwd[863]: 9.0 Mbps
may 27 12:02:53 iwd[863]: 12.0 Mbps
may 27 12:02:53 iwd[863]: 18.0 Mbps
may 27 12:02:53 iwd[863]: 24.0 Mbps
may 27 12:02:53 iwd[863]: 36.0 Mbps
may 27 12:02:53 iwd[863]: 48.0 Mbps
may 27 12:02:53 iwd[863]: 54.0 Mbps
may 27 12:02:53 iwd[863]: HT Capabilities:
may 27 12:02:53 iwd[863]: HT40
may 27 12:02:53 iwd[863]: Short GI for 20Mhz
may 27 12:02:53 iwd[863]: Short GI for 40Mhz
may 27 12:02:53 iwd[863]: HT RX MCS indexes:
may 27 12:02:53 iwd[863]: 0-15
may 27 12:02:53 iwd[863]: VHT Capabilities:
may 27 12:02:53 iwd[863]: 160 Mhz operation
may 27 12:02:53 iwd[863]: Short GI for 80Mhz
may 27 12:02:53 iwd[863]: Short GI for 160 and 80 + 80 Mhz
may 27 12:02:53 iwd[863]: Max RX MCS: 0-9 for NSS: 2
may 27 12:02:53 iwd[863]: Max TX MCS: 0-9 for NSS: 2
may 27 12:02:53 iwd[863]: Ciphers: CCMP TKIP BIP
may 27 12:02:53 iwd[863]: Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
may 27 12:02:53 iwd[863]: DEL_INTERFACE failed: No such device
may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
may 27 12:02:53 iwd[863]: RTM_GETLINK error -19: No such device
may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
may 27 12:02:53 iwd[863]: Could not register frame watch type 00d0: -19
may 27 12:03:31 iwd[863]: D-Bus disconnected, quitting...
may 27 12:03:32 iwd[863]: Terminate
may 27 12:03:32 iwd[863]: Removing scan context for wdev 2
may 27 12:03:33 systemd[1]: iwd.service: Deactivated successfully.
Arch Linux wiki on iwd troubleshooting mentions two issues that look possible causes to me:
- Low entropy pool
- Wireless device not renamed by udev
You can check it here: https://wiki.archlinux.org/title/Iwd#Troubleshooting
Any help to fix this issue would be appreciated.
Thanks!
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2023-01-17 20:23 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-31 18:39 iwd fails to create device 1148d778-20a8-4ab0-96b7-24572ddab965
-- strict thread matches above, loose matches on Subject: below --
2022-05-31 20:17 James Prestwood
2023-01-15 15:53 ` Kevin Boulain
2023-01-17 18:30 ` James Prestwood
2023-01-17 20:23 ` Kevin Boulain
2022-05-31 16:06 James Prestwood
2022-05-28 19:24 1148d778-20a8-4ab0-96b7-24572ddab965
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.