Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
no initrd image with new kernel!!
Name: kyfs Date: November 12, 2002 at 09:09:51 Pacific OS: red hat 8.0 CPU/Ram: celeron 466/ 385MB
Comment:
i recently downloaded the latest stable kernel 2.4.19 and i configured and compiled it correctly (i know it was compiled correctly at least because i followed the instructions in "Linux Complete") when it was all done i couldn't find the initrd image anywhere..someone help.. thanx in advance,
Name: Jonathan Date: November 12, 2002 at 09:14:07 Pacific
Reply:
look in linux2.4.19/arch/i386/boot
Jonathan
0
Response Number 2
Name: kyfs Date: November 12, 2002 at 09:16:20 Pacific
Reply:
i did and it wasn't there...is it under a differnet name???
0
Response Number 3
Name: Jonathan Date: November 12, 2002 at 09:58:16 Pacific
Reply:
Well, not knowing what sequence of commands you used to build the kernel, I really couldn't say. I do know, however, that initrd images are not made by default when you build the 2.4.19 kernel. If you used the command "make bzImage" sometime during the build process, there will be a compressed kernel image present (file name will be "bzImage"). If you just used "make", then the kernel image will be in the file vmlinux. You do know the difference between the standard kernel image, a compressed kernel image, and an initrd image, right?
Jonathan
0
Response Number 4
Name: kyfs Date: November 12, 2002 at 17:31:21 Pacific
Reply:
here are the steps i used:
# tar xvzf kernel-2.4.19.tar.gz # cd kernel-2.4.19 # make mrproper # make config # make dep # make bzImage # make modules # make modules_install # cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.19
and rebooted. what am i doin wrong? i understand that the vmlinux image isn't compressed and the vzlinuz is compressed but i don't understand a whole lot a bought initrd image.
thanx a lot for all your help.
-kyfs
0
Response Number 5
Name: kyfs Date: November 12, 2002 at 17:32:39 Pacific
Reply:
correction: vmlinuz is compressed. i hate typos
0
Response Number 6
Name: armin Date: November 12, 2002 at 17:51:30 Pacific
Reply:
so it is clear now, you did not make an initrd :)
an initial ramdisk is used to provide device access for the kernel with device drivers that are built as modules. the modules reside in /lib/modules/`uname -r`.
for example: you have a scsi card and your / disk is attached to that scsi card. the kernel needs a driver for the scsi card so that it can mount the disks. if the driver for the scsi card wasnt compiled into the kernel but built as a module u need an initrd containing the scsi driver because the kernel cannot access /lib/modules because / is not mounted yet...get it?
the kernel and the initrd are read raw off the device, thats why u need the modules necessary for disk mounting either in the kernel or in the initrd.
if u have the necessary drivers compiled into the kernel u need no initrd
man mkinitrd
hth
0
Response Number 7
Name: kyfs Date: November 12, 2002 at 17:59:22 Pacific
Reply:
i really appreciate all the help.
thanx again
-kyfs
0
Response Number 8
Name: gregg Date: November 16, 2002 at 02:06:05 Pacific
Reply:
But how do you build such an initrd image?
0
Response Number 9
Name: Jonathan Date: November 16, 2002 at 14:33:39 Pacific
Summary: I'm a newbie to Linux. With that said, I have compiled a new kernel with the options I wanted. I made sure to include my NIC (3com 3c905) when compiling the new kernel. When I reboot, I get the [faile...
Summary: Hi, I've build the kernel but when i reboot it, it gives me message: kernel panic: no init found Try passing init= option to kernel. Now, I've initrd-2.4.18-14.img in boot directory. I have build ...
Summary: I did install linux on the 2nd partition of my 3rd IDE drive (/dev/hdc2) so that it can boot from a boot floppy. Linux is not installed on MBR. At this point, LILO boots my linux partition with no ...