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

[dehjomz]

Done that Casey multiple times. I know the EFI folder works, because it boots from the USB drive. I know that Big Sur works because I can boot it from OC booted from the USB drive. I've put the EFI folder from the USB drive in the EFI partition of primary and backup. Nothing else is at root level. I use "EFI Agent" to mount the EFI partitions. It lists the "disk type" of the EFI portion as "EFI" so I am assuming that the partition type is correct. Here is "EFI Agent" display:

View attachment 533837


disk0 is my Windows Sabrent drive
disk1 is my primary Big Sur drive
disk1s1 is the EFI sector on the Big Sur Drive name EFI-SAB-822
disk4 is my Big Sur Backup Hard Drive
disk4s1 is the EFI sector on the Big Sur Backup Hard Drive and contains the same EFI folder as the USB drive.

Below is the contents of EFI-SAB-822 which is a copy of the EFI folder from the USB drive which boots into OCView attachment 533838

So as far as I can tell, everything is correct, yet BIOS doesn't see OC on either drive.

Thanks

Rand

When you formatted the new drive did you use GUID? That adds an EFI partition at the root of the drive and from there you can copy over your OC EFI folder and the boot picker will see the new drive.

 

[RandC]

BIOS checks for these files to determine whether an EFI partition is bootable:

• EFI folder at the root level
• EFI/BOOTfolder
  • BOOTx64.efi located inside the EFI/BOOT folder
• EFI/OCfolder
  • OpenCore.efi located inside the EFI/OC folder

First thing would be to check whether the internal SSD and backup SSD both meet these criteria.

Well found out something new.

i removed the USB drive. When I boot into BIOS with F12 I see the follow as boot devices:

UEFI OS (IP3:ST31000524AS)
UEFI OS (Sabrent)
Widows Boot Manager (Sabrent)
Enter Setup

If I select UEFI OS (IP3:ST31000524AS) I boot into OC (so this must be the Big Sur Backup Hard drive) but not called OpenCore.
If I select UEFI OS (Sabrent) I also boot into OC (so this must be the Big Sur Sabrent drive) but not called OpenCore.
The third drive must be the Windows Drive.

So I guess I can put them into the proper order and booting into OC still works, just not called that.

Assume that this is normal but when I boot the first drive I see:
1. Macintosh HD
2. Macintosh HD Backup
3. Windows
4. EFI-SAB-822 (the EFI partition on the second drive)

and when I boot into the second drive I see:
1. Macintosh HD
2. Macintosh HD Backup
3. Windows
4. EFI (the EFI partition on the first drive)

Anyway, everything does work, I just didn't recognize that those were the OpenCore drives. Don't remember if I didn't try booting from those drives, or reinstalling Big-Sur on both drivers, or removing USB drive enabled me to boot, but it is working. Just not called OpenCore. I can live with that .

Thanks again,

Rand

 

[dehjomz]

Well found out something new.

i removed the USB drive. When I boot into BIOS with F12 I see the follow as boot devices:

UEFI OS (IP3:ST31000524AS)
UEFI OS (Sabrent)
Widows Boot Manager (Sabrent)
Enter Setup

If I select UEFI OS (IP3:ST31000524AS) I boot into OC (so this must be the Big Sur Backup Hard drive) but not called OpenCore.
If I select UEFI OS (Sabrent) I also boot into OC (so this must be the Big Sur Sabrent drive) but not called OpenCore.
The third drive must be the Windows Drive.

So I guess I can put them into the proper order and booting into OC still works, just not called that.

Assume that this is normal but when I boot the first drive I see:
1. Macintosh HD
2. Macintosh HD Backup
3. Windows
4. EFI-SAB-822 (the EFI partition on the second drive)

and when I boot into the second drive I see:
1. Macintosh HD
2. Macintosh HD Backup
3. Windows
4. EFI (the EFI partition on the first drive)

Anyway, everything does work, I just didn't recognize that those were the OpenCore drives. Don't remember if I didn't try booting from those drives, or reinstalling Big-Sur on both drivers, or removing USB drive enabled me to boot, but it is working. Just not called OpenCore. I can live with that .

Thanks again,

Rand

“Opencore” isn’t added to the boot picker for a particular drive until after you’ve loaded OC at least once. Until then it’s UEFI OS*** on gigabyte (or some other name on other motherboards).

 

[RandC]

“Opencore” isn’t added to the boot picker for a particular drive until after you’ve loaded OC at least once. Until then it’s UEFI OS*** on gigabyte (or some other name on other motherboards).

Didn't know that, but I've loaded OC more than once and BIOS still lists it as UEFI OS (Sabrent) and UFEI OS (P3:ST31000524RSI). Maybe if I reset BIOS again and reconfigured it that would change but I think I'll leave things alone for now . This whole exercise started trying to make a backup to upgrade to Monterey.

Thanks @dehjomz

Rand

 

[lightmanrt]

@lightmanrt @haurb900

I also use SoftRaid with two 4-bay external SATA-to-USB enclosures. Will check for any issues with Monterey 12.1 soon. In the meantime, some notes:

• Sabrent Rocket 4.0 can be problematic under heavy load as stated here.
• The OC 0.7.5 EFI is using HfsPlus.efi from Monterey, as also disclosed in the OC 0.7.5 mini-guide. We can always replace it with the same file from OC 0.7.4 EFI folder to see whether it makes any difference during boot.

my system boots from the Sabrent Rocket 4.0 with no problem. Boot from power on to login screen is incredibly fast. Of course now I need to worry about trim. My disk performance issue is related only to Lightroom which accesses the RAID TB 3 enclosure. (RAID 5, SoftRaid 6.2). Right now Lightroom is fine since I am reading from a photo backup drive (8 TB HD) that is in my other TB 3 enclosure.
I will go back go OC 0.74 go see if it resolves anything.

 

[jd6]

has anyone used UGREEN Type C Ethernet Adapter USB C Gigabit Netwerk Adapter Lan RJ45

today I bought this USB adapter but won't work on my Hackintosh Z490 vision g Usb-c port any suggestions ....?

thanks.

---

I get it to work after remapping the USBports , usb-c was deactivated

 

[RandC]

When you formatted the new drive did you use GUID? That adds an EFI partition at the root of the drive and from there you can copy over your OC EFI folder and the boot picker will see the new drive.

Yes @dehjomz both drives have an EFI partition. It is possible that because BIOS didn't show OpenCore as a bootable option, I didn't try to boot the other drives. At least I know that re-installing Big Sur using the recovery drive and then selecting the drive shown by BIOS does indeed boot OC. It is just not called OC. Thanks for your help!

Rand

 

[CaseySJ]

has anyone used UGREEN Type C Ethernet Adapter USB C Gigabit Netwerk Adapter Lan RJ45

today I bought this USB adapter but won't work on my Hackintosh Z490 vision g Usb-c port any suggestions ....?

thanks.

Please post a link to the exact item you ordered so I can add it to a no-go list.

Meanwhile, here's a USB-C to 2.5GbE Ethernet adapter that works exceptionally well:

Gigabyte B550 Vision D (Thunderbolt 3) + AMD Ryzen 7 3700X + AMD RX 5600 XT

@macleap A very informative post. I will have to try your fix for Monterey Ethernet. My configuration is different than yours with an AMD Ryzen 7 3700x and RX 580. Sleep/wake has worked for me with Big Sur and Monterey under BIOS F10. However, CaseySJ had reported that BIOS F10 had problems...

www.tonymacx86.com

 

[CaseySJ]

Didn't know that, but I've loaded OC more than once and BIOS still lists it as UEFI OS (Sabrent) and UFEI OS (P3:ST31000524RSI). Maybe if I reset BIOS again and reconfigured it that would change but I think I'll leave things alone for now . This whole exercise started trying to make a backup to upgrade to Monterey.

Thanks @dehjomz

Rand

As you found out, we can completely disregard the word "OpenCore" in BIOS! It does not matter. Instead, we should look for the names of our actual disks.

 

[RandC]

As you found out, we can completely disregard the word "OpenCore" in BIOS! It does not matter. Instead, we should look for the names of our actual disks.

Thanks Casey!

FYI,

Now that everything is running again I upgraded to Monterey and tested I-255V (Ethernet 2). It does not work for me either. Network tells me the cable is not plugged in, yet the light next to the cable is blinking. I'm running:

BIOS F20
OC 0.7.5
Monterey 12.0.1

Rand