DG45FC, snd-hda-intel alsa audio not smooth

I am facing similar problems with sound output on a 810E intel chipset based desktop with CM8738 onboard sound card. In my case sound stutters initially and after a few minutes it drops totally. The commandline music player 'music123' shows a "buffer underun error" when the sound is stopped. I tried different fragment size settings in '/etc/pulse/daemon.conf ' but none worked.

Music plays perfectly when the sound is channeled through the 'OSS output plugin' which is found in the settings of VLC, audacious and mplayer .

The issue had come up during the development cycle of jaunty: https://bugs.launchpad.net/pulseaudio/+bug/345627 and the issue had supposedly been fixed by including this patch: https://lists.ubuntu.com/archives/kernel-team/2009-April/005405.html

Most probably there is a problem with pulseaudio + alsa 1.0.20 combinaton, see the comments section here(0021081): https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4642

Running linux 2.6.31-rc6, it seems to work ok now.

Hi latrom,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 407647

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Iirc it was a kernel bug and it is now fixed.

latrom,
    Thanks for the follow up. I am marking this bug Fix Released.

~JFo