Some boards have I2C errors when a DVI monitor is plugged in. This can prevent register access to the sgtl5000 audio codec when the audio driver is initializing. The symptom is that you will see in the boot messages some I2C errors and a message that it has not successfully id'd the sgtl5000.
The workaround is to take two resistors off the board (this is OK for babbage 2.0 and 2.5): R284 and R287. They are located on the top side of the board about 1cm from the DVI connector on either side of U33.
This will cut the I2C connection to the DVI connection so that it will not be able to read the EDID. So specifying the video mode in the kernel command line is necessary if you are not already doing so, i.e. "video=mxcfb:1024x768-16@60".
Some boards have I2C errors when a DVI monitor is plugged in. This can prevent register access to the sgtl5000 audio codec when the audio driver is initializing. The symptom is that you will see in the boot messages some I2C errors and a message that it has not successfully id'd the sgtl5000.
The workaround is to take two resistors off the board (this is OK for babbage 2.0 and 2.5): R284 and R287. They are located on the top side of the board about 1cm from the DVI connector on either side of U33.
This will cut the I2C connection to the DVI connection so that it will not be able to read the EDID. So specifying the video mode in the kernel command line is necessary if you are not already doing so, i.e. "video= mxcfb:1024x768- 16@60".