[Kernel-packages] [Bug 1933771] Re: Bluetooth headset random disconnects AX200
I still see the issue (last time was after 90 minutes during a conf call) with Ubuntu 21.10 with linux-firmware 1.202. -- 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/1933771 Title: Bluetooth headset random disconnects AX200 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: In Progress Bug description: [Impact] Using several different bluetooth headsets I find that the Bluetooth functionality of the built-in AX200 module of my motherboard keeps randomly disconnecting. I found that this has been fixed in recent Linux firmware updates, but I am not sure that fix has landed yet in Ubuntu Hirsute. Herewith I am posting the link to exactly the issue I am having: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155 And the Linux Firmware commit that resolves this: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180 A related Fedora bug: https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274 It's difficult to relate the upstream kernel version firmware version in which this was fixed (linux-firmware-20210511) to the version of the linux-firmware Ubuntu package (for me). Perhaps someone can comment on whether this has been merged in. I am still experiencing disconnects with 1.197.1 at least. -- Description: Ubuntu 21.04 Release: 21.04 linux-firmware: Installed: 1.197.1 Candidate: 1.197.1 I expected: Bluetooth headset to remain connected What happened: Bluetooth headset connects, then randomly disconnects and reconnects while playing media [Test Case] See above. [Fix] Update AX20x firmware blobs. [Where Problems Could Occur] New firmware blobs so previously working adapter might now fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1933771] Re: Bluetooth headset random disconnects AX200
I still have the issue on Ubuntu 21.10 with linux-firmware 1.201.3 -- 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/1933771 Title: Bluetooth headset random disconnects AX200 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: In Progress Bug description: [Impact] Using several different bluetooth headsets I find that the Bluetooth functionality of the built-in AX200 module of my motherboard keeps randomly disconnecting. I found that this has been fixed in recent Linux firmware updates, but I am not sure that fix has landed yet in Ubuntu Hirsute. Herewith I am posting the link to exactly the issue I am having: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155 And the Linux Firmware commit that resolves this: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180 A related Fedora bug: https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274 It's difficult to relate the upstream kernel version firmware version in which this was fixed (linux-firmware-20210511) to the version of the linux-firmware Ubuntu package (for me). Perhaps someone can comment on whether this has been merged in. I am still experiencing disconnects with 1.197.1 at least. -- Description: Ubuntu 21.04 Release: 21.04 linux-firmware: Installed: 1.197.1 Candidate: 1.197.1 I expected: Bluetooth headset to remain connected What happened: Bluetooth headset connects, then randomly disconnects and reconnects while playing media [Test Case] See above. [Fix] Update AX20x firmware blobs. [Where Problems Could Occur] New firmware blobs so previously working adapter might now fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1848790] Re: USB not working under arm64 on Pi4
Does someone know when the fix will be ported to the Ubuntu arm64 image? -- 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/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Triaged Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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
