[Kernel-packages] [Bug 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached
That's a different issue, LP: #2063365, which only started occurring after the recent wifi firmware bump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861338 Title: RPI4 wifi unreliable when usb3 storage is attached Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Expired Bug description: On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage device to one of the 2x usb3 ports (the ones closest to the ethernet port), wifi will sudden stop working. If you unplug the usb stick while running a ping, it will usually start working again almost instantaneously. Kernel version I have is: 5.3.0-1017-raspi2 and I've confirmed this happens on both armhf and arm64 The only thing I found in journalctl that looks suspicious is this, but it seems to have happened before plugging in the usb stick: Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from /dev/random: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2063255] [NEW] Cannot play audio from server on older models
Public bug reported: While attempting to play music as part of the ISO tests for the release, while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321 player used by the tests (which has never worked *well* on the older models, but at least worked) failed with: [0.029s] ubuntu@miss-piggy:~$ mpg321 -o alsa -a hw:1,0 test.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. Version 0.3.2-1 (2012/03/25). Written and copyrights by Joe Drew, now maintained by Nanakos Chrysostomos and others. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Title : Love on a Real Train Artist : State Azure Album : Dreams A Tribute to Tangerin Year : 2020 Comment :Genre : AmbientElectronic Playing MPEG stream from test.mp3 ... MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo Can't open libao driver with device hw:1,0 (is device in use?) I also tried ffmpeg (which usually works a bit better on the older models) and that fails with a constant series of ALSA buffer xrun errors. The specific models on which this has failed so far are the 2B and 3B+. It appears to work happily on the 4B, though. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio from server on older models Status in linux-raspi package in Ubuntu: New Bug description: While attempting to play music as part of the ISO tests for the release, while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321 player used by the tests (which has never worked *well* on the older models, but at least worked) failed with: [0.029s] ubuntu@miss-piggy:~$ mpg321 -o alsa -a hw:1,0 test.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. Version 0.3.2-1 (2012/03/25). Written and copyrights by Joe Drew, now maintained by Nanakos Chrysostomos and others. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Title : Love on a Real Train Artist : State Azure Album : Dreams A Tribute to Tangerin Year : 2020 Comment :Genre : AmbientElectronic Playing MPEG stream from test.mp3 ... MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo Can't open libao driver with device hw:1,0 (is device in use?) I also tried ffmpeg (which usually works a bit better on the older models) and that fails with a constant series of ALSA buffer xrun errors. The specific models on which this has failed so far are the 2B and 3B+. It appears to work happily on the 4B, though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+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 2062667] [NEW] Fails on (and should be removed from) raspi desktop
Public bug reported: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 ** Affects: protection-domain-mapper (Ubuntu) Importance: Undecided Status: New ** Affects: qrtr (Ubuntu) Importance: Undecided Status: New ** Also affects: qrtr (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Fails (and should be removed from) raspi desktop + Fails on (and should be removed from) raspi desktop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: New Status in qrtr package in Ubuntu: New Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2038924] Re: No alsa sound cards on Pi 5
** Changed in: linux-raspi (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2038924 Title: No alsa sound cards on Pi 5 Status in linux-raspi package in Ubuntu: Fix Released Bug description: During ISO testing of the final mantic images on the Pi 5, no ALSA cards are listed under /proc/asound/cards and (predictably) none of the ALSA utilities are able to output audio. Is this a DT related issue again? (reminiscent of LP: #1991254) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2038924/+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 1929791] Re: Bluetooth does not start if system boots from USB
I haven't managed to reproduce this on several systems (pi4 booting from USB, pi5 booting from NVMe, etc). Setting to incomplete until anyone can come up with a firm reproduction case. ** Changed in: pi-bluetooth (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1929791 Title: Bluetooth does not start if system boots from USB Status in linux-raspi2 package in Ubuntu: Invalid Status in pi-bluetooth package in Ubuntu: Incomplete Bug description: Hello! I have a strange bug with Bluetooth on Raspberry Pi 4 8Gb and Ubuntu 21.04 (also had it on Ubuntu 20.10). It's internal Bluetooth adapder does not initialize, if I boot system from USB, wherein does not matter what I am using: 16 Gb USB Flash Drive, 2 Tb External USB HDD or 1 Tb External SSD. After system boot up, it shows me "no Bluetooth adapters found", hcidev also shows nothing. I'm getting hciuart.service error: === taras@taras-rpi:~$ systemctl status hciuart.service ● hciuart.service - Configure Bluetooth Modems connected by UART Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor prese> Active: failed (Result: exit-code) since Thu 2021-05-27 08:22:57 EEST; 3mi> Process: 599 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE) тра 27 08:22:46 taras-rpi systemd[1]: Starting Configure Bluetooth Modems conne> тра 27 08:22:57 taras-rpi btuart[631]: Initialization timed out. тра 27 08:22:57 taras-rpi btuart[631]: bcm43xx_init тра 27 08:22:57 taras-rpi btuart[631]: Flash firmware /lib/firmware/brcm/BCM434> тра 27 08:22:57 taras-rpi btuart[631]: Set Controller UART speed to 300 bit> тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Control process exited, > тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Failed with result 'exit> тра 27 08:22:57 taras-rpi systemd[1]: Failed to start Configure Bluetooth Modem> === But if I continue reboot system, it may appear in 1-2 cases from 10. It'v very strange. If I disable this service manually via: === sudo systemctl disable hciuart.service === restart the system and run: === sudo systemctl start hciuart.service === Bluetooth adapter will appear in 100% cases. And if I boot Ubuntu from microSD card, everything works properly, Bluetooth starts all times. I thought, mb here is not enougth power for USB devices. I've bought USB hub with external power, but it does not help. Must say, that I don't have this problem on Raspberry Pi OS, I have it on USB HDD too and it works without any problems. Any suggestions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1929791/+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 2060942] [NEW] Missing power LED on earlier models
Public bug reported: The Pi Zero 2W, 2B, and 3B all fail to light their power LED once the kernel starts booting under noble (I hope this is only on noble; I only just noticed this during ISO testing and it's quite possible I missed it on earlier revisions...). Specifically, on the 2W (which only has a combined activity and power LED), /sys/class/leds/ACT/trigger is [actpwr] on RaspiOS, which makes it illuminate by default and blink off during mmc0 activity. This trigger setting appears to be unavailable under the Ubuntu kernel. On the 2B and 3B, the trigger is set to [none] which results in the LED initially illuminating while the bootloader is running and then disappearing. The default under RaspiOS is [input] which makes it illuminate normally, but switch off on undervolt. This trigger settging also appears unavailable under the Ubuntu kernel. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: raspi-image rls-nn-incoming ** Tags added: raspi-image ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2060942 Title: Missing power LED on earlier models Status in linux-raspi package in Ubuntu: Confirmed Bug description: The Pi Zero 2W, 2B, and 3B all fail to light their power LED once the kernel starts booting under noble (I hope this is only on noble; I only just noticed this during ISO testing and it's quite possible I missed it on earlier revisions...). Specifically, on the 2W (which only has a combined activity and power LED), /sys/class/leds/ACT/trigger is [actpwr] on RaspiOS, which makes it illuminate by default and blink off during mmc0 activity. This trigger setting appears to be unavailable under the Ubuntu kernel. On the 2B and 3B, the trigger is set to [none] which results in the LED initially illuminating while the bootloader is running and then disappearing. The default under RaspiOS is [input] which makes it illuminate normally, but switch off on undervolt. This trigger settging also appears unavailable under the Ubuntu kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060942/+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 1942260] Re: compress firmware in /lib/firmware
This was fixed with version 11 of linux-firmware-raspi in noble; I don't see a great deal of point in expending the effort to backport this to mantic, however, so I'll set that to invalid. ** Changed in: linux-firmware-raspi (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-firmware-raspi (Ubuntu Mantic) Status: Confirmed => Won't Fix -- 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/1942260 Title: compress firmware in /lib/firmware Status in firmware-sof package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware-raspi package in Ubuntu: Fix Released Status in firmware-sof source package in Mantic: Fix Released Status in initramfs-tools source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware-raspi source package in Mantic: Won't Fix Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1942260/+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 2060677] [NEW] Consistent (zfs?) errors at shutdown
Public bug reported: When shutting down Ubuntu noble desktop on my Pi 5, I consistently see the following kernel errors briefly flash by before the machine shuts down: kernel: spl: loading out-of-tree module taints kernel. kernel: zfs: module license 'CDDL' taints kernel. kernel: Disabling lock debugging due to kernel taint kernel: zfs: module license taints kernel. kernel: warning: `sssd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 3- } 21 jiffies s: 1069 root: 0x8/. kernel: rcu: blocking rcu_node structures (internal RCU debug): kernel: Sending NMI from CPU 0 to CPUs 3: kernel: NMI backtrace for cpu 3 kernel: CPU: 3 PID: 2587 Comm: modprobe Tainted: P C OE 6.8.0-1002-raspi #2-Ubuntu kernel: Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT) kernel: pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) kernel: pc : sha256_generic+0x2e8/0x10f0 [zfs] kernel: lr : sha256_generic+0x74/0x10f0 [zfs] kernel: sp : 80008389b530 kernel: x29: 80008389b610 x28: 0020 x27: 30cb87d6 kernel: x26: 94167d04 x25: 1f181b79 x24: 744284b5 kernel: x23: d7aa2aa2 x22: 9f4c26c4 x21: 6c0c81ee kernel: x20: 08800200 x19: 24378176 x18: 6617aa55 kernel: x17: ba448af2b8b7d59f x16: 56020089 x15: 3260389f kernel: x14: 0b8e0f17 x13: bc12729b x12: 73d5aafc kernel: x11: c2299b63 x10: 53710f11 x9 : 9e42204d kernel: x8 : 4640c118 x7 : d5eb7d70 x6 : 5405775e kernel: x5 : 0c7ffd41 x4 : b05fee52 x3 : 22c23503 kernel: x2 : a00063fc72c0 x1 : 0023 x0 : aa422449 kernel: Call trace: kernel: sha256_generic+0x2e8/0x10f0 [zfs] kernel: sha256_update+0x138/0x228 [zfs] kernel: SHA2Update+0x4c/0x60 [zfs] kernel: sha_incremental+0x2c/0x48 [zfs] kernel: abd_iterate_func+0x104/0x150 [zfs] kernel: abd_checksum_sha256+0x60/0xe8 [zfs] kernel: chksum_run+0xac/0x160 [zfs] kernel: chksum_benchit+0x140/0x198 [zfs] kernel: chksum_benchmark+0x1ac/0x3a8 [zfs] kernel: chksum_init+0x28/0xa8 [zfs] kernel: spa_init+0x130/0x168 [zfs] kernel: zfs_kmod_init+0x4c/0x108 [zfs] kernel: openzfs_init_os+0x1c/0xc8 [zfs] kernel: openzfs_init+0x70/0xcd0 [zfs] kernel: do_one_initcall+0x4c/0x368 kernel: do_init_module+0xa0/0x260 kernel: load_module+0x790/0x8c8 kernel: init_module_from_file+0x94/0xf8 kernel: idempotent_init_module+0x178/0x2a8 kernel: __arm64_sys_finit_module+0x6c/0xd8 kernel: invoke_syscall+0x50/0x120 kernel: el0_svc_common.constprop.0+0x48/0xf0 kernel: do_el0_svc+0x24/0x38 kernel: el0_svc+0x48/0x178 kernel: el0t_64_sync_handler+0x120/0x130 kernel: el0t_64_sync+0x1a8/0x1b0 I'm unsure why the kernel is attempting to load zfs on shutdown, or why this error occurs but it does seem consistent (I've got at least 5 separate backtraces similar to the above on shutdown in my kern.log). ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2060677 Title: Consistent (zfs?) errors at shutdown Status in linux-raspi package in Ubuntu: New Bug description: When shutting down Ubuntu noble desktop on my Pi 5, I consistently see the following kernel errors briefly flash by before the machine shuts down: kernel: spl: loading out-of-tree module taints kernel. kernel: zfs: module license 'CDDL' taints kernel. kernel: Disabling lock debugging due to kernel taint kernel: zfs: module license taints kernel. kernel: warning: `sssd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 3- } 21 jiffies s: 1069 root: 0x8/. kernel: rcu: blocking rcu_node structures (internal RCU debug): kernel: Sending NMI from CPU 0 to CPUs 3: kernel: NMI backtrace for cpu 3 kernel: CPU: 3 PID: 2587 Comm: modprobe Tainted: P C OE 6.8.0-1002-raspi #2-Ubuntu kernel: Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT) kernel: pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) kernel: pc : sha256_generic+0x2e8/0x10f0 [zfs] kernel: lr : sha256_generic+0x74/0x10f0 [zfs] kernel: sp : 80008389b530 kernel: x29: 80008389b610 x28: 0020 x27: 30cb87d6 kernel: x26: 94167d04 x25: 1f181b79 x24: 744284b5 kernel: x23: d7aa2aa2 x22: 9f4c26c4 x21: 6c0c81ee kernel: x20: 08800200 x19: 24378176 x18: 6617aa55 kernel: x17:
[Kernel-packages] [Bug 2052861] Re: NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10
I believe this is also "fixed" (or rather wasn't an issue) with the noble kernel; at least testing the current noble desktop beta image from an SD card shows an NVMe drive attached to a pimoroni base. I'll mark this as Fix Released; please feel free to re-open if this re-appears on the noble images. ** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2052861 Title: NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10 Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Mantic: Fix Released Bug description: [Impact] NVMe devices connected via PCIe are not enumerated on Raspberry Pi 5. [Fix] https://github.com/raspberrypi/linux/commit/2677529a4f8a50c7567f50d67f368f1d138fb4d2 [Test Case] Check whether NVMe devices connected via PCIe are detected with lspci/lsblk. [Where Problems Could Occur] PCIe devices might misbehave. [Original Description] 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
[Kernel-packages] [Bug 2060300] [NEW] KMS overlay causes OOM oops on 3A+
Public bug reported: Came across something bizarre when investigating the audio situation with server on the Pi 5 (LP: #2038924). Moving the server images to use the KMS overlay solves the situation, and would be preferable as it would eliminate another difference between server and desktop images. However, it also renders the 512MB 3A+ unbootable with an out-of-memory error. The reason this is strange is that the 512MB Zero 2W continues to boot quite happily. I'm attaching the serial output from the kernel up to the point of the crash (screenlog.0). The only changes made to the stock server config.txt were the addition of these lines under the final "[all]" section: [all] dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 This setup booted happily on all other boards. A trivial workaround is to manually specify a smaller CMA on the 3A+ with: dtoverlay=vc4-kms-v3d,cma-128 With this alteration, it boots happily (and I'll be using this in an appropriate [section] to work around the issue), but it might be nice to understand why this is required on this board specifically (and why the 512MB Zero 2W doesn't exhibit the same issue). ** Affects: linux-raspi (Ubuntu) Importance: Low Status: New ** Attachment added: "screenlog.0" https://bugs.launchpad.net/bugs/2060300/+attachment/5761694/+files/screenlog.0 ** Changed in: linux-raspi (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2060300 Title: KMS overlay causes OOM oops on 3A+ Status in linux-raspi package in Ubuntu: New Bug description: Came across something bizarre when investigating the audio situation with server on the Pi 5 (LP: #2038924). Moving the server images to use the KMS overlay solves the situation, and would be preferable as it would eliminate another difference between server and desktop images. However, it also renders the 512MB 3A+ unbootable with an out- of-memory error. The reason this is strange is that the 512MB Zero 2W continues to boot quite happily. I'm attaching the serial output from the kernel up to the point of the crash (screenlog.0). The only changes made to the stock server config.txt were the addition of these lines under the final "[all]" section: [all] dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 This setup booted happily on all other boards. A trivial workaround is to manually specify a smaller CMA on the 3A+ with: dtoverlay=vc4-kms-v3d,cma-128 With this alteration, it boots happily (and I'll be using this in an appropriate [section] to work around the issue), but it might be nice to understand why this is required on this board specifically (and why the 512MB Zero 2W doesn't exhibit the same issue). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060300/+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 2060240] [NEW] Pi DAC+ fails on Pi 5
Public bug reported: First reported on the Raspberry Pi forums (https://forums.raspberrypi.com/viewtopic.php?p=2162847), I've since confirmed that the Raspberry Pi DAC+ HAT (formerly the IQaudIO DAC+ HAT, which is basically the same board) works happily under RaspiOS on the Pi 5, but not Ubuntu 23.10 or 24.04. The board *does* work on Ubuntu on prior models, including 3B+ and 4B (those are all I've tested so far), but it does require the overlay (iqaudio-dacplus or rpi-dacplus depending on the variant) to be manually specified in config.txt (RaspiOS automatically detects and loads the board; I haven't figured out why we don't yet but that's an additional data-point that may be worth exploring). Anyway, on the Pi 5 the HAT is detected (/proc/device-tree/hat/uuid is populated with the correct value, and /proc/device-tree/hat/product lists "Pi-DAC+" which is correct), but the following appears in dmesg: [7.383734] designware-i2s 1f000a.i2s: Missing dma channel for stream: 0 [7.392977] designware-i2s 1f000a.i2s: ASoC: error at snd_soc_pcm_component_new on 1f000a.i2s: -22 [7.403212] snd-rpi-iqaudio-dac soc:sound: ASoC: can't create pcm Raspberry Pi DAC+ HiFi :-22 [7.405612] rpivid 100080.codec: bcm2712_iommu_of_xlate: MMU 105100.iommu [7.416183] rpivid 100080.codec: bcm2712_iommu_probe_device: MMU 105100.iommu [7.418036] snd-rpi-iqaudio-dac soc:sound: snd_soc_register_card() failed: -22 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2060240 Title: Pi DAC+ fails on Pi 5 Status in linux-raspi package in Ubuntu: New Bug description: First reported on the Raspberry Pi forums (https://forums.raspberrypi.com/viewtopic.php?p=2162847), I've since confirmed that the Raspberry Pi DAC+ HAT (formerly the IQaudIO DAC+ HAT, which is basically the same board) works happily under RaspiOS on the Pi 5, but not Ubuntu 23.10 or 24.04. The board *does* work on Ubuntu on prior models, including 3B+ and 4B (those are all I've tested so far), but it does require the overlay (iqaudio-dacplus or rpi-dacplus depending on the variant) to be manually specified in config.txt (RaspiOS automatically detects and loads the board; I haven't figured out why we don't yet but that's an additional data-point that may be worth exploring). Anyway, on the Pi 5 the HAT is detected (/proc/device-tree/hat/uuid is populated with the correct value, and /proc/device-tree/hat/product lists "Pi-DAC+" which is correct), but the following appears in dmesg: [7.383734] designware-i2s 1f000a.i2s: Missing dma channel for stream: 0 [7.392977] designware-i2s 1f000a.i2s: ASoC: error at snd_soc_pcm_component_new on 1f000a.i2s: -22 [7.403212] snd-rpi-iqaudio-dac soc:sound: ASoC: can't create pcm Raspberry Pi DAC+ HiFi :-22 [7.405612] rpivid 100080.codec: bcm2712_iommu_of_xlate: MMU 105100.iommu [7.416183] rpivid 100080.codec: bcm2712_iommu_probe_device: MMU 105100.iommu [7.418036] snd-rpi-iqaudio-dac soc:sound: snd_soc_register_card() failed: -22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060240/+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 2048864] Re: Remove armhf support
Indeed -- the Pi isn't compatible with our generic arm64 kernel, so we'll be sticking with the flavour limit for the time being, and this does actually reduce our delta with Debian. I've got a couple of other patches to incorporate into f-k this week, so I'm going to sponsor this as part of a larger upload but that should be fine for the devel series. ** Changed in: flash-kernel (Ubuntu Noble) Status: Won't Fix => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2048864 Title: Remove armhf support Status in flash-kernel package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in flash-kernel source package in Noble: New Status in linux-raspi source package in Noble: New Bug description: Noble and newer don't support armhf for Pi anymore. We can drop the armhf specific kernel flavor raspi-nolpae from flash-kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2048864/+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 1959113] Re: missing built-in disk encryption at install time
rpi-imager currently has no facility to encrypt the image it flashes to the storage on the Pi (and making such a facility generic enough that it would fit all potentially interested distros is a daunting task to say the least), so this isn't valid for rpi-imager. I *did* add some initial steps towards this in the lunar desktop images, which preserve space at the end of the root partition for LUKS headers (by ensuring the root file-system doesn't expand *all* the way to the partition size) which should make this easier to achieve in future, but there's still plenty of work to be done here. ** Changed in: rpi-imager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1959113 Title: missing built-in disk encryption at install time Status in Ubuntu: New Status in linux-firmware-raspi package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in rpi-imager package in Ubuntu: Invalid Bug description: Is there a simple way to install Ubuntu on SD card for Raspberry Pi4 with full disk encryption? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959113/+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 1874354] Re: limited wireles channels on a RPi 3B
Ah, I remember this old one. We discussed this with upstream and found the issue was that for that specific firmware, the clm-blob was included in the firmware blob itself, but the code that loaded firmware blobs still warned that it couldn't find the external file. That code was eventually cleaned up so it no longer complains, so this is essentially fix released. ** Changed in: linux-meta-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1874354 Title: limited wireles channels on a RPi 3B Status in linux-meta-raspi package in Ubuntu: Fix Released Bug description: I saw the following in my dmesg: [ 13.113608] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 13.113640] cfg80211: failed to load regulatory.db [ 13.259143] brcmfmac: F1 signature read @0x1800=0x1541a9a6 [ 13.268452] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 13.279732] usbcore: registered new interface driver brcmfmac [ 13.520854] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 13.532110] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 13.552859] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f I don't know if the channels are really limited. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-raspi 5.4.0.1008.8 ProcVersionSignature: User Name 5.4.0-1008.8-raspi 5.4.29 Uname: Linux 5.4.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Thu Apr 23 00:29:47 2020 SourcePackage: linux-meta-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/1874354/+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 1862760] Re: Unreliable 802.11ac connection on our raspi images
At this point, we've had all the necessary firmware blobs for numerous releases and I'm reasonably convinced that the remaining AC wifi issues are largely related to incorrect regulatory domain, because we don't provide a friendly way of setting this on desktop (see LP: #1951586 for more on this). I'm going to mark bionic as won't fix as it's EOL (sans ESM) anyway, focal as fix released as we did add all the relevant blobs (at the time) as a back-port to that, and the devel versions as fix released. If anyone is still have 802.11ac connectivity issues, I strongly recommend checking the wifi regulatory domain with "iw reg get". If it doesn't match your expected country, please see: * For server, see the "regulatory-domain" setting under "wifis:" in netplan -- https://netplan.readthedocs.io/en/stable/netplan- yaml/#properties-for-device-type-wifis * For desktop, add "cfg80211.ieee80211_regdom=CC" where CC is your country code to "/boot/firmware/cmdline.txt" and reboot. Urgh. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux-firmware-raspi2 (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: linux-firmware-raspi2 (Ubuntu Focal) Status: Triaged => Fix Released ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu) Status: New => Invalid ** Changed in: netplan.io (Ubuntu) Status: New => Invalid ** Changed in: netplan.io (Ubuntu Bionic) Status: New => Invalid ** Changed in: netplan.io (Ubuntu Focal) Status: New => Invalid -- 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/1862760 Title: Unreliable 802.11ac connection on our raspi images Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-raspi2 package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware-raspi2 source package in Bionic: Won't Fix Status in linux-raspi2-5.3 source package in Bionic: Won't Fix Status in netplan.io source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Won't Fix Status in linux-firmware-raspi2 source package in Eoan: Won't Fix Status in linux-raspi2-5.3 source package in Eoan: Won't Fix Status in netplan.io source package in Eoan: Won't Fix Status in linux-firmware source package in Focal: Invalid Status in linux-firmware-raspi2 source package in Focal: Fix Released Status in linux-raspi source package in Focal: Invalid Status in netplan.io source package in Focal: Invalid Bug description: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue can be located. While preparing and testing 18.04.4, certification reported issues with our uc18 images on the pi4 with wifi ac tests. One of our engineers (Brian) confirmed it locally with a wifi access point restricted only to 802.11ac. After some additional testing, he noticed that he had the same unreliable symptoms for both the classic and core images, as well as the 19.10.1 classic images. The symptoms seem to vary, from inability to detect 802.11ac APs, inability to connect and/or receive an IP address and no traffic getting through. We will provide all the information that we have. Raspbian works better in this regard. We have pulled in the wifi firmware bits from Raspbian and using those, and that seems to resolve all flakiness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+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 2041741] Re: Fan speed Control not working on RASPERRY PI RUNNING UBUNTU 23.10
** Changed in: linux-raspi (Ubuntu) Importance: Undecided => High ** Also affects: linux-raspi (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu Mantic) Importance: Undecided => High ** Summary changed: - Fan speed Control not working on RASPERRY PI RUNNING UBUNTU 23.10 + Fan speed control not working on Pi 5 under Ubuntu 23.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2041741 Title: Fan speed control not working on Pi 5 under Ubuntu 23.10 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Mantic: Confirmed Bug description: The fan speed control when running Ubuntu 23.10 on a Raspberry Pi 5 does not appear to be working. The fan runs at near maximum speed all the time and the cur_state in /sys/class/thermal/cooling_device0/ is stuck at the value of 4 no matter what the CPU temperature. I suspect it is related to this fault reported on Raspberry Pi OS: https://forums.raspberrypi.com/viewtopic.php?t=356881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2041741/+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 2037642] Re: [FFe] Raspberry Pi 5 support
** Changed in: ubuntu-release-notes Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: Fix Released Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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 2037059] Re: array index out of bounds in brcmfmac driver
** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037059 Title: array index out of bounds in brcmfmac driver Status in linux-raspi package in Ubuntu: Fix Released Bug description: Activating wifi on the current Mantic Beta images, on a Raspberry Pi 4B with 4GB or 8GB of RAM (the only two I've tested thus far) causes the following to show up in dmesg: [ 10.384021] [ 10.393418] UBSAN: array-index-out-of-bounds in /build/linux-raspi-dZDMS4/linux-raspi-6.5.0/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:1126:27 [ 10.408653] index 1 is out of range for type '__le16 [1]' [ 10.414856] CPU: 2 PID: 581 Comm: wpa_supplicant Tainted: G C E 6.5.0-1002-raspi #2-Ubuntu [ 10.414876] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 10.414881] Call trace: [ 10.414884] dump_backtrace+0x9c/0x128 [ 10.414897] show_stack+0x20/0x38 [ 10.414903] dump_stack_lvl+0xbc/0x120 [ 10.414911] dump_stack+0x18/0x28 [ 10.414916] __ubsan_handle_out_of_bounds+0xac/0xe8 [ 10.414922] brcmf_escan_prep+0x31c/0x338 [brcmfmac] [ 10.415003] brcmf_run_escan+0xac/0x1c8 [brcmfmac] [ 10.415050] brcmf_do_escan+0x90/0x100 [brcmfmac] [ 10.415096] brcmf_cfg80211_scan+0x108/0x2b0 [brcmfmac] [ 10.415142] rdev_scan+0x38/0x158 [cfg80211] [ 10.415348] cfg80211_scan+0x134/0x178 [cfg80211] [ 10.415453] nl80211_trigger_scan+0x438/0x9d8 [cfg80211] [ 10.415557] genl_family_rcv_msg_doit.isra.0+0xc0/0x130 [ 10.415568] genl_family_rcv_msg+0x1c8/0x240 [ 10.415574] genl_rcv_msg+0x64/0xe8 [ 10.415580] netlink_rcv_skb+0x64/0x138 [ 10.415586] genl_rcv+0x40/0x60 [ 10.415592] netlink_unicast+0x2f0/0x350 [ 10.415598] netlink_sendmsg+0x26c/0x490 [ 10.415603] sock_sendmsg+0x64/0xc0 [ 10.415610] sys_sendmsg+0x260/0x318 [ 10.415615] ___sys_sendmsg+0x88/0xf0 [ 10.415621] __sys_sendmsg+0x70/0xd8 [ 10.415626] __arm64_sys_sendmsg+0x2c/0x40 [ 10.415632] invoke_syscall+0x50/0x120 [ 10.415638] el0_svc_common.constprop.0+0x6c/0x140 [ 10.415642] do_el0_svc+0x34/0x50 [ 10.415646] el0_svc+0x30/0xc8 [ 10.415654] el0t_64_sync_handler+0x120/0x130 [ 10.415659] el0t_64_sync+0x1a8/0x1b0 [ 10.415668] However, the wifi still works afterward, so it's not entirely fatal! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2037059/+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 2038924] [NEW] No alsa sound cards on Pi 5
Public bug reported: During ISO testing of the final mantic images on the Pi 5, no ALSA cards are listed under /proc/asound/cards and (predictably) none of the ALSA utilities are able to output audio. Is this a DT related issue again? (reminiscent of LP: #1991254) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2038924 Title: No alsa sound cards on Pi 5 Status in linux-raspi package in Ubuntu: New Bug description: During ISO testing of the final mantic images on the Pi 5, no ALSA cards are listed under /proc/asound/cards and (predictably) none of the ALSA utilities are able to output audio. Is this a DT related issue again? (reminiscent of LP: #1991254) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2038924/+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 2037642] Re: [FFe] Raspberry Pi 5 support
The rpiboot package can be skipped for now; according to upstream the updated package won't be ready at release. The separate bug LP: #2032178 will track updates if/when I can get the uploaded. ** No longer affects: rpiboot (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037059] [NEW] array index out of bounds in brcmfmac driver
Public bug reported: Activating wifi on the current Mantic Beta images, on a Raspberry Pi 4B with 4GB or 8GB of RAM (the only two I've tested thus far) causes the following to show up in dmesg: [ 10.384021] [ 10.393418] UBSAN: array-index-out-of-bounds in /build/linux-raspi-dZDMS4/linux-raspi-6.5.0/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:1126:27 [ 10.408653] index 1 is out of range for type '__le16 [1]' [ 10.414856] CPU: 2 PID: 581 Comm: wpa_supplicant Tainted: G C E 6.5.0-1002-raspi #2-Ubuntu [ 10.414876] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 10.414881] Call trace: [ 10.414884] dump_backtrace+0x9c/0x128 [ 10.414897] show_stack+0x20/0x38 [ 10.414903] dump_stack_lvl+0xbc/0x120 [ 10.414911] dump_stack+0x18/0x28 [ 10.414916] __ubsan_handle_out_of_bounds+0xac/0xe8 [ 10.414922] brcmf_escan_prep+0x31c/0x338 [brcmfmac] [ 10.415003] brcmf_run_escan+0xac/0x1c8 [brcmfmac] [ 10.415050] brcmf_do_escan+0x90/0x100 [brcmfmac] [ 10.415096] brcmf_cfg80211_scan+0x108/0x2b0 [brcmfmac] [ 10.415142] rdev_scan+0x38/0x158 [cfg80211] [ 10.415348] cfg80211_scan+0x134/0x178 [cfg80211] [ 10.415453] nl80211_trigger_scan+0x438/0x9d8 [cfg80211] [ 10.415557] genl_family_rcv_msg_doit.isra.0+0xc0/0x130 [ 10.415568] genl_family_rcv_msg+0x1c8/0x240 [ 10.415574] genl_rcv_msg+0x64/0xe8 [ 10.415580] netlink_rcv_skb+0x64/0x138 [ 10.415586] genl_rcv+0x40/0x60 [ 10.415592] netlink_unicast+0x2f0/0x350 [ 10.415598] netlink_sendmsg+0x26c/0x490 [ 10.415603] sock_sendmsg+0x64/0xc0 [ 10.415610] sys_sendmsg+0x260/0x318 [ 10.415615] ___sys_sendmsg+0x88/0xf0 [ 10.415621] __sys_sendmsg+0x70/0xd8 [ 10.415626] __arm64_sys_sendmsg+0x2c/0x40 [ 10.415632] invoke_syscall+0x50/0x120 [ 10.415638] el0_svc_common.constprop.0+0x6c/0x140 [ 10.415642] do_el0_svc+0x34/0x50 [ 10.415646] el0_svc+0x30/0xc8 [ 10.415654] el0t_64_sync_handler+0x120/0x130 [ 10.415659] el0t_64_sync+0x1a8/0x1b0 [ 10.415668] However, the wifi still works afterward, so it's not entirely fatal! ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037059 Title: array index out of bounds in brcmfmac driver Status in linux-raspi package in Ubuntu: New Bug description: Activating wifi on the current Mantic Beta images, on a Raspberry Pi 4B with 4GB or 8GB of RAM (the only two I've tested thus far) causes the following to show up in dmesg: [ 10.384021] [ 10.393418] UBSAN: array-index-out-of-bounds in /build/linux-raspi-dZDMS4/linux-raspi-6.5.0/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:1126:27 [ 10.408653] index 1 is out of range for type '__le16 [1]' [ 10.414856] CPU: 2 PID: 581 Comm: wpa_supplicant Tainted: G C E 6.5.0-1002-raspi #2-Ubuntu [ 10.414876] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 10.414881] Call trace: [ 10.414884] dump_backtrace+0x9c/0x128 [ 10.414897] show_stack+0x20/0x38 [ 10.414903] dump_stack_lvl+0xbc/0x120 [ 10.414911] dump_stack+0x18/0x28 [ 10.414916] __ubsan_handle_out_of_bounds+0xac/0xe8 [ 10.414922] brcmf_escan_prep+0x31c/0x338 [brcmfmac] [ 10.415003] brcmf_run_escan+0xac/0x1c8 [brcmfmac] [ 10.415050] brcmf_do_escan+0x90/0x100 [brcmfmac] [ 10.415096] brcmf_cfg80211_scan+0x108/0x2b0 [brcmfmac] [ 10.415142] rdev_scan+0x38/0x158 [cfg80211] [ 10.415348] cfg80211_scan+0x134/0x178 [cfg80211] [ 10.415453] nl80211_trigger_scan+0x438/0x9d8 [cfg80211] [ 10.415557] genl_family_rcv_msg_doit.isra.0+0xc0/0x130 [ 10.415568] genl_family_rcv_msg+0x1c8/0x240 [ 10.415574] genl_rcv_msg+0x64/0xe8 [ 10.415580] netlink_rcv_skb+0x64/0x138 [ 10.415586] genl_rcv+0x40/0x60 [ 10.415592] netlink_unicast+0x2f0/0x350 [ 10.415598] netlink_sendmsg+0x26c/0x490 [ 10.415603] sock_sendmsg+0x64/0xc0 [ 10.415610] sys_sendmsg+0x260/0x318 [ 10.415615] ___sys_sendmsg+0x88/0xf0 [ 10.415621] __sys_sendmsg+0x70/0xd8 [ 10.415626] __arm64_sys_sendmsg+0x2c/0x40 [ 10.415632] invoke_syscall+0x50/0x120 [ 10.415638] el0_svc_common.constprop.0+0x6c/0x140 [ 10.415642] do_el0_svc+0x34/0x50 [ 10.415646] el0_svc+0x30/0xc8 [ 10.415654] el0t_64_sync_handler+0x120/0x130 [ 10.415659] el0t_64_sync+0x1a8/0x1b0 [ 10.415668] However, the wifi still works afterward, so it's not entirely fatal! To manage notifications about this bug
[Kernel-packages] [Bug 2035373] [NEW] Move nbd module into modules (from -extra)
Public bug reported: Would it be possible to move the "nbd" kernel module from linux-modules- extra-raspi into linux-modules-extra? This would enable NBD-based network boot (which has certain advantages over the NFS-based network boot more traditional in the Pi world, such as permitting services that refuse to run on NFS -- like snapd). ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2035373 Title: Move nbd module into modules (from -extra) Status in linux-raspi package in Ubuntu: New Bug description: Would it be possible to move the "nbd" kernel module from linux- modules-extra-raspi into linux-modules-extra? This would enable NBD- based network boot (which has certain advantages over the NFS-based network boot more traditional in the Pi world, such as permitting services that refuse to run on NFS -- like snapd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2035373/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
** Tags removed: rls-ll-incoming ** Tags added: foundations-todo -- 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/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 2019320] [NEW] i2c devices missing in lunar
Public bug reported: In the lunar release of linux-raspi, despite the boot configuration enabling the i2c_arm parameter of the base overlay, the usual /dev/i2c-0 and /dev/i2c-1 devices are missing (they are present in jammy and kinetic). These are the I2C interfaces present on the GPIO header (and thus rather important on the raspi as without these interfaces being present, I2C devices connected to the header cannot be used). I'm guessing this is a kernel change, but it *might* be something in the udev configuration; I haven't dug that far yet. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2019320 Title: i2c devices missing in lunar Status in linux-raspi package in Ubuntu: New Bug description: In the lunar release of linux-raspi, despite the boot configuration enabling the i2c_arm parameter of the base overlay, the usual /dev/i2c-0 and /dev/i2c-1 devices are missing (they are present in jammy and kinetic). These are the I2C interfaces present on the GPIO header (and thus rather important on the raspi as without these interfaces being present, I2C devices connected to the header cannot be used). I'm guessing this is a kernel change, but it *might* be something in the udev configuration; I haven't dug that far yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2019320/+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 1970603] Re: DSI touchscreen not working with KMS under 5.15
Under lunar's 6.2 kernel the situation is the same as kinetic's 5.19 kernel: display output works, but rotation is ignored and touchscreen input doesn't work. ** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1970603 Title: DSI touchscreen not working with KMS under 5.15 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Jammy: New Status in linux-raspi source package in Kinetic: New Status in linux-raspi source package in Lunar: Confirmed Bug description: The official Raspberry Pi touchscreen (the 7" model connected via the DSI port) does not operate when the KMS overlay is applied (as is the default on the Ubuntu Desktop for Raspberry Pi images). The display does operate on RaspiOS Bullseye, also running kernel 5.15, when the KMS overlay is used. Notably, the display does work on Ubuntu with no KMS overlay (legacy framebuffer), or with the FKMS ("fake" KMS) overlay. The symptom is simply no output at all on the display. Sometimes there is the initial "rainbow" screen of the start4.elf bootloader, but then nothing. Notably this is *slightly* different to the Impish 5.13 kernel. On thata version, the DSI display also failed with the KMS overlay, but in that case there was an initial flashing cursor (presumably at the start of the initrd, perhaps on a leftover framebuffer?) which then disappears before anything is printed. On 5.15 there's nothing after the "rainbow". The symptoms are the same on both armhf and arm64 images. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-raspi 5.15.0.1005.5 ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30 Uname: Linux 5.15.0-1005-raspi armv7l AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-1005-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Date: Wed Apr 27 10:04:10 2022 ImageMediaBuild: 20220419 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04d9:0006 Holtek Semiconductor, Inc. Wired Keyboard (78/79 key) [RPI Wired Keyboard 5] Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:33:F5:57 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait video=DSI-1:800x480@60,rotate=180 fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-1005-raspi N/A linux-backports-modules-5.15.0-1005-raspi N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: bcm2835_v4l2 bcm2835_isp vc_sm_cma bcm2835_codec bcm2835_mmal_vchiq snd_bcm2835 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1970603/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
As a workaround until the fix lands (and is subsequently back-ported to the jammy HWE kernel), Koba's test-kernel in comment 36 works nicely. However, please note that the test kernel is not signed and will require that you disable secure boot to try it (if it's enabled on your machine), which may or may not fit your circumstances. If you require secure boot to be enabled I'm afraid you'll need to wait a bit longer. If you don't require secure boot, then: * disable secure boot * grab all files from the link in comment 36 to a clean directory * sudo dpkg -i *.deb (from that directory) * (you likely don't actually need *all* of the packages, but rather than sorting out which you do / don't need it's easier to simply install the lot) * sudo reboot -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@Koba I can confirm the 5.19.9000-37-generic kernel from comment 36 fixes the issue for me as well, congratulations! I agree the 60Hz audio issue ought to be a separate report, but until that appears a quick side note to this one: my refresh rate is 60Hz and I have no issues with my audio but I wonder if that's also related to resolution. Specifically I'm on an old 1080p monitor so the lowest refresh rate I can drop to is 50Hz (and the highest ~72Hz), and neither seems to have any particularly noticeable effect on the audio output. I wonder if those having audio issues are running at a higher resolution, presumably 4K? -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
** Description changed: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. + + Currently known affected cards: + + * HD 7700 (comment 8) + * R9 290 (comment 21) + * RX 550 (LP: #2012141, and comment 27) + * RX 570 (mine) + * RX 580 (LP: #2009276, and comment 28) + * WX 3200 (comment 29) + * RX 6600 (LP: #2009542) + * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@duxeu To fill in a bit of background here, the AMD folks were emailed in the background and are of the same opinion. Personally, I'm not sure the bisect *did* identify that as the commit, but unfortunately bisection isn't an entirely straight-forward process when dealing with packages that have a ton of Ubuntu-specific patches on top of them (as the kernel naturally does). @kobako Are there any further test kernels to try? In the meantime I'll stick the currently affected list of cards at the top so new people coming to the bug can easily check against the list (though I have a feeling, looking at the list, it could be summarised as "pretty much all AMD GPUs"). -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2012141] Re: [22.04] After upgrade to 22.04.2, hdmi audio output is no longer detected
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 >From lspci.txt it appears your GPU is a Radeon RX 550, so this is almost certainly a duplicate of LP: #2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 & -37 (regression from -32) -- 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/2012141 Title: [22.04] After upgrade to 22.04.2, hdmi audio output is no longer detected Status in linux package in Ubuntu: Confirmed Bug description: Hi, since upgrade to Ubuntu 22.04.2, I have no longer HDMI audio input being detected. It doesn't show as an option in Sound settings and thus doesn't output audio to a monitor attached via HDMI. I noticed the following logs in dmesg: [5.466172] snd_hda_intel :08:00.1: Handle vga_switcheroo audio client [5.466174] snd_hda_intel :08:00.1: Force to non-snoop mode [5.466399] snd_hda_intel :0a:00.4: enabling device ( -> 0002) [5.468656] hdaudio hdaudioC0D0: no AFG or MFG node found [5.468672] snd_hda_intel :08:00.1: no codecs initialized The reason might be the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993884 I'm using AMD Ryzen 3900X. $ uname -a Linux adrian-desktop 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy Please let me know if I need to provide more information. Thanks, Adi --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian14268 F pulseaudio /dev/snd/pcmC1D1p: adrian14268 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-06 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=ce95ca9b-9845-4bf9-9323-5ed5327454d5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/26/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F37 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF37:bd12/26/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012141/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@koba I've tried each of the kernels in comment 25 and I'm afraid it rather refutes the theory that fdcc4c22b is the culprit: The latest vanilla kernel (#1) is "good"; HDMI audio works happily. That suggests (although not conclusively) that fdcc4c22b isn't the culprit as it presumably includes that commit. The latest vanilla kernel with fdcc4c22b reverted (#2) is also "good"; HDMI audio works, although I did note dmesg had an awful lot of preempt errors reported in it (which did not appear with the vanilla kernel above). Finally, just to put the nail in the coffin of fdcc4c22b being the faulty commit, the 5.19.0-35 kernel with fdcc4c22b reverted (#3) is "bad"; exhibits the original failure with HDMI audio being unavailable. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
** Description changed: + CLARIFICATION: Just to avoid any confusion for those coming to this bug + report; the "Jammy: invalid" status above does *not* mean that this bug + doesn't affect jammy -- it does, and the kernel team is aware of this. + All it reflects is that the fix has to go into the kinetic kernel + package which will then flow into the kernel-hwe package implicitly. + + [ Original Description ] + After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009815] Re: No HDMI audio anymore
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 & -37 (regression from -32) -- 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/2009815 Title: No HDMI audio anymore Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 Wayland 5.19.0-35-generic does not work 5.19.0-32-generic does work If following messages occures during boot, no HDMI audio : hdaudio hdaudioC1D0: no AFG or MFG node found snd_hda_intel :01:00.1: no codecs initialized No HDMI Audio does mean : Via lspci -nnk I get the following device : 01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:aae0] Subsystem: ASUSTeK Computer Inc. Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1043:aae0] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel But this device will neither be indicated via pavucontrol nor via audio settings (mainsettings). Before I did installed the Ubuntu 22.10 on my system, I did test the live system. It did work without problems. And two audio devices, that is what I expect, will be indicated in the audio settings (one of them, the given above via lspci -nnk, is necessary to have audio via HDMI) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1402 F wireplumber /dev/snd/seq:richard1399 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 9 10:11:41 2023 InstallationDate: Installed on 2023-03-04 (4 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=df59b1c2-c5b9-483d-b033-7c6b2264dc75 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. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4802:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MPRO:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009815/+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 2011334] Re: amdgpu HDMI audio device missing on kernel 5.15.0-35 / 5.19.0-35
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 I'm *reasonably* certain this is a duplicate of LP: #2009136 as that covers kernel 5.19.0-35. I don't think there *is* a 5.15.0-35, and the "reversion to 5.15.0-67" (which is the current 5.15 release) also suggests that this is limited to affecting the 5.19 releases, not the 5.15 releases. Anyway, marking this as a duplicate of the aforementioned bug for now but please do correct me if I'm wrong! ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 & -37 (regression from -32) -- 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/2011334 Title: amdgpu HDMI audio device missing on kernel 5.15.0-35 / 5.19.0-35 Status in linux package in Ubuntu: Incomplete Bug description: Multiple reports of amdgpu HDMI audio device becomes missing and the issue got fixed by reverting to 5.15.0-67 kernel https://askubuntu.com/questions/1457524/hdmi-audio-not-detected-after-update-for-amd-graphics https://askubuntu.com/questions/1457893/my-hdmi-display-port-audio-stopped-working-on-ubuntu-22-10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: unm2638 F pulseaudio /dev/snd/controlC0: unm2638 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-23 (1053 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200422) MachineType: Gigabyte Technology Co., Ltd. Z97X-SLI Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1db4cc4a-3e35-473c-9a5e-4b36d3282c60 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-05-05 (310 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-SLI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-SLI-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-SLI dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011334/+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 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@Timo ah I see, sorry for the noise! -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@bpl indeed -- I asked Timo if the targeting should be adjusted in comment 9 as I wasn't sure if the kernel team wanted to track this separately over in the hwe package, but given this bug was moved from that package this one I may as well just add jammy to the affected set. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Errr, let me try that again from root so it's actually got the caps output! ** Attachment added: "lspci.out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5653114/+files/lspci.out -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.15.9003-68-generic kernel in comment 16 is "good"; HDMI audio detected and working happily. I'm attaching the requested lspci output. ** Attachment added: "lspci.out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5653113/+files/lspci.out -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.19.9002-34-generic kernel in comment 14 is also "bad" -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.19.9001-34-generic kernel provided in comment 12 is also "bad" (same symptoms, same dmesg lines as seen in the -35 kernel) -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009032] Re: Kernel 5.19.0-35 killed HDMI audio for me
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 My apologies; I'm going to mark this as a duplicate of LP: #2009136 even though that bug was reported later as it's very likely the same issue (AMD-based card with HDMI audio output), and that seems to be where the kernel team are currently bisecting the issue. Sorry I didn't spot this one when reporting 2009136! ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- 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/2009032 Title: Kernel 5.19.0-35 killed HDMI audio for me Status in linux package in Ubuntu: Incomplete Bug description: On Kernel 5.19.0-32 everything is working fine. But when updating to Kernel 5.19.0-35, HDMI audio is no longer listed/working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009032/+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 2009287] Re: When using this kernel, the HDMI audio output dissapears
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- 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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: Confirmed Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009287/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.19.9000-34-generic kernel provided in comment 10 is "bad" (no HDMI audio present, same dmesg lines as seen in the -35 kernel) -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Hi Timo, this also affects jammy -- should I add that to the targeting, or is that to be handled separately? -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Looking through the growing list of duplicates, everyone has an AMD GPU so this is almost certainly an issue in that driver. The list of cards affected so far: * RX570 (mine) * RX6700 XT (from LP: #2009275) * RX580 (from LP: #2009276) * RX6600 (from LP: #2009542) I'm happy to post any additional logs / traces that would help debug this and/or test patched kernels (worth looking at the duplicates for additional logs too). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 2009276] Re: Audio Hdmi (Radeon rx580) not recognized
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009276 Title: Audio Hdmi (Radeon rx580) not recognized Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After kernel upgrade, from 5.19.0-32 to 5.19.0-35 the audio don't work. At boot appears the message: hdaudio_hdaudioC0D0: no AFG or MFG node found snd_hda-intel :26:00.1: no codecs initialized Processor: AMD® Ryzen 5 3600 6-core processor × 12 Graphic: AMD® Radeon rx 580 series OS Name: Ubuntu 22.04.2 LTS 64-bit GNOME version: 42.5 Graphic System: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:17:19 2023 InstallationDate: Installed on 2022-05-07 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009276/+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 2009542] Re: Can not select HDMI or Displayport as audio output device.
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009542 Title: Can not select HDMI or Displayport as audio output device. Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After I installed "linux-image-5.19.0-35-generic" package, I can not select HDMI or Displayport as audio output device in gnome setting. When I am using "linux-image-5.19.0-32-generic" package, I can select that. My PC also have S/PDIF as audio output device, I can select it. My environment is follows. Description: Ubuntu 22.04.2 LTS Release: 22.04 Graphics board: Radeon RX6600 Graphics driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009542/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "pactl-list-5.19.0-35" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651269/+files/pactl-list-5.19.0-35 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "pactl-list-5.19.0-32" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651268/+files/pactl-list-5.19.0-32 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "dmesg-5.19.0-35" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651267/+files/dmesg-5.19.0-35 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "dmesg-5.19.0-32" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651266/+files/dmesg-5.19.0-32 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 2009136] [NEW] No HDMI audio under 5.19.0-35 (regression from -32)
Public bug reported: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 1993120] Re: armhf kernel compiled with gcc-12 fails to boot on pi 3/2
Is there actually an issue in gcc-12 here? Looking at the patch Juerg linked to, it appears to be a kernel issue only? -- 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/1993120 Title: armhf kernel compiled with gcc-12 fails to boot on pi 3/2 Status in gcc-12 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Fix Released Status in gcc-12 source package in Kinetic: New Status in linux source package in Kinetic: Fix Committed Status in linux-raspi source package in Kinetic: Invalid Bug description: Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang on Pi 3 and 2. Seems to work fine on Pi 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1993120/+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 1989713] Re: Old start4.elf / fixup4.dat in 22.04
Marking linux-firmware-raspi2 invalid for now; will be used if we decide to backport to focal. Currently prepping an upload for ppa:waveform/firmware with a test updated firmware. If that works well, will upload to lunar then start SRU to kinetic and jammy. ** Also affects: linux-firmware-raspi2 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi2 (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-firmware-raspi (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: linux-firmware-raspi2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu Lunar) Status: Confirmed => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-firmware-raspi (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: linux-firmware-raspi (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-firmware-raspi (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware-raspi (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux-firmware-raspi (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux-firmware-raspi (Ubuntu Lunar) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: linux-firmware-raspi (Ubuntu Jammy) Milestone: None => ubuntu-22.04.2 ** Changed in: linux-firmware-raspi (Ubuntu Lunar) Milestone: None => ubuntu-23.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1989713 Title: Old start4.elf / fixup4.dat in 22.04 Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in linux-firmware-raspi source package in Jammy: Confirmed Status in linux-firmware-raspi2 source package in Jammy: Invalid Status in linux-raspi source package in Jammy: Invalid Status in linux-firmware-raspi source package in Kinetic: Confirmed Status in linux-firmware-raspi2 source package in Kinetic: Invalid Status in linux-raspi source package in Kinetic: Invalid Status in linux-firmware-raspi source package in Lunar: Confirmed Status in linux-firmware-raspi2 source package in Lunar: Invalid Status in linux-raspi source package in Lunar: Invalid Bug description: Hi there, there is the issue connected with "Initramfs unpacking failed: Decoding failed" error during Ubuntu boot. See https://github.com/raspberrypi/firmware/issues/1746 and https://github.com/raspberrypi/firmware/issues/1731. The Raspberry Pi have the update for start4.elf / fixup4.dat with fix it. Could you please include update for these files in new ubuntu release ASAP? Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/1989713/+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 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
** Tags added: foundations-todo -- 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/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+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 1990964] Re: FTBFS on kinetic
** Tags added: foundations-todo -- 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/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: In Progress Status in strace package in Ubuntu: New Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 1991254] [NEW] No HDMI sound output from alsa in server (no KMS)
Public bug reported: During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi armhf image, on a Raspberry Pi 4B, I noted that the HDMI "sound card" no longer appears in /proc/asound/cards; only the Headphones output (from the AUX socket on the board) appears. I checked with the current linux-raspi in the release pocket (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi), and both exhibit the same issue. On Kinetic: $ cat /proc/asound/cards 0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones On Jammy: $ cat /proc/asound/cards 0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1 bcm2835 HDMI 1 1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No HDMI sound output from alsa + No HDMI sound output from alsa in server (no KMS) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1991254 Title: No HDMI sound output from alsa in server (no KMS) Status in linux-raspi package in Ubuntu: New Bug description: During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi armhf image, on a Raspberry Pi 4B, I noted that the HDMI "sound card" no longer appears in /proc/asound/cards; only the Headphones output (from the AUX socket on the board) appears. I checked with the current linux-raspi in the release pocket (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi), and both exhibit the same issue. On Kinetic: $ cat /proc/asound/cards 0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones On Jammy: $ cat /proc/asound/cards 0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1 bcm2835 HDMI 1 1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1991254/+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 1826228] Re: api3a+ hang when reading /sys/devices/platform/soc/driver_override
** Changed in: linux-raspi2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826228 Title: api3a+ hang when reading /sys/devices/platform/soc/driver_override Status in linux-raspi2 package in Ubuntu: Invalid Bug description: I discovered this when running some tests on a core16 image with various rpi3 devices. Rpi3b, b+, cm3, rpi2, etc... don't have this problem, only rpi3a+. Kernel version: Linux localhost 4.4.0-1107-raspi2 #115-Ubuntu SMP Wed Apr 10 18:06:42 UTC 2019 armv7l armv7l armv7l GNU/Linux To reproduce, simply 'cat /sys/devices/platform/soc/driver_override' The process just hangs and cannot be killed. On other rpi devices, I just get this output immediately: (null) There was nothing in dmesg or syslog when it happened, no kernel crash, and I can still ssh into the system. The process that ran that command just silently hangs and can't be killed even with sudo kill -9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1826228/+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 1988838] [NEW] No console output on kinetic pi server images
Public bug reported: On kinetic pi server daily images with the 5.19 linux-raspi kernel (e.g. from http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/current/) there is no console output over HDMI. The "rainbow" boot screen appears as usual, but then remains while the system continues to boot and never switches to display the console. The system does still boot successfully, I can SSH into it, and console over serial still works but not over HDMI (testing on a Pi 3, and two revisions of the Pi 4). Adding either kms overlay (vc4-fkms-v3d or vc4-kms-v3d) to the boot configuration resolves this. Is it simply the case that future kernels are going to require a KMS overlay of some flavour or other to operate the console? If so, that's probably a good thing to some degree (it'll remove another difference between the pi server and desktop images), but ubuntu- release-upgrader will need to work to enforce that in the boot configuration for upgraders (and I'll need to tweak the gadget to ensure it's always included from now on). ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1988838 Title: No console output on kinetic pi server images Status in linux-raspi package in Ubuntu: New Bug description: On kinetic pi server daily images with the 5.19 linux-raspi kernel (e.g. from http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/current/) there is no console output over HDMI. The "rainbow" boot screen appears as usual, but then remains while the system continues to boot and never switches to display the console. The system does still boot successfully, I can SSH into it, and console over serial still works but not over HDMI (testing on a Pi 3, and two revisions of the Pi 4). Adding either kms overlay (vc4-fkms-v3d or vc4-kms-v3d) to the boot configuration resolves this. Is it simply the case that future kernels are going to require a KMS overlay of some flavour or other to operate the console? If so, that's probably a good thing to some degree (it'll remove another difference between the pi server and desktop images), but ubuntu-release-upgrader will need to work to enforce that in the boot configuration for upgraders (and I'll need to tweak the gadget to ensure it's always included from now on). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1988838/+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 1982627] Re: MT7612u wireless chipset not working on Raspberry Pi 400
Looks like this is one of the ones moved to the modules-extra package (this split is kernel specific, and wasn't done on the PC kernel which probably explains why this adapter works on your PC installation of Ubuntu Server). If you do the following: $ sudo apt install linux-modules-extra-raspi You should then be able to modprobe usbmon. I'll move the bug over to linux-raspi as it's technically a kernel issue. ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/1982627 Title: MT7612u wireless chipset not working on Raspberry Pi 400 Status in linux-firmware package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Bug description: I purchased the Alfa AWUS036ACM wireless adapter to use with my Raspberry Pi 400. The adapter works when using Raspberry Pi OS, but not when using "Ubuntu for Raspberry Pi" release 22.04. I have tested 64-bit variants for Ubuntu Desktop and Ubuntu Server, and the results are the same. I followed the Kernel Firmware Debugging steps, and included its output below. The LinuxWireless Debugging steps seem to only be appropriate if the wireless adapter is working to some capacity so the below output does not include those steps. I also attempted to follow the Kernel USB Debugging steps, but the commands do not seem appropriate for the Raspberry Pi 400. For example, `/proc/bus/usb` and `/sys/kernel/debug/usb/usbmon/` do not exist on the filesystem. As part of troubleshooting, I updated the bootloader for the Raspberry Pi 400 to version 507b2360 which was built on 2022-04-26. I also ran `sudo apt update` and `sudo apt full-upgrade`. Neither of these troubleshooting steps resolved the problem. On a separate note, I have another Ubuntu Server release 22.04 that is installed on dedicated hardware (not the "Ubuntu for Raspberry Pi" variant), and the wireless adapter does work on this machine. Raspberry Pi 400 Output $ sudo modprobe usbmon modprobe: FATAL: Module usbmon not found in directory /lib/modules/5.15.0-1012-raspi $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.2 Candidate: 20220329.git681281e4-0ubuntu3.2 Version table: *** 20220329.git681281e4-0ubuntu3.2 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages $ sudo udevadm control --log-priority debug $ tail -f /var/log/syslog Jul 22 20:56:03 ubuntu kernel: [ 533.687623] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd Jul 22 20:56:03 ubuntu kernel: [ 533.709177] usb 2-1: New USB device found, idVendor=0e8d, idProduct=7612, bcdDevice= 1.00 Jul 22 20:56:03 ubuntu kernel: [ 533.709203] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4 Jul 22 20:56:03 ubuntu kernel: [ 533.709214] usb 2-1: Product: Wireless Jul 22 20:56:03 ubuntu kernel: [ 533.709222] usb 2-1: Manufacturer: MediaTek Inc. Jul 22 20:56:03 ubuntu kernel: [ 533.709230] usb 2-1: SerialNumber: 0 Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device is queued (SEQNUM=4179, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[451]: Validate module index Jul 22 20:56:03 ubuntu systemd-udevd[451]: Check if link configuration needs reloading. Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device ready for processing (SEQNUM=4179, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[451]: Successfully forked off 'n/a' as PID 1330. Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Worker [1330] is forked for processing SEQNUM=4179. Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Processing device (SEQNUM=4179, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Failed to get watch handle, ignoring: No such file or directory Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'usb_id' Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1:1.0: Device is queued (SEQNUM=4180, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1:1.0: SEQNUM=4180 blocked by SEQNUM=4179 Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device is queued (SEQNUM=4181, ACTION=bind) Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: SEQNUM=4181 blocked by SEQNUM=4179 Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'hwdb --subsystem=usb'
[Kernel-packages] [Bug 1977764] Re: kernel modules "zstd" and "z3fold" missing.
** Also affects: ubuntu-seeds Importance: Undecided Status: New ** Changed in: ubuntu-seeds Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1980861] Re: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
I've finished some research with this on one of the larger Pis (a 400) for performance measurements, and a memory limited Pi (Zero 2W) for an idea of the impact on memory usage. First the performance side of things: the good news is it doesn't make anything worse, the bad news is it doesn't make them *much* better (unlike on the PC where it apparently makes a substantial difference). The biggest difference on the Pi 400 was a drop from 16s to 13s in the jammy release of Firefox's cold startup time. However, there was no difference at all in the warm startup time, and the difference in the cold startup time disappeared almost entirely when using the candidate version of Firefox with the lang pack fix (diff was 0.3s -- which I'd assume is essentially nothing given I was doing manual timing and thus the times are subject to my reaction time of ~0.2s). On the memory side of things I used a selection of 6 snaps installed on the Pi Zero 2W: mosquitto, node-red, micropython, node, ruby, and lxd (a combination of relatively common and fairly IoT specific snaps) which is probably about as much as anyone could reasonably expect to install and run on a half-gig system. I measured the system after a fresh boot running only default services, and otherwise idle on the Raspberry Pi jammy (22.04 LTS) arm64 server image. The arm64 architecture was selected partly for the wider availability of snaps (there are very few built for armhf) and partly because memory effects were more likely to be pronounced on this architecture. Over the course of 30 minutes, everything from /proc/meminfo was dumped to an SQLite database, first under the current release of the kernel (5.15.0-1011-raspi), then under a re-built version with CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU enabled (and CONFIG_SQUASHFS_DECOMP_SINGLE disabled). MemAvailable stayed reasonably stable across each run, and showed a median ~12MB less on the MULTI_PERCPU kernel than on the SINGLE kernel, suggesting that each snap's mount occupied somewhere in the region of 2MB more memory under the MULTI_PERCPU kernel. Other statistics were less clear cut: no significant difference in kernel stack, and MemFree actually showed the opposite (but this should probably be ignored as it doesn't exclude evictable pages like the disk cache, and the kernel has a duty to minimize it so it will typically fall predictably on a freshly booted system meaning that differences in the start time of a measurement run will lead to an irrelevant delta). The kernel slab measure showed a interesting (stable, median) 6MB increase from the SINGLE to MULTI_PERCPU which may account for some of the extra memory being used. Conclusion: * There's some memory loss but it's small enough that it shouldn't significantly impact even tightly constrained systems like the Zero 2W * The performance gains are likely minimal under ARM. As such, were ARM the only set of architectures being considered I'd probably recommend against this * However, the performance gains on the x86 family are significant so for me this comes down to a "lack of harm" judgment: If this can be enabled on amd64 and disabled on armhf+arm64 then that would probably be the ideal situation. However, I'm mindful that any delta means extra maintenance work, and an extra chance for errors. Given the mixed situation on ARM (minor performance gain, minor memory loss), I'd recommend simply enabling this option across the board. -- 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/1980861 Title: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: The snapd/desktop/advocacy team are investigating the startup performance of running snaps. While doing this and comparing various distros (fedora, opensuse, ubuntu) on Igors reference hardware we noticed that fedora is substantially faster at starting snaps. After some research it turns out that they use the CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y option when we use CONFIG_SQUASHFS_DECOMP_SINGLE. I build^Whacked a test kernel in my ppa:mvo/tmp PPA that just changes this one option (https://paste.ubuntu.com/p/NvS4GQjnSp/) and with that the first run firefox startup went from 15s to 6s (!) on Igors reference hardware. Given the dramatic performance improvements we would like to get this option switched. However we need to be careful and double check that the results from https://bugs.launchpad.net/snappy/+bug/1636847 are no longer an issue - back in 2016 the kernel team swtich to _DECOMP_SINGLE because just mounting a snap would use up 131Mb or memory(!). To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1980861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1980861] Re: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
I'm hoping to look into the effects of MULTI_PERCPU on the smaller Pi platforms (in particular the Pi Zero 2 and 3A+ which each have 512MB of RAM and, with the arm64 arch, typically have ~250MB free at runtime). Unfortunately building a local version of the linux-raspi package (just naively with sbuild) has thus far defeated me, but if I can get a version with the relevant config I'll run through some tests. -- 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/1980861 Title: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: The snapd/desktop/advocacy team are investigating the startup performance of running snaps. While doing this and comparing various distros (fedora, opensuse, ubuntu) on Igors reference hardware we noticed that fedora is substantially faster at starting snaps. After some research it turns out that they use the CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y option when we use CONFIG_SQUASHFS_DECOMP_SINGLE. I build^Whacked a test kernel in my ppa:mvo/tmp PPA that just changes this one option (https://paste.ubuntu.com/p/NvS4GQjnSp/) and with that the first run firefox startup went from 15s to 6s (!) on Igors reference hardware. Given the dramatic performance improvements we would like to get this option switched. However we need to be careful and double check that the results from https://bugs.launchpad.net/snappy/+bug/1636847 are no longer an issue - back in 2016 the kernel team swtich to _DECOMP_SINGLE because just mounting a snap would use up 131Mb or memory(!). To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1980861/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
Doh -- that one's my fault; included it in the kernel command line and completely forgot to include a patch in ubuntu-raspi-settings to add it to the set of modules for initramfs-tools to include in the initrd. The workaround for now: $ sudo -i # echo zstd >> /etc/initramfs-tools/modules # echo z3fold >> /etc/initramfs-tools/modules # update-initramfs -u I'll try and get this added to ubuntu-raspi-settings shortly. ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Kinetic) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: initramfs-tools (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** No longer affects: initramfs-tools (Ubuntu) ** No longer affects: initramfs-tools (Ubuntu Kinetic) ** No longer affects: initramfs-tools (Ubuntu Jammy) ** Changed in: ubuntu-settings (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-settings (Ubuntu Kinetic) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in linux-raspi package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: New Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: New Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+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 1931001] Re: Soft lockup due to interrupt storm from smbus
Also affects my Acer Aspire TravelMate Spin B118 on Ubuntu 22.04. The i2c-i801 workaround from comment 14 above (https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.11/+bug/1931001/comments/14) works nicely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: Soft lockup due to interrupt storm from smbus Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1931001/+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 1918583] Re: Switch to libgpiod and disable CONFIG_GPIO_SYSFS
Now that jammy's out (which still includes CONFIG_GPIO_SYSFS), let's at least consider this for kinetic. I would suggest it would sensible to at least try this in an interim release prior to the next LTS. There will undoubtedly be things that break, but it's probably better to be aware of how much breakage potential there is around this (and what it would take to encourage users over to libgpiod, or if that's practical in all cases). I'll add linux-raspi to the target list as that's probably the kernel flavour that this will impact most and target to kinetic. ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Tags added: rls-kk-incoming -- 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/1918583 Title: Switch to libgpiod and disable CONFIG_GPIO_SYSFS Status in linux package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: New Status in linux source package in Kinetic: Confirmed Status in linux-raspi source package in Kinetic: New Bug description: Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153 debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y However, this interface got deprecated for removal: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0910d72afc69b25703f7be9bf7d13f18937a478 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b4b76e73dc1486955d93f47276134 "This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for removal in 2020." https://www.kernel.org/doc/Documentation/gpio/sysfs.txt "THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED." libgpiod and the use of a character file-based interface is a replacement to the sysfs interface: https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ Those two interfaces cannot be used interchangeably and working via libgpiod is not possible when the sysfs interface is used: sudo gpioget gpiochip0 12 gpioget: error reading GPIO values: Device or resource busy sudo gpioinfo | grep 12 line 12: "GPIO12" "sysfs" input active-high [used] It would be good to switch to a newer interface since the old one does not get new features and there is no way to switch to libgpiod besides recompiling the kernel with "CONFIG_GPIO_SYSFS=n" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918583/+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 1889637] Re: Raspberry Pi 3B hangs - dev_pm_opp_set_rate: failed to find current OPP, Failed to get throttled, Failed to change plib frequency; mmc timeout waiting for hardware
I'm afraid if you're getting undervolt warnings that's almost certainly the cause of any serious issues like kernel hangs. The lightning bolt not being visible simply means that the undervolt condition is not sustained, but nevertheless any such warnings indicate that your power supply is dropping below 4.7V (usually under load). Before investigating this further, we'd need to eliminate that as a potential cause. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1889637 Title: Raspberry Pi 3B hangs - dev_pm_opp_set_rate: failed to find current OPP, Failed to get throttled, Failed to change plib frequency; mmc timeout waiting for hardware interrupt Status in linux package in Ubuntu: Incomplete Bug description: ### uname -a (64-bit ARM, official image): `Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux` ### LSB release (Ubuntu *Server*, focal): Description: Ubuntu 20.04.1 LTS ### Interesting packages installed - zfs-dkms (with initramfs support) @ 0.8.3-1ubuntu12.2 * spl-dkms @ 0.8.3-1ubuntu12.2 - dphys-swapfile ### Hardware model: Raspberry Pi 3 Model B - 32 GiB SD card with root partition * had a swap partition; now unused * migrated to dphys-swapfile - Attached 32 GiB USB stick as zpool for storage (not root FS) - Current PSU reportedly outputs 2.4A supply for the Pi * Still have occasional undervolt warnings (formally requires 2.5A) * Lightning indicator not present however - Connected over wireless networking ## Issue - When under significant computational load at some point, the machine appears to freeze. * I usually log in in a headless manner via ssh, so externally the machine is frozen and I need to pull the power cable - Connectig the HDMI monitor the following messsages appear, in various orders each time: ```terminal cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 9,223,372,036,854,775,698 ({illegible on my photograph, presumably -110}) hwmon hwmon1: Failed to get throttled (-110) raspberrypi-clk firmware clocks: Failed to change plib frequency: -110 mmc0: timeout waiting for hardware interrupt # mmc0 would be the root partition ### ... typically later on in the output rcu: INFO: rcu_sched detected stalls on CPU/tasks rcu: $1-...0: (1 GPs behind) idle=.../1/0x4{more 0s...}02 softirq=66377/66378 {or 26106/26107} fqs={this value varies} INFO: task kworker/{...} blocked for more than 120 seconds TAINTED: PWC OE 5.4.0-1015-raspi #15-ubuntu watchdog: BUG: soft lockup - CPU #3 stuck for 22s! ``` The OPP frequency above looks to me like it may be the cause of the issue, I have added the commas myself to the output but it would appear to be a rubbish value; [this](https://lkml.org/lkml/2020/7/24/683) mailing list archive I found whilst searching for terms found in the messages appears to back up my belief that we should be seeing a sensible CPU frequency here, expressed in integer Hz; the above would be 9.2 EHz assuming Hertz are the base unit, higher still if it's k/M/GHz etc. My most sensible guess is this value has been brought up somewhere as garbage, and understandably the system fails to scale the clock speed, with the resultant crashes presumably due to this. Beyond this point, there is no kernel panic, however the machine locks up externally; does not respond to USB keyboard NumLock and is invisible on the network, with more and more errors gradually being output to the console via the HDMI display; the most notable being the SD card is not responding Just before encountering this issue I had added a swap aprtition, to the SD card, as I had none by default and the system seemed to be hanging when it presumably was sending bad_allocs to userland processes as it failed to allocate memory. As the SD card was mentioned, I have tried a variety of power supplies (as I was getting several undervolt warnings) and eventually removed the swap partition and used a swapfile with `dphys-swapfile` knowing that the way the Pi accesses the SD card is somewhat different from a typical machine. However, neither of these two seems to have resolved the issue, giving further evidence that the frequency scaling may well be the primary issue and the rest is simply the carnage that ensues. ## Steps to Reproduce - Seems to happen sporadically when the machine is under stress, within 5-25 minutes - Currently I am trying to set up a rootless docker compose file * Attempting to pull the images eventually leads to the issue * The images are being downloaded to the zpool on the USB stick and *not* the SD card - The system seems to hang initially waiting on the SDcard to
[Kernel-packages] [Bug 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached
I've been unable to replicate this so far; tried with four different USB-SATA cables attaching boot storage to USB3 on a Pi 4B and a Pi 400; wifi worked happily in each case. Given this was expired for Eoan (a couple of years ago) I'll close this as invalid for now; please re-open if this is still an issue. ** Changed in: linux-raspi2 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861338 Title: RPI4 wifi unreliable when usb3 storage is attached Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Expired Bug description: On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage device to one of the 2x usb3 ports (the ones closest to the ethernet port), wifi will sudden stop working. If you unplug the usb stick while running a ping, it will usually start working again almost instantaneously. Kernel version I have is: 5.3.0-1017-raspi2 and I've confirmed this happens on both armhf and arm64 The only thing I found in journalctl that looks suspicious is this, but it seems to have happened before plugging in the usb stick: Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from /dev/random: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+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 1969689] Re: USB devices not detected on CM4
Argh, I'm an idiot -- had the flashing cable plugged into the micro-USB while the keyboard was *also* plugged into the USB-A sockets (which I knew doesn't work and apparently missed when originally debugging this). Closing as invalid. ** Changed in: linux-raspi (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Kinetic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1969689 Title: USB devices not detected on CM4 Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Jammy: Invalid Status in linux-raspi source package in Kinetic: Invalid Bug description: USB devices are not working on the CM4. When running `lsusb` the hub is detected, but devices are not. ``` ubuntu@ubuntu:~$ sudo dmesg | egrep -i "dwc2|usb" [0.151915] usbcore: registered new interface driver usbfs [0.151976] usbcore: registered new interface driver hub [0.152047] usbcore: registered new device driver usb [1.125855] usbcore: registered new interface driver lan78xx [1.125926] usbcore: registered new interface driver smsc95xx [1.125965] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.126070] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [1.126318] uhci_hcd: USB Universal Host Controller Interface driver [1.765785] usb_phy_generic phy: supply vcc not found, using dummy regulator [1.864470] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator [1.864674] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator [1.916752] dwc2 fe98.usb: DWC OTG Controller [1.916788] dwc2 fe98.usb: new USB bus registered, assigned bus number 1 [1.916822] dwc2 fe98.usb: irq 36, io mem 0xfe98 [1.917028] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 [1.917040] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.917048] usb usb1: Product: DWC OTG Controller [1.917055] usb usb1: Manufacturer: Linux 5.15.0-1005-raspi dwc2_hsotg [1.917062] usb usb1: SerialNumber: fe98.usb [1.917627] hub 1-0:1.0: USB hub found [7.831293] usbcore: registered new interface driver brcmfmac ``` @waveform was able to confirm the issue. The line `dtoverlay=dwc2,dr_mode=host` is present in config.txt. We suspect this to be a dtb/kernel issue. This is happening on both armhf and arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1969689/+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 1970603] [NEW] DSI touchscreen not working with KMS under 5.15
Public bug reported: The official Raspberry Pi touchscreen (the 7" model connected via the DSI port) does not operate when the KMS overlay is applied (as is the default on the Ubuntu Desktop for Raspberry Pi images). The display does operate on RaspiOS Bullseye, also running kernel 5.15, when the KMS overlay is used. Notably, the display does work on Ubuntu with no KMS overlay (legacy framebuffer), or with the FKMS ("fake" KMS) overlay. The symptom is simply no output at all on the display. Sometimes there is the initial "rainbow" screen of the start4.elf bootloader, but then nothing. Notably this is *slightly* different to the Impish 5.13 kernel. On thata version, the DSI display also failed with the KMS overlay, but in that case there was an initial flashing cursor (presumably at the start of the initrd, perhaps on a leftover framebuffer?) which then disappears before anything is printed. On 5.15 there's nothing after the "rainbow". The symptoms are the same on both armhf and arm64 images. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-raspi 5.15.0.1005.5 ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30 Uname: Linux 5.15.0-1005-raspi armv7l AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-1005-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Date: Wed Apr 27 10:04:10 2022 ImageMediaBuild: 20220419 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04d9:0006 Holtek Semiconductor, Inc. Wired Keyboard (78/79 key) [RPI Wired Keyboard 5] Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:33:F5:57 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait video=DSI-1:800x480@60,rotate=180 fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-1005-raspi N/A linux-backports-modules-5.15.0-1005-raspi N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: bcm2835_v4l2 bcm2835_isp vc_sm_cma bcm2835_codec bcm2835_mmal_vchiq snd_bcm2835 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug jammy raspi-image staging uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1970603 Title: DSI touchscreen not working with KMS under 5.15 Status in linux-raspi package in Ubuntu: New Bug description: The official Raspberry Pi touchscreen (the 7" model connected via the DSI port) does not operate when the KMS overlay is applied (as is the default on the Ubuntu Desktop for Raspberry Pi images). The display does operate on RaspiOS Bullseye, also running kernel 5.15, when the KMS overlay is used. Notably, the display does work on Ubuntu with no KMS overlay (legacy framebuffer), or with the FKMS ("fake" KMS) overlay. The symptom is simply no output at all on the display. Sometimes there is the initial "rainbow" screen of the start4.elf bootloader, but then nothing. Notably this is *slightly* different to the Impish 5.13 kernel. On thata version, the DSI display also failed with the KMS overlay, but in that case there was an initial flashing cursor (presumably at the start of the initrd, perhaps on a leftover framebuffer?) which then disappears before anything is printed. On 5.15 there's nothing after the "rainbow". The symptoms are the same on both armhf and arm64 images. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-raspi 5.15.0.1005.5 ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30 Uname: Linux 5.15.0-1005-raspi armv7l AlsaVersion: Advanced Linux
[Kernel-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
** Changed in: ubuntu-meta (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-image (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1954757] Re: Missing overlays/README
** Changed in: flash-kernel (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1954757 Title: Missing overlays/README Status in flash-kernel package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: Fix Released Status in linux-raspi source package in Hirsute: Won't Fix Status in linux-raspi source package in Impish: Fix Released Bug description: [ Impact ] overlays/README is used by the 'dtoverlay' command to display info on available overlays and params. [ Test Case ] $ apt install libraspberrypi-bin $ dtoverlay -h uart0 * Help file not found With the README present: $ dtoverlay -h uart0 Name: uart0 Info: Change the pin usage of uart0 Usage: dtoverlay=uart0,= Params: txd0_pinGPIO pin for TXD0 (14, 32 or 36 - default 14) rxd0_pinGPIO pin for RXD0 (15, 33 or 37 - default 15) pin_funcAlternative pin function - 4(Alt0) for 14&15, 7(Alt3) for 32&33, 6(Alt2) for 36&37 [ Where Problems Could Occur ] The output of the `dtoverlay` could be wrong but it's only informational so should have no negative impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1954757/+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 1900665] Re: Use the upstream dwc2 driver on arm64
** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: linux-raspi (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-raspi (Ubuntu Impish) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1900665 Title: Use the upstream dwc2 driver on arm64 Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Focal: Won't Fix Status in linux-raspi source package in Groovy: Won't Fix Status in linux-raspi source package in Hirsute: Won't Fix Status in linux-raspi source package in Impish: Fix Released Status in linux-raspi source package in Jammy: Fix Released Bug description: We currently use the dwc_otg driver from raspberrypi on 5.4 and 5.8 armhf and arm64 kernels. That driver supports FIQ interrupt handling (presumable for better performance) but lacks the maintenance and bug fixing of the vanilla upstream dwc driver. Turns out that FIQ handling is disabled in the dwc_otg driver on arm64 so it makes little sense to use that driver on arm64. In fact, upstream raspberrypi recommends to use the dwc2 driver on arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1900665/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop
Closing as we're now using "full" KMS on all supported desktops ** Changed in: linux-raspi2 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in PulseAudio: Unknown Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Invalid Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1899953/+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 1964591] [NEW] Move cdc-acm from modules-extra for embedded serial support
Public bug reported: Plugging in a Raspberry Pi Pico board (or several other MCU-based boards) results in the serial console /dev/ttyACM0 appearing on the Ubuntu PC desktop, but not on the Ubuntu Pi Desktop as the cdc_acm is currently in modules-extra. If there's not too many dependencies involved, it might be worth moving this over to the standard modules package just to make it a bit easier to work with Picos (and other MCUs) from a Pi. ** Affects: linux-raspi (Ubuntu) Importance: Low Status: New ** Changed in: linux-raspi (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1964591 Title: Move cdc-acm from modules-extra for embedded serial support Status in linux-raspi package in Ubuntu: New Bug description: Plugging in a Raspberry Pi Pico board (or several other MCU-based boards) results in the serial console /dev/ttyACM0 appearing on the Ubuntu PC desktop, but not on the Ubuntu Pi Desktop as the cdc_acm is currently in modules-extra. If there's not too many dependencies involved, it might be worth moving this over to the standard modules package just to make it a bit easier to work with Picos (and other MCUs) from a Pi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1964591/+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 1959452] Re: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64
This sounds more like it may be a pi-kernel or pi-gadget issue; I've added the linux-raspi package (from which the pi-kernel derives), but I don't think there's a project I can add for the gadget. However, I'll take a look at this from the gadget perspective. ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1959452 Title: 8GB Raspberry Pi 4 shows only 1 GB memory with Core20 arm64 Status in Snappy: New Status in linux-raspi package in Ubuntu: New Bug description: I installed Ubuntu Core 20 (Raspberry Pi4 arm64). The RaspberryPI has 8 GB memory but in Ubuntu-Core, only 1 GB is visible: toabctl@ubuntu:~$ sudo snap list Name VersionRevTracking Publisher Notes core20 20220114 1332 latest/stable canonical✓ base pi 20-1 97 20/stable canonical✓ gadget pi-kernel 5.4.0-1050.56 38720/stable canonical✓ kernel snapd 2.54.2 14553 latest/stable canonical✓ snapd toabctl@ubuntu:~$ sudo uname -a Linux ubuntu 5.4.0-1050-raspi #56-Ubuntu SMP PREEMPT Thu Jan 13 13:09:35 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux toabctl@ubuntu:~$ sudo cat /proc/meminfo MemTotal: 929960 kB $ sudo cat /proc/cmdline coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:640x480M@60 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=ttyS0,115200 elevator=deadline rng_core.default_quality=700 vt.handoff=2 quiet splash quiet splash snapd_recovery_mode=run snapd_recovery_system=20210630 panic=-1 systemd.gpt_auto=0 rd.systemd.unit=basic.target To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1959452/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
Hmmm, I wonder if this is in the seeds, given we *finally* got around to using the platform seeds to build the impish image (the intention was to do this in hirsute, and they were ready but for some reason they were never activated on that release). Ah ha! Here's the culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/raspi-common Now I wonder why that was added ... https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/commit/raspi- common?id=66ab1060453f5cdc8db8af901910282de20411bc Ohhh. I wonder if this is required to grow the partition on the desktop images. Those don't use cloud-init at all, instead there's a "x-systemd.growfs" tag in the fstab, but perhaps this package was required to operate that? I thought that was systemd-growfs though... Either way, it seems like something that could be added to the desktop seed specifically instead of the raspi-common seed. ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: cloud-init (Ubuntu) Assignee: Dave Jones (waveform) => (unassigned) ** Changed in: cloud-init (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1954757] Re: Missing overlays/README
** Changed in: flash-kernel (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1954757 Title: Missing overlays/README Status in flash-kernel package in Ubuntu: New Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: Fix Committed Status in linux-raspi source package in Hirsute: Fix Committed Status in linux-raspi source package in Impish: Fix Committed Bug description: [ Impact ] overlays/README is used by the 'dtoverlay' command to display info on available overlays and params. [ Test Case ] $ apt install libraspberrypi-bin $ dtoverlay -h uart0 * Help file not found With the README present: $ dtoverlay -h uart0 Name: uart0 Info: Change the pin usage of uart0 Usage: dtoverlay=uart0,= Params: txd0_pinGPIO pin for TXD0 (14, 32 or 36 - default 14) rxd0_pinGPIO pin for RXD0 (15, 33 or 37 - default 15) pin_funcAlternative pin function - 4(Alt0) for 14&15, 7(Alt3) for 32&33, 6(Alt2) for 36&37 [ Where Problems Could Occur ] The output of the `dtoverlay` could be wrong but it's only informational so should have no negative impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1954757/+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 1944541] Re: tvservice fails
This is indeed down to the (deliberately) outdated userland package. While this should be fixed for Jammy, the older series are a trickier prospect as bumping the userland version will remove mmal supported on arm64 (this is also the case for Jammy, but libcamera is intended to be the replacement for the legacy camera utilities there). I'll leave the targetting on the older series for now, pending a decision on whether it's possible to backport a specific patch for tvservice. ** No longer affects: linux-raspi (Ubuntu) ** Also affects: raspberrypi-userland (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: linux-raspi (Ubuntu Focal) ** No longer affects: linux-raspi (Ubuntu Hirsute) ** No longer affects: linux-raspi (Ubuntu Impish) ** Changed in: raspberrypi-userland (Ubuntu Jammy) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1944541 Title: tvservice fails Status in raspberrypi-userland package in Ubuntu: New Status in raspberrypi-userland source package in Focal: New Status in raspberrypi-userland source package in Hirsute: New Status in raspberrypi-userland source package in Impish: New Status in raspberrypi-userland source package in Jammy: New Bug description: $ sudo tvservice -s vchi_msg_dequeue -> -1(90) state 0x1 [TV is off] yields: [ 39.097720] vchiq: header 8000110d0f68: bufsize 10 < size 34 [ 39.103958] [ cut here ] [ 39.108725] invalid size [ 39.111398] WARNING: CPU: 2 PID: 2233 at drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c:952 vchiq_ioc_dequeue_message+0x180/0x2c0 [ 39.124567] Modules linked in: cmac algif_hash algif_skcipher af_alg bnep hci_uart btqca btrtl btbcm btintel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic bcm2835_codec(CE) ecc bcm2835_v4l2(CE) brcmfmac bcm2835_isp(CE) bcm2835_mmal_vchiq(CE) brcmutil v4l2_mem2mem snd_bcm2835(CE) videobuf2_vmalloc videobuf2_dma_contig cfg80211 videobuf2_memops snd_pcm videobuf2_v4l2 videobuf2_common snd_timer videodev raspberrypi_hwmon snd bcm2835_gpiomem vc_sm_cma(CE) mc rpivid_mem uio_pdrv_genirq uio nvmem_rmem sch_fq_codel drm ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear dwc2 crct10dif_ce spidev roles udc_core xhci_pci xhci_pci_renesas phy_generic aes_arm64 [ 39.197843] CPU: 2 PID: 2233 Comm: tvservice Tainted: G C E 5.11.0-1009-raspi #10+21.10.1-Ubuntu [ 39.207903] Hardware name: Raspberry Pi 4 Model B Rev 1.2 (DT) [ 39.213817] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 39.219909] pc : vchiq_ioc_dequeue_message+0x180/0x2c0 [ 39.225125] lr : vchiq_ioc_dequeue_message+0x180/0x2c0 [ 39.230334] sp : 800010e53c70 [ 39.233690] x29: 800010e53c70 x28: 46e3ce150f80 [ 39.239079] x27: x26: [ 39.244467] x25: x24: 8000110d0f68 [ 39.249855] x23: 8000110cd194 x22: 800010e53d48 [ 39.255243] x21: 0034 x20: 46e3c516e800 [ 39.260632] x19: 46e3c516f800 x18: 0030 [ 39.266019] x17: x16: [ 39.271406] x15: x14: 800090e53957 [ 39.276793] x13: 0006 x12: 80001002d000 [ 39.282181] x11: ad7c14e60f70 x10: 0b10 [ 39.287569] x9 : ad7c1400e418 x8 : 46e3ce151af0 [ 39.292957] x7 : 035f x6 : ad7c1548e000 [ 39.298345] x5 : x4 : 46e47b7bc948 [ 39.303731] x3 : 46e47b7cccf0 x2 : [ 39.309118] x1 : x0 : 46e3ce150f80 [ 39.314506] Call trace: [ 39.316981] vchiq_ioc_dequeue_message+0x180/0x2c0 [ 39.321841] vchiq_ioctl+0x7f4/0xdac [ 39.325464] __arm64_sys_ioctl+0xb4/0x100 [ 39.329530] el0_svc_common.constprop.0+0x88/0x220 [ 39.334392] do_el0_svc+0x30/0xa0 [ 39.337750] el0_svc+0x28/0x70 [ 39.340846] el0_sync_handler+0x1a4/0x1b0 [ 39.344910] el0_sync+0x17c/0x180 [ 39.348268] ---[ end trace b26bb2281d792cc5 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raspberrypi-userland/+bug/1944541/+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 1950214] Re: raspi 64 bit Impish image can't 'apt upgrade' without adding swap on pi zero 2
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-firmware (Ubuntu) -- 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/1950214 Title: raspi 64 bit Impish image can't 'apt upgrade' without adding swap on pi zero 2 Status in initramfs-tools package in Ubuntu: New Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950214/+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 1947601] Re: Cannot start docker container on ubuntu 21.10 server for raspberry pi
** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1947601 Title: Cannot start docker container on ubuntu 21.10 server for raspberry pi Status in linux-raspi package in Ubuntu: Invalid Bug description: Using the Ubuntu image for Raspberry Pi from here: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled- server-arm64+raspi.img.xz After installing the docker.io package, I cannot start a docker container. Example: $ sudo docker run --rm hello-world docker: Error response from daemon: failed to create endpoint pensive_greider on network bridge: failed to add the host (veth2102512) <=> sandbox (veth4fb66df) pair interfaces: operation not supported. This was working in the previous ubuntu release for 64 bit raspberry pi, 21.04. This problem is caused by the linux kernel shipped for ubuntu 21.10 for 64 bit raspberry pi, see post #14. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947601/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop
Worth noting that this issue only appears to occur when the fkms ("fake" KMS) overlay is in use on the Ubuntu Desktop for Raspberry Pi images. Under the kms ("full" KMS) overlay, the audio is fine. While kms is indeed the default overlay, it is likely (due to LP: #1946368 on impish) that many may be using fkms as a workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in PulseAudio: Unknown Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1899953/+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 1946368] [NEW] HDMI output freezes under current/proposed impish kernels
Public bug reported: Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels for the Ubuntu Pi pre-installed desktop impish release, the HDMI output occasionally freezes. A known workaround at this time is to change the following line in /boot/firmware/config.txt: dtoverlay=vc4-kms-v3d To the following: dtoverlay=vc4-fkms-v3d In other words, to use the "fake" KMS overlay (fkms) instead of the "full" KMS overlay (kms). I've been unable to determine a reliable method of guaranteeing a freeze, but it appears to occur much more readily when video playback is occurring, and when other interactions (especially moving windows around, minimizing, restoring) occurs simultaneously. Display suspend also periodically causes the same hang, which made me suspect this might be related to #1944397 but it appears that had a separate cause (now resolved). The following dmesg outputs have been observed immediately after the display hang; this one from 1007.8: [ 513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] co mmit wait timed out [ 513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:76:crtc-3] flip_ done timed out [ 524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:205:plane-25 ] commit wait timed out [ 534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out [ 534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit [ 534.250685] [ cut here ] [ 534.250701] refcount_t: underflow; use-after-free. [ 534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 refcount_dec_not_one+0xa0/0xbc [ 534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg hci_uart btqca btrtl btbcm btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth snd_compress snd_bcm2835(C) snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi snd_seq_midi_event bcm2835_codec(C) bcm 2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq videobuf2_common videodev snd_seq_devi ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem rpivid_mem uio_pdrv_genirq uio sch_fq_ codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon zstd_compress hid_generic usbhid raid 6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles udc_core gpu_sched crct10dif_ce i2c_ brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci xhci_pci_renesas sysfillrect sysimgbl t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64 [ 534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: GWC 5.13.0-1007-raspi #8-Ubuntu [ 534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT) [ 534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm] [ 534.251239] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 534.251248] pc : refcount_dec_not_one+0xa0/0xbc [ 534.251257] lr : refcount_dec_not_one+0xa0/0xbc [ 534.251265] sp : 8000118cbb50 [ 534.251269] x29: 8000118cbb50 x28: 6cf7ee894400 x27: 6cf80502e000 [ 534.251285] x26: 6cf80502e000 x25: 0006 x24: 6cf7ee94c500 [ 534.251300] x23: a94dff246018 x22: 6cf833068880 x21: 6cf805027c80 [ 534.251314] x20: 6cf88ead75ac x19: 6cf88ead7400 x18: [ 534.251328] x17: x16: a94e0a243314 x15: [ 534.251342] x14: x13: 0030 x12: 800010035000 [ 534.251356] x11: a94e0b30dfd0 x10: f000 x9 : a94e09d09f54 [ 534.251370] x8 : efff x7 : a94e0b30dfd0 x6 : [ 534.251384] x5 : 6cf8b799f948 x4 : x3 : 0027 [ 534.251397] x2 : x1 : x0 : 6cf800abec80 [ 534.251411] Call trace: [ 534.251416] refcount_dec_not_one+0xa0/0xbc [ 534.251424] vc4_bo_dec_usecnt+0x2c/0x120 [vc4] [ 534.251473] vc4_cleanup_fb+0x3c/0x4c [vc4] [ 534.251518] drm_atomic_helper_cleanup_planes+0x74/0xa0 [drm_kms_helper] [ 534.251604] vc4_atomic_commit_tail+0x24c/0x36c [vc4] [ 534.251648] commit_tail+0xac/0x190 [drm_kms_helper] [ 534.251723] drm_atomic_helper_commit+0x168/0x380 [drm_kms_helper] [ 534.251796] drm_atomic_commit+0x58/0x70 [drm] [ 534.251936] atomic_remove_fb+0x2a8/0x2f4 [drm] [ 534.252073] drm_framebuffer_remove+0x164/0x18c [drm] [ 534.252209] drm_mode_rmfb_work_fn+0x50/0x70 [drm] [ 534.252346] process_one_work+0x200/0x4d0 [ 534.252359] worker_thread+0x2c8/0x470 [ 534.252367] kthread+0x12c/0x140 [ 534.252374] ret_from_fork+0x10/0x3c [
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
@sil2100 sorry - that's my fault for skimming this (and the breaks: bit too -- that's actually not necessary as the backport re-instates the postinst installing the binaries to the boot partition; the breaks was there as later releases ditched the postinst and passed the responsibility for copying u-boot to flash-kernel). I'll work with jawn- smith to get this fixed up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: New Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Fix Committed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+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 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
** Changed in: xwayland (Ubuntu Hirsute) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen Status in linux-raspi package in Ubuntu: Invalid Status in xwayland package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Invalid Status in xwayland source package in Groovy: Confirmed Status in linux-raspi source package in Hirsute: Invalid Status in xwayland source package in Hirsute: Invalid Bug description: It is the same bug already described here: https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and- mouse-on-raspberry-pi-4b-with-ubuntu-20-10 My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired). How I could reproduce the mentioned crash: - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes - After five minutes, screen will turn black - If you move the mouse then, screen will be back again but frozen (mouse/keyboard not working). - restarting gdm.service via ssh is possible: sudo systemctl restart gdm.service - restarting it via Alt+SysRq+k is possible, but login after that fails for some reason Workaround: In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false as described here: https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+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 1918583] Re: Switch to libgpiod and disable CONFIG_GPIO_SYSFS
This post: https://waldorf.waveform.org.uk/2021/the-pins-they- are-a-changin.html should explain things rather more completely than I can here but the TL;DR version is: it would be nice to disable sysfs but there's *way* too much stuff that would break right now if we did (mostly Python GPIO interfaces, but given Python is the "blessed" language for much of the Pi Foundation's output, that's a lot of important stuff to break!). My hope is that with the addition of lgpio (a "full-featured" library also based on the gpiochip device) in hirsute we should be in a reasonable position to disable that for the LTS next year (maybe impish?). But right now there's too much that'll break. -- 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/1918583 Title: Switch to libgpiod and disable CONFIG_GPIO_SYSFS Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153 debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y However, this interface got deprecated for removal: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0910d72afc69b25703f7be9bf7d13f18937a478 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b4b76e73dc1486955d93f47276134 "This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for removal in 2020." https://www.kernel.org/doc/Documentation/gpio/sysfs.txt "THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED." libgpiod and the use of a character file-based interface is a replacement to the sysfs interface: https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ Those two interfaces cannot be used interchangeably and working via libgpiod is not possible when the sysfs interface is used: sudo gpioget gpiochip0 12 gpioget: error reading GPIO values: Device or resource busy sudo gpioinfo | grep 12 line 12: "GPIO12" "sysfs" input active-high [used] It would be good to switch to a newer interface since the old one does not get new features and there is no way to switch to libgpiod besides recompiling the kernel with "CONFIG_GPIO_SYSFS=n" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918583/+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 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
> Thanks for the details. You did address the part about upstreaming the change to Debian. How important is that notification in practice? If feels like we should have bluez preinstall on the raspi images if that's not the case, and if it's pre-install is that really worth the packaging overhead to have to carry a delta over Debian? Just to give a bit of context here, the bluetooth situation on the pi is somewhat complicated and there's compromises that we make between the desktop and server images: The bluetooth module on the Pi is controlled via a UART. Two UARTs are available on the Pi (there's more on the Pi 4, but it's the same situation for the bits we're talking about here): * the PL011 which is full featured (buffers, flow-control, etc.), and * the mini-UART which is ... not. Furthermore, the mini-UART's baud rate is tied to the GPU's clock, so if that floats then the mini-UART's baud rate floats too On models of Pi with a bluetooth module (everything except the Pi 2, the CM3/3+ and some models of the CM4), the PL011 is used to talk to the bluetooth module and by default the mini-UART is disabled. This is the configuration we use on the desktop images as we make the assumption a serial console is less important on something which almost certainly has a monitor, and this configuration permits the GPU clock to float (important for something relying upon graphical acceleration). On the server images, we assume that the serial console *is* important, and so this is enabled by default. We don't *disable* the bluetooth module, but we don't pre-install the packages for it either. This means that the PL011 is tied to the bluetooth module by default (but unused), and the mini-UART to the serial console. Because the mini-UART is in use, the GPU's clock is locked to the base speed. This is a compromise because all the alternatives are nastier in some way for some of the typical use cases: * If the server image is used without a graphical environment, and without bluetooth, this is fine (this is the default). The GPU's clock doesn't really matter in this scenario and the serial console will still work reliably. * If the server image is used without a graphical environment, but with bluetooth, all the user needs to do is install pi-bluetooth and reboot (personally I don't think the reboot warning is terribly necessary; like knowing to install pi-bluetooth in the first place, it's fairly widespread knowledge and tends to be part of first-time setup steps anyway). This again leaves the GPU's clock locked (but without a graphical environment that doesn't really matter), the serial console still works, and bluetooth works. * If the server image is used with a graphical environment, without bluetooth, the user needs to either disable the serial console (if they don't want it, this is a one-line change in the boot configuration), or alternatively add the line "dtoverlay=disable-bt" to the boot configuration which disables the bluetooth module entirely, allowing the serial console to use the "full" PL011 UART. Either option unlocks the GPU's clock. * If the server image is used with a graphical environment, with bluetooth, that's effectively the same as the desktop setup and we assume that in this scenario the user would disable the serial console (which means the mini-UART is no longer used and the GPU's clock can float again); again, a one-line change in the boot configuration. So the compromise is to ship an image which, with either zero steps or one step can be moved to one of the scenarios above, with hardware working acceptably for that scenario. We could default to, for example, shipping the server image with both serial console *and* bluetooth enabled, but that complicates moving to a GPU clock unlocked scenario as it involves either disabling the serial console (easy) or removing bluetooth (quite a bit harder, especially if the pi-bluetooth package is now depended on by a meta-package, and also still involves disabling the hardware module with the dtoverlay). Anyway, for the above reasons I don't foresee that we're likely to ship bluetooth enabled server images anytime soon. As to how necessary a reboot warning is -- I'd consider it "nice to have but by no means critical" (it's not hardware enablement after all). If we want to keep the delta minimal, I've no objections. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: In Progress Status in bluez package in Debian: New Bug description: In the case of upgrading or installing bluez for the first time on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1826228] Re: api3a+ hang when reading /sys/devices/platform/soc/driver_override
Appears to work happily on both hirsute and the latest core 20 beta image on a 3A+. May have been fixed in a kernel update prior to one of these. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826228 Title: api3a+ hang when reading /sys/devices/platform/soc/driver_override Status in linux-raspi2 package in Ubuntu: New Bug description: I discovered this when running some tests on a core16 image with various rpi3 devices. Rpi3b, b+, cm3, rpi2, etc... don't have this problem, only rpi3a+. Kernel version: Linux localhost 4.4.0-1107-raspi2 #115-Ubuntu SMP Wed Apr 10 18:06:42 UTC 2019 armv7l armv7l armv7l GNU/Linux To reproduce, simply 'cat /sys/devices/platform/soc/driver_override' The process just hangs and cannot be killed. On other rpi devices, I just get this output immediately: (null) There was nothing in dmesg or syslog when it happened, no kernel crash, and I can still ssh into the system. The process that ran that command just silently hangs and can't be killed even with sudo kill -9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1826228/+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 1918110] Re: overlay_map.dtb is in wrong location
** Also affects: flash-kernel (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: flash-kernel (Ubuntu Hirsute) Importance: Undecided Assignee: Dave Jones (waveform) Status: In Progress ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Also affects: flash-kernel (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux-raspi (Ubuntu Focal) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1918110 Title: overlay_map.dtb is in wrong location Status in flash-kernel package in Ubuntu: In Progress Status in linux-raspi package in Ubuntu: Invalid Status in flash-kernel source package in Focal: New Status in linux-raspi source package in Focal: Invalid Status in flash-kernel source package in Groovy: New Status in linux-raspi source package in Groovy: Invalid Status in flash-kernel source package in Hirsute: In Progress Status in linux-raspi source package in Hirsute: Invalid Bug description: overlay_map.dtb is supposed to be located in /boot/firmware/overlays and *not* in /boot/firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1918110/+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 1912905] Re: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image
Due to a missing brcmfmac43455-sdio.raspberrypi,4-compute-module.txt alias in linux-firmware-raspi2. The CM4's we'd encountered so far (and which had been tested for WiFi compatibility were all requesting brcmfmac43456-sdio.raspberrypi,4-compute-module.txt (note 43455 vs 43456) but it appears there's a couple of board revisions out there. I'll add the necessary alias in linux-firmware-raspi2 for hirsute, then we can see about SRU'ing this. ** Also affects: linux-firmware-raspi2 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1912905 Title: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image Status in linux-firmware-raspi2 package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-firmware-raspi2 source package in Focal: New Status in linux-raspi source package in Focal: Confirmed Status in linux-firmware-raspi2 source package in Groovy: New Status in linux-raspi source package in Groovy: Confirmed Status in linux-firmware-raspi2 source package in Hirsute: New Status in linux-raspi source package in Hirsute: New Bug description: [Description] Can't find WLAN device on Raspberry Pi CM4L with 20.10 armhf preinstall server image. This only happens on armhf image. [Steps to reproduce] 1. Flash image http://cdimage.ubuntu.com/ubuntu/releases/groovy/release/ubuntu-20.10-preinstalled-server-armhf+raspi.img.xz 2. Boot into system 5. Check wireless device using "ip a" [Expected result] Can't find WLAN device [Actual result] WLAN device works fine [Additional information] Hardware: RPI-CM4L Kernel Version: 5.8.0-1006-raspi, 5.8.0-1012-raspi, 5.8.0-1013-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1912905/+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 1918013] Re: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi, 3-model-b.txt lib/firmware/brcm/b
** Changed in: linux-firmware-raspi2 (Ubuntu Hirsute) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: linux-firmware-raspi2 (Ubuntu Hirsute) Status: Triaged => In Progress -- 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/1918013 Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-raspi2 package in Ubuntu: In Progress Status in linux-firmware source package in Hirsute: Invalid Status in linux-firmware-raspi2 source package in Hirsute: In Progress Bug description: Upgrade error Unpacking linux-firmware (1.195) over (1.194) ... dpkg: error processing archive /tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1. 195_all.deb (--unpack): trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu59 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dad1239 F pulseaudio /dev/snd/pcmC1D0p: dad1239 F...m pulseaudio /dev/snd/controlC0: dad1239 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Mar 6 14:59:23 2021 Dependencies: ErrorMessage: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 ImageMediaBuild: 20210302 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware StagingDrivers: bcm2835_v4l2 bcm2835_isp bcm2835_codec bcm2835_mmal_vchiq snd_bcm2835 vc_sm_cma Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918013/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
There's a version of bluez with the patches that I've submitted upstream built in the following PPA against the hirsute branch (the patch changes are pretty minimal; basically amounts to removal of the arbitrary sleep(1) as during December's tests I couldn't find a single platform that actually required that, even amongst the Pi's we don't support like the zero): https://launchpad.net/~waveform/+archive/ubuntu/bluez I'm happy to convert that to a git-ubuntu branch if that's preferable. Once sponsored, we should consider SRU'ing to focal given that Pi400 support is now being SRU'd there generally. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
@hujq is there anything unusual about your bluetooth setup? miniuart-bt overlay or anything like that? I'm unable to replicate the failure here on a Pi 4 8GB -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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
Re: [Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
On Fri, Nov 13, 2020 at 09:37:34AM -, Sebastien Bacher wrote: >@Matthieu, @Dave, thanks for the comments and details. > >I'm not blocking work to land, the 20.10 SRU could be accepted now and I >didn't revert in that serie. >The SRU team tries to ensure the fix is in the new serie so it doesn't get >forgotten/regress when next version is out but I think it's pretty clear we >are going to sort out the review details, that's not a blocker and SRU team >has been happy in the past to let things in with the understand than $newserie >is being sorted out Ah, my apologies - I had mis-interpreted the reversion as applying to the SRU. I've no issue with a reversion in hirsute, provided it doesn't delay existing users from using their Bluetooth hardware. >> If upstream say "yes" to the patches, without further discussion: that's >> great, but there'd presumably still be some delay before another version >> makes its way down to us, so we'd be applying *some* patch to make it work >> in the interim. > >Again I'm not asking for the patches to be reviewed or accepted upstream >before they are uploaded to Ubuntu, I'm just asking for them to be sent >upstream and the reference to the email/report/merge request to be added >to the patches. It would probably have been less work to just do it >rather than type a long explanation here on why we need to distro patch >in any case (which I never disagreed with) I estimate, as I think several others do judging by various comments, that the patches in their current state don't stand much chance of passing muster upstream, and I have no desire to waste their time with a premature submission. At the very least, some justification needs adding to the 1 second sleep: either a datasheet reference, which I've so far failed to find, or some empirical measurements that it's actually required (which I'm in the process of gathering; I've verified *a* delay is required but not the minimum, or whether it can be combined with the post-load nanosleep), along with evidence it doesn't break any existing platforms (I've found a datasheet reference to back that bit up, but tests are good too). Anyway, sorry I mis-interpreted the release your action applied to; I look forward to seeing the SRU land. In the meantime, rest assured a submission will be made upstream as soon as I think I've got a faint hope of it passing! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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
Re: [Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
On Thu, Nov 12, 2020 at 11:11:23AM -, Sebastien Bacher wrote: >Sorry but I'm reverting that upload for now until the patches are >properly upstreamed. We have been bitten too often by unforwarded >changes that create issues or create maintainance burden over the years >and we currently don't have the team capacity to deal with extra cost. >If foundations would like to step up and take over bluez though that's a >discussion we could have... My apologies; I omitted to note in the patch that the Pi 400 is a certified platform, i.e. we're effectively committed to making it work as best we can, which makes the status of whether upstream accept the patches or not rather moot: If upstream say "yes" to the patches, without further discussion: that's great, but there'd presumably still be some delay before another version makes its way down to us, so we'd be applying *some* patch to make it work in the interim. If upstream say "with these changes" to the patches: again great, but in the interim, we'd again be applying *some* patch to make things work on a certified platform while working through changes upstream. If upstream say "not in a month of Sundays" to these patches: we'd be left carrying *some* patch, and we'd do it because it's a certified platform and we're committed to making it work. From our end user's perspective therefore, the application of this patch-set, whether via upstream or not, and whether in this form or not, is not a matter of "if", but "when". Given we have in our possession a patch-set that fixes the problem, I at least don't have a good answer to the hypothetical user's obvious follow-up question: "why not now?" Anyway, onto technical matters: >I'm not asking for the patches to be merged upstream but at least to be >sent there for review and have the appropriate tagging, it's easy to >unblock from your side. Also I would like to see if we can get for a >better way to probe for the system to be ready rather than relying on a >random sleep The following involves a certain amount of educated guessing. I haven't dug into this extensively, but I can offer some reasons for why sleep(1) is being used (and how this could be refined a bit, but not much): Consider the bcm43xx_load_firmware routine in hciattach_bcm43xx.c [1] which is being called prior to the apparently arbitrarily inserted sleep(1) line in the patch. It's a fairly typical firmware load routine by all accounts: 1. Calls write() with a command (0x2e 0xfc) to place the device into a state where it's read to receive new firmware 2. Calls read_hci_event() to check the device responded "okay!" 3. Calls nanosleep() to wait a short while (50ms) for the device to be ready 4. Calls read() and write() repeatedly to write the firmware blob from a file to the UART 5. Calls nanosleep() again to wait another short while (200ms) after the firmware load So the existing (pre-patch) firmware load routine already has a seemingly arbitrary post-firmware-load delay of 200ms. If we have a look at the BCM4334 datasheet [2], p.159 we can see "wait at least 150ms after [power on] before initiating SDIO accesses" (SDIO being one of several interfaces for this particular module). However, that's just for the BCM4334. There's also the BCM4330, BCM4329, and the Cypress 305 (on the Pi 400, which uses the BCM43xx interface; Cypress, incidentally, acquired Broadcom's wireless business which explains why their chips suddenly have Broadcom's interfaces). The bluez interface *could* presumably check precisely which device it was dealing with and adjust its post-firmware-load delay accordingly. Or it could simply go with a delay that's "long enough" to cover all the supported chipsets, and avoid all that logic (which appears to be what's favoured in the original code). Given it's a one-time setup delay, and it's likely to occur during boot-up (or system wake-up) when half a dozen other things are happening in parallel, it's unlikely the user will notice a difference between a 150ms, 200ms, or even 1.2s delay to their Bluetooth module becoming available. Hence one possibility for the sleep(1) delay is that the Cypress 305, being a later and more feature-rich device, requires a longer delay. I can't confirm that as I can't find the datasheet online; sadly, this isn't remotely surprising, but I could reasonably assume that the Pi Foundation *do* have access to it and thus the 1 second delay isn't *entirely* arbitrary. In some of the BCM43xx modules it does appear that the UART CTS line is asserted to indicate the device is "ready" (e.g. the BCM4330 datasheet mentions this under the Bluetooth PMU section). However, one of the configurations (not the default, but a supported configuration nonetheless) for the Bluetooth module on all Pi models is to be operated via the mini-UART instead of the PL011. The mini-UART, as noted previously, explicitly lacks any hardware flow-control ([3],
Re: [Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
On Tue, Nov 10, 2020 at 03:12:30PM -, Sebastien Bacher wrote: >Thanks for the work but it there any work to upstream those changes? I'm >not happy to carry a sleep(1) hack in our package unless there is a >strong reason and we are working on a way to replace it by a better >solution The changes come from the Pi Foundation originally (though I've tidied them up a tiny bit). They're not interested in upstreaming them themselves, though they expressed no objections to my attempting to do so when I raised the question. I realize I'll probably have a bit of a battle on my hands with something like the patch involving sleep(1), but I would note that the sleep(1) hack is in the hciattach_bcm43xx module so it is not something that would be applied to every single Bluetooth module, only to those compatible with the BCM43xx line. While 1 second is obviously a suspiciously round number for the delay, I would further note that it's immediately after a firmware load over the controlling UART and that that UART can (in certain configurations) be the Pi's mini-UART which has some (minimal) buffering, but lacks any hardware flow control. Finally, these patches were also intended to work on the relatively slow, single core Pi Zero. Obviously we don't support the Zero, and thus it's possible *we* might be able to either do away with that sleep, or at least reduce the delay required, but given this is one-off initialization, and the delay is all of 1 second, I'm not convinced it's worth investing the time required to figure out the minimum. Also, I would assume in the interests of upstreaming the patch, the delay should be as widely applicable as possible. Anyway, I'll upstream what I can and we'll have to carry whatever's left over. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Description changed: + [Impact] + + Without these patches, Bluetooth is inoperable on the recently released + Raspberry Pi 400. + + [Test Case] + + * Boot the Ubuntu Desktop for Pi image on a Pi 400. + * Start the Settings application and switch to the Bluetooth tab + * Verify that Bluetooth is not enabled and attempting to activate it fails + * sudo add-apt-repository ppa:waveform/pi-bluetooth + * sudo apt update + * sudo apt install bluez + * sudo reboot + * Start the Settings application and switch to the Bluetooth tab + * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly + + [Regression Potential] + + Extremely low (on groovy in particular, this has the same version of + bluez as hirsute). The only significant risk is to non-Pi platforms or + dongles which also use the Broadcom 43xx (or Cypress 305) chips for + Bluetooth which might be inadvertently affected by these patches. + + [Original Description] + The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Confirmed Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Summary changed: - Bluetooth won't activate on the pi 400 + [SRU] Bluetooth won't activate on the pi 400 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Confirmed Bug description: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
@Daniel could you try out the bluez package from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/pi-bluetooth/+packages ? Should be as simple as doing: sudo add-apt-repository ppa:waveform/pi-bluetooth sudo apt update sudo apt upgrade The version in that PPA contains the pi foundation's patches to bluez which were necessary to enable bluetooth on the pi400 (LP: #1903048), but they also alter some of the general initialization of the bluetooth module on all pis (amongst other things). A (slightly tidied up) variant of this is currently intended for hirsute, to be SRU'd to groovy and focal, so I'd be interested to hear if it also fixes this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Incomplete Status in pi-bluetooth package in Ubuntu: Confirmed Status in bluez source package in Groovy: Incomplete Status in linux-raspi source package in Groovy: Incomplete Status in pi-bluetooth source package in Groovy: New Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+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