H11DSi-NT Oculink Ports (P2_NVME0 and P2_NVME1) do not work

[Layla]

Using Windows Server 2019, I can't seem to get the Oculink ports to detect my pm1725a SSDs, using the SuperMicro branded Occulink cables.

Has anyone else run into this? Any ideas on what is required to make it work? I would have expected them to be detected in the UEFI BIOS itself.

 

[Layla]

The drives do get warm, but they just don't show up anywhere as viable devices.

 

[Layla]

Crap, I think I should have posted this in Motherboards. Oops. If anyone can move it, please do!

 

[mirrormax]

2.1 bios was needed to see oculink NVME disks on my rev2 board, i should have posted my build thread already since you ran into all my issues aswell it looks like.

 

[Layla]

2.1 bios was needed to see oculink NVME disks on my rev2 board, i should have posted my build thread already since you ran into all my issues aswell it looks like.

I believe I read that 2.1 is also incompatible with ZS (ES) processors (due to newer AGESA)? That's more than a bit disheartening to discover. I wonder if just the Oculink part can be extracted from 2.1 into 2.0?

 

[mirrormax]

yea mine are OEM and did work but also read ZS dont, could try i guess. otherwise only other option is bios modding, iam sure more people are interested in this as theres quite a few fixes in the later bios it seems

 

[Layla]

TTT on this thread - has anyone else gotten the OCuLink ports on the H11DSi-NT working with ZS processors?

 

[Layla]

2.0b (11/19/2019)
1. Changed BIOS revision to 2.0b.
2. Added "DRAM Scrub Time" to Memory Configuration.
3. Updated AGESA RomePI to 1.0.0.4 based on 5.14_RomeCrb_0ACMK012.
4. Set AMD CBS "PCIe ARI Support" item to be used instead of "ARI Forwarding".
5. Updated item string "Input the description" and "HTTP Boot One Time" to adhere to Rome
BIOS Setup Template v0.7_20190705.
6. Displayed 3rd IPMI version in BIOS setup.
7. Updated SSID of AMD Host Bridge according to each project's board ID.
8. Forced all PCIe to Gen3 only for H11 drop-in projects.
9. Displayed the "4-link xGMI max speed" setup item and set to 10.667Gbps by default on H11
DP drop-in projects.
10. Set IOMMU default to Auto (Enabled)
11. Displayed "Preferred IO" item.
12. Prevented display of any AMD memory error messages during the POST phase.
13. Fixed malfunction of recovery.
14. Added support for OOB SATA HDD information and asset information of 2 SATA controllers.
15. Fixed missing screen output when Boot Mode is changed to EFI.
16. Fixed problem of system hanging when installing NVidia RTX 2080/5000/6000.
17. Fixed the issue of "SMCI POST Screen Message" appearing on BIOS setup menu.
18. Fixed the issue of "SMCI POST Screen Message" appearing on POST screen when executing EFI
Shell application.
19. Corrected the CPM table setting.
20. Fixed failure of iSCSI function when LAN option is in UEFI mode.
21. Fixed problem of the xGMI speed reaching 16G after pressing “load default.”
22. Fixed problem of the default xGMI speed not being 10.6G.
23. Fixed problem of yellow exclamation mark appearing in Windows 2019 Device Manager when
running AST2500 VGA UEFI OPROM on NBIO1.
24. Fixed inability to detect NVMe device on P2_NVME0 and P2_NVME1 ports.
2.0 (9/25/2019)
Initial Release

2.0b (11/19/2019)
1. Changed BIOS revision to 2.0b.

3. Updated AGESA RomePI to 1.0.0.4 based on 5.14_RomeCrb_0ACMK012.

24. Fixed inability to detect NVMe device on P2_NVME0 and P2_NVME1 ports.

So 2.0b is the BIOS required to support the P2_NVME0 and P2_NVME1 Oculink ports. That BIOS also updates AGESA to 1.0.0.4

Make sure the bios has an Agesa < 1.0.0.3 because otherwise it will not work.

Does anyone know how to swap an older AGESA into a newer BIOS? I haven't had much luck with google on BIOS modding tools, and it's been almost a decade since I've done any BIOS modding...

Also, does anyone have a copy of the H11DSI-NT 2.0b bios to begin with? Supermicro only lists 2.4 on their website currently.

 

[mrpasc]

Try your luck here: https://forums.servethehome.com/ind...-ipmi-listing-including-older-versions.30007/

 

[Layla]

Try your luck here: https://forums.servethehome.com/ind...-ipmi-listing-including-older-versions.30007/

Thanks a million, exactly what I needed!

 

[niftylou]

I'm having similar issues.

I've got an NVMe M.2 connected to an Occulink . I've been able to partition the drive through Occulink using gparted on a live CD. I can also partition using Ubuntu Server Install on a USB Stick. I can install Ubuntu Server through Occulink via USB. However, I cannot boot. When using UEFI Shell, I can see the devices CTRL # in the UEFI Shell. The Verbose report shows it under CTRL 25C. But alas the BIOS won't set it at as a boot device. I think I know why...

The unique thing in the verbose reports under UEFI Shell is the MEDIA TYPE. While my SSD shows as a hard disk, the M.2 drive on occulink shows as "unknown"

I would like to somehow force the BIOS (possibly within the shell to see this drive as an actual Hard Disk so that it can register it as a boot device. There must be a way within the Shell to to force it to recognize the drive as a "Hard Disk." The M.2 Hard Drive is a KIOXIA SSD 2TB KXG60PNV2T04 XG6-P NVMe

In the first attached file (20240421_173125.jpg), you can see that Ubuntu Server 22.04 recognizes the KIOXIA NVMe on the Oculink Port NVMe_P0 on motherboard H11DSi-NT Rev 2.00. On this photo, the operating system happens to be installed already.



The second (20240421_173727.jpg) and third (20240421_173826.jpg) attachment shows the boot options in BIOS. As you can see, the motherboard does not recognize the NVMe on Oculink Port NVMe_P0. It only sees my Crucial SSD on Sata Port.

The final fourth (20240421_174414.jpg), fifth (20240421_180407.jpg) and sixth (20240421_183738.jpg) attachments digs a little deeper into the BIOS UEFI shell list of devices. The device CTRL is 25C. Dev tree shows the paritions under device CTRL 25C. All Partition CTRLS 25D, 25E, and 25F show up as "Hard Disk." However, Device CTRL 25C shows up as "Unknown.". I"m wondering if this is the reason why the BIOS is not recognizing the device in boot options?