Audio issues after latest Raspbian updates (June 2020)
-
@Riverstorm said in Audio issues after latest Raspbian updates:
[..]
I just wanted to say THANKS, good sir, for all you do and have a great weekend. As that beer commercial goes... "This Bud's for you!" ...errr... whatever the beer of choice is on that side of the pond! ;)Thank for the - more than - kind words.
-
@VictimRLSH - lol...I apologize for my shortsightedness I should buy the man a proper drink and not just a pint! ;) I've never been but my wife has several times and wants to go as a family, which with the current state of affairs will probably be a while. I guess you could say I'm dead chuffed about that. I hope I used that properly I just learned it the other night on TV. I love their slang over there. Ok fellas, have a super weekend, heading home now to spend some time with the fam! ;)
-
I've just upgraded my 3B+ to Buster (it went exactly in this manner: https://djangocas.dev/blog/upgrade-existing-jessie-to-buster-without-re-image/ ), and this, of course, happened - the above fix, with the addition to cmdline.txt, did restore the sound.
(Incidentally, I had the sound in startx, even before the attempts to fix it in Retropie).
However, the volume still always resets to 0 in EmuStation, and the fix seems to only work sometimes - one time EmuStation will click when scrolling through titles, other times it will stay quiet.
Speaker-test from the command line, however, now always seems to make its noise properly.
(By the way, I've noticed that while the regular binary for EmuStation is from June, the one for EmuStation dev. version 2.10 is still from April - I'll check if this influences the sound fix. I normally use the dev. version, I switched to the regular for the sound fix).
-
Adding: hah, "funnily" enough, now EmuStation's sound is crackling, wobbly, and it also slowns down the emulators to the point that after updating to Buster, RP has become just unusable. :|
EmuStation 2.10 dev acts in the same manner, no matter what devices are selected in the menu - HDMI, PCM, ALSA, both...
-
@BazzCatt that sounds like another issue.
-
@BazzCatt This is what was happening to me. Check alsamixer and see what your default sound device is. I found a Bluetooth utility I installed into the desktop to facilitate file transfers also installed Pulseaudio and completely jacked up my sound in the same manner. I had to purge pulseaudio to remedy the problem (see above post).
-
This should fix the problem:
sudo rpi-update 8d64ec7016906fb1f2bbe937dd7401705c5acf33
Newer firmwares makes troubles with sound on Raspbian Buster.
Use that command on your own risk. -
@Sid1968 said in Audio issues after latest Raspbian updates:
sudo rpi-update 8d64ec7016906fb1f2bbe937dd7401705c5acf33
Using
rpi-update
is not recommended for normal updates. While this might get you a firmware version before the changes in the audio configuration, any updates for OS updates including kernel/firmware - viaapt
- will overwrite it.
I strongly advice against this approach.Newer firmwares makes troubles with sound on Raspbian Buster.
Hence the topic at hand. If you want to revert to the previous audio configuration, you can modify
cmdline.txt
as outlined in the first post. -
@mitu The problem is that the "normal" update command installs a new firmware. That causes the sound issues. My command restores an older version. For me it works well. But... that should everyone decide for themselves.
-
@Sid1968 as said in the topic starter, you can get back to your previous configuration without downgrading anything. There's no reason to use
rpi-update
. -
@mitu Ok i agree. :-)
-
@mitu Is it possible to prevent this error message to appear again by reverting back to previous configuration ?
-
@Yobiwan Yes, but I wouldn't recommend that. You have the new settings explained in the first port, once you set them, you shouldn't get any error.
-
@mitu OK thanks ! i'm out of data for this month (deep countryside!) so in a few days I will try updating all of that.
-
@mitu, Hi, I am running my Raspberry Pi 3b+ with an audio jack and I've been having sound problems as mentioned in this post (no audio from games, although I can verify my computer's audio works by running an mp3 file on omxplayer). The errors I've been getting when trying to change my audio settings in emulation station is "lvl0: VolumeControl::init() - Failed to attach to default card". I followed all the steps and configured the audio in the menu as you suggested. But, still hasn't solved anything, unfortunately.
I've been looking through blog posts all day trying to fix this, but it hasn't been working. If you'd like me to make a new post and list my system specs and whatnot, please let me know, and thank you.
-
@amansur Nvm, I gave up and just decided to reboot everything on the pre-installed image. For those that manually installed and are having trouble like I was and nothing seemed to be working, just do that. My recommendation.
-
Error message has gone, ingame audio is back, but my intro video has no audio anymore...
-
@Yobiwan Please open a separate topic and add your system info, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.
-
When you say "just do that", what is the "that" that you're talking about?
Nothing from the above has fixed audio here, and I'm getting the same error.
Just an FYI, this is a freshly flashed image on an SD card in an RPi 3b.
-
@undrwater Sorry for not being clear. What I mean by "that" is simply downloading the RetroPie software from the pre-made image as opposed to the manual installation. After doing so, I was able to figure it out.
Since you are still getting issues, after the installation, I followed these instructions from this video:
By audio settings currently are: Audio Card (Default), Audio Device (PCM), Enable Navigation Sounds (On) Enable Video Audio (ON), DMX Player Audio Device (Local).
It's worth noting that when I type in "uname -r" I see my version is "4.19.97-v7+" but in my old configuration (before I went with the flashed installation) it was at 4.19.118 or above. So if you followed the instructions in the video AND you have a lower kernel number than 4.19.118, then you should be fine... If your kernel number is at or above 4.19.118 and the post's instructions didn't work, then try downgrading the kernel. In essence, that's what I probably ended up doing when I switched over.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.