@ASentientBot glad to see that keep fighting! 
[doublepost=1560245393][/doublepost]
[doublepost=1560245393][/doublepost]
Had my imac11.2 this MXM 3 slot?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.15 Catalina on Unsupported Macs
- Thread starter 0403979
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I would say for all 2009,2010 and 2011 imac users out there, visit this thread about upgrading to a metal gpu :
https://forums.macrumors.com/threads/2011-imac-graphics-card-upgrade.1596614/
https://forums.macrumors.com/threads/2011-imac-graphics-card-upgrade.1596614/
@ASentientBot since you joined to macrumors from Mojave 10.14.0 beta 2, creating patches for Mojave USB devices, Core2Duo and Nvidia Tesla (and many other), you have proved to me and to this community your amazing and extraordinary skills especially in this subject and field, but for what you achieved today I can only say this is not luck, you're a genius!
I can learn from you.
I can learn from you.
I don’t have supported Mac to do initial install of Catalina, so I spoofed my 2007 iMac to think it was a 2012. And it worked
Your verbose screen doesn't tell much, while you should have had install on a clean Catalina APFS Volume, I guess instead you upgraded from a Catalina USB Installer your previous APFS Mojave (or worst an HFS+ Mojave), apparently there are permissions issues on some frameworks before reaching the GUI Mode, you could try to fix them booting in single user mode (holding CMD+S) and typing:
mount -uw /
chown -R 0:0 /System/Library/Frameworks/
chmod -R 755 /System/Library/Frameworks/
chown -R 0:0 /System/Library/PrivateFrameworks/
chmod -R 755 /System/Library/PrivateFrameworks/
exit
But before do that, once following an apple guide, I wrote something about changing the APFS Volumes Roles
It seems from your verbose that your previous Mojave (now Catalina) System/Data Volume doesn't have a valid APFS Role, it's reported as "0" (zero) that is according to the APFS scheme a non-system and non-data volume, but apparently your UUID is valid.
So could try to give it a Role in this way, but you need to boot or from Catalina USB Installer, or HighSierra/Mojave Installer from a Recovery Terminal:
mount -uw /
diskutil apfs list (or diskutil list)
Locate your Catalina APFS (Preboot, VM, Recovery, System and Data) disk identifiers example diskXsY of your System Volume
diskutil mount diskXsY1
diskutil apfs changeVolumeRole diskXsY1 S (This represents the System Volume)
diskutil apfs updatePreboot diskXsY1
(not sure if really needed the next lines I'm typing but if you want to set an APFS Role for each Volume you should add)
diskutil apfs changeVolumeRole diskXsY2 B (this represents the Preboot Volume)
diskutil apfs changeVolumeRole diskXsY3 R (this represents the Recovery Volume)
diskutil apfs changeVolumeRole diskXsY4 V (this represents the VM Volume)
I don't know yet the real role decided by apple for the new "APFS Data" but it should be this:
diskutil apfs changeVolumeRole diskXsY5 U (standing for Users I guess)
because I based on the fact that these are the APFS Volume Roles established by apple:
<roles> = one or more of 0|B|U|S|R|V
"0" is a generic empty APFS Volume containerized.
NOTE that Y1-Y5 are just indicatives partitions but you could have the Recovery on Y4 and System on Y3 for example.
[doublepost=1560256238][/doublepost]
Yes, I used your "perl" method earlier (during Sierra/HighSierra beta or Mojave) to create a custom Installer and it does allow to use an invalid signed OSInstall.mpkg allowing to customize the Distribution file inside avoiding the "package appears to be missing or damaged" in the OSX Installer GUI Mode.
Last edited:
[doublepost=1560261784][/doublepost]How did you did it?
There are essential 3 ways, though one is untested (but properly safe), another one dangerous (potential hardware damage!), and the third one not straight forward and thus overly complicated (well, all are for inexperienced users).
Assuming it works as it should the first is the best: use OpenCorePkg.
The prohibitive one is Clover which is somewhat the role-model for the latter. (DO NOT USE on Macs)
The last is the already detailed install from a virtualmachine using raw disk access.
Since non of those are end-user ready (yet), despite for those knowing what they do (alas no need for explanation), I will not link nor explain anything any further.
The APFS volume role for the Data volume is D for Data.
now that @ASentientBot was able to figure acceleration where do we go from here?
Not yet tested and not sure about that, since I played with APFS since HighSierra, I can't find the official apple where it was explained but these are the official apfs roles: 0|B|U|S|R|V
If I look at my Catalina APFS external drive diskutil apfs list
I can only notice the "APFS Data" Role reported as "No specific role".
I just found this: https://developer.apple.com/support/apple-file-system/Apple-File-System-Reference.pdf
But you can simply notice them typing this: diskutil apfs changeVolumeRole
And this is the answer:
If you type that from a Recovery Environment it will show other two APFS Roles: S and U
I believe System and Users.
Code:
Usage: diskutil apfs changeVolumeRole|chrole <apfsVolumeDisk> <roles>
where <apfsVolumeDisk> = APFS Volume DiskIdentifier
<roles> = one or more of 0|clear|b|r|v|B|R|V
Change the role metadata flag bits of the existing APFS Volume. Unspecified
bits are left alone; lower case clears a bit; upper case sets a bit; clear
clears all bits; 0 is ignored. You should be aware of any specific system
usage or legal combinations of role bits.
Ownership of the affected disks is required.
Example: diskutil apfs changeVolumeRole disk5s1 RI will release a beta of macOS Patcher 3 shortly, after I get my hands on the acceleration patches.
[doublepost=1560263872][/doublepost]
From a Catalina system it reports as a data role.
Oh wait, I haven't checked from there, I am still using HighSierra/Mojave as my main system, since my Catalina is installed externally USB and don't plug it often, let me check.
What about for those of us who have Metal cards? I have a RX580. Based on what I've read (every post in this thread) my only issue(s) would be wifi and bluetooth right because my card that I upgraded for Mojave, is no longer supported right?
Card Type: AirPort Extreme (0x14E4, 0x8E)
Firmware Version: Broadcom BCM43xx 1.0 (5.106.98.102.31)
I did buy a Broadcom BCM943602CS which I got in the mail yesterday only to realize it's the wrong one...
Anyway, I don't want to mess up the cloning process, I do have a 2015 MacBook running Catalina, so I'm hoping for a patcher that I can run natively on my 4.1->5.1 MacPro.
Thanks for everything, even though I don't understand every post, it's fascinating watching it all come together.
you can upgrade with no promblem
[doublepost=1560264925][/doublepost]
awesome, yo thanks @ASentientBot
You're right, and not only, they added a bunch of new APFS Roles, this 99% prevents an HFS+ convert, but honestly even to overcome the Catalina OTA updates, HFS+ is really no more required. It's time to drop it.
Code:
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
-bash-3.2# diskutil apfs changeVolumeRole
Usage: diskutil apfs changeVolumeRole|chrole <apfsVolumeDisk> <roles>
where <apfsVolumeDisk> = APFS Volume DiskIdentifier
<roles> = "0" or "clear" or one or more of
b|r|v|i|t|s|d|u|n|e|x|h|l|c|y|g|
B|R|V|I|T|S|D|U|N|E|X|H|L|C|Y|G
Change the role metadata flag booleans of the existing APFS Volume. Unspecified
flags are left alone; lower case clears a flag; upper case sets a flag; clear
clears all flags; 0 is ignored. You should be aware of any specific system
usage or legal combinations of role flags.
Ownership of the affected disks is required.
Example: diskutil apfs changeVolumeRole disk5s1 R
-bash-3.2# sw_vers
ProductName: Mac OS X
ProductVersion: 10.15
BuildVersion: 19A471t
-bash-3.2#
In the meantime, I'll prep for release and just include your patches when they're ready. Take your time. Speed of release < reliability.
Last edited:
Problem is that when I got to install all my drives are greyed out. Is this the part where I'm supposed to edit the plist or try to reboot in verbose mode (can't see boot screen though). Also are you saying that my wifi card will work or will I still need a newer card and/or kext?
Thanks
Thanks for the solution of the HID problem (busy timeout USB/HID for mouse / keyboard). I also had this on my HackMac Dell Optiplex. He is now working well with Catalina, thanks to metal graphics.
Installing on my HackMacBookPro with Intel 1st Gen IntelHD also no problem. Works fine, but of course still without acceleration, but you will solve the problem for sure. Good job so far! I follow everything here and also test myself for the acceleration.
Now my question. I did not have the courage for APFS ROM Patcher on my MacPro3,1 yet. Mojave is still working on HFS + with GT710 OOB metal graphics. I'm a bit worried about using the APFS ROM Patcher.
Is it still possible to install Catalina on HFS +, or can I prevent the conversion? Probably not, because the structure of Catalina with Catalina - Data is already explicit.
Installation via supported Mac is no problem here. Cancel before the first boot either. The installation in the MacPro3,1 only does not use, if not HFS +.
Maybe I should have the courage to use APFS ROM Patcher.
Installing on my HackMacBookPro with Intel 1st Gen IntelHD also no problem. Works fine, but of course still without acceleration, but you will solve the problem for sure. Good job so far! I follow everything here and also test myself for the acceleration.
Now my question. I did not have the courage for APFS ROM Patcher on my MacPro3,1 yet. Mojave is still working on HFS + with GT710 OOB metal graphics. I'm a bit worried about using the APFS ROM Patcher.
Is it still possible to install Catalina on HFS +, or can I prevent the conversion? Probably not, because the structure of Catalina with Catalina - Data is already explicit.
Installation via supported Mac is no problem here. Cancel before the first boot either. The installation in the MacPro3,1 only does not use, if not HFS +.
Maybe I should have the courage to use APFS ROM Patcher.
@0403979 forgot to say that till HighSierra/Mojave there was already, apart the ones mentioned, the APFS Role "I" and I guess it meant for "Installer", infact I used it to create some my personal custom hybrid HighSierra/Mojave APFS Recoveries, so this proves that on future macOS 10.16 a BaseSystem.dmg full APFS bootable is already possible.
Wow, I have to say I'm pretty amazed. Needless to say it looks like I'll be starting on a new Catalina Patcher!
Wow, so I had to create the HFS+ partition within Catalina? or am I mistaken, I tried running the commands you suggested in Single User Mode, I will attach a screenshot so you can confirm if I did it right, and will try to boot the USB right now, but even if it boots won't be installing. Is there some sort of service I can DM you over for quicker contact such as Discord?
Attachments
permissions chown -R 0:0 and chmod -R 755 not chown -R 775 or chown -R 755, re-check your Frameworks path
No, HFS+ won't work more on Catalina, only APFS.
But your main issue is that your Mojave (Catalina updated) Volume has an APFS role of "0", it should be instead Role "S", from your previous screen picture.
Anyway you can try, or better waiting for developers here to release a Catalina Patcher Installer.
Last edited: