-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Peach Pi/XE503C32: Speakers not working #233
Comments
it looks like i removed that script at some point as it was not required for peach pit - maybe give it a try if it helps in your peach pi case: 5d314bc#diff-925ce82269ebee50c5ac063a3a1f14a07c7a3b0062e27a3f6f6bd5ee571114b3 ... please let me know if it helps but i guess if you have headphones working, you kind of have working audio somehow already - did you already try to manually switch to speaker audio via pavucontrol? |
Okay so I tried the script, but it returns with "cp: cannot stat '/usr/share/alsa/ucm2/Peach-Pi-I2S-MAX98091': No such file or directory". |
i have at least removed the note about the audio setup script now as it is just confusing if the script is not there anymore and not needed as it looks like: f99b1a1 |
@hexdump0815 you can ship pmOS ucm configs as long as you ship the same kernel |
@jenneron - thanks a lot, i'll note that down - actually iirc sound is working well on my peach pit - will have to check and retest all that whenever i find some time |
The latest image I used works so far, but I can't get the internal speakers to work on Peach Pi (XE503C32)
Audio works through the headphone output, but not through the internal speakers. I havent tested HDMI Audio, whether that works or not.
It'll be appreciated if I can get some insight about this !
Image: Latest one for Pi Peach (https://github.com/hexdump0815/imagebuilder/releases/tag/230924-02)
It did say "after first boot please run /scripts/fix-peach-audio.sh as root to fix the ucm audio config files for the corresponding system and reboot" on that page, but there wasn't such a script in that directory.
The text was updated successfully, but these errors were encountered: