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: Fri, 1 Mar 2019 21:55:10 -0500 [thread overview]
Message-ID: <2e39892d-d206-e87f-c802-d427c54277cf@gmail.com> (raw)
In-Reply-To: <487c350c-c455-b490-8de5-1d68760aa3dc@lwfinger.net>
Larry,
Following up to your last reply, I blacklisted the r8822be module,
rebooted and was unable to bring up the wireless interface via rtw88.
Below are some errors recorded in my system log:
[ 267.509818] rtw_pci 0000:3d:00.0: Direct firmware load for
rtw88/rtw8822b_fw.bin failed with error -2
[ 267.509821] rtw_pci 0000:3d:00.0: failed to request firmware
[ 267.511068] rtw_pci 0000:3d:00.0: mac power on failed
[ 267.511072] rtw_pci 0000:3d:00.0: failed to power on mac
[ 267.511073] rtw_pci 0000:3d:00.0: failed to setup chip efuse info
[ 267.511075] rtw_pci 0000:3d:00.0: failed to setup chip information
[ 267.512817] rtw_pci: probe of 0000:3d:00.0 failed with error -114
As directed, I used the rtwpci module to perform load/unload the rtw88
module before I saw the errors above. Do I still need to install firmware?
Sincerely,
David R. Bergstein
On 3/1/19 8:46 PM, Larry Finger wrote:
> On 3/1/19 4:26 PM, David R. Bergstein wrote:
>> Larry,
>>
>> Thanks for the response and detailed instructions, which allowed me to
>> build and install the rtw88 kernel module. I cannot however seem to get
>> my system to actually use the module. Just to recap this is an HP Omen
>> laptop with secure boot disabled. Upon boot-up both the new rtw88 and
>> old r8822be modules are loaded. If I unload the r8822be module the wifi
>> network connection gets terminated, even if I unload/reload the rtw88
>> module.
>>
>> Is there something else I should be doing prior to invoking rtw88, e.g.,
>> blacklisting the old module?
>
> Yes, r8822be must be blacklisted. Use the lsmod command to see what
> modules are actually loaded. You load/unload rtw88 using the rtwpci
> module.
>
> Larry
>
next prev parent reply other threads:[~2019-03-02 2:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 4:09 Realtek r8822be kernel module does not negotiate 802.11ac connection 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 [this message]
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
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=2e39892d-d206-e87f-c802-d427c54277cf@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