Barrowman wrote: Thu Mar 24, 2022 5:03 pm
Hi, I decided to give Puppy a look at today.
Downloaded bionic uefi 32 bit. used dd to get it on a USB stick.
Tried booting on my HP G6- 16Gig Ram.
Got to boot menu and picked the first option but it hangs at an underscore character and no further response.
Only way out was pressing and holding the Power button.
Any idea what is wrong?
I've posted in the xenial forum because the xenial uefi 64 bit hangs at a line drawing of a pup with a bit of decoration.
Hmmm... I've just completed installing Zorin OS (Ubuntu also works) onto an HP Probook 430 G8 laptop (dual-booting with the pre-installed Windows 10 Pro). I also have KLV-Airedale (from this forum) booting on it, but only from a usb stick. However... the latter of these was not easy... By default no chance to boot alternative distro from usb stick because of various UEFI Secure Boot characteristics of this machine; even turning OFF 'Secure Boot' alone didn't seem to be sufficient to get this to work (but I can't remember so worth trying that if you can - but if you are using Win 11 Pro then that needs Secure Boot ON, and Win 10 Pro happens to also need Secure Boot ON on my G8 laptop if, as pre-installed, BitLocker encryption is enabled in Windows). Of course your G3 may not have such complicated and rigid Secure Boot (including TPM firmware and more) requirements.
So to get KLV-Airedale to boot from usb, I needed to have it on a usb stick that had a grub2 on it that included a UEFI/BIOS puppy.cer on it, which on first boot the laptop asks me if I want to install via MOK utility, to which I answered yes and browsed for puppy.cer and let that burn into the UEFI-related firmware; after that I could successfully boot KLV-Airedale from usb stick (but not if I put the KLV-Airedale frugal install files onto the internal hard drive - that flipping wouldn't work - I guess HP has that firmware protected too and puppy.cer not sufficient for that one in the boot chain security checking - KLV can't mount the internal hard drive on boot...).
How did I prepare such a puppy.cer usb stick for using with KLV-Airedale? Well, actually, on other machine I booted up Fossapup distro and it includes program frugalpup installed (I think that's what it is called, but can't check right now), which allows creation of a UEFI capable usbstick for booting fossapup (you need to read the frugalpup help on how to use it - basically two steps: 1. Install the fosspup files to usb and 2. Install the Boot loader, which does the grub2 and puppy.cer part for you). Forum member 'shinobar' I notice provides something similar lately called Grub2boot or somesuch (you'd need to search the forum for it). I then tried booting with the now usb-stick installed Fossapup and it was then my laptop said needed Mok certificate and I let it burn the puppy.cer into the related UEFI firmware; fossapup then started booting but crashed. However, clearly the grub2 itself was managing, so I copied in a KLV-Airedale frugal directory and edited grub.cfg on the usb stick to boot that, and that worked......... So not difficult, but not easy either...
However, maybe your machine isn't SO SECURE like this stupid HP ProBook 430 G8 machine, though I have heard that some HP laptops are crazy like my one and very difficult to install Linux on. Ubuntu and larger distros like full install Fedora and Debian (and Zorin as it happens) seem to really understand UEFI boot with Secure Boot change even in full-on complex security configurations - so I was able to install either official Ubuntu or Zorin onto hard drive physical partition and dual boot with Windows 10 Pro with full Secure Boot active, but not thus far any of our forum distros (so far only that usb stick with KLV Airedale success for forum distros, not yet any Puppy - BionicPup a bit old, so I think you need to first use Fossapup to create that special usb stick and then 'maybe' BionicPup might boot, but certainly no guarantee if same HP-laptop-related issue as I have had).
So I hope your problem is something else and some of the 'other' advice on this thread works for you, but does sound suspiciously like Secure Boot related issue (and funnily enough, turning OFF secure boot was NOT enough to get things going on my machine, so more security involved somehow - alas, I don't know the details of how the latest and greatest 'security' UEFI stuff works; it seems to be getting much trickier and small distros like Puppy are under threat of not being able to be booted it seems to me).
A lot of the information provided on this forum re: booting via UEFI with secure boot or not is often only correct for the howto writer's own tested (perhaps a few years old) hardware. Unfortunately there are some machines out there which are much more difficult to boot Linux on (some later HP models being particularly difficult it seems - I had no problem with slightly earlier HP laptops so this really frustrating problem turned out to be a complete and unwelcome surprise to me...). It is reaching the stage (and going to become the 'norm') that every piece of firmware code and lib is going to need specially signed and every component involved in the boot process and maybe even running state... so simply signing grub2 isn't going to be enough and I wonder how we are going to cope with this since upstream repos firware and so on, for example from Ubuntu, are only going to be signed with Ubuntu keys).
Even if you make a special puppy.cer uefi type stick and register via Mok to your UEFI/bios, fossapup may be too old, but maybe you could then try VoidPup64 at that stage since that may have newer libs, firmware, and kernel than the likes of old fossapup; or try KLV-Airedale at that stage. Anyway, hope it is indeed something simpler like BionicPup and XenialPup simply being too old generally for your recent laptops.