Hi there,
No, it looks like setting PCM to 100 doesn't fix the problem.
Should I Try rebooting after setting it to 100?
I should mention that PCM was set to zero until you brought that to my
attention, but I still cant seem to get sound.
-Mike
On Mon, Dec 1, 2008 at 5:31 AM, bugmenot <[EMAIL PROTECTED]>
wrote:
> As you said Jaunty is still alpha and it is "normal" that there break
> things.
> But there were a few similar bugs the past days that apply to Intrepid as
> well.
>
> Can you enable sound again by setting PCM in "alsamixer -Dhw" to 100 or
> so?
>
> --
> Sound completely non-functional
> https://bugs.launchpad.net/bugs/303908
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> upon doing a distribution update to the Jaunty alpha a few days ago, my
> system's sound is completely non-functional. sound works fine in my
> dual-booted windows XP install, and it worked great in intrepid Ibex. The
> change happened immediately after rebooting after the update to the jaunty
> alpha.
>
> I have no idea what might be causing the problem out of the hundreds of
> package updates between the release of the alpha and today.
>
> please let me know how I can help track down this problem. The model of
> laptop that i use is used by over 500 students at my school, and slightly
> upgraded hardware by another 500 students. Our LUG ( of which i am a member)
> has a hard enough time convincing students to try Linux as it is, and
> non-functional sound would more than likely be a dealbreaker for some
> people, come the 9.04 release.
>
--
Sound completely non-functional
https://bugs.launchpad.net/bugs/303908
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
