balena-sound icon indicating copy to clipboard operation
balena-sound copied to clipboard

Published 20 hours ago • verified publisher icon balena-io-experimental

No sound output with balenaOS 64 bit on Raspberry Pi 3

Open anujdeshpande opened this issue 5 years ago • 15 comments

See - https://jel.ly.fish/fbd336b3-c2c5-4e28-aefb-2c1f9daec5fe - for more info

anujdeshpande avatar Jan 21 '20 08:01 anujdeshpande

[anujdeshpande] This issue has attached support thread https://jel.ly.fish/#/fbd336b3-c2c5-4e28-aefb-2c1f9daec5fe

balena-ci avatar Jan 21 '20 08:01 balena-ci

@anujdeshpande could you add the information in the Github issue - Jellyfish isn't public so contributors won't be able to see what the problem is.

chrisys avatar Jan 27 '20 17:01 chrisys

[dtischler] This issue has attached support thread https://jel.ly.fish/#/7f704146-1aaa-4378-8b4d-dd8d4ea9fcb3

balena-ci avatar Feb 03 '20 22:02 balena-ci

While attempting this on a Raspberry Pi 3B+ with 64-bit OS, this appears to repeat indefinitely in the logs:

03.02.20 14:42:59 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:00 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:00 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:01 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:01 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:02 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:02 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:03 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:03 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:04 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:04 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:05 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:05 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:06 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:06 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:07 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:07 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:08 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:08 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:09 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:09 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:10 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:10 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device 03.02.20 14:43:11 (-0700) bluetooth-audio ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave 03.02.20 14:43:11 (-0700) bluetooth-audio /usr/bin/bluealsa-aplay: Couldn't open PCM: No such device

dtischler avatar Feb 03 '20 22:02 dtischler

Just a +1 on the Bluetooth issue above being reproduced on RPI 3B 64bit

gakonst avatar Mar 01 '20 16:03 gakonst

As a fix whilst we look into this, you should be able to simply remove the vc4-kms-v3d overlay from the device configuration and reboot, after that the 64-bit OS should work.

chrisys avatar Apr 01 '20 12:04 chrisys

As a fix whilst we look into this, you should be able to simply remove the vc4-kms-v3d overlay from the device configuration and reboot, after that the 64-bit OS should work.

This helped for me, thanks

andyzasl avatar Apr 12 '20 12:04 andyzasl

[ab77] This issue has attached support thread https://jel.ly.fish/#/61a47e67-6ed7-4fcd-b560-e341f8469e88

jellyfish-bot avatar May 25 '20 20:05 jellyfish-bot

[tmigone] This issue has attached support thread https://jel.ly.fish/a2a5c36f-afc2-4b70-aa1b-8fbb244c6f37

jellyfish-bot avatar Jun 23 '20 18:06 jellyfish-bot

[robertgzr] This issue has attached support thread https://jel.ly.fish/7630211b-a451-4ee4-a04b-71c456039567

jellyfish-bot avatar Oct 29 '20 16:10 jellyfish-bot

[pipex] This issue has attached support thread https://jel.ly.fish/1ef5fa52-0ac8-49bc-bb27-de482d0769e1

jellyfish-bot avatar Nov 02 '20 21:11 jellyfish-bot

Downgrading to v2.38.0+rev1 solved this for me. https://github.com/balenalabs/balena-sound/issues/62#issuecomment-758763978

theonlysinjin avatar Jan 12 '21 16:01 theonlysinjin

This issue is still present with me on a Raspberry Pi 4 64bit on balenasound v3.9.1. Works just fine on my Raspberry Pi 3 32bit.

The workaround reference in this issue fixed the no audio problem on my Raspberry Pi 4.

As a fix whilst we look into this, you should be able to simply remove the vc4-kms-v3d overlay from the device configuration and reboot, after that the 64-bit OS should work.

FrozenAtlas avatar May 23 '22 05:05 FrozenAtlas

As a fix whilst we look into this, you should be able to simply remove the vc4-kms-v3d overlay from the device configuration and reboot, after that the 64-bit OS should work.

I can confirm that removing it from DT overlays in a Raspberry Pi 3 (using 64bit OS) fixed the issue: Captura de pantalla 2023-02-10 a les 17 39 08

pjmartorell avatar Feb 10 '23 16:02 pjmartorell

@pjmartorell would you be able to add a PR to update the docs?

maggie44 avatar Feb 15 '23 11:02 maggie44