Actually now I have 2 boards, with 2 identical MAC address. any tool to restore original MAC Adderss?
1. Yes but not by bios modification. Official oa2intel tool are used it working on a running system. 3. Activated. After using of tool slic are present in a bios dump. That's why I give you 2 dumps: original and sliced bios for comparing. Middleton's mod with patched digital signature verification proved to be not working after flashing by programmer (computer give picture but do not finish POST procedure, recovery could not make it's job and I have to burn another clean dump).
Thanks Just so I understand... the oa2intel tool does not create a new capsulse/BIOS image to flash, it merely adds a SLIC to the existing BIOS in memory, correct? If the oa2intel tool works, what, if anything, do we still need to try and achieve with the SLIC Tool? Thanks for clarifying, Andy
I have lost track of this as well since there are not much EFI yet....I think there are some questions to be answered. IMO MSI and Asus will not digitally sign their EFI..anyway to examine what the intel tool does would be interesting.. I'll have a look at this soon...... Anyway I think the 2 TB limit can be exceeded with an ordinary bios...
WickedNick No. I have to use driver's interface to avoid conflict in a LAN. I did not find the suitable utility. BIOS recovery procedure did not resore the original MAC.
Nick This tool supports only intel network adapter. But my board has Realtek PCI-E Lan adapter. Is there any tools for it possible?
anmg, the Realtek chip, that is implemented on the board, can work in two modes: with separate EEPROM chip (93C46, mainly) and without it. In the second case, the MAC Address is programmed by the BIOS (in BootBlock - for AWARD BIOS). Look at the offset 0x260 of the image you have provided before. It looks like MAC Address variable - "LanMacAD". I will check the possibility of changing this variable by myself at first. If no success, I will ask Intel guys to help me change the MAC Address in the G41 series boards
Nick I think it is the second case. otherwise I would not have this problem. actually I can view all devices with command lanconf all But almost all marked as unsupported including Network device. I viewed all possible options and did not find where I can edit MAC.
Just a reminder, my board is DX58SO. @andyp: oa2intelwin.exe tool works with kernel mode driver (variable.sys) and a proxy DLL (EfiVar.dll) used to send IOCTLs to the driver. EfiVar.dll has 5 exported functions: 1. GetExportDb() 2. GetNextVariableName() 3. GetVariable() 4. ReadPhysicalMemory() 5. SetVariable() Here is what the tool reports when I run it with status command from Windows XP command prompt (I tried to load keys before from DOS): Code: c:\TEMP\Intel>oa2intelwin status OEM Activation 2.0 Utility - X006 Copyright (C) 2004-2007, Intel Corporation Distributed under restricted license. Do not redistribute. Windows Marker: PROGRAMMED Public Key: PROGRAMMED Signed Public Key: PROGRAMMED Requested operations completed successfully. This DLL seems to have some debug tracing code whose output I captured for my board using DbgView: Code: INFO:VarDLL:DllMain entry point INFO:VarDLL:InstallDriver:entry point INFO:VarDLL:InstallDriver:detected OS is WIN32 NT or WIN64 NT INFO:VarDLL:ReadPhysicalMemory:entry point INFO:VarDLL:GetVar:entry point ERROR:VarDLL:GetVar:DeviceIoControl call with IOCTL_DIOC_GETVAR failed INFO:VarDLL:GetVar:entry point INFO:VarDLL:GetVar:entry point ERROR:VarDLL:GetVar:DeviceIoControl call with IOCTL_DIOC_GETVAR failed INFO:VarDLL:GetVar:entry point ERROR:VarDLL:GetVar:DeviceIoControl call with IOCTL_DIOC_GETVAR failed INFO:VarDLL:GetVar:entry point ERROR:VarDLL:GetVar:DeviceIoControl call with IOCTL_DIOC_GETVAR failed INFO:VarDLL:DllMain entry point INFO:VarDLL:UninstallDriver:entry point That "failed" message probably explains why I was not able to find SLIC in the BIOS after my modding attempt. Driver itself is doing the following: 1. ptr = MmMapIoSpace(0xE0000, 0xFFFFF, 1); 2. After that, it is looking for "RSD PTR " (note spaces!) string in that region. If found, it copies 9 dwords. In my case, it seems to be failing because "RSD PTR " is located in 0xF0000, not in 0xE0000 segment. I tried to patch driver to look at 0xF0000, but still it doesn't make difference. Tool behaves as if it did something (shows "PROGRAMMED") but I cannot find the SLIC afterwards.
oa2intel The pubkey, marker, and sign (encrypted pubkey) came with the oa2intel tool for the following OEMs: ASUS, DELL, HP, J. The pubkey and marker appears to could be easily made from SLIC 2.1 file using WinHex utility. However, i is not clair, how to generate sign (encrypted pubkey) file, which is essentially the same as pubkey, but with the encrypted addition. This is important, if one wants to generate all three files from for other OEMs (e.g. SONY). Any ideas, how to generate the sign file?
pksign.bin there is from original JPSCSA intel only knows how to generate correct ecrypted pksign.bin