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: Re: 2.6.31.x vs. rme vs. alsa 1.0.22?
Date: Tue, 23 Feb 2010 00:06:57 +0000 [thread overview]
Message-ID: <1266883617.3704.195.camel@localhost.localdomain> (raw)
In-Reply-To: <1266882689.3704.178.camel@localhost.localdomain>
On Mon, 2010-02-22 at 23:51 +0000, Fernando Lopez-Lezcano wrote:
> On Tue, 2010-02-16 at 17:58 -0800, Fernando Lopez-Lezcano wrote:
> > 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,
>
> This is what hdspmixer prints when I attempt to run it:
>
> ----
> $ hdspmixer
>
> HDSPMixer 1.6 - Copyright (C) 2003 Thomas Charbonnel <thomas@undata.org>
> This program comes with ABSOLUTELY NO WARRANTY
> HDSPMixer is free software, see the file COPYING for details
>
> Looking for HDSP cards :
> Card 0 : HDA Intel at 0xfe020000 irq 17
> Card 1 : RME Hammerfall DSP + Multiface at 0xc0000000, irq 16
> Multiface found !
> 1 Hammerfall DSP card found.
> Initializing default presets
> HwDep ioctl failed. Metering stopped
> ----
And this is what strace says:
----
open("/dev/snd/controlC1", O_RDONLY|O_CLOEXEC) = 5
fcntl64(5, F_SETFD, FD_CLOEXEC) = 0
ioctl(5, UI_DEV_CREATE, 0xbff6aef4) = 0
close(5) = 0
open("/dev/snd/hwC1D0", O_RDONLY|O_CLOEXEC) = 5
fcntl64(5, F_SETFD, FD_CLOEXEC) = 0
ioctl(5, 0x80044800, 0xbff6b270) = 0
ioctl(5, SNDRV_HDSP_IOCTL_GET_PEAK_RMS, 0xbff6b57c) = -1 EINVAL (Invalid
argument)
write(2, "HwDep ioctl failed. Metering sto"..., 37HwDep ioctl failed.
Metering stopped
) = 37
close(5) = 0
----
-- Fernando
> > 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?
>
> I have been trying to see if I can figure _anything_ out of this...
>
> A diff of 2.6.29 (last known working) against 2.6.31.12 reveals
> something that might have an influence on the problem:
>
> in snd_hdsp_create_hwdep there are two lines added:
>
> + hw->ops.open = snd_hdsp_hwdep_dummy_op;
> hw->ops.ioctl = snd_hdsp_hwdep_ioctl;
> + hw->ops.release = snd_hdsp_hwdep_dummy_op;
>
> And snd_hdsp_hwdep_dummy_op just returns 0...
>
> Other differences between the two files (not that many) seem irrelevant
> to me.
>
> I imagine this is what is causing the difference in behavior (hwdep
> fails). Any suggestions on what I could try to fix this?
>
> Thanks for any help!
>
> -- Fernando
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-02-23 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 1:58 2.6.31.x vs. rme vs. alsa 1.0.22? Fernando Lopez-Lezcano
2010-02-22 23:51 ` Fernando Lopez-Lezcano
2010-02-23 0:06 ` Fernando Lopez-Lezcano [this message]
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=1266883617.3704.195.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).