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

[CaseySJ]

Anyone?

Please see the highlighted item in Quick Reference spoiler at the top of the Z390 Designare build guide. Simply click on the image below.

 

[johnvid]

Please see the highlighted item in Quick Reference spoiler at the top of the Z390 Designare build guide. Simply click on the image below.

View attachment 506795

Thanks for your advice. But I managed to fix it already.

I did a complete reinstall and in the installation I used my Time Machine backup to restore everything. That worked great and everything is working like it should.

 

[sonolink]

Sorry if this has already been answered elsewhere. Can the motherboard be replaced with a Vision P?
I can't seem to find the Vision D anywhere

Thanks for your help
Cheers
Sono

 

[CaseySJ]

... Can the motherboard be replaced with a Vision P?
...

Do you mean Z490 Vision G (not P)?

 

[RandC]

I have the same three operating systems on my Z490 Vision D, each on its own disk.

• Each disk was formatted with Scheme = GUID Partition Map, which means each disk has its own EFI partition.
  • macOS NVMe SSD with its EFI partition containing OpenCore
  • Windows SATA SSD with its EFI partition containing Microsoft boot loader
  • Ubuntu SATA SSD with its EFI partition containing Ubuntu boot loader
• When I installed Ubuntu, it installed its boot loader to one of the other SSDs (not to its own EFI partition).
  • So I simply moved those files into the EFI partition of the Ubuntu SSD.

Here are the resulting screenshots of the three EFI partitions:

This one is for macOS with OpenCore. It's the one specified in BIOS as Boot Priority #1.
View attachment 506730
This is the EFI partition on the Windows SSD. Note that the Microsoft folder takes precedence. The Windows boot loader is within the "Microsoft" folder:
View attachment 506732
And here is the EFI partition on the Ubuntu SSD. This one is just for Ubuntu. Now OpenCore will automatically detect Ubuntu Linux.
View attachment 506731

In the top level of this partition (not inside the EFI subfolder) I've also copied a file called .VolumeIcon.icns that contains a Linux boot volume icon. If this file exists, OpenCore will use it automatically! I've attached that file (zip) below, but had to remove the leading dot from its name. If you choose to use it, simply copy it to the EFI partition of the Linux SSD, then open Terminal and rename the file: mv VolumeIcon.icns .VolumeIcon.icns. You will, of course, need to "cd" to the correct folder first: cd /Volumes/<name-of-EFI>.

View attachment 506733
Here is the resulting OpenCore Picker menu:

View attachment 506734

Notice the label Kubuntu 20.04? We can specify any disk label of our choosing by creating a file in the EFI/BOOT folder called .disk_label.contentDetails as shown here:

View attachment 506736

Hi Casey,

Thanks for the help with this. You are a Linux guru also! It was mostly successful. I wondered why, after I did a normal Ubuntu install, that my primary Mac OS would not boot. I fixed that with Disk Utility but never looked at the EIF. Ubuntu installed it's EFI on my Mac OS disk. Who would have thought? So I finally figured out that if I don't do a normal Ubuntu install but instead partition the disk myself, on that screen you can change where the EFI partition gets installed to the Ubuntu disk. Did that along with using your icon and naming file. All of that worked perfectly. Here is the issue. Linux will boot from it's disk if I select the disk in BIOS. However if I select the disk in OpenCore I get the following errors:

I've also been downgrading the version of Linux to an earlier version which invoked grub so I don't know if that is the cause of the issue or if there is something else I don't know to get booting from OC to work. Thanks so much for your help. Everything boots, except I have to go to BIOS to boot Linux at the moment.

Rand

 

[CaseySJ]

Hi Casey,

Thanks for the help with this. You are a Linux guru also! It was mostly successful. I wondered why, after I did a normal Ubuntu install, that my primary Mac OS would not boot. I fixed that with Disk Utility but never looked at the EIF. Ubuntu installed it's EFI on my Mac OS disk. Who would have thought? So I finally figured out that if I don't do a normal Ubuntu install but instead partition the disk myself, on that screen you can change where the EFI partition gets installed to the Ubuntu disk. Did that along with using your icon and naming file. All of that worked perfectly. Here is the issue. Linux will boot from it's disk if I select the disk in BIOS. However if I select the disk in OpenCore I get the following errors:

I've also been downgrading the version of Linux to an earlier version which invoked grub so I don't know if that is the cause of the issue or if there is something else I don't know to get booting from OC to work. Thanks so much for your help. Everything boots, except I have to go to BIOS to boot Linux at the moment.

Rand

Some comments and suggestions:

• Linux has the nasty habit of co-installing its EFI into an existing EFI folder. As you discovered, that's why macOS could no longer boot.
• If you don't mind reinstalling Linux once again, I would suggest this procedure:
  • Boot into macOS
  • Run Disk Utility and erase the Linux disk. Format it as follows:
    • Name: Anything appropriate
    • Format: exFAT (don't worry, Linux will change this to ext4)
    • Scheme: GUID Partition Map (this is critical -- this will create EFI partition)
• Then shutdown the system and flip power switch on PSU to OFF.
• Physically disconnect/remove all macOS and Windows SSDs.
• Power up the system and install Linux. Now there will be only one SDD, hence Linux will not corrupt any other EFI partition.
• Then shutdown the system and flip power switch on PSU to OFF once again.
• Reinstall both macOS and Windows SSDs.
• Boot into OpenCore Picker.
• Do you see boot options now for all three operating systems?
• If so, can OpenCore boot Linux properly?

Option 2:
If you post a screenshot of the Linux EFI folder (all directories expanded) I can see if we can quickly fix the problem. No guarantees, but this is simpler than reinstalling Linux.

 

[JDL]

FYI

I have been running the BIOS version F20a since the release without any problems until yesterday.

Then the computer suddenly shut down, like if I pulled the power plug.

I have now flashed back to the BIOS version F7c. Hopefully this will fix it.

 

[bravo030]

Hey CaseySJ,

I report back after two months of using my system, overall I am very happy.

The only thing that bothers me is that the system sometimes does not wake up.

The failed wake up symptoms are: the computer appears to be working (fans are rotating and RGB works too) but there no signal on the monitor. The keyboard does not react either. When I hard restart the system everything works again.

Today I received the following error report (pls see below). Usually there so no report at all - the only difference today that I was using three external USB drives.

- Can you think of any fixes to improve the stability and to eliminate such unreliable wake up?
- Would you recommend to try to upgrade the BIOS (currently at 3a) to try to improve how it works?

As always, very much appreciated!
-------
My specs are:
- iMacPro1,1
- BigSur 11.1
- Z490 Vision D
- RX 5700 XT
- Fenvi T919
- 32 Gb RGB DDR4 Crucial Ballistix
- 2x1TB Sabrent Rocket Q

The error report was:
panic(cpu 0 caller 0xffffff800a7ed0e6): Kernel trap at 0xffffff7fab7f28a8, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000000b0, CR3: 0x000000045225c214, CR4: 0x00000000003626e0
RAX: 0x0000000000000000, RBX: 0xffffff937ab5b300, RCX: 0xffffff86e5558e00, RDX: 0x0000000000000000
RSP: 0xffffffa10a15b9d0, RBP: 0xffffffa10a15ba20, RSI: 0x0000000000000000, RDI: 0xffffff86e5558e00
R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x00000000000000f4, R11: 0x0000000000000080
R12: 0xffffff86e5558e00, R13: 0xffffff9376018500, R14: 0xffffff9376018500, R15: 0xffffff93804f6e00
RFL: 0x0000000000010286, RIP: 0xffffff7fab7f28a8, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00000000000000b0, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0

Backtrace (CPU 0), Frame : Return Address
0xffffffa10a15b3f0 : 0xffffff800a6b9aed mach_kernel : _handle_debugger_trap + 0x3dd
0xffffffa10a15b440 : 0xffffff800a7fc6e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa10a15b480 : 0xffffff800a7ecd1a mach_kernel : _kernel_trap + 0x55a
0xffffffa10a15b4d0 : 0xffffff800a65ea2f mach_kernel : _return_from_trap + 0xff
0xffffffa10a15b4f0 : 0xffffff800a6b938d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa10a15b610 : 0xffffff800a6b9678 mach_kernel : _panic_trap_to_debugger + 0x268
0xffffffa10a15b680 : 0xffffff800aebe3ca mach_kernel : _panic + 0x54
0xffffffa10a15b6f0 : 0xffffff800a7ed0e6 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffa10a15b870 : 0xffffff800a7ecdcd mach_kernel : _kernel_trap + 0x60d
0xffffffa10a15b8c0 : 0xffffff800a65ea2f mach_kernel : _return_from_trap + 0xff
0xffffffa10a15b8e0 : 0xffffff7fab7f28a8 com.apple.filesystems.ntfs : _ntfs_vnop_getattr + 0x339
0xffffffa10a15ba20 : 0xffffff800a978aae mach_kernel : _vnode_getattr + 0xae
0xffffffa10a15baa0 : 0xffffff800a91b204 mach_kernel : _fgetattrlist + 0x6c4
0xffffffa10a15bb80 : 0xffffff800a91ed01 mach_kernel : _getattrlistbulk + 0xb61
0xffffffa10a15bde0 : 0xffffff800a91e8dc mach_kernel : _getattrlistbulk + 0x73c
0xffffffa10a15bf40 : 0xffffff800ad68cdb mach_kernel : _unix_syscall64 + 0x27b
0xffffffa10a15bfa0 : 0xffffff800a65f1f6 mach_kernel : _hndl_unix_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.filesystems.ntfs(3.14.3)[65F52DBE-4603-3AF0-B6BB-A627B2FFE856]@0xffffff7fab7ea000->0xffffff7fab846fff

Process name corresponding to current thread: DesktopServicesHelper
Boot args: keepsyms=1 dart=0 debug=0x100 agdpmod=pikera alcid=11 shikigva=80

Mac OS version:
20C69

Kernel version:
Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64
Kernel UUID: 82E2050C-5936-3D24-AD3B-EC4EC5C09E11
KernelCache slide: 0x000000000a400000
KernelCache base: 0xffffff800a600000
Kernel slide: 0x000000000a410000
Kernel text base: 0xffffff800a610000
__HIB text base: 0xffffff800a500000
System model name: iMacPro1,1 (Mac-xxxxxxxxxxxx)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 117752510154547
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00006b18648a096e
Sleep : 0x0000688a78cc3cb6 0x0000000177c9068a 0x0000687b86a48f32
Wake : 0x0000688ac952a8bd 0x00000001777f0cfa 0x0000688ac33980e2

 

[CaseySJ]

@bravo030,

When troubleshooting such system panics it is always helpful to look for a pattern. For example:

• Looking through the error report, one of the items in the backtrace is "com.apple.filesystems.ntfs". You mentioned that 3 external USB drives were connected.
  • How many were NTFS drives?
  • How many were FAT32 or HFS or APFS?
• Does the wake-from-sleep crash occur if the NTFS drive is not connected?
• What types of USB drives are they?
  • Flash drives?
  • SSDs in USB enclosures?
  • HDDs or SSDs in multi-bay enclosures?

 

[bravo030]

@bravo030,

When troubleshooting such system panics it is always helpful to look for a pattern. For example:

• Looking through the error report, one of the items in the backtrace is "com.apple.filesystems.ntfs". You mentioned that 3 external USB drives were connected.
  • How many were NTFS drives?
  • How many were FAT32 or HFS or APFS?
• Does the wake-from-sleep crash occur if the NTFS drive is not connected?
• What types of USB drives are they?
  • Flash drives?
  • SSDs in USB enclosures?
  • HDDs or SSDs in multi-bay enclosures?

Hi CaseySJ,

That's an interesting question and I need to see if there is an actual pattern somewhere.

The wake-from-sleep crash sometimes also happens where no external drives or other factors are involved - just seemingly out of a clear blue sky.

As for the drives, all three are older HDDs in USB enclosures, all in NTFS formats.

What I cannot understand is why every time there is a crash I cannot see anything on the monitor - in fact it does not wake up at all.

- Any ideas what I could try to resolve?
- You did not respond to my question whether I should upgrade my BIOS (3a) to the newest one- could this fix it?

Thanks again!