From: Rudi Heitbaum <rudi@heitbaum.com>
To: Ronald Warsow <rwarsow@gmx.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.17 00/39] 5.17.1-rc1 review
Date: Sat, 26 Mar 2022 03:20:27 +0000 [thread overview]
Message-ID: <20220326032027.GA7@ba72772bdc1f> (raw)
In-Reply-To: <67e05375-077f-ebc7-c691-b0a0a31b3479@gmx.de>
On Fri, Mar 25, 2022 at 05:45:45PM +0100, Ronald Warsow wrote:
> hallo Greg
>
> 5.17.1-rc1
>
> compiles, boots and runs on my x86_64
> (Intel i5-11400, Fedora 35)
>
> btw I get:
>
> iwlwifi 0000:00:14.3: Direct firmware load for
> iwlwifi-QuZ-a0-hr-b0-69.ucode failed with error -2
>
> (not a regression in the 5.17-series, but compared to 5.16.x !)
Hi Ronald,
68 is the current correct firmware for the iwlwifi wireless cards
The 69 version (whilst supported by the kernel) is not
yet available. See the git below.
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/log/
[ 2.797185] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 2.798575] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-69.ucode failed with error -2
[ 2.803539] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
[ 2.803550] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[ 2.803694] iwlwifi 0000:00:14.3: loaded firmware version 68.01d30b0c.0 QuZ-a0-hr-b0-68.ucode op_mode iwlmvm
[ 2.855586] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
[ 2.979429] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
[ 3.044410] iwlwifi 0000:00:14.3: base HW address:
next prev parent reply other threads:[~2022-03-26 3:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 16:45 [PATCH 5.17 00/39] 5.17.1-rc1 review Ronald Warsow
2022-03-26 3:20 ` Rudi Heitbaum [this message]
2022-03-26 12:25 ` Ronald Warsow
-- strict thread matches above, loose matches on Subject: below --
2022-03-25 15:14 Greg Kroah-Hartman
2022-03-25 23:22 ` Shuah Khan
2022-03-26 1:22 ` Fox Chen
2022-03-26 2:53 ` Rudi Heitbaum
2022-03-26 3:07 ` Florian Fainelli
2022-03-26 4:54 ` Naresh Kamboju
2022-03-26 9:55 ` Greg Kroah-Hartman
2022-03-26 12:26 ` Naresh Kamboju
2022-03-26 12:19 ` Bagas Sanjaya
2022-03-27 0:13 ` Ron Economos
2022-03-27 0:52 ` Guenter Roeck
2022-03-27 1:37 ` Justin Forbes
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=20220326032027.GA7@ba72772bdc1f \
--to=rudi@heitbaum.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rwarsow@gmx.de \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).