This bug is awaiting verification that the linux-aws/5.15.0-1009.11 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1970586 Title: No sound support on Linux AWS/Azure kernels (but supported on GCP) Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-aws source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: In Progress Bug description: In GCP images it is possible to create virtual MIDI devices and generally do stuff like audio routing, etc. At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of our customers use this functionality to test audio equipment in their CI runs. Unfortunately they cannot run their tests on our AWS based VMs, as there is no sound support compiled into the kernel on the AWS kernel and images. See the package listings for the other kernels for, e.g. the loopback driver: ``` linux-modules-extra-5.4.0-99-generic: /lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko linux-modules-extra-5.8.0-1031-oracle: /lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko linux-modules-extra-5.8.0-1032-gcp: /lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko ``` We would love to be able to install the sound drivers (especially snd- aloop) with the linux-modules-extra-aws package, but currently cannot, and obviously do not want to start running our own kernels, as then we lose the immediacy of kernel patches provided upstream by Canonical. You can see the difference in the GCP: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884 and AWS kernel: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu again there. The reasoning for the removal appears to be in this commit from 2016: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+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
