From: Lee Revell <rlrevell@joe-job.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: j4K3xBl4sT3r <jakexblaster@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel config problem between 2.4.x to 2.6.x!
Date: Thu, 16 Mar 2006 14:06:07 -0500 [thread overview]
Message-ID: <1142535968.9395.7.camel@mindpipe> (raw)
In-Reply-To: <20060316112523.GA3078@elf.ucw.cz>
On Thu, 2006-03-16 at 12:25 +0100, Pavel Machek wrote:
> On Po 13-03-06 13:06:35, Lee Revell wrote:
> > On Mon, 2006-03-13 at 08:42 -0300, j4K3xBl4sT3r wrote:
> > > 1. before, the mouse worked fine. now, it doesnt works
> >
> > Probably /dev/input/mice vs. /dev/psaux isue
> >
> > > 2. before, the sound worked. and now, still working, just with ALSA,
> > > no OSS support (tested with mpg321 and ogg123 on bash terminal)
> >
> >
> > Best:
> > aoss ./oss-app
> >
> > Not as good:
> > modprobe snd-pcm-oss
> > ./oss-app
>
> Could snd-pcm-oss be fixed? If OSS is to be removed from kernel, it
> would be nice to have working and compatible emulation.
Well, snd-pcm-oss is a working and compatible emulation, but it can't
provide all of the features that ALSA implements in userspace like
channel routing, mixing of multiple streams, software volume control,
etc. So aoss is the recommended way to run OSS apps on a moden distro.
Lee
next prev parent reply other threads:[~2006-03-16 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 18:15 Kernel config problem between 2.4.x to 2.6.x! j4K3xBl4sT3r
2006-03-12 20:43 ` Chris Largret
[not found] ` <7c3341450603121247n7afe018m@mail.gmail.com>
[not found] ` <436c596f0603121632qe3151k793fd3ccd9a0eacb@mail.gmail.com>
[not found] ` <200603130708.13685.nick@linicks.net>
2006-03-13 11:42 ` j4K3xBl4sT3r
2006-03-13 18:06 ` Lee Revell
2006-03-16 11:25 ` Pavel Machek
2006-03-16 19:06 ` Lee Revell [this message]
2006-03-15 23:13 ` Pavel Machek
2006-03-16 20:49 ` Lee Revell
2006-03-14 0:52 ` Chris Largret
2006-03-14 1:31 ` j4K3xBl4sT3r
2006-03-14 1:37 ` Lee Revell
2006-03-14 20:50 ` marcos cunha
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=1142535968.9395.7.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=jakexblaster@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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