Well I looked into the code and there is a five second hard pause just for the logo. I can get rid of that and the red testing memory info.
Then its all good! Just digging in to the EDK2 source code.
For example did you know they included useless ‘Helloworld’ code in there. Could be removed to make it leaner…
@davidm71
I now believe we do not understand what you are talking about. What LOGO are you talking about, I have no DUET logo or no REFIND logo. I just have a split second red DXE, then a white memory testing progress bar, then the normal REFIND Boot Manager GUI for selecting the Operating Systems you want to launch at that time. What Logo?
If your talking about the OS list logo’s why on earth would we want to remove that? How would my eyes select the proper boot media if I couldn’t see the list of OS’s installed? LOL, and if you don’t want the OS logos, then why did you install the REFIND boot manager in the first place when that part was clearly "Optional". You could have just stuck to simple DUET only and set it up to boot only one OS automatically.
I took video to show you what I get. I see no DUET Logo and no REFIND logo, I just get that crappy red DXE flash, then it boots to REFIND Boot Manager so I can select the proper OS I want at the time, with Windows being my default.
@SkOrPn ,
Looks good! Nice job modding the DuetPkg!
Didn’t realize how far it has evolved. Thumbs up!
Thanks, but what modding? I have not touched a thing on it. This is EXACTLY as it comes from the first post in this thread.
@SkOrPn
Well… I did some, long story short:
That version, again, on the first page, is actually a sort of cherry build updated to 2017 since I manually updated (or modified) each of the module and the related components to allow the X58 to boot.
If you download the current ( or > than AUG 2013 ) GIT source version of EDK, chance are it will not boot on our platform.
Yeah but we already know this. I was saying that the downloadable version on the OP has not been modded "BY ME", as the previous user suggested.
@SkOrPn
Dunno! anyway, the 1E microcode for our CPU is out.
There some loss, depending by the task, coming with.
Hmm, 1E microcode? Is that an update to address Meltdown perhaps?
@SkOrPn
In theory a sort of mitigation is already implemented within the memory management of that DUET version.
The microcode is for the other one, it also seems to change\update the turbo ratio x core and something else.
On the DXSO everything’s seems fine, no nominal increase in temperature, both idle\pegged variance is 3c at most from previous 1D.
On the other X58, legacy based, pretty much same spec, I need to reseat the AIO with some extra rubber washer, cause the temperature difference doesn’t make sense << bracket was somehow off, changed also the thermal paste, so it’s the same.
So, if you plan to use it on your board, check the idle and under load temperature before.
Was wondering how many of you with NVME legacy rom on board needed to use the Duet method to boot? They say that with legacy rom mods arent needed?
Reason I ask is because Ethaniel found theres a Nvme VMware option rom included in the VMware Workstation package. With that you guys who have legacy rom
may be able to have native booting considering you can see your drive in your bios boot menu and had prior difficulty booting…
That’s a good question. I no longer have a NVMe enabled Legacy BIOS mobo. I gave my DX58SO to a good friend back in 2015, whos 2003 system had just died and he couldn’t afford to build a new system at the time and refuses to do anything AMD. So I gave him my i7-920 and DX58SO and we put a GTX 960 on it. He had never used an OS after XP but I managed to talk him into Win7 and a SSD, plus a new USB 3.0 card and a 4TB external drive. He is quite happy now.
I wish I could test to see if that DX58SO would boot to a 960 series SSD. Interestingly Intel kept updating its BIOS until mid 2013, so I would think if there is any truly Legacy board that has NVMe support it might be that one.
What size is that Option ROM? Would it fit inside these smaller Legacy BIOS’s by chance?
The DX58SO of mine came without BIOS, so, the firmware is kinda customized since I added NVME support for UEFI and other things…
anyway, the 960 boot normally with a DXE driver made for it, by default, with the intel bios 5600 release it won’t, cause there no driver within the firmware.
Oh, so the DX58SO just looks like an old school BIOS? I flashed BIOS 5600 onto it last. Is that 5600 UEFI? It appeared to my eyes just to be an old normal BIOS. How can you tell just by looking at it?
@SkOrPn
The DX58SO firmware uses UEFI. It’s not running in legacy ( real-mode [DOS] ).
If you open this file ( attached somewhere ) with something capable, you’ll see a full UEFI firmware, that’s the recovery I made to boot mine.
With a board like that and with native NVMe support, this thing could last a very very long time. In the future I could also install a hexa core Xeon for him and a NVMe SSD and it should run just fine for many years. Good to know… Thanks
@SkOrPn
Here if you need the native NVME driver for the DX58SO.
Notice to read at full extension the post mentioned before flashing something “made on spare time” into the board in your possession or anyone else board 
Its very small. About 8kb I think uncompressed. Working on a method to get the bios booting an Nvme drive just for kicks. Hold the legacy rom!
