Slacko won't boot with Grub 2

[martinus]

Computer has differnt Partitions
puppy has its own Partition
Normal boot with GRUB2 under Ubuntu:
Grub2 does not find Puppy even after "updat-grub"
What shall I write in grub.cfg for Puppy 520 or Puppy 533?

Martinus

[John Doe]

depends on if it's a full or frugal install.

I've got something like this for my full install:

# End GRUB global section
# Linux bootable partition config begins
title Linux (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro vga=normal
# Linux bootable partition config ends

I don't have frugal example for grub.

[Karl Godt]

example :

Code: Select all

menuentry "PUPPY LINUX 43 (on /dev/sda3)" {
	insmod ext2
	set root='(hd0,3)'
	search --no-floppy --fs-uuid --set b9df22eb-a9de-4e5b-8b08-f38594058ef7
	linux /boot/vmlinuz root=/dev/sda3
}

for full installs : UUID is obtained by

Code: Select all

blkid

command

and for frugals add the frugal bootparameters to the 'linux /path/to/kernel/vmlinuz" -line plus the usual initrd line below that "linux" -line

*
John : Puppy legacy_grub syntax is ^slightly^ different from grub_2 syntax and seemed to work for me sometimes but not always .

[John Doe]

... legacy_grub syntax is ^slightly^ different from grub_2 syntax...

whoops, missed that completely... I haven't been on a computer much for a few years.

[martinus]

Thanks for all information to get in Slacko with Grub2 24.7.12

I do not like "trial and error"
And i do not understand why developers often try to make things quite complicated. Complicated to use like the new UBUNTUs. Grub still seems to be a building plot. Grub2 now works quite automatically.
the main command is grub-update.

After lecture in internet, after hours and hours with trial and error I also found the old Grub methods are in Grub2 no longer successful.

GRUB2 introduces under
search..set about 30 ununderstandible codes in grub.cfg
The codes seem to differ so, that it makes no sense to copy one to another computer. That is meant with "Do not edit this file"
I recommend not to waste time ( as I did) to try those codes in Grub2 with the methods of the old GRUB. Now you can forget old rules with live CD, KNOPPIX and so on.

After all it is quite simple to start SLACKO with the boot loader GRUB2 under UBUNTU.


1. With Live CD I started SLACKO and made a FULL installation on a separate partition.
2. I switched over to that UBUNTU, which contained the boot GRUB.
3. I changed in terminal with sudo -s and Password to root
4. After inserting "update-grub" I could see how all my Programs on hd were found. (Merely "sudo update-grub" did not work. - It was not nessesary to remove "read only" on update-grub with chmod)
Grub could not identify Puppy as Puppy. Grub called it Unknown Linux.


With next start and "Unknown Linux" Puppy started normally within 20 seconds.
I wanted better information in boot loader window. So I went to boot partition, where I found grub.cfg under boot,grub. It was opened with editor.
In spite of "Do not open... "I changed the titles in menuentry lines. New were: Puppy, Ubuntu, XP with version-Nr and Partition identification.

Warning: all your personal inputs will be lost, when you use update-grub
ones more.

I repeated that successfully on three machines. So I think the problem is solved. You can "trial" Puppy now without error.

Martinus

[dk60902]

Maybe you can find this helpful. It's from Stu90

http://my.opera.com/stu90/blog/2011/01/ ... al-install

I have WinXP, Ubuntu 10.04 and Slacko 5.3.3 (frugal install) triple booting with Grub2.

[mini-jaguar]

example :

Code: Select all

menuentry "PUPPY LINUX 43 (on /dev/sda3)" {
	insmod ext2
	set root='(hd0,3)'
	search --no-floppy --fs-uuid --set b9df22eb-a9de-4e5b-8b08-f38594058ef7
	linux /boot/vmlinuz root=/dev/sda3
}

for full installs : UUID is obtained by

Code: Select all

blkid

command

and for frugals add the frugal bootparameters to the 'linux /path/to/kernel/vmlinuz" -line plus the usual initrd line below that "linux" -line

*
John : Puppy legacy_grub syntax is ^slightly^ different from grub_2 syntax and seemed to work for me sometimes but not always .

Yes, this works for frugal install, I did it exactly like that, with the uuid as well and initrd line added.

I didn't use the same hd numbers of course, and no quotes around the (hd0,3). Actually, I just tried it with the quotes and it works as well.

But for some reason my other OS won't boot anymore, and I didn't change anything in those entries.