alsaconf is the one giving the message
alsaconf
modinfo: snd-opl3sa2: no module by that name found
modinfo: snd-cs4236: no module by that name found
modinfo: snd-cs4232: no module by that name found
modinfo: snd-cs4231: no module by that name found
modinfo: snd-es18xx: no module by that name foun
> Marc is correct. I had the same problem. With the
> 2.4 kernel you must find
> the correct modules and load them. I never did get
> ALSA to work properly
> under the 2.4 kernel. So, I am not the right person
> to help further. I
> solved my problems by moving to the 2.6 kernel,
> which, as M
If you are running 2.4, then I think that you need to install alsa-modules-2.4.27-2-686
. The modules are built-in to the 2.6 kernels.--Best,Marc
Marc is correct. I had the same problem. With the 2.4 kernel you must
find the correct modules and load them. I never did get ALSA to work
properly under
alsaconf returns:modinfo: snd: no module by that name foundmodinfo: snd: no module by that name foundmodinfo: snd: no module by that name foundUnloading ALSA sound driver modules: (none loaded).Building card database... modinfo: snd-opl3sa2: no module by that name foundmodinfo: snd-cs4236: n
alsaconf returns:
modinfo: snd: no module by that name foundmodinfo: snd: no module by that name foundmodinfo: snd: no module by that name foundUnloading ALSA sound driver modules: (none loaded).Building card database...
modinfo: snd-opl3sa2: no module by that name foundmodinfo: snd-cs4236: no
--- Roger Creasy <[EMAIL PROTECTED]> wrote:
>
> Have you run alsaconf?
>
> Roger
>
alsaconf returns:
modinfo: snd: no module by that name found
modinfo: snd: no module by that name found
modinfo: snd: no module by that name found
Unloading ALSA sound driver modules: (none loaded).
Buildin
On 10/12/05, Jeremy Merritt <[EMAIL PROTECTED]> wrote:
> >> > 'cat /proc/asound/cards' returns "No such file or> > directory"--- marc <[EMAIL PROTECTED]> wrote:>> That's because you don't have a soundcard assigned
> to ALSA - which is> what Gstreamer was telling you earlier, but it's> best to check
> >
> > 'cat /proc/asound/cards' returns "No such file or
> > directory"
--- marc <[EMAIL PROTECTED]> wrote:
>
> That's because you don't have a soundcard assigned
> to ALSA - which is
> what Gstreamer was telling you earlier, but it's
> best to check.
>
> Open the Control Centre/Sound & Mul
> > After doing this, I did as you described. The
> message
> > returned in amarok is:
> >
> > [GStreamer Error] ALSA device "default" does not
> exist
> That's pretty clear. What does
> # cat /proc/asound/cards
> have to say?
Sorry for the top post.
'cat /proc/asound/cards' returns "No suc
After doing this, I did as you described. The message
returned in amarok is:
[GStreamer Error] ALSA device "default" does not exist
--- marc <[EMAIL PROTECTED]> wrote:
>
> The default gstreamer package in amarok is OSS.
> Remove it - why not? -
> and install the ALSA version (gstreamer0.8-alsa
When I use XMMS's ALSA driver, I get a message that
says:
"Couldn't open audio. Please check that: your
soundcard is configured properly, you have the correct
output plugin selected, and no other program is
blocking the soundcard."
...when attempting to playback.
Amarok has several engines to u
I second the recommendation to switch to ALSA. It may solve your
problem by itself. And Amarok does work with it. :)
Jeremy Merritt wrote:
I have recently been having an error with several
audio players, including amarok and xmms. Amarok
produces the following error message:
Did you recently convert to udev? (See below)
[GStreamer error] Could not open device '/dev/dsp' for
writing. ** gstosselementc
I have recently been having an error with several
audio players, including amarok and xmms. Amarok
produces the following error message:
[GStreamer error] Could not open device '/dev/dsp' for
writing. ** gstosselementc(752):
gst_osselement_open_audio /root/bin system error:
Resource temporari
14 matches
Mail list logo
