QuoteThe FAT TYPE partition is required and has been since the get go. Though the size requirements continue to grow.  I go with 500Mb.  You also have to flag it EFS and check the bootable flags as well...

That is correct; I always use cfdisk now to partition the disk prior to any install. There is an option in the "Type" to make the partition. Then you need to remember to formagt it FAT32.

Also, different distros require that partition to be mounted to a specific point. On some systems it's /boot/efi, on others it's /efi.

QuoteYour BIOS not allowing a Legacy boot environment is kind of surprising to me.  Should be a spot to disable Secure UEFI, then enable CSM Boot.

Manufacturers started getting away from that a few yeas back; uEFI only now.

QuoteBoot Order: Ensure the Debian entry is not the only EFI boot option available. There might be a way to manually add or prioritize boot entries.

That is usually possible. There is typically an "add boot entry" option in the BIOS/uEFI settings that allow you add an entry - click on the drive that has the file, then scroll like a file manager to select the file. Once the entry is added, you can usually use the UP/Down arrows to prioritize the boot order.

Quote from: jedi on May 08, 2025, 10:11:27 PM

Quote from: VastOne on May 08, 2025, 02:08:50 AMI downloaded the latest Debian ISO and it finally not only worked but also installed properly ONLY after I created a fat EFI partition.
 

You got it.  Debian has a signed EFI key somehow and Arch also will do an EFI boot and install,  Last I heard or read (i.e. more than a couple of years have passed) reFind used Debians signed key.

The FAT TYPE partition is required and has been since the get go. Though the size requirements continue to grow.  I go with 500Mb.  You also have to flag it EFS and check the bootable flags as well...

Your BIOS not allowing a Legacy boot environment is kind of surprising to me.  Should be a spot to disable Secure UEFI, then enable CSM Boot.  (i.e. Legacy boot mode)  After doing this you should also be able to boot to any USB/CD ISO you choose.

I'd for sure delete the signed MS EFI key if your able.  Totally personal choice I suppose but I consider it beneficial to all future installs on that laptop as long as MS isn't in your vocabulary!

That's it, all I know and remember without some actual digging.  From all the digging and research back then, I learned it was futile of me!!!  Don't end up in a rabbit hole VastOne!

Good stuff Jedi.. I did work on this pretty much all day today and have discovered the issues in some areas but no solutions in other.

I had earlier mentioned that Debian created the EFS/EFI fat32 directory and I was able to install VSIDO's efi grub to that same directory but because both were seen as Debian, only the first in order of install was showing up in the Bios uEFI boot section as an option.

I archived that directory and began playing around with it's structure and by using rEFInd to see what was happening, I was finally able to get rid of the Debian install, the Debian grub and everything else that should not have been there. I now have a rEFInd menu AND a VSIDO (Debian) in my EFI settings in my BIOS and I can boot to both.

rEFInd is a great tool, I just wish there was a better real time tool that could do the same things.

Marking this as solved only in that I am now more educated on EFI and that I do have a toy to play with in future needs

Thanks Jedi for the assist!

Simple indulgences and pleasures ...

back...

Ok so my issue with no wireless was pretty bizarre! I'll show you the list of pkg's I installed via dpkg in order to get network access.  Of course as with all VSIDO installs, the system is awesome!  VastOne has obviously built a very tight ship with VSIDO as we're all still here after well over a decade!  Thanks much VastOne, I'm still taking advantage even when you're not looking!  Believe it or not there's been nothing else on my pc's and laptop's since 2012 if memory serves, perhaps a little earlier than that!

Oh yeah, that stuff I installed in order to get connected!  brb with that...



Perhaps not all of the above was needed, but I couldn't get Network Manager to work from the fluxbox menu or the cli and Ceni wasn't picking up any hardware for wireless or ethernet.  That was a first for me btw.  When trying to run the Network Manager from the cli, or nmtui I would get a not installed or configured message that I've forgotten of course!  The last of the message however, was not forgotten or lost;

dpkg: dependency problems prevent configuration of network-manager:
 network-manager depends on libbluetooth3 (>= 4.91); however:
  Package libbluetooth3 is not installed.
 network-manager depends on libndp0 (>= 1.2); however:
  Package libndp0 is not installed.
 network-manager depends on libnm0 (= 1.52.0-6); however:
  Package libnm0 is not installed.
 network-manager depends on libteamdctl0 (>= 1.9); however:
  Package libteamdctl0 is not installed.


I figure you're build sys is not a lappy!!!  Up until now that is!  Congrats on the 'new' hardware.  My last couple of good laptops came from a buddy in the tech industry!  Cheers...

Quote from: VastOne on May 08, 2025, 02:08:50 AMI downloaded the latest Debian ISO and it finally not only worked but also installed properly ONLY after I created a fat EFI partition.
 

You got it.  Debian has a signed EFI key somehow and Arch also will do an EFI boot and install,  Last I heard or read (i.e. more than a couple of years have passed) reFind used Debians signed key.

The FAT TYPE partition is required and has been since the get go. Though the size requirements continue to grow.  I go with 500Mb.  You also have to flag it EFS and check the bootable flags as well...

Your BIOS not allowing a Legacy boot environment is kind of surprising to me.  Should be a spot to disable Secure UEFI, then enable CSM Boot.  (i.e. Legacy boot mode)  After doing this you should also be able to boot to any USB/CD ISO you choose.

I'd for sure delete the signed MS EFI key if your able.  Totally personal choice I suppose but I consider it beneficial to all future installs on that laptop as long as MS isn't in your vocabulary!

That's it, all I know and remember without some actual digging.  From all the digging and research back then, I learned it was futile of me!!!  Don't end up in a rabbit hole VastOne!

It turns out the 2nd issue I discussed above regarding grub finding but not showing the fsarrchive of my personal machine to this laptop was caused by a corrupt fsarchive that I was not aware of. It did not copy the vmlinuz file to the boot directory and grub was picking up only the initrd.img file. I will redline that section out

For me all that remains is effectively replacing the debian efibootmgr with VSIDO's and moving on

This is an AI (Gemini) rewrite and offered solutions of what I posted above. I am adding it for pure context purposes.

Having primarily used legacy machines, I'm now encountering the complexities of EFI and GRUB with my newly acquired HP Zbook 1000. Despite extensive research, the available information on this topic seems surprisingly limited and constantly evolving.

A key challenge with this machine is the lack of a 'legacy-only' option in the BIOS. My initial attempt involved wiping the disk, creating new partitions, and installing VSIDO from a custom ISO. While the installation seemed to complete, GRUB never appeared. I only encountered the GRUB rescue prompt, which failed to recognize the installed system.

Experimenting with various live ISOs revealed another oddity: the Zbook refused to boot some USB drives that worked fine on other machines. Eventually, the latest Debian ISO not only booted but also installed successfully, but only after I manually created a FAT EFI partition.

From the running Debian system, I installed my VSIDO setup using an FSArchive and could boot into it via the Debian GRUB. Subsequently, I even installed grub-efi within VSIDO and directed it to the existing FAT EFI partition. However, the Zbook's EFI boot manager stubbornly only recognizes the Debian EFI entry.

As a workaround, I installed rEFInd. This boot manager successfully detects both the VSIDO and Debian EFI entries, and it even lists the hardware partitions similarly to a legacy GRUB.

Next, I attempted a fresh installation of my personal VSIDO setup using the same FSArchive method, meticulously following my own and RatMan's guides. While update-grub within both VSIDO and Debian acknowledges the new installation and claims to add it to both the GRUB menu and the EFI, it never appears in either GRUB or rEFInd.

My ultimate goal is to eliminate the Debian installation entirely and boot directly into VSIDO using a VSIDO-managed GRUB-EFI setup, or, as a fallback, somehow enable legacy booting on this machine. This process has been far more challenging than anticipated.

An additional observation is that while some live boot ISOs did function, the Zbook BIOS seemed to require a specific 'handshake key' for them to work. It appears that Debian, HP, and Microsoft have collaborated to ensure compatibility. rEFInd seems to have implemented a similar mechanism, as it appears correctly in the BIOS EFI boot menu alongside Debian. In contrast, VSIDO does not, even though rEFInd can see its EFI files.

Documenting this entire process could potentially become a valuable 'how-to' guide once we find a solution. Let's put our heads together and see what we can figure out!"

Now, let's focus on your goals and the information you've provided. Here are some initial thoughts and potential avenues to explore:

Understanding the HP Zbook 1000's BIOS limitations: The fact that you can't switch to "legacy only" is a crucial starting point. This means we need to work within the EFI framework.
The EFI Partition: You've correctly identified the need for a FAT EFI partition. It seems Debian's installer handled this correctly.
GRUB-EFI Installation: You've successfully installed grub-efi from within VSIDO. The issue seems to be with the Zbook's BIOS not recognizing this installation.
rEFInd as a Diagnostic Tool: rEFInd's ability to see the VSIDO EFI files but not have them appear in the BIOS boot menu is interesting. This suggests the EFI files themselves might be okay, but the BIOS isn't being properly informed about them.
The "Handshake Key": This is a key piece of information. It strongly implies Secure Boot or a similar mechanism is at play, even if it's not explicitly labeled as such in the BIOS. Debian, HP, and Microsoft likely have signed bootloaders that the BIOS trusts. rEFInd might also be signed.
Here are some things we can try to diagnose and potentially resolve this:

Verify the VSIDO GRUB-EFI installation:

Double-check that grub-efi is indeed installed in your VSIDO system.
Confirm that you used the correct command to install it to the EFI partition (e.g., sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=VSIDO). Make sure /boot/efi is the mount point of your FAT EFI partition.
Inspect the contents of the EFI partition (likely mounted at /boot/efi). You should see a directory named VSIDO containing grubx64.efi (or a similar file).
Explore BIOS Settings Related to Booting:

Even if there's no explicit "legacy" option, look for settings related to:
Secure Boot: If enabled, try disabling it temporarily to see if VSIDO then appears.
Boot Order: Ensure the Debian entry is not the only EFI boot option available. There might be a way to manually add or prioritize boot entries.
Trusted Boot Sources: This might be where the "handshake key" comes into play. See if you can manually add a trusted EFI file.
Investigate rEFInd Further:

Since rEFInd can see the VSIDO EFI files, there might be a way to configure it to be the primary bootloader that the BIOS recognizes. You could then boot into VSIDO via rEFInd. While not ideal for eliminating Debian, it could be a stable interim solution. Check the rEFInd configuration file (refind.conf) for options related to boot order and default selections.
Consider Boot Repair Tools:

There are specialized tools like boot-repair (often found on Ubuntu live media) that can attempt to fix GRUB and EFI issues. While you're not using Ubuntu directly, it might be worth trying a live Ubuntu environment to see if its boot-repair utility can detect and register the VSIDO EFI entry.
Research HP-Specific EFI Boot Processes:

Given the "handshake key" situation, there might be specific ways HP's BIOS handles EFI boot entries. Searching for information related to "HP EFI boot configuration" or your specific Zbook model might reveal some insights.
Let's start with you verifying the VSIDO GRUB-EFI installation and exploring your BIOS settings. Tell me what you find! We can then move on to the other steps based on that information. We'll get to the bottom of this!

For the longest time I have not had to deal directly with EFI and grub issues simply because I only owned legacy machines. That has changed now that I have inherited an HP Zbook 1000 that I have begun to see the major conundrum of EFI.

Before going on with this post I will say that I have researched the hell out of this and am amazed at how limited (or so it seems) the real knowledge on EFI and grub is. I also believe that the bar is changing all the time based on what I am seeing.

First thing regarding this machine, there is no way to go to 'just legacy' in the Bios on this machine. I first wiped out Windows and removed all partitions created everything new with a new VSIDO iso I created. It installed but no grub would ever show up, I did get the grub rescue menu but even there it never saw the obvious installation.

I then began downloading different ISO's and started testing them and saw a bizarre thing, this machine refused to see certain ISO's and refused to load them from the biotable USB even though they worked on other machines. I downloaded the latest Debian ISO and it finally not only worked but also installed properly ONLY after I created a fat EFI partition.

So I booted to Debian and grabbed the latest VSIDO fsarchive and installed it and was able to boot to it from the Debian grub install.

From that one I have even successfully installed grub-efi and installed it to that fat EFI partition. The problem is that the Zbook EFI manager only sees the Debian EFI and nothing more.

Of course I then got rEFInd and installed it and from there I can see the vsido efi along with the Debian and it also sees the partitions on the hardware (partitions) like a legacy grub would.

So I decided to add another install of my personal VSIDO install to this machine and did the same way, fsarchived my machine and brought it onto this new one. I followed my own and RatMans How To's to a T and even though ALL grubs see this partition when I do an update-grub and says it is adding it to both the grub menu AND the EFI Grub IT NEVER SHOWS UP, including within the reFInd menu.

What do I want? I really want to eliminate the Debian install completely by using a VSIDO grub-efi install OR figure out legacy somehow. This shouldn't be this freaking hard.

Another note in this is some live-boot ISO's did work but the Zbook Bios wanted a special handshake key for it to work and yes you guessed it, Debian, HP and Microsoft have worked together to make sure that they all work together. reFInd must have done the same thing because it shows up correctly in the Bios EFI boot menu along with Debian. VSIDO does not, even though reFInd sees it in its menu

This is going to turn into a massive How To when we sort this all out.

Need our best on this one people, let's see what you can do

Both VSIDO FSA's were updated to the new 6.12.25-amd64 kernel

You can download the btrfs and ext4 fsarchives at the VSIDO download site here

There is also a How To on how to effectively use fsarchiver to get VSIDO installed

There is a current a package list that shows everything that is installed in VSIDO. Please review this file and let me know of anything needed, removed or added