Contribute
Register

The everything works Asus Z390-I Gaming * i7-8700K * SAPPHIRE NITRO+ Radeon RX Vega 64 Build

@ModMike, now I use your latest Clover, it works more stable for me. I noticed that my 5700 XT card is detected on macOS as Vega 64, that is, incorrectly. I think the problem is the extension RadeonBoost.kext.

In Geekbench, it is defined as: AMD Radeon Unkown Prototype Compute Engine.

Screenshot 2020-04-29 at 16.13.20.jpg

Снимок экрана 2020-04-29 в 16.13.29.jpg

Update #1

I deleted the Radeon Boost.kext file in Clover, but my graphics card is still detected as Vega 64.
 
Last edited:
iDrakus said:
I found out exactly when the black screen appears in the BIOS when using OpenCore.

The black screen in the BIOS appears only after the computer exits sleep mode when using macOS. If the computer slept, then
There are two ways to solve the black screen in the BIOS on the ASUS ROG Strix Z390-I Gaming. I checked both and they both work great.

Two ways to solve the problem:
1. Reset NVRAM in OpenCore bootloader
2. Flashing BIOS through Windows 10

In both cases, the problem is immediately resolved. I recommend using the first option, as it’s easier.
Click to expand...
I agree, resetting the NVRAM is lots easier, haven't had to deal with that in a while now but great to know.
 
fgxr8 said:
just had a reboot while watching a 4k video on youtube
after restart looked at the error report this is what it shows:
Code: 
panic(cpu 5 caller 0xffffff801ec4c32a): Kernel trap at 0xffffff7fa08fba46, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000038, CR3: 0x00000006ec0040ad, CR4: 0x00000000003626e0
RAX: 0x000000009a000010, RBX: 0x0000000000000000, RCX: 0x000000009a000010, RDX: 0x0000000021000000
RSP: 0xffffff83ce4c32a0, RBP: 0xffffff83ce4c3320, RSI: 0xffffff8065156df0, RDI: 0x0000000000000000
R8:  0xffffff83ce4c33c0, R9:  0x000000000000000d, R10: 0x000000000000006e, R11: 0x0000000000000003
R12: 0xffffff805e02a000, R13: 0xffffff8065156dd0, R14: 0xffffff805dc50d10, R15: 0xffffff8065156df0
RFL: 0x0000000000010246, RIP: 0xffffff7fa08fba46, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000038, Error code: 0x0000000000000000, Fault CPU: 0x5, PL: 0, VF: 0

Backtrace (CPU 5), Frame : Return Address
0xffffff83ce4c2d00 : 0xffffff801eb215cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff83ce4c2d50 : 0xffffff801ec5a3c5 mach_kernel : _kdp_i386_trap + 0x155
0xffffff83ce4c2d90 : 0xffffff801ec4bf7e mach_kernel : _kernel_trap + 0x4ee
0xffffff83ce4c2de0 : 0xffffff801eac7a40 mach_kernel : _return_from_trap + 0xe0
0xffffff83ce4c2e00 : 0xffffff801eb20c97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff83ce4c2f00 : 0xffffff801eb21087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff83ce4c2f50 : 0xffffff801f2c2c7c mach_kernel : _panic + 0x54
0xffffff83ce4c2fc0 : 0xffffff801ec4c32a mach_kernel : _sync_iss_to_iks + 0x2aa
0xffffff83ce4c3140 : 0xffffff801ec4c028 mach_kernel : _kernel_trap + 0x598
0xffffff83ce4c3190 : 0xffffff801eac7a40 mach_kernel : _return_from_trap + 0xe0
0xffffff83ce4c31b0 : 0xffffff7fa08fba46 com.apple.filesystems.apfs : _obj_release + 0x1e5
0xffffff83ce4c3320 : 0xffffff7fa08e548b com.apple.filesystems.apfs : __bt_lookup_variant + 0x3e6
0xffffff83ce4c33f0 : 0xffffff7fa08e5993 com.apple.filesystems.apfs : _bt_iterator_next + 0x4e
0xffffff83ce4c3430 : 0xffffff7fa08b76df com.apple.filesystems.apfs : _iterate_jobjs_with_hint_and_snap + 0x237
0xffffff83ce4c34f0 : 0xffffff7fa0878220 com.apple.filesystems.apfs : _apfs_vnop_readdir + 0x4d8
0xffffff83ce4c3d10 : 0xffffff801ed99bf9 mach_kernel : _vnode_readdir64 + 0x3e9
0xffffff83ce4c3dc0 : 0xffffff801ed9a15b mach_kernel : _getdirentries + 0x4bb
0xffffff83ce4c3ef0 : 0xffffff801ed9a3ab mach_kernel : _getdirentries64 + 0x6b
0xffffff83ce4c3f40 : 0xffffff801f1875f7 mach_kernel : _unix_syscall64 + 0x287
0xffffff83ce4c3fa0 : 0xffffff801eac8206 mach_kernel : _hndl_unix_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.apple.filesystems.apfs(1412.101.1)[EA36BB76-1D94-32FF-9D55-4CBAA20C8F5A]@0xffffff7fa0833000->0xffffff7fa096efff
            dependency: com.apple.kec.corecrypto(1.0)[A6D59354-C9A1-3C61-87A7-C04DD74421B1]@0xffffff7fa00f3000
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[4C3D892C-12F7-344D-AD97-FF3C154B54D8]@0xffffff7fa07eb000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[425BC668-32EC-368C-B4EB-CF8510846BEE]@0xffffff7f9f50c000

BSD process name corresponding to current thread: tccd
Boot args: keepsyms=1

Mac OS version:
19E287

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar  4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6
Kernel slide:     0x000000001e800000
Kernel text base: 0xffffff801ea00000
__HIB  text base: 0xffffff801e900000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 86103315063072

any ideas what went wrong?
Click to expand...
Have you used OpenCore or Clover? I have suspicions that OpenCore is unstable.
 
Leesureone said:
Are you still on the H370 board? You don’t say how you are expecting Bluetooth to work, what hardware are you using? @ModMike has kexts in place for a DW 1560 card, if you’ve got one of those you should be good.
Click to expand...
Same board; I never used any other card. I was able to connect my Android phone via Bluetooth and transfer a file 3 or 4 weeks ago. Not really a big deal that it no longer works, that was the only time I ever even tried it up until I tried to use my headphones after updating the EFI.
 
Daily
ROG Strix H370-I Gaming |  i5 8400 |  RX 580 Pulse 8GB
jb11381 said:
Same board; I never used any other card. I was able to connect my Android phone via Bluetooth and transfer a file 3 or 4 weeks ago. Not really a big deal that it no longer works, that was the only time I ever even tried it up until I tried to use my headphones after updating the EFI.
Click to expand...
Okay, not familiar with the H370. This motherboard requires replacement of the wireless/bluetooth card so different animal.
 
vio1 said:
Anyone have a way to change permissions for Catalina boot drive to be both read/write?
I've Googled it, and every way I've tried fails.
Click to expand...
www.tonymacx86.com

macOS 10.15 Catalina: How to Mount Root Partition Read/Write for Post-Installation

Just a quick post to share how to install Clover and other stuff to a 10.15 Catalina drive. The root partition is read-only by default. To make it read/write, use the following steps. 1. Open /Applications/Utilities/Terminal 2. Make the root partition read/write by entering the following: sudo...
www.tonymacx86.com www.tonymacx86.com
 
Build 1
ROG STRIX Z390-I GAMING |  i7 8700K |  Vega 64 8GB
Leesureone said:
How far did you read in that thread? Others reported the same error and apparently had it resolved with information later in the posting.
Click to expand...
Will take a look. Thanks.

I've started having another issue. When coming out of sleep, my Bluetooth is not working. My mouse and wireless keyboard won't respond. I have to plug in a USB cable to get my keyboard to work, and use a wired mouse. When I check the Bluetooth settings, it shows as Bluetooth is off, and pressing "turn Bluetooth on" doesn't do anything.

I've had this issue a while back on another install of Catalina (using Clover), and modMike suggested running Mac Optimizer and running Extras/ Execute All, and rebooting. It worked on my old installation of Catalina (Clover), but I tried it now on this OpenCore version, rebooted, put my computer to sleep, the Bluetooth is again off and cannot connect. Only a full reboot of the computer will temporarily keep Bluetooth operational. Any ideas on what I can try next?
 
Build 1
ROG STRIX Z390-I GAMING |  i7 8700K |  Vega 64 8GB
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top