Posts: 218 | Last online: 02.25.2017
Date registered
not specified
    • Zitat von David359 im Beitrag #1582
      Not certain how it impacts performance, but the ADATA device I purchased has an on-board NVMe controller so the X58 (legacy, not UFEI) bios can see it and boot from it with no BIOS mods. Perhaps the controller provides some other performance enhancements. I am purely speculating there, I have no facts. The motherboard is GA-EX58-EXTREME rev 1.0. I was pleasantly surprised that the ADATA device was bootable on the X58 board. I have several of these and this makes it seem pretty usable still. I have ordered more of the ADATA devices from newegg.com. There sale has been extended for several more days.

      You know I had that plextor drive in my Z87 board and was surprised it boooted without mods aswell but I guess the X58 is less tolerant anyhow it benched like 1300 mb/s read and 350 mb/sec write on Z87 so overall despite the cool red led illuminating lights im not thrilled with its performance. Anyhow can you post that newegg link? Interested in getting one..


    • Zitat von David359 im Beitrag #1580
      ADATA XPG SX8000 M.2 2280 256GB PCI-Express 3.0 x4 MLC Internal Solid State Drive (SSD) ASX8000NP-256GM-C
      Gigabyte X58 Motherboard, 2.6 GHz CPU
      Note: Motherboard is PCIe-2 so it slows down the PCIe-3 NVMe device

      AS SSD As requested:

      Those are some impressive numbers for x58. I wonder why I cant get half of your score on my x58!

    • Zitat von David359 im Beitrag #1578
      ADATA XPG SX8000 M.2 2280 256GB PCI-Express 3.0 x4 MLC Internal Solid State Drive (SSD) ASX8000NP-256GM-C
      Gigabyte X58 Motherboard, 2.6 GHz CPU
      Note: Motherboard is PCIe-2 so it slows down the PCIe-3 NVMe device

      That is impressive benchmark figures. When I tried I couldn't get over 770mb/sec on AS SSD Benchmark.
      Would you mind retesting with AS SSD bench as it tests more uncompressed data processing speeds.

      Way to go!

    • Zitat von David359 im Beitrag #1569
      All, After getting my Samsung 950 booting fine from the outstanding advice way back in this forum I, for some reason was drawn to order an Adata XPG SX800 (NVMe) from newegg.com on a one day flash sale ($109 for the 256GB). I mounted it on an adapter and on a whim I installed it in an older machine with a Gigabyte X58 chip set motherboard. To my surprise the BIOS recognizes the device. The device seems to have an on-board NVMe controller that signs on and provides status as part of the BIOS boot up, like an add on SCSI controller would do. It looks like it scans for other devices and can control up to 8 total. I restored a backup to the device and I was able to boot from it without any BIOS mods.
      The performance is way above AHCI, but a little below the Samsung devices. It is way less expensive than the Samsung devices. There is a sale on the 512GB version for $207.99 for the next two days at newegg.com.
      You lucked out! I just tried to get a Plextor M8Pey Nvme drive to boot on my old X58 Classified board and even though it was recognized by bios boot menu and probably has legacy option rom, it just refused to boot from either itself or any other drive such that it was impossible to use it as a slave drive. That unless I used a Tianocore Duet bootloader via Usb loading the Nvmexpress driver. Going to install the usb key off of a motherboard header. Anyhow did some benchmarks and got like max 770mb/s seq reads where as my 4-way ssd raid maxed out at like 660mb/s. Fwiw I also read that disabling C-states helps improve SSD benchmark scores so today will try to disable those C-states and see how much better scores I get. I mean do we really need C-States??


    • davidm71 has written a new post "Seeking Knowledge (Dell/NVMe)" 02.23.2017


      In my case the 9343 refers to the model number of the Dell XPS 13 ultrabook. I did some research in the differences between that model and the 9350. That is that the 9343 has a Sata M.2 type B-M Next Generation Form Factor (NGFF) interface. Such that its limited to like 600 mb/s seq reads I believe and NVME type drives will not work despite rumors stating otherwise. However the 9350 can go NVME but limited to a PCI-E x 2 bus transfer speed and its not recommended I read due to the power consumption of these drives eat up the battery life fast. Because I'm running out of hard drive space on my SM-851 256 gb my best option is just get the SM-851 512gb drive which is on Amazon for $200. Not sure if I would do that just yet. The fan noise on this particular notebook is atrocious and killing me!

    • davidm71 has written a new post "Intel EFI "RaidDriver" and "GopDriver" BIOS Modules" 02.22.2017

      Hi guys,

      Was wondering if there is an old fashioned EFI Shell Intel Raid driver out there? Trying to get my raid array recognized inside an EFI Shell running out of Tianocore's Duet Coreboot. What I would like to do is if its possible is to disable the old fashioned raid controller and within the Tianocore Shell load the UEFI raidDriver and then continue to load windows from there. Anyone know if this can be modded to work?


    • davidm71 has written a new post "Seeking Knowledge (Dell/NVMe)" 02.20.2017


      Was wondering if you guys have found more information on the 9343 2015 Dell XPS 13 supporting NVME drives. I found a lot of conflicting information on the internet. Some reports of success and some reports of the laptop not being able to see the nvme drive and or needing a bios update to do so but not confirmed. Fwiw there must be a diagnostic utility that can tell if the firmware supports nvme?


      Edit: Found this guide but I'm willing to bet its not correct: http://www.laptopmag.com/articles/upgrade-dell-xps-13-ssd

    • Well you do make sense. I tested this tool out on a half dozen bios files but there was one from Asus that was strange enough to make it say 'Image imploded' so I guess there will be the rare compatibility glitches and who needs the headache and worry that someone's board got bricked. Thanks for the encouragement though. Thank you.

    • I was and am very much aware of the gpl license and read it over twice. I did this out of fun and hobby and to learn coding. I meant no disrespect to the original authors or to take credit for their work or anything. The license was very clear that it was allowed as long as a documentation was included referencing the original author. In anycase thats interesting what Coderush has said about command line tools making it worse. All I did was open the app up to take other files besides the usual Oz files. I mean I've used this app myself when I was hackintoshing and worked for me. Granted i got a dual bios switch so if anything went wrong i could reflash by turning a switch. I did notice however there were portions of code marked '//Todo later' so i'm guessing its not a complete product. So I agree with you guys that a step by step approach is better. So with my sincere apologies please forget about it. Was just having fun.

    • So Fernando I reached out on the Clover forums about optimizing the nvmexpress driver and so far no one replied or wrote back.
      In anycase I have modified one of Coderush's (I think his) utilities based on the same UefiTool subroutines called Ozmtool and
      it will take your Nvme modules (the three vs the one) and insert it into a bios and automatically expand the main firmware volume
      so no need to delete Satadriver or recompress any other ffs files to make them fit. I have tested it and found that it has no problem
      making room for the nvme modules without needing to use Uefitool. Runs on the command line. So if beta testers brave enough
      to test it out please PM me.

    • Your right. Your Uefitool does the job nicely and should be the recommended app to use. I've repurposed the ozm tool to do the same on a command line for simplicity. Fernando asked if I'd write a guide using your uefitool for the uninitiated so going to help out and do my part. Thanks.

    • I see your point. Makes me wonder why some firmware modules have quite a few modelules already compressed such as coredxe for certain rom files I've come across. Since you can regrow the main volume wouldn't there be performance benefits uncompromising whatever ffs file that was compressed and re insert then uncompressed considering you can expand the volume?


    • Sure I'll write one

    • @Fernando,

      Been studying firmware volume structure using Coderush's UEFITool and it seems like from what I have learned is that unlike MMTool UEFITool will actually regrow the size of the main firmware volume containing all those necessary ffs files allowing more space to add more files without having to delete or compress out necessary system networking files or satadriver or any audio driver. So I strongly urge the modding community to learn how to use UEFITool and use it instead of MMTool to add your nvme files or what not. If I am wrong please someone correct me. Thank you.

    • Thanks @Coderush,

      I've been studying that code and trying to get a better understanding. For example there are like 200 some firmware ffs files within the main volume. I have made note that their parent volume has for example eb5000 bytes which is like 15421440 decimal bytes and looped through each one and summed up all their bytes to equal 15415558 bytes which is like 5882 bytes free which leaves no room to add a 20k module you would think but what your telling me is your code grows the size of the parent volume to make room for the inclusion of the added files? Therefor why does MmTool not allow adding extra modules that UEFItool or commandline utilities based on your code allow?

      So basically I'm trying to modify the utility to estimate how much compressing of non essential files based on free space on the volume. Finding that its not black and while or cut in stone. In matter of fact in one case after adding three ffs files I ended up with more free space than I had before! So fwiw I have QT framework setup and having fun experimenting making modifications here or there. Noticed though you left the 'Size' property on Treemodel not finished though and I successfully was able to finish that part up such that you can tell how big each module is by accessing its size property. New to C++ but getting the hang of it. Thanks for everything.

      EDIT: So after studying the firmware volume structure you are correct. Your UEFITool regrows the third ffs v2 firmware volume nested within the second firmware volume which has a total space of like 12 mb and the compressed firmware volume has lke no more than 6 mb leaving like another 6mb of free space! So why the hell are we deleting networking modules, and satadriver files to make room for our modded firmware files?!!!

      Doesn't make sense!

    • Zitat von Fernando im Beitrag #1476
      This is somehow irritating.
      Which one of the modules, which I am offering within the start post of this thread, did you check and got the 'Unknown section type' message?
      It was the one your posted on post #1225: [Guide] How to get full NVMe support for Intel Chipset systems from 6-Series up (82)
      Perhaps it was one used as an example.

      [[File:old NVMe module with unknown section.png|none|auto]]

      EDIT by Fernando: Unneeded parts of the fully quoted post removed and inserted picture resized (to save space)

    • @Coderush,

      Im experimenting with Ozmtool to add nvme modules (instead of oz modules) into my bios and i noticed that despite having on 5kb free it can squeeze about 50 kb of nvme file modules into the second volume and still have 2kb free at the end. How can it do this when MMTool refuses to do so? Does it automatically compress those files upon insertion? Think Uefitool acts in the same manner. How is this possible?

      Thank you

    • Well at least all of the modules on your main primary first page check out. This must have been one you posted ten pages back in an incomplete state also missing its identifying name inits header. So if anyone comes accross it it should be ignored although may still work. thanks.

    • @Fernando, @CodeRush

      The new NVMExpress driver you had posted has an 'Unknown section type' error. I found this utilizing bios injection command line ozmtool and also UEFITool. Is this an issue or just cosmetic?


      EDIT by Fernando: Attachment removed (to avoid further irritations), because its origin and source has been clarified (see next posts)



Xobor Forum Software von Xobor