From: Florian Fainelli <f.fainelli@gmail.com>
To: Florian Schmidt <florian@fls.name>,
Greenman Gregory <gregory.greenman@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi: intel ax210: module fail load firmware: Failed to start RT ucode: -110
Date: Wed, 26 Oct 2022 10:04:33 -0700 [thread overview]
Message-ID: <cba07be4-1afc-649f-a172-19f76d726232@gmail.com> (raw)
In-Reply-To: <4077a7705bb86501a9cbbce86fe1ea8c@mail.infomaniak.com>
On 10/26/2022 8:56 AM, Florian Schmidt wrote:
> Hi Gregory,
>
> Thank you for having a look at this. The .pnvm file was present in my test as shown by my original message:
>> md5sum /lib/firmware/*
>> 787381c60d907f81a3ddadc5c990a82b ./iwlwifi-ty-a0-gf-a0-71.ucode
>> d93cbdcc4bb5be69aac128e2fe291359 ./iwlwifi-ty-a0-gf-a0.pnvm
>> 33d13d236512466e71c81257209a356f ./regulatory.db
>
> I just ran the test again, ensuring I have the .pnvm you mention and the result is indeed the same.
>
> Any other ideas to solve this are welcome.
The driver indicated it wanted to load iwlwifi-ty-a0-gf-a0-72.ucode,
which you do seem to have based upon the listing above?
--
Florian
next prev parent reply other threads:[~2022-10-26 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <91cad7f52fe275bf567cf5aa7aa6f7c0@mail.infomaniak.com>
[not found] ` <28dfa897c38286b1cf9ae30631fb7438@mail.infomaniak.com>
2022-10-14 12:42 ` iwlwifi: intel ax210: module fail load firmware: Failed to start RT ucode: -110 Florian Schmidt
2022-10-26 14:13 ` Greenman, Gregory
2022-10-26 15:56 ` Florian Schmidt
2022-10-26 17:04 ` Florian Fainelli [this message]
2022-10-26 17:37 ` Florian Schmidt
2022-10-26 17:47 ` Florian Fainelli
2022-10-26 18:11 ` Florian Schmidt
2022-10-31 8:49 ` Greenman, Gregory
2022-10-31 11:20 ` Florian Schmidt
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=cba07be4-1afc-649f-a172-19f76d726232@gmail.com \
--to=f.fainelli@gmail.com \
--cc=florian@fls.name \
--cc=gregory.greenman@intel.com \
--cc=linux-wireless@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