Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

big sur 11.0.1 #370

Open
sail9708 opened this issue Nov 14, 2020 · 9 comments
Open

big sur 11.0.1 #370

sail9708 opened this issue Nov 14, 2020 · 9 comments

Comments

@sail9708
Copy link

sail9708 commented Nov 14, 2020

I have used this patcher on my mac catalina 10.15.6. And after i updated to 10.15.7. Everything was ok!
but i updated to 11.0.1 big sur yesterday. it doesn't work now!what should i do?
and there is no Coredisplay under the directory ‘/System/Library/Frameworks/CoreDisplay.framework/Versions/A/’

@MDandK
Copy link

MDandK commented Nov 17, 2020

Hi,
Have you found a solution ?
If not, could someone help please ?
Thanks

@sail9708
Copy link
Author

Hi,
Have you found a solution ?
If not, could someone help please ?
Thanks

i haven't found any solution to this. and i can't new or modify a file under directory '/System/...' in big sur

@MDandK
Copy link

MDandK commented Nov 17, 2020

I thinks the only solution to that is to use the the 4k@60hz capable Mini-Displayport to Displayport cable ... but need a compatible monitor !

@wallisch
Copy link

wallisch commented Nov 20, 2020

Big Sur will be more complicated, since it now has additional security mechanisms which prevent altering the system files. See https://eclecticlight.co/2020/06/25/big-surs-signed-system-volume-added-security-protection/.

Also, as you noticed, CoreDisplay apparently moved and i couldn't locate it yet.

The steps will probably be:

  • Boot to Recovery
  • Disable SIP
  • Disable Authenticated Root (Requires FileVault disabled)
  • Locate new CoreDisplay
  • Reverse engineer new CoreDisplay & patch the pixel clock
  • Bless new snapshot of now modified volume
  • Boot to macOS

@sail9708
Copy link
Author

Big Sur will be more complicated, since it now has additional security mechanisms which prevent altering the system files. See https://eclecticlight.co/2020/06/25/big-surs-signed-system-volume-added-security-protection/.

Also, as you noticed, CoreDisplay apparently moved and i couldn't locate it yet.

The steps will probably be:

  • Boot to Recovery
  • Disable SIP
  • Disable Authenticated Root (Requires FileVault disabled)
  • Locate new CoreDisplay
  • Reverse engineer new CoreDisplay & patch the pixel clock
  • Bless new snapshot of now modified volume
  • Boot to macOS

Thanks for your replying!
Referring to the latest method of enabling hidpi, maybe we can operate everything under directory ‘/Library/...' instead of '/System/Library/...' ?
is that be possible?

@Rothschildiuk
Copy link

Big Sur will be more complicated, since it now has additional security mechanisms which prevent altering the system files. See https://eclecticlight.co/2020/06/25/big-surs-signed-system-volume-added-security-protection/.

Also, as you noticed, CoreDisplay apparently moved and i couldn't locate it yet.

The steps will probably be:

  • Boot to Recovery
  • Disable SIP
  • Disable Authenticated Root (Requires FileVault disabled)
  • Locate new CoreDisplay
  • Reverse engineer new CoreDisplay & patch the pixel clock
  • Bless new snapshot of now modified volume
  • Boot to macOS

not working.
i get
`Olehs-MacBook-Pro:mac-pixel-clock-patch-V2-master oleh$ ./CoreDisplay-patcher.command
md5: /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay: No such file or directory
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
SIP looks to be disabled, all good!

(otool) Detected unpatched CoreDisplay on OS X 10.12 16A313a.
SIP looks to be disabled, all good!
Patching CoreDisplay with patch version 1
Password:
Can't open /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay: No such file or directory.
touch: /System/Library/Extensions: Read-only file system
Re-signing /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay
/System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay: No such file or directory
Closing...`

@Xess
Copy link

Xess commented Jul 24, 2021

Look like no hope to patch CoreDisplay in Big Sur.

I Just test opencore bootloader and override max-pixel-clock-frequency for intel. Now I got 4K/60Hz on Big Sur via mini displayport to HDMI 2.0 just like I had on Catalina(CoreDisplay Patch)

Screen Shot 2564-07-25 at 01 43 07

@duyleekun
Copy link

@Xess Did you modify max-pixel-clock-frequency or just use -igfxmpc(enable-max-pixel-clock-override)

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md#hdmi-in-uhd-resolution-with-60fps

@Spirarel
Copy link

@Xess or @duyleekun can you explain how to do this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants