setting up initrd / generic kernel in Grub2...can't load generic
So I am trying to figure out how to load the generic kernel in Grub2.
1. I have run the /usr/hare/mkinitrd/mkinitrd_command_generator.sh and ran the output: Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh Code:
### BEGIN /etc/grub.d/30_os-prober ### Code:
#!/bin/sh Code:
### BEGIN /etc/grub.d/30_os-prober ### |
could you tell me if Ubuntu is on the sda drive also. I have had some problems with install on sdb1 and slackware on sda1 and ubuntu thinking slackware is sdb1 and ubuntu is sda1.
Quote:
No root device. Quote:
Press your 'e' key from your GRUB Menu to switch into 'Edit Mode'. Use your 'Esc' key to return to the GRUB menu. why does grub see it but vmlinuz generic doesn't? Because when the small system grub2 rleases to the kernel the ext4 module is gone. now the kernel starts to run but can't load the ext4 because it is on a file system that it cant see. As you may know grub2 is for ubuntu. there is a couple other reasons but I need more input on your kernel panic code. |
Like you, I get a kernel panic in Slackware if I boot using the top menu entry (the "generic" kernel), but boot fine if I use the "huge" kernel. This is (as far as I know / can guess) not a problem with Grub2, it's to do with Slackware configuration - especially considering the huge kernel boots, and the only difference between the menu entries is the "linux /boot..." line. If you wanted to track down the source of the error, then you'd have to look at the difference between the huge and the generic kernels.
EDIT: No luck for me, at least, with Drakeo's suggestion, but that's the sort of thing I would expect it to be :) and the error I get is something like "Unable to mount root VFS filesystem on unknown block (0,18)" |
Quote:
like I said grub2 has problems with mapping drives and reading bios. Examples of the difference between Linux and GRUB device names. Quote:
|
There is a typo in your custom menu entry
Code:
#!/bin/sh Also, if you want "update-grub" to detect the initrd automatically, rename it to "initrd.gz-generic-smp-2.6.33.4-smp" @Drakeo It's slightly different in Grub2, the first drive is counted as 0, and the first partition is 1. So Code:
Linux: Grub Legacy Grub2 |
Quote:
Quote:
Can i Just ignore this and edit the non-working generic boot option to be the same as the current (spelling corrected) custom entry? --------- also thanks to Drakeo |
|
Quote:
|
guess I learn every day. thanks
|
Very helpful for Grub2'ers!
Have been fairly annoyed over the years that most "solutions" to getting a /boot initrd working seem to automatically keep **ASSUMING** that the Slackware bootloader is LILO instead of grub2. :mad:
This false assumption continues to be problematic for those having Grub2 load other distros and then getting continually, almost blindingly, push-pushed within the Slackware help guides into install the generic Slackware kernel with an initrd (of course using LILO) for maximum efficiency. Encouragement as in http://docs.slackware.com/slackware:beginners_guide and http://docs.slackware.com/slackbook:booting I think that the better solution is to go ahead and follow the 'mkinitrd' suggestions at http://docs.slackware.com/slackbook:booting and then halt before doing all that LILO junk the Slackware guides keep throwing at you. At that point, the previously mentioned steps for adding one or more file entry for /etc/grub.d/* are immensely helpful, followed by manually adding the ending generic kernel and initrd lines as Code:
linux /boot/vmlinuz-generic-smp-2.6.33.4-smp root=/dev/sda5 My hearty :twocents: |
Quote:
Quote:
Quote:
All that being said, if you feel that a lot of users are running into the same issues as you, you're more than welcome to update the Slackware docs. The forum isn't always the easiest place for other users to find information like this, since the terms in a search engine would turn up a lot of unrelated results. |
And maybe don't bring a 3 year old thread to life the next time.
|
Quote:
Instead of spewing your angry words, get wise and request a Wiki account or join the mailing list, so that you can propose a modification to that page. Or if you do not want an account, use the "Discussion" page to write your suggestions. Creating good documentation is not trivial, and it's very easy to stand at the sideline and point your finger. The Wiki team is always glad to get suggestions. |
All times are GMT -5. The time now is 01:05 AM. |