[SOLVED] No HDMI sound and volume keeps resetting to 0
-
Had a similar issue with trying to get my sound to output to the 3.5mm jack.
https://retropie.org.uk/docs/Sound-Issues/#using-the-built-in-hdmi-audio
Maybe this needs to be uncommented: hdmi_force_edid_audio=1
-
@bdpyle said in No HDMI sound and volume keeps resetting to 0:
When I go into alsamixer I am presented with 3 sound cards:
bcm2835 Headphones
vc4-hdmi-0
vc4-hdmi-1You seem to have configured the
vc4-kms-v3d
overlay inconfig.txt
, instead of the defaultfkms
overlay. Any reason you've done that ? -
@mitu I'm honestly not sure what that is. I didn't add that to my config.txt. I will say that I have a 64-bit version of Retropie that can run Wii and Gameube games natively, so the OS may have been adited to add that in.
-
@bdpyle said in No HDMI sound and volume keeps resetting to 0:
I will say that I have a 64-bit version of Retropie that can run Wii and Gameube games natively, so the OS may have been adited to add that in.
RetroPie support for 64bit is still not part of any official release. Any 3rd party images are not supported here, as stated in https://retropie.org.uk/forum/topic/3/read-this-first.
-
@mitu Here are the lines in my config.txt file:
# Enable DRM VC4 V3D drive dtoverlay=vc4-kms-v3d max_framebuffers=2 arm_64bit=1
-
@hellothere Just tried uncommenting that, but still no luck.
I am getting the following errors in alsamixer:
VolumeControl::init() - failed to find mixer elements alsactl: get_control:256: Cannot read control '3,0,0,Playback Channel Map,0': Invalid argument
-
@mitu So are you thinking that the reason it isn't working is because I am using a 64-bit version of RetroPie?
-
No, the audio errors are from enabling the
kms
GPU driver, which also adds the new HDMI audio driver.
Other than that, who knows what other configurations have been added to the image by its author - one of the reasons we don't support 3rd party images. -
@mitu Thanks for the help. Just flashed a stock image of retropie onto a new SD card and audio works perfectly through the screen. Going to try removing
dtoverlay=vc4-kms-v3d
and see if that works
-
I successfully replaced the line
dtoverlay=vc4-kms-v3d
in my config.txt file with
dtoverlay=vc4-fkms-v3d
and now everything works perfectly! Thanks for the help @mitu
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.