From: Alien <alien999999999@users.sourceforge.net>
To: alsa-devel@lists.sourceforge.net
Cc: Lee Revell <rlrevell@joe-job.com>, Alexandr <spiro@demiart.ru>
Subject: Re: Re: About my Live! 5.1
Date: Tue, 6 Dec 2005 20:12:02 +0100 [thread overview]
Message-ID: <200512062012.17768.alien999999999@users.sourceforge.net> (raw)
In-Reply-To: <1133128226.19505.2.camel@mindpipe>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
Op zondag 27 november 2005 22:50, schreef Lee Revell:
> On Sun, 2005-11-27 at 21:20 +0100, Alien wrote:
> > Op zaterdag 26 november 2005 19:32, schreef Lee Revell:
> > > On Sat, 2005-11-26 at 10:40 +0100, Alien wrote:
> > > > I too have the SB0220
> > >
> > > Do you have the same problem with the mixer as Alexandr?
> >
> > no, but then i have an old CVS version and i didn't apply the patch.
> >
> > more than that, it's my second soundcard, but 'alsamixer -c 1' works for
> > me, i've used it alot, maybe he should do an 'alsactl store' ?
> >
> > [alien@queen ~]$ cat /proc/asound/version
> > Advanced Linux Sound Architecture Driver Version 1.0.10rc1.
> > Compiled on Oct 15 2005 for kernel 2.6.11-12mdk.
>
> I believe there's something weird about the SB022x (multiple AC97
> codecs?) that the driver does not handle properly. The changelog for
> the kX driver 3538 mentions "SB022x fixes".
what is the kX driver and when was this changelog and was this change
introduced in alsa and if so, when?
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-06 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43875FC3.9040408@demiart.ru>
[not found] ` <1132950843.20390.62.camel@mindpipe>
2005-11-26 6:33 ` About my Live! 5.1 Alexandr
2005-11-26 9:40 ` Alien
2005-11-26 18:32 ` Lee Revell
2005-11-27 20:20 ` Alien
2005-11-27 21:50 ` Lee Revell
2005-12-06 19:12 ` Alien [this message]
2005-12-06 19:19 ` Lee Revell
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=200512062012.17768.alien999999999@users.sourceforge.net \
--to=alien999999999@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
--cc=spiro@demiart.ru \
/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