[b][/b]
[i][/i]
[u][/u]
[s][/s]
[code][/code]
[quote][/quote]
[spoiler][/spoiler]
[url][/url]
[img][/img]
[video][/video]
Smileys
smile
smile2
spook
alien
zunge
rose
shy
clown
devil
death
flash
sick
heart
idee
frage
blush
smokin
mad
sad
wink
frown
crazy
grin
hmm
laugh
mund
oh
rolling_eyes
lil
oh2
shocked
cool
[mail][/mail]
[pre][/pre]
Farben
[rot][/rot]
[blau][/blau]
[gruen][/gruen]
[orange][/orange]
[lila][/lila]
[weiss][/weiss]
[schwarz][/schwarz]
davidm71
Posts: 372 | Last online: 08.20.2017
Occupation
Healthcare
Hobbies
Computers
Date registered
11.23.2013
Description
Came up with original one file method to boot NVMe drives on unsupported hardware
Sex
male
    • davidm71 has written a new post "X58 Chipset with problems to boot off a PCIe connected SSD" 08.11.2017

      @Ghaben,

      Maybe you should try updating your USB 3.0 firmware or even disabling it and use a USB 3.0 add in card. I have no trouble on my X58 Duet system starting Duet with USB 3.0 PCI-E enabled card in place. Could be because of the chipset. However I have not tried booting Duet from that USB 3.0 port though not a deal killer in my case.

    • davidm71 has written a new post "Recommended AHCI/RAID and NVMe Drivers" 08.10.2017

      Just wanted to report on some reports of compatibility issues with the ver 1.5 Open Fabrics Nvme driver I came across. These reports I found on the Open Fabrics email list subscription I have however the exact details are above my head being technical. Probably be a ver 1.6 coming out soon..

    • @Praxis,

      I suspect some sort of a irq or resource conflict or timing conflict with the drive. You should run HWInfo and examine the device tree it prints out and look at each branch and what other devices are using the same bus and then disable that device. I would even recommend you try a different pci express slot such as the primary pci-e slot. Also make sure you update all the device drivers including the NVME drive's firmware to the latest. Of course make sure you have a fresh install of Windows to test from and don't install any oem software until you know the system is stable. In any case your sure it goes away when the drives removed?

      Edit: About ME read this.

    • Yes that's one other way to do it. Takes a little trial and error though.

    • davidm71 has written a new post "Recommended AHCI/RAID and NVMe Drivers" 07.23.2017

      Sorry missed your specs prior. Nothing missing.

    • @Praxis,

      Try a different bios release version perhaps. Use Ubu tool to mod the bios modules to different versions as well. Update your ME. Sounds like a compatibility issue.

    • davidm71 has written a new post "Recommended AHCI/RAID and NVMe Drivers" 07.23.2017

      @milks,

      Please detail your full system specs. From my experience Windows 10 installer can be very picky when it comes to installing on to NVME SSD. It took me literally a couple once to complete the install. Fernando will tell you to make your own bootable usb key using Rufus and his suggestion to load the nvme driver is the way to go. I made mine with the Windows 10 media creation tool. The key points though are to set your bios to Ahci mode and turn off raid, use diskpart to wipe your disk blank, disconnect any other foreign disks like linux or osx. I remember in my case the Windows 10 installer had trouble creating the system partition. Took a few tries. Others have tried using a newer machine to do the install, and then transplant the disk back into the older pc for it to run through its device configuration and final setup. I for one have used cloning software though found later the system would fail to update to a newer Windows 10 build. Key points though is to turn off other storage controllers in your bios.

      Good luck!

    • @Plutomaniac,

      Hi,

      I think I figured out how to transfer just the 'DATA' info from a configured ME onto a newer version and include it in my ROM File.

      Steps I took:

      1. You load the matching version factory stock RGN ME file into FIT tool and copy 'ME Region.bin' to a safe place.
      2. You then load your either dumped ROM file or downloaded Bios Rom file into FIT.
      -> set generate intermediate files to NO
      -> blank out paths to any output files with 0 kb
      Then save your config.xml file to disk and exit FIT.
      3. You then copy over your 'ME Region.bin' file overwriting the new 'ME Region' file from the dumped Rom.
      4. Run FIT again and load your config.xml and hit 'Build'.
      5. Open the new outputfile.bin with FIT and you should have a new 'ME Region.bin' file striped of the INIT info but with the OEM DATA transfered over.
      6. Correct the length of the new 'ME Region.bin' file to match the last extracted ME Region using UEFITool and use UefiTool to replace the Me Region with your new file.
      7. Save file.

      Questions I have:

      When I press Build I get a warning that Boot Gaurd will be disabled! Is this important?

      Alright to use downloaded bios rom file instead of direct dump? Obviously have to remove capsule?

      This statement confuses me a little:

      1
      2
       
       So we pick the firmware file 11.0.1.1001_CON_H_XX_PRD_RGN which matches perfectly what we saw at ME Analyzer. If for example the dumped SPI image had ME 11.0.0.1196 with LP SKU, we would have picked ME 11.0.0.1197 instead because the one we wanted is EXTR and not RGN.

       



      Thanks

    • davidm71 has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 07.22.2017

      Zitat von plutomaniac im Beitrag #3185
      Zitat von davidm71 im Beitrag #3184
      Was wondering if any of the gurus here know how to transplant the ME Region from an OEM bios ver 3002 lets say onto the same OEM bios ver 902?

      If they're both from the same motherboard model, then yes. Make sure the region size is the same, otherwise manually append padding.

      Zitat von davidm71 im Beitrag #3184
      Furthermore lets say I want to include a newer ME from the ME repository into my modded bios file for sharing how would I do that? Suppose I would have to use the FIT tool?

      [Guide] Clean dumped or extracted Intel Engine region images of Initialization data



      Thanks was reading that page this morning and responded to that thread with a few questions if anyone can take a look. Thank you.

    • davidm71 has written a new post "Intel Management Engine: Drivers, Firmware & System Tools" 07.22.2017

      Hi,

      Was wondering if any of the gurus here know how to transplant the ME Region from an OEM bios ver 3002 lets say onto the same OEM bios ver 902?

      For example I used UEFITool to save the "ME Region" using "Extract as is" from my 3002 bios and then used "Replace as is" of the "Me Region" of the 902 bios
      transplanting that 3002 ME region. Saved the file with out error.

      Will that work??

      Furthermore lets say I want to include a newer ME from the ME repository into my modded bios file for sharing how would I do that? Suppose I would have to use the FIT tool?

      Thanks.

    • davidm71 has created the topic "Asus Z170-WS Modded ver 902 Verified working". 07.22.2017

    • Thats how to do it!

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

      @SkOrPn ,

      What kind of usb 3.1 card did you buy? Maybe I'll buy one too. Also why would you want to boot through the usb 3.1 interface in the first place? Be faster on a SSD or something wouldn't it?

      Interestingly enough someone advised me last week to use a usb 3.1 type 2 interface to test OSX software changes before putting it on a SSD. Guy works for either Google or Intel I think. He doesn't mess around though as he already has like a 24 core cpu in his possession. Lucky guy..

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

      Just mess around with the Shell-nodisplay and Shell_nodelay files. Honestly I don't remember what the others do. About your Asmedia USB 3.1 booting problem it's not going to work with Clover and Duet both as long as you don't have a suitable efi driver for it. Going to have to google that one. I personally really wanted an efi driver for Intel raid but found nada. So your mileage may vary.

      But my reasoning for avoiding Clover was that I didn't want Mac OS stuff eating resident memory. It's mostly meant for booting OSX. Plenty of people multiboot with Clover so you should have no problems with Windows. Your PC won't explode. There's also the Refind bootloader out there but not sure it can load nvme drivers. Probably it can but it's like a bare metal loader and kind of has support. Used it in the past. Can have menus with that as well. Think Clover was based on Refind.

      Good luck.

Recipient
davidm71
Subject:


text:
{[userbook_noactive]}


Xobor Forum Software von Xobor