Hi pir8man,
So, do you think I should better have both old and new CPU microcodes? Or this is only needed for other, older CPUs than X5690?
I owe you and all the people who have contributed to keep this thread (and our motherboards) alive, a huge THANK YOU !
(12-21-2017, 02:22 AM)Stahab Wrote: [ -> ]Hi pir8man,
So, do you think I should better have both old and new CPU microcodes? Or this is only needed for other, older CPUs than X5690?
I owe you and all the people who have contributed to keep this thread (and our motherboards) alive, a huge THANK YOU !
This thread is about MY bios releases, not testing your own. Please start your own thread. You can always PM me if you have an off-topic question. Please do not hijack my thread with your own bios development.
(12-21-2017, 09:20 PM)pir8man Wrote: [ -> ] (12-21-2017, 02:22 AM)Stahab Wrote: [ -> ]Hi pir8man,
So, do you think I should better have both old and new CPU microcodes? Or this is only needed for other, older CPUs than X5690?
I owe you and all the people who have contributed to keep this thread (and our motherboards) alive, a huge THANK YOU !
This thread is about MY bios releases, not testing your own. Please start your own thread. You can always PM me if you have an off-topic question. Please do not hijack my thread with your own bios development.
I am sorry I may have been misunderstood. I have no time, not enough knowledge nor intention on developing my own bios, and for sure, no thought of hijacking this thread.
I have red the entire thread of yours from the beginning and used included info for testing and experimenting on YOUR releases only. I modified YOUR S18i using info from post #51, only to test the new microcode alone and spot any changes on the system.
Again, I apologize for any inconvenience I may have caused. And THANK YOU for the precious work of yours!
With the new year, I really need to work on my R3E system and get it running again. the I can test and resolve the new versions.
hi there!
any possibility to edit what numbers can we set in bios?
esp interested in further increasing tRFC, as manually we can set it as far, as 160, but at auto in can go further (currently sits at 232)
Any confirmed accounts of Rampage III Extreme users getting ECC Ram (Registered or Non) to work with Xeon processors? I have a Xeon X5690 and I'm looking to buy 48 GB of Ram for this board.
I know of only one account for an owner of a Rampage III Gene (which is VERY similar to the extreme), with one particular type of ECC registered ram.
If there's anyone else who's had success or failures, please post your CPU / RAM chip so others can make note of it. Thanks!
(01-02-2018, 09:02 PM)pir8man Wrote: [ -> ]With the new year, I really need to work on my R3E system and get it running again. the I can test and resolve the new versions.
Any updates coming soon or RIP R3E?
(02-26-2018, 10:16 AM)Iceberg Wrote: [ -> ] (01-02-2018, 09:02 PM)pir8man Wrote: [ -> ]With the new year, I really need to work on my R3E system and get it running again. the I can test and resolve the new versions.
Any updates coming soon or RIP R3E?
It's Alive! Sorry for anyone waiting on me. I have many other projects distracting me. But I got my R3E board running today. I just installed Win 10 to an SSD(Sata-3) drive on the Intel controller.
I have plenty of SSD and HDD drives to test the various controllers and the latest test BIOS versions. (Hopefully, I may be speaking too soon.) Anyway. My trusty old R3E is up an running with it's XEON cpu and 6GB of ram.
Any further feedback on the latest test bios'??
I did a bit of digging in the forums over at win-raid. I found that the *newest* Marvell 91xx firmware is for the controller card version only and will not work as a BIOS OROM module. This is why zenek_bb found that the BIOS kept re-flashing it's firmware to the controller chip. So, I will be scrapping T2 from my next round.
Ok, so we know the latest CPU microcode works (no surprise there) and the Marvell controller actually has the newest compatible firmware for our boards. It's sad to say, but no company will be developing any updates for these older boards anymore. Once I come out with my updated releases, that will be all we can do with this board.
That said, I did not see anyone respond about the Jmicron downgrade to enable AHCI. I suppose I can test T3 before I work up my final releases for the R3E.
I am ecstatic to have my R3E board up and running again... Once I get this round of testing done, I will be making it my new home NAS. Running FreeNAS for movie storage and backups and some software archives. A couple small virtual machine jails. The R3E, with some more memory will last me another 5 years as a reliable machine.
Welp, That was easy. T3 works!
I flashed quickly using EZ-Flash. Booted and deleted the ATA controller from device manager. Did a rescan and it was re-detected as SATA (AHCI) controller. I then plugged in an SSD drive to power and connected it's sata cable to the jmicron internal sata port. Windows detected and installed the drive via hotplug. no reboot necessary.
OK, so we have our two features for me to juggle into new BIOS releases. CPU Microcode update and AHCI on the Jmicron Controller.
I will try to get it done this weekend. but it may take up to next weekend for testing before release.
EDIT:
I found an updated LAN OROM. I will test the two newer versions I found and include my findings in the next batch of BIOS'.