Mobile Icelake issues

[MVDB0110]

After some Troubleshooting I got rid of most of the ACPI errors by adding compiled SSDTs. And came further in the boot process. Now I hang at Still Waiting for Root Device. Now I think the problem has to do with USB, because this laptop uses only USB-C/Thunderbolt, which are initialized but still I get the error Waiting for Root Device. Also I get the error of appleusbxhci unsupported speed mantissa.
I get ACPI error: _SB.PCI0.XHC.RHUB.HS09 is in DSDT but cannot be loaded on boot (I'm still in install phase).
For current EFI and photos of the error https://www.tonymacx86.com/threads/will-macos-run-on-the-xps-13-7390.285414/page-2#post-2123507

[khronokernel]

Yeah somewhat known issue with Icelake, had a user hit that roadblock a while back but disappeared before we could get a fix. So my guess are either:

• USBInjectAll failing with newer SMBIOS
  • may need to try an older SMBIOS and see, iirc MacBookAir8,1 should be supported
• Apple's XHCI drivers aren't matching with yours
  • If you can get the PCI ID of your XHCI controller(can find it in windows), I could make a quick kext to shove support in

Also issues tab is for guide issues and not personal hack issues, I'm throwing in this issue as "fix Icelake guide" as the Icelake platform has issues that need to be resolved but for future reference these kinds of issues should be in forums only

[MVDB0110]

Okay first ill try the InjectAll way and then I will make an USB Map and share with other XPS owners.

[MVDB0110]

The older SMBIOS MacBookAir8,1 isn't changing anything. My XHCI Controller dortania/vanilla-laptop-guide#1 is "\VEN_8086&DEV_34ED&SUBSYS_08B01028&REV_30\3&11583659&0&A0" dortania/vanilla-laptop-guide#2 is "\VEN_8086&DEV_8A13&SUBSYS_00000000&REV_03\3&11583659&0&68". You are my hero if you can make that kext for me.

[khronokernel]

Try this guy:

• IcelakeFixup-1.kext.zip

Edit: It's a plist-only kext, so no executable is needed when adding to your config.plist

[MVDB0110]

I have tried the kext. It did not boot up and got the same Still waiting for root device error. When I imported the kext in to config.plist it got no ExecutablePath is that the way it should be?

[khronokernel]

Hmm, only other thing that could affect USB off the top of my head is IRQ conflicts. Try running SSDTime's HEPT/IRQ patcher

[MVDB0110]

It still won't pass the Still waiting for root device. The SSDTime patcher output is here: http://www.mediafire.com/file/836jgn0bg5hr2kh/patches_OC.zip/file

[MVDB0110]

Maybe the OpenCore log helps:
00:000 00:000 AAPL: [EB|#LOG:INIT] 2020-05-17T21:33:31 00:117 00:117 AAPL: [EB|#VERSION] bootbase.efi 422.100.16~14 (Official), built 2020-02-29T16:54:28-0800 00:226 00:108 AAPL: [EB|#BUILD] BUILD-INFO[310]:{"DisplayName":"bootbase.efi","DisplayVersion":"422.100.16~14","RecordUuid":"0D6170BC-EA81-4EE7-B3B5-1D6A5DDB253B","BuildTime":"2020-02-29T16:54:28-0800","ProjectName":"efiboot","ProductName":"bootbase.efi","SourceVersion":"422.100.16","BuildVersion":"14","BuildConfiguration":"Release","BuildType":"Official"} 00:340 00:113 AAPL: [EB|H:IS] Err(0xE) @ GV boot-signature
00:446 00:106 AAPL: [EB|H:IS] Err(0xE) @ GV boot-image-key 00:554 00:107 AAPL: [EB|#H:IS] 0 00:670 00:116 AAPL: [EB|#WL:MODE] 0 00:782 00:111 AAPL: [EB|#CONFIG:SRC] <default> 00:890 00:108 AAPL: [EB|#CONFIG| 0] boot-save-log : 0x0000000000000002 (0x0000000000000002 < 0xFFFFFFFFFFFFFFFF) <default> 00:998 00:108 AAPL: [EB|#CONFIG| 1] wake-save-log : 0x0000000000000002 (0x0000000000000002 < 0x0000000000000002) <default> 01:109 00:111 AAPL: [EB|#CONFIG| 2] console : 0x0000000000000001 (0x0000000000000001 < 0x0000000000000001) <default> 01:215 00:105 AAPL: [EB|#CONFIG| 3] serial : 0x0000000000000000 (0x0000000000000000 < 0x0000000000000000) <default> 02:287 01:072 AAPL: [EB|#CONFIG| 4] embed-log-dt : 0x0000000000000000 (0x0000000000000000 < 0x0000000000000000) <default> 02:398 00:111 AAPL: [EB|#CONFIG| 5] timestamps : 0x0000000000000000 (0x0000000000000000 < 0xFFFFFFFFFFFFFFFF) <default> 02:506 00:107 AAPL: [EB|#CONFIG| 6] log-level : 0x0000000000000001 (0x0000000000000001 & 0x0000000000000001) <default> 02:614 00:108 AAPL: [EB|#CONFIG| 7] breakpoint : 0x0000000000000000 (0x0000000000000000 & 0x0000000000000000) <default> 02:723 00:108 AAPL: [EB|#CONFIG| 8] kc-read-size : 0x0000000000100000 (0x0000000000100000 < 0xFFFFFFFFFFFFFFFF) <default> 02:835 00:111 AAPL: [EB|#WL|0] 0x01 0x01 0 0x00 02:941 00:106 AAPL: [EB|#BRD:NV] Mac-827FAC58A8FDFA22 03:051 00:110 AAPL: [EB|#WL|1] 0x01 0x01 2 0x00 03:161 00:109 AAPL: [EB|BST:IDT] {
03:267 00:106 AAPL: [EB|BST:IDT] } 03:375 00:108 AAPL: [EB|#WL|2] 0x01 0x01 3 0x00 03:484 00:108 AAPL: [EB|#WL|3] 0x01 0x01 4 0x00 03:595 00:111 AAPL: [EB|#BRD:NV] Mac-827FAC58A8FDFA22 04:675 01:079 AAPL: [EB|#WL|4] 0x01 0x01 5 0x00 04:782 00:107 AAPL: [EB|H:CHK] BM: 0x0000000000000000
04:894 00:111 AAPL: [EB|H:CHK] Err(0xE) @ GV boot-signature 05:000 00:105 AAPL: [EB|#WL|5] 0x01 0x01 23 0x0E 05:109 00:108 AAPL: [EB|H:CPM] Err(0xE), (24, 24) @ GV Persistent-memory-note
05:219 00:110 AAPL: [EB|SB:EN] Err(0xE) @ LocP 24B73556-2197-4702-82A8-3E1337DAFBF2 05:333 00:113 AAPL: [EB|#LIMG:DP] Acpi(PNP0A03,0)/Pci(14|0)/Usb(8, 0)/HD(Part2,Sig11259E18) 05:448 00:115 AAPL: [EB|#LIMG:FP] \System\Library\CoreServices\boot.efi 05:554 00:105 AAPL: [EB|#LIMG:OPT] () 05:673 00:119 AAPL: [EB|#RPS] R?0 P?0 S?0 05:790 00:116 AAPL: [EB|OPT:LXF] 'LF (\System\Library\CoreServices\com.apple.Boot.plist)
05:898 00:108 AAPL: [EB|LD:LF] FIO: 0, DIR: 1, P: \\System\\Library\\CoreServices\\com.apple.Boot.plist, DP: 0 06:982 01:083 AAPL: [EB|LD:OFS] Err(0xE) @ OPEN (\System\Library\CoreServices\com.apple.Boot.plist)
07:087 00:104 AAPL: [EB|OPT:LXF] Err(0xE) @ 'LF 07:195 00:108 AAPL: [EB|OPT:LXF] 'LF (Library\Preferences\SystemConfiguration\com.apple.Boot.plist)
07:307 00:111 AAPL: [EB|LD:LF] FIO: 0, DIR: 1, P: Library\\Preferences\\SystemConfiguration\\com.apple.Boot.plist, DP: 0 07:435 00:128 AAPL: [EB:#KF] () 07:540 00:105 AAPL: [EB|#MBA:CL] () 07:654 00:113 AAPL: [EB|#MBA:NV] (-v keepsyms=1 debug=0x100 alcid=1) 07:763 00:109 AAPL: [EB|#MBA:KF] () 07:868 00:105 AAPL: [EB|#MBA:OUT] (-v keepsyms=1 debug=0x100 alcid=1) 07:977 00:108 AAPL: [EB|#LOG:VERBOSE] 2020-05-17T21:33:39 08:102 00:125 AAPL: [EB|#RBFU] F: 15 U: 0x0000000000008000 08:211 00:108 AAPL: [EB|#OPT:BM] 0x24083 08:318 00:106 AAPL: [EB|OPT:LXF] 'LF (\System\Library\CoreServices\PlatformSupport.plist)
09:403 01:085 AAPL: [EB|LD:LF] FIO: 0, DIR: 1, P: \\System\\Library\\CoreServices\\PlatformSupport.plist, DP: 0 09:545 00:142 AAPL: [EB|#B:VAw] 09:652 00:107 AAPL: [EB|CS:CSKSD] {
09:760 00:108 AAPL: [EB|CS:CSKSD] Err(0xE) @ GV 8D63D4FE-BD3C-4AAD-881D-86FD974BC1DF:boot-info-payload 09:866 00:105 AAPL: [EB|G:CS] } Ok(0)
09:971 00:105 AAPL: [EB|LD:LF] FIO: 0, DIR: 1, P: <null string>, DP: 1 10:136 00:164 AAPL: [EB|B:SBS] SZ: 617016
10:247 00:111 AAPL: [EB|#B:SHA] fe9e48a334db5bca8b8d8f3d0aa3f18b7dc5ad24
10:351 00:103 AAPL: [EB|WL:PWLFNV] Err(0x5) @ GV wake-failure 10:455 00:104 AAPL: [EB|WL:DT] Err(0x5) @ WL:PWLFNV
10:560 00:105 AAPL: [EB|LD:LKC] BM:R -> (System\Library\PrelinkedKernels\prelinkedkernel) 15:100 04:539 AAPL: [EB|LD:LKFS] } Ok(0)
16:212 01:112 AAPL: [EB|LD:LKC] } Ok(0) 17:305 01:092 AAPL: [EB|#FWFM] 0xFF9FFF3F 17:409 00:104 AAPL: [EB|#FWFT] 0xFD8FF42E 17:514 00:104 AAPL: [EB|#CSR:IN] 0x00000067 17:622 00:108 AAPL: [EB|#CSR:OUT] 0x00000067 17:742 00:119 AAPL: [EB|BST:FBS] {
17:854 00:112 AAPL: [EB|BST:FBS] BA.ADSZ: 0 17:958 00:104 AAPL: [EB|BST:FBS] BA.KSDSZ: 0
18:070 00:111 AAPL: [EB|B:WFDW] Err(0xE), 0 @ LocHB 71B4903C-14EC-42C4-BDC6-CE1449930E49 18:175 00:105 AAPL: [EB|#LOG:DT] 2020-05-17T21:33:49 18:284 00:108 AAPL: [EB|#LOG:EXITBS:START] 2020-05-17T21:33:49

[MVDB0110]

I also see some unsupported speed mantissa errors for several XHCI ports. With USBInjectAll or with your kext.

[danielehrhardt]

Same Problems with the Razer Blade Stealth 13 Late 2019 with the same CPU

[khronokernel]

@MVDB0110 Came across an AppleLife post regarding Z490 and the issue of _UPC and _PLD being a bit screwed up. Curious if it's the same situation here, can you provide a full ACPI dump?(not just DSDT, would like the SSDTs and such as well)

[MVDB0110]

Here is my whole usb + DSDT dump: https://drive.google.com/file/d/1d2eGrsXcwI2YihPgQFbPlClSM0xxkGah/view?usp=sharing I hope this is what you need.

[khronokernel]

@MVDB0110 I need all the ACPI tables, not just the DSDT

[MVDB0110]

Here is my ACPI Dump on Windows: https://drive.google.com/file/d/1t3u0XSFGX7kg0gsgohFtdKYNzrtWSGyB/view?usp=sharing

[khronokernel]

Can you provide the individual tables instead of one large txt file?

[MVDB0110]

Here is the acpidump in separated .dat files. https://drive.google.com/file/d/19Wg9xaGyd3naukEYn49fpeBLwRa7GLTx/view?usp=sharing

[khronokernel]

Awesome thank you, so here's a few things to try:

• Drop xh_Dell_
• Drop xh_Dell_ and use USBInjectAll from Shiki's repo
• Set PCI0.XHC_.RHUB's STA to 0 so macOS is forced to rebuild ports, would need USBInjectAll from Shiki's repo
• Drop xh_Dell_, use USBInjectAll and PCI0.XHC_.RHUB's STA to 0

Dropping xh_Dell_: ACPI -> Delete

All | Boolean | YES
Comment | String | Delete xh_Dell_
Enabled | Boolean | True
OemTableId | Data | 78685f44656c6c5f
TableLength | Number | 0
TableSignature | Data | 53534454

USBInjectAll: See here: https://github.com/Sniki/OS-X-USB-Inject-All/releases

You cannot use the MacBookAir SMBIOS as Sniki hasn't added them yet, I recommend MacBookAir8,1 until USB has been mapped though they should build by themselves without USBInjectAll's help

SSDT-RHUB-STA:

Use this guy:

SSDT-RHUB-OFF.aml.zip

[dhinakg]

Do you have a Windows installation or are you able to install Windows by any chance?

[MVDB0110]

@khronokernel My USB problem is solved! But now my problem lies with AppleIntelFramebuffer/AppleIntelClocks.cpp "Wrong CD clock frequency 0x249f0000 set by EFI".

[MVDB0110]

Photo of the kernel panic. https://drive.google.com/file/d/1f7Z6MzVGzz5XheeRXD3ZcpCFl7QQoPAy/view?usp=sharing

[khronokernel]

My USB problem is solved!

Yay! What fixed it specifically?

And regarding clockID, shit. See here: acidanthera/bugtracker#942

We can do a bit more troubleshooting, try -igfxvesa in boot-args to see if it'll go any further

Btw: Your SMBIOS is somehow DELL8215,1, I wanna give a cookie for even being able to boot macOS with that ;p

Have a feeling it's a corrupt SMBIOS table, try these:

• Kernel -> Quirk -> CustomSMBIOSGuid -> True
• PlatformInfo -> UpdateSMBIOSMode -> Custom

[MVDB0110]

Okay you are a hero. It is booting in the installer (My touchpad isn't recognized tho), so for the installation I will have to use my Dell WD19 (Keyboard/Mouse and Ethernet).

[khronokernel]

Awesome! Though please do report back on what actually fixed the USB issue. Pretty sure USBInjectAll did jack shit but thinking my SSDT was the answer

[MVDB0110]

Well without USBInjectAll, My XHC ports aren't recognized and I don't proceed in the boot process. But with the SSDT and the blocking of xh_dell all error seem to dissappear except unsupported speed mantissa but I don't believe that is a real error, because the boot process succeeds. I'm installing in russian haha, any idea how to fix that?

[khronokernel]

I'm installing in russian haha, any idea how to fix that?

Troubleshooting page says ;p:

https://dortania.github.io/OpenCore-Desktop-Guide/troubleshooting/troubleshooting.html#macos-installer-in-russian

[MVDB0110]

Do u want my EFI as-is for your icelake vanilla guide?

[khronokernel]

Nah I'm alright, though will likely do a write up in the ACPI guide on the STA and Table dropping. I'm likely gonna close this issue as the USB's been fixed though would like to figure out the Clock ID mess on the iGPU

[MVDB0110]

Do you need anything from me for the Clock ID mess?

[MVDB0110]

Okay I have installed MacOS on the laptop but now I have another problem with the iGPU. It says Could not register with IOFB. GPU SKU: 0. Unsupported ICL sku.

[MVDB0110]

Now I got into MacOS, but my graphics card doesn't get a kext in system summary it says 35mb and in Ubuntu it says "00:02.0 0300: 8086:8a52 (rev 07)", which means I got the right device id and aapl platformid. Any ideas on how to fix it?

[Kouseu]

@najeebanwer
Does Catalina 10.15.7 need edid injection?

[najeebanwer]

@Kouseu, Yes. I upgraded from Catalina and I had the same issue in Catalina 10.15.7 until I did the EDID injection. Note that there are multiple ways of doing the EDID injection:

1. Use an injector kext (a kext that only contains a plist file that specifies the properties of the graphics card including EDID)
2. Put the display properties override file in /System/Library/Displays/Contents/Resources/Overrides (see https://www.insanelymac.com/forum/topic/208410-fixing-scrambledstretched-or-wrong-resolution-laptop-display-problems/)
3. Put the EDID directly into the "AAPL00, override-no-connect" property.

I find that option 3 is the simplest. You can find examples of 1 and 2 by using Hackintool to generate the kext/display override.

[ghost]

Sorry that this is off topic, but is sleep working from someone on Ice Lake?

[Kouseu]

@najeebanwer
The edid can be put directly or needs to be limited to 48hz? I find some threads where they say it can’t work with 60hz.

[xenonstride]

Sorry that this is off topic, but is sleep working from someone on Ice Lake?

yes,
use platform-id = 01005C8A and device-id = 5C8A0000

[Kouseu]

@najeebanwer
Hi. I followed your previous instructions.


Where should I put the display.plist?
Whether I put it to the desktop or the same folder with the edid-gen.sh, it always shows File Doesn’t Exist.

[MVDB0110]

@Kouseu I see a permission denied. Did you use sudo as a prefix to the shell script?
sudo /path/to/edid-gen.sh

[Kouseu]

@becrespi, I have successfully upgraded my Dell XPS 13 9300 to macOS Big Sur (11.1) and EDID injection did work for me to resolve the issue with the internal UHD+ (4K, 16:10) display, with the following caveats:

1. When I have my external USB-C monitor (Dell U2719DC) connected, the internal display is initially blank but closing the lid and then re-opening it causes the internal display to "wake up" and display the correct resolution.
2. When there is no external monitor connected, the internal display is blank after boot, but will "wake up" after about a minute (I still need to close and open the lid a couple of times). Once it wakes, it works correctly.

The EDID that worked for me is derived as follows:

1. get the output of xrandr --props using Linux. This gives the EDID for the internal display, but in my case, it is not compatible with macOS. So, use this EDID to create a plist file to use as input to edid-gen.sh (see attached ZIP archive).
   Archive.zip
2. The output of edid-gen.sh is another plist file with the "corrected" EDID.
3. Use this corrected EDID in config.plist, DeviceProperties, "AAPL00, override-no-connect" property for the IceLake GPU as shown below:
   
4. Some of the other properties I have enabled are the result of trial & error and the result mostly works, but I cannot say which ones are absolutely required.
   

I hope this will help others having similar issues.

Hi
Can you describe how to get the CORRECTED edid more precisely?
For example, I’ve made a plist file but I don’t know how to use it as input.

[Kouseu]

@Kouseu I see a permission denied. Did you use sudo as a prefix to the shell script?
sudo /path/to/edid-gen.sh

I think it’s more like the plist file cannot be found.

[najeebanwer]

@Kouseu, so the steps are:

1. Edit display.plist to use your DisplayProductID and DisplayVendorID (converted from hex to integer). You can get these from Hackintool.
   
2. Edit display.plist to use your EDID output from Linux (xrandr --props). If you use a text editor for the plist file, then the hex output from Linux will need to be converted to base64 to use in the plist file. Any online hex to base64 converter will work. I use https://base64.guru/converter/encode/hex.
3. Run the shell script. It takes display.plist as the first argument and produces the output plist file on the desktop.
   
4. Edit your config.plist to add the new EDID under DeviceProperties for the graphics card, "AAPL00, override-no-connect".
5. You will also need some of the other properties that I have enabled. At least the following are required for 4K displays:
   enable-dpcd-max-link-rate-fix
   enable-cdclk-frequency-fix
   enable-max-pixel-clock-override

[Kouseu]

@najeebanwer
Thanks for your instructions. But I don’t know why it can’t recognize my edid even though I’ve used my edid in the display.plist
It recognizes my edid as 0x04 0x90 0x6c

[najeebanwer]

@Kouseu, I don't know but it appears that you have not entered the IODisplayEDID properly in display.plist.
Open display.plist in a text editor and then copy the base64 representation of the value of the EDID into a base64 to hex converter. The hexadecimal value you get must match the EDID you got from Linux. A properly formatted EDID must be 128 bytes (i.e. 256 hex characters)

Also, please use Command+Shift+4 to capture window contents for your posts instead of taking photos of your screen.

[Kouseu]

@najeebanwer
I’ve tried two ways. The first one is to use proper tree to edit the edid(hex) and the second one is to use a text editor(I use the result of the hex to base64 converter ). They are both recognized as 0x04 0x90 0x6c.
And if I use the display.plist (the original one without any editing) in your Archive.zip, it’s also recognized as 0x04 0x90 0x6c.
I don’t know what to do....

[najeebanwer]

@Kouseu Attach your display.plist and let me look at it.

[najeebanwer]

@Kouseu, I was wrong about edid-gen.sh. It does not appear to actually use the provided display.plist file. Instead it gets the current EDID from the IO Registry and then corrects it. In your case, apparently the IO Registry does not have a valid EDID.

I think maybe you should try generating the graphics injector kext using the Hackintool export button (circled in red below) and then loading that to inject the EDID.

I would look at the plist file inside the generated kext and see if the EDID being injected looks right (i.e. it is at least 128 bytes).

[Kouseu]

@najeebanwer
Hi. Is there any other way to get the corrected edid?
And I’m curious about why the original edid from Linux isn’t compatible. I mean if I inject the edid directly to the device properties, the display can’t be correctly recognized.

[najeebanwer]

@Kouseu, you can try this:

1. Inject the EDID from Linux, without modification, using the device properties.
2. Verify that the EDID has been injected by using IORegistryExplorer, or try the command:
   ioreg -n AppleBacklightDisplay -arxw0
3. If the EDID in IORegistryExplorer looks like what you injected, then you should be able to run the edid-gen.sh script to get the corrected EDID.
4. Inject the corrected EDID using device properties.

Good luck.

[Kouseu]

@najeebanwer
Thank you so much. I also followed your other instructions on insanelymac. The screen isn’t black after boot anymore. However, the screen is like this. It’s not static, but moving.

[najeebanwer]

@Kouseu, Okay, that's progress; this is exactly what I would get before I finally got the right combination of EDID and other device properties. Here are my suggestions:

1. I got this scrambled screen on the internal display when my external USB-C display was not connected. Try connecting an external display via USB-C/DP or HDMI and see if that helps.
2. Try all the other device properties I have enabled on my system and see if some combination works for you. Try adding enable-backlight-registers-fix and igfxfw (see the descriptions at https://github.com/acidanthera/WhateverGreen)

Unfortunately, at this point you are just going to have to experiment and see what works for your system.
Good luck.

[Kouseu]

@najeebanwer
The problem is finally solved. Now it gets full acceleration with 4K 60hz. I deleted the edid in my config file and added display information to the /Display/Overrides(https://gitter.im/ICE-LAKE-HACKINTOSH-DEVELOPMENT/community?utm_source=notification&utm_medium=email&utm_campaign=unread-notifications) mentioning that I had chosen a wrong display file before. This time I put it into a file named the same with the vendorID in Backlightdisplay and it worked. I also find that if I don’t use an external display but a config file with fake ID, although it can boot into the os but there’s no Backlightdisplay in IOregisterexplorer. Seems an external display is a must so that the internal display can be recognized at least.

[najeebanwer]

@Kouseu, great! Congratulations.

[Kouseu]

Does anyone solve the 1-2 minutes black screen issue at login?

[xenonstride]

Does anyone solve the 1-2 minutes black screen issue at login?

yes. use latest whatevergreen and use -igfxblr boot arg

[ivnnv]

I still cant make HDMI output work.

I have a HP 15s-fq1148ns laptop with i7-1065G7.

Acceleration is working and weird mouse cursor has been fixed using below params but HDMI (1.4b for this model) still not work:

<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
  <key>AAPL,ig-platform-id</key>
  <data>AABSig==</data>
  <key>framebuffer-fbmem</key>
  <data>AAAAAw==</data>
  <key>framebuffer-patch-enable</key>
  <integer>1</integer>
  <key>framebuffer-stolenmem</key>
  <data>AACwAw==</data>
  <key>device-id</key>
  <data>UooAAA==</data>
  <key>framebuffer-unifiedmem</key>
  <data>AAAAgA==</data>
  <key>model</key>
  <string>Intel Iris Plus Graphics G7</string>
</dict>

Anyone knows how to fix or debug?

[SeptemberHX]

Does anyone solve the 1-2 minutes black screen issue at login?

Could you share your efi? I have a yoga c940 with i7-1065G7, 4k screen. I always got black screen with different DeviceProperties, and there is no [IGPU] output before black screen. Thanks.

[bohenao]

@Kouseu, Okay, that's progress; this is exactly what I would get before I finally got the right combination of EDID and other device properties. Here are my suggestions:

1. I got this scrambled screen on the internal display when my external USB-C display was not connected. Try connecting an external display via USB-C/DP or HDMI and see if that helps.
2. Try all the other device properties I have enabled on my system and see if some combination works for you. Try adding enable-backlight-registers-fix and igfxfw (see the descriptions at https://github.com/acidanthera/WhateverGreen)

Unfortunately, at this point you are just going to have to experiment and see what works for your system. Good luck.

Hi, I have the same laptop as yours, dell 9300. Just want to know if you have had your Hackintosh working well when disconnect from external display ?
I found that if I use 0000528A, then I will get 1-2 min dark backlight.
If I use 01005c8A then I will get glich when disconnect external display.

Thanks.

[erheeeee]

@Kouseu, Thanks to your guide above. I managed to get my 7390 2in1's 4k internal display work at 60hz rather than 52hz after patching and injecting edid.

[DottiestDuke47]

Hi, I have an XPS 9300, and am facing an issue when my XPS sleeps. When I try to wake it, the display remains blank, but macOS is still awake in the backgroind as I can hear the system sounds. I have read that this may be an issue with macOS bieng unable to reattach the framebuffer to the display, but I have no clue how to fix this.

I read on a forum that someone injected the property
framebuffer-con0-alldata -> 00000800 02000000 98040000
and this fixed waking from sleep, but this didnt work for me

I would really appreciate any help. Thanks

[KTMatterhorn]

Does anyone solve the 1-2 minutes black screen issue at login?

Could you share your efi? I have a yoga c940 with i7-1065G7, 4k screen. I always got black screen with different DeviceProperties, and there is no [IGPU] output before black screen. Thanks.

Did you ever successfully install OSX via opencore? I have the same c940 build with Iris graphics and am getting stuck on the install with "PCI configuration end" loops, and "console relocated to" panics. Could you share a working EFI or help? thanks!