[Kernel-packages] [Bug 2032985] Re: Wifi works in kernel 5.19.0-46, but not in kernel 6.2.0-26 (Intel AX211)
I finally stumbled on the problem. I do not have time to investigate right now, but disabling AppArmor caused Wi-Fi to begin working again. It is possible that I ended up breaking it somewhere along the line. I marked this as invalid since I do not believe it should remain as an open bug. If I marked it incorrectly, please let me know or fix it yourself. ** Changed in: linux-meta-hwe-6.2 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2032985 Title: Wifi works in kernel 5.19.0-46, but not in kernel 6.2.0-26 (Intel AX211) Status in linux-meta-hwe-6.2 package in Ubuntu: Invalid Bug description: I am using Ubuntu 22.04.3 LTS When I updated my system and installed the new kernel (6.2.0-26), my wifi ceased to work at all, and I cannot find any way to solve this issue. I have tried the oem kernels to no avail (all versions were between 5.19.0-46 and 6.2.0-26) I have tried booting to the ubuntu 22.04.3 LTS livecd, and wifi did work in that. I even tried copying the firmware from that into my system, and that did not resolve the issue. Looking though the dmesg, I can see that when it would load cfg80211 on 5.19, it throws a trace on 6.2. the output of `dmesg` is attached. Also, in lspci, it does not say my wireless network controller has a driver in use, whereas it does on 5.19. It used to not even acknowledge the iwlwifi module, but after a purge and reinstall of all 6.2 packages, it does now show up. the output of `lspci -k` is also attached. I also included the output of `sudo journalctl -b` for completeness, and it contains the output of the service systemd-modules- load.service, which contains the line "systemd-modules-load[1404]: Failed to insert module 'iwlwifi': Invalid argument" I should also note that I have a friend who has the same laptop as I do, and was using the same version of Ubuntu, and they had faced this same problem as well due to the same causes. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-iwlwifi-generic-hwe-22.04 6.2.0.26.26~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 24 16:17:33 2023 InstallationDate: Installed on 2022-11-29 (268 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.2/+bug/2032985/+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 2041558] Re: failed to load firmware renesas_usb_fw.mem
I'm not sure that this error message causes problems. My card had firmware in its non-volatile memory, and worked without this. After I updated its firmware to 2.0.2.6 with the chip vendor's Windows tool, I didn't have problems with the card itself after suspend. https://dreamlayers.blogspot.com/2016/03/a-firmware-upgrade-fixed-linux- usb-3.html Sometimes however particular USB devices, like an Arduino Uno clone, didn't work after suspend, and I wondered if providing that firmware could help. So, I put that same 2.0.2.6 firmware extracted from k2026fwup1.exe as /lib/firmware/renesas_usb_fw.mem in /boot/initrd.img. This did remove the error message, but then after a suspend the card stopped working. Even fully cutting power isn't enough to make it work. Only using upd72020x-check-and-init from https://github.com/markusj/upd72020x-load makes it work. So, apparently supplying this firmware is dangerous, because it can corrupt the flash or otherwise mess up a USB 3 card. -- 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/2041558 Title: failed to load firmware renesas_usb_fw.mem Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-hwe-5.15 package in Ubuntu: Invalid Bug description: the log show below: xhci_hcd :27:00.0: failed to load firmware renesas_usb_fw.mem, fallback to ROM From this below, it seems just need to add renesas_usb_fw.mem into the initrd. https://bbs.archlinux.org/viewtopic.php?pid=1922549#p1922549 When the firmware is required and is not present, kernel message: Direct firmware load for renesas_usb_fw.mem failed with error When the firmware is required and is an empty file, kernel message: FW has invalid version, followed by the above message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2041558/+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 2024336] Re: LG Gram hangs at black screen on suspend on Ubuntu 23.04
This behavior is unchanged in 23.10 -- still the same bug. No such problems in Windows, and no such problem in Ubuntu prior to 23.04. -- 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/2024336 Title: LG Gram hangs at black screen on suspend on Ubuntu 23.04 Status in linux package in Ubuntu: Confirmed Bug description: My laptop is an LG Gram, model number 15Z980-R.AAS9U1. I am running the latest BIOS. Ever since upgrading to Ubuntu 23.04, my computer frequently hangs upon suspending to RAM and I am not able to recover it. The hang occurs on suspend rather than resume. I have my configuration set to suspend upon closing my laptop's lid. The first time I suspend after boot, it almost always suspends properly and appears to resume with no issues. Starting on the second or third suspend attempt, my computer's screen goes black (backlight off) but it never actually enters suspend state, as indicated by the power LED, processor temperature, and battery drain, which indicate the computer is still on. I am not able to recover the computer to a working state from this point -- it does not respond to any keyboard or touchpad input I have tried, or further closings/openings of the lid, and I need to hold the power button for several seconds to force a hard restart. Once it restarts, the first one or two suspend cycles will work again, and then the pattern continues. I experienced very infrequent suspend hang problems on 22.10, which were rare enough that I did not troubleshoot them. This problem appeared immediately after upgrading to 23.04. I use the Wayland environment by default but have also tried X11 mode to troubleshoot and the problem seemed to occur there too. Let me know what further troubleshooting would be helpful. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-23-generic 6.2.0-23.23 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andy 2317 F wireplumber /dev/snd/seq:andy 2305 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 18 23:00:17 2023 InstallationDate: Installed on 2018-12-01 (1660 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 10a5:0007 FPC FPC Sensor Controller Bus 001 Device 003: ID 0bda:562e Realtek Semiconductor Corp. LG Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LG Electronics 15Z980-R.AAS9U1 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-23-generic root=UUID=f2bf5af7-5cc8-4a4f-83e3-1b60fd7b6da7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-23-generic N/A linux-backports-modules-6.2.0-23-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-21 (58 days ago) dmi.bios.date: 04/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: K2ZC0254 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 15Z980 dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 63.41 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrK2ZC0254X64:bd04/02/2018:br0.1:efr63.41:svnLGElectronics:pn15Z980-R.AAS9U1:pvr0.1:rvnLGElectronics:rn15Z980:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:sku: dmi.product.family: Z Series dmi.product.name: 15Z980-R.AAS9U1 dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024336/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
booting with 6.5.0-25.25, and run L2CAP test case, all testcase in PTS could pass. Verification done for Mantic. ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux ** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
booting with 5.15.0-100.110, and run L2CAP test case, all testcase in PTS could pass. Verification done for Jammy. -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2052874] [NEW] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-comm
Public bug reported: $ sudo apt install linux-intel-iotg-tools-common linux-tools-common Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: hwdata The following NEW packages will be installed: hwdata linux-intel-iotg-tools-common linux-tools-common 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 649 kB of archives. After this operation, 2,011 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://in.archive.ubuntu.com/ubuntu jammy/main amd64 hwdata all 0.357-1 [26.6 kB] Get:2 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-intel-iotg-tools-common all 5.15.0-1047.53 [297 kB] Get:3 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-tools-common all 5.15.0-94.104 [326 kB] Fetched 649 kB in 2s (346 kB/s) Selecting previously unselected package hwdata. (Reading database ... 294862 files and directories currently installed.) Preparing to unpack .../hwdata_0.357-1_all.deb ... Unpacking hwdata (0.357-1) ... Selecting previously unselected package linux-intel-iotg-tools-common. Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1047.53_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1047.53) ... Selecting previously unselected package linux-tools-common. Preparing to unpack .../linux-tools-common_5.15.0-94.104_all.deb ... Unpacking linux-tools-common (5.15.0-94.104) ... dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.15.0 -94.104_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-io tg-tools-common 5.15.0-1047.53 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-tools-common_5.15.0-94.104_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-tools-common (not installed) ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: hwdata:amd64: Install linux-intel-iotg-tools-common:amd64: Install linux-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: boul-iisc 2492 F pulseaudio /dev/snd/pcmC0D0p: boul-iisc 2492 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Sun Feb 11 07:45:32 2024 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1047.53 InstallationDate: Installed on 2024-01-11 (31 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=bb015bf7-1f70-468a-9510-ceb36baafb05 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1047.53 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2023 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 01WV13 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd12/18/2023:br1.10:efr1.4:svnDellInc.:pnXPS159530:pvr:rvnDellInc.:rn01WV13:rvrA00:cvnDellInc.:ct10:cvr:sku0BEB: dmi.product.family: XPS dmi.product.name: XPS 15 9530 dmi.product.sku: 0BEB dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2052874 Title: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1047.53 Status in linux package in Ubuntu: New Bug description: $ sudo apt install linux-intel-iotg-tools-common linux-tools-common Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: hwdata The following NEW packages will be installed:
[Kernel-packages] [Bug 2052873] [NEW] package linux-intel-iotg-tools-common 5.15.0-1046.52 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf
Public bug reported: $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-image-5.15.0-92-generic linux-modules-5.15.0-92-generic linux-modules-extra-5.15.0-92-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: linux-headers-6.5.0-17-generic linux-hwe-6.5-headers-6.5.0-17 linux-image-5.15.0-94-generic linux-image-6.5.0-17-generic linux-modules-5.15.0-94-generic linux-modules-6.5.0-17-generic linux-modules-extra-5.15.0-94-generic linux-modules-extra-6.5.0-17-generic linux-modules-nvidia-535-6.5.0-17-generic linux-objects-nvidia-535-6.5.0-17-generic linux-signatures-nvidia-6.5.0-17-generic The following packages will be upgraded: code libde265-0 linux-cloud-tools-common linux-generic-hwe-22.04 linux-headers-generic-hwe-22.04 linux-image-generic linux-image-generic-hwe-22.04 linux-intel-iotg-tools-common linux-libc-dev linux-modules-nvidia-535-generic-hwe-22.04 linux-tools-common 11 upgraded, 11 newly installed, 0 to remove and 0 not upgraded. 10 standard LTS security updates Need to get 100 MB/391 MB of archives. After this operation, 1,340 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://packages.microsoft.com/repos/code stable/main amd64 code amd64 1.86.1-1707298119 [99.8 MB] Get:2 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-intel-iotg-tools-common all 5.15.0-1047.53 [297 kB] Fetched 100 MB in 5s (21.3 MB/s) Preconfiguring packages ... (Reading database ... 264771 files and directories currently installed.) Preparing to unpack .../00-code_1.86.1-1707298119_amd64.deb ... Unpacking code (1.86.1-1707298119) over (1.86.0-1706698139) ... Preparing to unpack .../01-libde265-0_1.0.8-1ubuntu0.1_amd64.deb ... Unpacking libde265-0:amd64 (1.0.8-1ubuntu0.1) over (1.0.8-1) ... Preparing to unpack .../02-linux-cloud-tools-common_5.15.0-94.104_all.deb ... Unpacking linux-cloud-tools-common (5.15.0-94.104) over (5.15.0-92.102) ... Selecting previously unselected package linux-modules-6.5.0-17-generic. Preparing to unpack .../03-linux-modules-6.5.0-17-generic_6.5.0-17.17~22.04.1_am d64.deb ... Unpacking linux-modules-6.5.0-17-generic (6.5.0-17.17~22.04.1) ... Selecting previously unselected package linux-image-6.5.0-17-generic. Preparing to unpack .../04-linux-image-6.5.0-17-generic_6.5.0-17.17~22.04.1_amd6 4.deb ... Unpacking linux-image-6.5.0-17-generic (6.5.0-17.17~22.04.1) ... Selecting previously unselected package linux-modules-extra-6.5.0-17-generic. Preparing to unpack .../05-linux-modules-extra-6.5.0-17-generic_6.5.0-17.17~22.0 4.1_amd64.deb ... Unpacking linux-modules-extra-6.5.0-17-generic (6.5.0-17.17~22.04.1) ... Preparing to unpack .../06-linux-generic-hwe-22.04_6.5.0.17.17~22.04.9_amd64.deb ... Unpacking linux-generic-hwe-22.04 (6.5.0.17.17~22.04.9) over (6.5.0.15.15~22.04. 8) ... Preparing to unpack .../07-linux-image-generic-hwe-22.04_6.5.0.17.17~22.04.9_amd 64.deb ... Unpacking linux-image-generic-hwe-22.04 (6.5.0.17.17~22.04.9) over (6.5.0.15.15~ 22.04.8) ... Selecting previously unselected package linux-hwe-6.5-headers-6.5.0-17. Preparing to unpack .../08-linux-hwe-6.5-headers-6.5.0-17_6.5.0-17.17~22.04.1_al l.deb ... Unpacking linux-hwe-6.5-headers-6.5.0-17 (6.5.0-17.17~22.04.1) ... Selecting previously unselected package linux-headers-6.5.0-17-generic. Preparing to unpack .../09-linux-headers-6.5.0-17-generic_6.5.0-17.17~22.04.1_am d64.deb ... Unpacking linux-headers-6.5.0-17-generic (6.5.0-17.17~22.04.1) ... Preparing to unpack .../10-linux-headers-generic-hwe-22.04_6.5.0.17.17~22.04.9_a md64.deb ... Unpacking linux-headers-generic-hwe-22.04 (6.5.0.17.17~22.04.9) over (6.5.0.15.1 5~22.04.8) ... Selecting previously unselected package linux-modules-5.15.0-94-generic. Preparing to unpack .../11-linux-modules-5.15.0-94-generic_5.15.0-94.104_amd64.d eb ... Unpacking linux-modules-5.15.0-94-generic (5.15.0-94.104) ... Selecting previously unselected package linux-image-5.15.0-94-generic. Preparing to unpack .../12-linux-image-5.15.0-94-generic_5.15.0-94.104_amd64.deb ... Unpacking linux-image-5.15.0-94-generic (5.15.0-94.104) ... Selecting previously unselected package linux-modules-extra-5.15.0-94-generic. Preparing to unpack .../13-linux-modules-extra-5.15.0-94-generic_5.15.0-94.104_a md64.deb ... Unpacking linux-modules-extra-5.15.0-94-generic (5.15.0-94.104) ... Preparing to unpack .../14-linux-image-generic_5.15.0.94.91_amd64.deb ... Unpacking linux-image-generic (5.15.0.94.91) over (5.15.0.92.89) ... Preparing to unpack .../15-linux-intel-iotg-tools-common_5.15.0-1047.53_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1047.53) over (5.15.0-1046.52) . .. dpkg: error processing archive
[Kernel-packages] [Bug 2052855] Re: Kernel 6.5.0-17-generic does not support Anysee E30(C)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/2052855 Title: Kernel 6.5.0-17-generic does not support Anysee E30(C) Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu Server v23.10 The default kernel 6.5.0-15-generic supports my USB Anysee E30C DVB adapter(s) But when upgrading to a newer 6.5.0-17-generic kernel, the device did not work anymore dmesg shows: dvb_usb_anysee: firmware version 1.2 hardware id 15 dvb_usb_anysee: Unsupported Anysee version. Please report to . after a roll-back to the 6.5.0-15-generic kernel the device was working again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052855/+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 1628204] Re: linux: 4.4.0-41.61 -proposed tracker
Great Information you can also checkout http://carxstreetsapk.com/ -- 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/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+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 1786013] Autopkgtest regression report (linux-meta/6.5.0.25.25)
All autopkgtests for the newly accepted linux-meta (6.5.0.25.25) for mantic have finished running. The following regressions have been reported in tests triggered by the package: systemd/253.5-1ubuntu6.1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2052856] Re: Ubuntu Studio 22.04 Kernel 6.5-Invisible Mouse Cursor
Just moving to the correct package since the signed kernel is merely derived. ** Package changed: linux-signed-lowlatency-hwe-6.2 (Ubuntu) => linux- lowlatency-hwe-6.2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2052856 Title: Ubuntu Studio 22.04 Kernel 6.5-Invisible Mouse Cursor Status in linux-lowlatency-hwe-6.2 package in Ubuntu: New Bug description: Upon a fresh install on a System76 Thelio Mira, the mouse has functionality (can click, drag, select, etc.) but the cursor is not visible. Dropping to 6.2 restores the cursor visibility, but still not sure how to fix on kernel 6.5. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1009-lowlatency 6.2.0-1009.9~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Feb 10 09:14:11 2024 InstallationDate: Installed on 2024-02-10 (0 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) SourcePackage: linux-signed-lowlatency-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency-hwe-6.2/+bug/2052856/+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 2052861] [NEW] NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10
Public bug reported: NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10 I've got one of the PCIe NVME extension HATs for rpi 5 [1] and installed a functioning NVME drive Samsung SM961. Tried to boot it first with an image of RaspberryPI OS from sd-card. Upon boot, the nvme drive was detected and I could mount it and perform some IO: > uname -a Linux raspberrypi 6.1.0-rpi8-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux > lspci -nnk :00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport :01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 [144d:a804] Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD [144d:a801] Kernel driver in use: nvme 0001:00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport 0001:01:00.0 Ethernet controller [0200]: Device [1de4:0001] Kernel driver in use: rp1 dmesg logs of rpios will be attached, but there is nothing suspicious. Then I've tried to run Ubuntu 23.10 and reimaged the sd-card with "Ubuntu Server 23.10 (64-bit) (released 2023-10-12). Upon boot, the drive didn't show up: > lspci -nnk 00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport 01:00.0 Ethernet controller [0200]: Device [1de4:0001] Kernel driver in use: rp1 Checked for updates and there was a newer kernel available, thus I've upgraded: > apt update > apt list --upgradable ... linux-image-raspi/mantic-updates,mantic-security 6.5.0.1010.11 arm64 [upgradable from: 6.5.0.1005.6] After reboot, the nvme still didn't show up. Full dmesg log is attached, but in essence the pcie driver is having troubles to enumerate one for devices on the bus: [0.00] Booting Linux on physical CPU 0x00 [0x414fd0b1] [0.00] Linux version 6.5.0-1010-raspi (buildd@bos03-arm64-017) (aarch64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.41) #13-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 18 09:08:04 UTC 2024 (Ubuntu 6.5.0-1010.13-raspi 6.5.8) ... [2.612956] brcm-pcie 100011.pcie: link down [2.617719] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01 [2.624391] pci :00:00.0: PCI bridge to [bus 01] ... [2.876967] brcm-pcie 100012.pcie: link up, 5.0 GT/s PCIe x4 (!SSC) [2.883637] pci :01:00.0: [1de4:0001] type 00 class 0x02 ... After digging a bit, I found a discussion on the Raspberry's kernel github [2]: - a bug was introduced sometime in 6.2.x [3] - a fix landed in 6.6.x [4] - it boils down to a misused `readw_` instead of `readl_` in the pcie-brcmstb driver This made me think that given that the upcoming 24.04 is going to be on 6.7 or 6.8 kernel, the fix might be already there. So I grabbed a build of the "6.7.0-1001.1"[5] kernel from the "Noble Proposed" and installed it on the Mantic on my sd-card. After reboot, the nvme drive was discovered and proper driver was loaded: > uname -a Linux pi 6.7.0-1001-raspi #1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 25 12:28:01 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux > lspci -nnk :00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport :01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 [144d:a804] Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD [144d:a801] Kernel driver in use: nvme Kernel modules: nvme 0001:00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport 0001:01:00.0 Ethernet controller [0200]: Device [1de4:0001] Kernel driver in use: rp1 > dmesg ... [2.221266] brcm-pcie 100011.pcie: link up, 5.0 GT/s PCIe x1 (!SSC) [2.227947] pci :01:00.0: [144d:a804] type 00 class 0x010802 [2.234031] pci :01:00.0: reg 0x10: [mem 0x1b-0x1b3fff 64bit] [2.241396] pci :01:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at :00:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link) ... [2.334202] nvme nvme0: pci function :01:00.0 [2.338940] nvme :01:00.0: enabling device ( -> 0002) To summarize: - RaspberryPI OS, kernel 6.1: OK - Ubuntu 23.10, kernel 6.5.0-1010: FAILS - Ubuntu 23.10, kernel 6.7.0-1001 from noble: OK It would be great if the fix[4] for mdio could land 23.10 kernel updates, so NVME drives could be used without waiting for the Noble release later this year. [1] https://geekworm.com/products/x1002 [2] https://github.com/raspberrypi/linux/issues/5873 [3] https://github.com/raspberrypi/linux/commit/ca5dcc76314d1fa6d7307fd3b95039b08d2f2b97 [4] https://github.com/raspberrypi/linux/commit/2677529a4f8a50c7567f50d67f368f1d138fb4d2 [5] -
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
After enabling the proposed repository following the instructions you
provided and running apt update, I did not see the updated package, so
I've downloaded https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.28/+build/27759768/+files/linux-
firmware_20220329.git681281e4-0ubuntu3.28_all.deb and installed it with
QApt.
After rebooting, I can see
lizsquir@PiMutant:~/Downloads$ sudo dmesg | grep mt
[sudo] password for lizsquir:
[7.182856] mt7921e :03:00.0: enabling device ( -> 0002)
[7.190207] mt7921e :03:00.0: ASIC revision: 79610010
[7.278615] mt7921e :03:00.0: HW/SW Version: 0x8a108a10, Build Time:
20231109190918a
[7.539254] mt7921e :03:00.0: WM Firmware Version: 01, Build
Time: 20231109190959
[8.367928] mt7921e :03:00.0 wlp3s0: renamed from wlan0
For me, the bug manifested in WiFi freezing
(https://askubuntu.com/questions/1499938/kubuntu-22-04-wifi-freeze-
after-hwe-kernel-upgrade-to-6-5-was-fine-on-6-2/1502925#1502925) - I did
not pay attention to IPv6. I've not had the issue reoccur in the 8 hours
since installing the proposed package.
--
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 two missing commits are specified in comment #4.
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1180974eb33ac67903269b71f35a489a2b77e5e9
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/6b91b2ef6f4173099c1434e5d7c552e51814e26e
** Tags added: verification-failed-jammy
--
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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
Do not remove PPTP. Just dont't use it for yourself. But I have no choises. -- 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/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Fix Released Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2041751/+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 examined the packages and I notice the MT7921 firmware (Which
confusingly goes by MT7961) is updated but "not" the MT7922 firmware.
Based on the above comments and below finding it seems that the MT7921
hardware is fixed with the update but not the MT7922 (which also
confusingly uses the mt7921e driver...).
I think it needs to be bumped again to pull in the MT7922 commits.
Upstream:
$ md5sum *MT79*
7cf075421ea7b6b9d0721b8744c2a576 BT_RAM_CODE_MT7922_1_1_hdr.bin
f8e386541ca02a6311d7c0d9441fbab7 BT_RAM_CODE_MT7961_1_2_hdr.bin
5b1812463de97fcb04f4eba19f37dafd WIFI_MT7922_patch_mcu_1_1_hdr.bin
0a4d833efe94a56c502de8a38405d8fe WIFI_MT7961_patch_mcu_1_2_hdr.bin
77aaec5c622d01736f7a0a5ac3d0558b WIFI_RAM_CODE_MT7922_1.bin
8d0a4f6dc2d01a8b442ae0b8d76d9122 WIFI_RAM_CODE_MT7961_1.bin
Jammy (as of 20220329.git681281e4-0ubuntu3.28)
$ md5sum *MT79*
98423461b3d66e93368a3228de2c1e4a BT_RAM_CODE_MT7922_1_1_hdr.bin
f8e386541ca02a6311d7c0d9441fbab7 BT_RAM_CODE_MT7961_1_2_hdr.bin
4180dc35aa66f62ab8a3e202b4712560 WIFI_MT7922_patch_mcu_1_1_hdr.bin
0a4d833efe94a56c502de8a38405d8fe WIFI_MT7961_patch_mcu_1_2_hdr.bin
8ff1bdc0f54f255bb2a1d6825781506b WIFI_RAM_CODE_MT7922_1.bin
8d0a4f6dc2d01a8b442ae0b8d76d9122 WIFI_RAM_CODE_MT7961_1.bin
Nobel (as of 20240202.git36777504-0ubuntu1)
$ md5sum *MT79*
7cf075421ea7b6b9d0721b8744c2a576 BT_RAM_CODE_MT7922_1_1_hdr.bin
f8e386541ca02a6311d7c0d9441fbab7 BT_RAM_CODE_MT7961_1_2_hdr.bin
5b1812463de97fcb04f4eba19f37dafd WIFI_MT7922_patch_mcu_1_1_hdr.bin
0a4d833efe94a56c502de8a38405d8fe WIFI_MT7961_patch_mcu_1_2_hdr.bin
77aaec5c622d01736f7a0a5ac3d0558b WIFI_RAM_CODE_MT7922_1.bin
8d0a4f6dc2d01a8b442ae0b8d76d9122 WIFI_RAM_CODE_MT7961_1.bin
--
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 2052856] [NEW] Ubuntu Studio 22.04 Kernel 6.5-Invisible Mouse Cursor
Public bug reported: Upon a fresh install on a System76 Thelio Mira, the mouse has functionality (can click, drag, select, etc.) but the cursor is not visible. Dropping to 6.2 restores the cursor visibility, but still not sure how to fix on kernel 6.5. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1009-lowlatency 6.2.0-1009.9~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Feb 10 09:14:11 2024 InstallationDate: Installed on 2024-02-10 (0 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) SourcePackage: linux-signed-lowlatency-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-lowlatency-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2052856 Title: Ubuntu Studio 22.04 Kernel 6.5-Invisible Mouse Cursor Status in linux-signed-lowlatency-hwe-6.2 package in Ubuntu: New Bug description: Upon a fresh install on a System76 Thelio Mira, the mouse has functionality (can click, drag, select, etc.) but the cursor is not visible. Dropping to 6.2 restores the cursor visibility, but still not sure how to fix on kernel 6.5. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1009-lowlatency 6.2.0-1009.9~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Feb 10 09:14:11 2024 InstallationDate: Installed on 2024-02-10 (0 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) SourcePackage: linux-signed-lowlatency-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-6.2/+bug/2052856/+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 2052855] Re: Kernel 6.5.0-17-generic does not support Anysee E30(C)
** Description changed: - I've installed Ubuntu Server v23.10 - The default kernel 6.5.0-15-generic supports my USB Anysee E30C + I've installed Ubuntu Server v23.10 + The default kernel 6.5.0-15-generic supports my USB Anysee E30C DVB adapter(s) But when upgrading to a newer 6.5.0-17-generic kernel, the device did not work anymore dmesg shows: dvb_usb_anysee: firmware version 1.2 hardware id 15 dvb_usb_anysee: Unsupported Anysee version. Please report to . after a roll-back to the 6.5.0-15-generic kernel the device was working again -- 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/2052855 Title: Kernel 6.5.0-17-generic does not support Anysee E30(C) Status in linux package in Ubuntu: New Bug description: I've installed Ubuntu Server v23.10 The default kernel 6.5.0-15-generic supports my USB Anysee E30C DVB adapter(s) But when upgrading to a newer 6.5.0-17-generic kernel, the device did not work anymore dmesg shows: dvb_usb_anysee: firmware version 1.2 hardware id 15 dvb_usb_anysee: Unsupported Anysee version. Please report to . after a roll-back to the 6.5.0-15-generic kernel the device was working again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052855/+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 2052855] [NEW] Kernel 6.5.0-17-generic does not support Anysee E30(C)
Public bug reported: I've installed Ubuntu Server v23.10 The default kernel 6.5.0-15-generic supports my USB Anysee E30C But when upgrading to a newer 6.5.0-17-generic kernel, the device did not work anymore dmesg shows: dvb_usb_anysee: firmware version 1.2 hardware id 15 dvb_usb_anysee: Unsupported Anysee version. Please report to . after a roll-back to the 6.5.0-15-generic kernel the device was working again ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2052855 Title: Kernel 6.5.0-17-generic does not support Anysee E30(C) Status in linux package in Ubuntu: New Bug description: I've installed Ubuntu Server v23.10 The default kernel 6.5.0-15-generic supports my USB Anysee E30C But when upgrading to a newer 6.5.0-17-generic kernel, the device did not work anymore dmesg shows: dvb_usb_anysee: firmware version 1.2 hardware id 15 dvb_usb_anysee: Unsupported Anysee version. Please report to . after a roll-back to the 6.5.0-15-generic kernel the device was working again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052855/+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
