Sure. But as far as I know ASUS they have the same BIOS tree for almost all boards, so they can just recompile it without any porting, if it's already done. The problem is that the whole thing is hard and makes no sense from the developer's point of view.

I have an open case with Asus and they do reply once a day. I'll relay as much information I can give them and hope they release a new BIOS revision for this specific issue.

There is nothing any of us can do. Here are the real changes between 4001 and 4003:



From that, only PciBus relates to this GOP issue. Sadly, not only the changes from 4001 to 4003 are all over the place (plus new code added), but P8Z68V_LX and P8Z68V_LE use a different code base than other P8Z68-V boards. So there is no possible way to port this in hex, no way to take that file as is. PciBus is marked as EFI Boot Driver, so you will brick your system faster than a speeding bullet.

But I see that they updated P8Z68V_PROGEN3 at 2014/11/17, almost two years after previous release. So, they haven't abandoned this completely, although no real fixes like in the other branch. This is the big issue here: why didn't they ported this at the release time, when it would have been easier and a big plus for them?

If ever ASUS fixes my issue, I can right away just switch from Legacy to EFI Compatible without any ill-effects on the already-installed Windows on my machine, right? If I understand correctly, Legacy/EFI only affects the drivers during boot time (pre-OS).

Zitat von plutomaniac im Beitrag #97

---

Did you try the gpu on a CSM-disabled system to rule that out as a problem source?

---

I wanted to update this thread and some further advices from you guys. Well, ASUS gave me a beta BIOS to try out. I flashed over that BIOS revision and it worked just fine, I even got into Windows and EFI boot was working already. Now I restarted the machine, went into the BIOS setup page and disabled the "full screen logo" and did the save settings and restart. After that, the board won't POST at all. The VGA_LED is now solidly lit red and it doesn't go past that.

I've already tried clearing CMOS by using the 3-pin header, removed the CMOS battery, removed all GPUs and tried using just the onboard GPU and it still doesn't work. When I google for this problem, it seems that this is a very common problem for this board when updating the BIOS. The beta BIOS that they gave is the one that caused it, definitely. I've flashed this board several times without any problems but this time it just failed on me.

Is there a way to flash back an older version if the board can't even pass POST? If worse comes to worst, can a universal K150 PIC programmer work in hopes of flashing the stable ROM file for the chip? The BIOS chip is easily removable from the board. I can buy a pic programmer locally for just about $10 here but I'm not sure if it'll work?

@Fernando

I actually did already and they're still passing the information to the correct department. It's just taking a while for them to sort this out and I'm without a computer currently. This is why I was wondering if I could do this myself by using this guide by Pacman: [Guide] Recover from failed BIOS flash using Raspberry PI

Now is coderush active in this forum and can I PM him about this?

ASUS agreed to flash my BIOS in their service center and it revived my board. The only thing I'm having problems with is the LAN MAC address. The MAC address of the NIC is now 88:88:88:88:87:88. Can we still change this?

It also turned out that they've flashed the non-GEN3 version of my board on my BIOS chip. It did work but is there any side effect with this? Should I just reflash using the correct BIOS without any problems?

Since this is the closest related thread, I will post here. This VBIOS posted by Station-Drivers has the same version 1002D as the one I already modded for kevindd, so it is a definitive proof that Nvidia GOPs are released per architecture (with MXM variants).



I will probably write a little script to help me in fast updating of the EFI part in VBIOS to the latest version. If anyone is interested in newer GOPs for their card, I have a few extracted. This doesn't necessarily mean that I will mod it for you, just that I will provide an updated EFI, if I have one.

Zitat von kevindd992002 im Beitrag #72

---

@lordkag

I experience the same exact issue after flashing a BIOS with an inserted SataDriver and Intel GOP driver. Any more ideas?

NOTE: I thought of something and tried booting off of the embedded Intel GPU as it has now a GOP driver associated with it. I then tried using the "EFI Compatible" PCI Priority ROM setting and it did boot and I can access the BIOS without any problems! With this said, we can safely say that the problem would be in the GOP driver inside the Gigabyte GTX 670's that I have as they seem to not be compatible with EFI booting on my board. What do you think?

@plutomaniac

Just to let you know, doing an EFI boot with the Intel GPU did significantly decrease the boot time on this old board. That means that even if it's not a "clean boot", it still does something aside from the nice looks.

---