@ Pacman:
Thank you very much for your efforts to find/extract new PCI ROM modules and to post the links within this thread.
@ all, who are willing to test new PCI ROM modules:
Since I am already offering some non-AHCI/RAID related PCI ROM modules within the start post of this thread, I would rather like to add other and newer ones, which have been inserted into a BIOS and flashed successfully. So please report about your test results here, inclusive the Device of the related Controller, which is part of your mainboard.
As soon as the successful insertion ("Controller works fine") has been confirmed, I will add these freshly tested PCI ROM modules to the start post of this thread.
Thanks in advance!
Fernando
Please tell me how to spell commands to unpack the PXE LAN from the main file BootIMG.FLB?
I get a file of zero length 05de03.LOM
Thank you.
Please tell me how to spell commands to unpack the PXE LAN from the main file BootIMG.FLB?
I get a file of zero length 05de03.LOM
Thank you.
It’s the command you typed. Are you sure the DevID 05DE is a valid Intel LAN? I just checked and saw it extracts a zero length file, so i think this DevID is not supported/Valid.
Please tell me how to spell commands to unpack the PXE LAN from the main file BootIMG.FLB?
I get a file of zero length 05de03.LOM
Thank you.
It’s the command you typed. Are you sure the DevID 05DE is a valid Intel LAN? I just checked and saw it extracts a zero length file, so i think this DevID is not supported/Valid.
If you put such DeviceID 10d3, 153a or 153b then all is well.
If Device ID 1502, 1503, 1533 are extracted file of zero length.
In principle, you can do this:
1) to extract such as Device ID 10d3
2) romhdr.exe -v 0x8086 -d 0x1503 -i %1 -o %2
Get the same 1503 + Adjusted checksum offset 0x07. I tested it, works without problems.
romhdr.rar (36.6 KB)
Done!
All posts with the topic "Intel Sandy/Ivy bridge and Haswell VBIOS differences", which have been within this thread, have been moved into the appropriate linked thread.
Thanks!
Fernando
@SoniX
Maybe this is a new one, Broadcom PXE v16.0.1
http://www.mediafire.com/download/puyn57…PXE_v16.0.1.zip
Thank you. 
Where did he and EFI module was not there too 16.0.1?
I could not find that module, but here is the original BIOS if you want to check also
http://www.mediafire.com/download/3si9uv…2t/8237V100.zip
I also found some FW and other files for some Broadcom controllers, if you want them, here is a link
http://www.mediafire.com/download/4rwecdbdgua98cl/BC.zip
Unfortunately there is no EFI-module. 
Here there are for NeteXtreme II. Will Come In Handy.
There’s this package "Broadcom Ethernet Software Kit". It has a lot of interesting, LegacyPXE, EFI UNDI etc. I have only this version 15.4.4.1 package and can’t find a more recent version.
Very strange, why Broadcom not lays out on his website anything other than drivers.
release_15.4.4.1.txt (6.08 KB)
Ah, i see that i missed including the UEFI folder in the BC.zip i uploaded Before.
I uploaded the whole package those files came from, only removed some Linux & Solaris drivers, it is 110Mb, i attach the release.txt, so you can check first if you want it.
http://www.mediafire.com/download/m8ntz8…oadcom_T7.6.rar
release.txt (11.6 KB)
@Pacman
Thank you very much.
This set is suitable for BCM NetXtreme II 1 Gigabit Server/NetXtreme II 10 Gigabit Server (for the following chipsets: 5706, 5708, 5709, 5716, 57710, 57711, 57711E, 57712, 57800, 57810).
So there is nothing to check. 
It is not suitable for BCM NetLink 57xx (for the following current generation Ethernet chipsets: 5784, 5785, 57780, 57781, 57785, 57785x, 57788, 57790, 57791, 57795)
NetXtreme I Desktop/Mobile (for the following chipsets:
5700, 5701, 5702, 5703, 5704, 5705, 5751, 5752, 5753, 5754, 5755, 5756, 5761, 5764, 5782, 5786, 5787, 5788, 5789, 57760, 57761, 57765, 57766, 5901, 5906 ).
The OROM BCM LAN PXE 16.0.1, that you found, suitable for NetXtreme I.
@ SoniX and Pacman:
Do you think, that I should add the Broadcom LAN-ROM v16.0.1 into the start post of this thread?
If yes, can it be used with all listed Broadcom Ethernet chips (DeviceIDs: 16xx)) without the need of changing the hex code within the module?
@Fernando
OROM LAN PXE 16.0.1 BCM NetXtreme I Desktop/Mobile for the following chipsets:
5700, 5701, 5702, 5703, 5704, 5705, 5751, 5752, 5753, 5754, 5755, 5756, 5761, 5764, 5782, 5786, 5787, 5788, 5789, 57760, 57761, 57765, 57766, 5901, 5906
Device ID - I have met only one on ASRock - 16b1.
To change the Device ID in OROM to use ROMHDR #24
PS This tool is suitable to change the Device ID in OROM from Intel, Realtek, QCM-Atheros, only LAN PXE modules.
Yes, i Think it would be good to add to the Collection.
@ SoniX and Pacman:
Meanwhile I have uploaded and added the download links to the Broadcom PXE LAN ROM v16.0.1 within the start post of this thread.
If I have written something wrong or misunderstandable, please let me know it.
Ok. 
@ SoniX:
Thanks! It is already corrected.
Hello. I have P5B Deluxe motherboard with 88E8056 (11AB:4364) and 88E8001 (11AB:4320) Network adapters integrated. Today I successfully updated 88E8056 Option ROM with one you posted for appropriate adapter. But now I’m thinking about is it correct to update 88E8001 also with the same Option Rom as you posted for 88E8056 ? Would it work correctly ? Or those adapters too different ?
Thanks.
@ Gannet:
Welcome at Win-RAID Forum!
I think, that they are different.
You may be able to verify it by extracting both modules from the original BIOS and to compare the files with a Hex Editor. If they should just differ regarding the DeviceID hex code, you probably will be able to insert the 88E8056 OROM module after having customized the DeviceID entries, but I suspect, that both modules are not compatible with each other.
Regards
Fernando
Recently compared both modules from original BIOS and it found only two differences:
First:
1
2
2
CB 36 C8 <-- 11AB:4364 (Marvell 88E8056)
CB 76 C8 <-- 11AB:4320 (Marvell 88E8001)
Second:
1
2
2
AB 11 60 43 <-- 11AB:4364 (Marvell 88E8056)
AB 11 20 43 <-- 11AB:4320 (Marvell 88E8001)
Both modules has the same size (in uncompressed mode). So, it seems I can update the second module too with the same Option Rom by just changing "AB 11 80 43" to "AB 11 20 43" in 11ab-4380_v66813.bin first. What do you think ?