Intel raid rom 12.0.0.1783

[BOLTS4BREKFAST]

This is the latest intel raid rom...
https://docs.google.com/file/d/0B5ALl8wHmmIQNjc5UHhqN1g1ZEk/edit?usp=sharing

Is there any way that the latest R4E BIOS can be modded to include this rom?

I have tried myself.. but i think it's above my paygrade! lol:p

Perhaps someone else could give it a shot? or is it even possible?

Thanks!

[Nodens]

sandro c wrote:
Hi Nodens,
just a little clarification for me ... I asked if Snakeyes when he wrote "Noden's 11.6/3404 bios", it just means the Bios 3404 Nodens or there is Also a RST 11.6 modified by Nodens? I currently use your Bios mod. 3404 with RST 11.7 downloaded from Intel. And a little suggest how to resolve my trouble in the post #102.
My greetings to you and to the Forum always at the top of the interest.
sandro c.

Ah, I thought Snakeyes already answered it. There are 2 versions of the UEFI 3404, one with 11.7 and one with 12. There's no modified driver. Initially I had made a modded driver for easier installation because I forgot about the driver signature enforcement which prevents the installation of modded drivers.
You see, I run Windows in Test Mode, so I can install self-modded drivers, something I do all the time..hence I forgot hehe. I don't recommend regular users running Windows in Test Mode because it opens an attack vector. So I stopped adding modded drivers. (The only difference they had is that you didn't need to force install them, anyway, so there's no point if you have to run Test Mode for that--bigger hassle than force installing).

Regarding your problem on #102, it could be that your specific CPU sample can't handle it..Did you try getting to 4.8 with RAM set to 1600 or less?

[Snakeyes]

Thanks Nodens. There is more frequent confusion about the ROM imbedded into your mods (and the seemingly similar named/ numbered RST drivers) than you realize and take for granted given your expertise..

[sandro_c]

Thanks Nodens,
I'll try as soon as possible also Bios 3404 mod. for the vers. RST 12.0.0
Concerning the problem of the clock with the multipl. X48, I do not think is a problem of mem. because they are perfectly stable with mutipl.X45 and mem clock @ 2170 (FSB @101,7), while just setup with ISuite2, the multip. 46x and the mem. clock @ 2133 - FSb @100(factory), passes all tests but then after the first boot, it hangs in the loading of Win7! It seems be critical @ 46x, and then the 4.6 Ghz, while it is perfectly stable at 4.570 Ghz. Strange!?
Thanks for the answers
sandro c.

[Nodens]

Not a problem with mem but a problem with the IMC. Always test your clock with memory at 1600 or less. Anything above that is overclocking the memory and your're putting pressure from "both sides" on the chip. The higher you clock your RAM the lower you can OC the CPU on these chips. So if you want to find the CPU limit you have to overclock only the CPU. Find the limit first, then start raising the RAM.

[Fernando_11]

FYI: Regarding the missing support of X79 RAID systems by Intel's actual RST(e) drivers v11.x.x.xxxx and v12.x.x.xxxx I just have started a new thread at the Chipset Forum of Intel Communities. You can find it >here<.
Maybe this discussion will help to get a better RAID driver support for X79 chipsets by Intel in the near future.

[Nodens]

Thank you Fernando. It is an interesting question you're posing and I would like an answer as well. I already joined your thread at Intel Communities.
The boards that change the DEV_ID in PCI Configuration Space while loading the 11.6 OROM (Asrock/Gigabyte) can install the original driver packages for this reason. Perhaps this is why Intel is not bothering with it (which would be a rather disappointing answer).