Jump to content

Intel Framebuffer patching using WhateverGreen


459 posts in this topic

Recommended Posts

3 hours ago, najeeb_anwer said:

@joevt So, unfortunately, things are not as rosy as I thought.

The internal display works great while I am also connected to the external USB-C monitor.

If I boot macOS with just the internal display (no external display connected) then the internal display is scrambled and unusable.

It appears that I have made some mistake in the display injector kext so that the timing for the internal display is messed up? But why would it work properly if the external display is connected?

Your insights would be greatly appreciated.

I don't know. Maybe remove the IODisplayEDID and the scale resolutions? You can do scale resolutions with SwitchResX afterward.

I found this post: 

I did what the author suggested; I removed the display injector kext and instead placed the attached file in /System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-4d10.

DisplayProductID-14cc

That works. The EDID is injected properly as well as the Display Name that I specified.

1173309444_ScreenShot2020-10-02at11_34_57AM.png.da061da134eda22a3d8174f9948b7d05.png

1826278420_ScreenShot2020-10-02at11_44_23AM.thumb.png.32a60ad8c20477914f61abcab002b92f.png

This is how it shows up in IORegistryExplorer:

55124652_ScreenShot2020-10-02at11_27_00AM.thumb.png.f6dd70d66f1c0ffdc6fa773232bd6ef7.png

 

Unfortunately, it still only works if the external display is connected. If I boot with just the internal display, the screen is scrambled.

 

On 9/30/2020 at 11:19 PM, najeeb_anwer said:

@joevt So, unfortunately, things are not as rosy as I thought.

The internal display works great while I am also connected to the external USB-C monitor.

If I boot macOS with just the internal display (no external display connected) then the internal display is scrambled and unusable.

It appears that I have made some mistake in the display injector kext so that the timing for the internal display is messed up? But why would it work properly if the external display is connected?

Your insights would be greatly appreciated.

 

It is an known issue on quite a few laptops on Ice Lake platforms, regardless of the resolution of your built-in display.

  • 2 weeks later...
On 7/25/2020 at 12:22 AM, MisterKeeks said:

I really wonder what controls AppleDisplay vs AppleBacklightDisplay... On my laptops this seems to be picked up automatically.

 

Anybody has a good answer to this?

Using CLOVER on Optiplex 3030 AiO I get AppleDisplay, and no backlight after wake up

i3-4160 / HD 4400

 

My System Properties shows correct connection as Thunderbolt/Displayport and display name is recognized as "Optiplex 3030" with correct resolution etc

 

I tried Hackintool "Display Injector" codeless kext (force load in Clover from Library\Extensions)

Shows as not loaded & still just AppleDisplay in IORegistry

Edited by sebus
  • 1 month later...

Lesson Learned: Start UHD/HD framebuffer patching with SMBIOS MacMini8,1

 

Been a while since I visited this thread and wanted to post something I discovered while patching the framebuffer on an HP EliteDesk 800 G3 Mini (i7-7700T HD630 Kabylake): I discovered that initially setting SMBIOS MacModel to MacMini8,1 with WEG boot-arg igfxagdc=0 is a very "forgiving" SMBIOS for framebuffer patching.  Using MM8,1 (even though it's not the correct SMBIOS for Kabylake CPU power management) made framebuffer patching much easier.  I found with MM8,1 that I could reliably remote desktop into my hack after booting to black screen, so that it was easy to make framebuffer config changes to continue my framebuffer experimentation.  After finding working WEG framebuffer patching with MM8,1, I then switched to iMac18,2 (the best CPU power management match for my i7-7700T) and my framebuffer patching continued to work fine.

 

For whatever reason, my first attempts to find correct framebuffer patches with SMBIOS iMac18,2 prevented me from remoting into my rig when incorrect framebuffer patches resulted in booting to black screen.

 

I hope this helps others.

  • 1 month later...

With the newest version of WEG i got a black screen after boot for several minutes. adding -igfxblr seems to fix the issue.

 

Another thing is I have to disable dedicated GPU to make sleep work else laptop wakes up with black screen and then reboot with this KP:

panic(cpu 2 caller 0xffffff801d56ea25): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since wake (130 seconds ago): 14, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (130 seconds ago): 2, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffff803bd9b670 : 0xffffff801a2b9aed mach_kernel : _handle_debugger_trap + 0x3dd
0xffffff803bd9b6c0 : 0xffffff801a3fc6e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffff803bd9b700 : 0xffffff801a3ecd1a mach_kernel : _kernel_trap + 0x55a
0xffffff803bd9b750 : 0xffffff801a25ea2f mach_kernel : _return_from_trap + 0xff
0xffffff803bd9b770 : 0xffffff801a2b938d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffff803bd9b890 : 0xffffff801a2b9678 mach_kernel : _panic_trap_to_debugger + 0x268
0xffffff803bd9b900 : 0xffffff801aabe434 mach_kernel : _panic_with_thread_context
0xffffff803bd9b970 : 0xffffff801d56ea25 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffff803bd9b980 : 0xffffff801d56e678 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffff803bd9b9a0 : 0xffffff801aa4569e mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffff803bd9b9f0 : 0xffffff801d56dab4 com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7c
0xffffff803bd9bb20 : 0xffffff801aa4f86b mach_kernel : _is_io_connect_method + 0x35b
0xffffff803bd9bc80 : 0xffffff801a3a7d81 mach_kernel : _iokit_server_routine + 0x4d81
0xffffff803bd9bd90 : 0xffffff801a2bf0e7 mach_kernel : _ipc_kobject_server + 0x337
0xffffff803bd9be00 : 0xffffff801a295905 mach_kernel : _ipc_kmsg_send + 0x115
0xffffff803bd9be60 : 0xffffff801a2ad012 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffff803bd9bef0 : 0xffffff801a3d0ec3 mach_kernel : _mach_call_munger64 + 0x273
0xffffff803bd9bfa0 : 0xffffff801a25f216 mach_kernel : _hndl_mach_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[7AE04EA4-D026-39A0-B2D5-5C9E4EE72967]@0xffffff801d56d000->0xffffff801d56efff

Process name corresponding to current thread: watchdogd
Boot args: -v keepsyms=1 alcid=15 brcmfx-country=DE brcmfx-aspm -igfxblr chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20C69

Kernel version:
Darwin Kernel Version 20.2.0: Wed Dec  2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64
Kernel UUID: 82E2050C-5936-3D24-AD3B-EC4EC5C09E11
KernelCache slide: 0x000000001a000000
KernelCache base:  0xffffff801a200000
Kernel slide:      0x000000001a010000
Kernel text base:  0xffffff801a210000
__HIB  text base: 0xffffff801a100000
System model name: MacBookPro16,3 (Mac-E7203C0F68AA0004)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 848878637159
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000000c5a51c186b
  Sleep   : 0x000000a49855cb54 0x00000008d1353bce 0x0000000000000000
  Wake    : 0x000000a49ac96fb3 0x0000000051af3664 0x000000a49962868e
last started kext at 718873478841: >!UAudio    401.4 (addr 0xffffff7fba70f000, size 307200)
last stopped kext at 806476866983: xyz.racermaster.NoTouchID    1.0.3 (addr 0xffffff801e458000, size 24576)
loaded kexts:

If GPU is disabled then I have to replug or power off and on the monitor to work again, sleep is working fine.

  • 2 weeks later...
On 1/24/2021 at 1:54 PM, Neblogas said:

With the newest version of WEG i got a black screen after boot for several minutes. adding -igfxblr seems to fix the issue.

I'm not familiar with that bootflag.   Where's it documented and what does it do?  Also, what chipset and CPU in your system?  Are you referring to your W.I.P. Laptop with i710510u?

 

EDIT: For others wondering about -igfxblr boot flag, I found it documented here as a WhateverGreen v1.4.6 addition.  Not sure why this didn't appear in my original search.

Edited by tonyx86
Added link to -igfxblr boot flag
I'm not familiar with that bootflag.   Where's it documented and what does it do?  Also, what chipset and CPU in your system?  Are you referring to your W.I.P. Laptop with i710510u?
 
EDIT: For others wondering about -igfxblr boot flag, I found it documented here as a WhateverGreen v1.4.6 addition.  Not sure why this didn't appear in my original search.

Luckily that boot flag did help on my laptop.
Big Sur
Clover 5130
Latest WEG & Lilu
Solved black screen on boot to macOS.
Doesn’t happen with earlier versions of weg
Intel HD 630.
Not sure what has changed in WEG to cause black screens when it was working perfectly before. Now have to use a boot flag to regain the same functionality as previous versions without a boot flag.


Sent from my iPhone using Tapatalk
×
×
  • Create New...