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

[sbushman18]

That is a darn good spot! Easy to miss with the untrained eye!

And just to add ... I haven't seen any "faults" in the correct version of ocvalidate, matched to the booting OpenCore version.


Not so.

I've just run 0.8.7 against the sample.plist ...

View attachment 560937

Simple to double-check ... so the above explanation for the behaviour does not apply.

Must be an error elsewhere, sorry.

Yeah. The error does not show in OCvalidate, only config validator. The latter must be the issue.

 

[jimbojingle]

This is possibly not a question for this forum but I will ask anyway since I have the same system as others.

Since I upgraded my Z490 Vision D to Big Sur and Monterey, I am no longer able to connect to external NAS Servers using the SMB Protocol. This works fine when I boot Windows 11 with all identical connections.

I have checked the IP address as stated in the error.

Any ideas what the cause might be?

 

[CaseySJ]

This is possibly not a question for this forum but I will ask anyway since I have the same system as others.

Since I upgraded my Z490 Vision D to Big Sur and Monterey, I am no longer able to connect to external NAS Servers using the SMB Protocol. This works fine when I boot Windows 11 with all identical connections.

I have checked the IP address as stated in the error.

Any ideas what the cause might be?

This may be a problem with older NAS devices that only support an older version of SMB. Windows continues to support those versions, but macOS only supports the latest.

Is there a firmware update for your NAS? Do you know which version of SMB the NAS supports?

 

[jimbojingle]

This may be a problem with older NAS devices that only support an older version of SMB. Windows continues to support those versions, but macOS only supports the latest.

Is there a firmware update for your NAS? Do you know which version of SMB the NAS supports?

Thanks for your response.

It is an old NAS and has the latest firmware from its time but I have four of them and would like to continue using them if possible as they have been great workhorses. I can upload files to them using Windows which will do if there is no macOS solution.

The model is Xtreamer eTrayz, and it is very old. So I guess it would not support the latest SMB. Is it possible to get macOS to work with an older version of SMB?

 

[bazzevo]

Thanks for your response.

It is an old NAS and has the latest firmware from its time but I have four of them and would like to continue using them if possible as they have been great workhorses. I can upload files to them using Windows which will do if there is no macOS solution.

The model is Xtreamer eTrayz, and it is very old. So I guess it would not support the latest SMB. Is it possible to get macOS to work with an older version of SMB?

I had the same issue with Big Sur using a Drobo 5N. It would randomly drop connection on both Ethernet ports after the upgrade from Catalina. Catalina never had an issue.

 

[grandosegood]

Hi, everyone!

Many thanks to this amazing community, including @CaseySJ for all their help! I recently installed two Samsung 970 EVO Plus into my 10900k/Gigabyte z490 Vision G setup. However, I get constant NVMe kernel panics. I've already switched M.2 slots, ignoring the one closest to the CPU since I don't have PCIe 4 or 11th gen. I also tried several versions of NVMe fix. The panics happen within 5-10 minutes of the system being on. Should I just get rid of the Samsung and go for WD SN750, as it seems to be the part of the trusted hardware for hackintosh NVMe? if not, what would be the recommended brands/models of NVMe SSD (looking for 2TB)? Thanks.

 

[CaseySJ]

Hi, everyone!

Many thanks to this amazing community, including @CaseySJ for all their help! I recently installed two Samsung 970 EVO Plus into my 10900k/Gigabyte z490 Vision G setup. However, I get constant NVMe kernel panics. I've already switched M.2 slots, ignoring the one closest to the CPU since I don't have PCIe 4 or 11th gen. I also tried several versions of NVMe fix. The panics happen within 5-10 minutes of the system being on. Should I just get rid of the Samsung and go for WD SN750, as it seems to be the part of the trusted hardware for hackintosh NVMe? if not, what would be the recommended brands/models of NVMe SSD (looking for 2TB)? Thanks.

Hello @grandosegood

The problem could be related to Ethernet, BIOS version and/or NVMe. If the same system with the same BIOS and same version of macOS has been running successfully for some time, and the only change is the switch from some other brand of SSD to Samsung EVO Plus, then of course the suspicion would fall primarily on the Samsung.

So:

• Has the system been running properly for some time?
• If so, was it using a different NVMe SSD or perhaps a 2.5” SATA SSD instead?
• Has there been a BIOS change?
• If Ethernet cable is disconnected, does the system work properly?

 

[grandosegood]

Hello @grandosegood

The problem could be related to Ethernet, BIOS version and/or NVMe. If the same system with the same BIOS and same version of macOS has been running successfully for some time, and the only change is the switch from some other brand of SSD to Samsung EVO Plus, then of course the suspicion would fall primarily on the Samsung.

So:

• Has the system been running properly for some time?
• If so, was it using a different NVMe SSD or perhaps a 2.5” SATA SSD instead?
• Has there been a BIOS change?
• If Ethernet cable is disconnected, does the system work properly?

Thanks for the quick reply @CaseySJ.

I recently migrated from an Asus z490 E board to a Gigabyte z490 vision G (BIOS ver F6) to get better Thunderbolt compatibility. I am re-using all other parts (10900K, 2 x 32GB DDR4 RAM with XMP on, Radeon VII, 2 x Samsung 970 EVO Plus).

I previously dual-booted Win10 and Big Sur without issue. I followed the Dortania guide to get everything working, but keep getting these NVMe panics. I will be picking up an sn750 tomorrow to test. I haven't tested with Ethernet disconnected, but I will try that. I'm using the device properties Comet Lake guide from Dortania, so I don't think that could be causing it. The Samsungs are also on the latest firmware, but I'm wondering if the latest version of Big Sur/OpenCore/NVMe fix have revealed yet another reason to ditch the Samsungs. Kind of a bummer because I always thought they were the gold standard for reliability.

 

[BYOH]

Hi, everyone!

For more than 2 years I had a very stable system (10700K, 32GB, RX570), dual boot with Big Sur and Win10. Suddenly I had random freezes on both OS. Well, the journey of finding the reason started with swapping different components. I even had the mainboard checked by Gigabyte with no result. They returned it to me with BIOS F21.
After several attempts I found the problem - it was the 10700K! Intel was so kind to replace it and I had to do a fresh install for the Mac OS (Win still worked).

Now I have OpenCore 0.7.8 with Monterey. I don't need all features running, so I am fine with how it works.
But! There is a problem when I leave the computer unused for a while. It starts to do so many reads on the NVME so that the system slows down. Beachball appears and it's hard to work with the system.

I don't have any idea where the reason for the problem is. If somebody had the same issue and could fix it - I would appreciated some info.

Best regards

 

[CaseySJ]

Hi, everyone!

For more than 2 years I had a very stable system (10700K, 32GB, RX570), dual boot with Big Sur and Win10. Suddenly I had random freezes on both OS. Well, the journey of finding the reason started with swapping different components. I even had the mainboard checked by Gigabyte with no result. They returned it to me with BIOS F21.
After several attempts I found the problem - it was the 10700K! Intel was so kind to replace it and I had to do a fresh install for the Mac OS (Win still worked).

Now I have OpenCore 0.7.8 with Monterey. I don't need all features running, so I am fine with how it works.
But! There is a problem when I leave the computer unused for a while. It starts to do so many reads on the NVME so that the system slows down. Beachball appears and it's hard to work with the system.

I don't have any idea where the reason for the problem is. If somebody had the same issue and could fix it - I would appreciated some info.

Best regards

Hello @BYOH

Early versions of Monterey had a problem with “mediaanalysisd” that analyzes photos for faces and other attributes, and tags them accordingly. But if you’re using latest version of Monterey you should be fine.

However, BIOS F21 is something to avoid. If you see the top of Post 1 just under the photo, you’ll see that only F5, F6, and F20 are recommended.