LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   initrd.gz and Grub2 (https://www.linuxquestions.org/questions/slackware-14/initrd-gz-and-grub2-4175489673/)

joshua60 12-31-2013 02:04 AM

initrd.gz and Grub2
 
Hi,

I've been told not to use 'huge' kernel but 'generic'. See:

http://www.linuxquestions.org/questi...fs-4175489134/

I am using Grub2 as bootloader and now I would like that Grub2 automatically detects the 'generic' kernel. Is it possible? How do I have to rename initrd.gz?

Thanks for your help and 'Happy New Year'

syg00 12-31-2013 02:43 AM

As you define the kernel with the "linux" statement, likewise for the "initrd" statement.
Documentation here.

aaditya 12-31-2013 03:15 AM

Hello, I had a similar issue, and got help here.

joshua60 01-02-2014 05:30 AM

I could run 'initrd initrd.gz' modifing grub.cfg but I got the following error:

No kernel modules found for linux 3.10.17.
mount: mounting /dev/sda8 on /mnt failed: no such device
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead.
You can try to fix it. Type 'exit' when things are done.
/bin/sh: can't access tty; job control turned off.

Richard Cranium 01-02-2014 08:41 PM

How did you generate that initrd.gz?

joshua60 01-03-2014 02:06 AM

I used

/usr/share/mkinitrd/mkinitrd_command_generator.sh

and

mkinitrd -c -k 3.10.17-smp -m ext4 (README.initrd)

as well.

ReaperX7 01-03-2014 02:51 AM

It's not recommended you use the Huge kernel, but honestly it works fine. I've found that Huge, for me when I used Slackware, was a better choice as dealing with the initrd.gz was just bothersome and a needless extra step that was only for someone wanting a kernel with a lighter memory footprint which, in my needs didn't matter.

Just take the safe option and stick with Huge. You can also remove the generic kernel package from pkgtools and grub2 will only detect huge.

Richard Cranium 01-03-2014 11:48 AM

Quote:

Originally Posted by joshua60 (Post 5091040)
I used

/usr/share/mkinitrd/mkinitrd_command_generator.sh

and

mkinitrd -c -k 3.10.17-smp -m ext4 (README.initrd)

as well.

What does
Code:

echo $(/usr/share/mkinitrd/mkinitrd_command_generator.sh -r)
show?

Which of those two commands did you run to create your initrd that was used to create that error message?

Could you also provide your /boot/grub/grub.cfg file contents?

Richard Cranium 01-03-2014 11:49 AM

Quote:

Originally Posted by ReaperX7 (Post 5091058)
It's not recommended you use the Huge kernel, but honestly it works fine.

The OP didn't ask "How do I not use the generic kernel?"

TSquaredF 01-03-2014 12:04 PM

Also, Reaper, refer to your sig & remember that if you have all those drivers loaded in your kernel, you are primed to do many things, possibly poorly.
Regards,
Bill

ReaperX7 01-03-2014 03:03 PM

True, but since I've been using a custom kernel with LFS, some of my drivers are located within the kernel minus several modularized drivers for certain hardware like video cards, sound cards, etc.

I've also used the Huge kernel as a basis to base my custom kernels off of also. In truth you could also recompile generic with the driver for your specific file system and not even need the initrd.gz as we'll and leave the rest to udev.

joshua60 01-04-2014 02:03 AM

Quote:

Originally Posted by Richard Cranium (Post 5091259)
What does
Code:

echo $(/usr/share/mkinitrd/mkinitrd_command_generator.sh -r)
show?

bash-4.2# echo $(/usr/share/mkinitrd/mkinitrd_command_generator.sh -r)
mkinitrd -c -k 3.10.17-smp -f ext4 -r /dev/sda8 -m usb-storage:xhci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd.gz

Which of those two commands did you run to create your initrd that was used to create that error message?

I first run /usr/share/mkinitrd/mkinitrd_command_generator.sh
then I deleted /boot/initrd.gz and /boot/initrd-tree and run
mkinitrd -c -k 3.10.17-smp -m ext4. Both gave the same error.

Could you also provide your /boot/grub/grub.cfg file contents?

Sure, here it is:

menuentry 'Slackware Linux (Slackware 14.1) (on /dev/sda8)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-2b64bf4d-d3b8-428d-81ce-516636141ac6' {
insmod part_msdos
insmod ext2
set root='hd0,msdos8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8 --hint='hd0,msdos8' 2b64bf4d-d3b8-428d-81ce-516636141ac6
else
search --no-floppy --fs-uuid --set=root 2b64bf4d-d3b8-428d-81ce-516636141ac6
fi
linux /boot/vmlinuz-generic-3.10.17 root=/dev/sda8
initrd /boot/initrd.gz
}

I would like to state that huge kernel is fine for me too.

Thanks

Richard Cranium 01-04-2014 06:50 AM

What does running the command
Code:

ls -l /boot/initrd-tree/dev/sda*
as root show?

Richard Cranium 01-04-2014 06:54 AM

You don't happen to have /boot on its own partition, do you?

joshua60 01-04-2014 09:35 AM

Quote:

Originally Posted by Richard Cranium (Post 5091765)
What does running the command
Code:

ls -l /boot/initrd-tree/dev/sda*
as root show?

bash-4.2# ls -l /boot/initrd-tree/dev/sda*
brw-rw---- 1 root disk 8, 0 Jan 2 12:03 /boot/initrd-tree/dev/sda
brw-rw---- 1 root disk 8, 1 Jan 2 12:03 /boot/initrd-tree/dev/sda1
brw-rw---- 1 root disk 8, 10 Jan 2 12:03 /boot/initrd-tree/dev/sda10
brw-rw---- 1 root disk 8, 11 Jan 2 12:03 /boot/initrd-tree/dev/sda11
brw-rw---- 1 root disk 8, 12 Jan 2 12:03 /boot/initrd-tree/dev/sda12
brw-rw---- 1 root disk 8, 13 Jan 2 12:03 /boot/initrd-tree/dev/sda13
brw-rw---- 1 root disk 8, 14 Jan 2 12:03 /boot/initrd-tree/dev/sda14
brw-rw---- 1 root disk 8, 2 Jan 2 12:03 /boot/initrd-tree/dev/sda2
brw-rw---- 1 root disk 8, 3 Jan 2 12:03 /boot/initrd-tree/dev/sda3
brw-rw---- 1 root disk 8, 4 Jan 2 12:03 /boot/initrd-tree/dev/sda4
brw-rw---- 1 root disk 8, 5 Jan 2 12:03 /boot/initrd-tree/dev/sda5
brw-rw---- 1 root disk 8, 6 Jan 2 12:03 /boot/initrd-tree/dev/sda6
brw-rw---- 1 root disk 8, 7 Jan 2 12:03 /boot/initrd-tree/dev/sda7
brw-rw---- 1 root disk 8, 8 Jan 2 12:03 /boot/initrd-tree/dev/sda8
brw-rw---- 1 root disk 8, 9 Jan 2 12:03 /boot/initrd-tree/dev/sda9
bash-4.2#

---------- Post added 01-04-14 at 04:35 PM ----------

Quote:

Originally Posted by Richard Cranium (Post 5091767)
You don't happen to have /boot on its own partition, do you?

No, I don't!


All times are GMT -5. The time now is 05:54 AM.