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
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
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.
Lee
No.
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
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* that all you
