Re: [Alsa-user] Hey... recommended kernel

2003-06-17 Thread lasse
Thanks for taking time. Sorry for being confusing and unclear... I'm quite confused myselft right now... I'm on 2.2.20 now... (couldn't get my pcmcia nic to recieve dhcp adress after i compiled new kernel... pcmia worked though.. missed something somewhere.. so i installed debian from start with '

Re: [Alsa-user] Hey... recommended kernel

2003-06-17 Thread Jeremy Henty
lasse wrote: > i'm on a fresh debian with kernel 2.2.19 ... i was just wondering. > is there any huge problems with such an old kernel, I run kernel 2.2.25 and I am stuck with alsa-0.9.0rc5 . rc6 gives odd messages from "alsactl restore" and any later version hangs any process that tries to use

Re: [Alsa-user] Hey... recommended kernel

2003-06-17 Thread Jaroslav Kysela
On Tue, 17 Jun 2003, lasse wrote: > Thanks for taking time. > > Sorry for being confusing and unclear... I'm quite confused myselft right > now... > I'm on 2.2.20 now... (couldn't get my pcmcia nic to recieve dhcp adress > after i compiled new kernel... pcmia worked though.. missed something > so

Re: [Alsa-user] Hey... recommended kernel

2003-06-17 Thread lasse
Yes sir, i am. I'm beginning to think 2.4.x to get alsa to party now... (but then again, what do i know) I have no idea what to do anymore =) On Tue, 17 Jun 2003, Stephen Mollett wrote: > On Tuesday 17 Jun 2003 18:10, lasse wrote: > > tried kernel-headers from debian package system... > > ./con

Re: [Alsa-user] Hey... recommended kernel

2003-06-17 Thread Stephen Mollett
On Tuesday 17 Jun 2003 18:10, lasse wrote: > tried kernel-headers from debian package system... > ./configure --with-cards=cs4236 --with-isapnp=no of alsa-driver ok > make not ok; > In file included from timer.c:33: > /usr/src/linux/include/linux/kmod.h:8: conflicting types for > `snd_compat_reques

Re: [Alsa-user] Hey... recommended kernel

2003-06-17 Thread Stephen Mollett
On Tuesday 17 Jun 2003 08:14, lasse wrote: > All of the ./configure;make;make install works like a charm, the problem > arises when i do the modprobe stuff... What exactly _is_ the problem? ie. what error message(s) do you get from modprobe, does anything show up in the kernel messages (do 'dmesg