** Description changed:
[SRU Justfication]
BugLink: https://bugs.launchpad.net/bugs/2119479
These binary firmware changes are required to fix the following issues
(provided by vendor):
Release Note:
- Fix "PCIE AER: RxErr" issue
- Fix "probe request Supported Rates Listed twice" issue
- with driver patch:
https://patchwork.kernel.org/project/linux-wireless/patch/[email protected]/
- Send Beacon frame (with MBSS IE) to driver directly for mac80211.
- with driver patch:
https://patchwork.kernel.org/project/linux-wireless/patch/[email protected]/
[Impact]
Addresses lack of some WiFi and Bluetooth functionality on mt7925 device
and undefined behavior / unreliability when connecting to some APs.
Specifically, this update changes how the beacon frame with MBSS IE is
delivered to the driver, in conjunction with this kernel change:
https://patchwork.kernel.org/project/linux-
wireless/patch/[email protected]/
[Fix]
Apply the following vendor-proposed patches from upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/mediatek/mt7925?id=2ccae12c4f73bf130143ab7cc9c8546d25faac47
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/mediatek/mt7925?id=ebf45cd0f8d0e98d08e7ecfc10342735425677b1
[Test Case]
Verify that Wifi and BT connections can still be established with the
updated blobs, and verify that MBSS functionality works as expected
[Where problems could occur]
Without these patches, affected wireless adapters connecting to 6GHz APs
that broadcast MBSSID have undefined behavior. In various tests, it was
observed that there were frequent disconnections in cases where the host
was closer in proximity to the AP, but that there were instances where a
connection could be maintained if they were farther away.
If this firmware is used without
https://patchwork.kernel.org/project/linux-
wireless/patch/[email protected]/ being
present in the running kernel, the firmware patch can cause some such
devices to be unable to detect their APs regardless of distance. This
could be perceived as a regression for users who don't observe this
issue (which would be resolved once they update their kernel to include
the related driver patch, which I will SRU into noble-generic and
derivatives).
Given that the best case behavior for impacted devices without these
patches is undefined behavior at best, I believe they are
necessary/appropriate to SRU.
[Other Info]
This update originates from a support request by Nvidia
+
+ PRs into Ubuntu's linux-firmware:
+ Questing: https://kernel.ubuntu.com/forgejo/kernel/linux-firmware/pulls/196
+ Plucky: https://kernel.ubuntu.com/forgejo/kernel/linux-firmware/pulls/197
+ Noble: https://kernel.ubuntu.com/forgejo/kernel/linux-firmware/pulls/198
** Changed in: linux-firmware (Ubuntu Plucky)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Plucky)
Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin)
** Changed in: linux-firmware (Ubuntu Noble)
Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2119479
Title:
[SRU][Q/P/N] mt7925: Wi-fi and Bluetooth FW update to 20250721232943
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2119479/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
