03-22-2022, 05:43 PM
There are multiple issues with supporting Hifiberry DAC2HD
1. If OS release uses 5.15.y kernel branch as does moOde 8 then DAC2HD requires 5.15.24 or later.
2. DAC2HD and other Hifiberry devices apparently store a device tree overlay in the board's EEPROM which is automatically read by Pi firmware during boot. If there is also a dtoverlay= in /boot/config.txt as is done by moOde for all I2S audio devices it will or may conflict with the overlay loaded from the audio board's EEPROM. This is because the EEPROM based overlay may not be compatible with newer kernels. The fix according to Hifiberry is to add "force_eeprom_read=0" to /boot/config.txt.
https://www.hifiberry.com/blog/configura...linux-5-4/
https://www.hifiberry.com/docs/software/...ux-3-18-x/
Note that no other manufacturer's audio cards require these configs. They all just support the explicit dtoverlay= setting in /boot/config.txt.
Upcoming moOde 8.0.2 release adds the "force_eeprom_read=0" for all Hifiberry cards / overlays listed in /boot/overlays.
-Tim
1. If OS release uses 5.15.y kernel branch as does moOde 8 then DAC2HD requires 5.15.24 or later.
2. DAC2HD and other Hifiberry devices apparently store a device tree overlay in the board's EEPROM which is automatically read by Pi firmware during boot. If there is also a dtoverlay= in /boot/config.txt as is done by moOde for all I2S audio devices it will or may conflict with the overlay loaded from the audio board's EEPROM. This is because the EEPROM based overlay may not be compatible with newer kernels. The fix according to Hifiberry is to add "force_eeprom_read=0" to /boot/config.txt.
https://www.hifiberry.com/blog/configura...linux-5-4/
https://www.hifiberry.com/docs/software/...ux-3-18-x/
Note that no other manufacturer's audio cards require these configs. They all just support the explicit dtoverlay= setting in /boot/config.txt.
Upcoming moOde 8.0.2 release adds the "force_eeprom_read=0" for all Hifiberry cards / overlays listed in /boot/overlays.
-Tim
