Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

sambul65
sambul65
Posted
Posted (edited)

WINDOWS WAKEUP FROM HIBERNATION WITH CLOVER

 

Since this is Clover General Discussion, I wanted to ask about booting Windows with Clover from NVMe drive hooked to a PCIe slot on a Legacy BIOS Motherboard that are still in mass use in less fortunate places (which are in majority on our small Planet). I hope you guys realize that NVMe drives become the low cost option to speedup an old system, and Clover is the ONLY way to boot them in UEFI mode in such setup for a typical user without modding an old BIOS.

 

Users clone onto NVMe drive and then convert an existing MBR based Windows install into GPT EFI Windows install by using Windows MBR2GPT tool before booting the OS with Clover. I couldn't find any Clover release fit to boot Windows from an MBR base NVMe drive hooked to a PCIe slot on a legacy PC, despite Clover boots MBR Windows installs from SATA drives, probably due to direct support by the Mobo chipset.

 

Upon boot the issue becomes evident: Windows can be sent to sleep or hibernation, but on some PCs can't wakeup from these (hibernation is more important for faster PC startup), or a user has to switch the PC Off-On by hardware buttons, and then OS boots up via Clover from its hibernation image if found. Some useful links are given here.

 

While wakeup from sleep & hibernation solutions were developed for Hackintosh, can you offer similar stable solution for current Windows releases, likely via prior set in Clover NVRAM records? I think for experienced developers this task has higher priority than playing with Clover GUI, since hibernation is the primary and widely used OS feature, while Clover menu is not even visible with timeout=0. 😊 While Apple is set to abandon Intel CPUs support, Clover support for Windows is getting a lot more relevant.

Edited by sambul65
  • Like 2
Max.1974
Max.1974
Posted
Posted (edited)
17 hours ago, sambul65 said:

WINDOWS WAKEUP FROM HIBERNATION WITH CLOVER

 

Since this is Clover General Discussion, I wanted to ask about booting Windows with Clover from NVMe drive hooked to a PCIe slot on a Legacy BIOS Motherboard that are still in mass use in less fortunate places (which are in majority on our small Planet). I hope you guys realize that NVMe drives become the low cost option to speedup an old system, and Clover is the ONLY way to boot them in UEFI mode in such setup for a typical user without modding an old BIOS.

 

Users clone onto NVMe drive & convert an existing MBR based Windows install into GPT EFI based Windows install with Windows MBR2GPT tool before booting it with Clover. I couldn't find any Clover release fit to boot Windows from an MBR base NVMe drive hooked to a PCIe slot on a legacy PC, despite booting MBR Windows installs on SATA drives, probably due to direct support by the Mobo chipset.

 

Upon boot the issue becomes evident: such OS can be sent to sleep or hibernation, but can't wakeup from any (hibernation is more important for faster PC startup), or a user has to switch the PC Off-On by hardware buttons, and then OS boots up via Clover from its hibernation image if found. 

 

While some wakeup from hibernation solutions were developed for Hackintosh, can you offer similar solution for current Windows releases, likely via prior set in Clover NVRAM records? I think for experienced developers this task has higher priority than playing with Clover GUI, since hibernation is the primary and widely used OS feature, while Clover menu is not even visible with timeout=0. 😊 While Apple is set to abandon Intel CPUs support, Clover support for Windows is getting a lot more relevant.

Hi 

Which Clover release are you using? Which Windows? 7, 10, 11? 

Edited by Max.1974
  • Like 1
sambul65
sambul65
Posted
Posted (edited)
On 12/12/2025 at 11:24 AM, Max.1974 said:

Which Clover are you using? Which Windows? 

 

BOOTING WINDOWS FROM NVME DRIVE WITH CLOVER ON A LEGACY BIOS PC

 

You likely don't suspect how tricky your 1st question is. I tried every public Clover release, and found that only 2-3 oldies can automap and boot Windows from the GPT UEFI formatted NVMe drive attached to my P45 chipset based legacy unmodified BIOS Mobo Gigabyte GA-EP45-UD3P despite being very popular in the past. But wait - there is more!!!!!! Even those releases v4439 and v5070 can only boot to Clover GUI on my Mobo if boot7 is renamed to boot as Slice suggested elsewhere when started from a pen drive prepped by BDU, or as ISO from a Ventoy pendrive. However, even these releases don't show the NVMe Boot option in Clover GUI, but at least allow to start the disk OS from shell by running the above code. Thus the request to enable startup.nsh, since config.plist can't recognise map -r instruction. Other users may find that a different older Clover release works better for their legacy Mobo and NVMe drive models.

 

However, the only way I found to directly boot the NVMe on my Mobo with timeout=0 is by booting Clover.iso v4439 or v.5070 from a prepped by Easy2Boot pen drive with 2 partitions. More tricks followed, as default install of Easy2Boot Pendrive already contains unpacked Clover v4458 with carefully selected by developer files from multiple Clover releases, yet it still doesn't boot NVMe drive attached to my Mobo. However, when Easy2Boot pendrive boots to Grub4DOS menu, a user can auto or manually start a chosen Clover.iso prior copied into a selected _ISO subfolder on pen's 1st volume, while Easy2Boot somehow mixes up at Clover boot its files from the ISO and pen's default EFI\Clover folder on its 2nd volume. This mind blowing combo produces the fruit: it shows up my NVMe drive in the booted Clover Menu, and offers several options to boot Windows from it!

 

I now setup autostart in the Clover config.plist of Windows boot from NVMe with EFI\microsoft\Boot\bootmgfw.efi, as it's faster than using Clover's bootx64.efi, and surprisingly allows the drive upon Windows boot be put into and later wakeup in a split second from hibernation without any special config on my part (!!!) by own Windows & Clover means. Wow... 😇 And I run current updated Windows 11 64-bit release 23H2, since Windows prevents installing latest Windows 11 R25H2 on my PC due to lack of certain security, virtualization and other modern Mobo features.

 

Last but not the least info bit was delivered by Slice recently that next Clover release will contain NVMe driver in boot6 and boot7 files. That presumably will easy enormous pressure on guys like me to learn just about everything on the topic published on most browsed tech forums in very compressed time to merely boot a modern hard drive with current Windows OS on an older PC. 😂 I'm waiting for a Clover release that finally implements booting Windows from GPT EFI NVMe drives installed in Legacy BIOS Mobos, and also supports Windows boot from an MBR formatted NVMe.

Edited by sambul65
  • Like 2
chris1111
chris1111
Posted
Posted (edited)

@sambul65 You can Try here Clover ESP Legacy R5164

There is no old boot6 and boot7 like BDU but it work on Legacy System, I just add NVME support

  

git clone https://github.com/chris1111/Clover-ESP-Legacy.git && cd $HOME/Clover-ESP-Legacy && ./Build.command

 

Edited by chris1111
  • Like 1
chris1111
chris1111
Posted
Posted
6 hours ago, Slice said:

I have to remind that the commit 

from Nov 8, 2025 changes the contens of boot6/boot7 files.

 

I've already mentioned this with several tests I performed on my Dell Optiplex 790 Legacy boot.
The changes to Duet affected the boot on modern systems, and I'm not talking about NVMe in my comment.

Since 3 or 4 years Duet not work for modern system for me on my Optiplex 790 thats why I use old boot6 and boot7 on clover 5164

Slice
Slice
Posted
Posted
17 minutes ago, chris1111 said:

 

I've already mentioned this with several tests I performed on my Dell Optiplex 790 Legacy boot.
The changes to Duet affected the boot on modern systems, and I'm not talking about NVMe in my comment.

Since 3 or 4 years Duet not work for modern system for me on my Optiplex 790 thats why I use old boot6 and boot7 on clover 5164

On my comp #1 old boot6 can't start from NVMe and new one can. Why? Because I inserted NVME driver directly into the boot to be joint by internal logics.

  • Like 1
chris1111
chris1111
Posted
Posted
1 hour ago, Slice said:

On my comp #1 old boot6 can't start from NVMe and new one can. Why? Because I inserted NVME driver directly into the boot to be joint by internal logics.

Check your PM 😁

  • Like 1
sambul65
sambul65
Posted
Posted (edited)
5 hours ago, Slice said:

See PM

The new boot7 doesn't change Clover boot results on my system. Probably corrresponding logic needs some improvement. It also shows some error in plist. I'm still able to boot the NVMe drive via Shell after Clover GUI starts, but not from Menu. Check PM for the preboot.log

 

13 hours ago, chris1111 said:

@sambul65 You can Try here Clover ESP Legacy R5164

There is no old boot6 and boot7 like BDU but it work on Legacy System, I just add NVME support

  

git clone https://github.com/chris1111/Clover-ESP-Legacy.git && cd $HOME/Clover-ESP-Legacy && ./Build.command

 

 

I hope so. Would you be able to post the Clover-ESP-Legacy.ISO, or its content is PC hardware dependent?

 

Can you guys explain why Clover can't boot Windows 11 from an MBR formatted NVMe drive hooked to the Mobo PCIe slot, while booting it OK from a GPT UEFI formatted NVMe drive (via Shell), and from MBR formatted SATA drive (from Menu)?

Edited by sambul65
  • Like 2
chris1111
chris1111
Posted
Posted (edited)
1 hour ago, sambul65 said:

The new boot7 doesn't change Clover boot results on my system. Probably corrresponding logic needs some improvement. It also shows some error in plist. I'm still able to boot the NVMe drive via Shell after Clover GUI starts, but not from Menu. Check PM for the preboot.log

 

 

I hope so. Would you be able to post the Clover-ESP-Legacy.ISO, or its content is PC hardware dependent?

Its not an ISO you need to build yourself from command I post

Install commandLine tool or Xcode to have Git installed

Edited by chris1111
  • Like 2
Max.1974
Max.1974
Posted
Posted (edited)

@sambul65   I used my Clover compilation tool, available in my GitHub signature, and here are all the compiled files (sym folder). I hope it helps, but also test Chris1111’s tools as well. ;) 

 

image.png.15dbf39a08ffc5013149d97a98115144.png image.thumb.png.08d67543418371fd4139974e0f2e54b3.png

 

image.png.b4b0f37357f49958202c341410c5b57c.png

 

Compiled by Clover Compiler Builder: https://github.com/maxpicelli/Clover-Compiler-Builder 

  

git clone https://github.com/maxpicelli/Clover-Compiler-Builder.git
cd Clover-Compiler-Builder
chmod +x setup.sh
./setup.sh

 

All Clover Sym folder complete  

 

MediaFire link:   https://www.mediafire.com/file/y4w5evku2aakgxx/sym.zip/file 

 

Alternatively, you can try older builds like NDK 

 

https://github.com/n-d-k/ndk_tools

Edited by Max.1974
  • Like 2
sambul65
sambul65
Posted
Posted (edited)
2 hours ago, Max.1974 said:

All Clover Sym folder complete  

 

Thanks for sharing. Slice also released v5165 on Github. Unfortunately, despite having NVMe drivers added to Boot6 and Boot7, it doesn't recognise my NVMe, so I used Reconnect -R from shell. Only Boot7 allows to boot Clover GUI when renamed to Boot. For now Legacy Boot is work-in-progress. (see log attached). I may check the NDK builds as well, however Easy2Boot pen with Clover_V5070.iso copied to it boots stable for me.

 

3 hours ago, chris1111 said:

Its not an ISO you need to build yourself from command I post

Install commandLine tool or Xcode to have Git installed

 

GIT doesn't compile your Clover Legacy version out of the box on a Windows PC, asking for more tools installed. Should it be only compiled on a target PC (why?), or you can post a compiled version?

preboot.log

Edited by sambul65
  • Like 1
chris1111
chris1111
Posted
Posted (edited)
2 hours ago, sambul65 said:

 

GIT doesn't compile your Clover Legacy version out of the box on a Windows PC, asking for more tools installed. Should it be only compiled on a target PC (why?), or you can post a compiled version?

preboot.log 17.32 kB · 0 downloads

its a clover install Package for macOS , you need a mac to using it

To solve your issue of boot nvme on windows try to add  NvmExpressDxe.efi

Hope that help ?

 

attaching files

NvmExpressDxe.efi.zip

Edited by chris1111
  • Like 4
chris1111
chris1111
Posted
Posted
21 minutes ago, sambul65 said:

 

Did you mean adding NVMeFix.kext to the EFI\Clover\kexts\Other folder on a pendrive formatted by BDU tool?

use only NvmExpressDxe.efi drivers NVMeFix.kext as no effect on windows

  • Like 2
sambul65
sambul65
Posted
Posted (edited)

@chris1111

This driver version doesn't make any difference compare to the driver now included with Clover. I'll probably wait until Slice improves his code logic of attaching to an NVMe disk the driver now included with Boot6 and Boot7. He seems to think Clover should support Legacy Boot in a generic manner with early intercept being the key but its seemingly not always the case, not for any Mobo. It may indeed require to reverse-engineer the old Clover releases code written after these Legacy Mobos become mainstream. Or better implement startup.nsh support in Clover.

 

Clover files included with Easy2Boot and files of Clover v5070 or v4439 when used in combination upon booting from Easy2Boot pendrive allow to boot legacy systems like mine from NVMe drive perfectly. It might be a good idea to check how they work and what's the difference compare to current Clover release. Don't forget, Easy2Boot developer spent 30 years in software engineering, and chosen files from various Clover releases very carefully, including those dated 2014+

 

It seems the main question is: why Clover current and older NVMe drivers, no matter how early launched in the boot process, usually timely identify presence, but for some Mobos fail to promptly connect to the NVMe drive, unless manually called later to Reconnect from Clover shell, which takes some time??? And how the file(s) from Clover v4458 included with Easy2Boot change the v5070 boot sequence allowing the NVMe driver to timely connect to the NVMe drive and show it in the Clover Menu???

 

Edited by sambul65
  • Like 1
chris1111
chris1111
Posted
Posted
2 hours ago, sambul65 said:

This driver doesn't make any difference compare to the driver now included with Clover. I'll probably wait until Slice improves his code of attaching to an NVMe disk the driver now included with Boot6 and Boot7.

Sorry I thought you were using an older version of Clover

  • Like 1
Alpha22
Alpha22
Posted
Posted

new update for Clover

 

Screenshot-2025-12-14-alle-10-17-23.png

 

@Slice

Kernel patch "Unlimit the number of Xhci Ports" will be in the menu "Binary patching"
Cancel restricting PCIe bus by zero number.
New package looks.
Include NVMe driver into CloverEFI for the possibility to launch Clover from NVME drive.

  • Like 6
sambul65
sambul65
Posted
Posted (edited)

I didn't notice at 1st look changes in the v5165 package GUI embedded theme compare to v5164 upon unpacking its ISO to a pendrive with BDU tool and booting Clover from it. Is it Mobo model dependent, and how to activate the new theme?

Edited by sambul65
  • Like 1
sambul65
sambul65
Posted
Posted
On 12/13/2025 at 12:54 AM, Slice said:

I have to remind that the commit 

from Nov 8, 2025 changes the contens of boot6/boot7 files.

 

I wonder why the nice thread Clover Change Explanations is no longer maintained? 😡

  • Like 1
sambul65
sambul65
Posted
Posted (edited)
On 12/15/2025 at 4:51 AM, MakAsrock said:

Update report - everything is OK

 

Thanks. How is your fork different from main release?

 

I wonder if its possible to add support for map -r  command to Clover GUI Options menu and also to config.plist in Boot - Arguments section, since reconnect -r seems to be supported in that section (or not)? That would hopefully allow to auto run the code below after NVMe driver start at Clover boot from the config.plist to launch OS from an NVMe drive on partially supported by Clover Legacy Mobos, since startup.nsh doesn't seem to work for that (or at all).

  

reconnect -r
map -r
fs0:\efi\boot\bootx64.efi

 

Edited by sambul65
  • Like 2
 Share
Go to topic listing
×
×
  • Create New...