Jump to content

[Release] macOS Catalina 10.15.1

gengik84

By gengik84,
in New Releases and Updates

 Share
98 posts in this topic

Recommended Posts

biciolino
biciolino
Posted
Posted (edited)
2 hours ago, pure.wisdom said:

Kexts don't depend on the bootloader.

I was under the same impression, but it seems WhateverGreen 1.3.4 does not need agdpmod=pikera with Radeon 5700 if used with OpenCore as bootloader. But almost every Clover user, here, included myself, seem to need that boot argument. Maybe the culprit is to be found elsewhere but for the time being, that seems to be the difference.

 

Biciolino

Edited by biciolino
  • Like 1
ASentientBot
ASentientBot
Posted
Posted

Not sure if anyone here is still on a non-Metal system, but I just released an updated version of the older framework wrappers here. This fixes the Notification Center crashes that some users were experiencing.

 

Have a good weekend :)

  • Like 3
  • Thanks 2
pure.wisdom
pure.wisdom
Posted
Posted
6 hours ago, biciolino said:

I was under the same impression, but it seems WhateverGreen 1.3.4 does not need agdpmod=pikera with Radeon 5700 if used with OpenCore as bootloader. But almost every Clover user, here, included myself, seem to need that boot argument. Maybe the culprit is to be found elsewhere but for the time being, that seems to be the difference.

 

Biciolino

I tested 5700 XT on OP. It still need agdpmod=pikera

  • Like 1
biciolino
biciolino
Posted
Posted (edited)
2 hours ago, pure.wisdom said:

I tested 5700 XT on OP. It still need agdpmod=pikera

Do you mean you tested it with Open Core and you also need that boot parameter? Then the discriminating factor must be another one, maybe the graphic card brand/model, dunno.

But, as i said, i for sure can live with one more boot parameter. I already have to use npci=0x3000, adding one more is not a problem :).

 

Biciolino

Edited by biciolino
STLVNUB
STLVNUB
Posted
Posted (edited)
4 hours ago, Badruzeus said:

I feel good... :yoji:

https://github.com/cormiertyshawn895/Retroactive

 

Screen Shot 2019-11-02 at 07.24.45.jpg

Screen Shot 2019-11-02 at 07.34.25.jpg

I did that months ago with the beta, old news here...

edit:

That aside, good job!

Edited by STLVNUB
  • Haha 1
Badruzeus
Badruzeus
Posted
Posted (edited)
56 minutes ago, STLVNUB said:

I did that months ago with the beta, old news here...

Nice, you might be using another method which I saw it on macrumors forum few months ago #LOL

Not really sure if Retroactive is just GUI version of it hmmmb. The github project has been started just a week. (nevermind).

 

4 hours ago, ASentientBot said:

Not sure if anyone here is still on a non-Metal system, but I just released an updated version of the older framework wrappers here. This fixes the Notification Center crashes that some users were experiencing.

First, thanks a lot for your (and team) great works. Unfortunately, Fermi is bit different compared to Tesla, IHD 1st Gen or HD3000 for 10.14 - 10.15 to achieve Graphics Accelerations. On my case, I need using these:

- CoreDisplayOriginal binary taken from Mojave Beta (Pre-release) + your prev. Wrapper (I don't remember which version)

- OpenGL.framework is from 10.14.4 (replacing libCoreFSCache.dylib from current macOS version)

- GPUSupport.framework is from 10.14.4. SkyLight (I no longer remember from which one) + your old Wrapper

- GeForceGLDriver.bundle on SLE is also from 10.14.4

- No need rolling AppleGraphics* IOAccelerator* IOGraphics* IONDRV* IOSurface* back from Sierra / HighSierra for Fermi.

And, for unknown reason GF119 is no longer able to reach Catalina Desktop with your recent wrapper(s), neither with Original CoreDisplay / SkyLight. Well yeah, I think what made it differs bcoz Apple still give NVDAGF* support for Fermi (?), or something else.

CoreDisplay-bin.zip

SkyLight-bin.zip

 

#EDIT: Oh, I have no issue with Notification Center just FYi

Edited by Badruzeus
  • Like 1
ASentientBot
ASentientBot
Posted
Posted
6 hours ago, Badruzeus said:

Nice, you might be using another method which I saw it on macrumors forum few months ago #LOL

Not really sure if Retroactive is just GUI version of it hmmmb. The github project has been started just a week. (nevermind).

 

First, thanks a lot for your (and team) great works. Unfortunately, Fermi is bit different compared to Tesla, IHD 1st Gen or HD3000 for 10.14 - 10.15 to achieve Graphics Accelerations. On my case, I need using these:

- CoreDisplayOriginal binary taken from Mojave Beta (Pre-release) + your prev. Wrapper (I don't remember which version)

- OpenGL.framework is from 10.14.4 (replacing libCoreFSCache.dylib from current macOS version)

- GPUSupport.framework is from 10.14.4. SkyLight (I no longer remember from which one) + your old Wrapper

- GeForceGLDriver.bundle on SLE is also from 10.14.4

- No need rolling AppleGraphics* IOAccelerator* IOGraphics* IONDRV* IOSurface* back from Sierra / HighSierra for Fermi.

And, for unknown reason GF119 is no longer able to reach Catalina Desktop with your recent wrapper(s), neither with Original CoreDisplay / SkyLight. Well yeah, I think what made it differs bcoz Apple still give NVDAGF* support for Fermi (?), or something else.

CoreDisplay-bin.zip

SkyLight-bin.zip

 

#EDIT: Oh, I have no issue with Notification Center just FYi

I don't have a Fermi card to test with, but they worked natively on Mojave/High Sierra, right? If so, try:

- current version of my wrapped binaries (based on 10.14.6 SkyLight and 10.14.4 CoreDisplay)

- OpenGL from 10.14.3 with replaced libCoreFSCache

- GPUSupport from 10.14.3

You're using a weird combination of versions that nobody else has tested; please try the above "standard" versions. I have no way to help you with your current untested configuration. (There is never a reason to use an older version of my wrappers in my knowledge, since I only add new symbols in new versions, nothing is removed. If those symbols don't exist in older macOSs, they will just do nothing. I'm pretty sure that the current version will work on any Catalina build.)

 

If that doesn't work, maybe also try:

- /S*/L*/E*/GeForce* (both .kexts and .bundles) from 10.15.0, 10.14.6 or 10.13.6

This is just a guess, but if Apple removed support for Fermi recently, it was probably from these kexts. The other replacements above are more "high level", if you have a working framebuffer and GLDriver then they will work. The fact that they're not implies to me that something changed with these files.

 

Also, "unable to reach Catalina Desktop" can mean a lot of things. Do you have a loginwindow or WindowServer crash log for me to look at? That might be informative.

 

Hope that helps! Thanks again for all your help on MacRumors :)

  • Thanks 1
hardcorehenry
hardcorehenry
Posted
Posted
15 hours ago, ASentientBot said:

Not sure if anyone here is still on a non-Metal system, but I just released an updated version of the older framework wrappers here. This fixes the Notification Center crashes that some users were experiencing.

 

Have a good weekend :)

 

Yep, without your last wrapper I wasn’t able to install apps that required notification access, now everything works. I’m not sure if I installed it properly, (not having Xcode on Catalina yet), just manually moved from output folder both binaries to each *.framework/Versions/A and repaired permissions. So far everything works as expected .Thanks for your amazing work.

 

cat.png.6e898a0b657403d027846316768d5d3e.png

  • Like 1
pure.wisdom
pure.wisdom
Posted
Posted
13 hours ago, biciolino said:

Do you mean you tested it with Open Core and you also need that boot parameter? Then the discriminating factor must be another one, maybe the graphic card brand/model, dunno.

But, as i said, i for sure can live with one more boot parameter. I already have to use npci=0x3000, adding one more is not a problem :).

 

Biciolino

yes sir we need that boot parameter with OpenCore

STLVNUB
STLVNUB
Posted
Posted
13 hours ago, Badruzeus said:

Nice, you might be using another method which I saw it on macrumors forum few months ago #LOL

Not really sure if Retroactive is just GUI version of it hmmmb. The github project has been started just a week. (nevermind).

Was just running iTunes/Contents/MacOS/iTunes in terminal, seemed to work ok

  • Like 1
macattackjack
macattackjack
Posted
Posted

I don't know if others have found it, but here's the official Apple link

https://support.apple.com/kb/DL2022?locale=en_US

does anyone know, does this update require the supplemental update that came out a few weeks ago?

Also, I have a Evga GT710 2GB. Any issues with that?

Badruzeus
Badruzeus
Posted
Posted (edited)
9 hours ago, ASentientBot said:

I don't have a Fermi card to test with, but they worked natively on Mojave/High Sierra, right? If so, try:

- current version of my wrapped binaries (based on 10.14.6 SkyLight and 10.14.4 CoreDisplay)

- OpenGL from 10.14.3 with replaced libCoreFSCache

- GPUSupport from 10.14.3

Ah haa.. I remember have tried this combination back to Mojave days, except your wrapped binaries & replacing libCoreFSCache. However my Fermi GF119 needs OpenGL, GPUSupport, SkyLight from 10.14.4 to make it works.

 

9 hours ago, ASentientBot said:

(There is never a reason to use an older version of my wrappers in my knowledge, since I only add new symbols in new versions, nothing is removed. If those symbols don't exist in older macOSs, they will just do nothing. I'm pretty sure that the current version will work on any Catalina build.)

Last time I run your build.tool from wrapper source under 10.13.6 with Xcode 10,1 but I was having "crashed: too many corpes being created" stuck. CoreDisplayOriginal & SkyLight Original are taken from current 10.15.1 (also from Mojave Beta & 10.14.3/4 SkyLight version). Or, are you guessing me need XCode 11+? It's worth to try I think.

 

9 hours ago, ASentientBot said:

If that doesn't work, maybe also try:

- /S*/L*/E*/GeForce* (both .kexts and .bundles) from 10.15.0, 10.14.6 or 10.13.6

I got bunch of missing symbols by replacing GeForce.kext binaries from diff. Major OS versions so, it was ommitted from prelinkedkernel.

 

9 hours ago, ASentientBot said:

This is just a guess, but if Apple removed support for Fermi recently, it was probably from these kexts. The other replacements above are more "high level", if you have a working framebuffer and GLDriver then they will work. The fact that they're not implies to me that something changed with these files.

This has been a really complicated thing about Fermi since Sierra #LOL :lol: SystemProfiler said "Metal supported", NVDAGF*.kext are also provided by Apple but it' s not metal capable, actually. Some workarrounds I've found with Desktop users, they use HDMI display connector but I have no idea how to change my laptop LVDS with another one #LMAO

 

9 hours ago, ASentientBot said:

Also, "unable to reach Catalina Desktop" can mean a lot of things. Do you have a loginwindow or WindowServer crash log for me to look at? That might be informative.

Just similar to Clamshell mode / console with blinking verbose logs like this; "ConsoleUsers: gIOScreenLockState...". But I/O devices still give respons. I also having this issue with recent CoreDisplay & SkyLight (plus your wrapper binaries).

 

9 hours ago, ASentientBot said:

Hope that helps! Thanks again for all your help on MacRumors :)

Also many thanks to you (and dosdude, parrotgeek, cs) for your great patches; I still use them on another laptop with 2nd Gen CPU + Intel HD3000.. seems like working fine.

 

#EDIT: I still have some stuffs from prev. macOS(es) so, I may try again later on Fermi (plus your wrappers)

 

 


Screen Shot 2019-11-03 at 05.19.30.jpg
 

 

 

 

 


Screen Shot 2019-10-17 at 22.22.24.jpg
 

 

Edited by Badruzeus
  • Like 1
ASentientBot
ASentientBot
Posted
Posted (edited)
5 hours ago, Badruzeus said:

Ah haa.. I remember have tried this combination back to Mojave days, except your wrapped binaries & replacing libCoreFSCache. However my Fermi GF119 needs OpenGL, GPUSupport, SkyLight from 10.14.4 to make it works.

 

Last time I run your build.tool from wrapper source under 10.13.6 with Xcode 10,1 but I was having "crashed: too many corpes being created" stuck. CoreDisplayOriginal & SkyLight Original are taken from current 10.15.1 (also from Mojave Beta & 10.14.3/4 SkyLight version). Or, are you guessing me need XCode 11+? It's worth to try I think.

 

I got bunch of missing symbols by replacing GeForce.kext binaries from diff. Major OS versions so, it was ommitted from prelinkedkernel.

 

This has been a really complicated thing about Fermi since Sierra #LOL :lol: SystemProfiler said "Metal supported", NVDAGF*.kext are also provided by Apple but it' s not metal capable, actually. Some workarrounds I've found with Desktop users, they use HDMI display connector but I have no idea how to change my laptop LVDS with another one #LMAO

 

Just similar to Clamshell mode / console with blinking verbose logs like this; "ConsoleUsers: gIOScreenLockState...". But I/O devices still give respons. I also having this issue with recent CoreDisplay & SkyLight (plus your wrapper binaries).

 

Also many thanks to you (and dosdude, parrotgeek, cs) for your great patches; I still use them on another laptop with 2nd Gen CPU + Intel HD3000.. seems like working fine.

 

#EDIT: I still have some stuffs from prev. macOS(es) so, I may try again later on Fermi (plus your wrappers)

  Reveal hidden contents

 


Screen Shot 2019-11-03 at 05.19.30.jpg
 

 

 

  Reveal hidden contents

 


Screen Shot 2019-10-17 at 22.22.24.jpg
 

 

Sorry, I don't think I can help you much more with this unless you send over some crash reports. You should be able to find them in /Library/Logs/DiagnosticReports or Console app. Missing symbols might be shim-able if we know what they are. parrotgeek1 managed it for nVidia Tesla and I did something similar for the wrappers as you know.

 

Why are you bothering with compiling my wrappers from scratch? Just use the binaries. Unless you're modifying them somehow, but I don't see much reason to at the moment.

 

Good luck! I'll help however I can.

 

-------------------------

 

Also, another update for the non-Metal folks: possibly the best transparency fix yet, including the menu bar!1896077287_ScreenShot2019-11-03at12_40_57AM.thumb.png.37bb03e914d4e9a4e662eb0f7c0c10a9.png

 

My apologies to the majority of you for whom this is irrelevant.

Edited by ASentientBot
add separator between merged messages
  • Like 4
Badruzeus
Badruzeus
Posted
Posted (edited)
4 hours ago, ASentientBot said:

Sorry, I don't think I can help you much more with this unless you send over some crash reports. You should be able to find them in /Library/Logs/DiagnosticReports or Console app. Missing symbols might be shim-able if we know what they are. parrotgeek1 managed it for nVidia Tesla and I did something similar for the wrappers as you know.

 

Why are you bothering with compiling my wrappers from scratch? Just use the binaries. Unless you're modifying them somehow, but I don't see much reason to at the moment.

 

Good luck! I'll help however I can.

 

Sorry for delay, I just did clean install 10.15 then updating to 10.15.1 (19B88), just #FYi

I took *.crash logs from /Library/Logs/DiagnosticReports as suggested with 2 conditions (attached):

1) 10.15.1-Clean => This one when system was fully unmodified (only able to boot with nv_disable=1)

2) 10.15.1-Patcher => Replacing some stuffs on /S*/L*/Frameworks && /S*/L*/PrivateFrameworks from macOS Catalina Patcher v1.2.3:

 

 

/System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay

/System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplayOriginal

/System/Library/Frameworks/OpenGL.framework

/System/Library/PrivateFrameworks/GPUSupport.framework

/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight

/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLightOriginal

 

 

#Notes for Point 2) SLE are untouched (using Stock / Vanilla GeForce* NVDAGF*, no Graphics related are modified). On this case, I'm unable to see Desktop at all even with nv_disable=1 (vesa) but just stuck at black screen with Console logs (I believe what I see are my Activity logs, with no Display / Window).

 

Thanks for your helps.

GT520M_Crash_Logs_10.15.1.zip

Edited by Badruzeus
  • Like 2
ASentientBot
ASentientBot
Posted
Posted (edited)
5 hours ago, Badruzeus said:

 

Sorry for delay, I just did clean install 10.15 then updating to 10.15.1 (19B88), just #FYi

I took *.crash logs from /Library/Logs/DiagnosticReports as suggested with 2 conditions (attached):

1) 10.15.1-Clean => This one when system was fully unmodified (only able to boot with nv_disable=1)

2) 10.15.1-Patcher => Replacing some stuffs on /S*/L*/Frameworks && /S*/L*/PrivateFrameworks from macOS Catalina Patcher v1.2.3:

 

  Hide contents

/System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay

/System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplayOriginal

/System/Library/Frameworks/OpenGL.framework

/System/Library/PrivateFrameworks/GPUSupport.framework

/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight

/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLightOriginal

 

 

#Notes for Point 2) SLE are untouched (using Stock / Vanilla GeForce* NVDAGF*, no Graphics related are modified). On this case, I'm unable to see Desktop at all even with nv_disable=1 (vesa) but just stuck at black screen with Console logs (I believe what I see are my Activity logs, with no Display / Window).

 

Thanks for your helps.

GT520M_Crash_Logs_10.15.1.zip

It looks like the system is trying to use Metal rather than OpenGL, but it fails to initialize with Metal. You said that this card was never Metal compatible, right?

 

If so, some of these options might be worth playing with.

https://www.reddit.com/r/hackintosh/comments/8lfu2t/how_to_disable_metal_ngfxgl1_boot_argument_and/

 

Edited by ASentientBot
add reddit link
  • Thanks 1
Alexey Boronenkov
Alexey Boronenkov
Posted
Posted
17 hours ago, yapan4 said:

Всем привет.

После обновления BIOS я получил загрузочную остановку в этом месте (мой хак от подписи)

20191031_213052.jpg

20191102_202504.jpg

Кто-то что-то подобное?

 

Снимок экрана 2019-11-03 в 17.16.00.png

On 02.11.2019 at 05:32, Badruzeus said:

Я чувствую себя хорошо... : Ёдзи:

https://github.com/cormiertyshawn895/Retroactive

 

Screen Shot 2019-11-02 в 07.24.45.jpg

Screen Shot 2019-11-02 в 07.34.25.jpg

 

Снимок экрана 2019-11-03 в 17.20.15.png

  • Like 1
  • Haha 1
Badruzeus
Badruzeus
Posted
Posted (edited)
39 minutes ago, ASentientBot said:

It looks like the system is trying to use Metal rather than OpenGL, but it fails to initialize with Metal. You said that this card was never Metal compatible, right?

 

If so, some of these options might be worth playing with.

https://www.reddit.com/r/hackintosh/comments/8lfu2t/how_to_disable_metal_ngfxgl1_boot_argument_and/

 

Yes, here's the problem.. I'm not sure for what reason Apple assummed that Fermi is Metal capable #LOL.. but it' s not, though SystemProfiler said it is. Honesly, I've used this `ngfxgl=1` boot-arg since HighSierra with WhateverGreen (NgfxGraphicsFixup is now part of WEG). Weird was, this `useIOP=false & useMetal=false` on /L*/Pref*/com.apple.CoreDisplay.plist also did nothing related to GF119 WindowsServer crash on Mojave - Catalina, except I lost "Metal Supported" info on SystemProfiler. Still, I have take a look again if crash reports would be differents.

 

Nevermind @ASentientBot, there're lot of things I need to learn with some trials & errors. :) (and this is just for fun, till I have no other choice than moving on Catalina. Screenshot below is from 10.13.6 BTW). Again, many thanks for your helps.

 



Screen Shot 2019-11-03 at 21.17.33.jpg

Edited by Badruzeus
  • Like 1
yapan4
yapan4
Posted
Posted (edited)

@alexboro3191

Thank you for responding to my message. 
This options enabled by default when MSR 0xE2 is locked(my case). I only add fix RTC ...no results:(, still stop on the same place.

I flach back old BIOS.

Thank you any way.

Edited by yapan4
 Share
Go to topic listing
×
×
  • Create New...