![]() I hope this answer some of your questions. Your 2 files ( extracted-from-dump-GbE.bin and extracted-stock-GbE.bin) (first 128bytes) were very similar, so I adjusted my files for you, which you can find in the attachment of this post. Just bytes being put together, with a description, in the source file). It’s not actual assembler code in anyway. (NOTE: I like the syntax of as for this sort of thing. s file which GNU assembler ( as) can turn into a binary again. To make my life easier I structured down the bytes of my GbE (with the descriptions from the ethernet-connection-i219-datasheet.pdf) into a. I’ve been messing around with my GbE recently. I think only the first 128 bytes are interesting in this case? The Intel I219 GbE is explained in ethernet-connection-i219-datasheet.pdf in section 10.0. Only the first 6 bytes of the GbE some questions about #1 (GbE region)! Just for reference: I flashed a stock GbE from Z170-A-ASUS-3802.CAP, then used eeupdate64e.efi (via UEFI Shell) to change the MAC address. List your NICs and MAC addresses: EEUPDATEW64e.exe /ALL /MAC_DUMPĬhange the MAC address of NIC 1: EEUPDATEW64e.exe /NIC 1 /MAC=macaddrĬheck the EEPROM checksum and size of NIC 1: EEUPDATEW64e.exe /NIC 1 /TESTĬhange the MAC address of NIC 2: EEUPDATEW64e.exe /NIC 2 /MAC=macaddrĬheck the EEPROM checksum and size of NIC 2: EEUPDATEW64e.exe /NIC 2 /TEST The tool to change the MAC address is EEUPDATEW64e.exe in Win圆4\OEM_Mfg (it needs administrative privileges and a driver which you can install by executing the install.bat file). I don’t know if this works, but you can try:ĭownload the TOOLS folder and read the install.txt file. I’ve recently discovered that there are leaked? (“ Confidential and not for general distribution.”) Intel Network Connection Tools which can change the MAC address and a million other things. Unfortunately I don’t have an ASUS Z170-WS, I only have an ASUS Z170-A. I still have doubts about the changes made by my for ASUS Z170-WS as I wrote in post #624! I still have doubts about the changes made by my for ASUS Z170-WS as I wrote in post did you receive the dumps for GbE region and BIOS region from so, can you give them to me too? This was what I was trying to sort out, where/if second MAC ID goes into BIOS, or not etc (it may be stored in on-chip FW only, we are not sure, has this all sorted out now, but I will like these files/info from you, so I can put into this boards folder, so I know for sure next time we run into this did you receive the dumps for GbE region and BIOS region from ? If you want, and you don’t mind, please dump GbE region for me (feel free to edit your MAC ID out, but please tell me what you change it to, so I know) > FPTw.exe -gbe -d gbe.binīut, if you really want to help, please also dump BIOS region > FPTw.exe -bios -d biosreg.binĪnd tell me your actual MAC ID, for both LAN Ports. Thanks, yes FD44 will change some things and sometimes not always correct, but I do not believe it will affect what I wanted to check about MAC ID in GbE region in “extracted-from-dump-GbE.bin” differs from the first block (offset 00000000)įiles.zip (828 - Sorry also, for my late reply to you now too differs more than the primary MAC address I extracted the two regions from davidm71’s dump (extracted-from-dump-GbE.bin) and from the last BIOS found on the ASUS site (extracted-stock-GbE.bin). Yes, plutomaniac is a ME FW genius!! And yes, always make backup, and then have someone check it to be sure it’s OK and valid if you don’t know for sure how to check, before you do any erase or some questions about #1 (GbE region)! ![]() ![]() If any header checksums of modules you edit need corrected UEFITool will do that on rebuild Main thing to keep in mind, always replace the same way you extracted. From the stock target BIOS, FD44 module (aka SMBIOSFlashData / FD44820B-F1AB-41C0-AE4E-0C55556EB9BD) expand to RAW area, select that, extract body, edit, replace body. ![]() From the stock target BIOS, Main padding between volumes in BIOS region, extract As-Is and replace As-Isģ. Extract davidm71’s GbE As-Is and then edit, then replace As-Is to your target stock BIOS.Ģ. Best practices, you know, until you know how to check post-edit vs pre-edit for issues.įor doing the actual edit with UEFITool, you need to extract only #1 from davidm71’s BIOS, the other two # below, you edit the stock one to match davidm71’s for that entire small block area in each instance, except with your data at the specific info locationsġ. The padding and GbE module should not be an issue, but that FD44 module inside volume may be, so best to stick with 25.0 until you know how to check to be sure it’s OK. Probably not in this case due to where you are editing, but I did not check if that second volume with FD44 module has any problems when using 28 or not. Please use 25.0 as mentioned, newer can cause issues on BIOS rebuild. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |