From: Bruno Dantas <dantas@airpost.net>
To: iwd@lists.linux.dev
Subject: iwd release 1.30 onwards cannot find available networks
Date: Mon, 12 Dec 2022 11:54:31 -0500 [thread overview]
Message-ID: <b7ff5956-f571-d9d8-1f7b-f3025e2055ae@airpost.net> (raw)
I was a happy iwd user through release 1.29. From 1.30 onwards (including the latest version 2.0) I had to switch to wpa_supplicant because in most (but, strangely, not all) locations where I go, iwd fails to find any available networks ("sudo iwctl station wlan0 get-networks" says "No networks available").
Today I finally got around to doing a git bisect to pinpoint the regression. The bisect concluded with this:
dfcba7c83c60f1a99ecf6f1424e97bf89fcab38e is the first bad commit
commit dfcba7c83c60f1a99ecf6f1424e97bf89fcab38e
Author: James Prestwood <prestwoj@gmail.com>
Date: Thu Aug 4 11:51:06 2022 -0700
wiphy: track GET_REG ID
Keep track of the GET_REG call so it can be canceled if the wiphy
goes down.
src/wiphy.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
In case it's helpful, my machine is an X230 ThinkPad with coreboot, linux kernel version 5.15.10, running Tiny Core Linux 13.1 x86_64. My wireless card is Intel Dual Band Wireless-AC 7265. If you guys need any more information, I'd love to help.
Please fix this regression if possible. I'd love to go back to using iwd in the future.
Happy hacking!
Bruno "GNUser" Dantas
next reply other threads:[~2022-12-12 16:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 16:54 Bruno Dantas [this message]
2022-12-12 17:22 ` iwd release 1.30 onwards cannot find available networks James Prestwood
2022-12-12 17:52 ` Bruno Dantas
2022-12-12 18:39 ` Paul Menzel
2022-12-12 18:58 ` Bruno Dantas
2022-12-12 19:01 ` Denis Kenzior
2022-12-12 19:27 ` Bruno Dantas
2022-12-12 19:38 ` Alvin Šipraga
2022-12-12 20:07 ` Bruno Dantas
2022-12-13 14:42 ` Bruno Dantas
2022-12-13 17:23 ` James Prestwood
2022-12-13 20:15 ` Bruno Dantas
2022-12-13 20:33 ` James Prestwood
2022-12-13 21:02 ` Bruno Dantas
2022-12-12 22:00 ` Denis Kenzior
2022-12-12 23:31 ` Bruno Dantas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b7ff5956-f571-d9d8-1f7b-f3025e2055ae@airpost.net \
--to=dantas@airpost.net \
--cc=iwd@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).