Contribute
Register

PSA: Gigabyte F20B BIOS changes

Status
Not open for further replies.
Hi,

I've updated my motherboard with F22a and now I'm stuck with this message at the very beginning:
Code:
OsxAptioFix2Drv: Starting overrides for System\Library\CoreServices\boot.efi
Using reloc block: no, hibernate wake: no
+++++++++++++++++++++++++
I've already tried to use "Patch APIC" and "KernelPM", I've already tried to change my BIOS settings, but with no luck!

It could be that I'm using a NVME disk, I've noticed that setting this BIOS Features>Storage Boot Option Control to "Legacy" the BIOS doesn't recognize the NVME disk anymore even if when I reboot the system it can load Clover (that is installed on the NVME).

Thank you.

P.S.:
I was writing in this thread about this issue, but then I found this more specific one.
 
I updated to f23a and destroyed nvme booting as well on my z170x-ud5. Mine has native support without patches. It appears the newer bios updates are changingbsonething woth nvme that breaks booting.

I get a kernel panic on boot when not in safe mode. The backtrack appears to mention power management for various motherboard and gpu monitoring however. Ive tried diagnosing and will keep trying for a bit before I abandon and rebuild this machine with another motherboard.

Anyone else able to patch a gigabyte board with the skylake/kabylake bug fix update successfully?


killkrt said:
Hi,

I've updated my motherboard with F22a and now I'm stuck with this message at the very beginning:
Code:
OsxAptioFix2Drv: Starting overrides for System\Library\CoreServices\boot.efi
Using reloc block: no, hibernate wake: no
+++++++++++++++++++++++++
I've already tried to use "Patch APIC" and "KernelPM", I've already tried to change my BIOS settings, but with no luck!

It could be that I'm using a NVME disk, I've noticed that setting this BIOS Features>Storage Boot Option Control to "Legacy" the BIOS doesn't recognize the NVME disk anymore even if when I reboot the system it can load Clover (that is installed on the NVME).

Thank you.

P.S.:
I was writing in this thread about this issue, but then I found this more specific one.
 
Hey all,
Just want to post about my experience with the new F20B BIOS. This Bios version was released for most of the SKylake/Z170 boards recently by Gigabyte. The BIOS adds support for Kaby Lake, but also does a pretty big overhaul of the UEFI and options as well. Generally this seems like a nice improvement but there are things to note...

I have tested the F20B versions for GA-Z170X-UD5 TH and GA-Z170X-Designare. They both have the same issues/improvements, but other boards may behave differently. First of all, the old bug where the BIOS would add extra UEFI boot entries every time it booted, for the same clover entry, flooding the BIOS with excessive boot options is now gone. It now correctly looks at the entry in EFI/BOOT and only sees this entry once. So that is good.

However in both my cases clover would NOT boot macOS at all until I checked/enabled both "Patch APIC" and "KernelPM" options in clover. This was not necessary in previous versions of the BIOS. If you do not enable these clover options, the boot will hang as soon as clover tries to load macOS (following the ++++++++++++++++++++++ in verbose readout). I don't see any downsides to having these options enabled but it does seem odd that it is required now when before it wasn't. This seems to be a CPUID issue or something related.

g\
how do i enable Patch APIC and KernelPM in clover?
 
how do i enable Patch APIC and KernelPM in clover?

I've put this settings in the Clover config.plist:

Code:
...
<dict>
    ...
    <key>ACPI</key>
    <dict>
       <key>PatchAPIC</key>
       <string>Yes</string>
        <key>DSDT</key>
        <dict>
            <key>Fixes</key>
            <dict>
                <key>FixShutdown_0004</key>
                <true/>
                ...
            </dict>
            ...
        </dict>
        ...
    </dict>   
    <key>KernelAndKextPatches</key>
    <dict>
        <key>KernelPm</key>
        <true/>
        ...
    </dict>
    ...
</dict>  
...

Note: I'm not at my PC, I'm trying to remember by hearth and checking the Clover configuration from this site.
 
Wow, so that BIOS is a bad one. It prevents me from booting Linux. I'm reverting or replacing this motherboard.

I've put this settings in the Clover config.plist:

Code:
...
<dict>
    ...
    <key>ACPI</key>
    <dict>
       <key>PatchAPIC</key>
       <string>Yes</string>
        <key>DSDT</key>
        <dict>
            <key>Fixes</key>
            <dict>
                <key>FixShutdown_0004</key>
                <true/>
                ...
            </dict>
            ...
        </dict>
        ...
    </dict>  
    <key>KernelAndKextPatches</key>
    <dict>
        <key>KernelPm</key>
        <true/>
        ...
    </dict>
    ...
</dict> 
...

Note: I'm not at my PC, I'm trying to remember by hearth and checking the Clover configuration from this site.
 
Downgraded to F20 based on some success in this tread. Will update when I install. Hoping i don't have a brick.

Wow, so that BIOS is a bad one. It prevents me from booting Linux. I'm reverting or replacing this motherboard.
 
Same stack trace on sensor monitors. I'll pull this board and replace it. From here I can experiment on it as an offline project vs my main development pc. My own fault for upgrading but I wanted to fix the skylake defect. Anyway...

Downgraded to F20 based on some success in this tread. Will update when I install. Hoping i don't have a brick.
 
Wow, so that BIOS is a bad one. It prevents me from booting Linux. I'm reverting or replacing this motherboard.

Uhm... That's strange, I am still able to boot Linux (Arch Linux distro) and Windows 10! I have only problems with OS X.
 
I've enabled KernelPM and APIC patch but get this kernel panic.. my bios settings seem to match up with the recommended settings.
 

Attachments

  • IMG_1267.JPG
    IMG_1267.JPG
    2.1 MB · Views: 145
Status
Not open for further replies.
Back
Top