The links for Marvell 88E8056 Yukon LAN ROM are invalid, please update.
Thank you very much
GenDalf
@gendalf :
Thanks for the info about the broken links. Today I have checked all links of the start post and repaired resp. updated the broken ones.
Since I have been travelling the last weeks, I couldn’t repair the links earlier.
@ikm :
Thanks for the info about te new Realtek LAN ROM module and for posting the related link.
Now this new module is listed and the download link available within the start post of this thread.
Update of the Start Post
Changelog:
- new: Intel LAN Boot Agent GE ROM v1.5.81 (latest version, usable with nearly all modern Intel LAN Controllers)
- updated: Intel LAN Boot Agent GE ROM for DEV_1502 and DEV_1503 (now v1.5.50)
- updated: Realtek LAN ROM (now v2.65, thanks to ikm for the info and link)
- removed: Download links to special Intel VGA ROM (vBios) versions for Ivy/SandyBridge iGPUs (due to the modifications done by the mainboard manufacturers)
- fixed: all broken download links
If you should see anywhere a newer Option ROM module or find a mistake resp. a broken link, please send me a PM.
Thanks!
Dieter (alias Fernando)
Earlier, we tried to replace Attansic L1 rom with (P5B-VM SE) - it was unsuccessful.
I have P5K SE and I have installed a new Atheros LAN ROM v2.1.1.5 module
Everything works like clockwork
EDIT by Fernando: Replaced the spoiler tag by the original posts
@walkman8196 :
Welcome at Win-RAID Forum and thanks for your contribution.
Regards
Dieter (alias Fernando)
Update of the Start Post
Changelog:
- new: Intel LAN Boot Agent GE ROM v1.5.83 (latest version, usable with nearly all modern Intel LAN Controllers)
Thanks to SoniX for the source file.
Enjoy the new Intel LAN ROM module!
Dieter (alias Fernando)
Many thanks! What change do I need to do to use it in UBU? Just remove the header? Thanks!
@gpvecchi :
You can either manually replace the current Intel LAN Option ROM module of your mainboard BIOS by using the UEFITool or use the currently latest UBU update (it is included).
This OROM has DevID 0xFFFF, and it is taken from Update 1 for UBU 1.65 / 1.66
Update of the Start Post
Changelog:
- new: Realtek LAN PXE ROM v2.66 (dated 05/26/2017, designed for the Realtek Ethernet Controllers DEV_8168, thanks to Phoenix48 for the link)
- new: Intel LAN Boot Agent CL ROM v0.1.12 (latest version, usable with nearly all modern Intel LAN CL Controllers, thanks to SoniX for the source file)
Enjoy the new LAN ROM modules!
Dieter (alias Fernando)
Update of the Start Post
Changelog:
- new:
- Important remark regarding the DeviceID customization and Checksum8 correction of the Option ROM modules - when indicated
- Hint to SoniX’s new tool named "SetDevID"
Enjoy it!
Dieter (alias Fernando)
The new Intel Boot Agent GE v1.5.85 can be found in the new UBU tool. (Thanks to SoniX)
Update of the Start Post
Changelog:
- new: Intel LAN Boot Agent GE ROM v1.5.85 (latest version, after customization of the DeviceID and correction of the checksum-8 usable with nearly all modern Intel LAN Controllers)
- new: Intel LAN Boot Agent CL ROM v0.1.13 (latest version, after customization of the DeviceID and correction of the checksum-8 usable with nearly all modern Intel LAN Controllers)
Thanks to SoniX for the source files.
Enjoy the new Intel LAN ROM modules!
Dieter (alias Fernando)
For intel, Atheros, Atheros-QCM Boot Agents from UBU.
All OROMs are not configured for Device ID. Use SetDevID to configure the desired Device ID.
setdevid <devid> <infile> <outfile>
OROM also has the status of LOM, that is, only for motherboards.
for the Marvell 88E8056 Yukon PXE LAN ROM v6.68.1.3 on page 1, I tried to change the Device ID using a Hex editor from DEV_4380 to DEV_4364.
The checksums are different.
new file checksum is: E4
original file checksum is: 00
at offset 0x07, it is 8E for both files.
How do I correct this checksum difference? Thanks.
@nikey22 :
Why haven’t you used SoniX’s SetDevID tool?
Look into the post above yours.
Another option is to update the related Option ROM by using CodeRush’s UEFITool, which will automaticly correct the checksum.
After having done that, you can compare the input and the output file by using an Hex Editor.
SetDevID not support LAN Marvell.
I need 2-3 files with different DevID and versions to learn, then to add to the utility.
I tried it doesn’t work as SoniX has mentioned for Marvell chipsets as of yet.
This probably won’t work either since the ASUS P5Q Pro Bios is not UEFI.
I don’t mind doing it manually, but how do I correct the checksum-8 in the bios file…
EDIT by Fernando: Quoting code corrected