Puppy Linux Discussion Forum

Hi sorry if this has been asked before, but I could find any info anywhere.
I have a partion with debian on it and two partions with puppy on them.(one is a full install BionicPupand the other is a frugal fossapup64).
Now grub4dos will boot the puppies but not the Debian it gives Error 13: Invalid or unsupported executable format

(If I reinstall grub it will boot the debian and bionic but wont find the frugal.)
I would prefer to use grub4dos
I think i need to do something to the debian entry on the menu list but not sure what.
Thanks,
Ali

ali9000 wrote: ↑Fri Nov 27, 2020 3:28 pm

Hi sorry if this has been asked before, but I could find any info anywhere.
I have a partion with debian on it and two partions with puppy on them.(one is a full install BionicPupand the other is a frugal fossapup64).
Now grub4dos will boot the puppies but not the Debian it gives Error 13: Invalid or unsupported executable format

(If I reinstall grub it will boot the debian and bionic but wont find the frugal.)
I would prefer to use grub4dos
I think i need to do something to the debian entry on the menu list but not sure what.
Thanks,
Ali

Probably it's because of the same issue as described here: http://murga-linux.com/puppy/viewtopic.php?t=111376
Test if your Debian partition is 64-bit ext4, if so, it can be easily fixed, convert it to 32-bit, see also here: http://murga-linux.com/puppy/viewtopic. ... 51#1013051

Fred

Thanks for that Fred.
That was the major part of the problem.
It didn't boot from the menu entry but did boot from the Find Grub2 entry.
It was coming up error 15 file not found
I eventually figured out the menu.lst file needed to edited for the debian entry, the links to the vimlinuz file and initrd.img don't seem to work in grub4dos.
So I changed the lines in the menu.lst.
kernel /vmlinuz to kernel /boot/vmlinuz-4.19.0-9-amd64
and
initrd /initrd.img to initrd /boot/initrd.img-4.19.0-9-amd64

Well done

Just a little hint.
You could have looked in the grub.cfg what makes debian boot and "translate" it to menu.lst.
Often the syntax has to be changed a little, but it is not difficult to do.
Another possibilty sometimes is to chainload to the other bootloader.
Whatever works.