Jump to content

2.4.22 boot


Recommended Posts

I've just finished a (successful?) install of kernel-2.4.22, I'm using mdk 9.1, and when I reboot there is no choice of the new kernel.

/etc/lilo.conf looks OK, and ran lilo -v; it shows the new kernel OK, /boot ... don't know...

Am I dreaming? Is it possible to run 9.1 with this kernel?

 

(Must get the head-scratching smiley)

Link to comment
Share on other sites

Here it is - looks wrong, but what to do with it?

 

boot=/dev/hdb

map=/boot/map

default="linux"

keytable=/boot/us.klt

prompt

nowarn

timeout=100

message=/boot/message

menu-scheme=wb:bw:wb:bw

disk=/dev/hdb bios=0x80

image=/boot/vmlinuz

label="linux"

root=/dev/hdb4

initrd=/boot/initrd.img

append="devfs=mount hdd=ide-scsi acpi=off quiet"

vga=788

read-only

image=/boot/vmlinuz

label="linux-nonfb"

root=/dev/hdb4

initrd=/boot/initrd.img

append="devfs=mount hdd=ide-scsi acpi=off"

read-only

image=/boot/vmlinuz

label="failsafe"

root=/dev/hdb4

initrd=/boot/initrd.img

append="devfs=nomount hdd=ide-scsi acpi=off failsafe"

read-only

other=/dev/hdb1

label="dos"

table=/dev/hdb

other=/dev/fd0

label="floppy"

unsafe

 

image=/boot/vmlinuz-2.4.21-0.25mdk

label=2421-25

root=/dev/hdb4

read-only

optional

vga=788

append="devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/initrd-2.4.21-0.25mdk.img

#The following boot section was added by buildkernel on

#Wed Oct 22 21:44:46 EDT 2003

#Please feel free to move this section, edit it, and remove these comments.

image=/boot/bzImage-2.4.22-1

label=2.4.22-1

root=/dev/hdb4

read-only

optional

vga=788

append="devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/bzImage-2.4.22-1

#End of autoinstall

--------------------------------------------------------------------------

 

william@localhost william]$ ls /lib/modules

2.4.21-0.13mdk/ 2.4.21-0.25mdk/ 2.4.22/

[william@localhost william]$

-----------------------------------------------------------

 

william@localhost william]$ ls /boot

bkinstall-2.4.22-1* initrd-2.4.21-0.25mdk.img message-text

boot.0340 initrd.img@ System.map@

bzImage-2.4.22-1 kernel.h@ System.map-2.4.21-0.13mdk

config@ kernel.h-2.4.21-0.13mdk System.map-2.4.21-0.25mdk

config-2.4.21-0.13mdk kernel.h-2.4.21-0.25mdk us.klt

config-2.4.21-0.25mdk map vmlinuz@

grub/ message@ vmlinuz-2.4.21-0.13mdk

initrd-2.4.21-0.13mdk.img message-graphic vmlinuz-2.4.21-0.25mdk

[william@localhost william]$

Link to comment
Share on other sites

What is "optional" for?...anyone know? Not needed so #comment it out. Your initrd is your kernel image (initrd=/boot/bzImage-2.4.22-1) :shock:...what's up with that? AND, you don't have a initrd-xxx.img for the new kernel (or am I blind?). Make one as root with;

mkinitrd /boot/initrd-2.4.22-1.img 2.4.22-1

 

then change lilo.conf to;

#The following boot section was added by buildkernel on

#Wed Oct 22 21:44:46 EDT 2003

#Please feel free to move this section, edit it, and remove these comments.

image=/boot/bzImage-2.4.22-1

label=2.4.22-1

root=/dev/hdb4

read-only

#optional

vga=788

append="devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/initrd-2.4.22-1.img

#End of autoinstall

...run

lilo -v

and reboot

Link to comment
Share on other sites

Well, that didn't work :(

[root@localhost william]# mkinitrd /boot/initrd-2.4.22-1.img 2.4.22-1

/lib/modules/2.4.22-1 is not a directory.

[root@localhost william]#

 

What sort of file/directory is it looking for?

Link to comment
Share on other sites

I did the last part of the kernel install from http://www.cs.technion.ac.il/~cs236340/con...ernel_comp.html but that doesn't work either :cry:

 

boot=/dev/hdb

map=/boot/map

default="linux"

keytable=/boot/us.klt

prompt

nowarn

timeout=100

message=/boot/message

menu-scheme=wb:bw:wb:bw

disk=/dev/hdb bios=0x80

image=/boot/vmlinuz

label="linux"

root=/dev/hdb4

initrd=/boot/initrd.img

append="devfs=mount hdd=ide-scsi acpi=off quiet"

vga=788

read-only

snip

 

image=/boot/vmlinuz-2.4.21-0.25mdk

label=2421-25

root=/dev/hdb4

read-only

optional

vga=788

append="devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/initrd-2.4.21-0.25mdk.img

#The following boot section was added by buildkernel on

#Wed Oct 22 21:44:46 EDT 2003

#Please feel free to move this section, edit it, and remove these comments.

image=/boot/bzImage-2.4.22-1

label=2.4.22-1

root=/dev/hdb4

read-only

vga=788

append="devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/initrd-2.4.22.img

image=/boot/vmlinuz-2.4.22

root=/dev/hdb4

label=2.4.22

initrd=/boot/initrd-2.4.22.img

read-only

vga=788

append="devfs=mount hdd=ide-scsi acpi=off quiet"

#End of autoinstall

 

I'm doing this in hdb4 which shares with win98. Thought maybe that's why lilo does't show....Bah. I did the newer mdk kernel the same way, and it's OK. Duh!

Link to comment
Share on other sites

these 2

image=/boot/bzImage-2.4.22-1

initrd=/boot/initrd-2.4.22.img

need to match. So mkinitrd again for

/boot/initrd-2.4.22-1.img

 

so that you'll have

image=/boot/bzImage-2.4.22-1

initrd=/boot/initrd-2.4.22-1.img

 

and take out;

image=/boot/vmlinuz-2.4.22

root=/dev/hdb4

label=2.4.22

initrd=/boot/initrd-2.4.22.img

read-only

 

 

 

So that all you have for the new kernel is;

image=/boot/bzImage-2.4.22-1

label=2.4.22-1

root=/dev/hdb4

read-only

vga=788

append="devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/initrd-2.4.22-1.img

Link to comment
Share on other sites

Did that, so here's the latest copy:

 

image=/boot/vmlinuz-2.4.21-0.25mdk

label=2421-25

root=/dev/hdb4

read-only

optional

vga=788

append="devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/initrd-2.4.21-0.25mdk.img

image=/boot/bzImage-2.4.22-1

label=2.4.22-1

root=/dev/hdb4

read-only

vga=788

append="devfs=mount hdd=ide-scsi acpi=off quiet"

initrd=/boot/initrd-2.4.22-1.img

 

then lilo, reboot. No Difference.

Its seems that the fault is not in lilo.config.

I will read http://www.redhat.com/docs/manuals/linux/R...wn-booting.html

until it makes sense. (takes time)

Link to comment
Share on other sites

Trashed that copy of mdk - its a test copy anyway.

On the way to re-install I noticed that kernel-2.4.22 was finally showing in the boot menu. Too late!

Reason was that on reboot, it looks at the lilo.config in hda. Always. So now I've unplugged the hda and re-installed.

 

I get:

Boot image: /boot/bzImage-2.4.22-1

Fatal: open /boot/bzImage-2.4.22-1: No such file or directory

when I run lilo -v

 

Tried omitting image (this means the first line?) and no good. Nothing shows on boot menu.

Used "Find" and there is no such file. there is a bzImage file in /usr/src/linux-2.4.22/arch/i386/boot but no version number.

There is also in /boot a vmlinuz (no version number) in italic which is a link, suspect it's for 2.4.22.

Link to comment
Share on other sites

could be....run

file /boot/vmlinuz

 

but if you've reinstalled the distro, you'll have to reinstall the kernel. Do you have a sepearate /boot partition? If so, the only kernels that can be booted to are the ones in /lib/modules/<version>

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...