Op Tuesday 16 December 2003 02:29, schreef Ivan Sergio Borgonovo:

On 15 Dec 2003 16:56:28 -0700

Marcel Lecker wrote:

...

Hi Ivan,

...

make menuconfig (you may need extra -devel packages and some other stuff)

'make cloneconfig' gets the config from the currently running kernel if it's a kernel from SuSE.

get out if you're satisfied with the original SUSE .config

This is a rough idea of what you'll have to do to compile a new kernel:

make clean dep clean bzImage modules modules_install | grep 'rror'

Huh? AFAIK to build the nvidia modules from nvidia only a 'make dep' is needed? ;) Cheers, Leen

Ivan, Well, this will certainly take me out of my comfort zone,...but I do need a push now and then and this may be it. Reinstalling is always an option so what's there to loose, eh? I've had 9.0 sitting on the shelf for about a month now ready to do a switch-over. I'll try this over the holidays and see how far I get, Plan B,...SuSE^H^H^HUSE 9.0. Thanks for the help, you may hear from me again. :) Marcel On Mon, 2003-12-15 at 18:29, Ivan Sergio Borgonovo wrote:

On 15 Dec 2003 16:56:28 -0700 Marcel Lecker wrote:

...

Hi Ivan,

Thanks for the reply. I made sure all my sources were in and it would appear to be a compiler issue. The plot thickens. I haven't a clue what to do from here as I'm not much of a coder. I'm a little out of my element here.

Then you should hear me singing ;)

...

You appear to be compiling the NVIDIA kernel module with a compiler different from the one that was used to compile the running kernel. This may be perfectly fine, but there are cases where this can lead to unexpected behaviour and system crashes.

OK, install the whole sources of the kernel you're using not just the headers. I'm not sure if you did.

Then go into the kernel directory (/usr/src/kernel...)

check if everything seems reasonable doing

make menuconfig (you may need extra -devel packages and some other stuff)

get out if you're satisfied with the original SUSE .config

This is a rough idea of what you'll have to do to compile a new kernel:

make clean dep clean bzImage modules modules_install | grep 'rror' cp arch/i386/boot/bzImage /boot/vmlinuz cp System.map /boot/System.map-2.4.18

/sbin/lilo /sbin/mk_initrd -k vmlinuz -i initrd /sbin/lilo

Beware this is not exactly what you'll have to do... it depends if you're running lilo or grub. You'll have to change the System.map-version to an appropriate name. You may not need an initrd. You may want to edit lilo or grub menu to have a copy of your old kernel and maybe rename vmlinuz to something else...

It would be better you know exactly what you're doing reading one of the tons of howto on how to compile your own kernel and configure lilo or grub.

It is not difficult, few precautions will let you start over and over in a safe way if you make some mistake of configuration. Even if you'll do some mistakes and you won't be able to boot from your box most of the times your data will still be there and you should be able to resurrect your whole system but this will be far more complicated than just know how grub or lilo work and take some precautions.

There should be a chapter on lilo and kernel compilation on SUSE's manuals too.

Once you've compiled your kernel with your compiler you'll have to run again nvidia installer.

It is not as difficult as it seems but some mistakes can put you into panic mode. Most of the time everything is still there and you can restart a fully working system... but better you read carefully a good howto on how to compile a kernel and how to configure lilo or grub.

...

If you know what you are doing and want to override this check, you can do so by setting IGNORE_CC_MISMATCH.

I wouldn't do that. -- Marcel Lecker