From: Ping-Ke Shih <pkshih@realtek.com>
To: rb <rb0171610@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: New binary rtw8852b_fw.bin not loading firmware not recognized
Date: Fri, 17 Mar 2023 00:35:27 +0000 [thread overview]
Message-ID: <386367223a2547669c60f7d1dcb42b40@realtek.com> (raw)
In-Reply-To: <df1ce994-3368-a57e-7078-8bdcccf4a1fd@gmail.com>
> -----Original Message-----
> From: rb <rb0171610@gmail.com>
> Sent: Friday, March 17, 2023 6:48 AM
> To: linux-wireless@vger.kernel.org
> Subject: New binary rtw8852b_fw.bin not loading firmware not recognized
>
> Briefly,
>
> I use rtw89_8852be in kernel driver
>
> HARDWARE:
> Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:b852]
>
> Lenovo Ideapad 1i
>
> ISSUE:
> Newest version of binary firmware 2023_03_10,
> rtw89/rtw8852b_fw.bin, will not load/firmware not recognized on Linux Kernel 6.2.5 (and others):
>
> [] loading firmare: rwt89/rtw8852b_fw.bin
> [] rtw89_8852be 0000:03:00.0: no suitable firmware found
> [] rtw89_8852be 0000:03:00.0: failed to recognize firmware
>
> Issue persists regardless of which 6.2 series kernel is used.
>
> All previous rwt89/rtw8852b_fw.bin firmware from linux-firmware 2023_02_10 and earlier loads and works
> correctly.
>
> I did file a bug report with the details:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=217207
>
The firmware format is changed, and wireless-next tree or upcoming 6.3 will
support it. I will also post this information on the bug.
Ping-Ke
next prev parent reply other threads:[~2023-03-17 0:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 22:47 New binary rtw8852b_fw.bin not loading firmware not recognized rb
2023-03-17 0:35 ` Ping-Ke Shih [this message]
2023-03-17 5:12 ` Kalle Valo
2023-03-17 5:55 ` Larry Finger
2023-03-17 7:29 ` Ping-Ke Shih
2023-03-17 8:57 ` Kalle Valo
2023-03-17 5:53 ` Larry Finger
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=386367223a2547669c60f7d1dcb42b40@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rb0171610@gmail.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.