[SOLVED] No soundcard found on Raspberry Pi 5 with aarch64
Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'd informed Exaga to include it in one of his packages a while ago and he hadn't done so yet, so the best I can do is share the info in a forum for others to happen upon
Then I apologise because I cannot recall ever being asked or informed about including this file in one of the SARPi packages.
I'd be more inclined to bug Stuart to address it in Slackware OS in any case, as it's an X11 thing and not something that's RPi kernel or firmware related.
Quote:
Originally Posted by drmozes
Thanks, I will drop it into the x11-skel package. It won't get installed under SARPi since it lacks the slk-hwm-discover tool, but it'll live within /usr/share/x11-skel/platform/aarch64/bcm2712/xorg.conf.rpi5
Thanks. Besides being 110% correct about SARPi, this is the most logical and effective solution in this instance.
I've installed Slackware current via Sarpi on an Rpi5, and it's deja vu, all over again. No HDMI sound, with no soundcards found, and the graphics are a bit tweaky with KDE. A USB soundcard works fine. The graphics issue is the same, or similar, to what happened on my Rpi4 a while back... Some elements aren't displayed, like the menu in System Settings... Other than that it's all good, so far.
I've installed Slackware current via Sarpi on an Rpi5, and it's deja vu, all over again. No HDMI sound, with no soundcards found, and the graphics are a bit tweaky with KDE. A USB soundcard works fine. The graphics issue is the same, or similar, to what happened on my Rpi4 a while back... Some elements aren't displayed, like the menu in System Settings... Other than that it's all good, so far.
Code:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
jbl@fiven:~$ uname -a
Linux fiven.lngn.net 6.6.21-rpi5+ #2 SMP PREEMPT Wed Mar 13 06:11:58 -00 2024 aarch64 GNU/Linux
Sounds does indeed work on the latest kernel 6.6.21. I think the barrier here is that users are not configuring their config.txt properly, as the one shipping with sarpi needs tweaking. Keep in mind, Exaga doesn't use wifi, nor does he use graphical environments (maybe I'm spilling the beans here) so users are effectively on their own with configuration afterwards. I DO however, think these nuggets of info should be presented to the user on the sarpi website, else how else will users know?
I'm attaching my current config.txt file, which users should backup theirs first, but then place this within their /boot directory and reboot the rpi5 afterwards. Pay close attention to the "dtoverlay" options, the video one is changed, and I've also explicitly enabled wifi. Before rebooting with this config, ensure you uncomment the correct kernel name line. I'm currently testing my own kernel build, and I've named it according to the defconfig in use.
I've installed Slackware current via Sarpi on an Rpi5, and it's deja vu, all over again. No HDMI sound, with no soundcards found, and the graphics are a bit tweaky with KDE. A USB soundcard works fine. The graphics issue is the same, or similar, to what happened on my Rpi4 a while back... Some elements aren't displayed, like the menu in System Settings... Other than that it's all good, so far.
OK, thanks for the feedback netcrawl.
I've just uploaded a new SARPi5 batch with updated content to address this issue specifically. Thanks mainly to jloco for sharing information, I've decided to do what he suggested to me weeks ago.
Just make sure you have the following line configured like this in your /boot/config.txt file:
Code:
dtoverlay=vc4-kms-v3d-pi5
Then the desktop on the Raspberry Pi 5 should work as expected.
Just make sure you have the following line configured like this in your /boot/config.txt file:
Code:
dtoverlay=vc4-kms-v3d-pi5
Then the desktop on the Raspberry Pi 5 should work as expected.
Indeed, HDMI audio and graphics are all good now. Installed the Sarpi bits from 15Mar24, & edited config.txt as described. Much thanks to Exaga & jloco for getting this happening.
Using Sarpi's installer of 15Mar2024 resulted in working audio and X-server. In /boot/config.txt I found "dtoverlay=vc4-kms-v3d-pi5" and the file "/etc/X11/xorg.conf.d/99-vc4.conf" does exist.
Plugging in an USB audio adapter works fine: HDMI audio will be switched off and the headphone will be turned on. After unplugging the USB audio adapter the audio will be returned to HDMI.
In Pavucontrol's "Playback" you can choose between HDMI audio and the USB adapter.
Using Sarpi's installer of 15Mar2024 resulted in working audio and X-server. In /boot/config.txt I found "dtoverlay=vc4-kms-v3d-pi5" and the file "/etc/X11/xorg.conf.d/99-vc4.conf" does exist.
Thanks Exaga for fixing.
Not really thanks to me, but thanks to jloco. Just having "dtoverlay=vc4-kms-v3d-pi5" in the /boot/config.txt file, and the Xorg conf file in place that jloco highlighted previously, is enough to get the HDMI video/audio working as expected on the RPi5.
The problems arose because traditionally HDMI has always been configured by firmware settings in config.txt, but devices that feature the RP1 chip now do this via KMS settings in cmdline.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.