Hello, I built a custom "gutsy gibbon" kernel, but I can't find the corresponding initrd.img file. There's a link in / that looks like this: initrd.img-> boot/initrd.img-2.6.22-generic. Shouldn't there be a new initrd.img file that was created when I built the new kernel or am I missing something? TIA, -- -Chuck
vze284qe@verizon.net wrote:
Hello,
I built a custom "gutsy gibbon" kernel, but I can't find the corresponding initrd.img file. There's a link in / that looks like this: initrd.img-> boot/initrd.img-2.6.22-generic.
Shouldn't there be a new initrd.img file that was created when I built the new kernel or am I missing something?
TIA,
If you built all of your necessary drivers to boot the machine into the kernel (not as modules) you don't need a initial ramdisk. Just set your grub to point to the kernel image. --karl
Chuck wrote:
Hello,
I built a custom "gutsy gibbon" kernel, but I can't find the corresponding initrd.img file. There's a link in / that looks like this: initrd.img-> boot/initrd.img-2.6.22-generic.
Shouldn't there be a new initrd.img file that was created when I built the new kernel or am I missing something?
TIA,
Yes, there should be a new initrd.img after you install the new linux-image.deb file that you created. Did you get a vmlinuz link to the correct kernel image, or is that still pointing to the generic kernel? I'm assuming you did this the debian/ubuntu way, and ran a command that looked something like this - make-kpkg -initrd --revision=ck12 kernel_image kernel_headers modules_image That should create some .deb files in the parent directory. Then you use 'dpkg -i' to install those debs, and you should end up with new links for vmlinuz and initrd.img. If you did everything right, and it still doesn't work, I'm not sure what to say. Did you check the ubuntu forums to see if others are having the same problem? Greg
vze284qe@verizon.net writes:
Hello,
I built a custom "gutsy gibbon" kernel, but I can't find the corresponding initrd.img file. There's a link in / that looks like this: initrd.img-> boot/initrd.img-2.6.22-generic.
Shouldn't there be a new initrd.img file that was created when I built the new kernel or am I missing something?
I'm not sure what process you used to build your kernel, but it's not uncommon to have to build the initrd yourself. mkinitrd /boot/initrd-2.6.X-mumble.img 2.6.X-mumble Cheers, Jeff
participants (4)
-
Gregory Avedissian
-
Jeff Moyer
-
Karl Hiramoto
-
vze284qe@verizon.net