linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Stuart Longland <stuartl@longlandclan.id.au>,
	Pkshih <pkshih@realtek.com>, Kalle Valo <kvalo@codeaurora.org>
Cc: Bogdan Nicolae <bogdan.nicolae@acm.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: No support for Realtek 8821CE RFE Type 6
Date: Sun, 13 Mar 2022 11:12:24 -0500	[thread overview]
Message-ID: <18140c6b-bb33-8f3d-b371-fe518d6da47a@lwfinger.net> (raw)
In-Reply-To: <20220313152451.692c1508@longlandclan.id.au>

On 3/12/22 23:24, Stuart Longland wrote:
> On Sun, 13 Mar 2022 14:01:41 +1000
> Stuart Longland <stuartl@longlandclan.id.au> wrote:
> 
>> On Mon, 8 Nov 2021 03:28:07 +0000
>> Pkshih <pkshih@realtek.com> wrote:
>>
>>>>> 2. If you boot this system into Windows 10, does the 8821CE work properly?
>>>>>     If so, please give me its VID/PID of PCI.
> 
>> … now to try that patch.
> 
> The patch as given does not apply, but I managed to hand-fiddle it:
> 
> --- rtw8821c.c.orig     2022-03-13 15:13:34.406747572 +1000
> +++ rtw8821c.c  2022-03-13 15:14:20.292573052 +1000
> @@ -1498,6 +1498,7 @@
>   static const struct rtw_rfe_def rtw8821c_rfe_defs[] = {
>          [0] = RTW_DEF_RFE(8821c, 0, 0),
>          [2] = RTW_DEF_RFE_EXT(8821c, 0, 0, 2),
> +       [6] = RTW_DEF_RFE(8821c, 0, 0),
>   };
>   
>   static struct rtw_hw_reg rtw8821c_dig[] = {
> 
> This indeed fixes the problem:
> http://static.vk4msl.id.au/2022/03/13-rtl8821ce/patched-dmesg.txt
> 
> [    4.166495] rtw_8821ce 0000:03:00.0: enabling device (0000 -> 0003)
> [    4.173911] Loading firmware: rtw88/rtw8821c_fw.bin
> [    4.185625] rtw_8821ce 0000:03:00.0: Firmware version 24.8.0, H2C version 12
> [    4.273629] rtw_8821ce 0000:03:00.0 wlp3s0: renamed from wlan0
> [    7.186954] rtw_8821ce 0000:03:00.0: start vif 0c:cf:89:ac:ac:be on port 0
> [   16.074249] wlp3s0: authenticate with 7a:45:58:c8:b4:33
> [   16.692213] wlp3s0: send auth to 7a:45:58:c8:b4:33 (try 1/3)
> [   16.693038] wlp3s0: authenticated
> [   16.711971] wlp3s0: associate with 7a:45:58:c8:b4:33 (try 1/3)
> [   16.713480] wlp3s0: RX AssocResp from 7a:45:58:c8:b4:33 (capab=0x1111 status=0 aid=15)
> [   16.713526] rtw_8821ce 0000:03:00.0: sta 7a:45:58:c8:b4:33 joined with macid 0
> [   16.713795] wlp3s0: associated
> [   16.832337] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
> [   17.241966] rtw_8821ce 0000:03:00.0: failed to get tx report from firmware

Stuart,

Yes, that patch has fallen through the cracks. It has been in my repo at 
git://github.com/lwfinger/rtw88.git since Dec. 31, 2021, but is not in 
wireless-drivers-next, and not in the mainline kernel. I have added the 
maintainer for the wireless drivers to this reply, and I will follow up with him.

Larry


I recommend the GitHub repo as it will get such fixes much more quickly.

      reply	other threads:[~2022-03-13 16:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28  5:04 No support for Realtek 8821CE RFE Type 6 Bogdan Nicolae
2021-11-03  5:44 ` Pkshih
2021-11-03  8:01 ` Pkshih
2021-11-03 17:25   ` Bogdan Nicolae
2021-11-03 18:36     ` Larry Finger
2021-11-04  0:17     ` Pkshih
2021-11-05  2:10       ` Bogdan Nicolae
2021-11-08  3:28         ` Pkshih
2022-03-12 10:12           ` Stuart Longland
2022-03-13  4:01           ` Stuart Longland
2022-03-13  5:24             ` Stuart Longland
2022-03-13 16:12               ` Larry Finger [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=18140c6b-bb33-8f3d-b371-fe518d6da47a@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bogdan.nicolae@acm.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=stuartl@longlandclan.id.au \
    /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).