From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: sudden sound loss
Date: Fri, 11 Apr 2008 06:24:27 -0700 [thread overview]
Message-ID: <5bdc1c8b0804110624y4458b711w3c83f640d1da317e@mail.gmail.com> (raw)
In-Reply-To: <1207913580.6155.26.camel@ws2912.agr.st.com>
On Fri, Apr 11, 2008 at 4:33 AM, Raffaele BELARDI
<raffaele.belardi@st.com> wrote:
> On Fri, 2008-04-11 at 07:16 -0400, Mark Haney wrote:
> > Well for me, the trick in alsamixer is to look at the bottom of each
> > 'bar graph' and see if it has 'MM' in it instead of the infinity symbol.
> > I am pretty sure that's a standard set of symbols for that. The 'MM'
> > is for muted' and the infinity symbol is for unmuted.
> >
>
> I have a question related to alsamixer, although not related to the
> subject.
>
> On my box with VIA chipset, alsamixer has a 'spread front to surround'
> control that duplicates the same signal on front and surround output
> jacks.
>
> There is no similar control on the box with the NVIDIA 430. Is it a
> configuration problem on my side? Anybody know how could I obtain the
> same effect without that control?
>
> raf
>
The controls shown in alsamixer are based on hardware features
revealed by the driver. My guess is that the nvidia 430 doesn't have
this feature, or it's driver hasn't turned it on by default. Possibly
there is a module parameter switch that shows up with modinfo that you
could play with?
If you think the hardware supports this feature but the driver isn't
enabling it then your best bet would be to contact the alsa developers
to look for some support. (Or do it yourself if you have the skill
set!)
cheers,
Mark
--
gentoo-amd64@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-04-11 13:24 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
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 [this message]
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=5bdc1c8b0804110624y4458b711w3c83f640d1da317e@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