[GUIDE] Gigabyte GA-Z370N-WIFI + i7 8700K + UHD 630 + Big Sur 11.0 DP1

[Max.1974]

Hi @Gigamaxx... maybe you want try test new EFI in your desktop Z170...just for boot install only...and the runnning install will long feel minutes after 20 sec at boot, and wait 4 minutes, so installer will run to install page region language...so, be patient...

 

Works fine in Lenovo E470 intel iGPU 620...is for install only, just put -igfxvesa on Nvram boot args.

 

 

EFI-Max.1974 - Z170 + AMD GPU.zip

[Synaesthesia]

Hi friend yes in the first command which reads 

hdiutil create -size 12G -fs hfs+ -volname install -type SPARSEBUNDLE ~/Desktop/install

12gb is not enough, for beta 3 so I used 16gb instead. Works!

hdiutil create -size 16G -fs hfs+ -volname install -type SPARSEBUNDLE ~/Desktop/install

 

Notice the difference. It's 16gb instead of 12gb. 

 

Also in the clean up commands where he says do this:

 

hdiutil detach `diskutil list |grep 'Install macOS Beta' |awk '{print $8}'` -force

 

I rather use command "diskutil list" to list all your disks. The one which is 12gb/16gb is the one you should detach. For me it was disk6 as you can tell here. (see attached screenshot)
 

hdiutil detach disk6 -force

I'm sure you notices your installer is probably called "Install Big Sur Beta" or something. I also use drag n drop to simplyfy matters. You can reveal the "createinstallmedia" file in finder and drag it into Terminal to avoid typing this whole command. Maybe you knew that. 

 

Good luck.

Edited July 23, 2020 by Synaesthesia

[Gigamaxx]

1 hour ago, Synaesthesia said:

Hi friend yes in the first command which reads 

hdiutil create -size 12G -fs hfs+ -volname install -type SPARSEBUNDLE ~/Desktop/install

12gb is not enough, for beta 3 so I used 16gb instead. Works!

hdiutil create -size 16G -fs hfs+ -volname install -type SPARSEBUNDLE ~/Desktop/install

 

Notice the difference. It's 16gb instead of 12gb. 

 

Also in the clean up commands where he says do this:

 

hdiutil detach `diskutil list |grep 'Install macOS Beta' |awk '{print $8}'` -force

 

I rather use command "diskutil list" to list all your disks. The one which is 12gb/16gb is the one you should detach. For me it was disk6 as you can tell here. (see attached screenshot)
 

hdiutil detach disk6 -force

I'm sure you notices your installer is probably called "Install Big Sur Beta" or something. I also use drag n drop to simplyfy matters. You can reveal the "createinstallmedia" file in finder and drag it into Terminal to avoid typing this whole command. Maybe you knew that. 

 

Good luck.

Yes it’s 12.88GB

[Somankr]

Successfully updated Big Sur Beta 2 to Big Sur Beta 3 through VMware Fusion

Edited July 24, 2020 by Somankr

[manmo71]

@ludufre 

 

I am following your guide to install Big Sur Beta 3 but I am stuck with this error (see attached image), I had success with Beta 1 & 2 with your method and with Beta 2 also managed to create a bootable USB installer.

I have been struggling with Beta 3.

Creating USB installer is fine, but I get stuck with the ASmedia failed to reset error prompt on boot, same as @meaganmargaret. But on one of my USB ports after a NVRAM reset it progresses fine all the way to the installer.

I end up with the same error above during installation even using the USB installer.

 

I have tried downloading the Beta3 using the gibMacOS script at least 3 times now, assuming the previous copies could have been corrupt.

But no luck so far.

 

Any clue what this error might be caused by?

[HenryV]

Donator, Obrigado para tudo sua trabalho.  Minha portugues e limitada.

 

Have HP laptop and want to install to single partition on internal HD or alternatively to USB flash card.   VM fusion does not list USB devices as option.

 

This does not work for partition nor for USB:

sudo diskutil unmountDisk diskX
/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/diskX fullDevice ~/Desktop/bigsur.vmwarevm/physical sata

This forum has this:

 

--BEGIN--

To create a Raw Disk vmdk:

    On the Mac terminal list all available disks and partitions by running this command:

    diskutil list
     
    Select the disk that should be used and list the partitions recognized by rawdiskCreator by running this command:

    /Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator print /dev/disk#

    Note: /dev/disk# should be one of the disk identifiers shown by diskutil list, for example /dev/disk1
     
    Create a vmdk file referencing the physical disk, and save it inside the virtual machine bundle by running this command:

    /Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk# <partNums> <virtDiskPath> ide

    Notes:
        <partNums> can be a comma-separated list of partitions to allow access to, such as "2" or "2,3". The numbers should match the output of the rawdiskCreator print command. Or to access the full disk, specify "fullDevice" instead of partition numbers.
        <virtDiskPath> should be a path inside the virtual machine bundle followed by a filename prefix, for example: ~/Documents/MyVM.vmwarevm/rawDiskFile

    This should create rawDiskFile.vmdk and for partitioned disks – rawDiskFile-pt.vmdk
     
    Edit the virtual machine configuration (.vmx) file of the virtual machine and add these lines. For more information, see Editing the .vmx file for your VMware Fusion virtual machine (1014782)

    ide0:0.present = "TRUE"
    ide0:0.fileName = "rawDiskFile.vmdk"
    ide0:0.deviceType = "rawDisk"
    suspend.disabled = "TRUE"
     
    Change ide0:0 to sata0:3
     
    Power on the Machine

---EOF--

 

Is there a better method to do the install to an existing partition with vmware fusion?  Prefer to install to USB to avoid any errors on the internal HD.

 

Alternatively, has anyone reading this used vmware workstation?

 

This is from vmware workstation info:

To add a physical disk to a virtual machine

1	Select the virtual machine.

Make sure the virtual machine is powered off.

2	Choose VM>Settings.

The virtual machine settings editor opens.

3	On the Hardware tab, click Add to start the Add Hardware wizard.

4	On the Hardware Type page, select Hard Disk and click Next.

5	On the Select a Disk page, select Use a physical disk and click Next.

6	When the warning appears, click OK.

7	Complete the Select a Physical Disk page and click Next.

•	Choose the physical hard disk to use from the drop-down list. Workstation supports physical disks up to 2TB.

•	Select whether you want to use the entire disk or only individual partitions on the disk. If you select Use entire disk, continue with Step 9.

8	If the Select Partitions page appears, select the partitions you want to use in the virtual machine and click Next.

This page appears if you selected Use individual partitions in Step 7.

Only the partitions you select will be accessible to the virtual machine. The other partitions might be “visible” to the guest operating system, but it is not possible to mount, access, or format them.

9	On the Specify Disk File page, accept the default filename and location or browse to a different location.

10	To specify a device node for your virtual disk, or to exclude disks from snapshots, click Advanced.

To exclude disks from snapshots, select Independent for the mode and choose one of the following options:

•	Persistent – Changes are immediately and permanently written to the disk.

•	Nonpersistent – Changes to the disk are discarded when you power off or revert to a snapshot.

For more information on the snapshot feature, see Using Snapshots.

11	Click Finish.

The wizard configures the new physical disk.

12	If the partitions used on the physical disk are not formatted for your guest operating system, use the guest operating system’s tools to format them.

 

Caution Regarding the use of fdisk or a similar utility: • After you add a virtual machine disk by using one or more partitions on a physical disk, never modify the partition tables by running fdisk or a similar utility in the guest operating system. • If you use fdisk or a similar utility on the host operating system to modify the partition table of the physical disk, you must re-create the virtual machine’s physical disk.

[d5aqoep]

Here is my EFI of OC 0.6.1 built from scratch for my Gigabyte Z370N Wifi. This one boots Big Sur DP 4 from usb and installs just fine. I am using Intel Display Port Audio and also the onboard Realtek HD Audio. Both work. Wifi is BCM94352Z card which also works flawlessly. Bluetooth and Airdrop also work. USB ports work as expected. You need to create your own USBMap.kext.

 

 

OC_0.6.1_EFI_Gigabyte_Z370N_Wifi.zip

Edited August 7, 2020 by d5aqoep

[HenryV]

DP3 fails to install to partiton with vmware fusion instructions given in forum.  HP laptop with single spinning rust no partition install, usb media no partition install.

 

Vmware conplains can not open device.

 

Anybody with a vmware fusion solution to this and a DP3 OC build that boots.n

 

Stuck at "no variable initialized for method ESDT.

 

Catalina goes right past this ESDT issue when booting.

[d5aqoep]

14 hours ago, HenryV said:

DP3 fails to install to partiton with vmware fusion instructions given in forum.  HP laptop with single spinning rust no partition install, usb media no partition install.

 

Vmware conplains can not open device.

 

Anybody with a vmware fusion solution to this and a DP3 OC build that boots.n

 

Stuck at "no variable initialized for method ESDT.

 

Catalina goes right past this ESDT issue when booting.

If you have the same motherboard, why not use the readymade EFI from my sig and install from USB?

[antic]

Ok. This was looking like a great guide until I got to 

hdiutil detach `diskutil list |grep 'Install macOS Beta' |awk '{print $8}'` -force

I had to change 'Install macOS Beta' to 'Intsall macOS Big Sur' as installing the latest release but I get the following error message.

chris@chriss-Mac-Pro ~ % hdiutil detach `diskutil list |grep 'Install macOS Big Sur' |awk '{print $8}'` -force

hdiutil: detach failed - No such file or directory.

 

Also had to change the size of SPARSEBUNDLE from 12G to 15G as getting error ' not enough memory'. Im assuming the beta had less memory requirements.

 

I have followed the guide to the 'T' only changing 'Beta' for 'Big Sur'. See below

 

 

hdiutil create -size 15G -fs hfs+ -volname install -type SPARSEBUNDLE ~/Desktop/install

hdiutil attach ~/Desktop/install.sparsebundle

sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/install --nointeraction

hdiutil detach `diskutil list |grep 'Install macOS Big Sur' |awk '{print $8}'` -force

hdiutil makehybrid -o ~/Desktop/install ~/Desktop/install.sparsebundle

rm -rf ~/Desktop/install.sparsebundle.

 

Any assistance would be gratefully received. Thanks

[gizlin]

Hello everyone,

 

I have been using my Hackintosh since 2019 almost with no issues. Recently I started getting random kernal panics on daily basis. Any help is much appreciated.

panic(cpu 0 caller 0xffffff80064d0860): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x19a VID=0x144d DID=0xa808
. FW Revision=2B2QEXE7\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/d7e177bcf5/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.120.1/Common/IONVMeController.cpp:5499
Backtrace (CPU 0), Frame : Return Address
0xffffffc0ffffb960 : 0xffffff8003c8e04d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffc0ffffb9b0 : 0xffffff8003dd4e13 mach_kernel : _kdp_i386_trap + 0x143
0xffffffc0ffffb9f0 : 0xffffff8003dc540a mach_kernel : _kernel_trap + 0x55a
0xffffffc0ffffba40 : 0xffffff8003c32a2f mach_kernel : _return_from_trap + 0xff
0xffffffc0ffffba60 : 0xffffff8003c8d86d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffc0ffffbb80 : 0xffffff8003c8db63 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffc0ffffbbf0 : 0xffffff800449dc0a mach_kernel : _panic + 0x54
0xffffffc0ffffbc60 : 0xffffff80064d0860 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController14CommandTimeoutEP16AppleNVMeRequest.cold.1
0xffffffc0ffffbc80 : 0xffffff80064b545b com.apple.iokit.IONVMeFamily : __ZN16IONVMeController13FatalHandlingEv + 0x1af
0xffffffc0ffffbde0 : 0xffffff80043f47e5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffc0ffffbe50 : 0xffffff80043f46e6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6
0xffffffc0ffffbe80 : 0xffffff8003cd4605 mach_kernel : _thread_call_delayed_timer + 0x4a5
0xffffffc0ffffbef0 : 0xffffff8003cd5574 mach_kernel : _thread_call_delayed_timer + 0x1414
0xffffffc0ffffbfa0 : 0xffffff8003c3213e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[8E899C96-D93C-337A-952A-B8C54E90FBC4]@0xffffff80064ae000->0xffffff80064d7fff
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[DC3B80FD-4D23-3608-8AA2-9C526D44F5D3]@0xffffff80050fe000->0xffffff8005107fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[152D7047-0D43-3CA8-B1EA-251D3F80AC28]@0xffffff80052c0000->0xffffff80052d5fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[F7AA4BAF-35CF-3784-A50C-5FD9CDCBE488]@0xffffff800676c000->0xffffff8006794fff
            dependency: com.apple.iokit.IOReportFamily(47)[AE367C5D-FEFC-390D-ABDF-86E037890F00]@0xffffff80067a3000->0xffffff80067a5fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[6CD2A6EC-9FFC-370D-8FEE-C8016E5C6BBA]@0xffffff800686f000->0xffffff8006880fff

Process name corresponding to current thread: kernel_task
Boot args: -v keepsyms=1 debug=0x100 alcid=1 -lilubetaall uia_exclude=HS01;HS02;HS09;HS11;HS12;HS13;HS14;USR1;SS01;SS02;SS07 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20G95

Kernel version:
Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64
Kernel UUID: FECBF22B-FBBE-36DE-9664-F12A7DD41D3D
KernelCache slide: 0x0000000003a00000
KernelCache base:  0xffffff8003c00000
Kernel slide:      0x0000000003a10000
Kernel text base:  0xffffff8003c10000
__HIB  text base: 0xffffff8003b00000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 426488397085
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000000634cb0858f
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000112e5f256a 0x0000000000000000

 

 

[Allan]

Hello @gizlin. Your hardware is the same as this topic? Give us more information.

 

Do this please:

 

[deeveedee]

@gizlin Did you start experiencing your kernel panics after installing a new NVMe SSD?  If so, what NVMe SSD are you using?  Read this.

[gizlin]

18 hours ago, tonyx86 said:

@gizlin Did you start experiencing your kernel panics after installing a new NVMe SSD?  If so, what NVMe SSD are you using?  Read this.

 

I have been using Samsung EVO 970 since forever. Never had any issues with it until recently.

I guess there is a problem with the SSD?

19 hours ago, Allan said:

Hello @gizlin. Your hardware is the same as this topic? Give us more information.

 

Do this please:

 

 

My specs are:

MOBO: z370n
CPU: i7 9700K
Power: Enermax 650W
RAM: Ballistix 32GB
SSD 1: EVO970 512Gb (macOS)
SSD 2: WD Blue 2Tb (data only)
GPU: RX 580

 

 

 

I have disabled TRIM. So far it seems to be fine.

Edited September 2, 2021 by gizlin

[gizlin]

Does any one have issues updating the OpenCore? After the update, it makes to the login screen and get stuck 😕

[Anto65]

hI, did you also update the config.plist and check with ocvalidate if there were any warnings?
When you can please sign your hardware

[eSaF]

8 minutes ago, gizlin said:

Does any one have issues updating the OpenCore? After the update, it makes to the login screen and get stuck

Zip and post your EFI Folder.

[ludufre]

@gizlin the EFI driver is changed the way has been  written down on the config.xml

 

From:

 

<key>Drivers</key>
<array>
<string>OpenRuntime.efi</string>
</array>

To:

<key>Drivers</key>
<array>
<dict>
<key>Arguments</key>
<string></string>
<key>Comment</key>
<string></string>
<key>Enabled</key>
<true/>
<key>Path</key>
<string>OpenRuntime.efi</string>
</dict>
</array>

Updates according to the entries you have.

 

[gizlin]

Thank you for your replies, people!

 

@antuneddu

My hardware:

MOBO: z370n WiFI

CPU: Intel 8-Core Intel Core i7 (Coffee Lake)

RAM: 32GB Ballistics

SSD: 1TB WD Black and 2TB WDBlue

 

@eSaF I have attached it here ^^

 

@ludufre I will give it a try.

 

 

This is a copy of my working EFI folder it works with BigSur and it worked with Monterey Beta. However, once it update OC to any version higher than what it is, it won't work.

I tried to updating and downgrading bios. I though the problem was with my NVMe drive and even bough a new one 😕

I just removed the SN and UUID from the config list.

Thank you for your help ^^

 

 

 

 

 

EFI.zip

[Anto65]

6 minutes ago, gizlin said:

Thank you for your replies, people!

 

@antuneddu

My hardware:

MOBO: z370n WiFI

CPU: Intel 8-Core Intel Core i7 (Coffee Lake)

RAM: 32GB Ballistics

SSD: 1TB WD Black and 2TB WDBlue

 

@eSaF I have attached it here ^^

 

@ludufre I will give it a try.

 

 

This is a copy of my working EFI folder it works with BigSur and it worked with Monterey Beta. However, once it update OC to any version higher than what it is, it won't work.

I tried to updating and downgrading bios. I though the problem was with my NVMe drive and even bough a new one 😕

I just removed the SN and UUID from the config list.

Thank you for your help ^^

 

 

 

 

 

EFI.zip 9.68 MB · 0 downloads

Try and let them know don forget SN etc.

https://easyupload.io/h15exp

[gizlin]

Sweet Jesus! It worked! What was the problem?

[Anto65]

 

 These are the things that needed to be fixed

 

as well as the kexts were obsolet 

 

To not depend on others and do everything correctly by yourself  🙂 , to update OC you can use this very simple tool  OCAT   and follow here  https://github.com/5T33Z0/OC-Little-Translated/blob/main/D_Updating_OpenCore/README.md how to use it

 BUT I WIL SEND ANOTHER PLIST ADD OPENCANOPY  for gui and correct this 

 

[Anto65]

replace please your config with this ( don t forget SN )

config.plist.zip

Edited November 10, 2021 by antuneddu

[WizeMan]

Are you getting dual monitor functionality with this setup?

 

Trying: 

HDMI -> HDMI monitor 1

DP -> DP to HDMI adapter -> HDMI monitor 2

 

And I get flickering.

[kisyu]

Hello @ludufre, will this guide work for Monterey also?