From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: The Linux Audio Developers' Mailing List
<linux-audio-dev@lists.linuxaudio.org>
Cc: alsa-devel@alsa-project.org
Subject: 2.6.31.x vs. rme vs. alsa 1.0.22?
Date: Tue, 16 Feb 2010 17:58:02 -0800 [thread overview]
Message-ID: <1266371882.3361.40.camel@localhost.localdomain> (raw)
Hey, has anyone been seeing strange behavior from this combination?
kernel 2.6.31.x rt20 + alsa 1.0.22 userland
RME card (pcmcia card + multiface)
hdspmixer is not doing the right thing (does not initialize the card in
a way in which playback works), it does not see the hwdep interface (or
something like that) and disables metering, alsamixer even segfaults
when I reach the end of the controls listed. Plain weird. Smells like
something changed deep in the kernel that makes alsa-lib very unhappy.
Alsa-tools rebuilt from source does not make a difference.
Weirdness goes away when I boot into 2.6.29.6 rt23...
Is there anything in alsa-* that depends on which _kernel_ is available
at compile time?
-- Fernando
next reply other threads:[~2010-02-17 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 1:58 Fernando Lopez-Lezcano [this message]
2010-02-22 23:51 ` 2.6.31.x vs. rme vs. alsa 1.0.22? Fernando Lopez-Lezcano
2010-02-23 0:06 ` Fernando Lopez-Lezcano
2010-02-23 0:16 ` Fernando Lopez-Lezcano
2010-02-23 0:20 ` Fernando Lopez-Lezcano
[not found] ` <1266884449.3704.214.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-23 20:48 ` [LAD] [alsa-devel] " Fernando Lopez-Lezcano
[not found] ` <1266958133.2507.234.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-23 21:22 ` Paul Davis
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=1266371882.3361.40.camel@localhost.localdomain \
--to=nando@ccrma.stanford.edu \
--cc=alsa-devel@alsa-project.org \
--cc=linux-audio-dev@lists.linuxaudio.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;
as well as URLs for NNTP newsgroup(s).