@SoniX

Not sure if you have seen my previous report about this, so please forgive me if it is already on your list. A bug with drvver and latest RSTe 4.3.0.1018 drivers.



I have also written some time ago about Marvell ROMs. The files that have an A in the ID are marked as IDE modules. These means 90A3, 91A0, 91A2, 91A3, 91A5, 91A8, 917A, 918A. The only exceptions are in 919x and 92xx IDs, where 91A2 and 922A, 923A are just alternate IDs. The class-code of 91Ax, 917A and 918A should be 01-01-8F (or 8F0101 in ROM) and it is found at 0x29-0x2B.

Zitat von lordkag im Beitrag #1673

---

Not sure if you have seen my previous report about this, so please forgive me if it is already on your list. A bug with drvver and latest RSTe 4.3.0.1018 drivers.

---

Zitat

---

I have also written some time ago about Marvell ROMs. The files that have an A in the ID are marked as IDE modules. These means 90A3, 91A0, 91A2, 91A3, 91A5, 91A8, 917A, 918A. The only exceptions are in 919x and 92xx IDs, where 91A2 and 922A, 923A are just alternate IDs. The class-code of 91Ax, 917A and 918A should be 01-01-8F (or 8F0101 in ROM) and it is found at 0x29-0x2B.

---

What is the best, correct or delete files for IDE?

Edit
@lordkag

Drvver 0.19.7
Fixed IRSTe SATA as sSATA in version 4.3.0.1018
Fixed Intel LAN UNDI 0.0.01, but as PRO/1000.

Edit2:
See BIOS from Asus P8Z77-V LE PLUS, it has OROM Marvell 9120, but the signature for IDE. How to understand?

Edit3: File remove.

If anyone has an older version of this software, suggest an achieve for ones with older machines, that has the 1c microcode if they could please pm me for an email addy it would be greatly appreciated.

Regards

Zitat von Shayne im Beitrag #1675

---

If anyone has an older version of this software, suggest an achieve for ones with older machines, that has the 1c microcode if they could please pm me for an email addy it would be greatly appreciated.

---

@SoniX

I would recommend to keep all common IDs, otherwise you will get reports on ROMs not being updated. In reality, only a few will be found on mainboards. Here is my take:
- for class-codes, it should be 01-01-8F/XY = IDE, 01-06-01 = AHCI, 01-04-8F/XY = RAID, 01-00-00/XY = SCSI
- Marvell it is using 01-01-8F on all its ROMs lower than 917x. You might think they do this to support those boards that are not AHCI compliant or default to IDE mode, but neither Intel nor AMD have done this. AMD and Intel are always using 01-06-00/01 on their AHCI ROMs. I would say this is a Marvell flop. They should use 01-01-8F on 91Ax devices and 01-06-01 for the rest.
- with 917x/918x they use the correct code: 01-01-8F on 917A/918A and 01-06-01 for the rest.
- with 919x they always use 01-04-8F. I'm not sure what is the purpose of 91A2, maybe it is in IDE mode and they switch the class-code internally, from firmware.
- with 92xx they appear to use 01-01-8F for an old 1.0.0.1003, while using 01-00-00 for the rest. The version 1.0.0.1003 is only found as a disabled link and can only be extracted with Extractor, MMTool doesn't see it.
- they often declare a bigger size for older ROMs, without adding padding.
- they used the same ID for different controllers. In HW_Config from firmwares you will find 9023, 90A3, 9110, 9190, 9111, 9191, 9120, 91A0, 9122, 91A2, 9123, 91A3, 9125, 91A5, 9128, 91A8, 9130, 91B0 and 9220, 9230, 9236, 9215, 9225, 9235, 922A, 923A. In the Marvell drivers you will find several others. Notice how 91A2 is used as an alternate ID for both 9122 and 9192.
- the firmware for 9128 controller starts with 9123 ID, then switches to 9128 in RAID mode and 91A3 in IDE mode. This means that they default to AHCI and can change the ID of ROM from firmware. This should have been the case for all others, start with AHCI ROM and AHCI class code, change when necessary.

I would say that Marvell doesn't know what it is doing half of the time. When cleaning the code of my scripts related to Marvell firmware, I have found the size bug:



As you can see, they declare the size three times as 0x36 blocks or 0x6C00 bytes, but the actual size is 0x6A00. And it is not only one file, many suffer from this bug. There is nothing against using more blocks than your ROM needs, but if you do declare a bigger size, add padding to fill that size. Luckily, the Marvell ROM it is always behind a link in CSMCore, so Extractor was not affected, but a fix has been added to 7.x just for this stupid thing of Marvell.

Here is my recommendation for UBU:
- add all the commons ID that can be found on mainboards: 9120, 91A0, 9123, 91A3, 9128, 9130 [maybe also 91B0], 9172, 917A, 9182, 918A, 9192, 91A2, 9230
- for 912x/91Ax/9130/91B0 use them as they are found, with class code 01-01-8F. Let Marvell deal with their mess. IDs 9130/91B0 should be used for Hyper-Duo, but they appear to use the same wrong 01-01-8F code.
- use 9172/9182 with class code 01-06-01.
- use 917A/918A with class code 01-01-8F.
- use 9192/91A2 as they are found, with class code 01-04-8F.
- use 9230 as found, with 01-00-00.

Hey, I'm trying to update the BIOS file of a Sabertooth P67, but I'm getting an error in MMTool saying I've got "insufficient space to add the file ...". The dots represent a long hexadecimal code.

I was halfway updating the various ROMs when this message started to appear. Any way to circumvent this?

Zitat von lordkag im Beitrag #1677

---

Here is my recommendation for UBU:
- add all the commons ID that can be found on mainboards: 9120, 91A0, 9123, 91A3, 9128, 9130 [maybe also 91B0], 9172, 917A, 9182, 918A, 9192, 91A2, 9230
- for 912x/91Ax/9130/91B0 use them as they are found, with class code 01-01-8F. Let Marvell deal with their mess. IDs 9130/91B0 should be used for Hyper-Duo, but they appear to use the same wrong 01-01-8F code.
- use 9172/9182 with class code 01-06-01.
- use 917A/918A with class code 01-01-8F.
- use 9192/91A2 as they are found, with class code 01-04-8F.
- use 9230 as found, with 01-00-00.

---

Zitat von Fernando im Beitrag #1680

---

The more modules you try to update at the same time, the more space is required within the BIOS.
My suggestion: Try to update the modules step by step.

---

@Fernando and @SoniX

Is Intel RSTe RAID ROM and EFI RaidDriver v4.3.0.1018 from UBU 1.28 Beta 5 safe for my GA-X79-UD3 F20 BIOS? A couple of weeks ago I heard that it only works on Intel X99 but I'm not sure if Intel added X79 support into the RSTe OROM.

Zitat von rootuser123 im Beitrag #1683

---

Is Intel RSTe RAID ROM and EFI RaidDriver v4.3.0.1018 from UBU 1.28 Beta 5 safe for my GA-X79-UD3 F20 BIOS?

---

My computer doesn't have RAID as I only have 1 single 2TB HDD. It is currently in AHCI mode. How do I set it to IRSTe mode?

EDIT: Oops Fernando just missed your edit when I was writing the post, so IRSTe mode is only for RAID Mode.