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.
Happy new year :)

I don't know if the subject has been discussed here yet. On my Mac mini 3.1 the screensaver does not turn on. I can activate it in the preview, but it won't activate after the defined time. This happens with the standard screensavers.

I use the latest version 10.5.2. of Catalina on my Mac mini. Any workaround for this problem?
 
@dosdude1 here it is I am talking about this; did you see, my file name is short but the right menu is long. Maybe this is a bug of Catalina or something wrong on my iMac9.1.

Screen Shot 2020-01-04 at 17.42.40.png
 
Happy new year :)

I don't know if the subject has been discussed here yet. On my Mac mini 3.1 the screensaver does not turn on. I can activate it in the preview, but it won't activate after the defined time. This happens with the standard screensavers.

I use the latest version 10.5.2. of Catalina on my Mac mini. Any workaround for this problem?
Never heard of that problem before. Check if you have your display set to sleep before the screensaver starts
 
  • Like
Reactions: avz
Hi, thanks for your post, but I'm not able to find any info about how to fix the sleep problem in my iMac 12.2. Could you please provide a link to the solution?

Greets from Barcelona

Buenas noches!

Read the very first post in the thread below, there you find which files to add to let your iMac sleep, again. What I do not understand is why this is not part of the normal patches added by the Patcher supplied. According to this post sleep is broken since Mojave.

 
  • Like
Reactions: Dilli
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 don't think there is one posted here, and I've seen a few ask. On my various macs using the dosdude tool I updated mohave to catalina via:
  • time machine backup
  • create the dosdude USB bootable installer for catalina
  • recovery boot, select new USB drive
  • select to install a new version of OSX
  • in my case, point to the drive/partition with mojave instance I want to upgrade to catalina
  • install, run any post-patches after installation if prompted
Apps, docs, etc. are carried over.

Hope that helps!
 
Last edited:
New mbp - new problem:

2011 13", mojave is running.
Starting with dosdude catalinas sd card while holding option key, mbp restarts when progress bar is at 50%.

Whats wrong?
 
Why?

It worked with mojave on several systems and also with catalina.
But not now.

This is whät i get after booting back into mojave:
a43ca98a61c43fb9aed981e532ded6a9.jpg
c193b9f06223c64234096fb470370765.jpg
dbbe7e993f612f221bc4b1e6f243a043.jpg
 
That is from TotalFinder.
Two users already answered you the same thing. TotalFinder modifying system menu. So just disable it completely and try. Most of all its your culprit. I have no problems with this and have no TotalFinder installed))
 
Hey folks,

So I`m trying to run the patcher on an mbp 5,5 (El Capitan), but when restarting it can`t find the usb drive. Any suggestions?
 
Hi all, I tried the catalina patcher install on my mac mini. It seems that it installs some off the stuff on the main hdd of the mac mini. But, it will not continue the installation process after the reboot.. it boots right into the catalina patcher boot external hdd again and shows the recover menu?
I've attached the log, so maybe one of you guys can see what is happening... thx
 

Attachments

  • Installeringslog 5-Jan-2020.txt.zip
    15 KB · Views: 186
Hi, I have an issue with installation on my mac pro 3.1.

1) I boot in to recovery.
2) I click (re)install.
3) The machine restarts but it boots in to the USB (recovery).
4) repeat the above...

I can't get it to boot in to the new installer on APFS formatted volume.

Note #1: The only time that I see the installer is trying to boot in to the APFS volume is when I clean the NVRAM but this just gives me the stop sign which means that the volume it tried to boot to is incompatible/doesn't contain an installer.

Note #2: I tried to enable/disable csrutil, I also tried to install with the no_compat_check flag but no dice.

Note #3: I tested with multiple USBs in case of some weird 2.0 / 3.0 driver stuff..

Note #4: After the installation the catalina disk has some data on it but doesn't appear as a startup disk.

What other logs can I send here?

It's a Mac Pro 3.1 early 2008 model.
The drive is Kingston 250GB SSD.
I have a native boot compatible GPU.
Prior to this I had the latest Mojave running just fine.

Please help.
Thanks.
 

Attachments

  • Installer Log 6-Jan-2020.txt.zip
    4.6 KB · Views: 178
Last edited:
I've run into a couple of issues with the Catalina Patcher 1.3 and 10.15.2 (19C57) on my cMP 5,1

Unlocking with apple watch stopped working.

Filevault has also stopped working. The error is:
FileVault cannot be used on this system and operating version

Anyone else see these problems? I wasn't seeing them with 10.15.1 and the patcher.

Thanks.
 
  • Like
Reactions: higgsboson
Hi, I have an issue with installation on my mac pro 3.1.

1) I boot in to recovery.
2) I click (re)install.
3) The machine restarts but it boots in to the USB (recovery).
4) repeat the above...

I can't get it to boot in to the new installer on APFS formatted volume.

Note #1: The only time that I see the installer is trying to boot in to the APFS volume is when I clean the NVRAM but this just gives me the stop sign which means that the volume it tried to boot to is incompatible/doesn't contain an installer.

Note #2: I tried to enable/disable csrutil, I also tried to install with the no_compat_check flag but no dice.

Note #3: I tested with multiple USBs in case of some weird 2.0 / 3.0 driver stuff..

Note #4: After the installation the catalina disk has some data on it but doesn't appear as a startup disk.

What other logs can I send here?

It's a Mac Pro 3.1 early 2008 model.
The drive is Kingston 250GB SSD.
I have a native boot compatible GPU.
Prior to this I had the latest Mojave running just fine.

Please help.
Thanks.
3.1 is not APFS bootong capable. Did you patch the firmware? if not, did you make the USB for non APFS booting capable?
 
  • Like
Reactions: TimothyR734
3.1 is not APFS bootong capable. Did you patch the firmware? if not, did you make the USB for non APFS booting capable?

I suspect that the APFS implementation is at fault here. It'd be great if this tool was documented so we know what behaviour to expect.

What do you mean by "did you patch the firmware?". Yes I used the catalina patcher.
It's my assumption that post install patches should be done after the system reboots and finishes the install, and also that this an optional step. cc @dosdude1

And YES, the APFS booter is enabled in the patcher when creating the USB installer.

Basically ONLY if I purge NVRAM then the APFS booter for unsupported macs implementation runs and ends up with 🚫 screen. If I don't purge NVRAM then it just keeps going back to recovery and never installs..
 
Last edited:
  • Like
Reactions: TimothyR734
I suspect that the APFS implementation is at fault here. It'd be great if this tool was documented so we know what behaviour to expect.

What do you mean by "did you patch the firmware?". Yes I used the catalina patcher.
It's my assumption that post install patches should be done after the system reboots and finishes the install, and also that this an optional step. cc @dosdude1

And YES, the APFS booter is enabled in the patcher when creating the USB installer.

Basically ONLY if I purge NVRAM then the APFS booter for unsupported macs implementation runs and ends up with 🚫 screen. If I don't purge NVRAM then it just keeps going back to recovery and never installs..
What ******* meant have you used the APFS bot room tool it is a very risky tool as it could brick your mac
 
I suspect that the APFS implementation is at fault here. It'd be great if this tool was documented so we know what behaviour to expect.

What do you mean by "did you patch the firmware?". Yes I used the catalina patcher.
It's my assumption that post install patches should be done after the system reboots and finishes the install, and also that this an optional step. cc @dosdude1

And YES, the APFS booter is enabled in the patcher when creating the USB installer.

Basically ONLY if I purge NVRAM then the APFS booter for unsupported macs implementation runs and ends up with 🚫 screen. If I don't purge NVRAM then it just keeps going back to recovery and never installs..
Use Startup Disk preferences panel to select any drive. Then use APFS Boot to check the actual Catalina partition that you want to boot.
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.