cancel
Showing results for 
Search instead for 
Did you mean: 

Patched TRIM in RAID! (Former: RIVE 3301 Patched for TRIM in RAID!)

Nodens
Level 16
Ok what you've all been waiting for 😛 After an insane amount of coffee and tea consumption I'm proud to announce, TRIM under RAID!

HowTo:

1. Download my modded UEFI image: http://bit.ly/VXz2cI (Newer links below, read the enitre post:))
2. Download F6 11.7 driver from Intel here: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3449&DwnldID=22194&keyword="Intel+Rapi...
(EDIT: There are newer driver versions)
3. Flash UEFI image via USB Flashback method (EZ-Flash won't flash it..like any modded UEFI).
4. Force install the 11.7 driver via device manager/have disk (You can use other 11.x versions BUT 11.7 is a must if you use Win8 due to a gazillion Win8 fixes it includes..Also I don't suggest anything bellow 11.6 as it's not made with the specific OROM in mind..)
5. Reboot and rerun the Windows Experience Index assessment (Windows uses this to figure out if the drive is SSD or HDD). (For Win8.1, run "winsat formal" in admin command prompt).
6. Go ahead and Optimize the array 🙂

Special thanks to my testers: jezjohnson and broken pixel!!


Disclaimer: This is my own work and is unrelated to ASUS. Also I am not responsible if this eats your data or makes you grow hair on your forhead..It has been tested enough but you know how these disclaimers go:p

Notes:
a) If you are installing a new operating system on the array the F6 drivers could probably fail, in that case install with a 3.x F6 driver and once installation finishes force install 11.x via device manager as normal.

b) You do not need to rebuild your arrays. It works with existing arrays as they are:)


The is only one image from now on. It includes both the patched OROM and the lastest UEFI Driver (Binary images: 12.0.0.1783 provided by Pacman, 12.5.0.1815/12.6.0.1867/12.7.0.1910&1936 provided by asder00 ). When you use the one, the other is not used at all, so there's no point making 2 versions.


All files moved from dropbox to Necrosan's server. I want to take a moment to thank Necrosan for volunteering to host them and accomodating all my needs!


The thread was getting too big and I was getting banned from dropbox for traffic every now and then heh. So new format, each board has a folder with all the mods for the board inside. Earlier versions are only OROM modded. those that come in 2 versions (plain and +UEFI) have either the patched OROM in the first case or an updated UEFI driver in the later. Versions after those have both.

New mods will be announced here.

Latest Rampage IV: 4310, Sabertooth:4210, P9X79/-Deluxe/-Pro/:4210, P9X79-WS: 3401

Repository:
--------------------------------------------------------------
RIVE: http://www.necrosan.com/rog/UEFI/RIVE/
RIVF: http://www.necrosan.com/rog/UEFI/RIVF/
RIVG: http://www.necrosan.com/rog/UEFI/RIVG/
Sabertooth X79: http://www.necrosan.com/rog/UEFI/Sabertooth_X79/
P9X79: http://www.necrosan.com/rog/UEFI/P9X79/
P9X79-Deluxe: http://www.necrosan.com/rog/UEFI/P9X79_Deluxe/
P9X79-Pro: http://www.necrosan.com/rog/UEFI/P9X79_Pro/
P9X79-WS: http://www.necrosan.com/rog/UEFI/P9X79_WS/
--------------------------------------------------------------
Patched OROMs for self-modding: http://www.necrosan.com/rog/UEFI/patched_orom/
They would work for any X79 board.
--------------------------------------------------------------


FAQ or Things you should read before asking questions

Q: Intel Toolbox is not working properly with this patch:
A: With this patch forget the Toolbox.

Q: How do I know if it working or not?
A: Installing Win8 and doing it's "Optimize" is the only verified method of triggering TRIM on demand. Anvil works for some drives and not for others on Win7. Most of the issues reported are with specific drives under Win7. To verify that the drives actually act upon the command you need to use the hex editor method as posted by Fernando here:
http://www.win-raid.com/t24f34-Easy-TRIM-test-methods.html
This method is the best for checking but it is a bit involved. A simpler approach for ordinary users is Trimcheck by CyberShadow: http://files.thecybershadow.net/trimcheck/
Source:https://github.com/CyberShadow/trimcheck

Q: My XYZ drive gets passed the command but the hex editor test shows TRIM has not been applied.
A: What drive controllers do with the command, depends on the drives.
If it doesn't work with your drives using this patch it would not work on ASRock and Gigabyte implementations as well and it's either a drive issue or Intel OROM/driver issue.

Q: Are there any drives /reported known to not work?
There is currently no drive known as not working.

NOTICE: Do not post ANY external links on this thread unless they point to Intel or a major manufacturer(drivers). I do not have time to personally verify any downloads other than the ones I make myself. Nor can I "police" the links in case they change to malicious targets at some point in the future. I can not support this unless I know exactly what's been flashed. Please respect this rule. I can not end up in a situation where I'm chasing an issue that doesn't exist because the user reporting it downloaded something else that may or may not be right.
If you want to send me new driver or OROM versions, use PM instead.
RAMPAGE Windows 8/7 UEFI Installation Guide - Patched OROM for TRIM in RAID - Patched UEFI GOP Updater Tool - ASUS OEM License Restorer
There are 10 types of people in the world. Those who understand binary and those who don't!

RealBench Developer.
642,755 Views
954 REPLIES 954

FROMTOR
Level 7
Thanks for the work Nodens. Issues 1 & 2 for me. reverting to 4206. I had to re-install win 8, as the RST was (expletive deleted) not working correctly.

perry185
Level 7
For the P9X79-WS the latest modded BIOS is version 3401. Currently, 4306 is available at ASUS. Would it be possible to patch this latest BIOS for the P9X79-WS?

perry185 wrote:
For the P9X79-WS the latest modded BIOS is version 3401. Currently, 4306 is available at ASUS. Would it be possible to patch this latest BIOS for the P9X79-WS?


Grab on *link removed*
I7 3930k (C2) @4.5 1.32V/Rapmage 4 Formula/Corsair H80i + MX-4/4x4gb 1866MHz G.SKILL/SLI GTX 780Ti/ OCZ Vertex 3 MI 120gb(win) /OCZ Vertex 3 120gb(games) /2x seagate 7200.11 @ 560 raid0 (strap 128)/Creative Zx/Corsair AX1200w/Silverstone Raven 2 (rv02b-w)/BENQ EW2730/Windows 8.1 x64

Alex1990 wrote:
Grab on/QUOTE]

That's quick, thanks man!

Since iRST 12.7 isn't available anymore from the Intel download center. Would the latest RST 12.8.0.1016 also work with this BIOS?

bogsha
Level 10
New 12.7.0.1936 images:

>RIVE-4501-12.7.0.1936<

>RIVE-4403-12.7.0.1936<


Hope you like it :cool:

perry185
Level 7
Hope someone can guide me bit with the following.

Currently I'm running the Nodens modded BIOS 3209 on my P9X79WS in combination with the (modded) IRST 11.7.0.1013 driver. TRIM works fine!

Now I would like to update to a newer BIOS version. In the OP the latest available modded BIOS is 3401 for the P9X79WS. Since there is already BIOS 4306 available at ASUS I would like to upgrade to that version. As far as I understand I should be able to patch this BIOS 4306 myself with the Patched 12.7.0.1936 for self-modding which is available in the OP.
Q: can somebody point me to the instructions how to do this?

Another thing: yesterday I tried to update the IRST driver to 12.8.0.1016 (without upgrading the BIOS). It failed because the device was unknown. Then I modified the .inf and added the deviceID (PCI\VEN_8086&DEV_2826). That allowed me to install the 12.8.0.1016 driver. However, TRIM didn't work anymore. So, Í'm back at 11.7.0.1013 with TRIM working again.

Q: does it make sense to update IRST to 12.8.0.1016 without updating the BIOS/OROM? I guess a 12.8.0.1016 driver would be backwards compatible with an older OROM.

perry185 wrote:
Hope someone can guide me bit with the following.


Q: can somebody point me to the instructions how to do this?


If understand go to translator 😄

From our russian forum wrote:
Внимание! Будьте очень внимательны при замене каких либо модулей!
Для работы с биосами AMI UEFI используется утилита MMTOOL версии 4.50.0023.
Что для этого нужно.
1) Утилита MMTool
2) Модули OROM и EFI/FFS
3) Терпение и внимательность.
!!! Важно!!! Нет никакого контроля со стороны MMTool за действиями пользователя и поэтому можно случайно, намеренно, по незнанию заменить любой OROM даже обычным текстовым файлом!
Замена Option ROM (OROM)
1) Запускаем MMTool
2) Нажимаем "Load Image" и выбираем файл биоса у которого будем менять OROM.
3) Переходим во вкладку "Replace" и ставим галочку "Link Present", будет доступна выпадающее меню Vendor ID.Device ID, список OROM которые доступны для замены.
4) Выбираем VID.DID. К примеру мы хотим поменять IRST, значит в списке ищем например 8086.2822, выбираем.
5) Нажимаем на кнопку "Browse" и указывем файл OROM который собираемся установить.
6) Убеждаемся, что всё установили и указали правильно, нажимаем кнопку "Replace"
7) После замены жмем на кнопку "Save Image" и прошиваем полученный биос

!!! Важно!!! Контроль со стороны MMTool за действиями пользователя только один, в типе модуля, нельзя вставить/заменить модуль если он не имеет заголовок FFS.Но можно случайно, намеренно, по незнанию заменить любой EFI/FFS модуль с GUID отличным от имеющего в биосе!
Замена EFI/FFS модулей
1) Запускаем MMTool
2) Нажимаем "Load Image" и выбираем файл биоса у которого будем менять EFI/FFS модуль..
3) Переходим во вкладку "Replace".
4) В списке внизу ищем нужный нам модуль EFI/FFS и становимся на него. Например мы хотим заменить модуль EFI/FFS IRST SataDriver. Находим его и запоминаем его GUID!
5) Нажимем на кнопку "Browse" и указывем файл EFI/FFS который собираемся установить.
6) Убеждаемся, что всё установили и указали правильно, нажимаем кнопку "Replace". Обязательно найдите в списке замененый модуль и сравните GUID с начальным в п.4. Всё должно совпадать! Если не совпало, то откажитесь от дальнейших действий и найдите модуль с тем же GUID, тк работать не будет.
7) После замены жмем на кнопку "Save Image" и прошиваем полученный биос.
I7 3930k (C2) @4.5 1.32V/Rapmage 4 Formula/Corsair H80i + MX-4/4x4gb 1866MHz G.SKILL/SLI GTX 780Ti/ OCZ Vertex 3 MI 120gb(win) /OCZ Vertex 3 120gb(games) /2x seagate 7200.11 @ 560 raid0 (strap 128)/Creative Zx/Corsair AX1200w/Silverstone Raven 2 (rv02b-w)/BENQ EW2730/Windows 8.1 x64

Alex1990 wrote:
If understand go to translator 😄


Thanks, this helps. I think I got a custom BIOS now with the Nodens modded OROM from the OP:
Patched 12.7.0.1936 for self-modding

For my understanding: do I need to find the related iRST floppy drivers for the 12.7.0.1936 version or could I also use the latest available (12.8.0.1016)?
And should I modify the .inf file with adding my device ID (PCI\VEN_8086&DEV_2826)?

matacks
Level 7
Im finding some of the information here confusing. Could someone make a dummies guide on how to do this with each step written verbatim in the simplest way possible?

thanks
3930k - Tuniq tower 120 extreme (with Noctua NF-F12 fan and 2011 socket mounting screws - ASUS P9X79 pro
sandisk extreme II 480gb x2 in RAID - CORSAIR Vengeance LP CML16GX3M4A2133C11B - MSI N780-3GD5 GeForce GTX 780
ASUS BW-14D1XT Blu-ray burner
Seasonic SS-760XP2
CM Storm Scout 2 with 5 noctua NF-F12S pwm

DragonClaVV
Level 9
Use that to verify if Trim is working.

http://www.wintotal.de/softwarearchiv/?id=6731&lnk=16997

My way with Raid 0 SSDs was the one described in the guide in the forum from nodens.