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.
It sounds odd... I can understand a general encryption issue, even with certain low-level patches, but an issue that only affects those patches and only on Catalina...
The weird part is, it's nothing with my implementation or anything. I tried using the APFS boot EFI script, but on a 2011 machine, and it can boot the encrypted volume no problem. It's machine specific for some reason.
 
The weird part is, it's nothing with my implementation or anything. I tried using the APFS boot EFI script, but on a 2011 machine, and it can boot the encrypted volume no problem. It's machine specific for some reason.

This is a MacBookPro 5,2... same as the one you recorded the video but with the glossy black finish.

Same issue using the APFS patcher to boot or starting it natively, after I enter the password it reboots like a reset.
Hope there’s a solution... if there’s anything I can do to help let me know.

Thanks!
 
Are their plans to release a software update and brightness control patch for the iMac 2008?
Brightness control working for me on an iMac 8,1 with GeForce 8800, both via keyboard and system preferences. Software Update is not patched for any unsupported mac yet, I don't believe.

Same problem here and no solution:(
I think the issue some people are mentioning about the incorrect installer version is just an Apple mistake. The "Get Info" in Finder shows 15.0.32 but the "About" within the installer app still shows 15.0.31, Apple probably just forgot to update the text
 

Attachments

  • Screen Shot 2019-10-10 at 4.31.18 PM.jpg
    Screen Shot 2019-10-10 at 4.31.18 PM.jpg
    23 KB · Views: 142
  • Screen Shot 2019-10-10 at 4.31.41 PM.jpg
    Screen Shot 2019-10-10 at 4.31.41 PM.jpg
    70.5 KB · Views: 148
  • Like
Reactions: TimothyR734
What ever happened to the plan to eliminate the need for setting the 'boot-args -no_compat_check' in nvram? Is support for unpatched machines like the MacPro 5,1 getting in the way of that?
 
  • Like
Reactions: TimothyR734
Confirming that macOS Catalina Patcher 1.1.7 cannot make APFS encrypted work even with BootROM patched too.

Installed on clear APFS new partition
Enabled FileVault. Waited until completion.
Restart machine.
Boot in the partition, Catalina image salutes asking for password... enter the password and system reboots!

Tries 3 times, same issue.

Also tried to install on an pre-formatted APFS encrypted and same issue

Has anybody been able to make FileVault work and successfully boot in the encrypted ?

Without this I won't "upgrade" to Catalina...
there are encryption issues with certain Macs best way is to Install Catalina then try encrypting
 
It technically should be eliminated, I just keep it using NVRAM as well, just in case.

justfor my own understanding...

I installed the GA version on my MP51 by disabling SIP and setting the NVRAM 'boot-args -no_compat_check' first, then proceeded with the patcher tool (installed from a booted Mojave drive directly to another NVMe SSD).

Could I have eliminated the above steps when using the current patcher?
 
I think it has to do with SSE 4.1 instructions some AMD GPU have support for it and some do
This isn't true. You're thinking of current AMD cards, for which SSE4.2 (not SSE4.1, which is required to even boot Catalina) is needed. There's a patch for this, but it was never explained here in much depth, to my knowledge, so I'm not sure quite how it works.

I don't think there's a clear explanation of why the 6xxx cards don't accelerate. If I remember correctly, the drivers load, but no acceleration is achieved. This has been the case since Mojave. (I've never had access to one of these machines to test, but several experts couldn't get it working so I highly doubt that I could.)

Those GPUs are notoriously unreliable anyways, so most people just elect to disable or swap them out.

Hope that helps clear things up a little. Please try to avoid spreading misinformation, it confuses people.

@Zahilla ^
 
The weird part is, it's nothing with my implementation or anything. I tried using the APFS boot EFI script, but on a 2011 machine, and it can boot the encrypted volume no problem. It's machine specific for some reason.

I am experiencing the same failure on MacBook Pro 5,5 when attempting to install Catalina to an encrypted APFS drive (firmware is updated using the dosdude APFS ROM patcher, not the Catalina Installer apfs software patch).
Immediately after entering FileVault disk password there is a kernel panic. If there are any logs that would be useful I'm happy to share.


Fortunately Catalina is working wonderfully on my iMac 10,1 !!! (This computer likewise has Encrypted APFS, of course it has native Apple bootrom).
Thank you @dosdude1 and everyone else for sharing the fruits of your labors!
 
  • Like
Reactions: TimothyR734
Finally a note to any manual patchers (or hackintosh people) who follow this thread and might've missed this. Revert your OpenGL patch from my "improved" minimalist patch suggestion. It causes problems.

Hi @ASentientBot, I am a hackintosh user with non-metal graphics, in fact an integrated Corei3 Arrandale with statically patched kexts from HighSierra. and while with the dosdude1 patcher I'm able to get everything working with my statically patched kexts, there is a flicker at around 70% progress at apple boot logo.
I'm wondering if this is due to some other patching dosdude1 patcher might have applied which is not relevant to my hackintosh.

So I wanted to understand the exact patches for the non-metal stuff and apply them manually. Can you please list them?
Also I wanted to understand your this statement "Revert your OpenGL patch from my "improved" minimalist patch suggestion. It causes problems.", did you mean to remove the minimalist patching and we should replace entire OpenGL and GPUSupport frameworks?
or you were saying that minimalist patching from the referred thread should be used?

Thanks in advance
 
Last edited:
Hi @All,

i'm successfully using dosdude's patcher on my iMac 8,1 and my MacBook 5,1 since the sierra-patch tool.
Some days ago i updated my mojave installs to catalina (19A583). Everything went fine, except for one problem (which i didn't find anything about in this whole thread :-/ ):

on my iMac (ATI Radeon HD 2600), if i doubleclick a photo in photos so it becomes larger, it shortly shows correct, but then immediately turns into this mess (see attachment)

It happens to every photo, regardeless of its resolution/filesize. I even created a new photos-library, imported only one photo and the problem still persists.

Has anybody experienced the same/similar problems and has some hint for me what i could try? (my MacBook doesn't have this problem)

thanks!
bulli_t2
 

Attachments

  • example_photo.png
    example_photo.png
    3.1 MB · Views: 133
MacPro 3.1 with Nvidia GeForce GTX650 connected to Cinema Display via DVI works fine, second monitor Sony 4k UHD TV connected via Displayport to HDMI is not recognised.
Anything I can do or check.

Thanks in advance.
 
  • Like
Reactions: foreverzvz
Hi @All,

i'm successfully using dosdude's patcher on my iMac 8,1 and my MacBook 5,1 since the sierra-patch tool.
Some days ago i updated my mojave installs to catalina (19A583). Everything went fine, except for one problem (which i didn't find anything about in this whole thread :-/ ):

on my iMac (ATI Radeon HD 2600), if i doubleclick a photo in photos so it becomes larger, it shortly shows correct, but then immediately turns into this mess (see attachment)

It happens to every photo, regardeless of its resolution/filesize. I even created a new photos-library, imported only one photo and the problem still persists.

Has anybody experienced the same/similar problems and has some hint for me what i could try? (my MacBook doesn't have this problem)

thanks!
bulli_t2
The following posts show this problem #4659 and #4661. Unfortunately, we have not made any progress with finding a solution. Rather strangely, it seems that the pictures can be printed correctly.
 
  • Like
Reactions: bulli_t2
The following posts show this problem #4659 and #4661. Unfortunately, we have not made any progress with finding a solution. Rather strangely, it seems that the pictures can be printed correctly.

Hi,

thank you so much for your information!! I was able to circumvent the problem with the "ResXtreme" app :)
Now the photos open and are shown as expected.

bulli_t2
 
Still no luck with Thunderbolt (display port) to HDMI... Doesn't see external display... Doesn't say "connected" in system info either. Is there a possibility that some kexts are broken?

MBP 13 2011
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.