From: Stanislaw Gruszka <sgruszka@redhat.com>
To: "g.schlmm" <g.schlmm@googlemail.com>
Cc: linux-wireless@vger.kernel.org, yhchuang@realtek.com
Subject: Re: rtw88: M.2 RTL8822BE not working - rfe 3 isn't supported
Date: Wed, 12 Jun 2019 11:13:30 +0200 [thread overview]
Message-ID: <20190612091330.GC2965@redhat.com> (raw)
In-Reply-To: <0d0159a8-a83e-cef3-fd32-4928a2301719@gmail.com>
Cc Tony
On Sat, Jun 08, 2019 at 02:26:51PM +0200, g.schlmm wrote:
> my RTL8822BE M.2 card is not working with linux 5.2rc3
>
> the staging r8822be driver in linux 5.1 was working for this card
>
> from dmesg:
> > [ 8.001186] rtw_pci 0000:04:00.0: rfe 3 isn't supported
> > [ 8.003870] rtw_pci 0000:04:00.0: failed to setup chip efuse info
> > [ 8.006405] rtw_pci 0000:04:00.0: failed to setup chip information
>
> lspci:
> > 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter
> > Subsystem: Lenovo RTL8822BE 802.11a/b/g/n/ac WiFi adapter
> > Flags: fast devsel, IRQ 19
> > I/O ports at c000 [size=256]
> > Memory at 81200000 (64-bit, non-prefetchable) [size=64K]
> > Capabilities: [40] Power Management version 3
> > Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
> > Capabilities: [70] Express Endpoint, MSI 00
> > Capabilities: [100] Advanced Error Reporting
> > Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01
> > Capabilities: [158] Latency Tolerance Reporting
> > Capabilities: [160] L1 PM Substates
> > Kernel modules: rtwpci
next prev parent reply other threads:[~2019-06-12 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 12:26 rtw88: M.2 RTL8822BE not working - rfe 3 isn't supported g.schlmm
2019-06-12 9:13 ` Stanislaw Gruszka [this message]
2019-06-14 8:24 ` Tony Chuang
2019-06-15 12:50 ` g.schlmm
2019-10-14 12:20 ` g.schlmm
2019-10-15 3:27 ` Tony Chuang
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=20190612091330.GC2965@redhat.com \
--to=sgruszka@redhat.com \
--cc=g.schlmm@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--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 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.