+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: No sound / MPD error (moode 8.2.0 / Allo BOSS / RPI 3 B+) (/showthread.php?tid=5102)
No sound / MPD error (moode 8.2.0 / Allo BOSS / RPI 3 B+) - wasbaer - 10-03-2022
Hello everybody!
Can someone please help?
On a fresh install, I keep getting this error when trying to play music.
Code:
MPD error: Failed to open "ALSA Default" (alsa); Failed to open ALSA device "_audioout": No such file or directoryWhat do I need to do?
Please tell me what kind of info you need to identify the problem.
I'm most grateful for your time.
Thanks!
RE: No sound / MPD error (moode 8.2.0 / Allo BOSS / RPI 3 B+) - Tim Curtis - 10-03-2022
Very odd. I have a 3B+ with a Boss on top and no issues.
Post the output from the following commands and I'll have a look.
Code:
moodeutl -l
lsmod | grep allo_bossRE: No sound / MPD error (moode 8.2.0 / Allo BOSS / RPI 3 B+) - wasbaer - 10-06-2022
don't bother please
RE: No sound / MPD error (moode 8.2.0 / Allo BOSS / RPI 3 B+) - wasbaer - 10-06-2022
Hey Tim,
did another clean install and now it works. Sorry, my bad.
RE: No sound / MPD error (moode 8.2.0 / Allo BOSS / RPI 3 B+) - wasbaer - 10-06-2022
I feel stupid. Admin, can you please delete this thread?
RE: No sound / MPD error (moode 8.2.0 / Allo BOSS / RPI 3 B+) - Tim Curtis - 10-06-2022
It's actually a useful thread because the specific error you reported (below) occurred on one of my I2S test systems the other day and after investigating I found that the file /boot/config.txt which contains the line that specifies the I2S device driver was gone :-0
Code:
MPD error: Failed to open "ALSA Default" (alsa); Failed to open ALSA device "_audioout": No such file or directoryThe key element of the error is this line
Code:
No such file or directoryMy test systems are thrashed and reloaded frequently and so I'll chalk it up to some weird combination of events but if the error comes up again in the Forum I'll have the "missing config.txt" file on the list of possible causes to investigate.