07-06-2007
Steps of compilation
Hello All,
These are the steps i followed for compiling kernel 2.4.32, some times there may be some problems in the source files as well , so instead of wasting just download a stable source code again.. it will surely work...
--> Firstly in kernel compilation is configuring the kernel in case of 2.4 kernels...
--> enter make config or make menuconfig (i prefer that)... or make xconfig..
--> then do a make bzImage ( as for now zImage is obsolete..), this step creates the bootable kernel image. copy that to the /boot/ directory.
--> then do a make modules ( this would bake the modules)
--> then as a root user do a make modules_install ( this would create a folder in /lib/modules/(kernel version) which would contain the modules..)
--> Now the next thing u have to create a initrd image .. in the /boot directory, so
# cd /boot
# mkinitrd initrd-2.4.32.img [kernel version, 2.4.32]
--> The last step would create the .img which is the initrd image.
Now u have to edit the file /etc/grub/grub.conf enter the lines
/initrd /boot/(initrd img)
/kernel /boot/bzImage (the image of the kernel).
may be some entries of the root files system..
/root /dev/hda3 ( also some options u can enter..)
--> Finally reboot the system and if every thing goes okay u will be see the option in the grub boot loader prompt, select it and enjoy.........
--> Currently lilo is less popular , but may be some one cud write steps for editing the lilo.conf
Regards,
9 More Discussions You Might Find Interesting
1. SuSE
Hi All,
Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.
Cheers,
Brendan (4 Replies)
Discussion started by: Brendan Kennedy
4 Replies
2. Red Hat
Hi,
While trying to build the linux kernel - 2.6.24.2,
i get the following error message during initial phase(make menuconfig) :
scripts/kconfig/lxdialog/dialog.h:32:20: error: curses.h: No such file or directory <===
In file included from scripts/kconfig/lxdialog/checklist.c:24:
It seems... (1 Reply)
Discussion started by: amit4g
1 Replies
3. UNIX for Advanced & Expert Users
I have one big module 2.6.18 kernel mod.c
I want to divide this to several files.
The problem is to write right Makefile
lib1.h
lib1.c
mod.c
mod.c works fine normally but when I divide into several files
and try to compile with this makefile
obj-m := mod.o
mod-objs := lib1.o
... (3 Replies)
Discussion started by: marcintom
3 Replies
4. Red Hat
Hi All,
I am trying to compile Kernel 2.6.31 with arm-linux-gcc3.2.2 for s3c2440a, but I am not able to perform the task.
I am using Redhat 9
firstly i am using the following commands
$make s3c2410_defconfig // there is no error in execution of this command
next i run
$make
... (0 Replies)
Discussion started by: niranjanvg
0 Replies
5. Linux
supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" message comes.
I tried giving acpi=off to the kernel command line but same problem.It shows everything ok and no problem with memory and processors and power supplies.Wt could be the reason?
It has... (1 Reply)
Discussion started by: pankajd
1 Replies
6. Solaris
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies
7. Linux
I have complied the kernel with a default settings... now if I load this kernel , it'll load perfectly but the INTERNET is not workink... I think in the default settings The network modules are not included.. Can anybody help me out with the selection of the network module when i give "make... (1 Reply)
Discussion started by: naresh046
1 Replies
8. UNIX for Dummies Questions & Answers
I have installed ubuntu 11.04 on my system.
After this when I used to give uname -r it showed me kernel version as 2.6.38.
Now I had downloaded kernel 2.6.34.12 from kernel.org and installed it using the following steps:
make
make modules
make modules_install
make install
This created... (2 Replies)
Discussion started by: rupeshkp728
2 Replies
9. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
LEARN ABOUT REDHAT
mkinitrd
MKINITRD(8) System Manager's Manual MKINITRD(8)
NAME
mkinitrd - creates initial ramdisk images for preloading modules
SYNOPSIS
mkinitrd [--version] [-v] [-f]
[--preload=module] [--omit-scsi-modules]
[--omit-raid-modules] [--omit-lvm-modules]
[--with=module] [--image-version]
[--fstab=fstab] [--nocompress]
[--builtin=module] [--nopivot]
image kernel-version
DESCRIPTION
mkinitrd creates filesystem images which are suitable for use as Linux initial ramdisk (initrd) images. Such images are often used for
preloading the block device modules (such as IDE, SCSI or RAID) which are needed to access the root filesystem. mkinitrd automatically
loads filesystem modules (such as ext3 and jbd), IDE modules, all scsi_hostadapter entries in /etc/modules.conf, and raid modules if the
system's root partition is on raid, which makes it simple to build and use kernels using modular device drivers.
Any module options specified in /etc/modules.conf are passed to the modules as they are loaded by the initial ramdisk.
If the root device is on a loop device (such as /dev/loop0), mkinitrd will build an initrd which sets up the loopback file properly. To do
this, the fstab must contain a comment of the form:
# LOOP0: /dev/hda1 vfat /linux/rootfs
LOOP0 must be the name of the loop device which needs to be configured, in all capital lettes. The parameters after the colon are the
device which contains the filesystem with the loopback image on it, the filesystem which is on the device, and the full path to the loop-
back image. If the filesystem is modular, initrd will automatically add the filesystem's modules to the initrd image.
The root filesystem used by the kernel is specified in the boot configuration file, as always. The traditional root=/dev/hda1 style device
specification is allowed. If a label is used, as in root=LABEL=rootPart the initrd will search all available devices for an ext2 or ext3
filesystem with the appropriate label, and mount that device as the root filesystem.
OPTIONS
--builtin=module
Act as if module is built into the kernel being used. mkinitrd will not look for this module, and will not emit an error if it does
not exist. This option may be used multiple times.
-f Allows mkinitrd to overwrite an existing image file.
--fstab=fstab
Use fstab to automatically determine what type of filesystem the root device is on. Normally, /etc/fstab is used.
--image-version
The kernel version number is appended to the initrd image path before the image is created.
--nocompress
Normally the created initrd image is compressed with gzip. If this option is specified, the compression is skipped.
--nopivot Do not use the pivot_root system call as part of the initrd. This lets mkinitrd build proper images for Linux 2.2 kernels
at the expense of some features. In particular, some filesystems (such as ext3) will not work properly and filesystem options will
not be used to mount root. This option is not recommended, and will be removed in future versions.
--omit-lvm-modules
Do not load any lvm modules, even if /etc/fstab expects them.
--omit-raid-modules
Do not load any raid modules, even if /etc/fstab and /etc/raidtab expect them.
--omit-scsi-modules
Do not load any scsi modules, including 'scsi_mod' and 'sd_mod' modules, even if they are present.
--preload=module
Load the module module in the initial ramdisk image. The module gets loaded before any SCSI modules which are specified in /etc/mod-
ules.conf. This option may be used as many times as necessary.
-v Prints out verbose information while creating the image (normally the mkinitrd runs silently).
--version
Prints the version of mkinitrd that's being used and then exits.
--with=module
Load the modules module in the initial ramdisk image. The module gets loaded after any SCSI modules which are specified in /etc/mod-
ules.conf. This option may be used as many times as necessary.
FILES
/dev/loop* A block loopback device is used to create the image, which makes this script useless on systems without block loopback
support available.
/etc/modules.conf Specified SCSI modules to be loaded and module options to be used.
SEE ALSO
fstab(5), insmod(1), kerneld(8), lilo(8)
AUTHOR
Erik Troan <ewt@redhat.com>
4th Berkeley Distribution Sat Mar 27 1999 MKINITRD(8)