Hi, how did you flash the BIOS? Gigabyte EEPROM is soldered, so no SPI flashing is easily possible. Or did you use modified efiflash to get it flashed to the Board?
1st: it is SPI "serial" flash. Not EEPROM. 2nd: And you can usually contact the memory with adapter like this one : https://goo.gl/DFBA96
50/50change the SPI has grounded CS when board is off so if unlucky you actually have to desolder.
NOTE: This is only for the time when normal flashing of the bios fails.
Pretty sure Gigabyte is grounded or I fried the BIOS Chip on my last board. Couldn’t get it working in any way with flasher or rasppi GPIO. Modified efiflash should be able to flash the modded BIOS in theory?
how did you flash the BIOS? Gigabyte EEPROM is soldered, so no SPI flashing is easily possible. Or did you use modified efiflash to get it flashed to the Board?
@all anyone knows if 6-Core are already tested successfully on the z170 Boards?
Hello, I would like to ask why the Clevo P7XXDM in the BIOS directly add microcode after the machine can boot, but will be stuck in the boot logo on it? You can enter the UEFI setting. But as long as any storage devices plugged in, the boot hard drive lights flashing several times on the card in the logo there.
for additional old bios only have 506e0 506e1 506e2 506e3 4 microcode updates and do not support kaby lake. added 506e8 microcode trying to support kaby lake es cpu
Is it possible to achieve 7 or 8 generations of support by replacing modules in the P7xxDM BIOS with a DM2 BIOS module?Or replace the relevant modules in DM2BIOS to restore audio and power off?
yes, 1203. try use original bios (capsule) for test purpose
After test, the orginal bios is ok, but fixbios show these errors ( already fix the mc, gop and vbios)
parseFile: non-empty pad-file contents will be destroyed after volume modifications parseFile: non-empty pad-file contents will be destroyed after volume modifications patch: replaced 10 bytes at offset 1D6F6h 4181FBE0060800741941 -> 4181FBE0060900741541 patch: replaced 10 bytes at offset 2BDEh 4181FBE0060800741941 -> 4181FBE0060900741541 patch: replaced 10 bytes at offset 1965h 4181FBE0060800741941 -> 4181FBE0060900741541 Image patched [total hits/matching patterns/non-matching patterns] [008/1/0] z270fnew2.cap.patched 1 files checked, 1 changed. bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/A8499E65-A6F6-48B0-96DB-45C266030D83/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/A8499E65-A6F6-48B0-96DB-45C266030D83/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/A8499E65-A6F6-48B0-96DB-45C266030D83/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/299D6F8B-2EC9-4E40-9EC6-DDAA7EBF5FD9/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/299D6F8B-2EC9-4E40-9EC6-DDAA7EBF5FD9/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/299D6F8B-2EC9-4E40-9EC6-DDAA7EBF5FD9/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/EEEE611D-F78F-4FB9-B868-55907F169280/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/EEEE611D-F78F-4FB9-B868-55907F169280/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/EEEE611D-F78F-4FB9-B868-55907F169280/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/59ADD62D-A1C0-44C5-A90F-A1168770468C/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/59ADD62D-A1C0-44C5-A90F-A1168770468C/info.txt’: No such file or directory bin/cat: ‘z270fnew2.cap.patched.dump/BIOS region/59ADD62D-A1C0-44C5-A90F-A1168770468C/info.txt’: No such file or directory
is it importance?
or do the pcie patch first before mod the mc and gpu?