grub2 making friends with puppy (linux)

[duruttye]

Hey oldfred!

I tried what you said, but it didn't work.

Error: file not found
error: you need to load the kernel first (or something similar), so I didn't load the kernel after all

this is in the grub.cfg:

### BEGIN

menuentry "Puppy 511" {
set root=(hd0,1)
linux /boot/lupu511/vmlinuz root=/dev/ram0 pmedia=atahd pkeys=us 
initrd /boot/lupu511/initrd.gz
}
### END

this is on the boot partition from where the ubuntu boots:

ls
bin    etc            initrd.img    media  root     sys  vmlinuz
boot   extlinux.conf  lib           mnt    sbin     tmp
cdrom  home           lost+found    opt    selinux  usr
dev    initrd.gz      lupu-511.sfs  proc   srv      var

when I copied it to this location, it asked if I want to replace vmlinuz, and I didn't replace it, I guess that belongs to ubuntu...

and this is the /boot/lupu511 folder:

/boot/lupu511$ ls
extlinux.conf  initrd.gz  lupu-511.sfs  vmlinuz

I can't really believe that there is nobody who wrote down how to boot puppy linux with grub2 from a clean, separate partition besides ubuntu, this is somewhat odd

Thank you for your time, I'm very close to giving up.

[duruttye]

I tried it without the

root=/dev/ram0

thing in grub.cfg, but it didn't do any good

[oldfred]

I just created a new partition sdc13 on my drive, but boot from sdb2 which is a gpt drive.

This worked:

menuentry "Puppy 511" {
    insmod part_msdos
    insmod ext2
    set root='(hd2,msdos12)'
        linux /boot/lupu511/vmlinuz root=/dev/ram0 pmedia=atahd loglevel=7 pkeys=us 
        initrd /boot/lupu511/initrd.gz
}

I did have to move lupu-511.sfs to the top level of the partition ( same as /boot not inside /boot) and created /boot/lupu511 with all the other files including vmlinux & initrd.gz.

[angelsguitar]

Hi.

I was just looking around for some references on how to boot Puppy using grub2 and found this.

Is it working alright? Did you solved your issue?

[melenegiorgo]

I actually made it work following this post

ust spent an "interesting" 2 hours wrestling with Grub2 after I downloaded the final release of Ubuntu 9.10 today.

I prefer to use Ubuntu's grub to boot all my distros and previously used the /boot/grub/menu.lst in Ubuntu. I did the same this time installing Ubuntu's grub into the MBR.

It picked up Windows xp, Windows 7, Ubuntu 9.10 and Ubuntu 9.04, Fedora 11 and Debian 5.

It failed to recognise any of my 5 Puppy frugal installs or Tiny Core Linux. But there again grub 0.97 also failed in that way.

Eventually got it to boot the Puppies so in case others want to do this, here goes (some of this is a repeat of what's above).....

1. As mentioned don't do anything to the /boot/grub/grub.cfg file !!!

2. Copy the file Quote:
/etc/grub.d/40_custom

somewhere.

3. rename it something like Quote:
41_puppy431



4. after the 5 lines of existing text add whatever you need to boot puppy ...see below.

5. move the file back to /etc/grub.d/

6. Code:
sudo chmod +x /etc/grub.d/41_puppy

to make the file executable.

7. Code:
sudo grub-makeconfig


then Code:
sudo update-grub



Without this the /boot/grub/grub.cfg file doesn't get updated.

8. Now the grub boot code that seemed to work for me was
Code:

menuentry "Whatever you call puppy" {
set root=(hd1,5)
linux /puppy431/vmlinuz psubdir=puppy431
initrd /puppy431/initrd.gz
}
EOF


Nice and simple. Obviously change depending on your installation. This was for Puppy431 residing as a frugal on sdb5 in a subdirectory called /puppy431. Note the numbering.

9. The way of describing a partition has changed!!!
I have my Puppies on sdb5 . This used to be described in grub as (hd1,4). Now it's (hd1,5).

10. Note that adding Quote:
insmod ext3

just after the menuentry line seemed to stop it booting.

Also adding a line Quote:
search --fs-uuid --set ehdn78sh-3738-6dg8-bba3-ehd76sgs6sgs

to identify the UUID of the partition that puppy is on didn't seem to be necessary.

This worked for puppy 412, 421, 431.1 and 431.

I am still struggling to get puppy214X working. It does work using the psubdir method above but you're back to having to tell it which pup_save file to use.

Make similar files for other puppies and note that grub will list them in numerical order so, for example, 42_puppy412 will come before 43_puppy214.

HTH
Dave

My puppy was in sda9 and I was keep writing root=(hd0,8) witch obsiously wrong due to changes.

The right thing to write is root=(hd0,9)

[mcdohl]

hi,
after googling here and there,
i actually didn't remember how i get to this and it works:

menuentry "Puppy linux 511 on sda7" {
set root=(hd0,7)
linux /boot/vmlinuz root=/dev/sda7 pmedia=atahd
}
### END

hope that help