Sidebar Sidebar
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

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.
nekton1 said:
The screenshots were taken on a Catalina-supported machine to show the relevant System Prefs settings locations.
I can take the same screenshots on the remaining affected machine if required but they add nothing and are in Japanese too!
It seems like the Romaji input setting is disabled in the patched Catalina—I think it is NOT related to the Legacy Video patch because one of the two affected machines is a MacPro 3,1 using a GTX680, so no Legacy Video patch. The other affected machine is the 2009 27" iMac 11,1, which I rolled back to Mojave and is now OK (and is using the Legacy Video patch).
Click to expand...

I remember once I downloaded some OTA packages from a japanese site (using the translator), and the OTA package was higher in size about 500 MB more than a standard US package.

Maybe the japanese input from Catalina is starting to be rendered through Metal, I mean apple to make them more precise and fast in output, especially on Safari web pages, documents or any other stock Catalina app.

If the issue is related to non-Metal (Video Legacy Patch) then a similar issue might apply also to other world languages that use their non-ASCII (UTF-8) text.

I guess these languages in their input encoding use more bytes per character, so imagine to render 500 pages for a pdf ebook, it requires some GPU help to render correctly any character, especially if you pinch-zoom on the document.
 
Hey guys, any idea why I have update my Mac Book Pro 7,2 to Mac OS 10.15 Catalina with the latest GM 19A582a version using DosDude's method, but it still says I'm on 10.15 Beta. Isn't the full version has been released?
 
KernkraftX360 said:
Hey guys, any idea why I have update my Mac Book Pro 7,2 to Mac OS 10.15 Catalina with the latest GM 19A582a version using DosDude's method, but it still says I'm on 10.15 Beta. Isn't the full version has been released?
Click to expand...

nope Catalina has not been released yet.
it's still in beta as far as I know..

A GM build however has been released :
2019/10/03 10.15.0 GM, build 19A582a, installer 15.0.32

See the first post of this thread, it's a wikipost and should informe you about the release updates of Catalina..
 
FlorisVN said:
nope Catalina has not been released yet.
it's still in beta as far as I know..

A GM build however has been released :
2019/10/03 10.15.0 GM, build 19A582a, installer 15.0.32

See the first post of this thread, it's a wikipost and should informe you about the release updates of Catalina..
Click to expand...

I downloaded DosDude's latest patch. Does the GM Build look like this?
Screen Shot 2019-10-06 at 19.17.41.png
 
Just, wondering, if the next Catalina OS would come up, am I eligible for OTA update, or do I need to update to the public release version using DosDude's Patcher again. OTA never works for me previously under previous Mac OS X. Thank you Floris, you've been helpful to me. Appreciate it.
 
KernkraftX360 said:
Just, wondering, if the next Catalina OS would come up, am I eligible for OTA update, or do I need to update to the public release version using DosDude's Patcher again. OTA never works for me previously under previous Mac OS X. Thank you Floris, you've been helpful to me. Appreciate it.
Click to expand...

I would advise you to wait to update/upgrade to the final version of catalina until the dosdude1 patcher or any other patcher out there is ready and tested for the final release..
mean while I would suggest you run Mojave/high sierra as a Main OS since this one is fully tested and optimised for patchers aswell as it is still not in beta stage.

doing an OTA update of catalina might break the patches your mac uses.
I personally always wait 1 year after a new MacOS release.
Then MacOS is almost bug free by apple, and the patcher tools are alsobug fixed and updated etc.
 
  • Like
Reactions: crjackson2134
Trying to get it running on an iMac 11,3 (mid-2010); everything works great (with GPU workaround) but I can't use the HomePods despite reconfiguring, resetting etc.
Any ideas what else to try? – Thank you!
 
dosdude1 said:
You can just use the "install to This Machine" option in DP8, that method is not affected by the ASR issue.
Click to expand...

Thanks alot, @dosdude1. Understood, but I do need the Legacy WiFi patch in order for my MBP4,1 17-inch to work. Is this specific patch being applied automatically, when I use the "install to this machine" method for the update from DP8 to GM? Else, how do I get the WiFi to work? I wouldn't have an external USB installer disk to boot from and apply the patch manually. Please advise.
 
Catalina GM installed without hitches on 2011 MacBook Pro 17 (dGpu software disabled).

Looking for a way to increase vram om the HD3000 in Catalina. This trick no longer seems to work.

forums.macrumors.com

How to increase vRAM for HD3000 graphics

Terminal command to increase vRAM for HD3000 graphics (Mac mini 2011 or MacBook Pro 2011) From *MB - The amount of vRAM you currently have. You can find it in System Profiler. From 256MB to 384MB From 256MB to 512MB From 384MB to 1GB From 384MB to 512MB From 512MB to 1GB (Thanks to...
forums.macrumors.com forums.macrumors.com
 
  • Like
Reactions: macinfo
This is one of my first time testing any Apple Beta MacOs’s and although I grabbed the final copy from the patcher and it’s the GM build under about this Mac it still says beta. Will I need to re-install once the official is released to the apple store to remove this or is there another way to remove the beta or is removing the beta is not enough the software will time out over time?
 
Larsvonhier said:
Just found that the previous constant crashing of Apple Maps seems to be fixed now with the golden master Catalina build (19A582a). Hope this keeps up to final release ;-)
Click to expand...
Yep same here, Maps works fine now. Looking forward to the release.

Created a 32GB Installer volume on an internal Sata2 SSD for the Patcher this time. So much faster than an USB stick.
 

Attachments

  • Cat GM1 & Maps.png
    Cat GM1 & Maps.png
    3.6 MB · Views: 169
Last edited:
osxfr33k said:
This is one of my first time testing any Apple Beta MacOs’s and although I grabbed the final copy from the patcher and it’s the GM build under about this Mac it still says beta. Will I need to re-install once the official is released to the apple store to remove this or is there another way to remove the beta or is removing the beta is not enough the software will time out over time?
Click to expand...
You can install all coming releases atop your GM beta. Or use the software updater (depends on how "unsupported" your machine is).
And no, there is no time-out or end of GM validity, so nothing to fear/lose.
 
  • Like
Reactions: TimothyR734
Granaten82 said:
Getting error message with kextbeast.
Click to expand...

Don't use that app, instead retry from a Catalina Terminal copy/paste this:

sudo mount -uw / ; killall Finder

open /System/Library/Extensions/

from Catalina Finder replace manually the two patched kext (overwrite all and do not merge) of your choice (1 gb or 1,5 gb or 2 gb)

return to the previous Catalina Terminal and copy/paste again (one line at once):

sudo chown -R 0:0 /System/Library/Extensions
sudo chmod -R 755 /System/Library/Extensions
sudo kextcache -i /
sudo reboot
 
  • Love
  • Like
Reactions: jdmc and Granaten82
The Video Legacy Patch is one theory but is contraindicated by:

1. It affects a MP3,1 with a metal-supported GTX680 GPU.
2. If direct keyboard input is set, the characters are displayed fine although it means learning a new keyboard layout.
3. If the Japanese ON-SCREEN keyboard is set to KANA input and used for input, the Japanese hiragana characters are displayed correctly as は　ひ　ふ　へ　ほ.
4. If the Japanese ON-SCREEN keyboard is set to Romaji input and used for input, the Japanese hiragana characters are NOT displayed and the phonetic equivalent is displayed (wrongly) as ha, hi, hu, he ho instead when it should be は　ひ　ふ　へ　ほ too.

If this were a Video Legacy Patch issue, IMO the Japanese on-screen keyboard would not work too.

To me, it seems as if the keyboard Romaji Japanese input method (Japan IM folder) is borked by the patch!

Screen Shot 2019-10-07 at 5.07.31.png


jackluke said:
I remember once I downloaded some OTA packages from a japanese site (using the translator), and the OTA package was higher in size about 500 MB more than a standard US package.

Maybe the japanese input from Catalina is starting to be rendered through Metal, I mean apple to make them more precise and fast in output, especially on Safari web pages, documents or any other stock Catalina app.

If the issue is related to non-Metal (Video Legacy Patch) then a similar issue might apply also to other world languages that use their non-ASCII (UTF-8) text.

I guess these languages in their input encoding use more bytes per character, so imagine to render 500 pages for a pdf ebook, it requires some GPU help to render correctly any character, especially if you pinch-zoom on the document.
Click to expand...
 
Last edited:
  • Like
Reactions: ASentientBot
nekton1 said:
The Video Legacy Patch is one theory but is contraindicated by:

1. It affects a MP3,1 with a metal-supported GTX680 GPU.
2. If direct keyboard input is set, the characters are displayed fine although it means learning a new keyboard layout.
3. If the Japanese ON-SCREEN keyboard is set to KANA input and used for input, the Japanese hiragana characters are displayed correctly as は　ひ　ふ　へ　ほ.
4. If the Japanese ON-SCREEN keyboard is set to Romaji input and used for input, the Japanese hiragana characters are NOT displayed and the phonetic equivalent is displayed (wrongly) as ha, hi, hu, he ho instead when it should be は　ひ　ふ　へ　ほ too.

If this were a Video Legacy Patch issue, IMO the Japanese on-screen keyboard would not work too.

To me, it seems as if the keyboard Romaji Japanese input method (Japan IM folder) is borked by the patch!
Click to expand...

If it's not a Metal issue, then from your pictures apple finder menus and prefpanes are displayed correctly in japanese, have you tried to type text from another text-editor or Pages.app or any third-party app ?

Or you may try to replace from Mojave the /S/L/Input Methods/ folder in Catalina (take a backup first).
 
  • Like
Reactions: ASentientBot
Yes, I have tried text edit, Pages, Word, web and all are affected.

I had thought about moving that Input Method folder too from Mojave but the System volume is locked and I was too tired to look up the terminal command to unlock it!

Will try it now.

jackluke said:
If it's not a Metal issue, then from your pictures apple finder menus and prefpanes are displayed correctly in japanese, have you tried to type text from another text-editor or Pages.app or any third-party app ?

Or you may try to replace from Mojave the /S/L/Input Methods/ folder in Catalina (take a backup first).
Click to expand...
[automerge]1570395355[/automerge]
Offhand, could you please tell me what's the terminal command to unlock the System volume so I can swap the IM folder for the Mojave one?
 
Last edited:
I successfully installed Catalina GM on my Mac Pro 3.1 with the latest catalina patcher from dosdude1.

I have a Nvidia GTX 770. Displayport is also MIA with this video card. I suppose it's the same problem reported by nekton1.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back