macOS 10.15 Catalina on Unsupported Macs

[Flacko]

What do you have for the Bluetooth fields...

Chipset: 20702B0
Firmware Version: v150 c9317

If there really is a difference at play here, we should see a pattern on those values for the ones that are working.

Exactly the same. Here are the fields for the trackpad.

And the USB for the card.

 

[Hindrik1997]

Newest Beta works flawlessly on my Mac Pro 3,1 with GTX 670. Thanks!

In hindsight, it seems that my WiFi card is not detected in Catalina, whereas it was in Mojave. Has anything changed regarding support for those things? (Not sure which Broadcom chip I have, as it doesn't show up anymore in system information)

 

[Flacko]

In hindsight, it seems that my WiFi card is not detected in Catalina, whereas it was in Mojave. Has anything changed regarding support for those things? (Not sure which Broadcom chip I have, as it doesn't show up anymore in system information)

If you still have the original wifi (have not upgraded the hardware to a BCM94360 for example) then you will need to patch the wifi using the post install patcher. Try the Broadcom BCM4321 Wifi support patch.

 

[iMac-Oldschool]

3th part developers will release ONLY Metal graphic apps (when running on official MacOS 10.15) or limitations will be only related to Cat native applications? Because we can easily survive without Apple Maps and Apple Photo. Google alternatives are much better ;-)

I’m very reluctant to give up Apple Photo. My installation includes a supported iMac13,1 and an unsupported iMac8,1. Consistently in the apps on the two systems is the main reason for following this thread. Don’t agree that Google offerings are “much better”, sorry.

 

[gyorgy]

Since you are on a MacPro 5,1 and should have native APFS support in your firmware, make sure that you select Disable APFS Boot in the Catalina patcher when creating the patched usb installer. Otherwise you will be install the APFS Boot Patch. I would also mount the s1 partition on your target drive to see the contents of the EFI partition and delete the three apfs.efi related files that are installed (two are in the EFI subdirectory if I recall correctly).

Thank you for your help.
This could be indeed the cause, but while creating the Catalina patcher I am not getting the option to disable the APFS Boot patch.

 

[jackluke]

This agrees to what I have experienced. The BCM94360CD works OOB with Catalina. In fact I have found this so since Mojave 14.4. In Cat B4 IO80211Family.kext has a create date of 12 July, Mojave 14.5 a date of 12 March. Also, the Mojave version has the AirportBrcm4331.kext in the plugins. This is missing in the Cat version, so dosdude's patcher did not replace the IO80211Family.kext as far as I can see. I never select any wifi patches post install.

Just guessing here but are all BCM94360CD cards identical? I upgraded to this card several years ago and believe it was what is called a "genuine" Apple Card from an iMac. Are the ones available today exactly the same as this or could there be some variations causing the differing results members are achieving.

As for the breakage of the Trackpad preferences pane. Just to be clear, I have not experienced this in either a clean install or an install over the top of Mojave.

I guess you're right, the "trackpad.prefpane" issue could be addressed to the IO80211Family.kext that from Catalina beta4 (as every other main binary) has a modified date by apple of 12 July.

Because this "AirPort combo BT/Wifi" even if the two modules are apparently independent instead they are dependent, so for those who upgraded their AirPort cards to a BT 4.0 one, they should de-select the "Wifi-Patch".

For instance the "Wifi-Patch" should include all these: IO80211Family.kext, IO80211FamilyV2.kext, corecapture.kext

So these 3 should remain the Catalina stock ones, I'd check for safety also the IOBluetooth*.kext that are from Catalina one they must have internally the date of 12 July 2019 , if their date is different then are surely the "patched" version.

Anyway I guess it would be helpful if you share the output of these so the other can compare the right kext-loaded version in use, open a Catalina Terminal:

kextstat | grep Brcm
kextstat | grep AirPort
kextstat | grep Bluetooth
kextstat | grep IO80211

 

[jhowarth]

In hindsight, it seems that my WiFi card is not detected in Catalina, whereas it was in Mojave. Has anything changed regarding support for those things? (Not sure which Broadcom chip I have, as it doesn't show up anymore in system information)

What is does the system profiler under patched Mojave show for the Card Type field under the Wifi section?

 

[jhowarth]

I guess you're right, the "trackpad.prefpane" issue could be addressed to the IO80211Family.kext that from Catalina beta4 (as every other main binary) has a modified date by apple of 12 July.

Because this "AirPort combo BT/Wifi" even if the two modules are apparently independent instead they are dependent, so for those who upgraded their AirPort cards to a BT 4.0 one, they should de-select the "Wifi-Patch".

For instance the "Wifi-Patch" should include all these: IO80211Family.kext, IO80211FamilyV2.kext, corecapture.kext

So these 3 should remain the Catalina stock ones, I'd check for safety also the IOBluetooth*.kext that are from Catalina one they must have internally the date of 12 July 2019 , if their date is different then are surely the "patched" version.

Anyway I guess it would be helpful if you share the output of these so the other can compare the right kext-loaded version in use, open a Catalina Terminal:

kextstat | grep Brcm
kextstat | grep AirPort
kextstat | grep Bluetooth
kextstat | grep IO80211

When I checked the versions of the IO80211Family.kext, IO80211FamilyV2.kext, corecapture.kext files on my MacPro 3,1, I they seemed to be the Catalina versions and not those from the Resources subdirectories in the post install patcher application. My impression was that Dosdude1 has coded in the past to check whether such patches really need to be applied for the currently installed hardware before their kexts are actually installed by the patches.

It would be nice if the post install patcher would log the exact kext that are installed in a text file somewhere on the target drive so one could quickly check those. The Patch Updater's list of installed patches is pretty useless on that count because patches exist that don't actually install kext when they aren't needed.

[doublepost=1563795329][/doublepost]

Thank you for your help.
This could be indeed the cause, but while creating the Catalina patcher I am not getting the option to disable the APFS Boot patch.

When you launch 1.0b11, you'll find a menu item for Disable APFS Booter in the menu bar. It isn't presented in the installer splash screens but has to be manually selected each time you launch the Catalina Patcher to recreate the usb installer. It would be nice if Catalina Patcher 'remembered' the last selection of Disable APFS Booter across launches but you still would have to remember to reselect it when using a new release of the Catalina Patcher.

 

[gyorgy]

When you launch 1.0b11, you'll find a menu item for Disable APFS Booter in the menu bar. It isn't presented in the installer splash screens but has to be manually selected each time you launch the Catalina Patcher to recreate the usb installer. It would be nice if Catalina Patcher 'remembered' the last selection of Disable APFS Booter across launches but you still would have to remember to reselect it when using a new release of the Catalina Patcher.

Thanks again!
I will give it a try and report back.

 

[Flacko]

I guess you're right, the "trackpad.prefpane" issue could be addressed to the IO80211Family.kext that from Catalina beta4 (as every other main binary) has a modified date by apple of 12 July.

Because this "AirPort combo BT/Wifi" even if the two modules are apparently independent instead they are dependent, so for those who upgraded their AirPort cards to a BT 4.0 one, they should de-select the "Wifi-Patch".

For instance the "Wifi-Patch" should include all these: IO80211Family.kext, IO80211FamilyV2.kext, corecapture.kext

So these 3 should remain the Catalina stock ones, I'd check for safety also the IOBluetooth*.kext that are from Catalina one they must have internally the date of 12 July 2019 , if their date is different then are surely the "patched" version.

Anyway I guess it would be helpful if you share the output of these so the other can compare the right kext-loaded version in use, open a Catalina Terminal:

kextstat | grep Brcm
kextstat | grep AirPort
kextstat | grep Bluetooth
kextstat | grep IO80211

IOBluetooth*.kext are all Catalina B4 - dated 12 Jul. Here is the output requested. Airport did not produce an output. Hope they may be of use.

 

[jackluke]

IOBluetooth*.kext are all Catalina B4 - dated 12 Jul. Here is the output requested. Airport did not produce an output. Hope they may be of use.
View attachment 849377

It's case-sensitive you should type "AirPort", but the result for AirPort and Brcm is the same.

I confirm that you are using the stock Wifi/BT kext Catalina beta4 (19A512f), I've compared with a supported Mac of mine and they match exactly:

AirPortBrcm* driver version: 1400.1.1
IO80211Family* driver version: 1200.12.2b1
IOBluetooth* driver version: 7.0.0d98

kextstat | grep AirPort
   77    0 0xffffff7f82022000 0x585000   0x585000   com.apple.driver.AirPort.Brcm4360 (1400.1.1) 61FE8F2D-D39C-3626-88DD-F7A799ADFB19 <76 74 71 18 13 8 7 6 5 3 1>

kextstat | grep IO80211
   76    1 0xffffff7f81eb9000 0x15b000   0x15b000   com.apple.iokit.IO80211Family (1200.12.2b1) D3EEA567-D500-3207-8E94-ABA9560E0E7E <75 74 21 18 10 8 7 6 5 3 1>

kextstat | grep Bluetooth
  112    0 0xffffff7f835ce000 0x3000     0x3000     com.apple.iokit.IOBluetoothUSBDFU (7.0.0d98) D497DF2A-9AC1-3D52-84D1-ECC401C3A621 <27 5 3>
  113    1 0xffffff7f830b6000 0xf000     0xf000     com.apple.iokit.IOBluetoothPacketLogger (7.0.0d98) EFC0826E-C914-369D-846E-8BEB604F7C5B <7 6 5 3 1>
  114    3 0xffffff7f830c5000 0xfd000    0xfd000    com.apple.iokit.IOBluetoothFamily (7.0.0d98) 0CA39A55-9046-3F05-A8FF-A017C5A33E55 <113 27 17 12 8 7 6 5 3 1>
  115    2 0xffffff7f83523000 0xb000     0xb000     com.apple.iokit.IOBluetoothHostControllerTransport (7.0.0d98) 1261671C-9E84-395E-B41E-7BDE4AA4FEA3 <114 27 13 12 8 7 6 5 3 1>
  116    1 0xffffff7f835ec000 0x22000    0x22000    com.apple.iokit.IOBluetoothHostControllerUSBTransport (7.0.0d98) 27D417CA-48F9-3466-B9D7-DB56C81CC2D2 <115 114 27 13 12 8 7 6 5 3 1>
  117    0 0xffffff7f8360e000 0xd000     0xd000     com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (7.0.0d98) 39AFF0EB-4BF1-3BFC-A028-9087CBB4C3DA <116 115 114 27 13 12 8 7 6 5 3>
  152    0 0xffffff7f8361f000 0xa000     0xa000     com.apple.iokit.IOBluetoothSerialManager (7.0.0d98) 17975E46-E2A6-3066-99FA-13DFFC74D20E <100 8 6 5 3 1>

I guess those who encountered issues with a "combo AirPort BT/Wifi" are not using the stock Catalina kext.

 

[Flacko]

It's case-sensitive you should type "AirPort", but the result for AirPort and Brcm is the same.

I confirm that you are using the stock Wifi/BT kext Catalina beta4 (19A512f), I've compared with a supported Mac of mine and they match exactly:

AirPortBrcm* driver version: 1400.1.1
IO80211Family* driver version: 1200.12.2b1
IOBluetooth* driver version: 7.0.0d98

kextstat | grep AirPort
   77    0 0xffffff7f82022000 0x585000   0x585000   com.apple.driver.AirPort.Brcm4360 (1400.1.1) 61FE8F2D-D39C-3626-88DD-F7A799ADFB19 <76 74 71 18 13 8 7 6 5 3 1>

kextstat | grep IO80211
   76    1 0xffffff7f81eb9000 0x15b000   0x15b000   com.apple.iokit.IO80211Family (1200.12.2b1) D3EEA567-D500-3207-8E94-ABA9560E0E7E <75 74 21 18 10 8 7 6 5 3 1>

kextstat | grep Bluetooth
  112    0 0xffffff7f835ce000 0x3000     0x3000     com.apple.iokit.IOBluetoothUSBDFU (7.0.0d98) D497DF2A-9AC1-3D52-84D1-ECC401C3A621 <27 5 3>
  113    1 0xffffff7f830b6000 0xf000     0xf000     com.apple.iokit.IOBluetoothPacketLogger (7.0.0d98) EFC0826E-C914-369D-846E-8BEB604F7C5B <7 6 5 3 1>
  114    3 0xffffff7f830c5000 0xfd000    0xfd000    com.apple.iokit.IOBluetoothFamily (7.0.0d98) 0CA39A55-9046-3F05-A8FF-A017C5A33E55 <113 27 17 12 8 7 6 5 3 1>
  115    2 0xffffff7f83523000 0xb000     0xb000     com.apple.iokit.IOBluetoothHostControllerTransport (7.0.0d98) 1261671C-9E84-395E-B41E-7BDE4AA4FEA3 <114 27 13 12 8 7 6 5 3 1>
  116    1 0xffffff7f835ec000 0x22000    0x22000    com.apple.iokit.IOBluetoothHostControllerUSBTransport (7.0.0d98) 27D417CA-48F9-3466-B9D7-DB56C81CC2D2 <115 114 27 13 12 8 7 6 5 3 1>
  117    0 0xffffff7f8360e000 0xd000     0xd000     com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (7.0.0d98) 39AFF0EB-4BF1-3BFC-A028-9087CBB4C3DA <116 115 114 27 13 12 8 7 6 5 3>
  152    0 0xffffff7f8361f000 0xa000     0xa000     com.apple.iokit.IOBluetoothSerialManager (7.0.0d98) 17975E46-E2A6-3066-99FA-13DFFC74D20E <100 8 6 5 3 1>

I guess those who encountered issues with a "combo AirPort BT/Wifi" are not using the stock Catalina kext.

Many thanks Jackluke. This now confirms that the BCM94360 works OOB with Catalina and hopefully nothing changes in the future releases. Those with issues can now compare the kext stat outputs to see if anything shows up.

 

[0134168]

Problems here also. Works like a charm in Mojave in my Mac Pro 3.1. And worked like a charm in Catalina Beta 3, with patcher 1.0b8. With Catalaina Beta 4 and 1.0b11 patcher simply can´t connect to wifi. Finds the avalaible wifi nets and then looses, looping every few seconds.

After the third try, everything works like a charm. Wifi and bluetooth rock solid now. Only thing I did different is not install the Broadcom Patch

 

[alexcorpse]

install beta 4 catalline without problems but after installing everything well install hd 3000 dosdude1 v3 restart a kernel panic from the other part of mojave delete telemetry.plugin and replace iosurface restart and gray display I have installed ioacceleratorfamily2, ioaccerator2d.plugin, coredisplay, skylight .framework, opengl.framework and I continue with gray display with mouse excuse my English this is in an unsoported mac hackintosh

 

[TimothyR734]

you need to have the latest Catalina patcher http://dosdude1.com/catalina/ and apply the post install patches

 

[0134168]

install beta 4 catalline without problems but after installing everything well install hd 3000 dosdude1 v3 restart a kernel panic from the other part of mojave delete telemetry.plugin and replace iosurface restart and gray display I have installed ioacceleratorfamily2, ioaccerator2d.plugin, coredisplay, skylight .framework, opengl.framework and I continue with gray display with mouse excuse my English this is in an unsoported mac hackintosh

Hackintosh its diferent stuff.

 

[DuncanGarp]

I have this Unsupported (for both Mojave and Catalina) MacbookPro5,3.

The 2 OSs were installed on an internal SSD both formatted APFS using dosdude1's respective patchers - v1.3.3 for Mojave, 1.0b11 for Catalina.

I can boot up to both but here's the weird situation.

In order to boot on either, I have to boot up first to the respective patcher, run post install and rebuild cache and then reboots fine to the specific OS. I cannot just go to SystemPreferences | Startup to select the SSD partition to boot to.

In other words, in order to switch default boots, I have to run the patcher steps above.

Hope that my explanation is clear. Thanks for any input on why this happens.

P.S. If I go to Restart | Option key pressed, I see the "EFI" as the SSD drive designation.

 

[alexcorpse]

with catallina public beta 2 perfect work I do not know why gray display I have replaced everything that has to do with hd 3000 but nothing

 

[TimothyR734]

I have this Unsupported (for both Mojave and Catalina) MacbookPro5,3.

The 2 OSs were installed on an internal SSD both formatted APFS using dosdude1's respective patchers - v1.3.3 for Mojave, 1.0b11 for Catalina.

I can boot up to both but here's the weird situation.

In order to boot on either, I have to boot up first to the respective patcher, run post install and rebuild cache and then reboots fine to the specific OS. I cannot just go to SystemPreferences | Startup to select the SSD partition to boot to.

In other words, in order to switch default boots, I have to run the patcher steps above.

Hope that my explanation is clear. Thanks for any input on why this happens.

P.S. If I go to Restart | Option key pressed, I see the "EFI" as the SSD drive designation.

Have you tried selecting the the startup disk using the patcher

 

[jackluke]

@ASentientBot Mojave 10.14.6 has been final released, what do you think in refreshing your SkyLight patch for the next Catalina beta 5 ?

 

[ASentientBot]

@ASentientBot Mojave 10.14.6 has been final released, what do you think in refreshing your SkyLight patch for the next Catalina beta 5 ?

Oops, I totally lost track of the Mojave thread. I'll download that soon and compare the two SkyLight versions, as well as making sure that the other new files from Mojave (I think just ethernet/wifi drivers on my 2010 MacBook, not sure about others) will still work on Catalina. As you suggest, I'll definitely be using those versions for DP5, assuming that no unexpected issues come up.

Thanks for keeping me updated!

 

[avz]

I have this Unsupported (for both Mojave and Catalina) MacbookPro5,3.

The 2 OSs were installed on an internal SSD both formatted APFS using dosdude1's respective patchers - v1.3.3 for Mojave, 1.0b11 for Catalina.

I can boot up to both but here's the weird situation.

In order to boot on either, I have to boot up first to the respective patcher, run post install and rebuild cache and then reboots fine to the specific OS. I cannot just go to SystemPreferences | Startup to select the SSD partition to boot to.

In other words, in order to switch default boots, I have to run the patcher steps above.

Hope that my explanation is clear. Thanks for any input on why this happens.

P.S. If I go to Restart | Option key pressed, I see the "EFI" as the SSD drive designation.

This is normal. Clearly you did not applied the APFS ROM PATCH. Some time ago dosdude1 has implemented a custom boot selector but I am not sure if that project is still current.

 

[0403979]

Oops, I totally lost track of the Mojave thread. I'll download that soon and compare the two SkyLight versions, as well as making sure that the other new files from Mojave (I think just ethernet/wifi drivers on my 2010 MacBook, not sure about others) will still work on Catalina. As you suggest, I'll definitely be using those versions for DP5, assuming that no unexpected issues come up.

Thanks for keeping me updated!

Unless the 10.14.6 SkyLight framework requires less work for your wrapper, I don’t think it really makes sense to use it instead of the 10.14.5 SkyLight just because it’s newer. If, on the other hand, it lessens the amount of code required, then it’d be a nice gift.

 

[haralds]

OTA of 10.14.6 on MacBook Air 4,1. All went reasonably well including follow up patch booting from DosDue patcher. The Patch Updater also loaded for update the System Updater and Legacy Video Card Patch.
The latter seems to stall, it is quite speedy from standalone boot. I am using FileVault2, but its obviously unlocked running the main system.
Is the live Legacy Video Card Patch different than the one from the USB stick? According to release notes, they both address the same issue.

 

[jhowarth]

The 10.14.6 release has clarified that a non-loaded IOBluetoothUSBDFU kext should have no relationship to the broken Trackpad in patched Catalina. The patched 10.14.6 has a functional Trackpad system preference panel but the IOBluetoothUSBDFU kext now doesn't load (unlike in patched 10.14.5 where it did).

Update: It turns out that 10.14.6 now is loading the IOBluetoothUSBDFU. It is unclear if launching the Trackpad system preference panel caused that. If so, I assume I should find some symbols from IOBluetoothUSBDFU in the Trackpad system preference panel binary.

Update2: Okay, we can really rule out IOBluetoothUSBDFU. I was able to use...

sudo kextutil /System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothUSBDFU.kext

under patched DP4 to force it to load and that still leaves Trackpad failing to launch with the 'Preference Error Could not load Trackpad preference pane.'.