search

balena-io-experimental / balena-sound

Build a single or multi-room streamer for an existing audio device using a Raspberry Pi! Supports Bluetooth, Airplay and Spotify Connect
https://balena.io/blog/turn-your-old-speakers-or-hi-fi-into-bluetooth-receivers-using-only-a-raspberry-pi/
MIT License
2.42k stars 430 forks source link

No sound output with balenaOS 64 bit on Raspberry Pi 3 #82

Open anujdeshpande opened 4 years ago

anujdeshpande commented 4 years ago

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

balena-ci commented 4 years ago

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

chrisys commented 4 years ago

@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.

balena-ci commented 4 years ago

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

dtischler commented 4 years ago

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

gakonst commented 4 years ago

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

chrisys commented 4 years ago

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.

andyzasl commented 4 years ago

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

jellyfish-bot commented 4 years ago

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

jellyfish-bot commented 4 years ago

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

jellyfish-bot commented 3 years ago

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

jellyfish-bot commented 3 years ago

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

theonlysinjin commented 3 years ago

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

FrozenAtlas commented 2 years ago

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.

pjmartorell commented 1 year ago

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
maggie44 commented 1 year ago

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