public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] after emerge -Du world - - no sound no errors
Date: Fri, 19 Aug 2005 15:15:43 +1200	[thread overview]
Message-ID: <20050819151238.34CF.NICK@rout.co.nz> (raw)
In-Reply-To: <4304EB5D.9020609@planet.nl>


On Thu, 18 Aug 2005 22:11:09 +0200
Holly Bostick wrote:

> Idea #1: Put alsasound in default, rather than boot runlevel. There is
> no use for sound in the boot runlevel, and having it there often causes
> (weird, inexplicable) problems.

boot is what the gentoo alsa docs say to do, although they aren't always
right for all situations

> 
> Idea #2: might something have gone wonky with your mixer settings?

very very likely, and perhaps tied in with:


Idea #3

new config options in /etc/conf.d/alsasound: you probably want to enable
SAVE_ON_STOP and RESTORE_ON_START

nick@sf /etc $ less /etc/conf.d/alsasound
# ENABLE_OSS_EMUL:
# Do you want to enable in-kernel oss emulation?
# no - Do not load oss emul drivers
# yes - Load oss emul drivers if they're found

ENABLE_OSS_EMUL="yes"

# RESTORE_ON_START:
# Do you want to restore your mixer settings?  If not, your cards will be
# muted.
# no - Do not restore state
# yes - Restore state

RESTORE_ON_START="yes"

# SAVE_ON_STOP:
# Do you want to save changes made to your mixer volumes when alsasound
# stops?
# no - Do not save state
# yes - Save state

SAVE_ON_STOP="yes"

-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-19  3:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 20:01 [gentoo-user] after emerge -Du world - - no sound no errors maxim wexler
2005-08-18 20:11 ` Holly Bostick
2005-08-19  3:15   ` Nick Rout [this message]
2005-08-19 15:41   ` maxim wexler
2005-08-19 16:48     ` Willie Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050819151238.34CF.NICK@rout.co.nz \
    --to=nick@rout.co.nz \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox