Hi,
This error often means problem with IRQ (interupt from soundcard is not
generated).
Peter Zubaj
On Sun, 2006-05-28 at 15:36 +1000, Nick Urbanik wrote:
> Dear Folks,
>
> Running FC5 on an IBM Thinkpad 570; sound worked fine previously. Now
> I get no sound, have fiddled with alsamixer exten
Hi
Had a system running with 2.6.15/alsa and mpd, arts and everything
working perfectly.
Upgraded my debian kernel to 2.6.16, and then suddenly, when logging in
to kde, received arts error message that it couldn't open the sound
device, and was going to use the null output device. of course mpd
st
Flavio Rump wrote:
> Hi
> Had a system running with 2.6.15/alsa and mpd, arts and everything
> working perfectly.
>
> Upgraded my debian kernel to 2.6.16, and then suddenly, when logging in
> to kde, received arts error message that it couldn't open the sound
> device, and was going to use the null
On Sun, 2006-05-28 at 19:29 +0100, David Greaves wrote:
> I have the same problem on an upgrade to 2.6.16.18
>
> Been googling and checking versions etc for hours now...
Are you *sure* that all you changed was the kernel? This error comes
from alsa-lib.
Lee
_
On Sun, May 28, 2006 at 07:29:13PM +0100, David Greaves wrote:
> # alsaplayer /everything/music/Stream.mp3
> /usr/lib/alsaplayer/output/libalsa_out.so: symbol
> snd_pcm_hw_params_set_periods_near, version ALSA_0.9.0rc4 not defined in
> file libasound.so.2 with link time reference
http://bugs.debi
Lee Revell wrote:
> On Sun, 2006-05-28 at 19:29 +0100, David Greaves wrote:
>
>> I have the same problem on an upgrade to 2.6.16.18
>>
>> Been googling and checking versions etc for hours now...
>>
>
> Are you *sure* that all you changed was the kernel? This error comes
> from alsa-lib.
>
So, all I have to do is wait a couple of hours until the patch is
uploaded to the debian ftp archive?
Flavio
Koef wrote:
> On Sun, May 28, 2006 at 07:29:13PM +0100, David Greaves wrote:
>
>
>># alsaplayer /everything/music/Stream.mp3
>>/usr/lib/alsaplayer/output/libalsa_out.so: symbol
>>snd_pcm
On Sun, 2006-05-28 at 20:52 +0100, David Greaves wrote:
> Lee Revell wrote:
> > On Sun, 2006-05-28 at 19:29 +0100, David Greaves wrote:
> >
> >> I have the same problem on an upgrade to 2.6.16.18
> >>
> >> Been googling and checking versions etc for hours now...
> >>
> >
> > Are you *sure*
Hi, following the last two apt-upgrades of libasound2, libasound2-dev,
& libasound2-plugins I have no sound with aplay, mplayer or ekiga,
and keep getting the following ..
Tux:/home/cyberia/Music/Cuba2# aplay track-01.wav
Playing WAVE 'track-01.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, S
My audio is nearly trashed, i.e. bad stutter (interrupts?), with the
latest generic kernel for Linux, 2.6.16.18, and an onboard VT8237A audio
controller. As of today, I've updated to Slackware Current with the
latest kernel which was a big mistake in retrospect. I'm also using
ALSA 1.0.1
10 matches
Mail list logo
