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)

@SkOrPn

I just find the black screen issue on POST strange :D
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! :P

@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.

Zitat von noInk im Beitrag #124

---

@SkOrPn

I just find the black screen issue on POST strange :D

---

Zitat von SkOrPn im Beitrag #126

---

@SkOrPn

http://www.greensumimage.com/ebay/images...ibility_VGA.jpg

---

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.

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.

Zitat von silekonn im Beitrag #130

---

Writing an MBR can be accomplished with the Clover BootDiskUtility.

---

@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? :D


--
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?

Zitat von noInk im Beitrag #132

---

@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.

---