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.
Status
Not open for further replies.

Macschrauber

macrumors 68030
Dec 27, 2015
2,981
1,487
Germany
no, its set to windows 10, now I get the language selection and can use the mouse, I was too impatient
[doublepost=1560303601][/doublepost]but I dont see the raw disk in Disk Utility. Must call it a night now.

Edit 2: Also no Keyboard, mouse is there.
 

jonwatso

macrumors member
Mar 22, 2016
33
27
Auckland, New Zealand
It probably becomes more likely with each forum post about how to bypass the cMP blocks in the Catalina installer.

Based off how long the 1,1 & 2,1 survived on patched installers I doubt it. Was more curious if there has been an OS in the past where they have switched instruction sets during beta?
 
Last edited:

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
no, its set to windows 10, now I get the language selection and can use the mouse, I was too impatient
[doublepost=1560303601][/doublepost]but I dont see the raw disk in Disk Utility. Must call it a night now.

Edit 2: Also no Keyboard, mouse is there.

1) Find the deviceID of your diskXX, you will need to use the correct one every time diskXX appears here:
Code:
diskutil list

2) Erase the SATA drive, diskXX:

Code:
sudo diskutil partitionDisk /dev/diskXX 1 MBR "Free Space" "%noformat%" 100%

3) Make the RAWDisk, diskXX:

Code:
/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/diskXX fullDevice rawDisk sata

The rawDisk.vmdk file is usually created at your user root folder, btw.

4) Create a HFS+ partition on the disk, then unmount it:

Code:
diskutil erasedisk jhfs+ Catalina GPT diskXX
diskutil unmountdisk diskXX

5) Create the Catalina VM as usual, name it Catalina, close the VM, close VMWare Fusion, add the rawDisk.vmdk to the Catalina VM folder (Finder, right button over the Catalina.vmwarevm, Show Package Contents) then add the rawDisk.vmdk to the VMX configuration file.

Edit from:
Code:
sata0.present = "TRUE"
sata0:2.fileName = "Temporary Installation Source Disk.vmdk"
sata0:2.present = "TRUE"
sata0:0.fileName = "Virtual Disk.vmdk"
sata0:0.present = "TRUE"
sata0:1.autodetect = "TRUE"
sata0:1.deviceType = "cdrom-raw"
sata0:1.fileName = "auto detect"
sata0:1.startConnected = "FALSE"
sata0:1.present = "TRUE"

To:
Code:
sata0.present = "TRUE"
sata0:0.fileName = "rawDisk.vmdk"
sata0:0.present = "TRUE"
sata0:1.autodetect = "TRUE"
sata0:1.deviceType = "cdrom-raw"
sata0:1.fileName = "auto detect"
sata0:1.startConnected = "FALSE"
sata0:1.present = "TRUE"
sata0:2.fileName = "Temporary Installation Source Disk.vmdk"
sata0:2.present = "TRUE"
suspend.disabled = "TRUE"
It's important to use exactly what are showed above or you will have to select the drive manually with PowerOnToFirmware, don't change it if you don't know exactly what you are doing.

6) Open VMWare Fusion, click over the Catalina VM with the right button, select Settings:
- Go to General and change from OS: macOS 10.14 to Windows 10 x64
- Go to Keyboard&Mouse and change the Profile from Mac Profile to Windows 10 Profile
- Close Settings

7) Startup the Catalina VM.
 
Last edited:

stupots

macrumors newbie
Mar 20, 2019
23
26
Kent, UK
@tsialex I've read back through the whole thread, but not seen this issue. I know it's early days, but I wanted to give it ago myself and not just be a spectator :)

What I did... I have installed Catalina on a SATA SSD drive with USB adapter from my 2016 Macbook Pro, if I select it as a startup disk before moving it boots fine. I've then restart (and held down command+r) and then disabled SIP and then booted back into Catalina on the MBP and run the sudo nvram boot-args="-no_compat_check" command from terminal. Then I've restarted with startup disk set to Mojave and ejected the Catalina disk.

What happens... When I fit this SSD into the Mac Pro 5,1 it seems to be going OK, I hear the chime, then about when the screen would normally display the Mac just powered off... It feels like something obvious I've missed; any idea? Spec is as per my signature +latest Wifi card.

Thanks

Stu
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
@tsialex I've read back through the whole thread, but not seen this issue. I know it's early days, but I wanted to give it ago myself and not just be a spectator :)

What I did... I have installed Catalina on a SATA SSD drive with USB adapter from my 2016 Macbook Pro, if I select it as a startup disk before moving it boots fine. I've then restart (and held down command+r) and then disabled SIP and then booted back into Catalina on the MBP and run the sudo nvram boot-args="-no_compat_check" command from terminal. Then I've restarted with startup disk set to Mojave and ejected the Catalina disk.

What happens... When I fit this SSD into the Mac Pro 5,1 it seems to be going OK, I hear the chime, then about when the screen would normally display the Mac just powered off... It feels like something obvious I've missed; any idea? Spec is as per my signature +latest Wifi card.

Thanks

Stu
It's your Mac Pro that needs -no_compat_check, not your MBP.
 

redheeler

macrumors G3
Oct 17, 2014
8,653
9,306
Colorado, USA
It probably becomes more likely with each forum post about how to bypass the cMP blocks in the Catalina installer.
Do you seriously think Apple executives or engineers frequently read this forum? You really seem impatient to see Apple enact forced obsolescence on our 5,1 Mac Pros...
 

AidenShaw

macrumors P6
Feb 8, 2003
18,667
4,677
The Peninsula
Do you seriously think Apple executives or engineers frequently read this forum? You really seem impatient to see Apple enact forced obsolescence on our 5,1 Mac Pros...
I'm sure that MR's server logs will show lots of activity from Apple Park and Infinite Loop.

I'm not "eager" to see a crackdown, but want to make it clear how quickly and easily Apple could declare "game over". What Jobs' Apple did for the 1,1 and 2,1 is not necessarily a predictor of what Tim Apple will do.
 
  • Like
Reactions: H2SO4 and Chung123

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
Do you seriously think Apple executives or engineers frequently read this forum? You really seem impatient to see Apple enact forced obsolescence on our 5,1 Mac Pros...
I'm sure Apple will remove -no_compat_check because we are using it for unintended purposes other than for debug on supported Macs. ;)

Btw people has been using it incorrectly since Mountain Lion:D
 

redheeler

macrumors G3
Oct 17, 2014
8,653
9,306
Colorado, USA
I'm sure Apple will remove -no_compat_check because we are using it for unintended purposes other than for debug on supported Macs. ;)

Btw people has been using it incorrectly since Mountain Lion:D
Yeah, it's interesting that Apple has never really attempted to crack down on people installing newer versions of MacOS on old unsupported Macs, even though it has been going on for years. But we all know Apple values profit above all else; supporting older hardware isn't free, but neither is inventing new measures to lock it out, measures that could inadvertently impact supported Macs and may be circumvented anyway.
 

Macschrauber

macrumors 68030
Dec 27, 2015
2,981
1,487
Germany
1) Find the deviceID of your diskXX, you will need to use the correct one every time diskXX appears here:
Code:
diskutil list

2) Erase the SATA drive, diskXX:

Code:
sudo diskutil partitionDisk /dev/diskXX 1 MBR "Free Space" "%noformat%" 100%

3) Make the RAWDisk, diskXX:

Code:
/Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/diskXX fullDevice rawDisk sata

The rawDisk.vmdk file is usually created at your user root folder, btw.

4) Create a HFS+ partition on the disk, then unmount it:

Code:
diskutil erasedisk jhfs+ Catalina GPT diskXX
diskutil unmountdisk diskXX

5) Create the Catalina VM as usual, name it Catalina, close the VM, close VMWare Fusion, add the rawDisk.vmdk to the Catalina VM folder (Finder, right button over the Catalina.vmwarevm, Show Package Contents) then add the rawDisk.vmdk to the VMX configuration file.

Edit from:
Code:
sata0.present = "TRUE"
sata0:2.fileName = "Temporary Installation Source Disk.vmdk"
sata0:2.present = "TRUE"
sata0:0.fileName = "Virtual Disk.vmdk"
sata0:0.present = "TRUE"
sata0:1.autodetect = "TRUE"
sata0:1.deviceType = "cdrom-raw"
sata0:1.fileName = "auto detect"
sata0:1.startConnected = "FALSE"
sata0:1.present = "TRUE"

To:
Code:
sata0.present = "TRUE"
sata0:0.fileName = "rawDisk.vmdk"
sata0:0.present = "TRUE"
sata0:1.autodetect = "TRUE"
sata0:1.deviceType = "cdrom-raw"
sata0:1.fileName = "auto detect"
sata0:1.startConnected = "FALSE"
sata0:1.present = "TRUE"
sata0:2.fileName = "Temporary Installation Source Disk.vmdk"
sata0:2.present = "TRUE"
suspend.disabled = "TRUE"
It's important to use exactly what are showed above or you will have to select the drive manually with PowerOnToFirmware, don't change it if you don't know exactly what you are doing.

6) Open VMWare Fusion, click over the Catalina VM with the right button, select Settings:
- Go to General and change from OS: macOS 10.14 to Windows 10 x64
- Go to Keyboard&Mouse and change the Profile from Mac Profile to Windows 10 Profile
- Close Settings

7) Startup the Catalina VM.


ok, that helped, thanx a bunch, mate :)

I used a real USB Stick and bootet Catalina Install.

The real Disk I refered is a SSD on an USB-Sata Adapter btw.

Did not all the settings but those pointing at the raw disk, not sure if my settings were wrong or the formating / partitioning did the trick.

Anyway, it is installing on the SSD, booted via USB Installer

thanx again for pointing me to the right direction
 

stupots

macrumors newbie
Mar 20, 2019
23
26
Kent, UK
It's your Mac Pro that needs -no_compat_check, not your MBP.

Thanks Alex, I didn't appreciate that command was doing something on the Mac itself and not on the Disk the Mac was booting from :rolleyes:
Booting into recovery on the Mac Pro, ran it and bingo! Everything appears to work well so far.

IMG_9113.JPG


Thanks for you help (once again!)

Stu
 

john36m

macrumors newbie
Jun 12, 2019
1
0
Boston
I have a Mac Pro 5,1. Running Sierra, with a Mojave friendly graphics card. Set up Mojave under VMWare Fusion 11.1.0. Run the Catalina Beta installer. It comes back with the screen that I cannot log into. Force Shut down VM. Boot VM into recovery mode. Set the nvram parameter as indicated in Terminal
nvram boot-args="-no_compat_check"
Then reboot with startup disk set.
Reboots "normally", but when it come back it says I am running Mojave.
What should I try next.
 

Auggie

macrumors 6502
Jan 21, 2017
384
108
I'm encouraged that Catalina can thus far run on a 5,1 with a few tricks. Hope that the release can also be made to run as I've already upgraded both my 5,1's with newer Airport cards.

But I won't mess with any of its beta's because trying to downgrade my daily 5,1 from Catalina if the release will no longer run on it will be a huge headache (not to mention there may be database changes with Photos, iTunes, etc, that won't prevent them from being downgraded or used on older OS's).

Regardless, it looks like a 2019 Mac Pro is gonna be on my "to buy" list sooner rather than later because I don't want to hobble along with hacked machines just to run the latest OS (like I do with my 3,1, which is troublesome whenever there is an OS update that requires patching the update to get it working).

At least I'm enjoying Catalina beta on my 2012 MBP for now...
 
Last edited:
  • Like
Reactions: mangombia

Demigod Mac

macrumors 6502a
Apr 25, 2008
840
288
Yeah, it's interesting that Apple has never really attempted to crack down on people installing newer versions of MacOS on old unsupported Macs, even though it has been going on for years. But we all know Apple values profit above all else; supporting older hardware isn't free, but neither is inventing new measures to lock it out, measures that could inadvertently impact supported Macs and may be circumvented anyway.
Probably not worth the effort it would take to hardline enforce hardware compatibility checks. As long as the process is sufficiently esoteric to the average user, Apple's tech support won't have to deal with people who try and fail.
 
  • Like
Reactions: stupots

krakman

macrumors 6502
Dec 3, 2009
451
512
I don't want to hobble along with hacked machines just to run the latest OS (like I do with my 4,1, which is troublesome whenever there is an OS update that requires patching the update to get it working).

are you aware that you can (unofficially) update the firmware on a 4.1 to make it a 5.1 which then allows you to update to Mojave without requiring any patches? you can also install the latest boot firmware which allows for NVME SSds to be used in the machine.
 

Auggie

macrumors 6502
Jan 21, 2017
384
108
are you aware that you can (unofficially) update the firmware on a 4.1 to make it a 5.1 which then allows you to update to Mojave without requiring any patches? you can also install the latest boot firmware which allows for NVME SSds to be used in the machine.

Oops, my bad: I meant my 3,1. I don't have a 4,1 (my brother-in-law does).
 

AidenShaw

macrumors P6
Feb 8, 2003
18,667
4,677
The Peninsula
Probably not worth the effort it would take to hardline enforce hardware compatibility checks. As long as the process is sufficiently esoteric to the average user, Apple's tech support won't have to deal with people who try and fail.
And changing the optimization settings to use AVX instantly eliminates all of the cMP systems.
 

jonwatso

macrumors member
Mar 22, 2016
33
27
Auckland, New Zealand
And changing the optimization settings to use AVX instantly eliminates all of the cMP systems.
I am no instruction set expert, but surely this wouldn't be worth the trouble after releasing the first beta? Has there ever been a beta where the instruction set has been changed before the final release?
 

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
I tested AirPortBrcm4331.kext from Mojave with Catalina DP1 and it works for enabling mid-2010 and mid-2012 AirPort Extreme (BCM94322MC). If you still has the original AirPort and need to use Wi-Fi, just use the Mojave kext.

In the long run, upgrading to BBCM94360CD or BCM943602CD (see the thread 802.11ac, BT 4.0 and Continuity & Handoff are working on Mac Pro 2010 (Keep Updating)) will make our lives easier, but if AirPortBrcm4331.kext continues to work with Catalina, no need to replace the original card.

Someone that have a MP4,1 with the original BCM94321MC please test it with AirPortBrcm4331.kext from Sierra and check if the kext still works with Catalina.
 
Last edited:

tsialex

Contributor
Original poster
Jun 13, 2016
13,455
13,602
Query: If I install Catalina to an external SSD from a compatible system (e.g., 2017 mBP) and put that drive in my 5,1 can I CCC that drive to a PCIe NVM drive?
Not yet, no cloning tool supports the way Catalina is installed.
 
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.