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

[CaseySJ]

Comparing my pictures to another found on the web, I find that I'm missing a tiny component :


Here is the missing component that I may have ripped of the board while placing the clamp :

Ouch!

It may be necessary to take the board to a local repair shop where experienced technicians can determine exactly which component needs to be soldered, and they can solder it.

This is not something to be done by an inexperienced person (even I messed up with a PCIe Thunderbolt card).

 

[pm974]

Ouch!

It may be necessary to take the board to a local repair shop where experienced technicians can determine exactly which component needs to be soldered, and they can solder it.

This is not something to be done by an experienced person (even I messed up with a PCIe Thunderbolt card).

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.

 

[Higgie]

Can you post screenshot of the custom entry?

@Inqnuam -- FYI.

Here is my custom entry before updating OpenCore, note commas and parentheses:

I then right-click and Update in the HackinDROM App, and the new config.plist looks like this:

There is a Windows option in the boot picker, but it won't boot anything because the path is incorrect. This caused me a headache for weeks as I just didn't realise the commas and parentheses had been omitted. As far as I could tell, the entry had been carried over to the new config.plist. It was only when I decided to do a new Windows entry from scratch I got it working again - only for it to be broken again when I upgraded to the latest OC yesterday. That's when I compared the old config.plist and saw what was happening.

 

[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

That looks perfectly fine. AIO is connected to power supply AIO is connected to ARGB header on motherboard No USB connection @Lensjocky reported a similar issue with his Gigabyte Z490 Vision D. After replacing an AMD Vega GPU with Sapphire Pulse AMD Radeon RX 6800 XT, his system no longer...

www.tonymacx86.com