macOS 10.15 Catalina on Unsupported Macs

[hvds]

Before I begin let me thank you all for the excellent work behind these great patches. I can only imagine the painstaking care you put into them, and for sure I appreciate the results I see on my ten yers old MacBookPro 5,3.
I installed Catalina 10.15.2 through Dosdude1 patcher ver. 1.3.0. I'm experiencing sleep problems, with the mac randomly rebooting some time after I close the lid. Here is what the log shows:

panic(cpu 0 caller 0xffffff8002ca295c): Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.
Failure code:: 0xd5f2a20d 00000031
...

Any idea on what I could do to solve the problem?

There are a few entries for this subject in this thread, and also in the Mojave thread. They seem to occur with MBP5,1-5,3, including in my case (MBP5,2 17"). So it could well be related to dual GPU kexts as ASentientBot suggests. And yes, jackluke provided a lot of improvements for people with dual GPU machines at Mojave times.

alphascorp suggested in his post #6680 this, though in a slightly different context:
sudo pmset -a darkwakes 0
You could try it out. Not sure if it cures symptoms only.

pmset -g will show you the current settings, which in my case are
System-wide power settings:
Currently in use:
womp 0
autorestart 0
halfdim 1
sms 1
hibernatefile /var/vm/sleepimage
gpuswitch 2
networkoversleep 0
disksleep 0
sleep 0
hibernatemode 3
ttyskeepawake 1
displaysleep 20
acwake 0
lidwake 1

I had the sleep/wake issue mostly in Mojave (see e.g. Mojave post #17878). Now free from it since more than 2 months on Catalina.
What I did in addition to the pmset is reset NVRAM and then switch to always use the 9600M GPU. Also had to disconnect the faulty magnet sensor (flap closing sensor) on my machine, which may be unrelated or not to my sleep/wake failures.

 

[B-G]

There are a few entries for this subject in this thread, and also in the Mojave thread. They seem to occur with MBP5,1-5,3, including in my case (MBP5,2 17"). So it could well be related to dual GPU kexts as ASentientBot suggests. And yes, jackluke provided a lot of improvements for people with dual GPU machines at Mojave times.

alphascorp suggested in his post #6680 this, though in a slightly different context:
sudo pmset -a darkwakes 0
You could try it out. Not sure if it cures symptoms only.

pmset -g will show you the current settings, which in my case are
System-wide power settings:
Currently in use:
womp 0
autorestart 0
halfdim 1
sms 1
hibernatefile /var/vm/sleepimage
gpuswitch 2
networkoversleep 0
disksleep 0
sleep 0
hibernatemode 3
ttyskeepawake 1
displaysleep 20
acwake 0
lidwake 1

I had the sleep/wake issue mostly in Mojave (see e.g. Mojave post #17878). Now free from it since more than 2 months on Catalina.
What I did in addition to the pmset is reset NVRAM and then switch to always use the 9600M GPU. Also had to disconnect the faulty magnet sensor (flap closing sensor) on my machine, which may be unrelated or not to my sleep/wake failures.

Thank you for your help. I will try to get a better understanding of those settings and see if there is anything I can change to solve this issue.

 

[hvds]

Thank you for your help. I will try to get a better understanding of those settings and see if there is anything I can change to solve this issue.

I just see that darkwake parameters are recorded in the file
/Library/Preferences/com.apple.PowerManagement.plist
from where eg xcode can display them.
pmset apparently doesn't show them. man pmset gives a different location for the file mentioned, no longer valid in Catalina as it seems.
I wish you success. The sleep/wake problems were indeed very annoying.

 

[gbecattini]

What I post herein seems to be out of topic but it is not, as you can read below.

I bought my Mac Pro, first because I love it, second because I was hoping to use it as a storage for +600,000 files of mine in conjunction with OneDrive, but I discovered that it is not possible.

I thought at beginning that it was a problem of its "unsupported" condition (patches). But it is not. The problem is in Mac itself, as I tried to explain here (see at the end of the page).

The point is that when Mac starts it assigns device IDs in a random way (es. /dev/disk1, disk2 etc.). So, the drive dedicated to OneDrive changes from one boot to the other, and any time you have to wait days or weeks to get the sync again.

The question I hope someone can answer is the following: with the Dosdude patched approach, the boot loader, that I believe you call EFI loader, is not the standard Apple, but one that someone has written to allow the loading of APFS volumes.

I have been writing C++ code for a large part of my life. Now is far the year when I did my last compile, but perhaps... ehm... if I could have the loader source code... perhaps...ehm... I might study a modification to assign drive IDs in a fixed way?

That would considerably extend the capability to use old patched Mac Pros, that would become even better then the new ones!

Well, I just asked....

 

[0403979]

What I post herein seems to be out of topic but it is not, as you can read below.

I bought my Mac Pro, first because I love it, second because I was hoping to use it as a storage for +600,000 files of mine in conjunction with OneDrive, but I discovered that it is not possible.

I thought at beginning that it was a problem of its "unsupported" condition (patches). But it is not. The problem is in Mac itself, as I tried to explain here (see at the end of the page).

The point is that when Mac starts it assigns device IDs in a random way (es. /dev/disk1, disk2 etc.). So, the drive dedicated to OneDrive changes from one boot to the other, and any time you have to wait days or weeks to get the sync again.

The question I hope someone can answer is the following: with the Dosdude patched approach, the boot loader, that I believe you call EFI loader, is not the standard Apple, but one that someone has written to allow the loading of APFS volumes.

I have been writing C++ code for a large part of my life. Now is far the year when I did my last compile, but perhaps... ehm... if I could have the loader source code... perhaps...ehm... I might study a modification to assign drive IDs in a fixed way?

That would considerably extend the capability to use old patched Mac Pros, that would become even better then the new ones!

Well, I just asked....

All the APFS loader does is find the volume with the correct UUID which is set in the ESP and then boot the volume using the apfs.efi file which is copied from the currently set volume and is also in the ESP.

 

[gbecattini]

So... no hope, right?

 

[crjackson2134]

Well, I just asked....

First, let me say I’m no expert on the subject and I don’t use one drive. Having said that, the problem sounds like it originates with an inflexible sync utility. If the sync utility isn’t built-in / required by OneDrive, I would turn it off and use a macOS native sync utility that leverages rsync.

 

[Pinarek]

Hi Pinarek
Its update today working for OS X 10.9 to macOS 10.15 ➢ Kext Droplet

@chris1111 Thank You for this Tips.

 

[gbecattini]

First, let me say I’m no expert on the subject and I don’t use one drive. Having said that, the problem sounds like it originates with an inflexible sync utility. If the sync utility isn’t built-in / required by OneDrive, I would turn it off and use a macOS native sync utility that leverages rsync.

Thanks for reply. I do not believe that I am able to force OneDrive to use a different sync application or to make Microsoft to modify something for me (they said me that know nothing about Mac OS, that is clearly false... they really wrote the app for Mac, didn't they? ). Microsoft tells me: ask Apple. I don't even try to ask Apple... The only way should be to assign always the same ID to the same physical drive, but that seems impossible.

I found a workaround: using an external USB disk drive. In this case its ID is always the last internal + 1, and so OneDrive works perfectly, until I do not change something in the physical drive equipment, obviously.

Anyway your suggestion is good: I will study this approach.

Thanks, I will insist searching a solution.

 

[crjackson2134]

{Deleted Off Topic Post}

 

[16v]

Thanks for reply. I do not believe that I am able to force OneDrive to use a different sync application or to make Microsoft to modify something for me (they said me that know nothing about Mac OS, that is clearly false... they really wrote the app for Mac, didn't they? ). Microsoft tells me: ask Apple. I don't even try to ask Apple... The only way should be to assign always the same ID to the same physical drive, but that seems impossible.

I found a workaround: using an external USB disk drive. In this case its ID is always the last internal + 1, and so OneDrive works perfectly, until I do not change something in the physical drive equipment, obviously.

Anyway your suggestion is good: I will study this approach.

Thanks, I will insist searching a solution.

I have similar issues - but not with my mac - with my sat receiver which is linux-based E2.
I have to edit fstab using the guuid from the drive.

Maybe a hint...

 

[Bobcov1]

My apologies, but I see no method to create a new topic title. My problem with my iMac9,1 is not, I don't think, at all attributable to this incredible program. I think my APFS failure to activate drive issue is an apple problem. Does anyone know a solution? It's a 320 gb drive which refuses to activate after being dismounted and formatted to APFS. And of course, the installer won't install to it. I reformatted to extended and am restoring from Time Machine. Not surprised, but it was a pain to lose the entire evening because of this bug. Everything was going fine until the APFS step. Oh, I first did a conversion and the installer ran but at the end, it said something about the existing is was not compatible??? After that I erased and formatted APFS and could not activate.

-Bob
Yes, I searched but I could not go through 25 pages of results.

 

[uMBP17"]

Just wanted to report that dosdude1's Catalina patcher works perfect on my late 2011 macbook pro 17inch model.

see video attached.

 

[vince22]

Just wanted to report that dosdude1's Catalina patcher works perfect on my late 2011 macbook pro 17inch model.

see video attached.

great job, just updated my trusty 2012 MBP 13" Raid0 APFS with latest catalina as well.

 

[uMBP17"]

great job, just updated my trusty 2012 MBP 13" Raid0 APFS with latest catalina as well.

Thanks, and well done to you as well!
Did you up the RAM as well?

 

[vince22]

Thanks, and well done to you as well!
Did you up the RAM as well?

no, it came 16gb ram when i bought it.

 

[Ausdauersportler]

Is anyone experiencing sleep/wake issues with its iMac 27" 2011 under Catalina using a GTX765M flashed by Nick Bios?

I am either getting a black screen (no backlight) or the screen stays black (backlight is on) with a mouse cursor when trying to wake up the iMac. I have to restart the iMac manually or it will restart automatically.
I can't tell if it's the Catalina upgrade that brought this or flashing the GPU. Before, using High Sierra with the default Bios, the iMac would wake up normally.

BTW, I have applied all the Catalina patches from Dosdude list.

Have the same experience with iMac 12,2, K2100M, Catalina 10.15.2. Sleep ends in restart. Startup with black screen for less than 5 seconds, than rapid boot with login screen in less than 5 seconds, again. Boot from SSD.
When I send the system to sleep via Finder menu it takes some time to shut down the fans. After that mouse movement or keyboard entries forces a restart.

Okay, after re reading page ONE of this thread I found problem and solution. Sorry for making noise here!

Have a good wakeup - probably with a more or less serious restart - in 2020

 

[Macbookprodude]

great job, just updated my trusty 2012 MBP 13" Raid0 APFS with latest catalina as well.

isn’t anything 2012 already natively supported for run Catalina without patcher ?

 

[Macbookprodude]

[automerge]1576908060[/automerge]

Another reason Catalina creates 2 Containers one is MacintoshHD-Data where important files etc is stored if you have a faulty HDD it might not be able to create both

dude just get another HDD or SSD - geez

 

[vince22]

its all about Catalina running Raid-0 APFS.

 

[0134168]

thank you - but what do you mean does work well but does not control brightness? and does the Mac sleep with the patch?

Just control colors, diming them. Not the brightness. But does the work, to work more comfortable to the eyes.

 

[overshoot]

Convert is risky... make a backup using CCC and restore to an HFS+ partition

In my last tests with version 5.1.14 (5780) it didn't work.
Can you please tell me the exact order? as I can restore it from an image from
Catalina 10.15.2 back to HFS +.

@overshoot I have an HFS + partition, slightly larger than the APFS partition, CCC always formats this HFS + in APFS with 2 partitions. It is NOT possible to convert an image from catalina 10.15.2 disk utility as an APFS image to an HFS + with only 1 partition. How did you do that because you write it would work ???

Thank you very much for that.

work this true with last version CCC ?

Well I am not saying that I had to do that but it's just that if things go wrong, you're screwed without a backup... Now you should just backup the Catalina "Data" partition to your HFS+ partition.

Actually it would be useful to understand what you're trying to achieve. Why would you have to convert back to HFS+?

 

[snorider]

I've searched around but I can't seem to find a clear answer on being able to simply upgrade from Mojave to Catalina on my MBP 5,3, since the tutorial video on dosdude1's site seems to run a clean install, and there are no instructions/steps outlined anywhere else that I can see that speak to an upgrade as there were previous versions.

So am i missing something obvious here, or is this a clean install, or nothing scenario?

Thanks for any help, and sorry if this has been beaten to death already, I just can't find a clear answer.

Cheers!

 

[crjackson2134]

I've searched around but I can't seem to find a clear answer on being able to simply upgrade from Mojave to Catalina on my MBP 5,3, since the tutorial video on dosdude1's site seems to run a clean install, and there are no instructions/steps outlined anywhere else that I can see that speak to an upgrade as there were previous versions.

So am i missing something obvious here, or is this a clean install, or nothing scenario?

Thanks for any help, and sorry if this has been beaten to death already, I just can't find a clear answer.

Cheers!

I installed directly over one of my Mojave drives, but keep in mind I'm on a MP51. It was nearly the same as any other upgrade install. If you have any 32bit legacy apps installed however, they won't work anymore. Catalina is strictly 64bit.

 

[snorider]

I installed directly over one of my Mojave drives, but keep in mind I'm on a MP51. It was nearly the same as any other upgrade install. If you have any 32bit legacy apps installed however, they won't work anymore. Catalina is strictly 64bit.

Thanks for your reply. So did you just follow the tutorial video to perform the update? I've watched it and it seems like he's formatting the existing HD to APFS, which i would assume wipes out all the data. Is there an alternative set of instructions available?