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
Wasalaam to you z
Thanks for that. When I initially tried Mojave, the screen would never sleep or dim and via email DosDude said it was a known issue - although I only tried it when it first came out so perhaps he patched it afterwards (I reverted back to high Sierra). I will try again with Mojave and see if it works again or not and then go to Catalina (still haven't done so in my 2015 supported Mac!). The MikeyN thing - is that the only thing you need to add or did you need to move the AMDRadeonX3000.kext and add the line to loginhook in order to disable the discrete GPU?
Hoping for some help. 2009 MacPro 4,1 upgraded to 5,1 firmware. I'm able to create bootable Catalina USB drive with DosDude patcher. After install on fresh SSD (with APFS), it just boots back up to the USB and says there is no OS installed on SSD. If I remove USB, I just get flashing question mark folder (no OS found). It looks like the USB copies files (install DMG) to my new hard drive, but never actually installs the OS. Any ideas what's gone wrong?
Sounds like your system firmware/BootROM is out of date. Ensure you're running the latest 144.0.0.0.0 version. If not, use a Mojave installer app to update.
Will i be running into problems, trying to 'update ' to Catalina on my Late 2009 Imac 27 11,1
and ATI Radeon HD 4850
and ATI Radeon HD 4850
Is anyone experiencing sleep/wake issues with its iMac 27" 2011 under Catalina using a GTX765M flashed by Nick Bios?
I am either getting a black screen (no backlight) or the screen stays black (backlight is on) with a mouse cursor when trying to wake up the iMac. I have to restart the iMac manually or it will restart automatically.
I can't tell if it's the Catalina upgrade that brought this or flashing the GPU. Before, using High Sierra with the default Bios, the iMac would wake up normally.
BTW, I have applied all the Catalina patches from Dosdude list.
I am either getting a black screen (no backlight) or the screen stays black (backlight is on) with a mouse cursor when trying to wake up the iMac. I have to restart the iMac manually or it will restart automatically.
I can't tell if it's the Catalina upgrade that brought this or flashing the GPU. Before, using High Sierra with the default Bios, the iMac would wake up normally.
BTW, I have applied all the Catalina patches from Dosdude list.
I have similar setup but never faced issues. Only thing is when you startup the iMac you will get black screen for couple of minutes. So wait for the iMac to boot fully and then the display will be visible with apple logo grey screen and bang to your desktop.
If you are getting black screen for longer than 2 mins approx then your bios has not been flashed correctly. You have to look into that.
Second issue maybe the display cable is damaged so you need to replace it.
Also check by tilting the display ab bit what led indicators are showing as glowing on the logic board.
I mentioned above points because I went through all above when I installed my 765M graphics card.
Hope to see your iMac running.
I have similar setup but never faced issues. Only thing is when you startup the iMac you will get black screen for couple of minutes. So wait for the iMac to boot fully and then the display will be visible with apple logo grey screen and bang to your desktop.
If you are getting black screen for longer than 2 mins approx then your bios has not been flashed correctly. You have to look into that.
Second issue maybe the display cable is damaged so you need to replace it.
Also check by tilting the display ab bit what led indicators are showing as glowing on the logic board.
I mentioned above points because I went through all above when I installed my 765M graphics card.
Hope to see your iMac running.
The boot screen is showing up, no issues here.
I can either select High Sierra which I still have on my Internal HDD or Catalina (10.15.2) on my internal SSD. It's that when I am using Catalina, if the computer has to go to sleep, it will not wake up.
At first, I could see the backlight with a mouse cursor but screen was black. Now I am getting a restart if I try to wake it up pressing a key.
I could have end up ripping off a component on the GPU or motherboard but the thing is, under High Sierra, sleep/wake works fine still.
I've done a PRAM reset and it did not help fixing this issue.
Any other idea?
SMC reset, followed by a three bong NVRAM reset.
Last edited:
Does anyone have any idea how I can convert macOS Catalina 10.15.2 from APFS back to HFS + without data loss? The Paragon Tool APFS to HFS + does not work with a Hackintosh, does it? someone has a tip.
Convert is risky... make a backup using CCC and restore to an HFS+ partition
I am using High Sierra on a MacBook Pro 4,1 (Early 2008 Macbook Pro) with an HFS+ formatted SSD. Would like to upgrade to Catalina 10.15.2, do I have to do a clean install or in-place upgrade is possible? Is it possible to convert the SSD to APFS without issues or data loss? Do I have to go through Mojave installation before, or in-place jump to Catalina is possible with the latest patch tool and how?
So many questions...grateful for any help/suggestions. I already CCCloned the High Sierra SDD to an external disk and patched it, for safety. But would like the upgrade process to be as much smooth as possible.
Thanks
So many questions...grateful for any help/suggestions. I already CCCloned the High Sierra SDD to an external disk and patched it, for safety. But would like the upgrade process to be as much smooth as possible.
Thanks
Convert is risky... make a backup using CCC and restore to an HFS+ partition
In my last tests with version 5.1.14 (5780) it didn't work.
Can you please tell me the exact order? as I can restore it from an image from
Catalina 10.15.2 back to HFS +.
@overshoot I have an HFS + partition, slightly larger than the APFS partition, CCC always formats this HFS + in APFS with 2 partitions. It is NOT possible to convert an image from catalina 10.15.2 disk utility as an APFS image to an HFS + with only 1 partition. How did you do that because you write it would work ???
Thank you very much for that.
work this true with last version CCC ?
In my last tests with version 5.1.14 (5780) it didn't work.
Can you please tell me the exact order? as I can restore it from an image from
Catalina 10.15.2 back to HFS +.
@overshoot I have an HFS + partition, slightly larger than the APFS partition, CCC always formats this HFS + in APFS with 2 partitions. It is NOT possible to convert an image from catalina 10.15.2 disk utility as an APFS image to an HFS + with only 1 partition. How did you do that because you write it would work ???
Thank you very much for that.
work this true with last version CCC ?
Last edited:
Is your hdd/ssd formatted APFS and have you checked your drive for any errors and are you using Catalina Patcher 1.3.0
Hi S,
with the patcher 1.3.0 you actually should not move the AMDRadeonX3000.kext from Extensions (otherwise the system crashes). Dosdude seems to have solved that kext issue with a workaround mod of kext. (Kudos to him). Even though Catalina boots fine after applying the 1.3.0 on its own, I did however still keep the Extensions-off with the AMDRadeonX3000.kext and created a the Loginhook in /Library as per MikeyN. I don't know if that is redundant but it doesn't seem to affect or conflict with boot and proper function of OS or apps under the 1.3.0 patcher setup. I created the shell script force-iGPU-boot.sh that executes the lengthy nvram "bypass" of dGPU at boot for the dGPU in case I need to do a reset of PRAM (Nvram) as this will revert back to boot via dGPU. btw if you do apply the "reset" of nvram to bypass the defective dGPU whether in its long form or shell script procedure you will at each boot up go through the "verbose" process as with MikeyN procedure. However if you reinstall with Patcher 1.3.0 you just boot through the usual Apple boot screen.
I find that even on a vintage 8,2 Catalina works slightly better than Mojave (where with the dosdude latest patchers I had no screen sleep/Dim issues at that time). With Catalina I also run with increased HD 3000 graphics RAM to 1536MB thinking that I would see an improvement using Parallels Desktop 15 (since certain programs I occasionally use run under W10 only) and Photoshop 2020 and very occasional basic Avid editing. However, I haven't seen any qualitative improvement performance wise. I am a total newbie (just like to experiment enough to be dangerous but backing up every time) and maybe an expert might tell me that apart from gaming I wouldn't see any kind of perceptible improvement in increasing HD 3000 VRAM. Bslama
Last edited:
Before I begin let me thank you all for the excellent work behind these great patches. I can only imagine the painstaking care you put into them, and for sure I appreciate the results I see on my ten yers old MacBookPro 5,3.
I installed Catalina 10.15.2 through Dosdude1 patcher ver. 1.3.0. I'm experiencing sleep problems, with the mac randomly rebooting some time after I close the lid. Here is what the log shows:
Any idea on what I could do to solve the problem?
I installed Catalina 10.15.2 through Dosdude1 patcher ver. 1.3.0. I'm experiencing sleep problems, with the mac randomly rebooting some time after I close the lid. Here is what the log shows:
Code:
panic(cpu 0 caller 0xffffff8002ca295c): Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.
Failure code:: 0xd5f2a20d 00000031
Backtracing specified thread
Backtrace (CPU 0), Frame : Return Address
0xffffff810e9cb900 : 0xffffff8002660088
0xffffff913a09b980 : 0xffffff800255d6f1
0xffffff913a09b9f0 : 0xffffff800255beef
0xffffff913a09ba40 : 0xffffff800254cae0
0xffffff913a09ba80 : 0xffffff7f83958aaa
0xffffff913a09bac0 : 0xffffff7f8396fe07
0xffffff913a09bad0 : 0xffffff8002c4084b
0xffffff913a09bb00 : 0xffffff7f83cd478b
0xffffff913a09bb50 : 0xffffff8002c421a8
0xffffff913a09bbb0 : 0xffffff7f83cce019
0xffffff913a09bbf0 : 0xffffff7f8396566b
0xffffff913a09bc10 : 0xffffff7f83960c3c
0xffffff913a09bc50 : 0xffffff8002c1431f
0xffffff913a09bcc0 : 0xffffff8002c2caa0
0xffffff913a09bd60 : 0xffffff8002c14b49
0xffffff913a09bdb0 : 0xffffff8002c2a151
0xffffff913a09be50 : 0xffffff8002c265ce
0xffffff913a09bea0 : 0xffffff8002c23f83
0xffffff913a09bef0 : 0xffffff8002c23e20
0xffffff913a09bf30 : 0xffffff8002c3f612
0xffffff913a09bf70 : 0xffffff8002c3eb9c
0xffffff913a09bfa0 : 0xffffff80024e213e
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(519.15)[D5F2A20D-CAB0-33B2-91B9-E8755DFC34CB]@0xffffff7f83950000->0xffffff7f83998fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1286D5E5-A6A1-3C44-A244-04C068903DB2]@0xffffff7f82f2f000
com.apple.driver.AppleMuxControl(3.28.4)[EB8D7A77-E073-36EB-A5B1-A3672CA840A3]@0xffffff7f83cca000->0xffffff7f83cdcfff
dependency: com.apple.driver.AppleGraphicsControl(3.28.4)[200F1816-A734-3977-B7AE-7A6B2363059F]@0xffffff7f83c89000
dependency: com.apple.iokit.IOACPIFamily(1.4)[3467C105-9354-3BD2-85F3-E5AEF94BD275]@0xffffff7f83277000
dependency: com.apple.iokit.IOPCIFamily(2.9)[1286D5E5-A6A1-3C44-A244-04C068903DB2]@0xffffff7f82f2f000
dependency: com.apple.iokit.IOGraphicsFamily(519.15)[D5F2A20D-CAB0-33B2-91B9-E8755DFC34CB]@0xffffff7f83950000
dependency: com.apple.AppleGraphicsDeviceControl(3.28.4)[400C2E21-0880-36D7-AC5E-6B9BC885F158]@0xffffff7f83c7a000
BSD process name corresponding to current thread: kernel_task
Boot args: -no_compat_check
Mac OS version:
19C57
Kernel version:
Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64
Kernel UUID: C3E7E405-C692-356B-88D3-C30041FD1E72
Kernel slide: 0x0000000002200000
Kernel text base: 0xffffff8002400000
__HIB text base: 0xffffff8002300000
System model name: MacBookPro5,3 (Mac-F22587C8)
System shutdown begun: NO
Panic diags file available: YES (0x0)
System uptime in nanoseconds: 4841948725074
last loaded kext at 2233778204961: >!AGraphicsDevicePolicy 3.28.4 (addr 0xffffff7f85c7d000, size 77824)
last unloaded kext at 2629788787842: @nvidia.NVDAStartup 14.0.0 (addr 0xffffff7f85c77000, size 12288)
loaded kexts:
com.intel.kext.intelhaxm 7.5.4
com.parrotgeek.SIPManager 1
@nke.rvi 2.0.0
@filesystems.smbfs 3.4
@fileutil 20.036.15
@filesystems.autofs 3.0
>AudioAUUC 1.70
@filesystems.ntfs 3.14.3
>AGPM 110.23.46
>!AMikeyHIDDriver 131
>!AHDA 281.52
@AGDCPluginDisplayMetrics 3.28.4
>!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.2f4
>pmtelemetry 1
@Dont_Steal_Mac_OS_X 7.0.0
>ACPI_SMC_PlatformPlugin 1.0.0
>!A!ISlowAdaptiveClocking 4.0.0
>!ASMCLMU 212
>!ALPC 3.1
>!AMuxControl 3.28.4
>AGDCBacklightControl 4.5.21
>!AUpstreamUserClient 3.6.8
>!AMCCSControl 1.5.6
>!AFWOHCI 5.6.2
@GeForceTesla 10.0.4
>SMCMotionSensor 3.0.4d1
>!AMikeyDriver 281.52
>!UTCButtons 255
>!UTCKeyboard 255
>!AIR!C 360
>!UCardReader 489.60.3
>!AVirtIO 1.0
@filesystems.hfs.kext 522.0.9
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
|SCSITaskUserClient 422.0.2
@private.KextAudit 1.0
@filesystems.apfs 1412.61.1
>AirPort.Brcm4331 800.21.31
@nvenet 2.0.22
>!AAHCIPort 341.0.2
>!ASmartBatteryManager 161.0.0
>!ARTC 2.0
>!AHPET 1.8
>!AACPIButtons 6.1
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
>!A!ICPUPowerManagement 222.0.0
|EndpointSecurity 1
@kext.triggers 1.0
|IOFireWireIP 2.3.0
>DspFuncLib 281.52
@kext.OSvKernDSPLib 529
|IOAVB!F 800.17
>!ASSE 1.0
>IOPlatformPluginLegacy 1.0.0
@!AGPUWrangler 3.28.4
|IOSlowAdaptiveClocking!F 1.0.0
>IOPlatformPlugin!F 6.0.0d8
>!AGraphicsControl 3.28.4
@!AGraphicsDeviceControl 3.28.4
>!ABacklightExpert 1.1.0
|IOFireWire!F 4.7.5
@nvidia.classic.NVDANV50HalTesla 10.0.4
>!AHDA!C 281.52
|IOHDA!F 281.52
>!ASMBus!C 1.0.18d1
@nvidia.classic.NVDAResmanTesla 10.0.4
>!ASMBusPCI 1.0.14d1
|IONDRVSupport 519.15
|IOGraphics!F 519.15
@plugin.IOgPTPPlugin 800.14
|IOEthernetAVB!C 1.1.0
|IOSkywalk!F 1
|Broadcom!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CTransport 7.0.2f4
|IO!B!F 7.0.2f4
|IO!BPacketLogger 7.0.2f4
>!UMultitouch 264
>usb.!UHub 1.2
>usb.IOUSBHostHIDDevice 1.2
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
|IOAudio!F 300.2
@vecLib.kext 1.2.0
|IOSerial!F 11
|IOSurface 269.6
@filesystems.hfs.encodings.kext 1
|IOSCSIMultimediaCommandsDevice 422.0.2
|IOBD!S!F 1.8
|IODVD!S!F 1.8
|IOCD!S!F 1.8
|IOAHCISerialATAPI 268
|IOAHCIBlock!S 316.40.3
|IO80211!F 1200.12.2
>corecapture 1.0.4
>usb.!UEHCIPCI 1.2
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
>!AEFINVRAM 2.1
>usb.!UOHCIPCI 1.2
>usb.!UOHCI 1.2
>usb.!UEHCI 1.2
>NVSMU 2.2.9
|IOAHCI!F 290.0.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$quarantine 4
$sandbox 300.0
[USER=381322]@Kext[/USER].!AMatch 1.0.0d1
>DiskImages 493.0.0
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!AKeyStore 2
>!UTDM 489.60.3
|IOSCSIBlockCommandsDevice 422.0.2
>!ACredentialManager 1.0
>KernelRelayHost 1
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
|IOUSBMass!SDriver 157.40.7
|IOSCSIArchitectureModel!F 422.0.2
|IO!S!F 2.1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
|CoreAnalytics!F 1
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
|IOTimeSync!F 800.14
|IONetworking!F 3.4
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC 3.1.9
>watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1Any idea on what I could do to solve the problem?
Last edited:
Please put that in a codeblock. To answer the question, it might be something to do with the acceleration wrappers.
If I had to guess, it's something related to the dual GPU related kext replacements, rather than the wrapped frameworks. I don't know a lot about those systems though since I have a single-GPU machine. @jackluke might!
Does it happen often @B-G? If you can turn on the
keepsyms=1 boot argument, the backtrace will be much more informative.Noob question here: should I do that by the following terminal command?
sudo nvram boot-args="keepsyms=1"
I'd say that there is a 40 to 50 % chance of the system rebooting after entering sleeping. It doesn't do that every time, and so far I've not been able to isolate a plausible cause for this behaviour.
sudo nvram boot-args="keepsyms=1"
I'd say that there is a 40 to 50 % chance of the system rebooting after entering sleeping. It doesn't do that every time, and so far I've not been able to isolate a plausible cause for this behaviour.
MBP 4,1 here. I followed the video tutorial and succeded in creating the patch installer USB drive, formatted the internal ssd to APFS and started the installation. But in the middle of the second phase (after the reboot and right after the apple logo screen becomes white on black) the installer turns to a gray screen and redirects me to the recovery utility instead of ending the installation. No errors appear, just quietly goes back to the recovery. What should I do to make the installation correctly finish the process?
One minute after posting the above, I solved it myself by pressing Option while the installation rebooted middle way, and choosing the “Mac installer” disk (or similar name, not one of the two EFI boot options).