[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I installed https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.28/+build/27759768/+files/linux-
firmware_20220329.git681281e4-0ubuntu3.28_all.deb via dpkg and rebooted,
but I still have the old firmware.
Do I need to install it via QApt? And if so, why is that?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I think the build time on both my and your firmware is the same, and
unchanged since the package installation. Your issue has a much more
reliable test, my issue manifested intermittently (and no longer
manifests since installing the updated firmware). QApt is just the GUI
deb installer in Kubuntu, installing via dpkg should be exactly the
same.
If I'm understanding @suprem1 correctly, there are actually two related
firmwares used by the same driver. It's possible that dmesg always shows
the build version of the first one of them, while only the second one
was updated. That second firmware would then be solving my issue but not
yours.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
To clarify, if your wifi card is an MT7921, it should be fixed. If it is
an MT7922, it is not fixed.
To check which card you have:
lspci | grep -i mt79
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
I had some difficulty with the test kernel, because the installation command wanted to remove the running kernel, so I got a warning about it. I think there was some kind of conflict with the normal 6.5.0-15 kernel. In the meantime, the kernel has been upgraded to 6.5.0-17, so I removed all older versions and tried again, and I think I managed to do it in the end: $ uname -a Linux rdiez-L2017 6.5.0-15-generic #15~22.04.1+TEST2049634v20240208b1-Ubuntu SMP PREEMPT_DYNAMIC Th x86_64 x86_64 x86_64 GNU/Linux This is the output from "journalctl --dmesg --follow": Feb 11 12:31:25 rdiez-L2017 kernel: FS-Cache: Loaded Feb 11 12:31:25 rdiez-L2017 kernel: Key type cifs.spnego registered Feb 11 12:31:25 rdiez-L2017 kernel: Key type cifs.idmap registered Feb 11 12:31:25 rdiez-L2017 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Feb 11 12:31:25 rdiez-L2017 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers Feb 11 12:31:25 rdiez-L2017 kernel: CIFS: Attempting to mount // This is the output from mount -l: // on /home/rdiez/MountPoints/ type cifs (rw,noexec,relatime,vers=1.0,cache=strict,username=,domain=,uid=1000,noforceuid,gid=0,noforcegid,addr=,file_mode=0666,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=61440,wsize=16384,bsize=1048576,echo_interval=4,actimeo=1,closetimeo=1,user=) I didn't specify "wsize" (I never did), so it looks like it has automatically negotiated the wsize down to 16 KiB for that SMB 1.0 connection. I then copied my test text file to and from the server, and there was no data corruption this time. So the patch is a step forwards. I am still concerned though that the work-around the patch implements is needlessly unreliable, misleading and risks data corruption at the smallest user's mistake, despite repeated reasoning in the mailing list. I hope the kernel cifs guys find the real bug and fix it properly, so that this patch can be reverted soon. By the way, during data transfer, I also get many errors like this: Feb 11 12:41:01 rdiez-L2017 kernel: CIFS: VFS: SMB signature verification returned error = -13 Feb 11 12:41:11 rdiez-L2017 kernel: CIFS: VFS: SMB signature verification returned error = -13 ... I looked more carefully this time, and it happens when I read data back from the server. It looks like there is one such warning per read block, according to the negotiated rsize. But these errors are "normal" over the years. I am guessing that the SMB 1.0 support is not very well polished. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: [Impact] Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize set will see data destruction when copying files from their systems onto a cifs smb 1.0 mount. wsize defaults to 65535 bytes, but when set to smaller values, like 16850, users will see blocks of 16850 bytes copied over, followed by 3900 binary zeros, followed by the next block of data followed by more binary zeros. A workaround is to increase wsize, but this only works for small files, as any files larger than wsize will see the bug. Most users will want to use the 6.2 HWE kernel until this is fixed. [Testcase] Start two VMs, one for the server, and the other, the client. Server -- $ sudo apt update $ sudo apt upgrade $ sudo apt install samba $ sudo vim /etc/samba/smb.conf server min protocol = NT1 [sambashare] comment = Samba on Ubuntu path = /home/ubuntu/sambashare read only = no browsable = yes $ mkdir ~/sambashare $ sudo smbpasswd -a ubuntu Client -- $ sudo apt update $ sudo apt install cifs-utils $ mkdir ~/share $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 //192.168.122.172/sambashare ~/share $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc -aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing --format '40/1 "%02x"' --format '"\n"' >"testdata.txt" ) $ sha256sum testdata.txt 9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2 testdata.txt Now copy the file to the share. Client -- $ cp testdata.txt share/ Server -- $ sha256sum sambashare/testdata.txt 9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866 sambashare/testdata.txt The SHA256 hash is different. If you view the file with less, you will find a block of wsize=16850 bytes, then 3900 bytes of binary zeros, followed by another wsize=16850 bytes, then 3900 by
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
lspci | grep -i mt79 doesn`t return anything in my case :(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038777] Re: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
I have the same error in hyper-v. It is ubuntu 22.04 and below is the corresponding error part of dmesg. It doesn't really prevent me from using it. [4.589667] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-ZV1Qen/linux-hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41 [4.589951] index 1 is out of range for type 'vmtransfer_page_range [1]' [4.590211] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-18-generic #18~22.04.1-Ubuntu [4.590216] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [4.590218] Call Trace: [4.590220] [4.590224] dump_stack_lvl+0x48/0x70 [4.590232] dump_stack+0x10/0x20 [4.590234] __ubsan_handle_out_of_bounds+0xc6/0x110 [4.590239] netvsc_receive+0x42f/0x480 [hv_netvsc] [4.590247] netvsc_poll+0x176/0x4a0 [hv_netvsc] [4.590252] ? srso_alias_return_thunk+0x5/0x7f [4.590257] __napi_poll+0x33/0x1f0 [4.590261] net_rx_action+0x181/0x2e0 [4.590263] ? srso_alias_return_thunk+0x5/0x7f [4.590265] ? srso_alias_return_thunk+0x5/0x7f [4.590269] __do_softirq+0xdc/0x349 [4.590271] ? _raw_spin_unlock+0xe/0x40 [4.590273] ? srso_alias_return_thunk+0x5/0x7f [4.590277] __irq_exit_rcu+0x75/0xa0 [4.590281] irq_exit_rcu+0xe/0x20 [4.590284] sysvec_hyperv_callback+0x92/0xd0 [4.590288] [4.590289] [4.590290] asm_sysvec_hyperv_callback+0x1b/0x20 [4.590294] RIP: 0010:pv_native_safe_halt+0xb/0x10 [4.590297] Code: 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 eb 07 0f 00 2d a9 20 2f 00 fb f4 70 9b 01 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 [4.590299] RSP: 0018:92403e20 EFLAGS: 0246 [4.590301] RAX: RBX: RCX: [4.590303] RDX: RSI: RDI: [4.590304] RBP: 92403e28 R08: R09: [4.590305] R10: R11: R12: 9240fbc0 [4.590306] R13: R14: R15: [4.590310] ? default_idle+0x9/0x30 [4.590313] arch_cpu_idle+0x9/0x10 [4.590316] default_idle_call+0x2c/0xf0 [4.590318] cpuidle_idle_call+0x153/0x190 [4.590322] do_idle+0x82/0xf0 [4.590324] cpu_startup_entry+0x2a/0x30 [4.590326] rest_init+0xde/0x100 [4.590328] ? acpi_enable_subsystem+0xe6/0x2a0 [4.590331] ? static_key_disable+0x1f/0x30 [4.590336] arch_call_rest_init+0xe/0x30 [4.590339] start_kernel+0x34f/0x440 [4.590342] x86_64_start_reservations+0x18/0x30 [4.590346] x86_64_start_kernel+0xa4/0xe0 [4.590349] secondary_startup_64_no_verify+0x17e/0x18b [4.590355] [4.590365] [4.590631] [4.590947] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-ZV1Qen/linux-hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41 [4.591246] index 1 is out of range for type 'vmtransfer_page_range [1]' [4.591509] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.5.0-18-generic #18~22.04.1-Ubuntu [4.591514] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [4.591515] Call Trace: [4.591517] [4.591518] dump_stack_lvl+0x48/0x70 [4.591521] dump_stack+0x10/0x20 [4.591523] __ubsan_handle_out_of_bounds+0xc6/0x110 [4.591527] netvsc_receive+0x44a/0x480 [hv_netvsc] [4.591534] netvsc_poll+0x176/0x4a0 [hv_netvsc] [4.591538] ? srso_alias_return_thunk+0x5/0x7f [4.591542] __napi_poll+0x33/0x1f0 [4.591544] net_rx_action+0x181/0x2e0 [4.591546] ? srso_alias_return_thunk+0x5/0x7f [4.591549] ? srso_alias_return_thunk+0x5/0x7f [4.591552] __do_softirq+0xdc/0x349 [4.591554] ? _raw_spin_unlock+0xe/0x40 [4.591595] ? srso_alias_return_thunk+0x5/0x7f [4.591599] __irq_exit_rcu+0x75/0xa0 [4.591602] irq_exit_rcu+0xe/0x20 [4.591604] sysvec_hyperv_callback+0x92/0xd0 [4.591607] [4.591608] [4.591609] asm_sysvec_hyperv_callback+0x1b/0x20 [4.591612] RIP: 0010:pv_native_safe_halt+0xb/0x10 [4.591614] Code: 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 eb 07 0f 00 2d a9 20 2f 00 fb f4 70 9b 01 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 [4.591616] RSP: 0018:92403e20 EFLAGS: 0246 [4.591618] RAX: RBX: RCX: [4.591619] RDX: RSI: RDI: [4.591620] RBP: 92403e28 R08: R09: [4.591621] R10: R11: R12: 9240fbc0 [4.591622] R13: R14: R1
[Kernel-packages] [Bug 2051720]
I discovered that Bluetooth starts working again after a cold boot (shutdown, disconnect power for 30 seconds, then boot normally). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051720 Title: Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210) Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: ``` kernel: Bluetooth: hci0: command 0xfc05 tx timeout ``` This issue started with kernel 6.5. Bluetooth has been broken ever since. The issue was not present in earlier versions of the kernel. ``` $ uname -a Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsusb | grep -i bluetooth Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth ``` ``` $ journalctl -b | egrep -i bluetooth Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth. Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support. Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110) ``` ``` linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all [installed,automatic] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2051720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Hmm... Can you post the results of
lspci | grep Network
If that doesn't show anything, post the entire lspci output.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
The output of lspci | grep Network:
01:00.0 Network controller: MEDIATEK Corp. Device 0616
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
For the record, I was running into the same issue as Max with my network
adapter.
harry@harry-Laptop:~$ lspci | grep Network
01:00.0 Network controller: MEDIATEK Corp. Device 0616
I don't have a snapshot from then, but updating my firmware from the
proposed repository didn't change the build date on my network adapter
firmware. Manually installing the newest MT7922 firmware files did seem
to update the firmware that my network card was using, though, and my
Wi-Fi connection seems to be working now.
harry@harry-Laptop:~$ sudo dmesg | grep mt
[sudo] password for harry:
[3.014470] mt7921e :01:00.0: enabling device ( -> 0002)
[3.024128] mt7921e :01:00.0: ASIC revision: 79220010
[3.108657] mt7921e :01:00.0: HW/SW Version: 0x8a108a10, Build Time:
20231120183400a
[3.128192] mt7921e :01:00.0: WM Firmware Version: 00, Build
Time: 20231120183441
[4.256697] mt7921e :01:00.0 wlp1s0: renamed from wlan0
Originally, my laptop would connect to, but not transfer data through,
my Wi-Fi 5 router. Now my laptop gets a real network connection through
my router without a hitch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2050103] Re: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake
Closing bug report as the issue was fixed in the drivers included in kernel 6.5.0-17. ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2050103 Title: Integrated Laptop screen not detected on 6.5 hwe - Intel UHD 630 Coffee Lake Status in linux-hwe-6.5 package in Ubuntu: Fix Released Bug description: lsb_release Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy Laptop: Rebadged Clevo Graphics: on-board Intel UHD 630 Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic Problem:- LCD laptop screen not detected on kernel 6.5.0-14 The laptop LCD screen is black but the external RGB monitor works fine. Using kernel 6.2.0-39, both the LCD and external monitor work. inxi -Gxx on 6.2 kernel shows 2 Monitors - DP-1 is the external and eDP-1 is the LCD Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK driver: i915 v: kernel ports: active: DP-1,eDP-1 empty: HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3e9b Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 5986:2110 Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1 compositor: gnome-shell v: 42.9 driver: X: loaded: vesa unloaded: fbdev,modesetting gpu: i915 display-ID: 0 Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19") Monitor-2: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3") OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes inxi -Gxx on 6.5 kernel shows 1 Monitor - DP-1 is the external Graphics: Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK driver: i915 v: kernel ports: active: DP-1 empty: HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3e9b Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:4 chip-ID: 5986:2110 Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1 compositor: gnome-shell v: 42.9 driver: X: loaded: vesa unloaded: fbdev,modesetting gpu: i915 display-ID: 0 Monitor-1: DP-1 model: Vw19B2 res: 1440x900 dpi: 89 diag: 483mm (19") OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes This line using journalctl is in the boot log of kernel 6.2 but not in the boot log of 6.5(probably not relevant) Jan 14 15:27:20 hybris kernel: i915 :00:02.0: [drm] Skipping intel_backlight registration Have noticed Bug:- https://answers.launchpad.net/bugs/2049245 which is against nvidia graphics but will try 1024x768 resolution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052840] Re: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62
I just tried linux-firmware 20230919.git3672ccab-0ubuntu2.8 and same issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2052840 Title: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62 Status in linux-firmware package in Ubuntu: New Bug description: Hello, I'm facing this issue before few months after software upgrade, Distro: Kubuntu 23.10 Kernel: Linux kernel 6.5.0-17-generic Linux Firmware: 20230919.git3672ccab-0ubuntu2.5 My Specs: CPU: Ryzen 9 7950X RAM: 64GB = 16GB × 4 5200/MT DDR5 GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire) Motherboard: Gigabyte B650M GAMING X AX NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at all there other users faced same issue (look like because linux-firmware): https://ubuntuforums.org/showthread.php?t=2489556 My dmesg logs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
By following a variation of Harry Mayrhofer's procedure, I've managed to
change my wireless firmware build times too! I'll watch my wireless
connection to see if it's behaving differently. Here's what I did.
For reproducibility, here are two ways that my system state differed
from the Ubuntu 22.04 defaults before I started.
* I had upgraded linux-firmware to version 20220329.git681281e4-0ubuntu3.28
from the jammy-proposed repository
* I had upgraded the kernel to version 6.5.0-18-generic, as a side effect of
upgrading my MESA graphics drivers from the kisak-mesa PPA
>From that starting point, here's how I changed my wireless firmware.
1) I removed these files from /lib/firmware/mediatek:
WIFI_MT7922_patch_mcu_1_1_hdr.bin
WIFI_RAM_CODE_MT7922_1.bin
2) I replaced them with the same files from commit
0a18a7292a66532633d9586521f0b954c68a9fbc of linux-firmware. To be explicit, I
got the new files from these URLS:
https://gitlab.com/kernel-firmware/linux-firmware/-/raw/0a18a7292a66532633d9586521f0b954c68a9fbc/mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin
https://gitlab.com/kernel-firmware/linux-firmware/-/raw/0a18a7292a66532633d9586521f0b954c68a9fbc/mediatek/WIFI_RAM_CODE_MT7922_1.bin
3) I regenerated the initial RAM disk associated with the latest version of my
kernel (which is the version that was running)
sudo update-initramfs -u
4) I rebooted
After the reboot, dmesg showed new wireless firmware build times:
[3.125009] mt7921e :01:00.0: enabling device ( -> 0002)
[3.131598] mt7921e :01:00.0: ASIC revision: 79220010
[3.217634] mt7921e :01:00.0: HW/SW Version: 0x8a108a10, Build Time:
20230627143702a
[3.234290] mt7921e :01:00.0: WM Firmware Version: 00, Build
Time: 20230627143946
[4.362764] mt7921e :01:00.0 wlp1s0: renamed from wlan0
Note that my build times are different from Harry's. I think that's
because I used the firmware files from the commit that Rudi Daemen
suggested, while Harry used the newest version of the files.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
