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.
Oh, I missed that during Mojave patches. Good hint, thanks, about the right click selection.
I´m fully aware though that these old patches might not work or even worse, corrupt a working setup. It was just an experiment and in case of the partially working backlight might give some clues...


Hi, @Larsvonhier sorry if I'm a little OT: Do you have found a final fix to SIRI on Catalina B3 always crashing after opening it? Thank you!
 
  • Like
Reactions: TimothyR734
Does that imply that now, on machines with the APFS ROM patch applied, that we will have three disks polluting the option boot screen (the APFS volume, the duplicate EFI Boot volume that the APFS ROM patch creates and now a third EFI boot volume holding the APFS patch)? Ugh.

If so, could you please add an option to the Catalina Patcher to allow users to create a customized usb installer that has the APFS ROM patch off by default?

From my experience, you are not going to have three disks(just an EFI Boot and the APFS partition). Also, it is false to say that EFI Boot volume is entirely useless. Granted it might be a very rare occasion for most but I personally came across a situation(twice) where I desperately needed an EFI Boot volume to be there for me.
 
Especially as you'll end up with a yet another icon congesting the boot selector on APFS ROM patched machines otherwise.

Excuse me, @dosedude1 has done a great deal of work, and for most of us a great favor, with his workarounds, and he does it to help the majority of his patch users. If you use his "FREE" patch, and use most of it's capabilities to help make the installation of whatever OS you're on, easier, you should be grateful. Crying because you're so inconvenienced by an additional boot option, is really acting as if this "privilege" given to you for free, is your personal right, it's not. Why don't you sit down and figure out all these solutions, then come back with that same attitude, after someone complains. I doubt you'd still have this attitude. Just a lil' reality check. It's easy to lose our focus and our gratitude, but this man deserves to be thanked.
Use rEFInd.
 
  • Like
Reactions: TimothyR734
Hi, @Larsvonhier sorry if I'm a little OT: Do you have found a final fix to SIRI on Catalina B3 always crashing after opening it? Thank you!

Here is: Catalina B3 Siri non-metal fix

The only thing you won't have is the useless "oscilloscope wave animation", because it's metal rendered, but Siri works fine.
[doublepost=1563002554][/doublepost]
From my experience, you are not going to have three disks(just an EFI Boot and the APFS partition). Also, it is false to say that EFI Boot volume is entirely useless. Granted it might be a very rare occasion for most but I personally came across a situation(twice) where I desperately needed an EFI Boot volume to be there for me.

I know it's inconvenient but if you delete or don't have any "EFI disk0s1 volume" on your internal disk, you can plug and use any HFS+ formatted usb drive (diskXsY) acting as external EFI bootloader (for the internal volumes), that will contain surely another EFI diskXs1 volume, since any EFI/UEFI machine after power-on search first for a FAT32 Boot-able partition.

That said having the EFI partition internally is without doubt very handy.
 
Last edited:
Simply copying a HFS volume onto a APFS volume won't create the normal APFS boot partitions. You should see...

/dev/disk5 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +499.9 GB disk5
Physical Store disk1s2
1: APFS Volume Catalina HD - Data 47.0 GB disk5s1
2: APFS Volume Preboot 69.1 MB disk5s2
3: APFS Volume Recovery 761.9 MB disk5s3
4: APFS Volume VM 1.1 MB disk5s4
5: APFS Volume Catalina HD 10.4 GB disk5s5

The fact that you don't have an icon under the actual volume name for the APFS volume for the APFS ROM patched MacPro 3,1's option boot selector is a huge red flag.

I think it´s ok now. Thanks again, @jhowarth
 

Attachments

  • IMG_1424.jpeg
    IMG_1424.jpeg
    2.6 MB · Views: 167
  • Like
Reactions: TimothyR734
Here is: Catalina B3 Siri non-metal fix

The only thing you won't have is the useless "oscilloscope wave animation", because it's metal rendered, but Siri works fine.
[doublepost=1563002554][/doublepost]

I know it's inconvenient but if you delete or don't have any "EFI disk0s1 volume" on your internal disk, you can plug and use any HFS+ formatted usb drive (diskXsY) acting as external EFI bootloader (for the internal volumes), that will contain surely another EFI diskXs1 volume, since any EFI/UEFI machine after power-on search first for a FAT32 Boot-able partition.

That said having the EFI partition internally is without doubt very handy.

Thank you @jackduke (& @ASentientBot For the fix) It works fine :)
 
Last edited:
This is my Mojave sound setup on Macmini 2010.
The Vmicro USB 2.0 PC Camera SOUND IN option is missing on Catalina (not shown)
but the video feature works. Any idea about how to fix? (I'm using the writing option with Siri)

audio.png
 
Last edited:
This is my Mojave sound setup on Macmini 2010.
The Vmicro USB 2.0 PC Camera SOUND IN option is missing on Catalina (not shown)
but the video feature works. Any idea about how to fix? (I'm using the writing option with Siri)

Right, Macmini doesn't have an embedded microphone, but only a little output speaker.

To try fix it I guess you should use the 5 (five) IOUSB*.kext non-patched from Catalina and maybe removing the LegacyUSBInjector kext, I write this because your Macmini 2010 hardware is almost identical to the MacBook7,1 .

Or you could try to use a 3.5 mm microphone and plug in the proper audio input behind the macmini.

example: https://i.stack.imgur.com/E2j9i.png

edit:
Just for curiosity, how do you type/write in Siri instead of dictate ?
 
Last edited:
Right, Macmini doesn't have an embedded microphone, but only a little output speaker.

To try fix it I guess you should use the 5 (five) IOUSB*.kext non-patched from Catalina and maybe removing the LegacyUSBInjector kext, I write this because your Macmini 2010 hardware is almost identical to the MacBook7,1 .

Or you could try to use a 3.5 mm microphone and plug in the proper audio input behind the macmini.

example: https://i.stack.imgur.com/E2j9i.png

edit:
Just for curiosity, how do you type/write in Siri instead of dictate ?

@jackluke Luckily there is the right option in "Accessibility" , but I try your fix :)
 
hi there does anyone know when I will be able to use the install on this machine function of the macOS catilina patcher?
[doublepost=1563031636][/doublepost]I would also like to know would this run well on a mid 2010 MacBook Pro with a hdd too use with photoshop or should I stay on high Sierra?
 
  • Like
Reactions: TimothyR734
@jackluke Luckily there is the right option in "Accessibility" , but I try your fix :)

You may also check inside Catlaina Sys Pref - Security & Privacy (tab)
if in "Camera" or "Microphone" (left tab) something is disabled or unallowed.

But I guess it's something more related to the Catalina USB driver not properly loaded for the audio compartment.

For example I used a third party usb device with an el capitan driver that worked till Mojave, but on Catalina the driver is loaded but the device is not recognized (even if detected in system report).
 
hi there does anyone know when I will be able to use the install on this machine function of the macOS catilina patcher?
[doublepost=1563031636][/doublepost]I would also like to know would this run well on a mid 2010 MacBook Pro with a hdd too use with photoshop or should I stay on high Sierra?
I haven't implemented that feature yet, but you can just use an external drive to do the install.
 
Do we know whether the Preboot partition is actually used on unsupported Macs with legacy bootroms? That is, does one need an APFS savvy official bootrom or does the APFS ROM patch provide support for using that partition?
 
  • Like
Reactions: TimothyR734
On my Macbook 7,1 I made a partition for Catalina and it is installed but It does not let me boot from it when I look at what I can boot from my Catalina Partition does not show up My macbook was updated to High Sierra then to Mojave with dosdude1's patcher so I think it should support AFPS booting. Idk what to do
 
  • Like
Reactions: TimothyR734
was able to boot and install on my macbook pro 5,5 with new apfs boot loader
do I not need to run the post-install setup now after installing? seems to be working without
 
  • Like
Reactions: TimothyR734
was able to boot and install on my macbook pro 5,5 with new apfs boot loader
do I not need to run the post-install setup now after installing? seems to be working without

The post installer patcher runs automatically. You only need to run it again manually if you are installing Catalina over an existing installation (because the stale kernel cache inhibits the cache being rebuilt). In that case, you need to force the cache rebuild (which should become enabled as the default in a later Catalina Patcher release).
 
There is a thread on this from back in 2010. I found out the hardway that the Mac Pro 3,1 8-Core maximum memory is 56GB. That is with 6 slots at 8GB and 2 slots at 4GB. I was previously running 48GB with 4 slots 8Gb and 4 slots GB which also runs extremely well and it is possible that 48GB could be more performant than 56GB because you can pair things in two directions (on the Riser and between Banks A and B of the two risers). The theoretical max on an 8core machine is 64GB. However, with 64GB the performance is unusable and will lead to KP's right after IOConsoleUsers is loaded or after the login screen. Also, your RAM will become an Easy Bake oven.

Reference:
https://forums.macrumors.com/thread...e-48-gb-fast-disks-why.1940030/#post-22338450

Apple lists the max at 32GB. And that was either by design and/or chip availability. In an 8-core Mac Pro 3,1 the you can run 48GB or 56GB without issue. Just be sure to put your RAM in pairs and if you can get banks A and B on the two risers to match, that will be faster as well. Obviously this cannot be done with 56GB RAM, you will end up with 1 pair that does not match the other bank.

That said, 56GB system seems faster to me than 48GB, but I did change the VM setting, so I don't have an Apples to Apples comparison and no speed tests yet between 56 and 48GB.

The thread above also mentions a nvram vm compressor 2 setting that disables Swap. It will still allocate some disk space to the VM volume but the page ins and page outs should be 0.

Example:
VM: 1909G vsize, 1379M framework vsize, 0(0) swapins, 0(0) swapouts.

Somewhere I saw it mention that Virtual Machines will run faster too, but have not confirmed that as I am in the middle of installing fresh systems as I as troubleshooting that the issue was on my box. I did many upgrades in a short amount of time and discovered before even reading about it that 64GB RAM was not good on this box. Mac Pro 5,1 should not this issue.

I should have suspected this sooner but at the time as I did seem system crawl after 64GB RAM was installed. But I thought maybe the system was caching something. Then I thought power, but lack of power or a power overload usually shuts down a machine completely and this was KPing at startup when graphics card kicked in and it happened even on installer disks and other startup volumes that were not touched. At that point, it thought it was my GPU but after a little more troubleshooting and starting with just 32GB, I found it was memory all the long and Worked by way up from 32GB to 56GB.

My main reason for adding RAM is running older Virtual Machines on this box and testing CloneToolX with RAMDisks to speed up testing. It will be maybe twice as fast on this system. And I originally thought it would be cool to max out this box with the original intention of 64GB, but was able to at least get 56GB. So to anyone who was a Mac Pro 3,1 with 8-Cores I would go after 32GB, 48GB, or 56GB and you should be happy!
 
Last edited:
  • Like
Reactions: TimothyR734
There is a thread on this from back in 2010. I found out the hardway that the Mac Pro 3,1 8-Core maximum memory is 56GB. That is with 6 slots at 8GB and 2 slots at 4GB. I was previously running 48GB with 4 slots 8Gb and 4 slots GB which also runs extremely well and it is possible that 48GB could be more performant than 56GB because you can pair things in two directions (on the Riser and between Banks A and B of the two risers). The theoretical max on an 8core machine is 64GB. However, with 64GB the performance is unusable and will lead to KP's right after IOConsoleUsers is loaded or after the login screen. Also, your RAM will become an Easy Bake oven.

Reference:
https://forums.macrumors.com/thread...e-48-gb-fast-disks-why.1940030/#post-22338450

Apple lists the max at 32GB. And that was either by design and/or chip availability. In an 8-core Mac Pro 3,1 the you can run 48GB or 56GB without issue. Just be sure to put your RAM in pairs and if you can get banks A and B on the two risers to match, that will be faster as well. Obviously this cannot be done with 56GB RAM, you will end up with 1 pair that does not match the other bank.

That said, 56GB system seems faster to me than 48GB, but I did change the VM setting, so I don't have an Apples to Apples comparison and no speed tests yet between 56 and 48GB.

The thread above also mentions a nvram vm compressor 2 setting that disables Swap. It will still allocate some disk space to the VM volume but the page ins and page outs should be 0.

Example:
VM: 1909G vsize, 1379M framework vsize, 0(0) swapins, 0(0) swapouts.

Somewhere I saw it mention that Virtual Machines will run faster too, but have not confirmed that as I am in the middle of installing fresh systems as I as troubleshooting that the issue was on my box. I did many upgrades in a short amount of time and discovered before even reading about it that 64GB RAM was not good on this box. Mac Pro 5,1 should not this issue.

I should have suspected this sooner but at the time as I did seem system crawl after 64GB RAM was installed. But I thought maybe the system was caching something. Then I thought power, but lack of power or a power overload usually shuts down a machine completely and this was KPing at startup when graphics card kicked in and it happened even on installer disks and other startup volumes that were not touched. At that point, it thought it was my GPU but after a little more troubleshooting and starting with just 32GB, I found it was memory all the long and Worked by way up from 32GB to 56GB.

My main reason for adding RAM is running older Virtual Machines on this box and testing CloneToolX with RAMDisks to speed up testing. It will be maybe twice as fast on this system. And I originally thought it would be cool to max out this box with the original intention of 64GB, but was able to at least get 56GB. So to anyone who was a Mac Pro 3,1 with 8-Cores I would go after 32GB, 48GB, or 56GB and you should be happy!

The Max for 4-core 3,1 should be 32GB. I have not confirmed this, but later this week, I will be upgrading my 4-core box.
 
  • Like
Reactions: TimothyR734
The Max for 4-core 3,1 should be 32GB. I have not confirmed this, but later this week, I will be upgrading my 4-core box.

I did some upgrades to my 4-core Windows Mac Pro 3,1 and it will take 32GB RAM. For me I had to put all four 8gb chips on one riser. Splitting them up in pairs two risers lead to blinking white syndrome.

Another route would be to use 4gb chips on all bays, both risers.

When swapping out RAM, there is a white reset button behind the top riser. Always push this for 10 seconds. When the machine is plugged it you will see an amber light. If you don't do this, RAM can be read wrong, and may be a smaller size. This happens with 2GB, 1GB and 512MB chips. The chips may not be read on at, it the case of larger chips 4GB and 8GB. Always install in pairs of two. And you mix and match 800 Mhz / 667 Mhz chips, they will use the lower rate.
 
Last edited:
  • Like
Reactions: TimothyR734
I must have missed that i though it was a collaborative effort. Does ANYONE have a fix for apps like Maps and Photos? Is it even possible? If it's not I'd just like to know to downgrade.
Dosdude said that they are unlikely to work on non-metal systems. It's one of the reasons I reinstalled High Sierra. You can downgrade by downloading a copy of macOS from the App Store and creating a bootable drive, then reinstall. You will need to back up as it will wipe the drive.
 
  • Like
Reactions: TimothyR734
FYI, unless they have enhanced Disk Utility in Catalina, the only way to get the full partition APFS partition set is through a clean install. The Convert to APFS only converts the selected volume and doesn't collapse the individually converted APFS volumes into a single container.
Dosdude said that they are unlikely to work on non-metal graphics cards due to Metal requirements. It's one of the reasons I reinstalled High Sierra. You can downgrade by downloading a copy of macOS from the App Store and creating a bootable drive, then reinstall. You will need to back up as it will wipe the drive.

Works already now, with non-metal graphic cards, thanks to the geniality of @dosdude1 and @ASentientBot and we are only at first betas. I'm confident that I will have Catalina fully working before October's GM release.

maps.png
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.