Clemens Ladisch wrote:
The ALSA initialization script doesn't want to run when some ALSA
modules are already loaded; the USB driver initializes earlier and
automatically loads all USB drivers.
Put snd-usb-audio into the blacklist file, too.
That made Alsa start up correctly for the soundcard.
On Mon, 8 Mar 2004, Clemens Ladisch wrote:
> "audio" is the OSS driver for USB audio devices. As long as that one
> is loaded, you won't be able to use /dev/dsp0, /dev/mixer0 etc. for
> ALSA's OSS emulation.
>
> Use snd-usb-audio instead. If your system automatically loads audio,
> put it into
On Sun, 7 Mar 2004, Gabriel Ebner wrote:
> Am Sonntag, 7. März 2004 16:50 schrieb Rich Drewes:
> > Thanks for your reply, but as I posted in my original message, I do have
> > all the appropriate snd-xxx-oss emulation modules installed,
> Stupid question, are they loaded?
Yes
llo,
>
> Am Sonntag, 7. März 2004 04:29 schrieb Rich Drewes:
> > In the past, I didn't have to use the aoss wrapper to get OSS apps to
> > work. Can anyone suggest an explanation for why I do now?
> AFAIK, aoss provides a virtual /dev/dsp file to the app you want to run by
&
I am able to get OSS apps to play sounds by invoking them with the "aoss"
wrapper, e.g.:
aoss esd
aoss frozen-bubble
In the past, I didn't have to use the aoss wrapper to get OSS apps to
work. Can anyone suggest an explanation for why I do now?
Thanks,
Rich
On Sat, 6 Mar 20
On Sun, 7 Mar 2004, faz wrote:
> But xmms doesn't work.
Right click on the xmms window and go to options->preferences. Select the
Alsa output plugin, or the plugin for your windowing environment (esound
or artsd, if either of those is installed and working). If you select OSS
output from xmms,
iled on Mar 2 2004 for kernel 2.6.3-4mdk.
# rpm -qa | grep libalsa-oss
libalsa-oss0-devel-1.0.2-3mdk
libalsa-oss0-1.0.2-3mdk
Should I get off the bleeding edge?
Thanks!
Rich Drewes
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Fr
