Booting Generic Kernel
So I'm aware this is a pretty popular topic so please don't bite too hard :)
I use Grub as my boot manager and as you can see below, there are two entries for Slackware: Code:
menuentry "Slackware Linux (Slackware 13.37.0) (on /dev/sdc1)" { From within "usr/share/mkinitrd" I ran "mkinitrd_command_generator.sh". The output is listed below: Code:
mkinitrd -c -k 2.6.37.6 -f ext4 -r /dev/sdc1 -m usb-storage:ehci-hcd:usbhid:xhci-hcd:jbd2:mbcache:ext4 -u -o /boot/initrd.gz Quote:
|
I forgot to add the output when I run the "mkinitrd" command, it's posted below (appears to go alright):
Code:
sudo mkinitrd -c -k 2.6.37.6 -f ext4 -r /dev/sdc1 -m usb-storage:ehci-hcd:usbhid:xhci-hcd:jbd2:mbcache:ext4 -u -o /boot/initrd.gz |
[deleted]
|
And do you need to tell grub where to find the initrd.gz?
|
Quote:
Code:
menuentry "Slackware Linux (Slackware 13.37.0) (on /dev/sdc1)" { |
But since the "huge" kernel works and that menu entry appears identical to the "generic" one, this shouldn't be an issue should it? I ran 'update-grub' afterwards to update the "grub.cfg" file. I'm using GRUB2 so it's full of that automated crap and doesn't like you to edit the "grub.cfg" file directly.
|
The huge kernel does not need an initrd, the generic one does.
By the way, why did you go out of your way to install grub2, when grub is on the install disc? |
Quote:
I've got grub2 on another hard drive that I've been using to boot whatever OS I need. I didn't install any bootloader for Slackware figuring I'd just use grub2 to boot it (since Slackware is on my third hard drive). However, I'm really sort of fed up with the fact grub2 wants you to run the "update-grub" script in order to generate the *.cfg file. I'm glad you told me that grub was on the install disk. I'm going to plan on either installing it or lilo later tonight in order to test out what you've said above. I know there's a file for custom entries on grub2 but then you just end up with whatever "update-grub" discovered plus what you've entered...what can I say, I don't like clutter :) |
If you have grub2 on a different drive on the same machine, then you really don't need to install any bootloader.
What I do is to make a menu.lst file in /boot/grub with entries that are symlinks. Then, when I update a kernel, I just update the symlinks myself and no update-grub is necessary to be able to boot. You can even have an entry for vmlinuz-old and initrd-old.gz to be able to boot your previous kernel. Here is what I use for my /boot/grub/menu.lst Code:
title S64 3.0-git-latest |
Quote:
|
Everything works! Thanks for your help...I ended up adding a "40_custom" file to Grub2 with the additional line "initrd /boot/initrd.gz" as you indicated above.
|
You're welcome.
Glad to be of help. |
All times are GMT -5. The time now is 08:22 PM. |