Hi Steve;
I'm not going to say I have a solution to your problem BUT as of
kernel version 2.4.19 I noticed a change in the way kernel patches are
applied.
Somewhat like you I do the following:
- Download kernel patch (ie. patch-2.4.19.gz)
- cd /usr/src
- make a backup copy of my old kernel
cp -av linux-2.4.18 linux-2.4.19
- change the /usr/src/linux symlink to point to 2.4.19
- gzip -cd patch-2.4.19.gz | patch -p0
- cd linux
- make oldconfig, etc, etc
- lilo, etc, etc.
When I went from 2.4.18 to 2.4.19 the new kernel was still identified
at 2.4.18! Well, this isn't the first time I've gotten a bad patch so
I downloaded the whole source tree for 2.4.19, copied over .config and
tried again ... all was well.
When I upgraded from 2.4.19 to 2.4.20 the same problem showed up! Two
bad patch files in a row is NOT possible so I investigated further.
It seems now, the 2.4.19 patch file is updating the linux-2.4.18
directory, NOT the linux symlink.
Now, this is a lot of typing without supplying a solution to your
problem BUT my point is there was a kernel handling change made right
around kernel 2.4.19 and you may be seeing another face of it. Maybe
this will tweak yours (or another readers memory) and shed some light
on this issue.
Good luck in your search!
>hi;
>using gentoo RC2.
>I was using kernel 2.4.19.
>when I did emerge 2 days ago, it downloaded a new kernel 2.4.20.
>Ok, So I went to /usr/src and made a link to the new directory
>and configured new kernel and build it (and modules, modules_install
>etc...)
>as I have done zillon times before:
>lrwxrwxrwx 1 root root 22 Mar 4 09:37 linux ->
>linux-2.4.20-gentoo-r1
>drwxr-xr-x 16 root root 840 Mar 4 09:36
>linux-2.4.19-gentoo-r10
>drwxr-xr-x 16 root root 840 Mar 4 10:02 linux-2.4.20-gentoo-r1
>next, as usuall, I copied the newly compiled bzImage to /boot/bzImage
>>cd /boot
>>ls -l
>total 3944
>-rw-r--r-- 1 root root 1485414 Mar 4 10:05 bzImage
>-rw-r--r-- 1 root root 1283810 Mar 1 18:48 bzImage.old
>next I rebooted. btw, I am not using lilo, but the other boot manager
>I think it is called grub.
>so, after I shutdown the system and boot, I select as before the file
>/boot/bzImage using the command
>>kernel /boot/bzImage
>>boot
>now, when the system is up, I do 'uname' expecting it to say 2.4.20,
>but
>it is still saying 2.4.19 !
>>uname -a
>Linux mymachine.mydomain.com 2.4.19-gentoo-r10 #2 SMP Sat Feb 1
>17:17:15 PST 2003 i686 Intel(R) XEON(TM) CPU 2.40GHz GenuineIntel
>GNU/Linux
>How could this be? is there another method to verify which kernel
>version
>I am running??
------------------------------------------------
http://www3.sympatico.ca/dmitton
SPAM Reduction: Remove "x." from my domain.
------------------------------------------------