@Black6spdZ

Did you end up figuring out your speed issue

Zitat von sibliss im Beitrag #706

---

@Black6spdZ

Did you end up figuring out your speed issue

---

@Black6spdZ

most people do not have this problem myself included, i am using a fairly new nvme myself and the driver seems fine so with that in mind i don't think it's a clover driver issue, I'm leaning more towards smbios
remember clover is a hardware emulator.

I'll refer to this wiki page regarding emulation https://sourceforge.net/p/cloverefiboot/wiki/SMBIOS/
so if i made a semi educated guess i'd say there's an issue with the emulation of the drive maybe ?

sorry i'm not much help on this i am no clover expert but i do what i can.

any way to bypass this Mac emulation? I may not be the only one here, has anyone else ever benchmarked their NVMe drives as a secondary drive before doing a clover boot/OS installation?

@Black6spdZ

There are options in the config.plist i just unfortunately do not know my way around the config.plist quite well enough to know exactly what we are looking for and which tags to edit.

Hi guys. Can someone please help because I cant even get clover to boot from USB no meter what method I try (BDU, Rufus, AIO, YouTube etc.). In tests it goes in boot loop on "booting from hard disk" and in real boot it goes to black screen and turns of my second screen. I didn't touch config.plist but in wiki it states to let it auto config before trying to set it up. I have Win10 on pretty old BIOS only Asus M4A79XTD EVO, AMD Phenom II 6X 1070T, 16GB DDR3 Kingston, 2TB HDD upgraded with Radeon RX570 8GB, and 120GB SSD as C: drive that i was hoping to replace with 500GB NVMe Kingston A2000 over adapter. Adapter can also take M.2 Sata and I have one of 250GB as external if that helps.

hello @BlackAdder
and welcome to the forums.

I have actually used clover with much success on an m4a series motherboard and almost identical system specs to yours.
In order to best help you resolve your issues please first ensure you have done a few things on your system.
1. in your existing win 10 install ensure you can access the nvme drive as a spare storage drive this proves that the adapter card works as intended.
2. try a few different usb sticks and run the BDU from your windows 10 installation to create a few clover usb's
3. remember to move the nvme driver file on the clover usb to activate it.
4. note that clover will only use/show on one of your screens.
5. insert clover usb and boot the computer do not remove the usb.
6. enter your bios and set your bios to boot from usb.
7. allow the computer to boot to clover from the usb. report here any errors

please refer to both OP #1 and my updated pined post see blue text in post 1 for details on how to do this.

Thx for welcome and quick and detailed replay. I already tried all of it before (and after) but didn't remember the stupidest thing of all and that is old USBs (I've been mostly using external drives). Still no luck. 3 stick same behavior. I'll get/borrow some newer ones and try again and report but in the mean time any advice about setting clover on 500MB Z: partition on HDD without having to format my entire HDD (D: and E: partition) as BDU would like to. That is the original plan, I wanted to get familiar with and learn Clover before any real work but I cant get damn thing even to boot into itself. And should I just migrate my C: drive or is fresh install better?

i've narrowed down the culprit.. it must be the nvmexpress driver. i ditched clover and just use a basic efi shell and autorun to load the nvme driver then map new drive to shell and launch windows.. same slow benchmarks however. I've tried 3 different nvme efi drivers that all perform just as bad. there is alot of performance being left on the table here probably for most using clover to boot from an nvme drive

Bump

So peculiar case. Got newer USB stick (unlike older ones bios reads it as generic mass storage) and managed to create and enter Clover using USBSetup program from this tutorial: [Guide] NVMe-boot for systems with legacy BIOS and UEFI board (DUET-REFIND) (2020 version is Clover), after that i managed to do the same on older stick and get clover to boot from new USB using BDU or this method. But next day after i returned to win and set up NVMe drivers in Clover i couldn't enter Clover any more. Both new and old USB behave the same with Clover (with or without NVMe drivers) going to black screen and not showing anything using BDU method and using other method Clover locks on load for a while the shows boot load error: couldn't load efi dvd/cd and couldn't load efi menu after it goes into Clover menu without keyboard or mouse so pretty much useless. I've been using MiniTool Partition wizard to format sticks along with BDU and USBSetup. Maybe that has some to do with it? NVMe drive works normally under the windows.

@Black6spdZ

Zitat von Black6spdZ im Beitrag #714

---

i've narrowed down the culprit.. it must be the nvmexpress driver. i ditched clover and just use a basic efi shell and autorun to load the nvme driver then map new drive to shell and launch windows.. same slow benchmarks however. I've tried 3 different nvme efi drivers that all perform just as bad. there is alot of performance being left on the table here probably for most using clover to boot from an nvme drive

---

The same card in same slot benchmarks MUCH faster as a slave in same PC booted from a sata drive.. How is this explained? When I mentioned driver I am talking about the low-level efi nvme driver, not windows.

Hi everyone.

I have followed this guide and successfully bootet from my NVMe already (on an Asus M4A785TD-V Evo). But it takes like 15 seconds until i even get to boot Win10. At this point i might aswell install the OS on my significantly slower 64GB SATA II SSD and use the NVMe only for programs and storage. Any help would be highly appreciated.
"timeout" was already set to 0 and I also tried giving my board time to initialize everything by waiting in the manual boot selection for a bit. "Log"/"Debug" already set to "false".

After BIOS I get a blinking " _ " for a couple of seconds, then a " 6 " and then a constant " _ " with a different font/size before booting into windows.


I read that BiosBlockIO may speed things up but I couldn't find out which files needed to be replaced and where to download the new ones.


Here's an extract of my preboot log of what i understand are the responsible steps (couldn't get a debug log to work):

Zitat

---

0:172 0:000 5 1280x1024 attr=BB - ok, edid+, working, highest, pref=5
0:173 0:001 6 1400x1050 attr=BB - ok, edid-
0:181 0:008 BV new mode: 5 1280x1024
0:333 0:152 SetMode pref 5 (5) = Success
5:518 5:184 CloverX64 : Image base = 0xCDAF7000
5:518 0:000
5:518 0:000 Now is 26.02.2021, 11:30:34 (GMT)
5:518 0:000 Starting Clover revision: 5131 (master, commit 949da631b) on CLOVER EFI

---

Zitat

---

5:587 0:000 Loading NvmExpressDxe.efi status=Success
5:620 0:033 - driver needs connecting
5:620 0:000 6 drivers needs connecting ...
5:620 0:000 PlatformDriverOverrideProtocol->GetDriver overriden
5:620 0:000 APFS driver loaded
9:811 4:191 === [ InitScreen ] ==============================
9:811 0:000 Console modes reported: 4, available modes:
9:811 0:000 - [01]: 80x25
9:811 0:000 - [02]: 80x50
9:811 0:000 - [03]: 100x31
9:811 0:000 - [04]: 160x53 (current mode)

---

Zitat von sibliss im Beitrag #717

---

@Black6spdZ

Zitat von Black6spdZ im Beitrag #714

---

i've narrowed down the culprit.. it must be the nvmexpress driver. i ditched clover and just use a basic efi shell and autorun to load the nvme driver then map new drive to shell and launch windows.. same slow benchmarks however. I've tried 3 different nvme efi drivers that all perform just as bad. there is alot of performance being left on the table here probably for most using clover to boot from an nvme drive

---

The reason you had the same results with 3 different driver's is because this is not a driver issue else i would have expect varied results. also if it were a driver issue everyone would have the same problems and we don't. I'm still leaning towards bios or hardware as i doubt this is emulation related. i would suggest trying your nvme adapter card in a different motherboard slot or even try a different card as we had learned repeatedly on this forum thread not all nvme adapter cards are created equal.
pcie 2 vs 3 number of pci lanes power handling etc these are all factors on adapter cards that can effect the way the nvme drive behaves.

Note for the record i have a samsung 970 evo and it actually exceeds it's rated speeds and it's an os drive booted with clover.

---