From: "David R. Bergstein" <david.r.bergstein@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
Tony Chuang <yhchuang@realtek.com>
Cc: Pkshih <pkshih@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Realtek r8822be kernel module does not negotiate 802.11ac connection
Date: Sat, 2 Mar 2019 13:09:03 -0500 [thread overview]
Message-ID: <96c5b6c4-61fe-570d-ba2d-7721b1be7cca@gmail.com> (raw)
In-Reply-To: <c64c435c-fda7-9356-0205-093182fb1398@lwfinger.net>
Larry,
I tried using iw but it gives the same reading for bit rate. In regard
to the firmware, it was not installed via "make install" so I did it
manually.
Sincerely,
David R. Bergstein
On 3/2/19 12:58 PM, Larry Finger wrote:
>> Larry,
>>
>> Sorry about all these extra replies. Shortly after I sent my last
>> message my access point started recognizing the connection as 802.11ac
>> with PHY Rate / Modulation Rate of 866.6 Mbps. What is somewhat
>> misleading is the information reported by iwconfig (see bit rate below).
>>
>> $ iwconfig wlo1
>> wlo1 IEEE 802.11 ESSID:"XXXXXXXXXX-5G"
>> Mode:Managed Frequency:5.22 GHz Access Point:
>> xx:xx:xx:xx:xx:xx
>> Bit Rate=6.5 Mb/s Tx-Power=23 dBm
>> Retry short limit:7 RTS thr:off Fragment thr:off
>> Power Management:on
>> Link Quality=70/70 Signal level=-40 dBm
>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>> Tx excessive retries:0 Invalid misc:11 Missed beacon:0
>
> The utility iwconfig is obsolete and not exactly up to date with the
> latest in wireless. I am not an expert on iw, but I think you want 'iw
> dev wlo1 link'.
>
> I am wondering about the missing firmware stage. Had you not done the
> 'sudo make install' step, or did that step fail to install the firmware?
>
> Larry
>
next prev parent reply other threads:[~2019-03-02 18:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 4:09 David R. Bergstein
2019-02-27 10:23 ` Tony Chuang
2019-03-01 2:32 ` David R. Bergstein
2019-03-01 17:28 ` Larry Finger
2019-03-01 22:26 ` David R. Bergstein
2019-03-02 1:46 ` Larry Finger
2019-03-02 2:55 ` David R. Bergstein
2019-03-02 3:16 ` David R. Bergstein
2019-03-02 3:52 ` David R. Bergstein
2019-03-02 10:03 ` Arend Van Spriel
2019-03-04 2:34 ` Tony Chuang
2019-03-02 17:58 ` Larry Finger
2019-03-02 18:09 ` David R. Bergstein [this message]
2019-03-02 18:39 ` Larry Finger
2019-04-14 21:39 ` rtlwifi-new v0.6 and dkms failures David R. Bergstein
2019-04-16 21:19 ` David R. Bergstein
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=96c5b6c4-61fe-570d-ba2d-7721b1be7cca@gmail.com \
--to=david.r.bergstein@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=yhchuang@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
Powered by JetHome