OK, I took the risk anyway and yes it still works on my 1080p TV. It did NOT work for my Korean monitor as I expected. I just need a new GPU for that to work. Maybe some day I can eventually afford one, but not yet.
Thanks again @noInk very excellent work.
@SkOrPn
In theory, with the update I just made today the resolution shall now always fixed @ the highest available.
On the laptop it works, it didn’t had the same issue as your since it was displaying on the lowest, anyhow give a try and see perhaps it also fix the monitor aww saw the reply,
Did you check if the EDID of the monitor is fine?
On the TV I suppose it should work now in 1080 if it didn’t before.
@noINk
Yeah the 1080p worked just fine. The TV has saved me many times before (I used it for 1080p gaming years back). Not sure about the EDID on the DIY display though. The input PCB is just a pass-through device with no controller chip or scaler built in. The GPU is responsible for the scaling and the displays pass-through device just converts DVI directly to LVDS, which is why I need special drivers for overclocking it to 120hz. I found an AMD utility to download the EDID and lol its just numbers and letters that mean nothing to me.
How would I check if the EDID is OK? Or better yet, why exactly would I check that? Nothing is broken on it. Only my Dell 2407WFPb is broken and in dozens of pieces, lol. I am making a list of parts to repair the Dell myself, but not yet finished with my diagnosis. Nothing is wrong with my LG DIY monitor though.
Oh, and I used the format tool this time around and sure enough you fixed it. Thanks again for the DUET.
@SkOrPn
Quick bit of addition to this conversation. I have worked with a few EDID utilities over the years. Here are some that were useful:
https://www.nirsoft.net/utils/dump_edid.html
https://www.nirsoft.net/utils/monitor_info_view.html
(Nirsoft rule)
http://www.entechtaiwan.com/util/moninfo.shtm
http://www.tested.com/tech/pcs/457468-tr…nd-edid-issues/
(MonInfo and Powerstrip have been around a long time and are great software - the directly above link is an article for utilizing them)
https://www.mtbs3d.com/phpBB/viewtopic.p…7&f=122&t=15727 (Completing the above with free software instead of PowerStrip)
https://www.extron.com/product/software…didmanager#supp (here because it is “updated for Win8”)
http://www.edidreader.com/ (for the speed if the others help)
https://www.monitortests.com/forum/Threa…ion-Utility-CRU (for completeness only, involves Intel drivers and might be another approach for someone else)
(Pertaining to a different configuration:)
Check whether there is an EDID EEPROM populated or not. The EDID EEPROM will be in socket U7 close to the HDMI input connector.
If there is no EEPROM in this socket then the camera is likely defaulting to the lowest resolution mandated format.
This EEPROM, even if it is populated, is not programmable from the system board I do not believe, so would need to be programmed either externally or by pulling the EEPROM WP line low then using the HDMI connector’s DDC lines to program the EEPROM.
Maybe you can find something in those. I dealt with an issue or two over the years. If I am barking up the wrong tree feel free to let me know.
@noInk
I am closely following your NVME->MBR progress and wanted to contribute. I did try the software last week and was stuck on the MBR write issue. I diskpart cleaned, ensured MBR and formatted my 8GB flash drive with a 50MB FAT(16) partition. Writing the MBR reported success. It did not reformat FAT32 nor did it boot. The MBR error occurred. I have the logs if they are useful.
A few questions. You mentioned removing the Tianocore screen. I just discovered the many options the (audiocricket version of) that screen offered. Properly configured/enabled it would offer an environment to dynamically load/unload drivers, boot entries and all else with a (semi-)GUI interface. Is it completely without value on USB? Do you know of any system for partitioning and installing UDK2017 and would that activate the features? I investigated purchasing SATA DOMs just to avoid the trouble with USB.
Not using a USB drive would be a huge benefit to this entire project. I read there was some sort of infrequent corruption issue. I find it difficult to understand as the software is not adjusting anything to do with its own disk/partition structure (or is it?). Can that be accomplished?
I am interested to know what your MBR solution was. Have looked at BOOTICE or any other software? If a HEX editor or other application can manually write the MBR from a clean state it might be something the particular application does that triggers some protection.
One more idea. I recommend scripting to remove the USB drive hardware in between step one and two. It should be easy with devcon. I have always just devmgmt’d with the Connections view and then removed the hardware directly above the drive in question. It makes for easily completing the task while connected remotely.
If you do intend to put more real time on this that would be awesome. I will rebuild and fire up a few personal systems and drives to assist in testing if it would help. An H67N-USB3-B3 and PM961 are nearly ready. Keep up the great work.
@SkOrPn
I just find the black screen issue on POST strange 
on the X58 it could even be that the CPU is too tighten, dunno!
Check it with an EDID EDITOR to see if everthing is in there, should be a table from 00toFF (h100) with extended information (not zero filled) there are user friendly GUI out there.
Might be nothing, or relative to the GPU like you say so, it shoulnd’t be anyway the cause itself!
The drill;
(save settings)
remove any switch or KVM from the USB port
remove battery
take out all ram slot except for one
flash back the MB bios (be sure it has support for the CPU in use and not corrupted)
clear CMOS
load default
reseat the GPU
attach the GPU also to something else while booting on that monitor
flash back the GPU bios
change PCIe slot if supported
check on your MB manual for jumper setting
boot without GPU to ear the beep
Hope you solve it, or find a good video board under the tree! 
@silekonn
Space is an issue with DUET.
The current unpacked firmware is 1024KB and I already squeezed space by dropping some debug information.
Adding all the missing part require from 1,5to8MB of space, so, DUET with it’s current design require a major code overhaul to work with more module ( like the device menu ETC, ETC ).
Doing operation with the config on the USB at the moment cause the OS kernel to panic, this also require major code rewrite and that’s why there the “startup.nsh”.
If there is a MBR present on the USB disk already, then the GenBootSector simply patch it, there are no sanity check in place.
If the USB is not booting with the CreateUSB it could either mean you didn’t detached the USB when prompted, or, the MBR could be already corrupt and require user interaction to restore both’s disk sector(1) offset 0-200 and sector(2049) offset 100000-100200. For the latter, you either bare write on the physical disk at the location and manually sanitize the byte or find an utility to do it, diskpart can but like devcon can cause disaster for the user.
If you are reporting issue on the DUET2017 version I will eventually see to add a sanitize before the format, it shoulnd’t happen anyway in the first place because the USB shouldn’t be on corrupted MBR state.
Anyway, if the USB became unreadable after using a third party utility or you need to start from scratch:
BE SURE TO SELECT THE RIGHT VOLUME.
The DiskPart utility will completely erase the partition table on the drive you select.
1) Open the Windows Command Prompt with “Run as Administator” option ( ie. Run “cmd” as Administrator ).
2) Type “diskpart” ( without quotes ). Enter.
3) Type “list vol” seek and triple check your USB disk: compare the size, the type and the letter before proceeding.
4) Type "sel vol “DRIVE_LETTER:” (without quotes) - ie: “K:” is the drive letter of MINE USB flash drive…
Be sure to select the USB Drive or the next command will wipe the DISK. Enter.
5) Type “clean” (without quotes). Enter.
6) Type “convert mbr” (without quotes). Enter.
7) Type “create partition primary offset=1024” (without quotes). Enter.
8) Type “format fs=fat32 quick” (without quotes). Enter.
9) Type “exit” (without quotes). Enter.
2) Type “diskpart” ( without quotes ). Enter.
3) Type “list vol” seek and triple check your USB disk: compare the size, the type and the letter before proceeding.
4) Type "sel vol “DRIVE_LETTER:” (without quotes) - ie: “K:” is the drive letter of MINE USB flash drive…
Be sure to select the USB Drive or the next command will wipe the DISK. Enter.
5) Type “clean” (without quotes). Enter.
6) Type “convert mbr” (without quotes). Enter.
7) Type “create partition primary offset=1024” (without quotes). Enter.
8) Type “format fs=fat32 quick” (without quotes). Enter.
9) Type “exit” (without quotes). Enter.
UPDATE: Added the diskpart as command via script and also disabled it for safety reason. Do not use unless you are sure about selecting the right disk…
It took me two hours to find this old compatibility flyer from Yamakasi. All Yamaksi, Crossover and Shimians using this Bypass PCb had the same issue,. No one on planet Earth ever got their 5870 to work in the BIOS with this display. When we asked the MANY Korean manufacturers they clearly said it was a issue with "very specific" AMD cards as they did not have the firmware programming to understand how to function with these overclocking Bypass boards. Again, it was a common non-fixable issue. You can clearly see my card listed as incompatible in the below image. What they did not tell us was that it works once the OS loads.
http://www.greensumimage.com/ebay/images…ibility_VGA.jpg
@SkOrPn
Yea, I see the flayer, doesn’t make sense 
If the EDID is non-empty the board is doing the communication on digital, so you either check with the EDID or if possible ( dunno duo the bypass board mention ) force the analog pass-through full resolution without the EDID, also you’ll might want to give a try and disable the DDC mode and selecting manually the signal on the monitor ( if any option are exposed ) or if the data within the EDID is not garbage try to use an HDMI to DVI or a pass-through DVI emulator.
Cheer!
I have two options. Both options means giving up on the point of this build, overclocking this panel to 100Hz which works perfectly on my panel.
One, put a Startech Dual-Link active adapter which will take the DP from the video card and convert it to DVI-D DL for the panel. This has worked to show the panel, but it limits the panel to 60Hz.
Two, install this instead. https://www.ebay.com/itm/DisplayPort-LCD…0/272218036587?
The last option allows me to remove the HY-2560M board, put back on the original SDDB TCON, and then I will have a DisplayPort monitor running at 2560x1440 @ 60Hz.
I can also buy the latest NVIDIA GPU’s such as a 1080 GTX and be done with it since they still have DL DVI ports. This will allow me to run it at 2560x1440 @ 120Hz no problem.
Those are my options at present. However, I plan on converting it to DP once I get a UltraWide display later in 2018. That was the plan all along. The Startech option is too expensive and according to Startech engineers that is the only adapter they know of that works on my display type.
@SkOrPn
OK, I get the issue you are facing, it’s goes sort of dead end in mine view.
If it work already and satisfy you, I wouldn’t toss money at anything.
Having just the DVI port on the board is a technical limit per se, hardly bypassed without engineering \ disassembling or fix whatever is wrong with either the GPU or the boards itself, it might somehow working as expected duo the mismatched hertz in use \ range.
UPDATe
The version you primed few day ago, the one with the resolution change has no graphical boot manager.
If you HIT ESC during the boot process the PC will stuck (OPS sorry).
I’ve already updated the package and included back the necessary libraries and also changed how the startup.nsh work.
Now the script will always boot from the first Bootx64.EFI found, be sure there are no other USB key with DUET during the boot.
UPDATE2:
Also added some instruction about how to use the X58 RAID software option ( mainly tested in Window 7 ) for the SATA port in DUET and updated the “startup.nsh” to check if the file exist before loading the module.
Even compressed the packaged firmware lack the physical space to hold it, must be loaded with the “load” shell command.
RAID to AHCI - AHCI to RAID ( Windows 10 ) DO NOT INSTALL any Rapid Storage Manager greater then the 12.9.0.1001.
On mine board ( dreaded by 64KB IO/SPACE limit and abandoned by the manufacturer* ), installing newer RST software make Windows 10 stuck on the loading circle, if your board never reach the desktop too, go to the DELETE RAID driver section.
*OFFTOPIC: ((If someone know how to deal with these dead 128KB system bios from PHOENIX386AWARD, dunno like extracting\replacing the BOOTROM binary within or by knowing in specific the header and the structure…))
To use the SATA RAID software option:
find the suitable RST EFI SATA\RAID driver version 11 or 12 ( GUID: 90C8D394 \ 91B4D9C1 ) and place it inside the “EFI\Raid” directory, then modify the “startup.nsh” accordingly or rename the file in “SataRaid.efi”.
1) Uninstall the RAID or AHCI SATA driver ( intel matrix/rapid storage technology ).
2) Open the Windows Command Prompt with “Run as Administator” option ( ie. Run “cmd” as Administrator ).
3) Type “start devmgmt.msc” ( without quotes ). Enter.
4) In “Storage controller” double check if the Intel(R) ICH10| Desktop/Workstation/Server Express Chipset AHCI or SATA RAID Controller is still there, in case uninstall and also check the “delete drivers” option.
4) Open msconfig > boot tab > check safe boot > restart.
5) Go into the BIOS and set the SATA mode either RAID or AHCI.
6) Boot Windows 10 in safe mode.
7) Open msconfig and under the main menu tab ( general ) click the normal startup circle and restart.
8) Install your AHCI or RAID driver ( intel matrix/rapid storage technology).
DELETE RAID driver:
1) Go into the BIOS and set the SATA mode to AHCI.
2) Boot Windows 10 in safe mode by pressing “F8” or “shift+F8” after the EFI shell script reach the end.
3) Open the Windows Command Prompt with “Run as Administator” option ( ie. Run “cmd” as Administrator ).
4) Type “set devmgr_show_nonpresent_devices=1” ( without quotes ). Enter.
5) Type “start devmgmt.msc” ( without quotes ). Enter.
6) CTRL+V and select “show hidden device”.
7) On “Storage controller” locate the semi transparent Intel(R) Desktop/Workstation/Server Express Chipset | Premium SATA RAID Controller and uninstall by also checking the “delete drivers” option.
8) Open msconfig and under the main menu tab ( general ) click the normal startup circle and restart.
Devmgr_show_nonpresent_devices=1 doesn’t have an effect in Win8+. See:
https://docs.microsoft.com/en-us/windows…-hidden-devices
Writing an MBR can be accomplished with the Clover BootDiskUtility. It is a small tool that writes the current version of the Clover EFI bootloader, a system with a similar purpose. If it is run without installing clover DUET has an easy path. Just one way to skin the cat.
Please add versions to the builds. Thank you.
That is what most of us have been using all along anyway, right? That is the tool I been using since last year to write mine. Once its bootable I can always delete and or add files to it to change from Clover to DUET and back again. But normally DUET formats without problem.
@silekonn
The “Devmgr_show_nonpresent_devices=1” does work on Windows 10.
If I make others update, I will add a note with progressive revision.
@SkOrPn
YEa, I should have fixed that already, right?
–
Answering to mine OFFTOPIC…
-After hitting the desk with mine head for almost a week I handled the PHOENIX386AWARD somehow and made the magic happen with this board.
@noInk
I believe you have it just right for now. Works perfect for one OS installation. I might have to go back to Clover though, just because I want to dual boot again and since Clover gives us a nice clean UI to select the OS it makes it far easier than DUET. I wish DUET had some sort of OS selection scree at bootup, so that you could simply use the arrow keys (left, right, up, down) and the enter key to select the OS to boot into.
Any good ideas on how to make DUET as easy as Clover for DUAL boot configurations? Or will DUET always be CLI based?
EDIT: Wait, I just had a idea. Why not edit Clover (its open source no?) and make it work better just for us X58 users, meaning pull all the Apple specific files out of it and release it for us Windows and Linux guys who have older systems? Wouldn’t that work brilliantly? I mean Clover is based on DUET so its just an extension of DUET anyway, right?
Hmm, I was not aware of it until just now. Is that similar to what I was mentioning? Does it use the latest EFI versions? Is it based on DUET, or Clover or what? Very interesting stuff.
It is based on the concept of an EFI GUI multi-boot. That aside I am not versed in it. I believe you would be using Clover/DUET to load the rEFInd executable (EFI file). http://www.rodsbooks.com/refind/
Yeah, I already read that page thank you.
It is clearly not useful here though. It would not make any sense to boot like this "BIOS>CLOVER>rEFInd>OS", when you can already do "BIOS>CLOVER>OS". Adding extra time consuming steps for no benefit at all makes no sense to me. On the rEFInd page it clearly says it does not boot on BIOS based systems, so like you said that means I would have to boot rEFInd with Clover or DUET anyway. But why would you do that when all you need Clover/DUET to do is to boot your Windows or Linux OS, which it already does that. rEFInd is obviously for newer UEFI systems, and we here are using older BIOS only systems.
DUET = Seems perfect for ONE OS instance!
CLOVER= Seems OK for Multiple OS instances. BUT it is geared towards MAC systems! Which is why it would be ideal if someone edited it for Windows and Linux only.
@silekonn
YOu see broken driver like the one intel is making for the ICH10
or non-present device… installed device not there, or there but not! better to use it carefully some device are shown non-present even if actually are.
@SkOrPn
Yep, it can’t yet save the config on the USB.
DUET like it is now seems more oriented to single OS install.
In theory, you could always use the graphical BOOT MANAGER manually each time by selecting the device (F2 during the tiano logo display) > (boot device or something), but, this defeat the purpose of having a managed boot manager… ( hardcoded config is set to boot from USB ).
Didn’t had the time to look at, mainly duo the check I’ve made to bring mine bios board to use the >64KB OROM
I went back to using clover so I could try to perfect an install of Kubuntu 17.10. I discovered that Youtube videos were not working correctly, so I hesitantly installed Xanmod 4.14.1 and then Padoka PPA using the very latest MESA 17.3 and now the videos work perfectly. Kubuntu should have worked just fine since it is now using MESA 17.2.2, but it wasnt which I bet was the kernel 4.13.
Anyway, I am going to make yet another attempt to get someone at the clover forums to help me remove the extra efi files that are safe to remove for my machine and OS’s. I believe all I need are the xhci.efi and nvme.efi files, but I digress. I wish Intel would have released something like Clover for their old school BIOS only users and for booting Windows.
OH, and I almost forgot today I got a bunch of Capacitors from Digikey and I am going to try and repair my old Dell 2407WFPb finally. Tired of needing to turn on the TV just so I can see Clovers UI screen. I need my BIOS screens back, lol…