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.
This comes right after the installer loads the stick. I can not get to the actual installation.

____

Das kommt direkt nachdem der Installer vom Stick geladen hat. Ich komme gar nicht zur eigentlichen Installation.
Thst’s not normal. Have you tired recreating the installer stick. And how large is your usb?
 
  • Like
Reactions: TimothyR734
So you have an official Apple installed BCM94360CD transplanted into a MacPro 3,1? If so, it would be interesting to know if the stock Catalina IO80211Family*.kext recognize that card or if you have to drop it back to the Mojave copies? If it isn't recognized, it would be really interesting to know if it was transplanted back into the original iMac 14,1 whether it becomes recognized by the stock Catalina IO80211Family*.kext.

That would depend if that card is available and is the interface same type that 3,1 accepts. Plus the 3,1 may have a different entry point to get its network working with may rely on the previous kext to access it. Also if it's an 802.11ac card, it would be an expensive replacement. 802.11n cards are much cheaper.
 
  • Like
Reactions: TimothyR734
One thing we should check is for differences with the
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext/Contents/Info.plist

<key>IOKitPersonalities</key>
<dict>
<key>Broadcom 802.11 PCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AirPort.BrcmNIC</string>
<key>IOClass</key>
<string>AirPort_BrcmNIC</string>
<key>IOMatchCategory</key>
<string>IODefaultMatchCategory</string>
<key>IONameMatch</key>
<array>
<string>pci14e4,43ba</string>
<string>pci14e4,43a3</string>
<string>pci14e4,43a0</string>
</array>
<key>IOProbeScore</key>
<integer>1400</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>TruePowerOff</key>
<true/>
</dict>

in Mojave to see if the IONameMatch keys have been reduced and if that would explain why the BCM94360CD wifi card isn't recognized by stock Catalina.

https://wikidevi.com/wiki/Broadcom_BCM94360CD shows the PCI id as http://pci-ids.ucw.cz/read/PC/14e4/43a0 so that the last entry there seems to be the match.
 
One thing we should check is for differences with the
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext/Contents/Info.plist

<key>IOKitPersonalities</key>
<dict>
<key>Broadcom 802.11 PCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AirPort.BrcmNIC</string>
<key>IOClass</key>
<string>AirPort_BrcmNIC</string>
<key>IOMatchCategory</key>
<string>IODefaultMatchCategory</string>
<key>IONameMatch</key>
<array>
<string>pci14e4,43ba</string>
<string>pci14e4,43a3</string>
<string>pci14e4,43a0</string>
</array>
<key>IOProbeScore</key>
<integer>1400</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>TruePowerOff</key>
<true/>
</dict>

in Mojave to see if the IONameMatch keys have been reduced and if that would explain why the BCM94360CD wifi card isn't recognized by stock Catalina.

https://wikidevi.com/wiki/Broadcom_BCM94360CD shows the PCI id as http://pci-ids.ucw.cz/read/PC/14e4/43a0 so that the last entry there seems to be the match.

This is the OSX Terminal command (possibly doing from your supported OSX ElCapitan/HighSierra) to get your AirPort (ARPT) Wifi PCI id:

ioreg -r -n ARPT | grep IOName

However adding in the Info.plist an additional <string>pci14e4,4xxx</string>

is not suffice, you have to binary patch your AirPortBrcmNIC.kext whitelisting your boardID to make the stock Catalina IO80211Family.kext working. I done it with AirPortBrcm4360.kext and everything is working .
 
On pre-2010 Mac you won't have the bluetooth OOB working on Catalina (especially in the Installer) , so you should use only usb-wired-keyboard/mouse (possibly plugged from the power-on) during the Catalina Installer.


My mouse and keyboard are plugged in via USB and they won't work at all and I still get that same screen. I've even tried to hit spacebar key (because I've read doing that will bypass that) with zero results
 
My mouse and keyboard are plugged in via USB and they won't work at all and I still get that same screen. I've even tried to hit spacebar key (because I've read doing that will bypass that) with zero results

You may try to use this in your Catalina Installer, download from dosdude1 repository the "macOS Catalina PartialPatcher.app"

Then show its packages /Contents/Resources/prelinkedkernel

copy this prelinkedkernel inside your /CatalinaInstaller/System/Library/Prelinkedkernels/

This should enable the very legacy USB kext.
 
Last edited:
Hello everyone. First of all, I wanna thanks everyone who is involved in making old MACs to run latest releases of macOS. I have MacBook Pro5.5 (C2D, without native APFS support), so I was wondering can I use @dosdude1 or @0403979 patchers to install Beta 2 on my MacBook Pro, or I have to wait for full patchers? I have tried dosdude's patcher, but right before end i get this message: "macOS could not be installed on your computer. An error occurred while updating systen extension information. Quit the installer to restart your computer and try again."
 
  • Like
Reactions: TimothyR734
One thing we should check is for differences with the
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext/Contents/Info.plist

<key>IOKitPersonalities</key>
<dict>
<key>Broadcom 802.11 PCI</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.driver.AirPort.BrcmNIC</string>
<key>IOClass</key>
<string>AirPort_BrcmNIC</string>
<key>IOMatchCategory</key>
<string>IODefaultMatchCategory</string>
<key>IONameMatch</key>
<array>
<string>pci14e4,43ba</string>
<string>pci14e4,43a3</string>
<string>pci14e4,43a0</string>
</array>
<key>IOProbeScore</key>
<integer>1400</integer>
<key>IOProviderClass</key>
<string>IOPCIDevice</string>
<key>TruePowerOff</key>
<true/>
</dict>

in Mojave to see if the IONameMatch keys have been reduced and if that would explain why the BCM94360CD wifi card isn't recognized by stock Catalina.

https://wikidevi.com/wiki/Broadcom_BCM94360CD shows the PCI id as http://pci-ids.ucw.cz/read/PC/14e4/43a0 so that the last entry there seems to be the match.
I posted previously that my BCM94360CD is working in Cat B2. The part of the Info list for CAT B2 is here:

<key>IOKitPersonalities</key>

<dict>

<key>Broadcom 802.11 PCI</key>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.driver.AirPort.BrcmNIC</string>

<key>IOClass</key>

<string>AirPort_BrcmNIC</string>

<key>IOMatchCategory</key>

<string>IODefaultMatchCategory</string>

<key>IONameMatch</key>

<array>

<string>pci14e4,43ba</string>

<string>pci14e4,43a3</string>

<string>pci14e4,43a0</string>

</array>

<key>IOProbeScore</key>

<integer>1400</integer>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>TruePowerOff</key>

<true/>

</dict>

This seems the same as Mojave to me. Mojave info list gives the same. However, I did use dosdude1's patcher so do not know what changes this made behind the scene. All I know is that I have wifi and bluetooth working fully with continuity, handoff and Airdrop all working. If you need any info let me know.
 
Hello everyone. First of all, I wanna thanks everyone who is involved in making old MACs to run latest releases of macOS. I have MacBook Pro5.5 (C2D, without native APFS support), so I was wondering can I use @dosdude1 or @0403979 patchers to install Beta 2 on my MacBook Pro, or I have to wait for full patchers? I have tried dosdude's patcher, but right before end i get this message: "macOS could not be installed on your computer. An error occurred while updating systen extension information. Quit the installer to restart your computer and try again."
A prerequisite of both our patchers is that you must either have native APFS support or use the APFS ROM Patcher.
 
I posted previously that my BCM94360CD is working in Cat B2. The part of the Info list for CAT B2 is here:

<key>IOKitPersonalities</key>

<dict>

<key>Broadcom 802.11 PCI</key>

<dict>

<key>CFBundleIdentifier</key>

<string>com.apple.driver.AirPort.BrcmNIC</string>

<key>IOClass</key>

<string>AirPort_BrcmNIC</string>

<key>IOMatchCategory</key>

<string>IODefaultMatchCategory</string>

<key>IONameMatch</key>

<array>

<string>pci14e4,43ba</string>

<string>pci14e4,43a3</string>

<string>pci14e4,43a0</string>

</array>

<key>IOProbeScore</key>

<integer>1400</integer>

<key>IOProviderClass</key>

<string>IOPCIDevice</string>

<key>TruePowerOff</key>

<true/>

</dict>

This seems the same as Mojave to me. Mojave info list gives the same. However, I did use dosdude1's patcher so do not know what changes this made behind the scene. All I know is that I have wifi and bluetooth working fully with continuity, handoff and Airdrop all working. If you need any info let me know.

You may try this: AirDrop function "Search for an Older Mac" for Catalina

That will add the extra AirDrop menu to discover and be discovered from legacy Mac that from Catalina supported Mac (or recent Broadcom Airport devices) has been dropped and also the ContinuityActivationTool developers are unaware of it.

Since your AirPort has been detected OOB, you just need this AirDropInfoView.nib
 
This is the OSX Terminal command (possibly doing from your supported OSX ElCapitan/HighSierra) to get your AirPort (ARPT) Wifi PCI id:

ioreg -r -n ARPT | grep IOName

However adding in the Info.plist an additional <string>pci14e4,4xxx</string>

is not suffice, you have to binary patch your AirPortBrcmNIC.kext whitelisting your boardID to make the stock Catalina IO80211Family.kext working. I done it with AirPortBrcm4360.kext and everything is working .
Do you have instructions patching it?
 
  • Like
Reactions: TimothyR734
Do you have instructions patching it?

Here

Not sure if you use the AirPortBrcm4360, but same method should apply also to the AirPortBrcmNIC.kext

Just open "AirPortBrcmNIC" unix exec with an hex editor search for this ASCII "Mac-" or its hex "4d 61 63 2d"

I have noticed that inside the AirPortBrcmNIC there are more AirPort functions, of course, since those Wifi Cards support natively continuity, handoff and other services.
 
Please use the -v flag at the end of the command for verbose output.
You can also hold down command-v at boot to do the same thing.

I keep my nvram set with -v. And with this I can always boot up single user mode by holding down command-s. And for safe mode command-x.

Just demonstrating you can do these options on the fly and just put your most popular one in nvram.
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.