The sound is distorted on Macbook Pro 17" 2.16 GHz

How can I help in solving this problem?

Gutsy is Final now, have u tried updating to all the latest Packages thru update-manager?

All up to date.
Still there. Would it help if I recorded it or something?

On Nov 23, 2007 5:35 AM, nowshining <email address hidden> wrote:

> Gutsy is Final now, have u tried updating to all the latest Packages
> thru update-manager?
>
> --
> The sound is distorted on Macbook Pro 17" 2.16 GHz
> https://bugs.launchpad.net/bugs/146558
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Jon Ramvi
0424 889 893

if ur all updated then ur using the final release of Gutsy :) that's why I suggested making sure ur all up to date on packages as u put RC1..

AS for "Still there. Would it help if I recorded it or something?" It's all up to u if u'd like to include an example. ;) but i am not no maintainer or developer of the site, I'm just here asking obvious questions and U said u had RC1 which is why i suggested doing a full update and then trying again...

Ah, thanks! I've updated the bug report :) I'll wait for a maintainer to ask me for an example before making one

Hi. Please read the following page on debugging sound problems and attach the info requested there. Thanks!

This bug was nominated for various stable release updates (SRU) but does currently not qualify and the nomination is therefore declined. According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https://wiki.ubuntu.com/StableReleaseUpdates

Hi again,
I would say the importance of this is higher than low, as it drastically reduces the value of the Macbook Pro.

Anyway, after having crackling sound for over a year, I got it fixed!
I got the fix from gentoo's wiki: http://gentoo-wiki.com/HARDWARE_Apple_MacBook#Crackling_Sound_on_the_left_Channel

The fix that worked for me was:
rmmod snd_hda_intel
modprobe snd_hda_intel

There is no fix released. This bug is still active

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!