linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stuart Longland <stuartl@longlandclan.id.au>
To: Pkshih <pkshih@realtek.com>
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: Sat, 12 Mar 2022 20:12:40 +1000	[thread overview]
Message-ID: <20220312201240.48e27a63@longlandclan.id.au> (raw)
In-Reply-To: <3f5e2f6eac344316b5dd518ebfea2f95@realtek.com>

On Mon, 8 Nov 2021 03:28:07 +0000
Hi Ping Ke, Bogdan et all…
Pkshih <pkshih@realtek.com> wrote:

> Thanks for your information. 
> Since we don't have this module, I'll have internal discussion further.
> 
> I have a quick look of RFE type 0, 2, 4 and 6. I think type 0 and 6
> are similar. So, could you try following patch to see if it works?
> 
> diff --git a/rtw8821c.c b/rtw8821c.c
> index 80a6f4da..1b86a21b 100644
> --- a/rtw8821c.c
> +++ b/rtw8821c.c
> @@ -1513,6 +1513,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),
>         [4] = RTW_DEF_RFE_EXT(8821c, 0, 0, 2),
> +       [6] = RTW_DEF_RFE(8821c, 0, 0),
>  };

I'll give this patch a try but I stumbled on another machine with this
particular WiFi chip… the Leader SN4PROv3.

I have 14 of them sitting here… all victims of the 2022 Brisbane flood.
(My workplace at Milton bought a lot of these to load with Linux and
run NodeRED flows on … then the Brisbane River decided to get out of
bed and check them out.)

Despite this, they all power on, and I'm going through and assessing
the condition of the survivors.  If there's any corrosion, so far it's
on mounting hardware like screws, with little on the PCBs itself.  The
machines were in their factory packaging at the time.

I've got three powered on now, doing a test install of Gentoo Linux as
a stress-test.  Two of the lot are happily talking on the WiFi network
here with no ill effects… barring the odd complaint:

[    4.076641] rtw_8821ce 0000:03:00.0: enabling device (0000 -> 0003)
[    4.084721] rtw_8821ce 0000:03:00.0: Firmware version 24.8.0, H2C version 12
[    4.108215] rtw_8821ce 0000:03:00.0 wlp3s0: renamed from wlan0
[    7.196982] rtw_8821ce 0000:03:00.0: start vif 24:18:c6:cd:e2:28 on port 0
[   16.273500] rtw_8821ce 0000:03:00.0: sta 7a:45:58:c8:b4:33 joined with macid 0
[   16.801990] rtw_8821ce 0000:03:00.0: failed to get tx report from firmware
[ 3104.402095] rtw_8821ce 0000:03:00.0: firmware failed to leave lps state
[ 3844.402114] rtw_8821ce 0000:03:00.0: firmware failed to leave lps state
[11020.402339] rtw_8821ce 0000:03:00.0: firmware failed to leave lps state
[11404.402353] rtw_8821ce 0000:03:00.0: firmware failed to leave lps state

A third one reports the error mentioned in this thread.  I'll grab more
details when I get it onto a wired network (at the moment it's
isolated).  Sadly, I've just nuked its Windows 10 installation.  (Not
that I expect such an OS to run well on a Celeron N3350 with 4GB RAM.)

The WiFi module appears to be soldered to the main PCB: not removable
without a hot air gun.  Seems strange that the same model PC would have
two different versions of the same family of modules.

Questions:

1. is it possible to read what "RFE" type the two working units are?
2. is this RFE value derived from reading GPIO pins?  (i.e. is possible
   my type 6 is actually a type 2 or type 4; but with some Brisbane River
   crud shorting pins out?)

-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

  reply	other threads:[~2022-03-12 10:21 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 [this message]
2022-03-13  4:01           ` Stuart Longland
2022-03-13  5:24             ` Stuart Longland
2022-03-13 16:12               ` Larry Finger

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=20220312201240.48e27a63@longlandclan.id.au \
    --to=stuartl@longlandclan.id.au \
    --cc=bogdan.nicolae@acm.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).