On Mon, 2003-09-22 at 04:52, Yaakov Nemoy wrote:

I did a fresh download of the 2.4.22 kernel, copied the .config file from the old kernel, (2.4.20-SuSE) double checked everything with xconfig (ALSA wasn't an option, and I'm wondering if that will be problematic knowing SuSE uses ALSA) and started compiling the bzImage. It will be if you want sound. Luckily that's easy to sort out. Download alsa (just the driver package, the tools and libs aren't necessesary as they are already on your system. Boot into your new kernel, and install alsa with:

I'm now getting a lot of warnings saying "comparison between signed and unsigned". Is this normal or will it be a problem. (With the little I know about programming, I do know that getting this error for nearly every *.c file isn't a good thing.) Should be OK if it doesn't give any errors. From what I've read on this

./configure make make install The alsa drivers will now bit in your /lib/modules/2.4.22 somewhere and SuSE can use them. list and elsewhere the newer GCC is just a lot more strict on syntax and so on, so it does give more warnings (and won't compile some earlier kernels because of that). Hans

I had problems with my card defined as es1371 instead of ens1371 and the modules loaded would cause sound not to work. I downloaded the alsa CVS, set up my config with just CONFIG_SOUND=m and soundcore as a module in the kernel. Built and installed the kernel, booted to runlevel 3 and built alsa. Regards Sid. Yaakov Nemoy wrote:

I did a fresh download of the 2.4.22 kernel, copied the .config file from the old kernel, (2.4.20-SuSE) double checked everything with xconfig (ALSA wasn't an option, and I'm wondering if that will be problematic knowing SuSE uses ALSA) and started compiling the bzImage. I'm now getting a lot of warnings saying "comparison between signed and unsigned". Is this normal or will it be a problem. (With the little I know about programming, I do know that getting this error for nearly every *.c file isn't a good thing.)