Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: why is my sound always muted on startup?

  1. #11
    Join Date
    Aug 2010
    Location
    Arizona USA
    Beans
    2,870
    Distro
    Ubuntu Development Release

    Re: why is my sound always muted on startup?

    Hrm... That's interesting!

    I'm dual-booting 10.04.1 LTS and 10.10 Alpha 3 on this machine.

    Lucid doesn't have the "muted on startup" problem. Soooo...

    I simply renamed the alsa-utils file in Maverick and copy n' pasted the one from Lucid. End of problem!

    The interesting thing is, I compared the 2 alsa-utils files, and the only difference is:

    Code:
    $ diff /sbin/alsa-utils /sbin/alsa-utils-orig 
    384a385
    > 	mute_and_zero_levels "$TARGET_CARD" || EXITSTATUS=1
    A single (missing) line is the only difference.

    That was an easy fix!

  2. #12
    Join Date
    Aug 2010
    Location
    Arizona USA
    Beans
    2,870
    Distro
    Ubuntu Development Release

    Re: why is my sound always muted on startup?

    Quote Originally Posted by pilinux View Post
    Always happens during testing.
    This is *probably* intentional.

    Thinking about it a little...

    A dev release is likely to have problems with the audio system, as they are sorting out drivers, config files, and such.

    I'm using a very modest amplifier/speaker setup on this machine, however, I could just as easily have it hooked up to my $8000 Klipschorns and Harmon/Kardon amp (110dB @ 1 watt input).

    LoL! I would be thoroughly miffed if I lost my hearing, or gave my wife a heart attack @ 3:30 AM, because of an errant update.

    Perusing the alsa-utils file, it would appear that the 'mute_and_zero_levels' section is called after an error. If I'm reading it correctly, when an error is detected in the sound system, it zeroes out (and mutes) the volume, restarts the sound card, and exits.

    This would correspond with the 'muting problem' that I've been having with Maverick.

    In my case, the volume didn't always mute at startup. When it was muted at startup, I would occasionally see a PulseAudio error @ Plymouth. The error flashes so quickly, I wasn't able to read the whole thing. And, AFAIK, Plymouth doesn't have an error log. But, I'm *guessing* that when the muting occurs, it's because of a sound system error, and it's intentional, on the part of the devs.

    Anyway, I *think* you're correct! It makes sense...

  3. #13
    Join Date
    Jun 2007
    Beans
    13,610

    Re: why is my sound always muted on startup?

    I can't see this as being intentional, but have been surprised before.
    First the changelog indicates the opposite intention
    alsa-utils (1.0.23-0ubuntu1) maverick; urgency=low
    ..........
    + Stop muting on reboot/shutdown
    But the issue does seem directly related to alsa-utils, not if it is installed which doesn't cause this.
    With the line in pulse.pa uncommented and alsa-utils installed sound is fine on a reboot (not muted or set to 0

    Once alsamixer is run though, upon reboot sound will be muted and or level sound set to zero.

    The line could be removed or set to (possibly the intention
    mute_and_zero_levels "$TARGET_CARD" || EXITSTATUS=0

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •