search

cstrouse / Dell-PowerEdge-T30-Hackintosh

OpenCore and Clover EFI folders for a Dell PowerEdge T30/Precision T3620 hackintosh running macOS Catalina 10.15.7 and Big Sur 11.4.
BSD 2-Clause "Simplified" License
25 stars 4 forks source link

CPU name and wake up issues #5

Open ptHpmN opened 3 years ago

ptHpmN commented 3 years ago

Hi, I preciated for your project here, it help me force the T30 ran a smooth Big Sur. I got the issues as following:

Wrong CPU name (not as your mac about photo) Screen Shot 2021-08-05 at 1 47 11 PM

one more issue is when the CPU sleep over an hour, I can wake it up by mouse or keyboard, but it run in black ground only, there is no signal to wake the monitor up (the Dell U2417H)

swanduron commented 3 years ago

Hello Bro, do you follow the poster's guide to use the setup_var command in the UEFI loader? In my experience, most possibilities of "the death of waking up" is related to the wrong configuration around "Set DVMT pre-alloc to 64MB (or greater)".

Or there is another easier solution is, buy an RX570 card, this is my way to kick off the wake issue forever.

Return your first question about wrong CPU information, it's nothing to do with any function. My CPU is E3 1225v5, anything works fine.

WX20210814-064413@2x

At the ending of the post, very thanks for the original poster "cstrouse" and his work on T30/T3620 platform in BigSur. Thanks.

ptHpmN commented 3 years ago

Hi swanduron, Thanks for your comments. I followed step by step with UEFI modify for sure, but as a remind that it happen if sleep over an hour only. The Big Sur was backed to operation but no signal for monitor, it means the Mac OS has been waked up already. Anyway, T30 can have smooth run, I will try to get the RX graphic card and test later. Thanks

cstrouse commented 3 years ago

@ptHpmN Skylake chipsets tend to have ongoing issues with sleep as well as with waking of external displays. I never really had problems with display wake with either of the LG 4k monitors I have. If you're using the config.plist provided in this repo without modifying the device properties for your iGPU then you just need to follow the guide in the WhateverGreen repo for patching Intel framebuffers. Apologies if I misunderstood and you are using the same Xeon as I but it sounds like you've installed a different CPU and need to adjust your iGPU device properties.

If the issue is with HDMI rather than DP make sure you include igfxonln=1 in your boot args as that fixes HDMI-related display wake problems. Of course, you'll still probably want to go through what I suggest below and make sure you're using the right IDs including a device-id spoof if necessary.

Xeon CPUs in the E3 series which end in 5 have an iGPU based on a mobile variant of a similar design. I recommend researching the differences between your CPU and the E3 1225 v5 Xeon that I have installed focusing on the iGPUs. Compare the two to one another carefully and then also compare to other Skylake iGPUs. You'll probably find that your chip shares more in terms of clock speeds, core count, memory, cache, etc, and most importantly how it is physically wired to the display outputs on the motherboard and GPU power management settings.x

I went through a bunch of the chips on Intel's ARK and found that the recommendation in the Dortania guide was not necessarily the correct option since I have the P530 variant rather than the HD530. ARK will list the iGPU device ID and if you switch the following lines to more appropriate values display wake problems should become a rarity. It also seems to matter which DP port you use to connect your monitor with the port at the top being the best to use. I also recommend using a high-quality, well-shielded cable that's rated for 4k@60Hz if possible.

iGPU WhateverGreen patching
  1. Make sure you have the right value for AAPL,ig-platform-id.
  2. If your iGPU does not have the same ID according to ARK as a CPU that Apple actually shipped in the iMac you may need to use another ID as I did.
  3. If you're not using a 4k display via DP then you should remove this entry.

@swanduron has the same CPU in his build as I do and a dGPU so all he needed to get things rock solid was adjust the preallocated shared memory to be at least 64MB. Intel did mention a problem related to graphics instability when exiting C8 power states and deeper in their product update erratum and labeled it as "won't fix" so if you end up not resolving it with the boot arg and device property changes try a dGPU like the RX 570 or 580. The graphics power state transition issue is on page 32 beneath the heading "SKW63".