Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Just installed DP2 and experienced the same issue -- hanging on the Apple logo due to repeated loginwindow crashes. I hit it with the ol' stub hammer again and managed to get to the Desktop, but still lack acceleration (framebuffer working though). There are a ton of new symbols in CoreDisplay, which is a bad sign.

I'll report back if I make any progress. @pkouame or @dosdude1 , have you looked into this yet? Anything I should be aware of?
i can almost promise you Apple is looking at these,,
 
  • Like
Reactions: TimothyR734
Just installed DP2 and experienced the same issue -- hanging on the Apple logo due to repeated loginwindow crashes. I hit it with the ol' stub hammer again and managed to get to the Desktop, but still lack acceleration (framebuffer working though). There are a ton of new symbols in CoreDisplay, which is a bad sign.

I'll report back if I make any progress. @pkouame or @dosdude1 , have you looked into this yet? Anything I should be aware of?
Ouch! Have yet to install b2, but since you raise the alarm I'll install tonight and inspect CoreDisplay and SkyLight. Hope it's not as bad it sounds... Can you PM me your latest patch code (you know where...)
 
Ouch! Have yet to install b2, but since you raise the alarm I'll install tonight and inspect CoreDisplay and SkyLight. Hope it's not as bad it sounds... Can you PM me your latest patch code (you know where...)
why is Apple changing up so much code,, like was this happing a lot in 10.14?
 
  • Like
Reactions: TimothyR734
Ah, I found the cause of the diskmanagementd issue! Apple is sure making things tricky now. Got it all patched properly, though. Tool is now updated to Beta 9.
this is happening on beta 8
 

Attachments

  • 1D72CA9C-895E-4AFB-87CB-61273402ADE3.jpeg
    1D72CA9C-895E-4AFB-87CB-61273402ADE3.jpeg
    4.2 MB · Views: 329
Just installed DP2 and experienced the same issue -- hanging on the Apple logo due to repeated loginwindow crashes. I hit it with the ol' stub hammer again and managed to get to the Desktop, but still lack acceleration (framebuffer working though). There are a ton of new symbols in CoreDisplay, which is a bad sign.

I'll report back if I make any progress. @pkouame or @dosdude1 , have you looked into this yet? Anything I should be aware of?
So I just installed b2 on a supported Mac. Quick inspect of CoreDisplay.b2 shows a pretty massive increase in procedures and symbols vs CoreDisplay.b1 - over 600 new procedures...wow!

Not necessarily bad, but there are definitely a few changes a foot ;) I'll do a deeper dive in the morning as well as cracking SkyLight open.

This is not unusual, b2 didn't just take a few weeks to cook. Development cycles overlap a lot! So it was probably ready in some sort of alpha stage by the start of WWDC19. Expect more changes throughout the summer.

You may have to apply your same methodology again: plug the missing holes with stubs to make other frameworks sing. Worked once, no reason why it shouldn't again. This will test our stamina... If you check the release notes Apple has a very long list of bugs and those are just the "public" release notes... I'll check back if I find anything useful. Luck.
 
I don't get it. its doing the same to me. How did you get it to finish the install. It reboots the first time at about the 5 minute mark and just goes back to the reinstall Mac recovery screen
Didn't yet. Had problems with patcher. I have solved the issue with my USB and going to try the instalation procedure late this morning... Let's see what it brings.
 
Looks like the PerfPowerServices(Although I don't have much experience with the Console):

View attachment 843585
You may be on to something. Search for PerfPowerServices in the system log - there may be associated crash logs also.
[doublepost=1560835699][/doublepost]@ASentientBot - just noticed that CoreDisplay b2 references a new library

/System/Library/PrivateFrameworks/HIDDisplay.framework/HIDDisplay

I don't think that was there before in CoreDisplay b1 (doesn't show up in the system library load sections). You may want to check that out...
 
Looking through the Mojave Patcher.app/Contents/Resources/macOS Post Install.app/Contents/Resources files, I assume that the stock scripts for...

sipPatch.sh
legacyPlatform.sh
legacyAudioPatch.sh
legacyusb.sh
usbohci.sh
legacyiSight.sh
platformsupport.sh

should be sufficient to patch a MacPro 3,1 with GTX680. However I am unclear what should be done for wifi. I have a supported Broadcom BCM94322MC which doesn't require Mojave legacy wifi patch. My understanding is that those drivers were removed from Catalina. So. does that imply that I want to copy over the IO80211FamilyV2.kext from Mojave and do I need any additional kext?
I doubt you would need the additional kexts, but I am new to kexts.
 
Last edited:
  • Like
Reactions: TimothyR734
Ah, I found the cause of the diskmanagementd issue! Apple is sure making things tricky now. Got it all patched properly, though. Tool is now updated to Beta 10.
Ciao... It's possible to have step by step instruction to try your patch...
Thank's for your job...
Franco
 
Using patcher beta 10 mac os catalina beta 1 don't know why i'm getting this issue "macos could not be installed on this computer" also can't format to apfs in the installer it just doesn't work so i had to use mac os extended journaled and if i used mojave to format it to apfs i get this error "could not create a preboot volume for APFS install "
 

Attachments

  • image.jpg
    image.jpg
    3.8 MB · Views: 306
  • FE6B89E3-3E7F-4917-8A48-B9BEDD4B4069.jpeg
    FE6B89E3-3E7F-4917-8A48-B9BEDD4B4069.jpeg
    4.5 MB · Views: 459
Using patcher beta 10 mac os catalina beta 1 don't know why i'm getting this issue "macos could not be installed on this computer" also can't format to apfs in the installer it just doesn't work so i had to use mac os extended journaled and if i used mojave to format it to apfs i get this error "could not create a preboot volume for APFS install "
The tool now only supports using the Developer Preview 2 installer app (due to some extreme changes Apple made to the DP2 installer). You can download it using my macOS Downloader tool.
 
You may be on to something. Search for PerfPowerServices in the system log - there may be associated crash logs also.

My reports should be taken with a grain of salt though as I've made some uneducated choices during the installation and perhaps corrupted my system unnecessarily. As a proof of concept it worked great. No doubt, I would have to do a re-install at some stage. It feels very good to return to the quiet coolness of Mojave partition.
 
Acceleration achieved on DP2! :)

Screen Shot 2019-06-18 at 2.12.59 AM.png Screen Shot 2019-06-18 at 2.24.05 AM.png

Yay!

Unfortunately, I feel that this effort will soon come to an end if we can't find a better solution than replacing the entire SkyLight and CoreDisplay. But for now, I made stuff happy again by stubbing out another several functions. (It only took so long because dumbass me somehow removed the symlinks inside the OpenGL framework in the process of copying it, and apparently those are necessary.)

It's late so I don't have time to thoroughly test, but it seems much the same as before. Key differences include an actually read-only filesystem, some nice "Loading..." text in Finder's columns view, and a lot of changes to what seems to be mostly accessibility-related display code. (Related: none of the display-related accessibility features in System Preferences really work at the moment due to my stub functions not actually doing anything.)

Anyways, a new CoreDisplay.framework (the SkyLight wrapper is unchanged) is attached for those who want to be on the bleeding edge. Good luck and goodnight.
 

Attachments

  • CoreDisplay.framework.zip
    562.5 KB · Views: 481
Last edited:
Acceleration achieved on DP2! :)

View attachment 843591 View attachment 843597

Yay!

Unfortunately, I feel that this effort will soon come to an end if we can't find a better solution than replacing the entire SkyLight and CoreDisplay. But for now, I made stuff happy again by stubbing out another several functions. (It only took so long because dumbass me somehow removed the symlinks inside the OpenGL framework in the process of copying it, and apparently those are necessary.)

It's late so I don't have time to thoroughly test, but it seems much the same as before. Key differences include an actually read-only filesystem, some nice "Loading..." text in Finder's columns view, and a lot of changes to what seems to be mostly accessibility-related display code. (Related: none of the display-related accessibility features in System Preferences really work at the moment due to my stub functions not actually doing anything.)

Anyways, a new CoreDisplay.framework is attached for those who want to be on the bleeding edge. Good luck and goodnight.
I knew you'd pull it off! Thanks a ton, once again!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.