bullseye 64 bit support

Darksavior

@ParadoxGBB Retroarch emulators work on 64bit bullseye lite. I haven't tested the rest.

Audio doesn't work right now. To get it working, I used to use the audiosettings.sh from cmitu's audio-ks dev branch, but a recent update in that branch broke it.

mitu

@Darksavior said in bullseye 64 bit support:

Audio doesn't work right now. To get it working, I used to use the audiosettings.sh from cmitu's audio-ks dev branch, but a recent update in that branch broke it.

'my branch' has been merged into RetroPie-Setup for at least a month.

windg

I am testing the latest weekly image, i know that this image is not tested and stable, but i don't have audio too.

mitu

@windg Did you configure the audio from the RetroPie's Audio settings ?

windg

I set the audio output to HDMI 0. I set also sound card from Headphones to vc4-hdmi-0 but still don't have sound.

From ES sound settings, audio card set to Default and audio Device set To HDMI, with the system volume to stay to zero,

mitu

@windg said in bullseye 64 bit support:

I set the audio output to HDMI 0. I set also sound card from Headphones to vc4-hdmi-0 but still don't have sound.

Post your $HOME/.asoundrc file.

windg

I can't find this file

mitu

@windg said in bullseye 64 bit support:

I can't find this file

This usually means you haven't configured the Audio from the RetroPie system.

windg

After i changed the audio to HDMI 0 i check in the mixer and it's still says Headphones, also the old issue with "fail to find mixer elements" appearing.

mitu

I'll take a look to see what's going on, after using the Audio settings, you should have a $HOME/.asoundrc file used by ALSA choose the correct sound output.

Do you have installed the desktop or PulseAudio ?

windg

@mitu No i haven't install it. I flash a fresh copy of weekly image (08-Aug-2023) few minutes ago just to be sure that i didn't modify something that i don't remember.

mitu

Actually, the audiosettings have moded to /etc/alsa/conf.d/99-retropie.conf, can you check to see if you have that file and - if yes - post the contents ?

windg

Alsa folder doesn't exist

mitu

That could explain the issue. Can you manually create the folder with sudo mkdir /etc/alsa/conf.d/ and re-configure again the Audio ?

windg

I create the folders, i set audio to HDMI 0 but no sound. I check into the /alsa/conf.d/ but is empty.

mitu

@windg said in bullseye 64 bit support:

I check into the /alsa/conf.d/ but is empty.

It's /etc/alsa/conf.d.

windg

Yes , i create to /etc a alsa folder and inside it a conf.d folder

windg

@mitu It looks that something i did wrong when i try to create the folders. I try again and now the sound is working.

I did exactly :

sudo mkdir /etc/alsa
sudo mkdir /etc/alsa/conf.d
I set from RetroPie menu audio to HDMI 0
Restart EmulatioStation

After tha sound is working, the only thing that remains is the message about mixer.

Many thanks mitu!

mitu

@windg said in bullseye 64 bit support:

@mitu It looks that something i did wrong when i try to create the folders. I try again and now the sound is working.

Thanks for the confirmation, I'll take a look at why the folder is missing and maybe create it automatically, will need to start from a clean image again since my bullseye image has suffered many changes and was installed from an earlier RaspiOS version.

Ideally we can also make HDMI the default audio output on a fresh image, since the analog audio is now the default.

ParadoxGBB

Hey all, thanks for the support. I know that this is a grey zone but it's much appreciated. My bad in conflating Bullseye support with 64 bit support.

I was having issues with audio as well, even before installing RetroPie (speaker-test failing with error 524, could not add HDMI via mixer or emulation station). The only way I was able to fix it was to move to fkms from kms (the default) in config.txt.

It seems very similar to this thread: https://retropie.org.uk/forum/topic/32888/amiberry-audio-not-working-on-bullseye-64-bit-pi4-kms

After installing RetroPie the setup script was complaining about ALSA configuration and I ended up removing it this morning, and things are working now.