public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alex G." <mr.nuke.me@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: pkshih@realtek.com, neojou@gmail.com, s.hauer@pengutronix.de
Subject: Issues with rtw88_8821cu
Date: Wed, 1 Mar 2023 15:57:04 -0600	[thread overview]
Message-ID: <ee614c10-cfd7-de88-3f85-6448aaa17c5a@gmail.com> (raw)

Hi,

I'm seeing some issues with a BrosTrend AC650 adapter (rtw88_8821cu). I 
have all the recent fixes, up to and including commit 4a267bc5ea8f 
("wifi: rtw88: use RTW_FLAG_POWERON flag to prevent to power on/off twice").

1)   rtw_8821cu 1-3:1.0: Firmware version 24.11.0, H2C version 12
     rtw_8821cu 1-3:1.0: failed to download firmware
     rtw_8821cu 1-3:1.0: failed to setup chip efuse info
     rtw_8821cu 1-3:1.0: failed to setup chip information

This first issue is related to USB errors. Generally, it starts with the 
"failed to download firmware" followed by an assortment of other "failed 
to" messages. At this point the adapter may show up in iw, but is 
unusable until unplugged and replugged.

2) The second issue is unusably low Rx signal levels on the 2.4 GHz 
bands. The scan results report about 30dB to 50dB lower than adjacent 
adapters. That's if the 8821cu can even detect the beacons.

3) The third issue is that, in IBSS mode, the adapter cannot receive any 
packets or see adjacent IBSS nodes.
	iw <wlanx> station dump
shows no results, unless also running a scan. Even so, ifconfig shows 0 
Rx packets, and the adapter is not able to receive. This happens in 
either noHT, HT20, or HT40 modes.


Where do I begin getting these running?

Alex

             reply	other threads:[~2023-03-01 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 21:57 Alex G. [this message]
2023-03-03 12:51 ` Issues with rtw88_8821cu Sascha Hauer
2023-03-03 15:53   ` Larry Finger
2023-03-03 18:15     ` Alex G.

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=ee614c10-cfd7-de88-3f85-6448aaa17c5a@gmail.com \
    --to=mr.nuke.me@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=neojou@gmail.com \
    --cc=pkshih@realtek.com \
    --cc=s.hauer@pengutronix.de \
    /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