From: "Ducky Z." <duckyhatezchat@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ALSA: All modules loaded, mixer unmuted, still no sound
Date: Mon, 27 Feb 2006 15:47:09 +0630 [thread overview]
Message-ID: <de2610f90602270117n30ffcb7ld3840ca80f1cf30f@mail.gmail.com> (raw)
In-Reply-To: <200602262257.49951.bss03@volumehost.net>
Hello,
I've removed kernel support for ALSA and using alsa-driver instead.
Still no luck and same error. And I still don't have /etc/asound.conf
or ~/.asoundrc. Is that a problem?
Thanks.
On 2/27/06, Boyd Stephen Smith Jr. <bss03@volumehost.net> wrote:
> On Sunday 26 February 2006 22:46, Zac Slade <krakrjak@volumehost.net> wrote
> about 'Re: [gentoo-user] ALSA: All modules loaded, mixer unmuted, still no
> sound':
> > On Sunday 26 February 2006 22:17, Ducky Z. wrote:
> > > I'm using the modules provided by the kernel, which is 2.6.15.
> > > alsa-lib is 1.0.10.
> >
> > This should be fine.
>
> Hrm, is alsa-lib 1.0 backwards compatible to 0.9? 'Cause the kernel
> shipped with 0.9 support for a while and my kernel now has to have an
> option to provide the 0.9 abi/api.
>
> You could try either upgrading your kernel or downgrading your alsa-lib.
> Or, you could abandon the kernel-provide modules and use alsa-drivers.
>
> > > When I aplay a file, it shows:
> > >
> > > ALSA lib pcm_direct.c:900:(snd_pcm_direct_initialize_slave) unable to
> > > install hw params
> > > ALSA lib pcm_dmix.c:831:(snd_pcm_dmix_open) unable to initialize slave
> > > aplay: main:544: audio open error: Inappropriate ioctl for device
> >
> > Hrm.... Is this being done as root? I think your /etc/asound.conf file
> > might need some help. I'm not sure here, but it might not be able to
> > play because the wrong information is in the asound.conf file.
>
> Yeah, try as root and if that works, check permissions on stuff
> in /dev/sound.
>
> If you can get the 1.0 alsa-lib to work with your kernel, you can probably
> blow away your asound.conf file anyway. The move to 1.0 made dmix
> automatic for devices that don't do hw mixing.
>
> --
> "If there's one thing we've established over the years,
> it's that the vast majority of our users don't have the slightest
> clue what's best for them in terms of package stability."
> -- Gentoo Developer Ciaran McCreesh
> --
> gentoo-user@gentoo.org mailing list
>
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-27 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 8:20 [gentoo-user] ALSA: All modules loaded, mixer unmuted, still no sound Ducky Z.
2006-02-26 8:38 ` Zac Slade
2006-02-26 8:50 ` Ducky Z.
2006-02-26 9:05 ` Zac Slade
2006-02-26 9:59 ` Ducky Z.
2006-02-26 14:41 ` Boyd Stephen Smith Jr.
2006-02-27 4:17 ` Ducky Z.
2006-02-27 4:46 ` Zac Slade
2006-02-27 4:57 ` Ducky Z.
2006-02-27 4:57 ` Boyd Stephen Smith Jr.
2006-02-27 9:17 ` Ducky Z. [this message]
2006-02-27 9:29 ` Ducky Z.
2006-02-27 14:41 ` Boyd Stephen Smith Jr.
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=de2610f90602270117n30ffcb7ld3840ca80f1cf30f@mail.gmail.com \
--to=duckyhatezchat@gmail.com \
--cc=gentoo-user@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