From: James Prestwood <prestwoj@gmail.com>
To: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>,
Denis Kenzior <denkenz@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: iwd 2.22 scan fails but... works ok with ConnMan
Date: Thu, 24 Oct 2024 09:51:35 -0700 [thread overview]
Message-ID: <ec368cb3-325e-4df5-aeaa-f84dc0641da6@gmail.com> (raw)
In-Reply-To: <A112F6DF-E1BE-4350-86DD-7A85BA4FC1CA@gmail.com>
Hi Piotr,
On 10/24/24 7:32 AM, Piotr Oniszczuk wrote:
> Pls see inline
>
>> Wiadomość napisana przez Denis Kenzior <denkenz@gmail.com> w dniu 24.10.2024, o godz. 16:00:
>>
>> Hi Piotr,
>>
>>>> What hardware is being used?
>>> this is allwinner h618 zero3 sbc with uwe5622 wifi chip.
>>> Kernel is 6.11.5 with uwe5622 driver backported from vendor bsp (https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.11/files/0630-net-wireless-add-uwe5622-support-v20231020.patch)
>> So yet another non-upstream driver, sigh.
> Ah - believe me: mine frustration because of this is much bigger :-p
>
>>>> Can you include iwmon output?
> After compiling nlmon now is much better: https://gist.github.com/warpme/4b21b51dd1e2c74075498acd9af5082d
>
>> Is this in any way related to the problem reported in this thread?
>> https://lore.kernel.org/all/CAOCHtYj9OjZGQ=G139i=KRRcxpFD-1=GSvUPmFYaqSvFz0NwJg@mail.gmail.com/
>>
> Indeed I saw this thread.
> Some time ago I was trying to play with iwd.cfg without success
> Maybe I put incorrect settings there?
>
> May you hint me what exactly I need to add in iwd.cfg?
>
> To load wifi kernel module I’m using: modprobe sprdwl_ng
>
> Btw: all was working ok few versions back of iwd/kernel
> Unfortunately I can’t say which change: iwd or kernel breaks iwd operation on uwe5622 wifi….
>
>
Thank you for the iwmon logs, that really helped diagnose the issue.
There are a few patches on the list that I just sent which will
hopefully fix your problem. We identified a few separate issues:
- Incorrect starting frequency for operating class 136
- No check for the correct band when checking the e4 table
- No check for the correct band when parsing the advertised
frequencies from the kernel/driver
Your hardware seems to be advertising some frequencies [1] which are
not exactly common and this threw IWD for a loop and exposed several
bugs. These fixes will basically disallow those frequencies, but we need
to take a closer look at them to be able to parse them correctly.
[1] https://en.wikipedia.org/wiki/List_of_WLAN_channels#5.9_GHz_(802.11p)
Thanks,
James
next prev parent reply other threads:[~2024-10-24 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 8:56 iwd 2.22 scan fails but... works ok with ConnMan Piotr Oniszczuk
2024-10-23 22:04 ` Denis Kenzior
2024-10-24 10:04 ` Piotr Oniszczuk
2024-10-24 14:00 ` Denis Kenzior
2024-10-24 14:32 ` Piotr Oniszczuk
2024-10-24 16:51 ` James Prestwood [this message]
2024-10-24 18:37 ` Piotr Oniszczuk
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=ec368cb3-325e-4df5-aeaa-f84dc0641da6@gmail.com \
--to=prestwoj@gmail.com \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=piotr.oniszczuk@gmail.com \
/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