[Jaunty] Sound muted on boot

No sound after yesterday's updates. IBM Thinkpad R31 with Multimedia audio controller [0401]: Intel Corporation 82801CA/CAM AC'97 Audio Controller [8086:2485] (rev 02)

"Was working fine on Intrepid, Jaunty...."

Jerry

I have it here also with jaunty 64bit , amd64x2 and nvidia mcp51 audio . If I go to system>prefs>sound and try different settings it does not help , no sound on playback or test .

Sound is now working again. Right clicked on speaker - Volume Control: Nvidia CK804-all settings set to off/minimum under Playback tab. Adjusted the sliders and I have sound again. CD works fine, system sounds are fine.

I also had a look under Volume Control, but all mine were on/full, and still no sound, so not quite "working again."

I had this bug for about 24 hours interesting to note that I actually had sound at the login screen, which is weird but anyway all is resolved and sound is back to normal after I updated my packages a few minutes ago. For me at least its fixed.

Justed booted into 9.04 from 8.0.4.1. Audio found to be muted and volume set to minimum after boot (even though previous settings were left at mid-range).

the bug is still here on my sys as of nov 12, 11 PM east coast US , tried all fixes suggested here no help , the error msg when I go to sys>prefs>sound and test sound is .
audiotestsrc wave=sine freq=512!
audioconvert! audioresample ! gconfaudiosink:
could not open audio device for playback

This fault is also being reported in the Ubuntuforums as occurring in Intrepid.

I've found some information in my user.log that may be of use.

Audio not working with T61p 6457-7WU either. Installed Jaunty from today's daily, and have installed whatever few updates became available so far.

Just installed Jaunty Alpha 1 today

It doesn't appear to be saving sound settings.

Every reboot and the sound is muted.

And I've found something else.

my 5.1 set is totally messed up. There is only sound on the front left speaker and surround left.

I even try the paconfig (Pulseaudio configuration utility) http://ubuntuforums.org/showthread.php?t=759147

It always did the trick for me since Hardy and nothing happens.

PS: I also just noticed that the first sound on the GDM prompt my subwoofer actually is working. But after login the sound is muted. Pulse Audio Volume Meter show all channels working, except LFE, but that's far from reality.

http://xs.to/xs.php?h=xs133&d=08476&f=pulseaudio_volume_meter775.png

My soundcard is a SB LIve 5.1

On every boot, all my sound levers get down to zero, and the mute is On.
This is very annoying

$ apt-cache show alsa-base
Package: alsa-base
Section: sound
Architecture: all
Source: alsa-driver
Version: 1.0.18.dfsg-1ubuntu2

$ apt-cache show pulseaudio
Package: pulseaudio
Section: sound
Installed-Size: 1820
Architecture: amd64
Version: 0.9.13-1ubuntu3

Changing package from alsa-driver to linux, as per DebuggingSoundProblems on the wiki, since the user does not state having manually compiled a driver.

Could you please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems ?

And is this *only* after reboots, or does this occur when you log out and log back in as well? If it occurs from starting a new X session, I think it's more likely to do with PulseAudio than the driver.

$ cat /proc/asound/cards
 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xf3ff8000 irq 21

loging off and logging on did not affected my sound volume! all controls were left as they were before ending the session

The problem seems at least partly to be a PulseAudio problem maybe a consecutive problem though.

The problem as mentioned earlier here is that some sound channels are muted and most handles reset after a reboot but not at a re-login. After adjusting the main sound handle then Totem sound works but not e.g system sound, vlc sound, etc. Using the mouse pointing at a system sound e.g in directory /usr/share/sounds/ubuntu/stereo works but not playing them under System/Preferences/Sounds.

However after adjusting the main handle for sounds AND removing the directory ~/.pulse everything seems to work until a reboot or re-login where this directory is recreated and thus has to be removed (workaround) again to get all sounds and sound apps working.

No driver has been manually configured for sound (or for Hardy 8.0.4.1). Sound works fine in Hardy with no errors. Logging off and on again is not a problem as sound settings are saved between sessions. There is no switch for audio as the sound is integral to the monitor and the cable is fine. Sound works fine when I switch to Hardy, but not when I try Jaunty.

$ cat /proc/asound/cards in Hardy and Jaunty.
0 [CK804 ]: NFORCE - NVidia CK804
                      NVidia CK804 with ALC655 at irq 22

My alsa-info file for Jaunty is located at http://www.alsa-project.org/db/?f=4a74e5f973593d4dd29c7c3337d18b52671faedb

There are a few differences between the alsa-base files for Jaunty and Hardy - I have not made changes to either as Hardy worked as is and I expected Jaunty to work the same (these are attached as alsa-base-jaunty.txt and alsa-base-HH804.txt).

My version of Jaunty was originally pre-Alpha1 and I have now installed Alpha1 2.6.27-7 64 bit which gives me the same results.

Note that this issue does not seem to be pulseaudio related to me. I've removed most parts of it (except: gstreamer0.10-pulseaudio, libpulse-browse0, libpulse-mainloop-glib0 and libpulse0) and I experience the same issue: no sound after booting, unmuting the "Front" control temporarily fixes the issue until the next reboot.

On Mon, 2008-11-24 at 19:01 +0000, Kjell Braden wrote:
> Note that this issue does not seem to be pulseaudio related to me. I've
> removed most parts of it (except: gstreamer0.10-pulseaudio, libpulse-
> browse0, libpulse-mainloop-glib0 and libpulse0) and I experience the
> same issue: no sound after booting, unmuting the "Front" control
> temporarily fixes the issue until the next reboot.

Do you have a ~/.pulse anyway? If you remove it with PA uninstalled,
then log out and back in, is it recreated?

The pulseaudio executable fails which is also logged in my user.log. Another way to find out is e.g. to use the command
pulseaudio --dump-modules
to list the PA's modules. This gives the following initial output:

I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root priviliges.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
N: main.c: Called SUID root and real-time/high-priority scheduling was requested in the configuration. However, we lack the necessary priviliges:
N: main.c: We are not in group 'pulse-rt' and PolicyKit refuse to grant us priviliges. Dropping SUID again.
N: main.c: For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
W: main.c: High-priority scheduling enabled in configuration but not allowed by policy.
W: ltdl-bind-now.c: Failed to find original dlopen loader.

The file pulseaudio has the suid-bit set but still fails so it seems that the statement "For enabling real-time scheduling please acquire the appropriate PolicyKit priviliges" is what is missing.

I'm having this problem too. My master and PCM channels are fine, but the rest (front etc) are muted each boot.

Current suspect: alsactl store and/or restore

Been working on this with Bugabundo, and for the sake of archiving tests, I'm posting what we've checked:

* On boot, before logging into GDM, all but Master are 0% and mute.
* After booting, try changing settings and running "PULSE_INTERNAL=0 alsactl store" as root in TTY. Log into GNOME and settings persist. Reboot, and it's still back to 0% and mute.
* Purge alsa-utils and reinstall to ensure a default /etc/init.d/alsa-utils ...still 0% and mute after reboot.

Can someone please:
1. change mixer values to something that lets them hear sound
2. run "sudo -i" followed by "PULSE_INTERNAL=0 alsactl store"
3. check /var/lib/alsa/asound.state to see if it was stored (or just attach it to the bug, and I'll look later)
4. run "PULSE_INTERNAL=0 alsactl restore"
5. Are mixer values now 0 + mute? (so, did it reset everything?) Or are they unchanged (it did nothing at all)
If unchanged (being very very careful):
6. as root, edit /var/lib/alsa/asound.state *very* slightly. For example, change "Front Playback Volume"'s value.0 and value.1 to some number within the comment.range listed.
7. run "PULSE_INTERNAL=0 alsactl restore"
8. Check the mixer values. Same as before editing the file? (file not being read right) Or are the updates done to the file reflected in the mixer? (file is being read just fine)

On Tuesday 25 November 2008 12:17:21 Mackenzie Morgan wrote:
> Been working on this with Bugabundo, and for the sake of archiving tests

Thank you for all the hard work.

> Can someone please:
> 1. change mixer values to something that lets them hear sound

Done.

> 2. run "sudo -i" followed by "PULSE_INTERNAL=0 alsactl store"

Done.

> 3. check /var/lib/alsa/asound.state to see if it was stored (or just attach it to the bug, and I'll look later)

Done.
 control.1 {
  comment.access 'read write'
  comment.type INTEGER
  comment.count 2
  comment.range '0 - 31'
  comment.dbmin -4650
  comment.dbmax 0
  iface MIXER
  name 'Front Playback Volume'
  value.0 13
  value.1 26
 }

> 4. run "PULSE_INTERNAL=0 alsactl restore"

Done.

> 5. Are mixer values now 0 + mute? (so, did it reset everything?) Or are they unchanged (it did nothing at all)

It was unchanged.

> If unchanged (being very very careful):
> 6. as root, edit /var/lib/alsa/asound.state *very* slightly. For example, change "Front Playback Volume"'s value.0 and value.1 to some number within the comment.range listed.

Done. I changed left with right value.
 control.1 {
  comment.access 'read write'
  comment.type INTEGER
  comment.count 2
  comment.range '0 - 31'
  comment.dbmin -4650
  comment.dbmax 0
  iface MIXER
  name 'Front Playback Volume'
  value.0 26
  value.1 13
 }

> 7. run "PULSE_INTERNAL=0 alsactl restore"
> 8. Check the mixer values. Same as before editing the file? (file not being read right) Or are the updates done to the file reflected in the mixer? (file is being read just fine)

Mixer was updated.

--
BUGabundo :o)
(``-_-´´) http://LinuxNoDEI.BUGabundo.net && Ubuntu LoCoTeam Portugal http://ubuntu-pt.org
Linux user #443786 GPG key 1024D/A1784EBB

I have the same problem, and when I try to lower or increase the volume level using the buttons in my laptop it doesn't work i have to do it using the Volume Control Applet

Mackenzie Morgan schrieb:
> Do you have a ~/.pulse anyway? If you remove it with PA uninstalled,
> then log out and back in, is it recreated?
>=20

Oh yes, indeed. It contains one symbolic link to one empty directory in
/tmp:

$ ls -ld ~/.pulse/*
lrwxrwxrwx 1 k k 23 2008-11-25 15:48
/home/k/.pulse/8abcecd60aa72f7d61c512e5481c6ab2:runtime ->
/tmp/pulse-JHUoUZm8zSky

Olá LinkinXp e a todos.

On Tuesday 25 November 2008 15:05:27 LinkinXp wrote:
> I have the same problem, and when I try to lower or increase the volume
> level using the buttons in my laptop it doesn't work i have to do it
> using the Volume Control Applet

LinkinXp thats another bug... not this one! this one is about the controls being muted on boot.
Not havingthe multimedia keys act, is a totally different thing

--
BUGabundo :o)
(``-_-´´) http://LinuxNoDEI.BUGabundo.net && Ubuntu LoCoTeam Portugal http://ubuntu-pt.org
Linux user #443786 GPG key 1024D/A1784EBB

My file /var/lib/alsa/asound.state didn't exist so I copied the one for Intrepid (same machine) and modified it manually then restored settings using "PULSE_INTERNAL=0 alsactl restore" and it works! But the settings do not survive a reboot. Furthermore, any changes made in the Volume Control Panel does not update the file asound.state so that has do be done manually.

Moreover, pulseaudio is running "native" which gives a distorted system sound and for some other apps like vlc. To get around this I first deleted the native executable in the subdirectory to ~/.pulse that kills pulseaudio running in the background. I finally solved this problem simply by uncomment the two lines

#load-module module-alsa-sink
#load-module module-alsa-source device=hw:1,0

in the file /etc/pulse/default.pa to force load of those audio drivers statically as it seems that "module-hal-detect" does not work properly here. But this is maybe not an issue for this bug report but might turn up to be a consequence of it.

On Tue, 2008-11-25 at 16:00 +0000, BUGabundo wrote:
> Olá LinkinXp e a todos.
>
> On Tuesday 25 November 2008 15:05:27 LinkinXp wrote:
> > I have the same problem, and when I try to lower or increase the volume
> > level using the buttons in my laptop it doesn't work i have to do it
> > using the Volume Control Applet
>
> LinkinXp thats another bug... not this one! this one is about the controls being muted on boot.
> Not havingthe multimedia keys act, is a totally different thing

That's probably an acpi bug.

Thank you Bugabundo. It *seems* like alsactl store and restore are
functional, in that case.

Mackenzie,

> is this *only* after reboots, or does this occur when you
> log out and log back in as well?

For me, only after a reboot. Logging out and back in has its own problems (X won't restart properly, and reverts to a default 800x600 display until I reboot), but audio settings are preserved.

$ cat /proc/asound/cards
 0 [Intel ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xfe220000 irq 17

> 1. change mixer values to something that lets them hear sound

Done.

> 2. run "sudo -i" followed by "PULSE_INTERNAL=0 alsactl store"

Done.

> 3. check /var/lib/alsa/asound.state to see if it was stored
> (or just attach it to the bug, and I'll look later)

Done, and will attach.

> 4. run "PULSE_INTERNAL=0 alsactl restore"
> 5. Are mixer values now 0 + mute? (so, did it reset everything?)
> Or are they unchanged (it did nothing at all)

Unchanged, as would be desired.

> 6. as root, edit /var/lib/alsa/asound.state *very* slightly.
> 7. run "PULSE_INTERNAL=0 alsactl restore"
> 8. Check the mixer values. Same as before editing the file?

Worked fine. Changed MASTER VOLUME from 28 to 25, and saw that reflected.

Thanks Noel, but the bug's been figured out now. alsactl works
fine...it just happens to have ended up in the wrong place so that the
init script couldn't find it. That's why it's been marked a duplicate.
And a fix was released a few minutes ago. It should propagate to all of
the mirrors in the next few hours.

On Tuesday 25 November 2008 22:08:20 Mackenzie Morgan wrote:
> It seems like alsactl store and restore are functional, in that case.

So why aint it getting restored on boot, Mac?

--
BUGabundo :o)
(``-_-´´) http://LinuxNoDEI.BUGabundo.net && Ubuntu LoCoTeam Portugal http://ubuntu-pt.org
Linux user #443786 GPG key 1024D/A1784EBB

On Wed, 2008-11-26 at 09:15 +0000, BUGabundo wrote:
> *** This bug is a duplicate of bug 299093 ***
> https://bugs.launchpad.net/bugs/299093
>
> On Tuesday 25 November 2008 22:08:20 Mackenzie Morgan wrote:
> > It seems like alsactl store and restore are functional, in that case.
>
> So why aint it getting restored on boot, Mac?

Because of the bug that this is a duplicate of :P The init script is
looking for it in a different place than where it is. Dan figured it
out based on the fact that we could prove it worked on its own.

sorry about that.
hadnt read the entire bug mail...

Its now fixed.

@Bowmore can that native mode be the cause of bug #295519 ?

> @Bowmore can that native mode be the cause of bug #295519 ?

Thanks BUGabundo, I'll try to contribute to that bug as it seems to be the same problem as I experienced before my workaround by forcing alsa modules to load.