From: Viacheslav <adeep@lexina.in>
To: Gabriel Tisan <gabriel.tisan@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: rtw88: rtl8822cs AP mode not working
Date: Mon, 6 May 2024 13:18:48 +0300 [thread overview]
Message-ID: <a30c323a-d09a-4ea3-952b-26adf909b069@lexina.in> (raw)
In-Reply-To: <CAD9ZU8DBn_pmkAX2JkBh2_HPe08pGRx6n+8i0TgKq3xXa2+2eQ@mail.gmail.com>
Seems that was github morrownr/8821cu-20210916 repo.
see
https://github.com/armbian/build/blob/2c0fef166f78962500fecfb6a2208550cc897fb5/lib/functions/compilation/patch/drivers_network.sh#L257
06/05/2024 12.38, Gabriel Tisan wrote:
> I tested again and I could confirm that rtw88 does not send any beacon
> in AP mode.
> Once again, maybe you could tell me which repo of the driver rtl8821cu
> you tested successfully in AP mode.
>
> On Thu, Apr 18, 2024 at 12:55 PM Viacheslav <adeep@lexina.in> wrote:
>>
>>
>>
>> 18/04/2024 09.58, Gabriel Tisan wrote:
>>> @ Viacheslav:
>>> Can you please tell me which repo did you use when your run USB 8821cu
>>> successfully in AP mode ?
>>> From your log bellow it seems that is not the mainline driver rtw88_8821cu.
>>>
>>> On Wed, Jan 17, 2024 at 10:49 AM Viacheslav <adeep@lexina.in> wrote:
>>>> I have USB RTL8821CU. It works in AP mode:
>>>>
>>>> [511809.841083] usb 1-1.4: New USB device found, idVendor=0bda,
>>>> idProduct=c820, bcdDevice= 2.00
>>>> [511809.841111] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
>>>> SerialNumber=3
>>>> [511809.841118] usb 1-1.4: Product: 802.11ac NIC
>>>> [511809.841124] usb 1-1.4: Manufacturer: Realtek
>>>> [511809.841130] usb 1-1.4: SerialNumber: 123456
>>>> [511809.973789] usbcore: registered new interface driver btusb
>>>> [511810.432057] usbcore: registered new interface driver rtl8821cu
>>
>> Damn, I thought the rtw88 driver had been picked up, but now I see that
>> it hasn't. I will test again and report back with the results.
prev parent reply other threads:[~2024-05-06 10:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 7:07 rtw88: rtl8822cs AP mode not working Viacheslav
2024-01-10 9:15 ` Ping-Ke Shih
2024-01-10 11:04 ` Viacheslav
2024-01-11 0:42 ` Ping-Ke Shih
2024-01-11 6:19 ` Viacheslav
2024-01-12 0:39 ` Ping-Ke Shih
2024-01-13 22:50 ` Martin Blumenstingl
2024-01-15 2:17 ` Ping-Ke Shih
2024-01-16 22:07 ` Martin Blumenstingl
2024-01-17 0:35 ` Ping-Ke Shih
2024-01-17 7:34 ` Sascha Hauer
2024-01-17 9:48 ` Viacheslav
2024-01-17 20:48 ` Martin Blumenstingl
2024-04-18 6:58 ` Gabriel Tisan
2024-04-18 10:55 ` Viacheslav
2024-05-06 9:38 ` Gabriel Tisan
2024-05-06 10:18 ` Viacheslav [this message]
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=a30c323a-d09a-4ea3-952b-26adf909b069@lexina.in \
--to=adeep@lexina.in \
--cc=gabriel.tisan@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).