Ubuntu
alsa-driver package

  1. Bug #296738
  2. Comment #24

Comment 24 for bug 296738

Revision history for this message
Mackenzie Morgan (maco.m) wrote :

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)