kanotix.com :: Thema anzeigen - Messed up with kernel update

kanotix.com

General Support - Messed up with kernel update

HomerCube - 16.08.2006, 09:37 Uhr
Titel: Messed up with kernel update

I'm in a bit of a mess about updating my kernel. Here's my scenario:

have a Pentium 4 2.8 GB EE (hyperthreading enabled)
have an Nvidia FX5200 video card, works fine with Nvidia drivers
installed Kanotix 2005-04, went fine
made regular apt-get upgrade from time to time, all went fine, too
made regular Nvidia drivers' update from time to time, all went fine, too
tried to update kernel by downloading kernel-2.6.17.8-slh-smp-1.zip and installing it as known here (install-kernel-kanotix.sh , dpkg -i *modules*.deb, reboot and so on)

But what I get is:

at startup I can see two Tux on screen (i.e. kernel did not identify hyperthreading)
trying to Nvidia drivers' installation with install-nvidia-debian.sh failed because of mismatch between gcc used for modules and the one now active (gcc was regularly updated)

Lucky enough I had backupped partitions with PartImage before I start, so I could recover without having to perform a full reinstall.
Now I would like to know exactly what I have to do if I want to perform a kernel update, provided my Kanotix box has "grown" during time, and I would like to understand why hyperthreading is well managed in original kernel while it's not in newer ones. Should I start from sources and recompile instead? If it's the case, could anyone tell me if install-kernel-kanotix.sh gets me complete kernel and patches to start with?

Please forgive this request but I can see lots of posts in this forum about kernel update and I honestly lost my way in them.
TnX

devil - 16.08.2006, 10:36 Uhr
Titel: Messed up with kernel update

hm, if you have a hyperhtreading cpu and using smp-kernel, seeing 2 tuxes is perfectly right.
the problem with gcc is, that kernels from 2.6.17 and up need gcc version 4.1 instead of gcc-4.0.4 for 2.6.16 and down. all you had to do was: apt-get install gcc.
you could have booted to your old kernel as well.

greetz
devil

HomerCube - 16.08.2006, 10:50 Uhr
Titel: Re: Messed up with kernel update

devil hat folgendes geschrieben::

hm, if you have a hyperhtreading cpu and using smp-kernel, seeing 2 tuxes is perfectly right.

This sounds strange to me, because former 2.6.14 kernel did show me only one; is there a reason for it to have changed behaviour?

devil hat folgendes geschrieben::

the problem with gcc is, that kernels from 2.6.17 and up need gcc version 4.1 instead of gcc-4.0.4 for 2.6.16 and down. all you had to do was: apt-get install gcc.

So I should wait for Debian repositories to have gcc 4.1, right? (please bear in mind I use "testing" ISOs for my updates, so this could happen with a slight delay face to "unstable" repository)

devil hat folgendes geschrieben::

you could have booted to your old kernel as well.

Yes, I know. I just wanted to restart from a clean situation.

devil - 16.08.2006, 11:10 Uhr
Titel: Re: Messed up with kernel update

homer,
maybe before you used -up kernel (uniprocessor).
that will show only one tux.
gcc 4.1 is in testing also, so just get it.

greetz
devil

HomerCube - 16.08.2006, 14:46 Uhr
Titel: Re: Messed up with kernel update

devil hat folgendes geschrieben::

maybe before you used -up kernel (uniprocessor).

I remember I tried both an -up and an -smp kernel and they both showed up two Tux images, but I'll have another try as soon as I can.

ThanX for your precious help.