From: James Courtier-Dutton <James@superbug.co.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>,
Takashi Iwai <tiwai@suse.de>,
Arnaud Patard <arnaud.patard@rtp-net.org>,
Mikael Magnusson <mikaelmagnusson@glocalnet.net>,
Peter Zubaj <pzad@pobox.sk>
Subject: Re: Fix emu10k1 breakages in kernel 2.6.12
Date: Sat, 02 Jul 2005 23:30:25 +0100 [thread overview]
Message-ID: <42C71581.4070504@superbug.co.uk> (raw)
In-Reply-To: <1120328091.2196.16.camel@mindpipe>
Lee Revell wrote:
>
> Right, but if the name does not match, alsactl cannot restore the
> previous mixer settings, so the mixer is reset to the default state, ie
> no sound.
>
Ok, which name should we be using here?
cat /proc/asound/cards
0 [Audigy2 ]: Audigy2 - Audigy 4 PRO [SB0380]
Audigy 4 PRO [SB0380] (rev.4, serial:0x20071102) at
0x9000, irq 23
1 [Audigy2_1 ]: Audigy2 - Audigy 2 Value [SB0400]
Audigy 2 Value [SB0400] (rev.0, serial:0x10011102)
at 0x9400, irq 17
2 [CA0106 ]: CA0106 - CA0106
Live! 7.1 24bit [SB0410] at 0x8400 irq 21
3 [CA0106_1 ]: CA0106 - CA0106
AudigyLS [SB0310] at 0x8800 irq 22
But alsactl asound.state uses the following names:
state.SB0400 {
state.SB0240 {
state.SB0380 {
state.CA0106 {
state.Audigy2 {
If I clear asound.state, I now get:
state.Audigy2 {
state.Audigy2_1 {
state.CA0106 {
state.CA0106_1 {
This must have been a change to alsactl. I think that using Audigy2_1
etc. is a much better idea than using something like SB0400.
I don't believe my changes to emu10k1 caused this to change. It was
something independent that changed.
James
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-02 22:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 3:08 Fix emu10k1 breakages in kernel 2.6.12 Lee Revell
2005-07-02 4:56 ` [stable] " Greg KH
2005-07-02 5:45 ` Lee Revell
2005-07-02 5:52 ` Greg KH
2005-07-02 21:15 ` Lee Revell
2005-07-02 10:34 ` James Courtier-Dutton
2005-07-02 18:14 ` Lee Revell
2005-07-02 22:30 ` James Courtier-Dutton [this message]
2005-07-02 23:20 ` Lee Revell
2005-07-02 23:41 ` Lee Revell
2005-07-02 22:46 ` James Courtier-Dutton
2005-07-02 23:12 ` Lee Revell
2005-07-05 15:33 ` Lee Revell
2005-07-05 15:40 ` Takashi Iwai
2005-07-05 15:41 ` Lee Revell
2005-07-05 15:45 ` Takashi Iwai
2005-07-05 16:16 ` James Courtier-Dutton
2005-07-05 16:22 ` Lee Revell
2005-07-05 16:31 ` Takashi Iwai
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=42C71581.4070504@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=arnaud.patard@rtp-net.org \
--cc=mikaelmagnusson@glocalnet.net \
--cc=pzad@pobox.sk \
--cc=rlrevell@joe-job.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.