[SRU][F/H/I] Add MT7921 wifi fw

Bug #1936452 reported by AaronMa
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
HWE Next
Fix Released
Undecided
Unassigned
linux-firmware (Ubuntu)
Fix Released
High
Unassigned
Focal
Fix Released
Undecided
Unassigned
Hirsute
Fix Released
Undecided
Unassigned
Impish
Fix Released
High
Unassigned

Bug Description

SRU justification:

[Impact]
No support for MT7921 wifi card.

[Fix]
MT7921 needs both driver and firmware, driver is almost ready,
add firmware first, then get driver bug fixed later.

[Test]
Verified on hardware, cold boot system wifi works fine.
Reboot make it fail, but I will fix it in SRU of kernel patch.
After that, it works fine.

[Where problems could occur]
The MT7921 wifi may not work.

AaronMa (mapengyu)
no longer affects: linux (Ubuntu)
AaronMa (mapengyu)
description: updated
Revision history for this message
You-Sheng Yang (vicamo) wrote :
Revision history for this message
You-Sheng Yang (vicamo) wrote :
AaronMa (mapengyu)
tags: added: oem-priority originate-from-1928170 sutton
Timo Aaltonen (tjaalton)
Changed in linux-firmware (Ubuntu Impish):
importance: Undecided → High
Timo Aaltonen (tjaalton)
Changed in linux-firmware (Ubuntu Impish):
status: New → Fix Released
Changed in linux-firmware (Ubuntu Hirsute):
status: New → Fix Committed
Changed in linux-firmware (Ubuntu Focal):
status: New → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :

It looks to me like this is an update of an existing driver, mt7921, which it seems to me might have existing users. If that's the case will rebooting causes WiFi to fail for hardware that's already supported?

Revision history for this message
AaronMa (mapengyu) wrote (last edit ):

Hi Murray:

That bug of rebooting is fixed by bug#1936790

Revision history for this message
Chris Halse Rogers (raof) wrote :

Specifically: this is a straight addition for focal, but is an update of existing firmware for hirsute. Does the existing hirsute kernel have any driver that uses that firmware, or is that firmware unused in hirsute?

If it is unused in hirsute then updating it is less risky.

Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello AaronMa, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/1.187.16 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

according to bug 1936790 mt7921 driver is only on 5.13 and up

Revision history for this message
Chris Halse Rogers (raof) wrote :

In conversation with Timo we've verified that the relevant firmware files modified here are currently unused in hirsute - there are no hits for them in the existing mt79 driver.

Accordingly, this is not expected to affect any existing hirsute systems.

Revision history for this message
Chris Halse Rogers (raof) wrote :

Hello AaronMa, or anyone else affected,

Accepted linux-firmware into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/1.197.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

You-Sheng Yang (vicamo)
tags: added: verification-done-focal verification-done-hirsute
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Update Released

The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-firmware - 1.187.16

---------------
linux-firmware (1.187.16) focal; urgency=medium

  * Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi
    firmware crash under iperf stress tests: Microcode SW error detected.
    Restarting 0x0 (LP: #1934217)
    - iwlwifi: update and add new FWs from core56-54 release

  * [SRU] Update amdgpu/renoir firmware (LP: #1934014)
    - amdgpu: update renoir firmware from 21.20

  * To support AMD W6600 and W6700 (LP: #1938149)
    - amdgpu: add sienna cichlid firmware for 20.45
    - amdgpu: update sienna cichlid firmware for 20.50
    - amdgpu: update sienna cichlid firmware from 21.10
    - amdgpu: update sienna cichlid firmware from 21.20
    - amdgpu: add initial dimgrey cavefish firmware from 21.20

  * [SRU][F/H/I] Add MT7921 wifi fw (LP: #1936452)
    - linux-firmware: add firmware for MT7921
    - linux-firmware: update firmware for MT7921 WiFi device
    - linux-firmware: update firmware for MT7921 WiFi device to 20210612122753
    - linux-firmware: add frimware for mediatek bluetooth chip (MT7921)
    - linux-firmware: update frimware for mediatek bluetooth chip (MT7921)

  * Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error
    detected. Restarting 0x0. (LP: #1933415)
    - iwlwifi: add new FWs from core60-51 release

 -- Timo Aaltonen <email address hidden> Mon, 02 Aug 2021 18:41:24 +0300

Changed in linux-firmware (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-firmware - 1.197.3

---------------
linux-firmware (1.197.3) hirsute; urgency=medium

  * [SRU][F/H/I] Add MT7921 wifi fw (LP: #1936452)
    - linux-firmware: update firmware for MT7921 WiFi device
    - linux-firmware: update firmware for MT7921 WiFi device to 20210612122753
    - linux-firmware: update frimware for mediatek bluetooth chip (MT7921)

  * To support AMD W6600 and W6700 (LP: #1938149)
    - amdgpu: update sienna cichlid firmware from 21.10
    - amdgpu: update sienna cichlid firmware from 21.20
    - amdgpu: add initial dimgrey cavefish firmware from 21.20

 -- Timo Aaltonen <email address hidden> Mon, 02 Aug 2021 18:21:43 +0300

Changed in linux-firmware (Ubuntu Hirsute):
status: Fix Committed → Fix Released
Revision history for this message
Mario (mario156090) wrote :

Bluetooth does not work for me, I'm using Hirsute + linux 5.14 RC6.

mario@Asus-Ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.04
Release: 21.04
Codename: hirsute
mario@Asus-Ubuntu:~$

=========================================================

mario@Asus-Ubuntu:~$ inxi -nz
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  driver: r8169
  IF: enp2s0 state: down mac: <filter>
  Device-2: MEDIATEK driver: mt7921e
  IF: wlp3s0 state: up mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: Pr0 state: down mac: <filter>
  IF-ID-3: virbr0 state: down mac: <filter>
  IF-ID-4: vpn0 state: down mac: N/A
mario@Asus-Ubuntu:~$

Revision history for this message
bohb (pop-os-user-pls-dont-kill) wrote (last edit ):

Bluetooth isn't working for me either. I'm using Hirsute + linux 5.14 RC6. I needed to upgrade to linux 5.12.19 to get wi-fi working and then tried kernel versions 5.13.9/5.14-rc6. I have installed linux-firmware version 1.197.3.

Hardware Specifics: I am using an Asus Zephyrus G14 (Product Code: GA401Q).

=============================================================

xenonex@overwatch-command:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Pop
Description: Pop!_OS 21.04
Release: 21.04
Codename: hirsute

=============================================================

xenonex@overwatch-command:~$ inxi -nz
Network: Device-1: MEDIATEK driver: mt7921e
           IF: wlp2s0 state: up mac: <filter>
           IF-ID-1: virbr0 state: up speed: 10 Mbps duplex: unknown mac: <filter>
           IF-ID-2: vnet0 state: unknown speed: 10 Mbps duplex: full mac: <filter>

=============================================================

xenonex@overwatch-command:~$ blueman-adapters
blueman-adapters version 2.1.4 starting
blueman-adapters 18.31.39 ERROR Adapter:53 __init__ : No adapter(s) found

=============================================================

xenonex@overwatch-command:~$ sudo rfkill list
0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

Revision history for this message
AaronMa (mapengyu) wrote :

Looks the card doesn't work on ASUS, could you please upload the "sudo lspci -vvvnn", "lsusb -v" and dmesg?

Revision history for this message
bohb (pop-os-user-pls-dont-kill) wrote (last edit ):

I should probably mention that the card is working on Windows. I believe that I have done most of the things necessary for a proper dual boot, I have disabled hibernation entirely, I have disabled fast boot in the BIOS, and I always shut-down Windows with the command "shutdown /s /f /t 0" from an admin prompt.

Revision history for this message
bohb (pop-os-user-pls-dont-kill) wrote :

Lspci output

Revision history for this message
bohb (pop-os-user-pls-dont-kill) wrote :

Lsusb output

Revision history for this message
AaronMa (mapengyu) wrote :
Revision history for this message
bohb (pop-os-user-pls-dont-kill) wrote :

Thanks for the fix, can't wait :)

You-Sheng Yang (vicamo)
Changed in hwe-next:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.