09-23-2019, 01:20 PM
@shanghai2004
The smoking gun in your dmesg output is:
You can search the web on these messages but most of the hits are very old and refer either to the transition to device trees or to early HFB production problems.
I'd agree with @aknaggbaugh that there's possibly a driver issue since your board works using the same distro on an RPi3B.
I just checked the HiFiBerry Community board. Back in June a user Alex posted
A lot of tweaks have occurred in the Raspbian distro since then as the RPF finds its footing with the new RPi4B. As @Tim Curtis suggests, you could try different kernels to see if a regression slipped in recently.
Regards,
Kent
The smoking gun in your dmesg output is:
Code:
[ 5.298471] wm8804 1-003b: Failed to read device ID: -121
[ 5.298803] wm8804: probe of 1-003b failed with error -121You can search the web on these messages but most of the hits are very old and refer either to the transition to device trees or to early HFB production problems.
I'd agree with @aknaggbaugh that there's possibly a driver issue since your board works using the same distro on an RPi3B.
I just checked the HiFiBerry Community board. Back in June a user Alex posted
Quote:I did some testing with the rasp 4 and hifiberry digi+ pro.
For now, i used Raspbian Buster and VLC, the digi+ pro works as it should, no problem for music and video (dd and dts)
A lot of tweaks have occurred in the Raspbian distro since then as the RPF finds its footing with the new RPi4B. As @Tim Curtis suggests, you could try different kernels to see if a regression slipped in recently.
Regards,
Kent
