Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
I have updated the Intel RAID O-ROM, but left other O-ROMs untouched. Should be safe for your array.
-
Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
Meltdown and Spectre Patched BIOS for X58 Motherboards
- Thread starter Regeneration
- Start date
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
Depends on the vendor/model.
IIRC, v11.6 for yours, the latest official version for ICH10R.
IIRC, v11.6 for yours, the latest official version for ICH10R.
Ok thanks for the info it is on 11.6.0.1702 now so , I think your are correct the Array should be okay.....
Gotta go look up my Notes , been a while since I Flashed a Board this Old
I think it has EZFlash 2 (or 3) though....Will Report back when I do it ...... , Cheers
Came across this on google and had to create an account to upvote. 
First of all, thank you very much @Regeneration for the effort you put in, very much appreciated!
If you don't mind I'd like to know more about how you go about patching the ROMs. From what I understand from an earlier post is that you simply use a hex-editor and the Intel-provided microcode and drop that into the old vendor ROMs. But how do you know where you have to plop which microcode for which ROM? I'd assume that say an MSI BIOS is different from an Asus BIOS, even if both come from AMI. Do you search for the old microcode that the specific ROM uses and try to find that within the ROM?
I'm planning to try your image for the Asus P6T Deluxe V2 on my board, together with a C0 i7 920. Also because I'm thinking about upgrading the CPU to a Xeon X56xx I looked at the latest microcode file for Westmere-EP (06-2c-02) from Intel's latest Linux microcode package (20180807) and found the matching blob in your image for the Asus P6T Deluxe V2, but not in the original vendor ROM, so I assume that's just dropped in. However also the surrounding area of the ROM was different, compared to the stock version, so I assume those are probably option ROMS/checksums/..?
Did you have to do some reverse-engineering of the BIOS or do you just happen to know how they are structured? In the latter case, can you point me to any resources regarding that topic?
I'm just asking out of curiosity btw. With projects like coreboot/libreboot/heads, etc. that replace the entire mess that is the outdated vendor firmware (on a few select platforms), being able to drop in fresh microcode into proprietary vendor images seems like a great first step to save old hardware from becoming obsolete from a security standpoint.
Cheers!
First of all, thank you very much @Regeneration for the effort you put in, very much appreciated!
If you don't mind I'd like to know more about how you go about patching the ROMs. From what I understand from an earlier post is that you simply use a hex-editor and the Intel-provided microcode and drop that into the old vendor ROMs. But how do you know where you have to plop which microcode for which ROM? I'd assume that say an MSI BIOS is different from an Asus BIOS, even if both come from AMI. Do you search for the old microcode that the specific ROM uses and try to find that within the ROM?
I'm planning to try your image for the Asus P6T Deluxe V2 on my board, together with a C0 i7 920. Also because I'm thinking about upgrading the CPU to a Xeon X56xx I looked at the latest microcode file for Westmere-EP (06-2c-02) from Intel's latest Linux microcode package (20180807) and found the matching blob in your image for the Asus P6T Deluxe V2, but not in the original vendor ROM, so I assume that's just dropped in. However also the surrounding area of the ROM was different, compared to the stock version, so I assume those are probably option ROMS/checksums/..?
Did you have to do some reverse-engineering of the BIOS or do you just happen to know how they are structured? In the latter case, can you point me to any resources regarding that topic?
I'm just asking out of curiosity btw. With projects like coreboot/libreboot/heads, etc. that replace the entire mess that is the outdated vendor firmware (on a few select platforms), being able to drop in fresh microcode into proprietary vendor images seems like a great first step to save old hardware from becoming obsolete from a security standpoint.
Cheers!
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
All of AMI and Award BIOSes from 2010 share a similar structure and leave the microcode uncompressed.
ucodes normally start with the following hex 01 00 00 00 XX.
However, there are a few rules, the ROM itself must remain in same size, some have checksum checks, AMI require ucodes to be in a specific size, and some motherboards are more sensitive to checksum errors.
There are a few 3rd party apps for BIOS modification and microcode extraction/injection (MCExtractor, CBROM, MMTool), but from my experience, can corrupt the ROM's structure and lead to POST issues.
My advice is to use those apps to learn about the procedure, but to do it manually.
ucodes normally start with the following hex 01 00 00 00 XX.
However, there are a few rules, the ROM itself must remain in same size, some have checksum checks, AMI require ucodes to be in a specific size, and some motherboards are more sensitive to checksum errors.
There are a few 3rd party apps for BIOS modification and microcode extraction/injection (MCExtractor, CBROM, MMTool), but from my experience, can corrupt the ROM's structure and lead to POST issues.
My advice is to use those apps to learn about the procedure, but to do it manually.
Last edited:
Well thx for the hard work !
I updated my Bios (Asus P6XD58-Premium / Core i7 970) yesterday.
Was easy to update, I have just used the built in Asus flashing utlility trough the bios..
I suppose this will also be the case for other Asus X58 owners...
I ran SpectreMeltdownCheck and InSpectre before and after applying this modded bios.
And they see no difference, and it looks like i'm still vulnerable for spectre ??
See screenshots bellow, before and after.
I don't understand what I'm doing wrong here.
(also running latest Windows 10 Pro build with updates)
Thanks again for all the hard work, great to see some love for x58 systems !
I updated my Bios (Asus P6XD58-Premium / Core i7 970) yesterday.
Was easy to update, I have just used the built in Asus flashing utlility trough the bios..
I suppose this will also be the case for other Asus X58 owners...
I ran SpectreMeltdownCheck and InSpectre before and after applying this modded bios.
And they see no difference, and it looks like i'm still vulnerable for spectre ??
See screenshots bellow, before and after.
I don't understand what I'm doing wrong here.
(also running latest Windows 10 Pro build with updates)
Thanks again for all the hard work, great to see some love for x58 systems !
Attachments
-
after bios mod.JPG -
before bios mod.JPG
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
InSpectre seems to cache the results. Try to disable protection, reboot, re-enable, and reboot again. Also make sure the microcode revision is 1F, and try to power cycle the system.
Last edited:
- Joined
- Oct 26, 2016
- Messages
- 1,787 (0.61/day)
- Location
- BGD
| System Name | Minotaur |
|---|---|
| Processor | Intel I9 7940X |
| Motherboard | Asus Strix Rog Gaming E X299 |
| Cooling | BeQuiet/ double-Fan |
| Memory | 192Gb of RAM DDR4 2400Mhz |
| Video Card(s) | 1)RX 6900XT BIOSTAR 16Gb***2)MATROX M9120LP |
| Storage | 2 x ssd-Kingston 240Gb A400 in RAID 0+ HDD 500Gb +Samsung 128gbSSD +SSD Kinston 480Gb |
| Display(s) | BenQ 28"EL2870U(4K-HDR) / Acer 24"(1080P) / Eizo 2336W(1080p) / 2x Eizo 19"(1280x1024) |
| Case | NZXT H5 Flow |
| Audio Device(s) | Realtek/Creative T20 Speakers |
| Power Supply | F S P Hyper S 700W |
| Mouse | Asus TUF-GAMING M3 |
| Keyboard | Func FUNC-KB-460/Mechanical Keyboard |
| VR HMD | Oculus Rift DK2 |
| Software | Win 11 |
| Benchmark Scores | Fire Strike=23905,Cinebench R15=3167,Cinebench R20=7490.Passmark=30689,Geekbench4=32885 |
@Regeneration ,
Thanks this fix my issue, disabling and renabling meltdown protecion..
I'm all good now
Keep it going !
Thanks this fix my issue, disabling and renabling meltdown protecion..
I'm all good now
Keep it going !
Attachments
-
after renabling.JPG -
cpu.JPG -
Motherboard.JPG
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
Glad to hear it solved the problem. Seems like a bug in Windows.
I've added the registry entries to disable/enable both protections to the 1st post, along with the latest official chipset and AHCI drivers for X58.
I've added the registry entries to disable/enable both protections to the 1st post, along with the latest official chipset and AHCI drivers for X58.
- Joined
- Aug 14, 2018
- Messages
- 2 (0.00/day)
Hi, this is the last BIOS for Asus P6X58D-E BIOS V8.03 with marvell 1.0.0.1038 :
https://www.bios-mods.com/forum/Thread-P6X58D-E-Marvell-Update?pid=102799#pid102799
Direct link: https://goo.gl/4VOonr
Can you add the last patches for meltdown and spectre?
Thanks for you effort and greetings from Spain
https://www.bios-mods.com/forum/Thread-P6X58D-E-Marvell-Update?pid=102799#pid102799
Direct link: https://goo.gl/4VOonr
Can you add the last patches for meltdown and spectre?
Thanks for you effort and greetings from Spain
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
@Probotector
Its better not to inject random upper versions of option ROMs. Doesn't always work as intended.
Besides, sometimes Intel's ICH10R performs better than all those Marvell/Jmicron PCIe x1 onboard controllers.
Its better not to inject random upper versions of option ROMs. Doesn't always work as intended.
Besides, sometimes Intel's ICH10R performs better than all those Marvell/Jmicron PCIe x1 onboard controllers.
Last edited:
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
Added ROMs for Elitegroup (ECS), Shuttle, XFX and Zotac.
If you have old X58 motherboard somewhere in the closet, feel free to put a Xeon in it now.
If you have old X58 motherboard somewhere in the closet, feel free to put a Xeon in it now.
Last edited:
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
Intel chipset driver isn't significant and the latest version is for Windows 7. It's probably will work just fine on Windows 10. RST driver is more important (AHCI/RAID) and it's compatible with Windows 10.
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
RST delivers better performance for SATA AHCI mode.
- Joined
- Jul 20, 2018
- Messages
- 30 (0.01/day)
Installed only the RST drivers, and now Windows 10 refuses to boot, gets top logo and then pc restarts continues in this loop, and eventually the repair options appear. Even trying Safe Mode does not work. Had to do System Restore. Hard drivers are set to AHCI mode in the bios. So I am back to the default drivers which have always worked. Ant idea why this would be happening? I have not updated my BIOS still using the last official version, could this be the problem?
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
Did you install Windows with SATA IDE or SATA AHCI? Try to install the RST driver manually via device manager.
- Joined
- Oct 22, 2014
- Messages
- 14,086 (3.82/day)
- Location
- Sunshine Coast
| System Name | H7 Flow 2024 |
|---|---|
| Processor | AMD 5800X3D |
| Motherboard | Asus X570 Tough Gaming |
| Cooling | Custom liquid |
| Memory | 32 GB DDR4 |
| Video Card(s) | Intel ARC A750 |
| Storage | Crucial P5 Plus 2TB. |
| Display(s) | AOC 24" Freesync 1m.s. 75Hz |
| Mouse | Lenovo |
| Keyboard | Eweadn Mechanical |
| Software | W11 Pro 64 bit |
Rapid Storage Technology IS NOT REQUIRED.
The best Chipset drivers are those supplied by the Motherboard manufacturer.
- Joined
- Jul 20, 2018
- Messages
- 30 (0.01/day)
Windows was installed with SATA AHCI, and the driver was installed via Device Manager, I didn't want any unnecessary Intel apps installed.
Regeneration
NGOHQ.COM
- Joined
- Oct 26, 2005
- Messages
- 3,128 (0.45/day)
Perhaps some 3rd party software (like DVD burning or SPTD) is interfering with the change of SATA drivers.
In the device manager, open one of your disk drives, navigate to details, and look for class upper/lower filters.
If some 3rd party driver/filter is assigned to a controller, changing the driver would result in BSOD at Windows' startup.