My apologies for the belated reply but other things got in the way.
mikeb:
Thanks but I have been using root=/dev/ram0 for a frugal install. I see you
are using pup212. I believe ttuuxxx made a lot of changes making 214x
including how it boots. But I could be wrong.
Dewbie
Thanks for the suggestion of other puppies. I need to narrow it down and have always liked the look and performance of 214X but if I can't get it to boot with grub2 then that's a deal breaker for me.
I am quite happy with grub-legacy but need it to boot with grub2 for reasons I won't go into here.I am sure I got it working before but don't think it was 214X top 10 but an earlier version.
Colonel Panic
Glad you like the name. I have to say the same about yours!
Tried Legacy OS2 and had even more troubles booting it and it's a bit heavy for some of our PCs here. But if you care to give me your boot stanza so I can "translate" it to grub2 speak I'll give it a go.
.............................
This weekend I did some tests and found the following. FWIW I am using a single sata HDD with 4 primary partitions.
sda3 has Linux LXLE with grub2 installed to the MBR.
sda4 I am using to test puppies.
1. 214X Top-10 seems to have a problem with its grub-installer. Even if you select simple it gives you the expert menu and then it just goes into a loop
when you select install. Looks like it's broken.
So there's no way grub2 will boot it (unless you do a manual grub install from CLI.)
2. So I tried an earlier version of 214X ie RC5 which I had lying around. The
grub-installer works ok on this one. But still can't get grub2 to boot either
a full or frugal install.
3. So tried a newer pup 528 and both full and frugal installs worked like a
charm.
4. Then checked inodes and found that the gparted in 214x defaults to 128
inodes but lxle and pup528 use 256 inodes. Could this be the problem?
5. So I installed a copy of pup412 which booted like a charm even though I
noted it's gparted makes 128 inodes and uses the same version as 214X ie 0.3.3
6. Next I deleted LXLE from sda3 and installed 214x RC5 to it and installed
its grub to the MBR. Pup RC5 now booted happily (after minor changes to the boot stanza. Then installed 214X top10 to sda4 and this booted up after I had added it to the grub menu list on sda3.
The grub I used for pup528 was simply (these are the grub legacy versions, I used the grub2 "translation")
Code: Select all
title puppy on sda4 FULL install
root (hd0,3)
kernel /boot/vmlinuz root=/dev/sda4
and
Code: Select all
title puppy on sda4 FRUGAL install
rootnoverify (hd0,3)
kernel /puppy/vmlinuz root=/dev/sda4 psubdir=puppy
initrd /puppy/initrd.gz
For 214x I used
Code: Select all
title puppy on sda4 FRUGAL install
rootnoverify (hd0,3)
kernel /puppy/vmlinuz root=/dev/ram0 pmedia=sata psubdir=puppy
initrd /puppy/initrd.gz
7. Also there doesn't seem to be any way to make a save file in a subdirectory. it just plonks it to /dev/sda4/
8. And when I move the save file to the subdirectory it then asks me on boot up which I want to use but shows the save file twice.
Okay...any ideas guys?
It looks as if there was a change between RC5 and Top10 that screwed up the grub installer. Any idea in which of the 10 in-between versions it was?
Hopefully folk have noticed all this before and have a fix.
Grateful for any help as ever.
ET