Compiling redhat 9.0

cholzsc1 · 07-14-2003, 07:49 AM

Ok so far i have
1) make mrproper
2)make xconfig
3)make dep
4)make clean
5)make bzImage
6)make modules
7)make modules_install

Finally then im confused dunno what to do do i cp /usr/src/linux-2.4.20-18.9 /boot/test 2.4.20-18.9.img ? Then do i edit my grub config file to match? what do i do?

Using grub as bootloader

cnjohnson · 07-14-2003, 08:51 AM

Quote:

Originally posted by cholzsc1
Ok so far i have
1) make mrproper
2)make xconfig
3)make dep
4)make clean
5)make bzImage
6)make modules
7)make modules_install

Finally then im confused dunno what to do do i cp /usr/src/linux-2.4.20-18.9 /boot/test 2.4.20-18.9.img ? Then do i edit my grub config file to match? what do i do?

Using grub as bootloader

If you got no errors in your 7 steps, then all you have to do is reboot. Step 7 copies the img file, and updates grub for you. Try the reboot and report back!

Cheers--
Charles

cholzsc1 · 07-14-2003, 09:09 AM

Yeah got a kernel panic error how do i edit the grub.conf to say the correct stuff?Dunno how to edit file says cant mount root...Dont i have to edit grub b4 reboot or mkinitrd /boot/newmkinitrd ???????

cholzsc1 · 07-14-2003, 09:41 AM

Says kernel panic vfs unable to mount root fs on 00:00
VFS cannot open root device "LABEL"/ or 00:00
Please append a correct "ROOT" = boot option

acid_kewpie · 07-14-2003, 09:48 AM

Quote:

Originally posted by cnjohnson
If you got no errors in your 7 steps, then all you have to do is reboot. Step 7 copies the img file, and updates grub for you.

no it doesn't, it installs the modules, hence the name. you will still need to update grub. you won't alwaysneed an init idisk though, so just clone the existing entry and change the path to the new image e.g /boot/vmlinux-2.4.21-test

cholzsc1 · 07-14-2003, 11:06 AM

Now it says try passing the init version to the kernel?????
Mounting /proc filesystem
Creating block devices
Creating boot device
Mounting root filesystem
mount: error 19 mounting ext3
pivotroot: pivot_root(/sysroot, sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
freeing unused kernel memory: 132k freed
Kernel panic: No init found. Try passing init= option to kernel.

cholzsc1 · 07-14-2003, 11:13 AM

This is my grub.conf file am i missing something or is there something i have to compile to get it to work?

#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-18.9custom)
root (hd0,0)
kernel /vmlinuz-2.4.20-18.9custom ro root=/dev/hda2=/ hdd=scsi
initrd /initrd-2.4.20-18.9custom.img
append="hdd=scsi"

title Red Hat Linux (2.4.20-18.9)
root (hd0,0)
kernel /vmlinuz-2.4.20-18.9 ro root=LABEL=/ hdd=scsi
initrd /initrd-2.4.20-18.9.img
append="hdd=scsi"

cnjohnson · 07-14-2003, 01:15 PM

Quote:

Originally posted by acid_kewpie
no it doesn't, it installs the modules, hence the name. you will still need to update grub. you won't alwaysneed an init idisk though, so just clone the existing entry and change the path to the new image e.g /boot/vmlinux-2.4.21-test

In fact, RH9 takes care of all the copying, and the updating of grub. See the RH 9 docs.

Cheers--
Charles

Moltag · 07-14-2003, 03:15 PM

>>"mount: error 19 mounting ext3"

Check to make sure that you set EXT3 FS support as static (<*>) in your kernel configuration.

I made that mistake once. My boot partition was ReiserFS and I compiled ReiserFS support as a module. Big mistake. How could the kernel load support for ReiserFS if the support module is on a ReiserFS partition?

So, as a best practice, it's always a good idea to hard-code FS support for whatever FS your boot partition's using.

solspin · 07-14-2003, 04:14 PM

You missed one final step:
make install
This command will update the GRUB file and copy the kernel to the /boot partition. You don't have to manually do anything. Simply reboot after that and the new kernel should appear in the GRUB menu.

cnjohnson · 07-14-2003, 06:50 PM

Quote:

Originally posted by solspin
You missed one final step:
make install
This command will update the GRUB file and copy the kernel to the /boot partition. You don't have to manually do anything. Simply reboot after that and the new kernel should appear in the GRUB menu.

Good eye! I didn't catch that. That would 'splain everything!

Cheers--
Charles