[Bug 2127044] Re: MT7925 wifi is hard blocked on HP's machine

This bug is awaiting verification that the linux-azure-
fde-6.17/6.17.0-1008.8~24.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-noble-linux-
azure-fde-6.17' to 'verification-done-noble-linux-azure-fde-6.17'. If
the problem still exists, change the tag 'verification-needed-noble-
linux-azure-fde-6.17' to 'verification-failed-noble-linux-azure-
fde-6.17'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-azure-fde-6.17-v2 verification-needed-noble-linux-azure-fde-6.17

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2127044

Title:
MT7925 wifi is hard blocked on HP's machine

Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-firmware source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid

Bug description:
[Impact]
The wifi is hard blocked and can't be used randomly.

[Fix]
The issue is introduced by commit 085749115fd37 ("wifi: mt76: mt7925: add rfkill_poll for hardware rfkill")
The machine doesn't support this feature may lead to undefined behavior, and MTK will submit a firmware to fix this issue in the near feature.

For short-term solution, we made a DMI quick to list the machines that
doesn't support this feature.

[Test]
1. Boot up HP Z2 Mini G1a Workstation
2. Run `rfkill list` to check wlan0 block state
3. Re-plug power cord and then check rfkill state again
4. The wlan0 should not be hard blocked.

[Where problems could occur]
Should be pretty safe to return the function call directly, since the machine doesn't support it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2127044/+subscriptions