From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: sudden sound loss
Date: Thu, 10 Apr 2008 10:43:10 -0700 [thread overview]
Message-ID: <5bdc1c8b0804101043pdfacaeep2d6793d11ceac10@mail.gmail.com> (raw)
In-Reply-To: <47FE4C4F.4030100@ercbroadband.org>
On Thu, Apr 10, 2008 at 10:20 AM, Mark Haney <mhaney@ercbroadband.org> wrote:
>
> Mark Knecht wrote:
>
> > On Thu, Apr 10, 2008 at 9:49 AM, Mark Haney <mhaney@ercbroadband.org>
> wrote:
> > <SNIP>
> >
> > > I've only ever run alsamixer from the console. I've never used a gui to
> > > configure sound. It doesn't look muted in alsamixer.
> > >
> > >
> >
> > Again, did you actually delete /etc/asound.state and then run
> > alsamixer again to recreate it anew? When you run alsamixer in this
> > way once again make sure everything is unmuted and both master and PCM
> > volumes are up.
> >
> > If your version of Alsa changed through an update or this file becomes
> > corrupted then you can have some very strange results.
> >
> > Just for kicks what's in /proc/asound? Do the expected sound cards
> > show up? lsmod results look reasonable?
> >
> > Good luck,
> > Mark
> >
>
>
> I'm a total idiot. There was ONE option muted in alsa mixer that I over
> looked. Actually it wasn't overlooked so much that I /thought/ that setting
> had always been like that. I apologize to everyone for missing the obvious
> and wasting bandwidth and time. I'll try not to be a moron in the future.
>
> Sheesh.
>
<hehe> Glad to help.
I cannot even remember anymore how many times these setting have
fooled me. I use a lot of audio apps and they have a tendency to leave
some of these settings in somewhat unknown states so starting here
generally works for me.
Enjoy,
Mark
--
gentoo-amd64@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-04-10 17:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 11:43 [gentoo-amd64] sudden sound loss Mark Haney
2008-04-10 12:16 ` Raffaele BELARDI
2008-04-10 12:22 ` Mark Haney
2008-04-10 13:44 ` Raffaele BELARDI
2008-04-10 15:52 ` Chris Brennan
2008-04-10 12:45 ` Beso
2008-04-10 14:13 ` [gentoo-amd64] " Duncan
2008-04-10 14:30 ` Mark Knecht
2008-04-10 15:02 ` Duncan
2008-04-10 16:49 ` Mark Haney
2008-04-10 17:10 ` Mark Knecht
2008-04-10 17:20 ` Mark Haney
2008-04-10 17:43 ` Mark Knecht [this message]
2008-04-10 19:33 ` Duncan
2008-04-10 19:45 ` Mark Knecht
2008-04-11 8:14 ` Beso
2008-04-12 2:29 ` Duncan
2008-04-11 11:16 ` Mark Haney
2008-04-11 11:33 ` Raffaele BELARDI
2008-04-11 13:24 ` Mark Knecht
2008-04-11 14:33 ` Raffaele BELARDI
2008-04-11 15:32 ` Mark Knecht
2008-04-12 16:32 ` Duncan
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=5bdc1c8b0804101043pdfacaeep2d6793d11ceac10@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-amd64@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