Zitat von silekonn im Beitrag #134

---

@SkOrPn Why not use rEFInd ?

---

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/

Zitat von silekonn im Beitrag #136

---

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/

---

@silekonn

YOu see broken driver like the one intel is making for the ICH10 :D
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...

Zitat von noInk im Beitrag #138

---

@silekonn

YOu see broken driver like the one intel is making for the ICH10 :D
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.

---

Zitat von silekonn im Beitrag #140

---

If you would augment Clover or DUET with a GUI bootloader wouldn't that be an improvement?

---

@SkOrPn

Intel x58 board, like the DX58SO is running UEFI (2.0) as reference.
SORT of OFFTOPIC..
A good board with a good interface, but sold like anything by intel with an expiration date since no documentation to the OWNER ( final user ) is available to easy disable the enforcement via EFI driver, jumper or whatever.. so, forget about updating it's module without any risk or without a good hardware programming experience.
In general, even today intel board ( from Xbox360 onward ) are subject, in mine view, to catastrophic hardware failure due the efuse embedded like candy and thing like that should only be triggable via a dedicated SPI pathway on costumers hardware.
Just think for a second of one chernobily/sasser variant exploiting the current intel management engine, that's would be a sort nightmare for Intel..

--
Hope you fix the Monitor, I'm still dealing with mine bios, but it's limitation are plain stupid.
As for now I'm loading the ROM outside the OS reach and windows doesn't even know it's there.
That's along the non-working updated RST software for the ICH10 is totally scrapping the optane drive as cache for the RAID ( managed in the OS ) I was aiming in this revived board.

@silekonn

Nah, I'm doing just for backup purpose and while @ it I shared the link to the archive. As it is DUET dependency are pretty much already updated to the current 2017 branch of EDKII.
Also, rEFInd should be implementable by the user on DUET. All you need to do is to download the USB image, unpack it's file and place them on the DUET USB.
DUET will bootstrap to it. From there you'll have the rEFInd GUI environment to do as you please.
Anyway, rEFInd is too much optimized for the macintosh to be included as default boot manager.

--

This version of DUET doesn't require any additional driver to be manually loaded trough the EFI shell, so, if you need to boot a single local system or plan to use the OS boot manager you could always move the "Bootx64" and the "startup.nsh" to another directory or delete them: one its the shell the other a script to exit from it.
in this way DUET will boot stright to the OS boot manager.

I don't understand what you were trying to tell me. I know the DX58SO because I sold one to a friend back in 2015, but I have Asus Rampage III Extreme, so no UEFI (I think). I have to use DUET or Clover as far as I know to get UEFI bootable devices to work, such as NVMe. Or were you trying to tell me that the DX58SO can see and boot NVMe devices because it has UEFI?

Zitat von SkOrPn im Beitrag #139

---

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

---

OK, I see you were replying to my Intel wish lol. Yeah I knew the DX58SO appeared to be UEFI, at least its bios seemed similar to the stock UEFI I have seen around. And I know Intel had no plans to bring support for NVMe to older systems. I just wish they would have released a bootable UEFI setup, similar to duet but with a UI, and intended for legacy BIOS systems only. But Intel figures that would be shooting themselves in the foot. And I do not believe that at all, I believe it would have helped us with already powerful legacy systems to adopt at least NVMe devices. So long the user is OK with a slightly longer boot time.

Oh well Clover and DUET works just fine for me.

@SkOrPn & @silekonn

CLOVER seems to use DUET > REFIT > OS

anyway, since a graphical boot manager is what you guy's are asking.

Here the DUET version from UDK2017 with REFIND included ( also built with it ).
Seems to work but I didn't really tested :D
The MAC functionality are too much nested into the code.
Unless you use the secure boot ( we don't have it) there seems to be (sort of) no strange things going on with the code.
Configuration is minimal.
Preconfigured and disabled what I could and also made a mini theme. Hope you like it! LOL
To add/remove more things you should read the config and/or ask it's dev.

Also, I didn't included the driver for specific partition type, so, if you really need them they are included within the REFIND binary release

Additional steep for the OPTIONAL BOOT MANAGER:

@noInk

Wow, wow, wow, this is exactly what I was looking for, for years now. I wish I had this kind of knowledge that you possess.

One question please, can I still use my USB 3.1 PCIe card during the DUET boot in order to boot from my USB 3.0 flash drives (for Linux live distro testing and parted magic use)? All I have to do is just put my "XhciDxe-64.efi" drivers in the same folder as before? i.e X:\EFI\drivers\XhciDxe-64.efi. Then that way all I have to do is go into the Shell and use the command "load fs0:\EFI\drivers\XhciDxe-64.efi" and then "map -r" in order to see my bootable USB 3.0 drives, right?

OR, can I simply put the "load fs0:\EFI\drivers\XhciDxe-64.efi" command into the "startup.nsh" file to make it easier on me? Any tips on this question? Thank you VERY much for this wonderful DUET implementation.

THIS BUILD OF DUET DESERVES ITS OWN THREAD!!!!!! LOL

@Fernando

This DUET on post #147 is FAR FAR better then Clover for legacy systems, especially if your using x58 to boot from NVMe M.2 devices. This version of DUET is EXACTLY what we have needed for many years now. Think of it as our very own Clover implementation but for Legacy BIOS systems, instead of for MAC. Sure Clover works but it has far too much unnecessary code for what we do here.

So, please consider making a dedicated THREAD using this fantastic "Legacy NVMe Booting with noInk's DUET" on post #146. This feels like a Christmas gift for my computer...