Thanks!
 

If I were you, I'd try secure erasing both SSDs with Parted Magic:
 
http://www.corsair.com/applicationnote/secure-erase
 
Before you attempt that, make sure to break the RAID in the Intel ROM config tool by hitting CTRL+I on boot-up. Don't use CCleaner or any other app to write zeros to an SSD. Once you're done with the secure erase, setup your RAID again and install the Intel Solid-State Drive Toolbox to optimize and perhaps run some diagnostics:
 
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18455
 
Let us know how it goes.

anyway, i did the secure erase, Parted Magic is a nice distro btw.
 
so anybody is interested to see the core? what tool to use, crystal disk ?

Thanks, again!
 

Thanks!

Haha. I think I remember you from Dejanh's old thread, dude :) That's why you still have the pic, isn't it?
 
I'll keep updating the X58 BIOS until I either get rid of my old rig or until Intel's ROMs stop working with it again. I think eventually, they'll stop providing legacy ROMs and go UEFI only.

Probably the best and most detailed guide out there by my fellow German bud Fernando:
 
http://www.win-lite.de/wbb/board208-specials/board281-bios-bios-modding/16658-bios-modding-how-to-update-pci-rom-modules-of-an-ami-phoenix-award-bios/

henryvits

Probably the best and most detailed guide out there by my fellow German bud Fernando:

http://www.win-lite.de/wbb/board208-specials/board281-bios-bios-modding/16658-bios-modding-how-to-update-pci-rom-modules-of-an-ami-phoenix-award-bios/

Henry, does 12.6 no longer support the ICH chipset? I can't get the Windows drivers to install :/
 
And if 12.6 doesn't support ICH, should I not be using a 12.6 OROM in my 758 BIOS?

henryvits

Hey dude. I had no problem installing the 12.6 drivers on my X58 with Windows 8 64-bit. I did have some trouble getting them installed properly on my 6-series chipset laptop and server, however.

Both the latest OROM and drivers work fine on all platforms, though.

 
Strange! How come station-drivers reports that ICH isn't supported past 11.7?
 
http://www.station-driver..m/page/intel%20raid.htm
 
Are you sure the 12.6 driver is "taking" on your x58? When I ran the 12.6 RST installer, it appeared like it installed just fine, but upon checking the actual Intel ICH10R SATA AHCI Controller device in Device Manager, it still shows the 11.7 driver. And then when I try to manually update this device to 12.6 through Device Manager, it won't "take" the update. When I pull a "Have Disk" and try to force it, it says that the device isn't supported.
 
I opened up the 12.6 INF and it doesn't have any vendor or device ID's that appear to support ICH10R
 
 
[Strings]
;
; Localizable Strings
;
diskId1 = "RST AHCI Installation Disk"
;client
PCI\VEN_8086&DEV_3B29&CC_0106.DeviceDesc = "Intel(R) 5 Series 4 Port SATA AHCI Controller"
PCI\VEN_8086&DEV_3B2F&CC_0106.DeviceDesc = "Intel(R) 5 Series 6 Port SATA AHCI Controller"
PCI\VEN_8086&DEV_3B22&CC_0106.DeviceDesc = "Intel(R) 5 Series/3400 Series SATA AHCI Controller"
PCI\VEN_8086&DEV_1C02&CC_0106.DeviceDesc = "Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller"
PCI\VEN_8086&DEV_1C03&CC_0106.DeviceDesc = "Intel(R) Mobile Express Chipset SATA AHCI Controller"
PCI\VEN_8086&DEV_1D02&CC_0106.DeviceDesc = "Intel(R) C600 Series Chipset SATA AHCI Controller"
PCI\VEN_8086&DEV_1E02&CC_0106.DeviceDesc = "Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller"
PCI\VEN_8086&DEV_1E03&CC_0106.DeviceDesc = "Intel(R) 7 Series Chipset Family SATA AHCI Controller"
PCI\VEN_8086&DEV_8C02&CC_0106.DeviceDesc = "Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller"
PCI\VEN_8086&DEV_8C03&CC_0106.DeviceDesc = "Intel(R) 8 Series Chipset Family SATA AHCI Controller"
PCI\VEN_8086&DEV_9C02&CC_0106.DeviceDesc = "Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller"
PCI\VEN_8086&DEV_9C03&CC_0106.DeviceDesc = "Intel(R) 8 Series Chipset Family SATA AHCI Controller"
 
Compared with 11.7's INF:
 
[Strings] 
; 
; Localizable Strings 
; 
diskId1 = "RST AHCI Installation Disk" 
;client
PCI\VEN_8086&DEV_2929&CC_0106.DeviceDesc    = "Intel(R) ICH9M-E/M SATA AHCI Controller" 
PCI\VEN_8086&DEV_3A02&CC_0106.DeviceDesc    = "Intel(R) ICH10D/DO SATA AHCI Controller" 
PCI\VEN_8086&DEV_3A22&CC_0106.DeviceDesc    = "Intel(R) ICH10R SATA AHCI Controller" 
PCI\VEN_8086&DEV_3B29&CC_0106.DeviceDesc    = "Intel(R) 5 Series 4 Port SATA AHCI Controller" 
PCI\VEN_8086&DEV_3B2F&CC_0106.DeviceDesc    = "Intel(R) 5 Series 6 Port SATA AHCI Controller" 
PCI\VEN_8086&DEV_3B22&CC_0106.DeviceDesc    = "Intel(R) 5 Series/3400 Series SATA AHCI Controller" 
PCI\VEN_8086&DEV_1C02&CC_0106.DeviceDesc    = "Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller"
PCI\VEN_8086&DEV_1C03&CC_0106.DeviceDesc    = "Intel(R) Mobile Express Chipset SATA AHCI Controller"
PCI\VEN_8086&DEV_1D02&CC_0106.DeviceDesc    = "Intel(R) C600 Series Chipset SATA AHCI Controller"
PCI\VEN_8086&DEV_1E02&CC_0106.DeviceDesc    = "Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller"
PCI\VEN_8086&DEV_1E03&CC_0106.DeviceDesc    = "Intel(R) 7 Series Chipset Family SATA AHCI Controller"

Strange indeed!
 
I've never run a 12+ driver, no. The highest I've reach is 11.7.4.1001. Drivers higher than this won't "take".
 
Interesting -- in Device Manager, mine still shows as "Intel(R) ICH10R SATA AHCI Controller. I run my motherboard in AHCI mode, so perhaps it has something to do with that?

Fernando has released a set of modified INF's, for the sole purpose of getting the 12.6 driver to "take". Could you possibly post the vendor and device ID of your SATA controller when you have the chance? Mine is VEN-8086 and DEV-3A22.
 
Additionally, what results/improvements have you noticed using 12+ drivers? On Fernando's site, he seems to mention that it might be better for x58 chipsets to stay on the series 11 drivers, and even then, I think he recommends the 11.2 driverset.
 
Have you noticed benefits to using 12.6? I typically prefer using the latest and greatest drivers and whatnot, but if Intel hasn't added or improved anything for the x58 in drivers 12+ and up, then perhaps it might make sense for me to stay on the older 11 series drivers.

Thoughts?

Updated original post (http://forums.evga.com/fb.ashx?m=1605686) with links to modded BIOSes containing latest Intel RAID Option ROM 12.7.0.1910 as well as latest Realtek PXE ROM 2.55.
 
Latest Intel RST package 12.7.0.1018 available here:
http://www.station-drivers.com/forum/viewtopic.php?f=32&t=4509

To answer your question, for a single drive RAID acts just like AHCI. The RAID ROM won't get invoked at boot, but it will show its version in the IRST software (not sure if that's the case with AHCI). Performance-wise, there should not be any difference. And yes, unfortunately, Intel decided not to support TRIM in RAID with the X58 chipset.

henryvits

To answer your question, for a single drive RAID acts just like AHCI. The RAID ROM won't get invoked at boot, but it will show its version in the IRST software (not sure if that's the case with AHCI). Performance-wise, there should not be any difference. And yes, unfortunately, Intel decided not to support TRIM in RAID with the X58 chipset.

 
First, I'd like to thank you for taking the time to update our raid roms. I also run a single  ssd, Samsung 840 Pro, with sata set to RAID in the bios with the latest RST. I was always under the impression that the latest RAID roms updated the RAID controllers AHCI rom? I've always done this since our x58 boards use the Pheonix ahci rom, it does not have Intel's ahci rom when the bios is set to AHCI. In terms of performance, I may be mistaken. However it seems the single SSD on RAID is more responsive in terms of windows startup, loading games and applications than when the bios isset to ahci on the pheonix rom. Have you or anyone experienced this?

henry, do you use any other tools besides CBROM for modding the BIOS?
 
I'm curious, as after following Fernando's tutorial (and successfully modding the 758 83 BIOS with today's Intel 12.7 OROM), I see that Fernando stresses to "replace" the ROM modules with ones that are named exactly the same. However, in your modded BIOS updates, you inject the ROM modules with their version numbers in their respective filenames --

Does this make a difference in anything? Is there any "harm" to be had by this? Of course, it'd be ideal to have the ROM modules named with their current version numbers after being injected, and so I'd prefer to do so, I'm just a smidgen "concerned" about Fernando's warning to keep the names exactly the same in order to use CBROM's "swap"/replace function (rather than releasing the ROMs then injecting the new ROMs, which apparently can lead to varying differences in BIOSes and/or BIOS checksums.

Just curious what your approach and reasoning is, and if there are other tools and/or methodologies that you employ.

 

henryvits

UPDATED 6/18/2013 with latest available ROMs!

Here are the links to all EVGA X58 motherboard BIOS 83 modded by me with the latest available Intel RAID Option ROM 12.7.0.1936, JMicron RAID Option ROM 1.07.28, and Realtek PXE ROM 2.55. Mod tool used is CBROM v.198. The only BIOS I have actually tested is the E75783.bin file, which is for the X58 LE board. All BIOSes should work just fine with these new ROMs, but just like Dejanh, I take absolutely no responsibility for any damage this may cause to your motherboard. Enjoy!

E756 https://docs.google.com/open?id=0B1_E2jaFAbT2MnlZWjluRC15VFk
E757 https://docs.google.com/open?id=0B1_E2jaFAbT2Vm9JSVNYNmRYUDg
E758 https://docs.google.com/open?id=0B1_E2jaFAbT2MllKUjZvaVFRRW8
E759 https://docs.google.com/open?id=0B1_E2jaFAbT2WDV4X3piS2tvZjA
E760 https://docs.google.com/open?id=0B1_E2jaFAbT2U0hwMWZic3ZYVVk
E762 https://docs.google.com/open?id=0B1_E2jaFAbT2b21WcHI0aGI4Ums
E767 https://docs.google.com/open?id=0B1_E2jaFAbT2OXFGOXp4UUh6aDQ
E768 https://docs.google.com/open?id=0B1_E2jaFAbT2X1daaTh2Q2hLWkE
E770 https://docs.google.com/open?id=0B1_E2jaFAbT2eUJDN3FPY0t2OWc

Holy Mother of God - you're awesome!
 
I just received my first BSOD in many a long time on a fairly new clean install (6 months old) on my 770 based rig.  Time to *finally* update the BIOS again :P