[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[skroutz999]

Bluetooth peripherals (keyboards, mice, BT speakers, etc.) generally work very well in Monterey with Fenvi FV-T919. For AirDrop and other Continuity-related issues it might be good to try this:

• iPhone --> shutdown and restart
• Hackintosh --> Reset NVRAM (press spacebar at OpenCore boot picker and select Reset NVRAM)

I tried your suggestions but they didn't work. I just also noticed that I can't send files via messenger in Safari. Strange behavior from both hackintoshes after upgrade to Monterey.

 

[CaseySJ]

I tried your suggestions but they didn't work. I just also noticed that I can't send files via messenger in Safari. Strange behavior from both hackintoshes after upgrade to Monterey.

I regularly AirDrop files to the Hackintosh, but not from the Hackintosh. Other Continuity features work quite well. Here’s another procedure to try:

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Logic Pro might crash if platform ID is set to 0x3E9B0007 (non-headless). If you run Hackintool, you'll see the current Platform ID immediately: Currently, it is set to 0x3E980003

www.tonymacx86.com

 

[skroutz999]

I regularly AirDrop files to the Hackintosh, but not from the Hackintosh. Other Continuity features work quite well. Here’s another procedure to try:

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Logic Pro might crash if platform ID is set to 0x3E9B0007 (non-headless). If you run Hackintool, you'll see the current Platform ID immediately: Currently, it is set to 0x3E980003

www.tonymacx86.com

Yes Airdrop files to Hackintosh works. The opposite function doesn't work anymore. I tried also the additional steps w/o success. Is there any chance to blame my config.plist CaseySJ? If it so I can attach it so you can take a look if you can.

 

[mrfatcatt]

I second. Anyone had tested the new BIOS? Something I don’t like however:
« Introduce capsule BIOS support starting this version.
Customers will NOT be able to reverse to previous BIOS version due to major vulnerabilities concerns. »

I did the update the BIOS to latest, and I didn't have any problems in hackintosh. My avid carbon was running fine thru my Asus 10G card. I didn't try TB but the latest Monterey OS booted fine and seemed ok so far.

I am having some weird problem where this motherboard now sometimes fast boots right into Windows 11 without showing the BIOS screen. Its frustrating as hell when it happens cause i have to pull the CMOS battery out. I haven't been able to get a AMD card so I have to constantly switch from my Nvidia card to Intel to boot OpenCore.

My fast boot is off in BIOS. Is there something I can do to prevent this automatic fast booting from happening??? It's extremely disruptive to my work.

 

[brousseau6933]

I did the update the BIOS to latest, and I didn't have any problems in hackintosh. My avid carbon was running fine thru my Asus 10G card. I didn't try TB but the latest Monterey OS booted fine and seemed ok so far.

I am having some weird problem where this motherboard now sometimes fast boots right into Windows 11 without showing the BIOS screen. Its frustrating as hell when it happens cause i have to pull the CMOS battery out. I haven't been able to get a AMD card so I have to constantly switch from my Nvidia card to Intel to boot OpenCore.

My fast boot is off in BIOS. Is there something I can do to prevent this automatic fast booting from happening??? It's extremely disruptive to my work.

Are USB-C devices recognized on the Thunderbolt ports? With f9j, it wasn’t working anymore…

 

[CaseySJ]

I did the update the BIOS to latest, and I didn't have any problems in hackintosh. My avid carbon was running fine thru my Asus 10G card. I didn't try TB but the latest Monterey OS booted fine and seemed ok so far.

I am having some weird problem where this motherboard now sometimes fast boots right into Windows 11 without showing the BIOS screen. Its frustrating as hell when it happens cause i have to pull the CMOS battery out. I haven't been able to get a AMD card so I have to constantly switch from my Nvidia card to Intel to boot OpenCore.

My fast boot is off in BIOS. Is there something I can do to prevent this automatic fast booting from happening??? It's extremely disruptive to my work.

When Windows applies system updates, it can change the boot preferences. When that happens we can press F12 at the Gigabyte Splash Screen and choose the OpenCore (UEFI) boot option. Additionally, we can enter BIOS Setup and fix the boot order in Boot section.

 

[mrfatcatt]

When Windows applies system updates, it can change the boot preferences. When that happens we can press F12 at the Gigabyte Splash Screen and choose the OpenCore (UEFI) boot option. Additionally, we can enter BIOS Setup and fix the boot order in Boot section.

Yeah, what I'm trying to say is the BIOS screen doesn't show. It goes straight into Windows after boot; no splash screen. I can't get into the BIOS to change the boot drive when this happens.I just have to pull the CMOST battery out.

I haven't tried any USB-c devices. I can try but I think I only have a Android phone, not sure that would help you with a dock or some other peripherals.

 

[jiffyslot]

I did the update the BIOS to latest, and I didn't have any problems in hackintosh. My avid carbon was running fine thru my Asus 10G card. I didn't try TB but the latest Monterey OS booted fine and seemed ok so far.

I am having some weird problem where this motherboard now sometimes fast boots right into Windows 11 without showing the BIOS screen. Its frustrating as hell when it happens cause i have to pull the CMOS battery out. I haven't been able to get a AMD card so I have to constantly switch from my Nvidia card to Intel to boot OpenCore.

My fast boot is off in BIOS. Is there something I can do to prevent this automatic fast booting from happening??? It's extremely disruptive to my work.

When I set up my BIOS for MacOS, (preferred operating mode = Setup) I password-locked the BIOS access (not the login) so that Windows cannot "fix" (break) the correct BIOS settings.

 

[faithie999]

Yeah, what I'm trying to say is the BIOS screen doesn't show. It goes straight into Windows after boot; no splash screen. I can't get into the BIOS to change the boot drive when this happens.I just have to pull the CMOST battery out.

I haven't tried any USB-c devices. I can try but I think I only have a Android phone, not sure that would help you with a dock or some other peripherals.

This isn't the answer you want, but you need to get into BIOS to change the boot order. Somehow the boot order got corrupted, and Windows Boot Manager ended up as the first boot device. I have had lots of trouble with my Designare (and Aorus Pro) getting into the BIOS menu after I get the Gigabyte splash screen. I need to mash the proper keys repeatedly, and, about 1 time out of 5, I get the BIOS setup screen. Often, instead I have to mash the F12 key repeatedly, which, when it the keystroke is recognized, at the bottom of the list of boot choices is a link to BIOS setup.

good luck

 

[zipb]

I have been getting these kernel panics while booting once in a while. I think it started after upgrading to Big Sur. Anyone know what this is about:

panic(cpu 4 caller 0xffffff8002dc4356): Kernel trap at 0xffffff800542c13b, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000001f8, CR3: 0x00000000080ae000, CR4: 0x00000000003626e0
RAX: 0x0000000000000000, RBX: 0xffffff936c02e7a0, RCX: 0xffffffa114393c90, RDX: 0x0000000000000000
RSP: 0xffffffa114393c20, RBP: 0xffffffa114393c70, RSI: 0xffffff936c02e7a0, RDI: 0xffffff86a70dea80
R8:  0x0000000000000020, R9:  0x0000000000000000, R10: 0xffffffb4d6b60450, R11: 0x0000000f936aa1c0
R12: 0xffffff936c4f78e0, R13: 0xffffff936c4f78e0, R14: 0xffffffa114393d88, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff800542c13b, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0x00000000000001f8, Error code: 0x0000000000000000, Fault CPU: 0x4, PL: 0, VF: 1

Backtrace (CPU 4), Frame : Return Address
0xffffffa114393640 : 0xffffff8002c8c26d
0xffffffa114393690 : 0xffffff8002dd3993
0xffffffa1143936d0 : 0xffffff8002dc3f8a
0xffffffa114393720 : 0xffffff8002c30a2f
0xffffffa114393740 : 0xffffff8002c8ba8d
0xffffffa114393860 : 0xffffff8002c8bd83
0xffffffa1143938d0 : 0xffffff800349c7ba
0xffffffa114393940 : 0xffffff8002dc4356
0xffffffa114393ac0 : 0xffffff8002dc403d
0xffffffa114393b10 : 0xffffff8002c30a2f
0xffffffa114393b30 : 0xffffff800542c13b
0xffffffa114393c70 : 0xffffff80033d770d
0xffffffa114393d10 : 0xffffff80033b5e79
0xffffffa114393d40 : 0xffffff80033bd863
0xffffffa114393d70 : 0xffffff80033d580f
0xffffffa114393e10 : 0xffffff80033d1bcd
0xffffffa114393e60 : 0xffffff80033cf120
0xffffffa114393eb0 : 0xffffff80033dc548
0xffffffa114393ee0 : 0xffffff80033ceb32
0xffffffa114393f30 : 0xffffff80033ec94e
0xffffffa114393f70 : 0xffffff80033ebf36
0xffffffa114393fa0 : 0xffffff8002c3013e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOHIDFamily(2.0)[A24CE0EE-3AC3-3F99-8353-78D651FBE744]@0xffffff800541b000->0xffffff8005477fff
            dependency: com.apple.iokit.IOReportFamily(47)[37461963-03B3-38F8-89AE-C2E4CF31422B]@0xffffff80057a2000->0xffffff80057a4fff

Process name corresponding to current thread: kernel_task
Boot args: alcid=11 shikigva=80 igfxfw=2

Mac OS version:
20G314

Kernel version:
Darwin Kernel Version 20.6.0: Wed Nov 10 22:23:07 PST 2021; root:xnu-7195.141.14~1/RELEASE_X86_64
Kernel UUID: C67468D8-72C1-36BC-A0DA-CD5FA852AD32
KernelCache slide: 0x0000000002a00000
KernelCache base:  0xffffff8002c00000
Kernel slide:      0x0000000002a10000
Kernel text base:  0xffffff8002c10000
__HIB  text base: 0xffffff8002b00000
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: 67676671639
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x0000000fc1d810dd
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000001787de33c8 0x0000000000000000