Posts: 94 | Last online: 08.14.2017
Date of birth
28. May 1966
Computer Tech
Hiking, Camping, Solar, Computers, Technology
New Mexico, USA
Date registered
    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 08.14.2017

      Zitat von Ghaben im Beitrag #89
      Major problem is that system won't start at all if on-board USB 3.0 chip is enabled.

      I decided to test it on my board for you because I have the exact same Renases u720200, but I usually keep it disabled because my USB 3.1 card is so vastly superior to it, like night and day. Anyway, my 720200 does NOT work when my system is overclocked so I had to go back to default stock settings in order to enable the Rensases chip. Clover boots up and I can use the rear USB 3.0 ports. I see nothing wrong with it other than the really crappy usb 3.0 implementation that is called Renases. When I overclock past a certain point the Renases chip just disappears entirely, but that has always been the case for me.

      This of course means I do not know how DUET would work on my machine. If I were you I would quickly build a Clover (based on DUET, but it's very latest implementation of course) usb disk and boot using that to see if it still does the same thing. Try the simple and easy guide here in these forums. Boot Disk Utility (BDU) is just too simple to not try at this stage, especially considering it downloads the very latest EFI implementation for you.

      [Guide] NVMe-boot without modding your UEFI/BIOS (Clover-EFI bootloader method)

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 08.11.2017

      Zitat von Ghaben im Beitrag #86
      Am I doing something wrong? My startup.nsh looks the following:
      load fs0:\efi\drivers\nvmexpressdxe-64.efi
      load fs0:\EFI\Drivers\XhciDxe-64.efi
      map -r
      Should I perhaps try loading the Xhci driver differently (like to fsX, where X is not 0)?
      Is there a way at all to get my onboard USB 3.0 ports working properly (in Windows) or I should snap in a USB 3.1 extension card, perhaps? (I have no intention for booting from an USB 3.0 port, my next step is to create a boot partition on one of my RAID1 arrays. For now, I'm content with booting from the USB 2.0 stick.)
      1. Enable USB 3.0 ports within your BIOS.
      2. Boot DUET from a USB 2.0 port (its driver is already built into DUET natively) USB 3.0 should NOT cause DUET to freeze, there is no reason for that unless you were using a 3.0 port to boot DUET. Don't do that on legacy BIOS systems.
      3. When Windows loads it will initialize the USB 3.0 chip using its own drivers.
      4. You can install your own drivers such as USB 3.0 directly from the chips manufacturer, and for the NVMe SSD.

      Unless you plan on using USB 3.0 ports for some reason during bootup, there is no reason to load the XhciDxe-64.efi drivers. UNLESS of course you frequently try Live Distros or need something else to occasionally boot from USB 3.0, such as something like Parted Magic, etc. Otherwise remove it from your Startup.nsh file as its not needed. The OS does the initialization for those things.

    • Zitat von Xensage im Beitrag #123
      hello i am using your guide to boot my Samsung Evo 960 form pci-e 4x on my motherboard Z87-G45 with a 4th Gen Intel CPU last BIOS 1.9 update. So i am using a 3.0 USB to boot clover and have a other USB with windows 10 setup on it both boot on UEFI and after Step 6a it hangs at a black screen. anytips?

      Are you sure you created the proper USB installer pendrive using GPT for UEFI, then burned the Windows 10 installer iso? At the Shell prompt did you type " fsX:\efi\boot\bootx64.efi "? (where X is your usb drive)? If the USB does not appear, or work from the clover gui menu, you need to boot the Windows 10 installer from the UEFI Shell. It always works that way for me.

      You just have to figure out which one is your pendrive. fs0 is usually the Clover pendrive, so fs1 or fs2 should be the Windows 10 installer pendrive, and fsX:\efi\boot\bootx64.efi will boot it.

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 07.17.2017

      Booting and testing live linux sessions is almost exclusively done on USB, at least that is what most people do. You know what a Live Linux Session is right? I got the GC-USB 3.1 (from Gigabyte) mainly because it has the chipset I wanted and wasn't too expensive. I think this asmedia chipset is the one we see on so many newer Motherboards these days. They have had tons of firmware and driver updates so that is a bonus. Plus I wanted one Type-A and one Type-C port. My on board USB 3.0 ports never really worked properly (and never booted anything), and after about 182 BCLK it just dies. Since I like to always be overclocked I needed a good USB card that could handle an overclocked system and my crappy on board usb 3.0 just couldn't do it.

      Anyway, my local storage is now from NAS and USB 3.0 exclusively, so I don't use SATA devices any more. I just boot Windows from my SM961, and Linux Live Sessions from USB 3.0 serviced from that USB 3.1 card. Simple normal setup really.

      24 cores, sweet jesus.... lol, I cant wait to get me some more Cores, but I think 8-16 would be enough for me for a very long time. I'm more interested in higher IPC and new components and technology etc, so I think something like Ryzen 7 would be plenty. Its been a long time since I had me an AMD rig but it could happen before the end of next year.

      EDIT by Fernando: Unneeded fully quoted post removed and replaced by direct addressing (to save space)

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 07.16.2017

      Good news is my USB 3.1 card DOES boot Linux live distros just fine. Just tested it with both Clover and DUET and it works. For some reason when I installed Windows 10 last week DUET would NOT run the Windows 10 installer, which led me to believe DUET does not work with my 3.1 card. It just sat there kinda in frozen state even though I had the Windows USB perfectly formatted. I had to use the USB 2.0 ports to install Windows last week. I guess I need to now test Clover to see if it can boot my "USB GPT UEFI Windows 10 installer" or not. Maybe neither will, or both will this week, lol.

      I guess what I want out of this is to "select" from an automatically generated list of bootable devices i.e NVMe SSD, USB 3.0, USB 2.0 etc". Clover UI shows you a list of bootable devices but is clearly not edited to work how I want as like said before is tailored for OSX, which can be remedied through research and editing of configuration files. Which means I just need to do more research on how to set it up. But now at least I know "xhcidxe-64.efi" works for Linux distros just fine. I don't know why but I swear Clover loaded the Fedora live faster than Duet, but I don't see how that is possible if using the same efi module.

      Thanks again, I will continue to work on this until its just right for my usage pattern. This is actually quite fun really. So rare for someone to be trying to convert an older system to use UEFI. My father has been a computer tech since well before we ever heard the word computer, and even he thought I was nuts trying to do this. He was in shock when I invited him over to witness me booting on NVMe. HAHAHA

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 07.16.2017

      Thanks David for the suggestions.

      I think I will list my needs so that it is clear what I am hoping for.

      1. Must be able to boot Windows 10 (both duet and clover = check) or a modern Linux distro.
      2. Must be able to boot Live Linux distros from USB 3.0 flash drives (DUET = NOT WORKING. Have not tested Clover yet)
      3. Don't need invisible menus, just a fast theme-able one that works. (UEFI 2.6+?)

      Like any piece of software, as newer versions release so do such features as USB 3.0 booting. Right now DUET refuses to boot from my USB 3.0 setup (USB 3.1 card + USB 3.0 flash drives), which is a major desire of mine. I went through 5 USB cards before settling on this super fast USB 3.1 x4 card. I test new Linux builds almost daily and USB 2.0 just sucks to say the least. My USB card is the latest 2017 USB 3.1 PCIe x4 card and uses the latest asmedia chipset, so I am sure DUET will never have the ability to boot from that without having newer versions of UEFI. However, newer Clover versions certainly will as standards become even more standardized. Unless we can compile newer versions of UEFI into DUET I do not see DUET ever booting from my USB 3.1 card, which is the ONLY USB 3.0+ that I have (in my PC at the moment) and the second major reason I am doing this conversion to UEFI. I love my x58 Xeon machine and just not ready to say goodbye to it yet.

      Quick question, if Clover boots Windows just as fast as DUET, then why would DUET be considered better for my x58 system? I mean the Clover team is working on OS booting in general, not exclusively OSX, right? Can Clover possibly cause my computer to explode, maybe? (As lightning strikes my property lmao)

      BRB, really bad storm over head and I need to shut down the PC asap. LOL

      Back, lightning was hitting my property as I was typing the above so I had to go for a bit. Seems to have let up though.

      So anyway, I have "shellx64_v1.efi" and "shellx64_v2.efi" inside the "tools" folder. I also see you have "shell0" and "shell01". Does the later mean a 1 second menu timeout? Do I just rename your shell mods into one of the ones I have and drop it in overwriting shellx64_v1.efi or v2? I would like a working UEFI menu that holds settings, and actually allows me to select different boot devices such as the old BIOS did. Is that possible with DUET? Thanks

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 07.16.2017

      I just found this post which solved my Clover issue. Since Clover is easily edited for timeout, it now beats DUET in booting my Windows 10 from power on to desktop in 19 seconds. Apparently it was DUET taking longer to boot Windows because now test after test its taking about 31 seconds for DUET to get me to desktop. Even if I managed to use 0 timeout on DUET, it would still lose to Clover's speed. Tomorrow I need to test further if it is the usb drives themselves that are giving me the greatest differences, or the efi programs. Not that any of this is of true concern, a few seconds here or there, blah, its just that I have plenty of USB drives and I might as well use the one that provides the fastest stable Clover or DUET EFI boot, especially if we are talking nearly ten seconds difference with just the right setup.

      Now I can research how to theme Clover and possibly get myself an Asus ROG theme going on when I need to boot Linux live sessions ;)

      EDIT by Fernando: Unneeded and already previously quoted post removed (to save space)

    • Zitat von agentx007 im Beitrag #72
      @Fernando I figured out settings for autobooting Windows from NVMe on HDD based Clover.
      They work for my LGA 775 platform (and should be universal for all non-Mac type PC's, I used Windows 7 x64 SP1 OS :
      In config.plist file (EFI\Clover\Config.plist), I set :


      If this is setup correctly, there should be a countdown timer under "Boot Microsoft EFI from EFI" text.

      Could you add this new info to "3b optional" section of the Guide ?

      Thank you for this useful post.

      THIS was one of the most important replies in the thread for me. I had to do this on my Clover setup in order to get Windows auto-booting on the Sandisk Extreme 16GB I am using. I think this particular USB drive was setup by Sandisk as a removable USB HDD, and not a normal bootable USB drive. Mainly because many boot programs, such as Windows USB Tool refuse to use it as a normal flash drive, so I think its one of those Windows ReadyBoost drives Sandisk was selling years ago that got Sandisk in trouble with many people. I myself tried to get RMA repair work done to it so it could be used as a removable usb boot device, but Sandisk was having none of it because they said there was nothing wrong with it as long as it was readable as storage. So it seems like the perfect drive to sacrifice for Clover, since I can't really use it as originally intended (Windows install media), although Rufus does in fact format it when forced to show hdd devices. Since Clover does in fact format usb HDD's this means I can finally put it to some good use. Yay

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 07.16.2017

      Zitat von davidm71 im Beitrag #77
      Wanted to let you know I actually got rid of that timeout with "Startup.nsh'" and suppressed its video output so nothing or no text is displayed on the screen on my X58 system. I did this by messing with Duet's source code and compiling it myself. Happy to share the files if you want. If I could only replace the 'Tianocore' logo with EVGA I'd be happy.
      Edit: Here are the files. Basically I messed with the code for the shell.efi file. Either choose the one for '0 second' delay or No Display.
      Wow, thank you. Yeah the display doesn't bother me none. However, 0 seconds timeout is great. Can you still use Esc to enter UEFI shell if needed for something else perhaps, just have to do it quicker?

      I wanted to try out Clover because it is themeable, and like you I wanted something more in-line with my Asus ROG boards theme, something maybe that looks like the Asus UEFI menus of today lol. But like I said I have no clue how to set Clover to autoboot and I need to do that before I can leave DUET. And I believe the startup.nsh only works on clover when you actually select UEFI Shell from the main UI menu of Clover. Maybe I should actually try using a startup.nsh before I deem it non functional. So until I get Clover autobooting Windows I have to say DUET is better for our older systems.

      I will give your DUET a try and see if I can break under 20 seconds boot time. That would be crazy awesome on x58 to say the least. Thanks again...

      EDIT by Fernando: Unneeded part of the fully quoted post removed (to save space)

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 07.16.2017


      Thought you would like to know that I finally bit the bullet and got the SM961 256GB. I then used your method and the clover method here and both work really good. The DUET method though is much faster for some reason and shaved 8 seconds off my bootup to desktop. The Clover method doesn't auto boot Windows 10 though, it just boots up to the Clover UI. I then have to manually select Windows 10 EFI Boot in order to actually boot Windows. Not sure why that is because I followed the directions to the letter.

      But DUET boots to desktop in 22 seconds flat from system power-on, when my legacy BIOS using Samsung 840 Pro AHCI took 30 seconds. I gave clover a super fast Sandisk Extreme USB too, and gave DUET the slowest 8GB USB 2.0 I had, a $1 special drive LOL. DUET is amazing as it is on my x58. I only wish we could figure out how to get rid of the "startup.nsh" timeout ( set to 0 or 1 ) because that would boot my system like a brand new 2017 system practically.

      Thank you again!

    • Zitat von Mrus im Beitrag #35
      Hi @mireque

      Finally managed to start working. All you have to do is to create startup.nsh file under shell.
      Just go:
      Shell> fs0:
      edit startup.nsh

      Then insert all commands, save and exit.

      After restart it worked.

      I had the identical same problem as you, but in Windows all I did was set view of extensions to on, so that I could see the file was incorrectly named as "startup.nsh.txt" which is the way Windows natively would always name it. The problem went away when I changed it to "startup.nsh" removing the .txt file extension from the end of it.

      Thought I would mention this for anyone else who has this problem.

    • SkOrPn has written a new post "CPU Microcode BIOS modding questions/problems" 07.11.2017

      Zitat von drizzler im Beitrag #133

      Is there a link you can share that will shed more light on what exactly needed to be fixed on the Westmere microcode please? Curious to find out if anyone is having any Overclocking issues using this newer Intel Xeon Microcode. Thanks

      Also, has anyone tried using this microcode within their Rampage III Extreme board using a Xeon X5650, or any other Westmere-EP for that matter? Curious what your results were. Thanks again.

    • SkOrPn has written a new post "Recommended AHCI/RAID and NVMe Drivers" 07.09.2017

      Anyone know what Device ID this is please? I got it from device manager off of my new OEM SM961 256GB NVMe SSD. I tried to install the latest drivers but Windows says the best driver is already installed, the 2006 Microsoft driver. Can't we install new NVMe drivers on the SM961? Or do I need to re-install Windows 10 using UEFI mode maybe, and then try the new drivers?

      Firmware is CXZ73H0Q

      Device Hardware ID's: SCSI\DiskNVMe____SAMSUNG_MZVPW2563H0Q

      EDIT: Never mind, I somehow messed up and thought I had to install the drivers on the Disk drive, and until now it didnt dawn on me that I needed to install the pure drivers for the NVMe Storage Controller. I feel like Homer Simpson... DOH! lol

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 01.06.2017

      Zitat von mireque im Beitrag #72
      I've got some good news to share - I've finally managed to compile the latest stable TianoCore EDK2 sources (the UDK2015 release, UEFI v2.5) with UEFI drivers (NVMe + XHCI) compiled directly into DUET (no need to load drivers now). If this proves stable over time (I'm currently running / testing it now), I'll most probably release it - then the whole tutorial / process will be much easier to do. Will let you know for sure.

      Yeah wow that is very good news. Congrats on your success. I can't wait to try this... Wish I could afford the SSD today, but I can't yet.

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 01.05.2017


      Do you happen to know if DUET can see other USB chips on the PCIe bus, such as my Gigabyte GC-USB3.1 x4 card? I am wondering if I can build the DUET device on a USB 2.0 flash drive, insert that flash drive into a USB 2.0 port (so the BIOS see's it), boot to the DUET but then have the "startup.nsh" point to the Windows 10 setup files on my SanDisk Extreme connected to that super fast USB 3.1 card? Like I said, I will have to play around for sure, lol.

      I assume I would have to somehow find a command to ask DUET if it see's the SanDisk flash drive on the USB 3.1 card, and if it does figure out what drive number assignment it has been given so I can use that information in the automated "startup.nsh".

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 01.04.2017

      I think I will give this duet a try just to see how it works and possibly make some adjustments for my particular system. Maybe I can use duet to load xhci drivers, and just maybe have it point to my usb 3.1 add-in card. With any luck maybe I can also install Windows from a USB 3.0 device.

      Thanks again for your time and effort getting something working for people who want to use nvme on older systems.

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 01.04.2017


      Utterly brilliant to say the least. The only thing that could possibly beat this is actual BIOS modifications. But I have no problem at all with an implementation such as this.

      One last question, is the XHCI drivers for accessing your USB 3.0 drive? My Rampage III Extreme does not boot USB 3.0 devices (unless I use the USB 2.0 port of course), so I would be forced to use USB 2.0. I have some old but very fast HyperX and OCZ USB 2.0 drives I retired years ago. These are top of the line USB 2.0 flash drives and just as fast as any USB 3.0 drive on a USB 2.0 port. Again, I do not have any working USB 3.0 ports on my board that are seen in my BIOS, so I wouldn't be able to use DUET on a USB 3.0 port. I tried to solve this problem for the past few years but it seems Asus did NOT make my USB 3.0 ports bootable, for some very odd reason.

      So I have to use USB 2.0 ports to boot DUET from. I naturally assume this is perfectly OK? And the reason why I ask is because I thought XHCI was a USB 3.0 driver? If that's the case, would I even need that driver since my BIOS can't see those ports anyway??

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 01.03.2017


      I wasn't confused, I already read everything and it is all VERY clear to me, so thank you for that. My questions were outside of what you covered in your guide. Is the USB DUET device visible from Windows after windows has already loaded? I mean can you see it with your eyes in your file manager and thus possibly manipulate or accidentally destroy your DUET? This was not answered in your guide as far as I can tell.

      Also, you answered my other question about using Samsung drivers for the full effect of the SSD performance, so thank you for that. That also wasn't in your guide because its just not necessary information and I understand that. Your guide is perfect as it is, thank you.

      One more question though, are these files for download in your guide publicly available and kept up to date at all times? Or should we make backups of them at cloud storage places like MEGA or Dropbox? I guess I am asking if the links/files are safe and will always be available? Is DUET an ongoing open project (I haven't done any searches for it yet)? And did DUET create this method to boot NVMe SSD's, or did you put it together yourself? The reason I ask these questions is because I am the maintainer of the Samsung 960 thread at Overclock.net and I need important information so I don't accidentally tell lies to the public, haha. Hope that makes the reason for all these questions more clear and understandable. Thank you very much mireque.

    • SkOrPn has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 01.02.2017

      Zitat von Falco75 im Beitrag #61

      that limitation cannot be avoided.

      Another (functional) boot device is always needed (hard disk or usb device), using a standalone NVMe or PCIe SSD with no other disks will not be possible.

      I can't imagine who would care about the extra layer. BIOS's routinely add layers upon layers before it actually boots a device anyway. If the extra layer bothers anyone all they have to do is disable a few of them within their BIOS. I plan on getting TWO M.2 SSDs and completely turning off my SATA ports and USB 3.0 ports entirely. I now use a USB 3.1 card, for USB 3.0 devices anyway and a VERY nice USB 3.0 hub. So the back ports are useless to me. That's one layer now gone that frees up PCIe lanes. SATA ports will also be disabled to free up resources and time within the BIOS. I have 5 PCIe ports that all comply with at least the x4 requirement of M.2 SSD's that I can use, one for the GPU, one for the USB 3.1 card and TWO for the SSD's. Having a dedicated USB 2.0 device (I have the perfect super fast USB 2.0 drive already present for this type of thing) for this procedure is perfectly OK with me if it allows me to take advantage of my PCIe's underlying speeds over the SATA bottleneck.

      My only thought is if its possible to use this DUET dual booting method using a MBR partition format it using EXT4 instead, or something Windows 10 can not see? Or is that already the case with the DUET partition, is it a hidden partition? Once Windows boots it would be really nice if the device that is loading Windows isn't visible to the Windows system, except for maybe inside the Disk Manager of course.

      Another thought I have is, does this method allow Windows to load and use the Samsung drivers for the SSD?



Xobor Forum Software von Xobor