Some infos for intel Rst NVMe

https://intel.activeevents.com/sz14/conn...A5425C2702BED8/

Ghostearth.

Zitat von MonarchX im Beitrag #1093

---

Zitat von Fernando im Beitrag #1092

---

Zitat von MonarchX im Beitrag #1091

---

OMG, I asked a question here about overclocking and now I can't find it.

---

>Here< is the post, which you obviously mean.

Zitat

---

Do these forums have option that will show me all my previous posts???

---

Have you ever tried to click onto your name as the author of any of your posts?

---

Thank you, but nope, not it. It was a later post where I provided my CPU specifics and a screenshot too (might be gone now), asking whether CPU Micrcode for overclockers would or could actually affect my CPU/system. Just tell me how to view all my posts and then I can find it. I'm not lazy - I just can't find the right options anywhere... I tried to click on my username from within forums and most forums have this "View all of this member's posts" option, but not these forums. I use Mozilla Firefox if that's of any help.

Just in case, here's my CPU info:



Would the microcode for overclockers (Sandry Bridge / Ivy Bridge) that is available through UBU benefit my CPU overclock somehow???

I am talking about Microcode 6A9-1B (newer) vs. 6A9-19 (older). The 6A9-19 is older, but supposedly better for overclockers. I remember a while back UBU stated somewhere that it was for Sandry Bridge overclocking, NOT Ivy Bridge. Now it seems it also benefits Ivy Bridge. Is that so? Would it help achieve higher clocks?

---

Hello MonarchX! I remember at the time I answered your question that i promised you a complete answer but this would be handled with a delay because i had lot of upcoming deadlines and urgent work but i advised you and Fernando of this situation RE:CPU Microcode BIOS modding questions/problems.
After this period i had problems at home with my father to the hospital and i wasn't able to follow the forum for obvious reasons, but in the meantime, Fernando was very kind and opened a thread for this specific topic for discussion and we could go on that thread:

RE:CPU Microcode BIOS modding questions/problems

Cheers,

KK

Zitat von Ghostearth im Beitrag #1095

---

Some infos for intel Rst NVMe

https://intel.activeevents.com/sz14/conn...A5425C2702BED8/

Ghostearth.

---

@Pacman

No, I haven't tested them, because I don't have the needed hardware. Should have posted a warning, but it is not too late to do it now. I uploaded the ffs files, because this way Sonix can inspect the files and cut to his needs, which is the executable section - body of PE32+. It is not recommended to use the ffs file as is, because your BIOS might expect a different GUID or not be able to follow the dependencies. Not to mention that these particular files I have uploaded have the dependencies after PE32+, which I don't know if it is the right thing to do.

In order to use them, open your BIOS file in UEFITool, search for SataDriver, select "Replace as is..." and replace with the above file, save as temp.rom. Open temp.rom in UEFITool, search again for SataDriver, expand it until you see PE32+ image section, extract body of PE32+ and delete temp.rom. Then open your BIOS file again, search again for SataDriver, expand it until you see PE32+ image section, replace body of PE32+ with the previous saved body and save. This preserves the GUID, dependencies, UI. Or you can wait for Sonix to provide clean files, with common GUIDs and dependencies.

There is also the manual way, with parsing sections and extracting the body of section type 0x10, but you again end up with UEFITool, unless you want to fix the section size, data size and checksums on your own.

If you did all this and still have problems, then maybe it is the driver itself.

@lordkag, I'm really glad that you can use my code to develop something, so I will never say anything against it, no need to mention it further.
Thank you for the report on that new Intel BIOS, support for this type of GUID section is added to UEFITool 0.19.0 release.

@lordkag
Totally agree with CodeRush. I want to wish you further success! :)

Added:

Zitat von lordkag im Beitrag #1090

---

Back to UBU.
- I have found some types of BIOS that are Aptio4, but are missing "USB Storage" in CSMCORE, like this one. I have added a search for "USB Device".
- On the other hand, EVGA X99 Micro BIOS E995_107 is AptioV, but not detected as such.

---

Zitat

---

- I think I know where the problem with Atheros Lan UNDI is. The pair 1.1.0.3 EFI + 2.1.1.4/2.1.1.5 OROM is normally for regular controllers, while the pair 1.1.0.4 EFI + 2.1.1.5 OROM is for Killer cards, former Bigfoot-Bitfoot.

---

I think generally exclude update LAN BOOT QCM-Atheros.

Zitat

---

- AMD VBIOS names should be Kaveri, Trinity, Kabini. See Kaveri, Trinity, Kabini or here.

---

Kaveri and Kabini this APU, iGPU (VBIOS) have another name Spectra and Kalindi.

Zitat

---

- Is hexfind set to test wb as default, instead of rb? It has problems with read-only files.

---

Fix.

Zitat

---

- Found some errors in AMD and EFI GOP version. Files attached.
- Since there could be some false positives in drvver, could you add a check for those affected? Like checking for Realtek or Aspeed or Intel in unicode? This doesn't affect UBU of course, since you already check before calling drvver, but it affects the normal testing, where "drvver file.ffs" could show version "Realtek 0.000" even when file.ffs has nothing to do with Realtek.

---

Tool DrvVer must write all over again. I'll do later.

Thanx SoniX,
UEFITool 0.19.1 is also out....
https://github.com/LongSoft/UEFITool/releases/tag/0.19.1.1 (UEFIExtract 0.3.2 / UEFIPatch 0.2.2 too).

When comparing latest UBU 1.8.15 with previous 1.8.13 I've noticed that Modules>VGA>2170.bin has been replaced with a September-modified one vs the November one in 1.8.13. Probably SoniX has a good reason for it, but since is not listed in changelog, I report it just in case

Zitat von Reducer im Beitrag #1107

---

When comparing latest UBU 1.8.15 with previous 1.8.13 I've noticed that Modules>VGA>2170.bin has been replaced with a September-modified one vs the November one in 1.8.13. Probably SoniX has a good reason for it, but since is not listed in changelog, I report it just in case

---

Hello,

the changes at AMD AHCI OROM v3.2.2.0 (Device ID 4391/7801) from v3.2.1.0 has on my ASRock AOD790GX/128M the following effects:
+ In Bootorder (BIOS) there's written correct "AHCI: SSD 850 Pro" instead of "IDE: SSD 850 Pro" (in AHCI-Mode).
o AHCI-Mode is funktion normaly.
- The Bootprocess is delayed at least 1 Minute for every SSD/HDD while the Operation-LED ist shining almost all the time. Maybe the drive is testing S.M.A.R.T.-Errors?

I don't like that & kicked it away and gone back to Version 3.2.1.0 - that's I would let you know ... and share my experience.

Best regards, MiMo

Am I missing something? I have Rampage IV Extreme. EFI installation Windows 8.1

Prior to using v1.8.15 .. Intel RST software reported I was using RAID ROM version 13.5.0.2118

After changing bios with 1.8.15 .. RST software now reports I'm using 13.1.0.2126 :( Is there no 13.5.0.2164 for my board?

I notice in the MODULES\IRST\13_5\ Folder there's no SataDriver43_x79 in v1.8.15 is this an error?