kernel upgradation

**kris.c** · 05-23-2007

I tried to update my SUSE-10.0 which came with kernel version number 2.6.13-15-default to the latest 2.6.21. I have copied the new bzImage and the System.map to the /boot directory. Now, I have to edit the "lilo.config" file. But the file doesnt exist in the /etc on my comp. When i tried to search for it, I got his outpout:

Code:

whereis lilo
lilo: /sbin/lilo /usr/share/man/man8/lilo.8

Ironically, there are many references to "/etc/lilo.config" in the file lilo.8.
I am a little concerned here, what should i do modify the boot loader. I hope someone replies soon. What can happen if i am forced to switch off my comp at this stage?

**gogalthorp** · 05-23-2007

Suse does not normally use LILO It uses GRUB

The menu file is

/boot/grub/menu.lst

But the structure is different so be careful with the changes Use the other entries as a guide

**kris.c** · 05-24-2007

Yes, you are right. I edited the grub file and i was able to boot into the new kernel

Buoyed by this, i wanted to another kernel up gradation, this time on an FC4 machine.
The menu.lst in /boot/grub on a Fedora-core 4 machine, has lines like :

Code:

 kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/
  initrd /initrd-2.6.11-1.1369_FC4.img

The initrd line was absent on my SUSE machine.
The equivalent initrd for the kernel that i am trying to upgrade to has not been created in the /boot directory.
How important is the initrd file?
Can I boot into the new kernel without including this line in the menu.lst file?
What should i set it to?

**devils casper** · 05-24-2007

Buoyed by this, i wanted to another kernel up gradation, this time on an FC4 machine.
The menu.lst in /boot/grub on a Fedora-core 4 machine, has lines like :

Fedora uses grub.conf file instead of menu.lst.

**kris.c** · 05-24-2007

Hmm.. Both grub.conf and menu.lst have the same content.
Which one should i modify?

And, with a bit of googling, i realised, i need the initrd if my device has SCSI devices. And my device does have SCSI devices. So, i found out that i need to do something like:

Code:

[root@dx1 boot]# /sbin/mkinitrd /boot/initrd-2.6.21.img 2.6.21

Where 2.6.21 is the new kernel directory in /lib/modules.
But, this is the error message i got:

Code:

No module mptbase found for kernel 2.6.21, aborting.

How do i get around this issue?

**kris.c** · 05-24-2007

Well, i got around that by commenting out all references to the mptbase and its now working.
Also, I had to compile the kernel on another machine so that I can conduct my TIPC experiments, I faced a new peoblem, though there was sufficient space in the hard disk of this machine, i got error messages saying something like - the images are too large and that some of the files have been truncated for both "make zImage" as well as "make bzImage". As a result of which the images have not been created in the /arch/i386/boot.
Is there a way out?
Out of curiosity, can i copy the bzImage that i created a few hours back on another machine into this machine's /arch/i386/boot directory and use it?. Both are of exactly the same architecture.

**kris.c** · 05-25-2007

To be precise, this is the error message that i got :

Code:

BFD: Warning: Writing section `.bss' to huge (ie negative) file offset 0xc0555000.
objcopy: arch/i386/boot/compressed/vmlinux.bin: File truncated
make[2]: *** [arch/i386/boot/compressed/vmlinux.bin] Error 1
make[1]: *** [arch/i386/boot/compressed/vmlinux] Error 2
make: *** [bzImage] Error 2

**gogalthorp** · 05-25-2007

Just guessing but do you really have enough room on the root partition? You may have room on the drive but it may be taken by the home partition.

**vskp1999** · 05-25-2007

Hi,
While trying to install gtk+-2.4 version i'm returning with the following error: please anyone help me in coming out with this problem.

checking for GLIB - version >= 2.4.0...
*** 'pkg-config --modversion glib-2.0' returned 2.4.0, but GLIB (2.6.0)
*** was found! If pkg-config was correct, then it is best
*** to remove the old version of GLib. You may also be able to fix the error
*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing
*** /etc/ld.so.conf. Make sure you have run ldconfig if that is
*** required on your system.
*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH
*** to point to the correct configuration files
no
configure: error:
*** GLIB 2.4.0 or better is required.

**kris.c** · 05-25-2007

I found out that this actually depends on binutils and this comp runs RH-9. I think that could be the problem. I guess i will just ask the admin to install FC-4 on that machine too , so that i can have a homogenous cluster. Thanks

Thread Tools

Display

kernel upgradation

Error while trying to install gtk+-2.4 tarball

Posting Permissions