From: Joao Marcos Costa <joaomarcos.costa@bootlin.com>
To: iwd@lists.linux.dev
Cc: gregory.clement@bootlin.com, prestwoj@gmail.com,
Salahaldeen.Altous@leica-camera.com
Subject: Iwd: unable to start AP with NXP 88W9098 chipset
Date: Thu, 21 Dec 2023 16:46:43 +0100 [thread overview]
Message-ID: <6c9b05a2-7474-4eed-bb74-6f5de1d433ba@bootlin.com> (raw)
Hello,
I hope this email finds you well.
I'm currently facing what seems to be the very same bug reported at
https://lore.kernel.org/iwd/AM7PR01MB67244F63EBEAB9A65D965BEAADC69@AM7PR01MB6724.eurprd01.prod.exchangelabs.com/
As for my own context, I'm using:
- Ublox wifi module Jody-W377-00A
- IWD v1.26 (from meta-openembedded)
- Linux v6.1.68 (x86_64)
- NXP Wi-Fi driver for NXP 88W9098 chipset, from
github.com/nxp-imx/mwifiex (branch=lf-6.1.55_2.2.0)
I followed the steps in https://iwd.wiki.kernel.org/ap_mode, and this is
the error I get in my iwctl console:
# iwctl
NetworkConfigurationEnabled: enabled
StateDirectory: /var/lib/iwd
Version: 1.26
[iwd]# device muap0 set-property Mode ap
[iwd]# device list
Devices *
--------------------------------------------------------------------------------
Name Address Powered Adapter Mode
--------------------------------------------------------------------------------
uap0 62:09:c3:80:9b:1d on mwiphy0 ap
mlan0 60:09:c3:80:9a:1d on mwiphy0 station
muap0 62:09:c3:80:9b:1e on mwiphy1 ap
mmlan0 60:09:c3:80:9a:1e on mwiphy1 station
[iwd]# ap list
Devices in Access Point
Mode *
--------------------------------------------------------------------------------
Name Started
--------------------------------------------------------------------------------
uap0 no
muap0 no
[iwd]# ap muap0 start-profile testap
[iwd]# [22444.663032] wlan: Starting AP
[22444.668197] fw doesn't support 11ax
[22444.674130] CMD_RESP: cmd 0xb1 error, result=0x1
[22444.679286] IOCTL failed: 00000000ae152881 id=0x20000, sub_id=0x20001
action=1, status_code=0x1
[22444.689145] woal_cfg80211_add_beacon: start uap failed
Operation failed
My /var/lib/iwd/ap/testap.ap file is identical to the one provided in
the Wiki, and as for my main.conf:
---
[General]
EnableNetworkConfiguration=true
UseDefaultInterface=true
[Network]
[Scan]
DisablePeriodicScan=true
---
I tried adding Country=FR and ControlPortOverNL80211=false, but without
any success.
I also added DisableHT=true in the testap.ap file later on, but the
result was the same.
However, I was able to start the Access Point using hostapd, and it
worked fine.
I can provide you with my hostapd.conf, if you find it pertinent.
Since referencing the original thread, are there any updates?
Has anyone else encountered a similar issue? Even if the chipset is not
precisely the same.
Please feel free to ask for logs or other unmentioned details, and thank
you for your assistance.
--
Best regards,
João Marcos Costa
next reply other threads:[~2023-12-21 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 15:46 Joao Marcos Costa [this message]
2023-12-21 16:08 ` Iwd: unable to start AP with NXP 88W9098 chipset James Prestwood
2023-12-22 15:36 ` Joao Marcos Costa
2024-01-19 14:28 ` Joao Marcos Costa
2024-01-19 17:44 ` James Prestwood
2024-01-24 10:18 ` Joao Marcos Costa
2024-01-24 12:29 ` James Prestwood
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=6c9b05a2-7474-4eed-bb74-6f5de1d433ba@bootlin.com \
--to=joaomarcos.costa@bootlin.com \
--cc=Salahaldeen.Altous@leica-camera.com \
--cc=gregory.clement@bootlin.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@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