After kernel upgrade, reported version has not changed

HarveyJAAP · 01-25-2009, 06:33 PM

Distro - Xandros 2.0 (ancient magazine disc)
----No internet connection so manual upgrades ...
Initial linux kernel - 2.4.24-x1
upgraded to 2.6.28

All went well, eventually, as per the README file, but $ uname -r ==> 2.4.24-x1; $ cat /proc/version ==> Linux version 2.4.24-x1 (gcc 3.2.2 ........

It boots nicely; all the images and files referenced in /etc/lilo.conf point to files with the new date of compilation; these have different file sizes to the originals, which match the file sizes of files in the new compilation directory.

However, the following dates are a little different -
/dev/initrd -> rd/initrd
25/1/2009 1/1/1970 Is this significant?

I have already upgraded coreutils in case it was a uname problem, but reinstalling the new kernel made no difference.

Am I actually running the new kernel and misreporting the version?
Or is lilo actually installing the old kernel despite the lilo.conf settings?

I can foresee future problems when I later upgrade the kernel again or when I instal an upgrade that requires a particular kernel version. Can somebody point me in the right direction? Thanks.

I am trying to get my wifi dongle to connect me - ndiswrapper needs a later kernel than the one I had.

Drakeo · 01-25-2009, 06:46 PM

why don't you type uname -a and post it and post your lilo.conf and then look /boot/ file and see what vmlinuz is linked to. you will find that 90 percent of all the net drivers are in the new kernel and ndiswraper is not being used very much. the old broadcom cards are supported just down load the firmware for it . and type lspci and post it and then you may get some help from the people here that use free open source uname tells you the modules you are running.. and yes they are supposed to match the kernel. Xandros is a paid for system that has there own support.

HarveyJAAP · 01-26-2009, 10:20 AM

As requested ...

----------uname -a
Linux HarveyPartridge 2.4.24-x1 #1 SMP Fri Feb 20 16:30:52 EST 2004 i686 GNU/Linux

----------cat /proc/version
Linux version 2.4.24-x1 (root@build-kunstable) (gcc version 3.3.2 20031005 (Debian prerelease)) #1 SMP Fri Feb 20 16:30:52 EST 2004

----------/etc/lilo.conf
boot=/dev/hda
install=/boot/cboot.b
message=/boot/splash.lilo
timeout=300
map=/boot/map
prompt
fix-table
lba32
read-only
disk=/dev/hda bios=0x80
image=/vmlinuz
label=[]s_Desktop_2.0
vga=0xf04
root=/dev/hda2
initrd=/boot/initrd-2.6.28n.gz
append="rw acpi=on "
image=/vmlinuz
label=Safe_Video_Mode
vga=0xf04
root=/dev/hda2
initrd=/boot/initrd-2.6.28n.gz
append="3 rw acpi=on "
image=/vmlinuz
label={}ure_(Expert)
vga=normal
root=/dev/hda2
initrd=/boot/initrd-2.6.28n.gz
append="single rw acpi=on "

----------/ls -l /vmlinuz
lrwxrwxrwx 2 root root 14 2009-01-25 01:03 /vmlinuz -> vmlinuz-2.6.28

----------/ls -l /boot/vmlinuz
lrwxrwxrwx 2 root root 14 2009-01-25 01:03 /boot/vmlinuz -> vmlinuz-2.6.28

----------/ls -l /boot/vmlinuz-2.6.28
-rw-r--r-- 1 root root 1469392 2009-01-25 01:03 /boot/vmlinuz-2.6.28

----------/ls -l /boot/vmlinuz-2.4.24*
-rw-r--r-- 1 root root 966008 2004-02-20 23:25 /boot/vmlinuz-2.4.24-x1
-rw-r--r-- 1 root root 966008 2009-01-22 21:56 /boot/vmlinuz-2.4.24-x1.old

The Xandros distro came free with Linux User several years ago (2004?) and I have neither paid for it nor am I easily able to access their after sales service because I cannot currently connect to the internet. It is the only one of half a dozen or so distros in my possession that I was able to correctly install. Hence the need for manual upgrades.

lspci currently reports my Thomson WIFI dongle - to connect to France Telecom/Wanadoo/Orange LiveBox - as "unknown device". This may be a result of my original problem ...

Thanks for addressing my problem so quickly.

Drakeo · 01-26-2009, 09:23 PM

here is waht a lilo should look like.

Quote:

# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot="/dev/hda"
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout="1200"
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga="773"
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins

image="/boot/vmlinuz"
root="/dev/hda1"
label="Linux"
read-only
# Linux bootable partition config ends

image=/mnt/hda2/boot/vmlinuz24
label="slack12.1-24"
root=/dev/hda2
read-only

image=/mnt/hda2/boot/vmlinuz27
label="slack12.1-27"
root=/dev/hda2
read-only

image=/mnt/hdb1/boot/vmlinuz-2.6.18.8.tex5
label="pcl2007"
root=/dev/hdb1
read-only
initrd="/mnt/hdb1/boot/initrd-2.6.18.8.tex5.img"
append="acpi=on resume=/dev/hda3 splash=silent"

image=/mnt/hdc1/boot/vmlinuz-2.6.24-22-generic
label="gos3"
root=/dev/hdc1
read-only
initrd="/mnt/hdc1/boot/initrd.img-2.6.24-22-generic"

image="/pup412/vmlinuz"
label="pup412"
initrd="/pup412/initrd.gz"

image="/mnt/hda2/boot/vmlinuz"
label="slack12.1-28"
root="/dev/hda2"
read-only

notice how it points to the drives and has tittle
these are a few of my systems/ check it out and any time you change lilo you have to run /sbin/lilo
it will never miss report if it says it is running a kernel trust me it loaded and ran that kernel.
and you are running that kernel run lilo and look at the out put.type lilo as root.