Contribute
Register

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

CaseySJ said:
Are you certain that the Sabrent NVMe SSD has both an EFI partition and the entire OpenCore EFI folder?

If so, please try a CMOS Reset, which will require configuring BIOS parameters once again.
Click to expand...
Thanks for the reply - I will check this today. It is possible that this is the problem as I did find the EFI partion was empty when I loaded the RadeonBoost.kext - Ended up installing to the SSD and then cloning (CCC) to the SABRENT NVME. Question though is why would the system boot ok from NVME via OC bootloader if no EFI folder is present??
 
Does anyone know what to do if your Fenvi FT-919 card does show Bluetooth and WiFi connection but does not enable handoff or unlock with Apple Watch?

First time I booted with this card inserted it showed Bluetooth in Systeminfo but it would not find or connect to my trackpad.

When I booted into a clean live install MacOS from USB stick I could see the trackpad and connect to it without problem.

After that I rebooted into the fully installed MacOS again and I could directly work with the trackpad without any problems or connecting again.

But handoff does not work but it is turned on in Preferences. Also it can’t turn on unlock with Apple Watch. It keeps loading but does not do anything.

Does anyone know what to do to fix this?

I did try the intel WiFi+BT EFI in the past but got rid of it before I installed this Fenvi card. And I’m using the normal O.C. 0.6.5 again.
 
MacOS Flight
Z490 Vision D |  i9 10850K |  Vega 64 8GB
JBADER1 said:
Thanks for the reply - I will check this today. It is possible that this is the problem as I did find the EFI partion was empty when I loaded the RadeonBoost.kext - Ended up installing to the SSD and then cloning (CCC) to the SABRENT NVME. Question though is why would the system boot ok from NVME via OC bootloader if no EFI folder is present??
Click to expand...
CaseySJ said:
Are you certain that the Sabrent NVMe SSD has both an EFI partition and the entire OpenCore EFI folder?

If so, please try a CMOS Reset, which will require configuring BIOS parameters once again.
Click to expand...
[RESOLVED] As you suspected @CaseySJ and @emistral the EFI partition on the Sabrent NVMe was empty. Copied the entire EFI folder from the EVO SSD across to the Sabrent drive and now available in the BIOS and boots automatically from the OC bootloader. Thanks for pointing me in the right direction.

I bench marked the build this morning (post RadeonBoost install).

GB5
Single Core : 1328
Multi Core : 11113

GB 5 Compute Metal : 54860
GB 5 Compute OpenCl :66979
 
hi guys, I finished building this hackintosh with the same exact configuration and components, only the power supply is different. It has been working well for the most part but it is the second time that everything stops working. I have this in the report:

panic(cpu 2 caller 0xffffff7f846a0ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (13470 seconds ago): 1348, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (13440 seconds ago): 1328, last successful checkin: 120 seconds ago


that's the first part of the report, I can past the rest, just wanted to make sure it is ok to post it.

I am currently running catalina with opencore 6.4 and the corresponding efi from this thread.

Any help appreciated, thanks a lot :)
 
rd3500 said:
hi guys, I finished building this hackintosh with the same exact configuration and components, only the power supply is different. It has been working well for the most part but it is the second time that everything stops working. I have this in the report:

panic(cpu 2 caller 0xffffff7f846a0ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (13470 seconds ago): 1348, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (13440 seconds ago): 1328, last successful checkin: 120 seconds ago


that's the first part of the report, I can past the rest, just wanted to make sure it is ok to post it.

I am currently running catalina with opencore 6.4 and the corresponding efi from this thread.

Any help appreciated, thanks a lot :)
Click to expand...
Hello @rd3500,
  • Did you make a full bootable backup?
    • If so, how long ago?
    • Have you tried booting from that backup to see if the crash still occurs?
  • Does the crash always occur when running a certain application such as Safari or performing a certain task such as exporting a video?
  • What applications and drivers were installed recently?
  • If you did not make a backup, a good option is to install macOS again from scratch on a spare external SSD, even a cheap 128GB or 256GB SATA SSD.
    • Do not migrate any data after doing the fresh install.
    • Use the same EFI folder that you're using now.
    • Just boot into the fresh copy of macOS and see if the problem occurs. If the problem only happens when using a third-party application, go ahead and install only that application.
As you can see, this is simply a process of elimination. Hopefully hardware is not at fault, but we must rule out software issues first, which is what the above procedure attempts to accomplish.
 
zedoc said:
Looks like F20a BIOS is gone from download page...Hope it's not buggy because I'm on it now :think:
https://www.gigabyte.com/Motherboard/Z490-VISION-D-rev-1x/support#support-dl-bios
Click to expand...
F20a is bad. I suggest to not use it... or if you like living on the edge, to have a usb stick with an earlier bios on it (named “gigabyte.bin” in the root directory) just in case you need to do a flashback.

This broken bios is known to hard crash, and then fail to post, entering into an infinite reboot loop. With the only way to recover is to do a flashback, and pray the process doesn’t fail...

I reported it to gigabyte, I guess others have too, and good that they finally removed it.
 
dehjomz said:
F20a is bad. I suggest to not use it... or if you like living on the edge, to have a usb stick with an earlier bios on it (named “gigabyte.bin” in the root directory) just in case you need to do a flashback.

This broken bios is known to hard crash, and then fail to post, entering into an infinite reboot loop. With the only way to recover is to do a flashback, and pray the process doesn’t fail...

I reported it to gigabyte, I guess others have too, and good that they finally removed it.
Click to expand...

When a new BIOS is released I only flash it to the main BIOS and not the backup one. That way, if anything disastrous happens I can flick the switch on the motherboard and boot from the backup BIOS. It is then easy to flash the previous BIOS file back to the main one.

After a few weeks of use, if everything is running fine, I then flash the backup BIOS.

Better to be safe than sorry.
 
1st Build
Z370 AORUS Ultra Gaming |  i7 8700K |  RX 580 Pulse 8GB
2nd Build
Z390 AORUS MASTER |  i9 9900K |  RX 580 Pulse 8GB
Ploddles said:
When a new BIOS is released I only flash it to the main BIOS and not the backup one. That way, if anything disastrous happens I can flick the switch on the motherboard and boot from the backup BIOS. It is then easy to flash the previous bios file back to the main one.

After a few weeks of use, if everything is running fine, I then flash the backup BIOS.

Better to be safe than sorry.
Click to expand...
Nice!

Vision D has a backup BIOS ? Or is that just a feature on your Z390 board(s)?
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top