Puppy Linux Discussion Forum

Haha hoho and heehee. I DOOD IT! Ventoy (and Bookwormpup64) is working again even though I have the
Window update that broke Ventoy. You are going to spaz when you see how easy it is to fix. No need to disable Secure Boot.

1) Get an ISO of the newest Ubuntu. Linux Mint doesn't have the mmx64.efi file.

2) Copy BOOTX64.efi and mmx64.efi from EFI/BOOT folder to the VTOYEFI partition EFI/BOOT folder. The partition can be made visible in Windows by using Storage Settings or I suppose This PC/Manage to give it a drive letter. You can extract the files from the ISO with Winrar. Watch the filenames. BOOTX64.efi needs to be just that.

3) Rename grub.efi in /EFI/BOOT as grubx64.efi.

You may kiss my big toe now. lol

@HarveyH

Great find!! I think this topic/post should be more prominent and perhaps a topic in the How-To section and or make this topic sticky.

In any case it's probably a big help until it is known that there is a fix from the Ventoy dev's

@Clarity perhaps can also test this if possible.

I'm curious if above workaround for Ventoy works also for puppy distros frugal installed to internal hard drive. My computer uses grub2 from full installed Linux Mint.

In the past when experimenting thus with secure boot it wasnt a problem booting frugal installs from usb sticks, but secure boot seemed to to then require ubuntu signed kernel to boot from internal drives. That serious restriction didnt seem to apply to booting from usb sticks back then. Sounds like secure boot has tightened up a bit.

My request would therefore be to also try booting puppy or KLV frugal install on internal drive. Ok for ventoy usb stick is certainly useful.

On a wild hunch, I tried replacing those 2 files on a Rufus-Created BookwormPup64 USB drive and for the first time ever IT GAVE ME A CHANCE TO ENROLL THE MOK key (the "cer" file, right?)

It still didn't work. Keeps going back to the enroll the key part. Oh well, I did get a lot further than ever before to getting Puppy to boot natively. It never got that far before. It used to just say policy forbids booting that.

I think I read that no Puppy ever had a working MOK key. If that's true, then I'll take this as a technical win.

That's OK. Ventoy is fine and Ventoy works now with those file replacements.

1. Add Fatdog ISO to test on Partition #1. (I keep all my ISO in a folder on it named BOOTISOS for both housekeeping reasons as well as in the event I boot SG2D as if will find and list any ISOs in that folder. This allows Ventoy and SG2D to find all ISOs on the partition.) @fatdog is found here on the forum

2. When Ventoy boots, launch FATDOG ISO. Ventoy will offer 2 options to boot: take its default, not the Ventoy GRUB2 offer to the FATDOG boot menu.

3. Observe FATDOG's Menu to Menu setup (their distro works with Secure Boot and is clever in MOK registration. @jamesbond has a FATDOG webpage describing one-time registration and path for such)

Enjoy
Report here any ideas for Puppy users and developers as this continues to make PUPPY Linux relevant and easy to use via the ISOs, OOTB.

wiak wrote: ↑Fri Sep 13, 2024 2:00 pm

I'm curious if above workaround for Ventoy works also for puppy distros frugal installed to internal hard drive. My computer uses grub2 from full installed Linux Mint.

Uh, Linux Mint is one of those Linuxes that still work fine.

I cannot answer your question, but my guess is that the "evil" Windows update tells the UEFI to ignore all BOOTX64.efi(?) that aren't modern and official. This is my guess as to why the Ventoy hack works. When Ventoy boots with the replaced files, the system says, "OK cool, it's Ubuntu. I will allow it to boot." <-- WILD GUESS

I would *think* that the "Ventoy Hack" would also work with a real install of Puppy. You would be making the system think that Puppy is really Ubuntu <---WILD GUESS

My dumb-ass opinion: if your Puppy install won't boot anymore, try it. Rename the existing bootx64.efi and mmx??? to something else and add the files from Ubuntu. What could you lose, a little time? You can always put it back.

Note: The EFI partition is windows format, so just use Storage Setting/Advanced/Disks and Volumes to give that partition a letter so Win can access it.

DISCLAIMER:
I am an idiot and don't know sh**. Don't take my word for anything. Do stuff at your own risk.
Batteries not included.
Not valid in AK and HI.
May cause anal leakage.

rockedge wrote: ↑Fri Sep 13, 2024 1:41 pm

@HarveyH

Great find!! I think this topic/post should be more prominent and perhaps a topic in the How-To section and or make this topic sticky.

I reposted the basic info in the How-To/Boot section.

https://forum.puppylinux.com/viewtopic.php?t=12667

NONSENSE POST REMOVED