01-20-2018
02:48 AM
- last edited on
03-06-2024
08:10 PM
by
ROGBot
10-23-2018 02:18 AM
pottzman wrote:
Just want to ask a question here. I have followed this guide and have success. I flashed the latest ASUS 3902 bios. It contains revision 3C for 5960X (306F2) mCode. However there is now a revision 3D for this cpu. I have since modded the 3902 bios with revision 3D mCode and the system is running fine however using Inspectre as guided by OP it tells me there is a microcode update available. searching google I came across this page https://support.microsoft.com/en-us/help/4090007/intel-microcode-updates that shows the 5960X as having a CPUID of 40661 and a revision of 19. surely this is a typo right. However this site https://newsroom.intel.com/wp-content/uploads/sites/11/2018/03/microcode-update-guidance.pdf also has the same CPUID and revision and it seems to be from intel themselves......... whats going on here and why does inspectre tell me there is a mCode update available? can't make sense of it
10-31-2018 04:17 AM
04-02-2019 06:53 AM
04-05-2019 03:24 PM
Eikonic wrote:
I came across this thread when trying to get a bit more info on using the Bios Flashback button on the back of the board. I've used it before successfully, but that was years ago, and I've always been hesitant about flashing BIOS. Now i see this thread and Im even more hesitant as I need to do this stuff myself. How come Asus have not released a new bios for this board in almost a year? Is it because each system would need a bios specific for its chip... so bios updates are now just abandoned? I have always found this system to be flakey, and I was gathering up the nerve to finally flash to a much more recent BIOS... this is kinda scaring me again.
To clarify, the link to the new microcode says Linux. My chip is listed, and has been mentioned about, the 5960x. Im in Windows10. Im not somehow missing some fact that this is NOT meant for windows users? The post above me says win10, so im guessing its fine.
Why i started searching in the first place was to see if any special preparations were needed for the USB stick... format type, etc.... Can i just format to fat32 and then start the instructions on page1 here?
Finally, the new UBU 1.71 seems to have changed its menu options. I cant find the options for the steps in the first post. Can you update those steps so I know how to do this? I tried some 'logical' choices based on the available options, but couldnt find an update option.
Thanks
05-14-2019 11:34 PM
05-15-2019 03:27 AM
CMDRZOD wrote:
After reading about the latest zombie load attack on Intel CPU's I decided to see if there is a new microcode. Sure enough there is. Thanks again for having these instructions, once again they worked flawlessly. If you guys really want I can just post a link to the R5E.CAP I produced, which has the microcode 36h.
Here's links to the microcode and R5E.CAP if you don't feel like patching yourself. Note: My CPU is 6950X. If you do not have this CPU then this BIOS will not help you. You will have to build it yourself using the instructions on the first page and the new mCode from the link below.
Microcode:
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/archive/microcode-20190514.tar.g...
R5E.CAP I produced from building this myself for 6950X:
https://drive.google.com/open?id=1iW4S_rA6gcF4_WiXCrHXFdz46I2Pvw-_
Just booted it up and using it now. Seems no different from before, but I'm eagerly awaiting benchmarks and more news of what kind of performance may be lost due to mitigating this new vulnerability.
05-16-2019 06:04 PM
Axle Grease wrote:
Man, I read about the exploit only a few hours ago. Thank you very much for bringing this to our attention. I'll try the patch for the i7-5960X tomorrow.
Update: I tried flashing both modded and non-modded BIOSes using the USB BIOS Flashback method. For some reason that method no longer works.
05-16-2019 11:24 PM
CMDRZOD wrote:
I had a 2GB stick. I formatted it to FAT16 and put the R5E.cap file there. USB flashback port is one closest to motherboard. At first I was pressing the Bios reset button, till I realized I was supposed to be holding the bluetooth ROG connect button. Worked fine then.
Pretty sure an NTFS drive will not work.
05-17-2019 12:43 AM
05-17-2019 01:04 AM