LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 07-20-2003, 01:33 PM   #1
John Newbie
LQ Newbie
 
Registered: Jun 2003
Location: Denmark
Distribution: KUbuntu
Posts: 15

Rep: Reputation: 0
upgraded kernel but still wrong version


I just upgraded kernel from 2.4.18 to 2.4.21 and now when I run: cat /proc/version , I still get the old kernel 2.4.18.

I have corrected the lilo.conf and run lilo.
At /usr/src is linux->/usr/src/kernel-headers-2.4.21-1
At root is initrd.img->boot/initrd.img-2.4.21-1-686
At root is vmlinuz->boot/xmlinuz-2.4.21-1-686

Anybody any ideas, please and thanks
 
Old 07-20-2003, 03:16 PM   #2
fancypiper
LQ Guru
 
Registered: Feb 2003
Location: Sparta, NC USA
Distribution: Ubuntu 10.04
Posts: 5,141

Rep: Reputation: 58
Did you re-boot?
 
Old 07-21-2003, 09:04 AM   #3
John Newbie
LQ Newbie
 
Registered: Jun 2003
Location: Denmark
Distribution: KUbuntu
Posts: 15

Original Poster
Rep: Reputation: 0
I did reboot
 
Old 07-27-2003, 08:12 PM   #4
Corin
Member
 
Registered: Jul 2003
Location: Jette, Brussels Hoofstedelijk Gewest
Distribution: Debian sid, RedHat 9, Suse 8.2
Posts: 446

Rep: Reputation: 31
Hi John!

Can you do

dpkg -l | egrep kernel

(where -l is ELL as in LIMASSOL)

and can we see your lilo.conf file, please?

And when you rebooted did you make sure that you booted on the lilo menu entry for your new kernel rather than it auto-booting on the lilo entry for the old kernel?

Last edited by Corin; 07-27-2003 at 08:14 PM.
 
Old 07-28-2003, 02:14 PM   #5
John Newbie
LQ Newbie
 
Registered: Jun 2003
Location: Denmark
Distribution: KUbuntu
Posts: 15

Original Poster
Rep: Reputation: 0
Hi

Well if you know the answer to my problem(s) (or as somebody is saying, there is no problems only tasks at hand), you are my God, no more than that, you are my Linux-Tux.

Just have to start by saying that I apt-get upgraded and got kernel-image-2.4.21-3-686, but still showing wrong kernel version

uname -a => Linux debian 2.4.21-1-686
---------------------------------------------------
At /usr/src is linux -> /usr/src/kernel-headers-2-4-21-3
At root (/) is initrd.img -> boot/initrd.img-2.4.21-3-686
At root (/) is initrd.img.old -> boot/initrd.img-2.4.21-2-686
At root (/) is vmlinuz -> boot/vmlinuz-2.4.21-3-686
At root (/) is vmlinuz.old -> boot/vmlinuz-2.4.21-2-686

dpkg -l | egrep kernel
----------------------------
ii kcmlinuz 3.1.2-1 KDE Frontend for the Linux kernel configurat
ii kernel-doc-2.4 2.4.21-3 Linux kernel specific documentation for vers
ii kernel-headers 2.4.21-1 Header files related to Linux kernel version
ii kernel-headers 2.4.21-1 Linux kernel headers 2.4.21 on PPro/Celeron/
ii kernel-headers 2.4.21-2 Header files related to Linux kernel version
ii kernel-headers 2.4.21-2 Linux kernel headers 2.4.21 on PPro/Celeron/
ii kernel-headers 2.4.21-3 Header files related to Linux kernel version
ii kernel-headers 2.4.21-3 Linux kernel headers 2.4.21 on PPro/Celeron/
ii kernel-image-2 2.4.21-3 Linux kernel image for version 2.4 on PPro/C
rc kernel-image-2 2.4.16-1 Linux kernel image for version 2.4.16 on PPr
ii kernel-image-2 2.4.21-1 Linux kernel image for version 2.4.21 on PPr
ii kernel-image-2 2.4.21-2 Linux kernel image for version 2.4.21 on PPr
ii kernel-image-2 2.4.21-3 Linux kernel image for version 2.4.21 on PPr
ii pciutils 2.1.11-2 Linux PCI Utilities (for 2.[12345].x kernels

lilo.conf
----------
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81

#disk=/dev/sda
# bios=0x80

# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hdc1

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hdc3
append="hdd=ide-scsi"

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
# prompt
# single-key
# delay=100
# timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal

# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""

# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
initrd=/initrd.img
label=Linux
read-only
# restricted
# alias=1

image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
other=/dev/hdc1
label="Linux(hdc1)"

other=/dev/hda1
label="Other(hda1)"

other=/dev/hda5
label="WinNT(hda5)"

other=/dev/hdb1
label="Other(hdb1)"
--------------------------------------------------

As far as booting/lilo.conf goes. It seems to me that, when I "install" a "new" kernel it make the new kernel version boot-default and the old one Linux-old. If that is right, then I know something about Linux
 
Old 07-28-2003, 03:00 PM   #6
fancypiper
LQ Guru
 
Registered: Feb 2003
Location: Sparta, NC USA
Distribution: Ubuntu 10.04
Posts: 5,141

Rep: Reputation: 58
Hm.. I don't like wizards, so I hand edit stuff to make sure it is right. I find that I am better than the wizard.

Did you run /sbin/lilo to enforce the changes in lilo? Did you select your new kernel on boot or boot to the old kernel?
 
Old 07-28-2003, 03:24 PM   #7
John Newbie
LQ Newbie
 
Registered: Jun 2003
Location: Denmark
Distribution: KUbuntu
Posts: 15

Original Poster
Rep: Reputation: 0
Hi fancypiper

From the 1st tread: "I have corrected the lilo.conf and run lilo."
I did select the new one.
I just think that Linux somewhere is misssing a LN, just my guess.

[Not meaned as hard, as it sound, sorry]
When i comes to Linux I do preferer wizard. Every time I try to install something, I alway miss something. The latest is missing QT for the CD-burn-gui and I do not seem to be able to find this QT. Compileing a new kernel is a nightmare.
Why not put all you need is the package, it seems that Linux tells you if you allready got what you are trying to install.
If the meaning of Linux is to be exclusive for Needs then it is succeded/ok.
If Linux should be for everybody , I hate to say this but then please do it a bit like the Microsoft way.
This error forum and all the others say's it all.

Sorry about this, just a bit annoyed about how hard it is to install a simple application.

Last edited by John Newbie; 07-28-2003 at 03:29 PM.
 
Old 07-28-2003, 03:35 PM   #8
fancypiper
LQ Guru
 
Registered: Feb 2003
Location: Sparta, NC USA
Distribution: Ubuntu 10.04
Posts: 5,141

Rep: Reputation: 58
It would help us to spot your distribution and release number if you would put it in your profile. Look to the left of my post for an example.

Will this help you?

Creating custom kernels with Debian's kernel-package system

LILO fails: Error messages and their interpretation
LILO mini HOWTO
Multiboot with LILO HOWTO
LILO, Linux Crash Rescue HOW-TO
Installing a bootloader

Last edited by fancypiper; 07-28-2003 at 03:46 PM.
 
Old 07-28-2003, 04:50 PM   #9
Corin
Member
 
Registered: Jul 2003
Location: Jette, Brussels Hoofstedelijk Gewest
Distribution: Debian sid, RedHat 9, Suse 8.2
Posts: 446

Rep: Reputation: 31
John Newbie: I just upgraded kernel from 2.4.18 to 2.4.21

dpkg tells us

ii kernel-image-2 2.4.21-3 Linux kernel image for version 2.4.21 on PPr

which means that kernel 2.4.21 is indeed installed on your machine

uname -a => Linux debian 2.4.21-1-686

which tells us that the running kernel is indeed 2.4.21

So which kernel is it that you want to be running?

If you do a

cat /proc/version

now, what does it say?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
uname -r reports wrong kernel version branque Fedora 5 09-16-2005 10:26 AM
Kernel Reporting Wrong Version JShadow Linux - General 7 03-24-2005 09:34 AM
rpm -qa | grep kernel gives wrong kernel version markelo Red Hat 3 07-18-2004 09:35 AM
Upgraded to SuSE 9, is this kernel version correct? Thermodynamic Linux - Software 1 01-24-2004 12:04 AM
wrong kernel version? enrico Slackware 4 05-01-2003 12:05 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 04:54 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration