From: Zach Forrest <zach@disinformation.ca>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] alsa 0.9
Date: Mon, 20 May 2002 10:01:08 -0700 [thread overview]
Message-ID: <3CE92BD4.6020904@disinformation.ca> (raw)
In-Reply-To: 5.1.0.14.0.20020518143443.00b83a10@imap.wpi.edu
Have you tried using alsamixer? I think amixer is for use with the older
versions of alsa.
zach
Chuck Haines wrote:
> I am having the damndest time with alsa 0.9. I have installed
> everything that is suppose to be installed,
> alsa-lib,alsa-driver,alsa-utils,alsa-tools. I have edited the config
> files like I was told. When i run /etc/init.d/alsasound start and type
> lsmod, I can see that all the modules are there and I get no errors.
> However, when I try to run amixer as root or as my user, it keeps sef
> faulting (amixer that it). I have checked the perms in /dev/snd/ and
> /dev/sound and both of the directories have perms crw-rw---- crypto
> audio. Crypto is my user (I have no idea why the perms aren't root
> audio like I have devfs.conf set up to do). I have tried with both
> these settings and crw-rw---- root audio and amixer still seg faults.
> My user is part of the audio group.
>
> anyone have any ideas?
>
> Thanks,
>
> -----------------------------------------------------------------------
> | Chuck Haines | AIM: CyberGrex |
> | WPILA Lab Manager | Yahoo: CyberGrex_27 |
> | http://www.wpila.org | ICQ: 3707881 |
> | GDC Webmaster | http://gdc.wpi.edu |
> ------------------------------------------------------------------------
> "Geek by nature, Linux by choice."
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
next prev parent reply other threads:[~2002-05-20 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-18 18:38 [gentoo-dev] alsa 0.9 Chuck Haines
2002-05-20 17:01 ` Zach Forrest [this message]
2002-05-24 6:18 ` Miguel S. Filipe
2002-05-23 0:41 ` José Fonseca
2002-05-23 4:53 ` hanez
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=3CE92BD4.6020904@disinformation.ca \
--to=zach@disinformation.ca \
--cc=gentoo-dev@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