You mean with the kms setting, i.e. dtoverlay=vc4-kms-v3d without f, right?
EDIT: Ah, missed your previous post. Ensure to set the checkbox [x] System default below the sound device selection. That should do the magic.
With the setting dtoverlay=vc4-kms-v3d and system default it didn’t work under Amiberry 5.6.9 but now with the setting dtoverlay=vc4-fkms-v3d everything works very well and without any error messages the sound is played without any problems, I’m happy, thank you for the effort to help you are great
Hmm, that is unintended. The SDL2 backend is intended to run with full KMS, not fake KMS. I mean the latter is provides the same API, hence it obviously works, but it will probably not be available forever, now that all the libraries it was supposed to support are essentially gone from standard RPi OS installations.
Since we are trying to indeed find a solution for the vc4hdmi driver with vc4-kms-v3d, if you have time, it would be great if we could debug this, since it does work here on my RPi Zero W, and I’ll test on an RPi 5 as well.
With vc4-kms-v3d, did running speaker-test on console produce some noise on your HDMI screen?
I carried out dtoverlay=vc4-kms-v3d without and the rake at system default under amiberry at the sound it was also displayed the hdmi port only in the system karm no sound it’s strange that it worked at zero I had the same effect as before on it I switched to fkns again and it all works with the amiberry version 5.6.9 from the testing folder
It didn’t give me any peace and I tried again bit of your setting but still can’t get any sound with system default with the Raspberry Pi 3a+ under dtoverlay=vc4-kms-v3d and what I noticed today is that Amiberry 5.6.9 has been changed Within a day I now get an error message under my advertising image and the salt ratio is no longer displayed correctly. I wanted to say to improve it and there is also the wrong date under info
The Amiberry testing build has no changed, but you is behaved differently now? The build date on the info tab should show the same as yesterday, I did not trigger a new build since then.
About fake KMS vs full KMS: It would be great if you could run speaker-test on the console with full KMS dtoverlay=vc4-kms-v3d enabled and /etc/asound.conf removed. It this does not produce any noise or even an error, it cannot work in Amiberry either, but indicates that something is still setup differently compared to my RPi Zero W system, which we would need to find out. Another helpful output would be:
aplay -L
with capital L, to show the available ALSA PCMs and whether the default and sysdefault is there the intended way, or whether some other config overrides the default (and hence breaks/bypasses this IEC958 conversion plugin. E.g. check also whether there is a user-specific config:
ls -l /root/.asoundrc
rm /root/.asoundrc
so habe kms eingestellt system default asound.conf gelöscht trotzdem bekomme ich nicht wie bei ihnen mit dem zero sound
.Asoundrc can’t be removed doesn’t find the directory I can only delete the asound.conf from the root
Ah, you have still “auto” onboard audio selected, hence practically 3.5mm/analogue output in this case. Please try to select HDMI audio explicitly, then remove /etc/asound.conf.
I btw fixed this in dietpi-config, so you could also wait for the release, then /etc/asound.conf won’t be generated in the first place, when selecting HDMI audio while KMS is enabled: v9.2 · MichaIng/DietPi@0dac52b · GitHub
First of all, thank you, I’ve never had anyone who has tried as hard as she did michalng the problem is solved, it works wonderfully kms directly hdmi set dietpi 9.2.1 and amiberry 5.6.6 top sound I’m thrilled 1000 thanks
1 Like
Through the many tests, I noticed that amiberry 5.6.8 does not display full scaling and amiberry 5.6.9 often causes errors in my workbench image when I go to amiberry mui and back the image is moved I just want to mention it so that you get fewer problems thank you again
Maybe you can also help me with this, I use these settings to hide all the boot text in the time I would like to insert in picture in the boot process, unfortunately I don’t know how to do it
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.