All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Alexis <flexibeast@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: rtw_8821ce: "rfe 4 isn't supported". Asus D509DA laptop.
Date: Tue, 11 May 2021 13:08:00 -0500	[thread overview]
Message-ID: <9e0a95fc-f068-9478-ff59-ce9e68751149@lwfinger.net> (raw)
In-Reply-To: <8735v9sdw6.fsf@ada>

On 4/29/21 3:17 AM, Alexis wrote:
> 
> Hi all,
> 
> i've just acquired an Asus D509DA, and wifi isn't working:
> 
>    rtw_8821ce 0000:01:00.0: enabling device (0000 -> 0003)
>    rtw_8821ce 0000:01:00.0: Firmware version 24.8.0, H2C version   12
>    rtw_8821ce 0000:01:00.0: rfe 4 isn't supported
>    rtw_8821ce 0000:01:00.0: failed to setup chip efuse info
>    rtw_8821ce 0000:01:00.0: failed to setup chip information
> 
> `uname -a`:
> 
>    Linux voidlinux 5.11.16_1 #1 SMP 1619045101 x86_64 GNU/Linux
> 
> Void firmware package:
> 
>    linux-firmware-network-20210315_2
> 
> Some previous mentions of this issue on this list:
> 
>    https://marc.info/?l=linux-wireless&m=159981742905028
>    https://www.spinics.net/lists/linux-wireless/msg206075.html
> 
> Some other mentions elsewhere:
> 
>    https://bugzilla.kernel.org/show_bug.cgi?id=212435
>    https://github.com/tomaspinho/rtl8821ce/issues/142
> 
> Please let me know if there's any further information i can provide. i'm not 
> subscribed to the list.

My contact at Realtek just sent me a message containing "I'd like to let you 
know that I don't forget this thing, and my colleague is working on this. If 
there's any update, I'll let you know. Please wait a while."

Larry



  reply	other threads:[~2021-05-11 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  8:17 rtw_8821ce: "rfe 4 isn't supported". Asus D509DA laptop Alexis
2021-05-11 18:08 ` Larry Finger [this message]
2021-09-08  2:13 ` Fwd: " Alexis

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=9e0a95fc-f068-9478-ff59-ce9e68751149@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=flexibeast@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.