wl18xx: iwd needs to be restarted before (a particular) AP appears

wl18xx: iwd needs to be restarted before (a particular) AP appears

[Donald]

Top of the morning,

I am seeing a quirk against wl18xx, where the first time iwd is
launched it fails to see certain APs and produces:

Received error during CMD_TRIGGER_SCAN: Invalid argument (22)

on relaunch of iwd, this CMD_TRIGGER_SCAN error does not manifest and
the AP in question is visible. Some APs are visible, but not the one
we happen to be interested in.

I see a bug from the distant past which alludes to this:

https://lore.kernel.org/all/f4d9e6cf-f7e4-49b9-adbf-92dbc006812a@gmail.com/T/#m6fd56354e1cdb32233adcce414bd8ff098c011da

and which demonstrates the same error message/symptoms. but adding:

[DriverQuirks]
DefaultInterface=wl18xx

to main.conf does not change the outcome.

I am running:

commit 7d5bcd738bb92cd33756985ffd2c4c67452a7f85 (tag: 3.6,
origin/master, origin/HEAD)
Author: Marcel Holtmann <marcel@holtmann.org>
Date:   Wed Apr 2 15:05:43 2025 +0200

    Release 3.6

against:

commit c5e32b0a3c19f6cf40241e323e02dff00810406e (tag: v6.13.5)
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date:   Thu Feb 27 04:34:22 2025 -0800

    Linux 6.13.5

The only solution I have found which consistently works is to run:

timeout 1 /usr/libexec/iwd &> /dev/null

exec /usr/libexec/iwd

in my systemd service, which consistently works.

It warrants mentioning that:

iwctl station wlan0 scan && iwctl station wlan0 get-networks

does not show the desired AP on first run of the restarted iwd daemon,
but when running this a second time I can see/connect.

So start iwd, restart iwd, scan, scan, get-networks - success

Yours sincerely,
Donald

-- 
-------------------------------
 °v°  Donald Carr
/(_)\ Chaos Reins
^ ^   http://chaos-reins.com/

Re: wl18xx: iwd needs to be restarted before (a particular) AP appears

[James Prestwood]

Hi Donald,

On 4/23/25 12:33 AM, Donald wrote:
> Top of the morning,
>
> I am seeing a quirk against wl18xx, where the first time iwd is
> launched it fails to see certain APs and produces:
>
> Received error during CMD_TRIGGER_SCAN: Invalid argument (22)
>
> on relaunch of iwd, this CMD_TRIGGER_SCAN error does not manifest and
> the AP in question is visible. Some APs are visible, but not the one
> we happen to be interested in.
>
> I see a bug from the distant past which alludes to this:
>
> https://lore.kernel.org/all/f4d9e6cf-f7e4-49b9-adbf-92dbc006812a@gmail.com/T/#m6fd56354e1cdb32233adcce414bd8ff098c011da
>
> and which demonstrates the same error message/symptoms. but adding:
>
> [DriverQuirks]
> DefaultInterface=wl18xx
>
> to main.conf does not change the outcome.
>
> I am running:
>
> commit 7d5bcd738bb92cd33756985ffd2c4c67452a7f85 (tag: 3.6,
> origin/master, origin/HEAD)
> Author: Marcel Holtmann <marcel@holtmann.org>
> Date:   Wed Apr 2 15:05:43 2025 +0200
>
>      Release 3.6
>
> against:
>
> commit c5e32b0a3c19f6cf40241e323e02dff00810406e (tag: v6.13.5)
> Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date:   Thu Feb 27 04:34:22 2025 -0800
>
>      Linux 6.13.5
>
> The only solution I have found which consistently works is to run:
>
> timeout 1 /usr/libexec/iwd &> /dev/null
>
> exec /usr/libexec/iwd
>
> in my systemd service, which consistently works.
>
> It warrants mentioning that:
>
> iwctl station wlan0 scan && iwctl station wlan0 get-networks
>
> does not show the desired AP on first run of the restarted iwd daemon,
> but when running this a second time I can see/connect.
>
> So start iwd, restart iwd, scan, scan, get-networks - success
>
> Yours sincerely,
> Donald

Do you see this behavior with wpa_supplicant? If not, could you do an 
iwmon capture of both wpa_supplicant working, and IWD not working. That 
would let me see potentially what field IWD is sending that the driver 
doesn't like (assuming wpa_supplicant does function as expected).

https://archive.kernel.org/oldwiki/iwd.wiki.kernel.org/debugging.html

(iwmon section)

Thanks,

James