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

[drumattacks]

I totally agree. Looking at the size of this chip, there is no doubt I'll do more harm than anything.
Thank's anyway it's always good to share.

For some solidarity - I too must have knocked off a small nearby cap when flashing. Had a ton of trouble fighting with the super strong spring on the SOIC clip. Eventually got the chip read and flashed but my Thunderbolt sys report looked identical to yours. No power to TB ports from then on. Just had to go expansion card for now

 

[Inqnuam]

Can you post screenshot of the custom entry?

@Inqnuam -- FYI.

I guess the issue is caused by this declaration which is applied for "Path" here
This is useful to fix borked oc entries.
Previously I used to filter by printable ASCII characters (as documented in OC source code, like for "Comment" entry ) but it caused some issues, (difference between Swift and C ascii ??).
I can add comma "," into valid characters, hopping it will not have side effects

EDIT:
same for parentheses ( )

EDIT 2:
here's the fixe
https://github.com/Inqnuam/HackinDROM/releases/tag/v2.1.5

 

[Higgie]

I guess the issue is caused by this declaration which is applied for "Path" here
This is useful to fix borked oc entries.
Previously I used to filter by printable ASCII characters (as documented in OC source code, like for "Comment" entry ) but it caused some issues, (difference between Swift and C ascii ??).
I can add comma "," into valid characters, hopping it will not have side effects

EDIT:
same for parentheses ( )

EDIT 2:
here's the fixe
https://github.com/Inqnuam/HackinDROM/releases/tag/v2.1.5

Works perfectly. Thank you very much for fixing it so quickly!

Now to try and rectify this TB3 Hot Plug issue!

 

[mickelsn]

OK, random question which I haven't seen it answered anywhere, yet, and can't seem to find it via search.

When I set up my hack, I included dual-boot to Windows 10 Pro with a separate NVMe SSD in the first slot as recommended here. I don't use it often, but time and again I do use it so I've been thinking about upgrading to Windows 11.

So the question is this -- is it safe to run the Windows 11 upgrade process in place on the drive as-is without disturbing my macOS partition and its EFI directory? Or do I need to hassle with opening the unit and physically disconnecting the macOS SSD from its NVMe slot to be safe?

Appreciate any real-world experience on this one...

 

[CaseySJ]

OK, random question which I haven't seen it answered anywhere, yet, and can't seem to find it via search.

When I set up my hack, I included dual-boot to Windows 10 Pro with a separate NVMe SSD in the first slot as recommended here. I don't use it often, but time and again I do use it so I've been thinking about upgrading to Windows 11.

So the question is this -- is it safe to run the Windows 11 upgrade process in place on the drive as-is without disturbing my macOS partition and its EFI directory? Or do I need to hassle with opening the unit and physically disconnecting the macOS SSD from its NVMe slot to be safe?

Appreciate any real-world experience on this one...

I have done numerous Windows 11 updates on multi boot systems without any problem. Windows 11 is much better behaved than Windows 10.

 

[abc1mce2]

I have a problem. I have a very good working Z490 Vision D Catalina 10.15.7 Hackintosh system. My problem is after I upgraded to Monterey 12.6.3 my (Intel wifi) Bluetooth is not working. It's grayed out and I just don't know why.
I backed up my system on an external drive with CCC before the upgrade, but I really want to get this 12.6.3 Bluetooth working.

 

[CaseySJ]

I have a problem. I have a very good working Z490 Vision D Catalina 10.15.7 Hackintosh system. My problem is after I upgraded to Monterey 12.6.3 my (Intel wifi) Bluetooth is not working. It's grayed out and I just don't know why.
I backed up my system on an external drive with CCC before the upgrade, but I really want to get this 12.6.3 Bluetooth working.

Please see this post:

Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

@CaseySJ Another data point -- Gigabyte Z690 Aero G DDR4 with a Sapphire RX 6800 XT sleeps without problem. I recently replaced the RX 580 used with this board with the RX 6800 XT. I did clear the CMOS and reset BIOS as @HenryM suggested above. When booting at about 1/3 through the Apple...

www.tonymacx86.com

 

[abc1mce2]

Thanks again CaseySJ. For some reason, after I only added the kexts and rebooted, Bluetooth is working again.
Appreciate your help as always.

 

[emistral]

@CaseySJ Hi there, not sure if it is the right forum but recently (this happened after an opencore update from 0.8.3 to 0.8.5 from memory) when clicking on any of the macos icons (for instance bluetooth, wifi, user, etc.) in the toolbar at the top of the screen on the right hand side, the menu is displayed on the left hand side. This happens only when clicking Macos icon. I have other icons in my toolbar such as parallel toolbox, cleanmymac, switchresx, one drive, etc. and those ones work properly (the menu is displayed underneath the mouse cursor when I select those icons). Any idea what could be the cause? It is weird and started only after an opencore update. For info I always reset the nvram at the first reboot after upgrading to a new OC version.

 

[CaseySJ]

@CaseySJ Hi there, not sure if it is the right forum but recently (this happened after an opencore update from 0.8.3 to 0.8.5 from memory) when clicking on any of the macos icons (for instance bluetooth, wifi, user, etc.) in the toolbar at the top of the screen on the right hand side, the menu is displayed on the left hand side. This happens only when clicking Macos icon. I have other icons in my toolbar such as parallel toolbox, cleanmymac, switchresx, one drive, etc. and those ones work properly (the menu is displayed underneath the mouse cursor when I select those icons). Any idea what could be the cause? It is weird and started only after an opencore update. For info I always reset the nvram at the first reboot after upgrading to a new OC version.

Hello @emistral,

Can you post a screenshot of the problem?

OpenCore is most likely not responsible. One can always go back to previous version of OpenCore. If OpenCore was updated using HackinDROM, then the previous EFI folder is zipped and backed-up in the EFI partition.