From: "Linux regression tracking (Thorsten Leemhuis)" <email@example.com>
To: "Barnabás Pőcze" <firstname.lastname@example.org>,
"Gregory Greenman" <email@example.com>
Cc: linux-wireless <firstname.lastname@example.org>,
Bagas Sanjaya <email@example.com>,
Linux kernel regressions list <firstname.lastname@example.org>
Subject: Re: iwlwifi: AX201 misdetected as AX101
Date: Thu, 29 Jun 2023 18:50:10 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On 29.06.23 17:28, Barnabás Pőcze wrote:
> 2023. június 29., csütörtök 13:31 keltezéssel, Thorsten Leemhuis <firstname.lastname@example.org> írta:
>> On 27.06.23 23:55, Barnabás Pőcze wrote:
>>> 2023. május 26., péntek 19:55 keltezéssel, Barnabás Pőcze <email@example.com> írta:
>>>> I have an Acer Aspire A315-58 laptop, which, according to lspci has the following intel wireless chip:
>>>> Device: 00:14.3
>>>> Class: Network controller 
>>>> Vendor: Intel Corporation 
>>>> Device: Wi-Fi 6 AX201 [a0f0]
>>>> SVendor: Intel Corporation 
>>>> SDevice: Wi-Fi 6 AX201 
>>>> Rev: 20
>>>> ProgIf: 00
>>>> Driver: iwlwifi
>>>> Module: iwlwifi
>>>> However, in the kernel message buffer, the following message is written:
>>>> [ 3.633490] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX101, REV=0x351
Gregory who is CCed since the start of the thread might care to look
into this. According to a quick search lspci is right, but this needs
expects. Maybe it's just a cosmetic problem.
>>> For the record, I have done a git-bisect, and that turned up
>>> as the first good commit.
>>> Sadly, that patch (or even the series) does not appear to be easily backportable,
>>> so it seems likely that current stable kernels won't be able to support this device.
>> Thx for bisecting.
>> Thing is: 6.3 will be EOL in about two or three weeks anyway. And Arch
>> will likely switch to 6.4 (which works -- or did I get this wrong?)
>> within a week or two. Makes be wonder if it's the best solution for
>> everyone involved to not resolve this and move on.
> Yes, 6.4 seems to work.
#regzbot inconclusive: unlikely to be fixed in 6.3 before EOL, but 6.4 works
> I mainly meant LTS releases. Nonetheless, lspci
> and iwlwifi still disagree on what device it actually is.
Not sure if I properly understand this.
Is this broken in 6.1.y as well, but working in earlier kernels? Then it
needs a separate report.
Or do you mean the disagreement? Maybe mentioning Gregory's name above
will do the trick to make the Intel folks look into this.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
If I did something stupid, please tell me, as explained on that page.
next prev parent reply other threads:[~2023-06-29 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 17:55 iwlwifi: AX201 misdetected as AX101 Barnabás Pőcze
2023-05-31 13:59 ` Bagas Sanjaya
2023-05-31 14:57 ` Barnabás Pőcze
2023-06-27 21:55 ` Barnabás Pőcze
2023-06-29 11:31 ` Thorsten Leemhuis
2023-06-29 15:28 ` Barnabás Pőcze
2023-06-29 16:50 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-06-29 17:30 ` Barnabás Pőcze
2023-06-29 18:46 ` Greg KH
2023-06-29 20:03 ` Barnabás Pőcze
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).