From: Pkshih <pkshih@realtek.com>
To: Bogdan Nicolae <bogdan.nicolae@acm.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: No support for Realtek 8821CE RFE Type 6
Date: Thu, 4 Nov 2021 00:17:17 +0000 [thread overview]
Message-ID: <e57352ddd0644463b398d6dc0a6e6a86@realtek.com> (raw)
In-Reply-To: <CA+ORkNQ_shEZGYQUmRT-_uSp3xkFA2fvfUbyGXzGkP6AmqXf6Q@mail.gmail.com>
> -----Original Message-----
> From: Bogdan Nicolae <bogdan.nicolae@acm.org>
> Sent: Thursday, November 4, 2021 1:26 AM
> To: Pkshih <pkshih@realtek.com>
> Cc: linux-wireless@vger.kernel.org
> Subject: Re: No support for Realtek 8821CE RFE Type 6
>
> Thanks Ping-Ke,
>
> The Realtek Wifi 8821CE RFE Type 6 is used in a broad range of
> embedded systems based on Intel Celeron J4125 SoCs. A popular example
> is GK3 Mini PC, sold under a large number of brands, for example:
> https://www.amazon.com/gp/product/B09FTCPBHK/
> These systems are rising in popularity in favor of laptops, as people
> tend to stay at home and are looking for affordable upgrades.
> Unfortunately, lack of Wifi Linux support is a major drawback.
>
Could you help to confirm following things:
1. Do you see "rfe 6 isn't supported" in kernel log?
I want to confirm the type again.
2. If you boot this system into Windows 10, does the 8821CE work properly?
If so, please give me its VID/PID of PCI.
3. Could I have the pictures of the module of both sides?
I would like to know the module marker; as well as antenna location.
--
Ping-Ke
next prev parent reply other threads:[~2021-11-04 0:17 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 [this message]
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
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=e57352ddd0644463b398d6dc0a6e6a86@realtek.com \
--to=pkshih@realtek.com \
--cc=bogdan.nicolae@acm.org \
--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 NNTP newsgroup(s).