Zitat von Fernando im Beitrag #3482

---

My advice: Remove the NvmExpressDxe_4 module from the BIOS.

---

@OlEF,

You can try previous NvmExpressDxe_3 module...that's the one I prefered to insert instead of the Dxe_4

(I've attached .zip for you)

@N607,

Thank you for proposal. But i think Fernando is right, it looks like additional nvme module conflicts with default one.
I wonder if it's possible to disable or remove default module, another option is to patch older official bios (without nvme support).

My nvme mod work, only a thing i do not understand, there 2 controller nvme in device management

Zitat von Fernando im Beitrag #3497

---

Zitat von OlEF im Beitrag #3494

---

Is there a chance to replace NVME module in official bios with NvmExpressDxe4?

---

Due to the dependencies between the original EFI module named Nvme and the other 2 NVMe BIOS modules and the different GUIDs I would not replace the original Nvme by the NvmExpressDxe_4 module.
What you can try to do is to remove the original EFI module named Nvme and to insert the NvmExpressDxe_4 according to my guide (= start post).

---

All resolved, now its only one nvme device
Ven_144d dev_a802

@Fernando:
I removed Nvme, NvmeSmm and NVMEINT13 (is it enough? or something should be deleted as well?). But sometimes something still prevents NVME drive working full speed.
OS boots fast only in 7 of 10 attempts.

@Fernando ,

1. No in both cases, same behavior
2. I tried same disk in my laptop and it works like a charm. No issues with nvme boot, high speed.
3. I don't think problem with drivers, since disk shows random speed both in Windows and Linux. Same nvme drivers on windows work good in laptop.

I'll try to use another nvme disk with same pcie adapter and share results.

@Fernando ,

I did some tests and here are some of my findings.
I replaced nvme disk with another (Toshiba -> Colorful) under patched bios with cutted out original modules and faced same issue - random speed. However read speed on new disk was a bit faster (30mb/s versus 250mb/s, i think this fact can be ignored).

Then I flashed bios with original firmware and found that new NVME disk is bootable. Multiple boot attempts didn't show any speed issues, worked as expected.

Thus I can only assume there is some kind of hardware incompatibility which cannot be resolved. I'm out of luck :(

Hi Fernando,

I've found something really interesting. As you know, my motherboard is a SuperMicro X10DRi, which is a UEFI motherboard but does not detect or boot any NVME device before booting the OS form a non-NVME drive. Also in my case, I was trying to make it detect/boot an Ubuntu OS system.

Ok, this might be interesting for both Windows and Ubuntu/Linux guys.

When installing an Ubuntu system in a GPT disk (which nowadays as any modern disk), you must create a BIOS-boot or EFI partition. This partition is normally a 512MB, FAT32 partition with a /boot/efi mount point and, if possible (I didn't need it), a boot, esp flag (so two flags in the same partition). This partition must be created at the beginning of the disk.

Also, following that first partition -and here comes the trick-, we can add a second partition of 1GB and an ext4 filesystem, with a /boot mount point, no flag.

All of this can be done from a Live USB / Live DVD Ubuntu Installation drive during the installation or just loading an Ubuntu "fake" session, where you can install a program called "Boot Repair" and use gparted, Ubuntu's software for making/deleting/modifying partitions. This applies to any Ubuntu, Desktop or Server. Don't forget to choose the first partition (/boot/efi) for booting the system from.

The above is exactly what I did. You will need two disks: a SATA disk for these two partitions and your NVME disk where you want your OS to be working from. So the process is: the system boots from your SATA disk with GRUB2, which is Ubuntu's OS loader. Then, it detects your NVME SSD drive and you're done. The only problem is you will need that SATA drive in the first place just to load the OS loader. It doesn't work without any of the two small partitions.

Now, I've been working with Windows/Linux in the same PC and even same disk for many years, that's form 1995. My process has been always the same: first you install Windows and all its crap, and then you install Linux and fix the boot system with its OS loader. With Windows 10 and Ubuntu it's no exception, in fact is less problematic than other really tricky situations in the past. I'm saying all this because you may not be interested in working with Linux, but maybe you can make room at the beginning of your SATA drive for the two little partitions. Then you can install Windows in your NVME drive, but of course it won't be detected when booting.

BUT then you can boot an Ubuntu live USB session (imaging being able to work with a full Windows system but without installing it), install the two small partitions and also GRUB in the EFI one, and hopefully be able to boot Windows 10 without any Linux or anything else in your system.

So I have solved my problem and perhaps other people can solve it too.
Thanks