Argh, another wrinkle in this story: during ISO testing of the server
images, I also tried the audio output tests with both the current setup
(framebuffer driver) and the intended setup (KMS driver). The KMS driver
works happily for audio output on the Pi 4 and 5. But on the 3B+, it
throws the following error in mpg321:
$ mpg321 -o alsa -a hw:1,0 test.mp3
...
Can't open libao driver with device hw:1,0 (is device in use?)
The device isn't (to the best of my knowledge) in use, as this is
directly after boot-up. Attempting output to the same device with ffmpeg
results in no sound, and numerous ALSA buffer xrun reports:
$ ffmpeg -i test.mp3 -f alsa default:
...
[alsa @ 0xaaaae49062f0] ALSA buffer xrun.N/A speed= 0x
Last message repeated 6 times
[alsa @ 0xaaaae49062f0] ALSA buffer xrun.ed=0.743x
Last message repeated 6 times
[alsa @ 0xaaaae49062f0] ALSA buffer xrun.ed=0.553x
Last message repeated 1 times
The content of /proc/asound/cards on the machine is:
$ cat /proc/asound/cards
0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones
bcm2835 Headphones
1 [vc4hdmi ]: vc4-hdmi - vc4-hdmi
vc4-hdmi
I can accept that using KMS is the way forward, and the "proper"
solution to the lack of soundcards on the Pi 5. But if we go this route,
we also need to avoid breaking audio output on the older platforms too.
** Changed in: linux-raspi (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038924
Title:
No alsa sound cards on Pi 5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2038924/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
