[SOLVED] No audio devices on RPi5 with latests builds

[miksi]

I've installed 1.4.1 on my rpi5 over recommended Ubuntu server but I couldn't get any audio device detected. I did update to 1.4.2 but still no audio devices. Also tried to alter config.txt in boot folder but no success. My intention is to use rpi hat dac with 2 es9038q2m dac chips of Ian canada and maybe  some USB dacs.

[agent_kith]

I've installed 1.4.1 on my rpi5 over recommended Ubuntu server but I couldn't get any audio device detected. I did update to 1.4.2 but still no audio devices. Also tried to alter config.txt in boot folder but no success. My intention is to use rpi hat dac with 2 es9038q2m dac chips of Ian canada and maybe  some USB dacs.

Things to look at:

1. Have you look up your HAT documentation and configure the necessary overlay file?
   
2. Under players page, if you see this "Uninstall Pulse" button in red, click on it.. Wait patiently for the operation to finish, and then refresh the page. If your HAT is configured properly the audio device should pop up in the list.
   

[hkphantomgtr]

I've installed 1.4.1 on my rpi5 over recommended Ubuntu server but I couldn't get any audio device detected. I did update to 1.4.2 but still no audio devices. Also tried to alter config.txt in boot folder but no success. My intention is to use rpi hat dac with 2 es9038q2m dac chips of Ian canada and maybe  some USB dacs.

Would you please show us the path of your config.txt and content of that config.txt?  For the USB dac, it only shows up when it's connected to Pi 5.

FYI, currently I'm building this rpi5 music server for fun and testing (the photos may take a minute to load), with a cheap clone audio hat.  It's my first audio hat.  I thought ubuntu, Raspberry OS, and some other big name audio OS will auto detect the hat and configure accordingly and automatically.  But NONE.  All shows no audio device found.  Some audio OS got a nice webui to let me to choose from a long list.  Some got to input manually in the cli, including ubuntu and raspberry OS.  For the cli case, one got to know the exact name of the overlay (driver) in that OS.  There is a folder holding them all.  Just I forgot the path at that moment.

[miksi]

Thanks for your posts people,

It seems that RPi5 has this problem with audio devices on newer builds (1.4.x), RPi4 doesn't have this problem but I'll try another build for RPi5. Actually, a wanted to try RPi5 because i didn't really had the time to play with it and I wanted to tryout mpd compiling speed against RPi4... It is quicker but unfortunately I have yet to setup nvme ssd, perhaps it will be significantly faster.
This is config.txt with little changes:
[all]
arm_64bit=1
kernel=vmlinuz
cmdline=cmdline.txt
initramfs initrd.img followkernel

# Enable the audio output, I2C and SPI interfaces on the GPIO header. As these
# parameters related to the base device-tree they must appear *before* any
# other dtoverlay= specification
dtparam=audio=on
dtparam=i2c_arm=on
dtparam=spi=on

# Comment out the following line if the edges of the desktop appear outside
# the edges of your display
disable_overscan=1

# If you have issues with audio, you may try uncommenting the following line
# which forces the HDMI output into HDMI mode instead of DVI (which doesn't
# support audio output)
hdmi_drive=2

# Enable the KMS ("full" KMS) graphics overlay, leaving GPU memory as the
# default (the kernel is in control of graphics memory with full KMS)
dtoverlay=vc4-kms-v3d
disable_fw_kms_setup=1

# Enable the serial pins
enable_uart=1

# Autoload overlays for any recognized cameras or displays that are attached
# to the CSI/DSI ports. Please note this is for libcamera support, *not* for
# the legacy camera stack
camera_auto_detect=1
display_auto_detect=1

# Config settings specific to arm64
dtoverlay=dwc2

[pi4]
max_framebuffers=2
arm_boost=1

[pi3+]
# Use a smaller contiguous memory area, specifically on the 3A+ to avoid an
# OOM oops on boot. The 3B+ is also affected by this section, but it shouldn't
# cause any issues on that board
dtoverlay=vc4-kms-v3d,cma-128

[pi02]
# The Zero 2W is another 512MB board which is occasionally affected by the same
# OOM oops on boot.
dtoverlay=vc4-kms-v3d,cma-128

[cm4]
# Enable the USB2 outputs on the IO board (assuming your CM4 is plugged into
# such a board)
dtoverlay=dwc2,dr_mode=host

[all]

I don't know which overlay to put there because on 1.3.1 (RPi4) I've entered generic i2s RPi dac overlay and it could show this in audio devices no problem.
Also, both hdmi audio outputs are enumerated and accessible. Here, nothing...

[hkphantomgtr]

Thanks for your posts people,

It seems that RPi5 has this problem with audio devices on newer builds (1.4.x), RPi4 doesn't have this problem but I'll try another build for RPi5. Actually, a wanted to try RPi5 because i didn't really had the time to play with it and I wanted to tryout mpd compiling speed against RPi4... It is quicker but unfortunately I have yet to setup nvme ssd, perhaps it will be significantly faster.
This is config.txt with little changes:
[all]
arm_64bit=1
kernel=vmlinuz
cmdline=cmdline.txt
initramfs initrd.img followkernel

# Enable the audio output, I2C and SPI interfaces on the GPIO header. As these
# parameters related to the base device-tree they must appear *before* any
# other dtoverlay= specification
dtparam=audio=on
dtparam=i2c_arm=on
dtparam=spi=on

# Comment out the following line if the edges of the desktop appear outside
# the edges of your display
disable_overscan=1

# If you have issues with audio, you may try uncommenting the following line
# which forces the HDMI output into HDMI mode instead of DVI (which doesn't
# support audio output)
hdmi_drive=2

# Enable the KMS ("full" KMS) graphics overlay, leaving GPU memory as the
# default (the kernel is in control of graphics memory with full KMS)
dtoverlay=vc4-kms-v3d
disable_fw_kms_setup=1

# Enable the serial pins
enable_uart=1

# Autoload overlays for any recognized cameras or displays that are attached
# to the CSI/DSI ports. Please note this is for libcamera support, *not* for
# the legacy camera stack
camera_auto_detect=1
display_auto_detect=1

# Config settings specific to arm64
dtoverlay=dwc2

[pi4]
max_framebuffers=2
arm_boost=1

[pi3+]
# Use a smaller contiguous memory area, specifically on the 3A+ to avoid an
# OOM oops on boot. The 3B+ is also affected by this section, but it shouldn't
# cause any issues on that board
dtoverlay=vc4-kms-v3d,cma-128

[pi02]
# The Zero 2W is another 512MB board which is occasionally affected by the same
# OOM oops on boot.
dtoverlay=vc4-kms-v3d,cma-128

[cm4]
# Enable the USB2 outputs on the IO board (assuming your CM4 is plugged into
# such a board)
dtoverlay=dwc2,dr_mode=host

[all]

I don't know which overlay to put there because on 1.3.1 (RPi4) I've entered generic i2s RPi dac overlay and it could show this in audio devices no problem.
Also, both hdmi audio outputs are enumerated and accessible. Here, nothing...

config file path = /boot/firmware/config.txt

in the config.txt, just add this line at the end, under [All] or "Enable Audio hat" in Raspberry OS.
 

Code:

dtoverlay=i-sabre-q2m

Or try dtoverlay=i2s-dac

The overlay path = /boot/firmware/overlays

the filename after "dtoverlay=" must be exactly the same in that folder.

If still doesn't work, I hope adding this line will help:
 

Code:

force_eeprom_read=0

 
Good Luck and Enjoy.

[miksi]

I tried dtoverlay=i-sabre-q2m and force_eeprom_read=0 but this didn't make a difference.
I have connected Amanero USB and then it shows as audio device and I can save this config, myMPD can be started but it's not connected to MPD.

---

Reboot fixed this and now library is being scanned... I added only one NFS share from network but it's huge...
Now I need to fix i2s DAC connection...

[hkphantomgtr]

I tried dtoverlay=i-sabre-q2m and force_eeprom_read=0 but this didn't make a difference.
I have connected Amanero USB and then it shows as audio device and I can save this config, myMPD can be started but it's not connected to MPD.

---

Reboot fixed this and now library is being scanned... I added only one NFS share from network but it's huge...
Now I need to fix i2s DAC connection...

I'm sorry that I forgot to tell you to reboot to make the changes effective after editing the config.txt,

[miksi]

I did full install again on RPi5 and i2s dac wouldn't show up no matter what I put in config.txt for dtoverlay and also hdmi audio ports doesn't show up either. Only USB attached device works (Amanero for now). Config.txt is the same on RPi4 and RPi5 but on RPi4 adding dtoverlay=i2s-dac simply works and HDMI outputs also. Maybe RPi5 require some additional settings...
Never mind, I'll use RPi4 for i2s dac... At least I've got sacd mpd working...
PS. How to show info of current file playing in myMPD like sample rate, type (PCM, DSD...), bit depth and similar?

[hkphantomgtr]

I did full install again on RPi5 and i2s dac wouldn't show up no matter what I put in config.txt for dtoverlay and also hdmi audio ports doesn't show up either. Only USB attached device works (Amanero for now). Config.txt is the same on RPi4 and RPi5 but on RPi4 adding dtoverlay=i2s-dac simply works and HDMI outputs also. Maybe RPi5 require some additional settings...
Never mind, I'll use RPi4 for i2s dac... At least I've got sacd mpd working...
PS. How to show info of current file playing in myMPD like sample rate, type (PCM, DSD...), bit depth and similar?

I suspect, would it be a physical connection issue, rather than software issue?

[miksi]

Thing is, i2s dac doesn't have to be connected... In the case of RPi4 it's not connected... Also both HDMIs are not connected but they are enumerated.
I was on a trip today, just got back and I'll try to build newer kernel, possibly RT... Maybe I'll mess something, I don't know, this would be the first time for me to do something like this... Either way it's just another flash of SD card anyway... RPi4 works, fortunately...
I read something about issues with I2S DACs on Linux kernel forums yesterday, and there are definitely problems with the RPi5. Ubuntu uses kernel which doesn't include latest fixes for RPi5... I'll try to find links from browser history...