From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jian-Hong Pan <jian-hong@endlessm.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
"Frank A. Cancio Bello" <frank@generalsoftwareinc.com>,
Stanislaw Gruszka <sgruszka@redhat.com>,
devel@driverdev.osuosl.org, Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Upstreaming Team <linux@endlessm.com>,
Colin Ian King <colin.king@canonical.com>,
Ping-Ke Shih <pkshih@realtek.com>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [BUG] staging: r8822be: RTL8822be can't find any wireless AP
Date: Wed, 4 Jul 2018 16:04:49 +0300 [thread overview]
Message-ID: <20180704130448.pta7t5joj5qrxlpq@mwanda> (raw)
In-Reply-To: <CAPpJ_ed1oFQW_xmBtetP-ztoL7Z14T6akOSgKJ_8jxogdf3FWg@mail.gmail.com>
On Wed, Jul 04, 2018 at 04:03:33PM +0800, Jian-Hong Pan wrote:
> Hi,
>
> We have an ASUS X530UN (Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz)
> laptop equipped with Realtek rtl8822be wireless which cannot find any
> access point after WiFi is launched.
>
> Realtek rtl8822be wireless' information:
> dev@endless:~/linux-eos$ sudo lspci -nnvs 02:00.0
> 02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd.
> Device [10ec:b822] (rev ff) (prog-if ff)
> !!! Unknown header type 7f
> Kernel driver in use: r8822be
> Kernel modules: r8822be
>
> System always hits the error: "halmac_init_hal failed" in dmesg after
> WiFi is launched.
>
> [ 8.591333] r8822be: module is from the staging directory, the quality
> is unknown, you have been warned.
> [ 8.593122] r8822be 0000:02:00.0: enabling device (0000 -> 0003)
> [ 8.669163] r8822be: Using firmware rtlwifi/rtl8822befw.bin
> [ 9.289939] r8822be: rtlwifi: wireless switch is on
> [ 10.056426] r8822be 0000:02:00.0 wlp2s0: renamed from wlan0
> ...
> [ 11.952534] r8822be: halmac_init_hal failed
> [ 11.955933] r8822be: halmac_init_hal failed
> [ 11.956227] r8822be: halmac_init_hal failed
> [ 22.007942] r8822be: halmac_init_hal failed
I really prefer to see the whole dmesg instead of an edited ... in the
middle.
I agree that it feels like the default aspm setting should be 2 (use
what the chip says). Although I don't know the device well enough to
say if that will break anyone's system. Perhaps someone who knows
better will be able to respond.
regards,
dan carpenter
next prev parent reply other threads:[~2018-07-04 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 8:03 [BUG] staging: r8822be: RTL8822be can't find any wireless AP Jian-Hong Pan
2018-07-04 13:04 ` Dan Carpenter [this message]
2018-07-04 13:37 ` Daniel Drake
2018-07-04 13:55 ` Larry Finger
2018-07-04 14:09 ` Dan Carpenter
2018-07-04 15:13 ` Larry Finger
2018-07-04 15:33 ` Daniel Drake
2018-07-05 7:36 ` Pkshih
2018-07-05 9:26 ` Jian-Hong Pan
2018-07-05 9:32 ` Dan Carpenter
2018-07-05 9:57 ` Jian-Hong Pan
2018-07-05 17:06 ` Larry Finger
2018-07-06 3:34 ` Pkshih
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=20180704130448.pta7t5joj5qrxlpq@mwanda \
--to=dan.carpenter@oracle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=arnd@arndb.de \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=frank@generalsoftwareinc.com \
--cc=gregkh@linuxfoundation.org \
--cc=jian-hong@endlessm.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=pkshih@realtek.com \
--cc=sgruszka@redhat.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