@knightrider2003

Zitat von knightrider2003 im Beitrag #555

---

@sibliss how does that tool do that? It doesn't change folderstructure at all.

---

@sibliss seems like the disk already was in basic gpt, that's why clover could read it. Then the bootpartition, it hasn't a drive letter. So can't edit it. So clover is looking for the uefi folder structure, while it is still in bios folder structure after being converted to gpt.

@knightrider2003

so give it a letter with disk part ?
Also clover should not be looking at file structure, does your volume have a label ?

@sibliss just a '*' .

Zitat von Mrus im Beitrag #35

---

Hi @mireque

Finally managed to start working. All you have to do is to create startup.nsh file under shell.
Just go:
Shell> fs0:
edit startup.nsh

Then insert all commands, save and exit.

After restart it worked.

Have another question. Can i skip 5second waiting time, and load startup.nsh script immediately.

---

seems vrm is not good, so voltage dropped again to 3 volt. A little lower and the nvme gives code 10 error and doesn't work.

@knightrider2003

If I understand correctly you are having under voltage issues ? If so It is most likely one of 3 issues first being that your motherboard cannot supply adequate power to the pcie bus and the adapter card. Second your adapter card may be faulty or just slightly out of spec enough to cause an issue for you. And lastly it's worth checking your computers power supply to ensure it is performing properly... I've had issue's with power supllies under volting once loaded in the past.

Sorry I can't be of great help without more information.

@sibliss i inspected the beneath side of the mainboard. There are some black stains right where the vrm is. When i completely drain the mainboards voltages, it's back at 3.2 volt. Then after a week it's 3 volt. Overclocking, but also the spectre bug i think has caused this. Cause the spectre bug made the pc randomly shutdown, like i hit the switch at the back. Intel has done several years to find the bug :) . With an amd system i didn't have that back then.

Hi
I have an MSI Z87-G41 motherboard coupled with a I5 4670K. I bought a PCIe card in which i can put a nvme drive there and windows can see it as a second drive. I cloned the main drive and after doing this i removed it but in my bios there is no way i can boot from the PCIe card that contains the NVME drive. Is there any way the bios can be modified in a way that the NVME drive will be seen in the bios and allow me to choose that one as a boot drive?
Thanks

@Spanish_Tony

Zitat von Spanish_Tony im Beitrag #564

---

Hi
I have an MSI Z87-G41 motherboard coupled with a I5 4670K. I bought a PCIe card in which i can put a nvme drive there and windows can see it as a second drive. I cloned the main drive and after doing this i removed it but in my bios there is no way i can boot from the PCIe card that contains the NVME drive. Is there any way the bios can be modified in a way that the NVME drive will be seen in the bios and allow me to choose that one as a boot drive?
Thanks

---

@herrscher

Zitat von herrscher im Beitrag #560

---

Zitat von Mrus im Beitrag #35

---

Hi @mireque

Finally managed to start working. All you have to do is to create startup.nsh file under shell.
Just go:
Shell> fs0:
edit startup.nsh

Then insert all commands, save and exit.

After restart it worked.

Have another question. Can i skip 5second waiting time, and load startup.nsh script immediately.

---

For some reason this does not work for me. I also tried creating the same file using notepad++.

I created the file the following method:
Shell> edit fs0:\startup.nsh
--- added a single line inside ---
fs0:
ctrl+s
enter
ctrl+q

Shell> cat fs0:\startup.nsh
fs0:

So I have startup.nsh under root of fs0. The reason having a single line inside the file is to debug the failure isolating other potential errors.

Shell> fs0:\startup.nsh
Command Error Status: Out of Resources

It seems like some memory allocation problem. Is there anyone who suspects what could be the problem?

///
Actually inside startup.nsh final goal is to have:
fs0:
load efi\clover\drivers64\NvmExpressDxe.efi
map -r
fs1:
efi\boot\bootx64.efi

---

Zitat von sibliss im Beitrag #566

---

Please be aware this is the clover boot method forum and clover does not use the startup.nsh, If i am not mistaken that is used by duet ? are you trying to use duet or clover ? if you are using duet method i suggest posting in that forum.
If you are trying to use clover please start from the beginning and ignore those comments about the startup.nsh.

If you have any clover questions please post them here and i will do my best to help you.

---

@herrscher
what i meant is that clover is built on duet but 99% of clover issues are not that deep.
normally it's a case of putting the drivers in the right place.
you should be in clover\drivers64\uefi\NvmExpressDxe.efi not directly in clover\drivers64\NvmExpressDxe.efi
did you install clover with the BDU ? have you not also put the driver in both Efi\CLOVER\drivers\bios and Efi\CLOVER\drivers\uefi ? clover will look in these 2 directories first. it doesn't look like you are actually using the newer X64 driver so i would try going the typical 32bit route first... note these two directories are not the same as the drivers64 directory you mentioned i recommend using the directories generated by the BDU but you can always throw these in with no ill effects.

fun fact it actually doesn't matter if you use uefi clover or even if you use x64 or x32 clover all it has to do is call the windows bootloader, after which the windows bootloader will set it's own settings regardless of what settings clover uses.

hehe, voltage is back at 3.15 again :) so nvme is working again. Don't know what i did to get it back up again. Pc had some trouble booting this morning though.

Zitat von sibliss im Beitrag #568

---

@herrscher
what i meant is that clover is built on duet but 99% of clover issues are not that deep.
normally it's a case of putting the drivers in the right place.
you should be in clover\drivers64\uefi\NvmExpressDxe.efi not directly in clover\drivers64\NvmExpressDxe.efi
did you install clover with the BDU ? have you not also put the driver in both Efi\CLOVER\drivers\bios and Efi\CLOVER\drivers\uefi ? clover will look in these 2 directories first. it doesn't look like you are actually using the newer X64 driver so i would try going the typical 32bit route first... note these two directories are not the same as the drivers64 directory you mentioned i recommend using the directories generated by the BDU but you can always throw these in with no ill effects.

fun fact it actually doesn't matter if you use uefi clover or even if you use x64 or x32 clover all it has to do is call the windows bootloader, after which the windows bootloader will set it's own settings regardless of what settings clover uses.

---