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.
@dosdude1 Strange issue. Used the Patcher 1.2 and my Mac (MBA 2013) downloaded Catalina Beta 15.0.15 instead of the GM. I'm not enrolled to the Beta program. Anyone has an idea (besides downloading via AppStore)? I want to create a stick for my MP3,1.
I confirm this, Patcher 1.2.0 last night downloaded installer 15.0.15 when I tried to download 2nd supplemental (should be 15.0.34, build 19A603). Before, 15.0.33, build 19A602 was downloaded OK; that's what I am running at present.
 
Last edited:
  • Like
Reactions: TimothyR734
Yesterday I was able to download Catalina 19A603 via the dosdude1 app. If things got messed on Apple servers since, you can try to download it from the App Store. For those use Clover, you can boot with a changed SMBIOS or System Definition of a supported Mac to be able to get it. Indeed, as far as I know, Apple does give updated install macOS apps for beta builds after the official release, you need to install macOS from App Store on the latest non-beta build, the enrol the machine into the Apple Beta program and download the latest beta build install via System Preferences. You have the technical details on the Apple web site.
 
  • Like
Reactions: TimothyR734
For all the beginners out there: battery is just as important as the motherboard, its purpose goes far beyond the portability. Your trackpad issues has nothing to do with running unsupported systems.

The battery is important for performance, but it has nothing to do with the trackpad, unless it’s still in place and swollen to the point where it pushed against the trackpador associated components. It has worked fine without a battery for the past three years except for CPU speed being slow. It also worked fine the first time I installed Catalina, but then for some reason it didn’t. Now I’m running El Capitan again and the trackpad is fine.

I really appreaciate and respect the people who work hard to let us run macOS on unsupported systems. It was a fun project for me to try, but in the end it didn’t live up to the standard I want from a computer. It’s not for me, but I know a lot of people are happy with it. Great stuff 👍🏻
 
  • Like
Reactions: TimothyR734
The battery is important for performance, but it has nothing to do with the trackpad, unless it’s still in place and swollen to the point where it pushed against the trackpador associated components. It has worked fine without a battery for the past three years except for CPU speed being slow. It also worked fine the first time I installed Catalina, but then for some reason it didn’t. Now I’m running El Capitan again and the trackpad is fine.

I really appreaciate and respect the people who work hard to let us run macOS on unsupported systems. It was a fun project for me to try, but in the end it didn’t live up to the standard I want from a computer. It’s not for me, but I know a lot of people are happy with it. Great stuff 👍🏻

All good, the choice is always yours. The regulars of the unsupported threads know very well that your issue is trivial and came up quite a few times here and in Mojave thread as well.
 
  • Like
Reactions: TimothyR734
In about the past 36 hours, Patch Updater displayed on my Mid 2009 Macbook (5,2) running Catalina 19A602 (installed using dosdude1's Catalina Patcher 1.1.9), an alert announcing "Backlight Control Patch" was available, so I let Patch Updater install it. It's version 0. I was hoping it would bring back F1/F2 brightness up/down key functionality on my model, but it didn't--instead, though the F1/F2 keys now brightened and dimmed the backlight, with the brightness control feedback icon showing more bars or fewer bars accordingly, the brightness then changed to about two bars worth of brightness, and stayed there until I pressed the F1/F2 keys again, but again each time, brightness settled back to about two bars.

So I did some searching here on the Catalina on Unsupported Macs forum, using the term "backlight", and found a recent post by Larsvonhier (https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27900070) referring to dosdude1's standalone patch for F1/F2 which he posted in December 2018, at https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-447#post-26927734. It's for these models:
  • MacBook5,2
  • iMac7,1
  • iMac8,1
  • iMac9,1
  • MacBookPro4,1 (17" model only)
I had forgotten about this patch, which I had installed at the time, after I had updated to Mojave 10.14.4 (which broke the previous F1/F2 patch), so I reinstalled it again today, and that fixed my F1/F2 keys under Catalina.

As user 'unilock' says at https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27900448, before running this script, you'll need to enter this into Terminal, to remount the startup volume as writable:

sudo mount -uw /; killall Finder

…then run the script by entering this into Terminal:

cd /path/to/bkltpatch10.14.2
./install.sh
 
Last edited:
In about the past 36 hours, Patch Updater displayed on my Mid 2009 Macbook (5,2) running Catalina 19A602 (installed using dosdude1's Catalina Patcher 1.1.9), an alert announcing "Backlight Control Patch" was available, so I let Patch Updater install it. It's version 0. I was hoping it would bring back F1/F2 brightness up/down key functionality on my model, but it didn't--instead, though the F1/F2 keys now brightened and dimmed the backlight, with the brightness control feedback icon showing more bars or fewer bars accordingly, the brightness then changed to about two bars worth of brightness, and stayed there until I pressed the F1/F2 keys again, but again each time, brightness settled back to about two bars.

So I did some searching here on the Catalina on Unsupported Macs forum, using the term "backlight", and found a recent post by Larsvonhier (https://forums.macrumors.com/threads/macos-10-15-catalina-on-unsupported-macs.2183772/post-27900070) referring to dosdude1's standalone patch for F1/F2 which he posted in December 2018, at https://forums.macrumors.com/thread...ed-macs-thread.2121473/page-447#post-26927734. It's for these models:
  • MacBook5,2
  • iMac7,1
  • iMac8,1
  • iMac9,1
  • MacBookPro4,1 (17" model only)
I had forgotten about this patch, which I had installed at the time, after I had updated to Mojave 10.14.4 (which broke the previous F1/F2 patch), so I reinstalled it again today, and that fixed my F1/F2 keys under Catalina.
How do you installed this patch? I tried to install it but it brings me a lot of errors. If I execute "sudo ./install.sh", I can see errors about permissions. So i first made a "sudo /sbin/mount -uw /" and then i execute the first sentence, but the errors now are "no such file or directory" and "kext with invalid signature". I have got a macbook 5.2 too.

"csrutil status" Shows me that all configurations are "disabled".

I tried to boot with the pen drive of OSX and execute it in terminal, but i could't do it too.

How did you do it?

Another thing... I have a macbook 5.1 too and the brightness control works well as it. I think that the hardware of both computers are very similar, so i'm confused with this.
 
Last edited:
  • Like
Reactions: TimothyR734
How do you installed this patch? I tried to install it but it brings me a lot of errors. If I execute "sudo ./install.sh", I can see errors about permissions. So i first made a "sudo /sbin/mount -uw /" and then i execute the first sentence, but the errors now are "no such file or directory" and "kext with invalid signature". I have got a macbook 5.2 too.

"csrutil status" Shows me that all configurations are "disabled".

I tried to boot with the pen drive of OSX and execute it in terminal, but i could't do it too.

How did you do it?

Another thing... I have a macbook 5.1 too and the brightness control works well as it. I think that the hardware of both computers are very similar, so i'm confused with this.
MB5,1 has a very different HW compared to MB5,2 and does not need any CCFL patch (it is a unibody alu macbook and has LED backlight).

As for the script: Be sure to mount writable (as you did) and also cd into the path where the script is, otherwise relative path arguments do not work and files will not be found by the script. Only after that, fire up the script from there!
 
MB5,1 has a very different HW compared to MB5,2 and does not need any CCFL patch (it is a unibody alu macbook and has LED backlight).

As for the script: Be sure to mount writable (as you did) and also cd into the path where the script is, otherwise relative path arguments do not work and files will not be found by the script. Only after that, fire up the script from there!
I think that i'm doing all that you are saying. I think that i'm doing something wrong but i don't know what it is.

I can see this in Terminal when i try to execute the patch.

Code:
Blanquito:bkltpatch10.14.2 marcos$ sudo /sbin/mount -uw /
Password:
Blanquito:bkltpatch10.14.2 marcos$ sudo ./install.sh
rm: /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AGDCBacklightControl.kext: No such file or directory
cp: cannot overwrite directory /System/Library/PrivateFrameworks/DisplayServices.framework/Resources with non-directory DisplayServices.framework/Resources
cp: cannot overwrite directory /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/Current with non-directory DisplayServices.framework/Versions/Current
Kext with invalid signature (-67054) allowed: <OSKext 0x7fa4365231a0 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/AMDRadeonX4000HWServices.kext/", ID = "com.apple.kext.AMDRadeonX4000HWServices" }
Kext with invalid signature (-67030) allowed: <OSKext 0x7fa436657480 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/IOSurface.kext/", ID = "com.apple.iokit.IOSurface" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fa437810a60 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/IONetworkingFamily.kext/", ID = "com.apple.iokit.IONetworkingFamily" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fa437880f00 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/AppleBacklightExpert.kext/", ID = "com.apple.driver.AppleBacklightExpert" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fa437912c20 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/AppleHDA.kext/", ID = "com.apple.driver.AppleHDA" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fa437976640 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/GeForceTesla.kext/", ID = "com.apple.GeForceTesla" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fa43798ca60 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/IO80211Family.kext/", ID = "com.apple.iokit.IO80211Family" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fa4379b1130 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/AppleGraphicsControl.kext/", ID = "com.apple.driver.AppleGraphicsControl" }
Kext with invalid signature (-67030) allowed: <OSKext 0x7fa437aa7850 [0x7fff954c8b00]> { URL = "file:///Library/Extensions/NDRVShim.kext/", ID = "com.parrotgeek.NDRVShim" }
Kext with invalid signature (-67030) allowed: <OSKext 0x7fa4365022a0 [0x7fff954c8b00]> { URL = "file:///Library/Extensions/LegacyUSBVideoSupport.kext/", ID = "com.parrotgeek.LegacyUSBVideoSupport" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fa437aeb1f0 [0x7fff954c8b00]> { URL = "file:///Library/Extensions/LegacyUSBInjector.kext/", ID = "com.parrotgeek.LegacyUSBInjector" }
Kext with invalid signature (-67050) allowed: <OSKext 0x7fa437b34ba0 [0x7fff954c8b00]> { URL = "file:///Library/Extensions/SIPManager.kext/", ID = "com.parrotgeek.SIPManager" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fe9f6ec0630 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/IONetworkingFamily.kext/", ID = "com.apple.iokit.IONetworkingFamily" }
Kext with invalid signature (-67050) allowed: <OSKext 0x7fe9f82781c0 [0x7fff954c8b00]> { URL = "file:///Library/Extensions/SIPManager.kext/", ID = "com.parrotgeek.SIPManager" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fe9f81f2180 [0x7fff954c8b00]> { URL = "file:///Library/Extensions/LegacyUSBInjector.kext/", ID = "com.parrotgeek.LegacyUSBInjector" }
Kext with invalid signature (-67030) allowed: <OSKext 0x7fe9f81c37b0 [0x7fff954c8b00]> { URL = "file:///Library/Extensions/LegacyUSBVideoSupport.kext/", ID = "com.parrotgeek.LegacyUSBVideoSupport" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fe9f8163370 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/AppleGraphicsControl.kext/", ID = "com.apple.driver.AppleGraphicsControl" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fe9f8088a40 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/IO80211Family.kext/", ID = "com.apple.iokit.IO80211Family" }
Kext with invalid signature (-67062) allowed: <OSKext 0x7fe9f8078500 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/GeForceTesla.kext/", ID = "com.apple.GeForceTesla" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fe9f6ff4ab0 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/AppleHDA.kext/", ID = "com.apple.driver.AppleHDA" }
Kext with invalid signature (-67030) allowed: <OSKext 0x7fe9f6cc6a90 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/IOSurface.kext/", ID = "com.apple.iokit.IOSurface" }
Kext with invalid signature (-67054) allowed: <OSKext 0x7fe9f6fb5770 [0x7fff954c8b00]> { URL = "file:///System/Library/Extensions/AppleBacklightExpert.kext/", ID = "com.apple.driver.AppleBacklightExpert" }
Invalid signature -67050 for kext <OSKext 0x7fe9f82781c0 [0x7fff954c8b00]> { URL = "file:///Library/Extensions/SIPManager.kext/", ID = "com.parrotgeek.SIPManager" }
Invalid signature -67030 for kext <OSKext 0x7fe9f81c37b0 [0x7fff954c8b00]> { URL = "file:///Library/Extensions/LegacyUSBVideoSupport.kext/", ID = "com.parrotgeek.LegacyUSBVideoSupport" }
KernelCache ID: 30E032AE0BD0ED8E4305B020B57325A8
Blanquito:bkltpatch10.14.2 marcos$

Any idea to solve this?
 
  • Like
Reactions: TimothyR734
@hal90088
Seems all right (ignore the cannot copy messages, that´s ok and does not cause non-functioning), even a new prelinked kext is generated in the end.
The only thing that is different from my outcome is the last to invalid kext lines for USBvideo and SIPmanager. One should be tha patch for iSight and the other takes care of always-off SIP state.
I´d suggest you hop into one of the many kext tools (kext wizard i.e.) and see what kexts are actually really loaded after logging in to the UI.
 
  • Like
Reactions: TimothyR734
I have been serching for a solution for the last few days since installing Catalina on my late 2009 imac. My wifi card shows airdrop is supported and i have the airdrop icon in finder but nothing else. I went through some of your instructions below but dont understand how to find the driver etc. my mac boardID
Mac-F2268DC8.

Would appreciate the assistance.



I guess I found a fix to make working again AirDrop (from Catalina Finder) on unsupported Catalina Mac

Premise: I have noticed that starting from Catalina, AirDrop feature requires a Bluetooth 4.0 device (internal or USB) in order to be showed in the Finder, and to detect the other Mac and iOS devices connected on the same wifi network.
While till Mojave it was still possible to find older Mac and iOS devices even without a BT 4.0 dongle.

Before start, this method: https://apple.lib.utah.edu/airdrop-how-to-enable-on-os-x-mavericks-via-ethernet/
doesn't worked on Catalina, it just enables a Finder AirDrop icon without any functionality, and more over (if worked) was only for ethernet connected Mac, not Wifi Mac/devices.


Here is how I made and understood "my fix":

First of all I observed that both on my MacBookPro2010 (i5 cpu dualGPUs) and MacBook7,1 (core2duo cpu Nvidia) the driver used for my Wifi Airport Broadcom was this: kextstat | grep AirPort

com.apple.driver.AirPort.Brcm4331

Then looking at the "Continuity Activation Tool" I understood that the allowed Wifi Broadcom driver to support AirDrop over a BT 4.0 device is this com.apple.driver.AirPort.Brcm4360

So using a couple of BT 4.0 USB dongle, with "continuityactivationtool" I have attempted to partial fix whitelisting (without touching the IOBluetooth) inside the AirPortBrcm4360 binary file the machine boardID, but it can also be done manually, open Terminal and copy/paste:

ioreg -l | grep "board-id" | awk -F\" '{print $4}'

from output get your boardID for example: Mac-F22C89C8 (MacBook7,1 mid 2010)
And opening inside IO80211Family.kext the "AirPortBrcm4360 binary exec" using an hex editor (or other method) whitelist this boardID from "ascii to hex" searching for "Mac-" in hex becomes "4d 61 63 2d".
Typically the first occurrence should be suffice, but I've swapped all the other encountered for safety and to catch any possible additional function adding only that boardID (example picture attached).
Since the older machine boardID numbers are shorter, after added your (ascii-to-hex) boardID add an octet of "00" (example picture attached).

Response: it worked!

I attach for now only a "fix" tested and working for MacBook7,1 mid 2010 , and before replacing the attached kext, from Catalina Terminal:
sudo mount -uw / ; killall Finder ; open /S*/L*/E*/IO80211Family.kext/C*/P*/

Then back to Terminal and type:
sudo chown -R 0:0 /S*/L*/E*
sudo chmod -R 755 /S*/L*/E*
sudo kextcache -i /


I attached also the non-patched AirPortBrcm4331.kext because I discovered that Wifi Airport Broadcom can use both 4331 and 4360 , in fact the "PCI Match device id" for this Broadcom wifi is present (from HighSierra, Mojave) in both the driver Info.plist : <string>pci14e4,4353</string>

So if my patch for some reason doesn't work on your machine your wifi will use the other driver, but I repeat the patch I posted is only for MacBook7,1 mid 2010.

I add also another for MacBookPro6,2 15" mid 2010 dualGPUs (in the specified folder).

The file attached allows to enable the AirDrop feature on Catalina Finder, and if you plug a Bluetooth 4.0 dongle it should work too and detect all the devices inside the same wifi network (with "discovered by Everyone" checked).
 
  • Like
Reactions: TimothyR734
I have been serching for a solution for the last few days since installing Catalina on my late 2009 imac. My wifi card shows airdrop is supported and i have the airdrop icon in finder but nothing else. I went through some of your instructions below but dont understand how to find the driver etc. my mac boardID
Mac-F2268DC8.

Would appreciate the assistance.

The fact you have the AirDrop icon in Finder doesn't tell much, in order to check if enabling AirDrop on your iMac 2009 is still possible with Catalina, you should post also the output of these Terminal commands (copy/paste):

ioreg -r -n ARPT | grep IOName

system_profiler -detailLevel mini | grep "Card Type"
 
  • Like
Reactions: TimothyR734
Hello,
What is going on with the CUDA and Nvidia drivers for Catalina?

I need CUDA and Nvidia drivers for the EVGA GTX 680 4GB Mac Edition for OSX Catalina. It was working properly with OSX Mojave. It also works now with Catalina but slower. Will they release any new drivers or they stopped for ever? What I have to do, change system?

Also:
I have installed a Quadro K5000 4GB Mac Edition on a Mac Pro 3.1. It was working fine with the OSX Mojave and previous OSXs, connected with two monitors LG 27EA83 (2560x1440) via 1x DVI and 1x DisplayPort, working on full resolution. I installed the new OSX Catalina and after that the GFX Card does not work properly. That means only the two DVI ports give signal, the one of them on full resolution and the other at 1920x1080, which is normal. The problem is that the two DisplayPorts do not work at all and I cannot get the maximum resolution of the card video output. I mention that the Nvidia website has not announced the drivers for Quadro K5000 for OSX Catalina yet and the system works with the default macOS Graphics Driver. My question is when/where I can get the proper drivers which will make the GFX card work properly. Is the drivers the main issue or I have to take other action? The system is working professionally for video editing and the GFX card is the heart, as you understand, it is a big problem for 15 days now.

Kind Regards,

I don't think it's a driver issue, but configuration. I was able to get DisplayPort to function using Clover's boot loader. However, I did notice some stability issues with things like Safari hanging and haven't looked into it much further. I using Mojave for my production work, but when where is time, I will mess around with Catalina and the DisplayPort some more.
 
  • Like
Reactions: TimothyR734
For the purpose of the backlight here times following note.
On my Hackintosh Thinkpad T61p I have been working with Rollback "AppleBacklight.kext and AppleBacklightExpert.kext" for a long time from Capitan for Sierra / HS / Mojave / Catalina.
Both Kext's are still working with Catalina.
Maybe it's better than patching all the new Kext's, right?
It's worth a try.

Edit:
AirDrop with Atheros is now broken too.
Are there solutions for Atheros with Catalina?
 
  • Like
Reactions: TimothyR734
Hi can anybody help me? I have an MacBook Pro 5.x and I tried to install the patcher via the USB boot Catalina. However, everything goes well, until I have selected the HDD and the installation should start. There will always be a message saying "An error occurred while preparing to install. Try running the program again." I have already corrected the date with the terminal (so I have to set the date of the site so Germany or another), have repeatedly created the USB stick with the patcher and formatted the SSD as APFS. What am I doing wrong? I also can not reinstall El Capitan. Please help! Thank you very much
 
Last edited:
  • Like
Reactions: TimothyR734
Hi,

I need an advice : what best usb "bluetooth/wifi" dongle for my MP3,1 running Catalina ?

Many thanks in advance,


Serviteur

You can't have an unique "bluetooth/wifi usb dongle", but rather a Bluetooth 4.0 usb dongle (any third-party vendor should work), and another 802.11 Wifi usb dongle , I have tried some of them, and noticed that while a "Bluetooth 4.0 usb dongle" works with Catalina stock Bluetooth kext, a Wifi usb dongle needs a proper driver/kext that till Mojave worked with an El Capitan one, however many cheap usb wifi dongles are made with these chips (and these drivers): https://www.mediatek.com/products/connectivity-and-networking/broadband-wifi
 
  • Like
Reactions: TimothyR734
What? There's no battery in the computer anymore. It went bad many years ago. rEFInd found the partition I made for the patched installer just fine, and the Xubuntu partition. I guess the special boot configuration for the patched Catalina isn't compatible with rEFInd out of the box.

I can't use it for long until I get symptoms from the flickering screen anyways so what software I use is not that important. I'm just going to use it for rtl-sdr (Xubuntu) and Navigraph Charts (macOS) until I can afford a new MacBook. Catalina worked better than expected on it, but I can't be bothered to go though the process to get everything working, and I assume updates need some post install work to be done.
Trackpad preferences is NOT WORKING without the battery in High Sierra and newest.
It’s a weird bug, but if you think about this all the High Sierra compatibles MB have a non removable battery, so it’s thinking there is a mismatch and show this error.
 
https://devtalk.nvidia.com/default/...ivers-be-released-for-macos-10-15-catalina-/1

Highly unlikely at this point, especially since Apple has depreciated the MacPro 5,1 from support in Catalina. They seems to be just waiting to age out the Nvidia systems entirely.

Display port is the reason for staying in Mojave, as DP is a must for me and do not wish to use , time being, the method advised in earlier ports, by using Hackintosh boot methods.
MacPro3,1 GTX 780 Mac efi rom (Macvidcards)
 
  • Like
Reactions: TimothyR734
Hello. I have a problem with my MacBook Air Mid 2011, I can't install Catalina with Catalina patcher because when I try to install it the window opens and says ''an error occurred while preparing the installation. Try running this application again.'' Please help me, thanks
 
Hello. I have a problem with my MacBook Air Mid 2011, I can't install Catalina with Catalina patcher because when I try to install it the window opens and says ''an error occurred while preparing the installation. Try running this application again.'' Please help me, thanks

Same problem, but nobody can help anymore?
 
  • Like
Reactions: TimothyR734
Catalina 10.15.0 release (build 19A583, installer 15.0.32) running well on my MBP5,2 17", mid 2009.

First cloned the internal SSD Mojave 10.14.6 to a frehsly APFS formatted external SSD (Samsung 840 EVO). Installed Catalina over it with dosdude's patcher 1.1.7 via USB installer. Also installed Nightshift with the patch updater. Checked again stability and performance like with the betas. Then swapped SSDs - Catalina is now on SATA as production system! TRIM support is on. Mojave SSD kept in reserve to be connected to USB just in case.

Everything behaves very stable. Prepared a lengthy Keynote presentation today: the MBP will travel with me to a physics+computing workshop in Kathmandu, and I'm confident it will not cause any problems. Yet I'll take the USB installer with me, and the Mojave SSD, and a screwdriver.

What a pleasure. Thanks Dosdude, ASentientBot and all contributors!

Running with the 9600M GT, dark mode, reduced transparency to reduce the work for the graphics. The machine is a bit slower than with Mojave it seems, which may be due to photoanalysisd and CalendarAgent activity in the background.

(MBP5,2 17" mid 2009, 2.8GHz T9600, 8GB, APFS ROM patch applied, Samsung SSD 840 EVO with APFS, Catalina 10.15.0.)

Try also to unmount unused USB pendrives and partitions. My CPU IDLE charge drops from 37% to 10% simply removing an HFS+ Mojave backup...
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.