From: Collins Richey <erichey2@home.com>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] sound for esssolo1 (solved)
Date: Sat Jul 7 15:30:02 2001 [thread overview]
Message-ID: <20010707153925.0cc12365.erichey2@home.com> (raw)
In-Reply-To: <20010707153228.246a0fe0.erichey2@home.com>
On Sat, 7 Jul 2001 15:32:28 +0000 Collins Richey <erichey2@home.com> wrote:
> On Sat, 07 Jul 2001 21:16:31 +0200 AGottinger@t-online.de (Achim Gottinger) wrote:
>
> > Collins Richey wrote:
> > >
> > > I'm confused. On every other distro that I've used (Mandrake, Caldera, Vectorlinux - all all 2.4.x kernels), all I have to do to get sound for xfce, etc., is to compile the esssolo1 kernel module and do a modprobe (or equivalent at boot time) for esssolo1. The esssolo1 and soundcore modules get loaded, and the sound card works.
> > >
> > > Why won't this work on Gentoo? I'm using the identical kernel compile that works on every other distro. The modules get loaded, but sound is dead.
> > >
> > I think you need the play binary coming with sox for xfce.
> > If not try to fine the sound player binarie used by xfce and run it on
> > the console.
> >
>
> I've submitted my question to xfce as well, but no definite answer yet. One thing for sure, xfce definitely requires sox, so why wasn't sox merged when I merged xfce? I had to do it manually.
OK, the final answer is: /dev/dsp needs 666 permission, and xfce needs a dependancy for sox.
--
Collins Richey
Denver Area
Gentoo_rc5 XFCE
next prev parent reply other threads:[~2001-07-07 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 14:07 [gentoo-dev] sound for esssolo1 Collins Richey
2001-07-07 14:36 ` Achim Gottinger
2001-07-07 14:46 ` Collins Richey
2001-07-07 15:23 ` Collins Richey
2001-07-07 15:30 ` Collins Richey [this message]
2001-07-07 19:43 ` [gentoo-dev] sound for esssolo1 (solved) Achim Gottinger
2001-07-07 19:57 ` Collins Richey
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=20010707153925.0cc12365.erichey2@home.com \
--to=erichey2@home.com \
--cc=gentoo-dev@cvs.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