Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

mdog474 said:
Hi @CaseySJ My ID was originally 0300913E. I tried 07009B3E and 0300983E and neither one worked.
I have my machine starting up, but the Ultrafine 5K is seen on the thunderbolt bus, but not as a display (the audio on the monitor works). The Pro Display XDR does not show up on the TB3 bus at all. Any ideas of what else to try? I've also tried the Belkin displayport to thunderbolt VR cable. No luck. What is working is dual displayport to a 5K monitor with dual DisplayPort inputs. These are the boot-args I'm using: slide=0 alcid=7 darkwake=0 shikigva=80 agdpmod=pikera
Is there a BIOS option I should be setting to enable DisplayPort in to TB3?
Any ideas what to try next?
Click to expand...
You won't like this answer, but alas there's nothing else I can suggest. I have been discouraging the use of Thunderbolt monitors for a few weeks now due to these and similar intractable problems.
 
CaseySJ said:
@mishar,

There's no harm installing NVM23, 43, or 50 on the GC-TR v1.0. We need to flash only the blue-dot chip. The TI PD firmware is independent of the Thunderbolt firmware so no need to worry about that.
Click to expand...
I will certainly try that then! Thank you
CaseySJ said:
As you sure the Asus X299 Prime Deluxe II contains a Titan Ridge controller instead of Alpine Ridge? Hackintool's PCIe tab will give you the answer. We cannot activate a Titan Ridge controller through SSDT alone, but most (not all) Alpine Ridge controllers can be activated this way. But even then there's no guarantee that it will perform adequately. We've found that flashing the controller tends to provide better overall results.
Click to expand...
I'm pretty sure it's a Titan Ridge controller. It's listed as a 15eb Controller device in the Device Manager in windows.


I don't have direct access to the motherboard right now, as I sent it out to ASUS to see if they could figure out what was going on. (Posted in this thread about initial findings: https://www.tonymacx86.com/threads/asus-x-299-deluxe-ii-thunderbolt-solution.267392/post-2180513)
I did not try and read the firmware chip yet either, but certainly will try now when I get it back.

I just noticed @liufei added some notes about the tps65988 multiplexer that seems to be at the heart of what might be going on with that motherboards thunderbolt implementation.

www.tonymacx86.com

ASUS X-299 Deluxe II - Thunderbolt Solution?

Thanks @dez! I have since run a few more tests and figured out that hot-plug only seems to be working on Port 1 for Thunderbolt devices in Windows 10 as well. Behaviour for Port 2 (closest to PCIe slots) is similar to the USB-C in that it only works when cold booted but if device is removed...
www.tonymacx86.com www.tonymacx86.com

It seems to have something to do with the Power Delivery system there.

The GC Titan Ridge cards were definitely a lot easier to get working than the onboard one. I could not get hot plug working at all with the onboard.

If there is a way to flash the onboard thunderbolt controller on this board, that would be fantastic! I'm pretty happy with everything else about it. I think it's been a somewhat popular board in the hackintosh community.
 
Last edited:
Just bought a new monitor for my hackintosh and I have a problem with the detected screen resolution.

Although everything looked fine at the beginning, I noticed that the text on websites for example is much more clear when using Windows so I started to investigate and here is a problem that I found:

To begin with, I am using a Samsung C43J89x 3840 × 1200 monitor and here are my settings:

Screenshot 2020-12-10 at 01.12.24.png


Everything looks fine but when I go to System Report it detects that my monitor resolution is 7680x2400 as you can see in the screenshot below:

Screenshot 2020-12-10 at 01.13.32.png


From what I understand by discovering this, MacOS is rendering everything at 7680x2400 and it's scaling it down to 3840x1200. Any idea about how can I fix this?

Here is more information about my system if needed:

Screenshot 2020-12-10 at 01.15.28.png

Screenshot 2020-12-10 at 01.15.33.png
 
andrai886 said:
Just bought a new monitor for my hackintosh and I have a problem with the detected screen resolution.

Although everything looked fine at the beginning, I noticed that the text on websites for example is much more clear when using Windows so I started to investigate and here is a problem that I found:
Click to expand...
---
andrai886 said:
From what I understand by discovering this, MacOS is rendering everything at 7680x2400 and it's scaling it down to 3840x1200. Any idea about how can I fix this?
Click to expand...
In the past I solved some resolution problems with my monitor using a great app called SwitchResX. You can try it out. Hope it works
 
ummario said:
---

In the past I solved some resolution problems with my monitor using a great app called SwitchResX. You can try it out. Hope it works
Click to expand...
Thank you! It solved my problem. Used SwitchResX to change to the exact same resolution without HiDPI.
 
Maybe I am wrong, but I feel like my system must need to configuration work. I am trying to import footage for a video clip I am working on. I have not even started editing yet. After finishing importing and naming all the clips, final cut begins transcoding. My fans on the GPU and CPU are running and this is what activity monitor is showing.

Screen Shot 2020-12-10 at 1.02.47 AM.png
 
Hi There! Thanks everyone for this wonderful thread and especial CaseySJ!
In am on Big Sure with OpenCore 0.6.3 on this hardware and I would like to edit the root filesystem. I posting here to see if anyone else has seen this on their hack.

I followed Mount root as writable in Big Sur on stackexchange and I disable authenticated-root on recovery and then mount the partition as rw edit it and try to create a snapshot and make it bootable by using bless and end up with the error:

Bash: 
~ $ df .
Filesystem     1K-blocks      Used Available Use% Mounted on
/dev/disk2s5s1 976557744 269283980 689455292  29% /
~ $ mkdir ~/xxx
~ $ sudo mount -o nobrowse -t apfs /dev/disk2s5 ~/xxx
~ $ cd xxx
~/xxx $ ls
Applications  Desktop    Library  Users    bin    data  etc  private  tmp  var
System   Volumes  cores  dev   opt  sbin     usr  xarts
~/xxx $ touch test
~/xxx $ sudo bless --folder /Users/user/xxx/System/Library/CoreServices --bootefi --create-snapshot
Couldn't copy file "/Users/user/xxx/System/Library/CoreServices/boot.efi.j137ap.im4m" - Error Domain=NSCocoaErrorDomain Code=513 "“boot.efi.j137ap.im4m” couldn’t be copied because you don’t have permission to access “CoreServices”." UserInfo={NSSourceFilePathErrorKey=/System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j137ap.im4m, NSUserStringVariant=(
    Copy
), NSDestinationFilePath=/Users/user/xxx/System/Library/CoreServices/boot.efi.j137ap.im4m, NSFilePath=/System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j137ap.im4m, NSUnderlyingError=0x7fda23f05dd0 {Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"}}
Can't copy img4 manifests for file /Users/user/xxx/System/Library/CoreServices/boot.efi
~/xxx $ ls -la /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi*
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j132ap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j137ap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j140aap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j140kap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j152fap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j160ap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j174ap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j185ap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j185fap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j213ap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j214kap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j215ap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j223ap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j230kap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j680ap.im4m
-rw-r--r-- 1 user staff 3626 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.j780ap.im4m
-rw-r--r-- 1 user staff 3627 Nov  7 04:57 /System/Volumes/Preboot/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/usr/standalone/i386/boot.efi.x86legacyap.im4m


Since this did not work I created the apfs snapshot manually and then boot from that based on this egpu.io thread.

Bash: 
~ $ df .
Filesystem     1K-blocks      Used Available Use% Mounted on
/dev/disk2s5s1 976557744 269283980 689455292  29% /
~ $ mkdir ~/xxx
~ $ sudo mount -o nobrowse -t apfs /dev/disk2s5 ~/xxx
~ $ cd xxx
~/xxx $ ls
Applications  Desktop    Library  Users    bin    data  etc  private  tmp  var
System   Volumes  cores  dev   opt  sbin     usr  xarts
~/xxx $ touch test
# Create snapshot.
~/ $ sudo /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -s "ChangedRoot" -v /Users/users/xxx
# Tag snapshot for next boot.
~/ $ sudo /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -r "ChangedRoot" -v /Users/xxx/mount
$ diskutil apfs snapshots disk2s5s1
Snapshots for disk2s5s1 (3 found)
|
+-- yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy
|   Name:        com.apple.os.update-yyyyyyy.....yyyyyy
|   XID:         489684
|   Purgeable:   No
|   NOTE:        This snapshot limits the minimum size of APFS Container disk2
|
+-- xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
   Name:        ChangedRoot
   XID:         490985
   Purgeable:   Yes


So by doing this I am worried that I will not be able to update my system when a new update comes out. Also it seems that I cannot really delete those snapshots which translates that every time I want to make a change on the filesystem I need to add a new snapshot.

Anyone facing the same issue? Any help or direction?

Thanks!
 
CaseySJ said:
Some questions:
  • With which previous configuration did the monitor work on boot?
    • Catalina with Clover?
    • Catalina with OpenCore?
  • Is it a Thunderbolt monitor?
  • If not, what is the make/model of the monitor?
Click to expand...
Click to expand...

Hi Casey

Yes Catalina with Clover was working fine.

The current test Monitor is a basic DELL SE2219H Display - can only connect via HDMI.

I am currently trying to source a new 49" Ultrawide which will then connect via DisplayPort.

However must be something to do with OpenCore / BigSur - as all worked fine on Catalina/Clover.
 
@CaseySJ I read and re-read the raspberry pi guide several times to make sure I got everything correct. BUT I had a bit of a scare tonight and I wanted to see if you could help me.
I was originally going to set up my cables from GPIO to the SOI clip as per your original instructions, but then followed the instructions for the supplemental procedure since that is what was recommended. However, in the "run
Code: 
flashrom
as shown below" step it says "it should not work, but it should partially detect the chip." But my situation was different. I was able to read and backup the chip as though I had already done the "connect power cable to the Designare PSU..." steps. In fact I ran the backup 3x as dictated, ran checksum and they all matched. I tried the next steps of turning on the power on the PSU, but then it was NOT able to read the chip. So I shutdown the pi, removed the power cable from the PSU again, and tried a second time. I was again able to read the backup, so I decided to go ahead with the final step of writing the modified flash. That was when things went south. It failed on the erase and write,
Code: 
flashrom
kept trying with "a different method of erase" and it seemed to have left my TB3 chip in an unknown state. I was so nervous that I completely bricked my new motherboard, but it boots up in Big Sur just fine, although the system lists 'unknown' next to firmware version. I haven't dared try, but I would imagine that I just broke Thunderbolt? All of the guides show what it SHOULD look like when it's successful but what do I do now that it isn't? I tried setting up my wiring as per the original instructions rather than the supplemental variation, and now it can't recognize the chip at all. Is there any hope to write the modified or restore from my backups?
 
GA-X99P-SLI - i7-6850K - RX 5600XT
GA-X99P-SLI |  i7 Other |  Radeon Nitro+ RX 5700 XT 8GB
B550 Vision D - Ryzen 3950X - Radeon RX 5700XT
Other |  Xeon W3680 |  Radeon RX 5700 XT OC 8GB
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top