I have found a new version for Broadcom Lan modules. There are a few things to consider: - it was released as a NIC update, but as you have seen in older Broadcom packages, it can easily be converted to LOM modules. I have attached the original files for inspection, in Original folder. The folder Original_Split has the same files, just that image_nr2.bin is a multi-image ROM and was split into components. - Broadcom is offering a wild combination of images, based on the PXE and PCI specs. I’m not a master in those specs (only browsed them), but I will try to offer some details. >PXE< and >RPL< are different specifications for network booting. PXE is usually offered as a combination of BC [Base-Code] (= Protocol) and UNDI (= API). There is also the possibility of a third component, BUSD [CardBus] code, but I haven’t found any ROM with that component. Intel (who released PXE specification) also offers the possibility of two architectures, monolithic implementation and split implementation. Luckily, Broadcom hasn’t gone that far to offer all possible combinations. They offer BC as split implementation, UNDI as split implementation, or BC + UNDI as monolithic implementation - this covers only PXE code so far. They also offer PXE + RPL as MBA images. One strange case they offer is images with RPL support only, where the PXE section is not removed, just disabled. - Broadcom is offering 3 folders, based on PCI FW implementation. Legacy folder is based on PCI 2.3 and older, while fw30 is based on >PCI 3.0<. FW30_CLP is just PCI 3.0 with Command-Line Protocol. - The file image_nr1.lom is equivalent to q57mmbae.lom from legacy folder. The second image is equivalent to q57pxee.lom from from fw30_clp folder. - UBU uses q57pxee.lom from legacy folder. - My recommendation is to use image_nr1.lom, as it has PXE (BC + UNDI) and RPL, basically all available components from Broadcom. I don’t think PCI FW 3.0 or CLP has anything to offer to regular users. You can check the images in Extractor for more details, with “oromext bro”. - The supported IDs by ROM/EFI are included. - There are two variants of image_nr2.lom, the only difference being padding added to match the images from fw30_clp folder. This also involved changing the offsets of BC code and UNDI code. In terms of usage they should be identical.
@lordkag Thank You for the new files. Do you recommend use image_nr1.lom (q57mmbae.lom), but I’m not quite sure what the end user need all protocols PXE, RPL, BOOTP, and iSCSI Boot.
Q1 - I was just wondering if there is a web page where the UBU have the older versions since they contained older OROM versions. Example, the new version (1.42) has the Intel OROM 14.7.0.2341. Version 1.37 has the Intel OROM has 13.2.2.2224. So if I wanted an older OROM that was contained in one of these versions, how can I get to it?
Q2 - BTW, I am looking for the UBU version 1.41.1 version with version 14.6.1.2340.
We generally do not offer download links to outdated versions of the UBU tool, but there is another and probably better way to solve your problem: 1. Download the desired Intel RAID ROM module from the start post of >this< thread and unzip it. 2. Open the Modules\IRST\14_7 of the latest UBU tool and delete the file named SataOrom.bin. 3. Copy the unzipped Intel RAID ROM file you want to get inserted into the Modules\IRST\14_7 UBU subfolder and rename it to SataOrom.bin. 4. Run the UBU tool and choose to update the Intel RAID ROM to v14.7.0.2341. Since you had previously replaced the originally present OROM module v14.7.0.2341, you will get your desired OROM module instead. You can easily verify it by re-running the UBU tool.
Yes, image_nr1.lom is my recommendation, being similar to what UBU currently offers, but with the addition of RPL support. File image_nr2_v1.lom is almost identical to UBU file, just that it is the equivalent from fw30_clp folder. File image_nr2_v2.lom is the same as image_nr2_v1.lom, but with some padding before BC code, just like the .lom images from fw30_clp folder.
If you ask me about their usefulness, I would say that even PXE is overrated. Apart from the "feeling" of having it available in their systems and updated, I doubt you can find 10 users from this site who actually have an use for PXE/RPL/iSCSI/FCoE/etc. code. But since UBU is not about fixing bugs or safe updating, I would say that any easy updatable module should be offered as a choice.
There are not UBU-related. They are for your own collection (if you keep one). As far as I can see from the CPUIDs they are for older Core 2 Duo / Xeon systems.
They might be related to this Intel Memory SinkHole exploit that was found recently. The microcodes were found at an HP SPI with the only changelog being "fixed Intel Memory SinkHole exploit" or similar. Some info:
@lordkag I agree with you. I think the versatility to support different protocols are better than one. Size of course, a little more and not all BIOS have extra space. OK. In version UBU 1.43, be replaced by the universal MBA instead PXE.
Here is a new Marvell EFI driver, AHCI 1.1.0.1020. Unfortunately, RAID was not present in the package. I have some new details about these Marvell EFI drivers, but it mostly concerns drvver and Extractor. I will explain them in the next days, just posted the driver in case you plan on releasing a new UBU version.
It has been left there. The structure of the UBU tool stays untouched. You have just to copy/move the file named UBU_Upd_2.exe into the root UBU folder.
Edit: Actually I am not entirely certain for what it’s for. The sources are two mobile Skylake machines, Microsoft Surface Book & Microsoft Surface Pro 4. So some sort of Skylake microcode.
