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.
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.
This was about a flag for my patcher’s verbose.
 
  • Like
Reactions: TimothyR734
After tested thoroughly this method: fix AirDrop on Catalina unsupported Mac with AirPort Broadcom Wifi

I have discovered that with the same method I was able to patch and use all the stock Catalina IO80211Family*.kext , but this method is only valid for "AirPort Broadcom Wifi cards" previously supported on HighSierra/Mojave , the advantage of my manual method is that it will fix the Catalina stock Wifi and more over will add the AirDrop channel capability.

I attach a guide I wrote.
Thanks for this, I will give it a whirl.
 
Thanks @ASentientBot finally full GFX Acceleration (QE/CI) on my Nvidia Fermi GF119 achieved on 10.15 Beta 2. What insteresting is I need using these additional tweaks from 10.14.4 (not 10.14.3):
Code:
- CoreDisplay.framework (10.14.4) + your wrapped CoreDisplay & CoreDisplayOriginal (10.14.4)
- OpenGL.framework (10.14.4)
- GPUSupport.framework (10.14.4)
- SkyLight.framework (10.14.4) + your wrapped SkyLight + SkyLightOriginal (10.14.4)
- GeForce.kext, GeForceGLDriver.bundle, GeForceVADriver.bundle (10.14.4)
- AppleGraphicsControl, IOAccelerator, IOGraphics, IONDRV, IOSurface, NVDA* are vanilla from 10.15 Beta 2
- I don't use NDRVShim.kext on Fermi #CMIIW

Sorry, screenshot is taken from H*ckintosh laptop. Yeah, I think provided GeForce, NVDAGF100, NVDAResman* (10.15) from Apple make differences here.
 

Attachments

  • macOS-Catalina.png
    macOS-Catalina.png
    613.8 KB · Views: 271
Last edited:
A prerequisite of both our patchers is that you must either have native APFS support or use the APFS ROM Patcher.

Well, then I will wait full Catallina patcher. My MacBook Pro have Nvidia chipset which isn't supported by APFS Patcher. And I have one more question. Does MacBook6,1 support APFS native or not? Beacause when I try to install Catalina, I get error Symbol (circle with slash inside). It's support High Sierra, but I can not find Firmware update on Apple site for MacBook6,1, only for 7,1 is there.
 
  • Like
Reactions: TimothyR734
Well, then I will wait full Catallina patcher. My MacBook Pro have Nvidia chipset which isn't supported by APFS Patcher. And I have one more question. Does MacBook6,1 support APFS native or not? Beacause when I try to install Catalina, I get error Symbol (circle with slash inside). It's support High Sierra, but I can not find Firmware update on Apple site for MacBook6,1, only for 7,1 is there.
It should update automatically when you install High Sierra. And make sure you run “sudo nvram boot-arts=“-no_compat_check” before using either patcher.
 
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
Thanks Jackluke. Will probably leave things as they are for now.
 
Before try, you should check from SystemReport Wifi section to have a Broadcom AirPort Wifi 14E4, 0x9* or higher (example 0xD*, 0xF*, 0x111 and so on)

Because some that tried with 0x8* or earlier reported that method doesn't worked.
Sure thing. I don’t know much about the hex values, so i’ll Probably list mine first before tinkering.
 
Thanks Jackluke. Will probably leave things as they are for now.

I understand, but it's totally safe it's just a .nib (NeXT Interface Builder) file from Mojave, but if you don't need to AirDropping from-to older OSX BT 2.1 with Catalina, then you don't need it.

If notice you had that function in Mojave, instead from Catalina apple has dropped that to exclude older OSX from file sharing I guess.
 
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.

For what it’s worth, I’ve got a non-Apple BCM94360CD in my desktop hackintosh and it wasn’t recognized in beta 1. I checked the PCI IDs in the info.plist files from Mojave and Catalina and mine was listed in both. Not sure why it didn’t work, but installing the Mojave kext fixed it.
 
  • Like
Reactions: TimothyR734
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.

I tried this as it's shown here and I still get no mouse or keyboard recognition, just stuck on the welcome screen....:(
 
help my mac pro 4,1 died ..PSU ... I have a complete system I want to use on IMAC running Sierra .. Can I use my Mojave from Mac Pro system on iMac by just using sudo boot args
[doublepost=1561410582][/doublepost]
I tried this as it's shown here and I still get no mouse or keyboard recognition, just stuck on the welcome screen....:(
I have beem following this thread and my pus in Mac Pro just died .. can I get an iMac on sierra to run my Mojave boot disk by sudo nvram ..
 
Hey all,

I've got this running smoothly on my Macbook Pro 2011 without much modification, the only issue I'm facing is Sidecar crashes after showing a black screen on the iPad for 5 seconds. After checking, it seems that Sidecar is looking for a Metal Device (a GPU supporting metal) for Sidecar. I'm wondering if it would be possible at all to use OpenGL for Sidecar? It seems very far fetched and I'm not sure if it's possible but it was worth a suggestion.

Thanks!

Screenshot 2019-06-24 at 22.21.53.png
upload_2019-6-24_22-19-0.png

Edit:
After reading the logs, this is what I get from when Sidecar is started to when it crashes:
SidecarReplay sends an event ‘com.apple.sidecar’ with 1 key
SidecarRelay activates something
SidecarRelay registers events with the IDs *
SidecarRelay (RPStreamServer) activates 0x0>
SidecarRelay (RPRemoteDisplaySession) registers the request ID “streamStart”
SidecarRelay (RPRemoteDisplaySession) registers the request ID “streamStop”
rapportd (RPRemoteDisplaySession) activates a session from SidecarRelay:ID to the iPad, in my case an iPad 7,5
SidecarReplay sends an event ‘com.apple.sidecar’ with 2 keys (to the iPad maybe?)
SidecarReplay sends another event ‘com.apple.sidecar’ with 2 keys (to the iPad maybe?)
SidecarRelay (RPRemoteDisplaySession) is activated, probably established the link with the iPad.
SidecarReplay sends another event ‘com.apple.sidecar’ with 2 keys (to the iPad maybe?)
rapportd queues multiple event sends, these are then sent
SidecarReplay sends another event ‘com.apple.sidecar’ with 2 keys (to the iPad maybe?)
rapportd then receives an event ID ‘com.apple.sidecar’ with 1 key from the iPad
SidecarRelay (RPStreamServer) starts a stream session with the ID: ‘ID:HIDRelay’, the type RPCnx
SidecarRelay’s CUTCPServer Is then activated on port 51804
The session that was started is then prepared by SidecarRelay in the RPStreamSession
SidecarRelay starts a stream session with the type UDPNWPath and another with an AVCVideoStream
The UDPNWPath is then queued for activation
The UDPNWPath is then started
The connection is started from a UDID at the port 50440 (probably the iPad)
the session connection is accepted from the HIDRelay (RPCnx)
There is another server connection queued for startup by the SidecarDisplayAgent with the type RCPnx

SidecarRelay (CUTCPServer) then invalidates the stream, after the stream is activated on socket 4. This is repeated multple times until it gives up, with errors from the AVCVideoStream and more, hinting at a metal issue? ‘Unable to get metal device’ is also printed multiple times from the avconference daemon.

From my research, it seems like sidecar is requiring metal to function, it may be possible to use OpenGL instead but very unlikely, hopefully this analysis can help someone, if you have anything to add just reply and I’ll add it.
 
Last edited:
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.

Yes, it works, the slot is compatible with an adapter (although it's a PITA to connect the antennas) and it supports 802.11ac (see screenshot). And yes, it was expensive from here.

https://www.osxwifi.com/product/mac...94360cd-802-11-a-b-g-n-ac-with-bluetooth-4-0/


Screen Shot 2019-06-25 at 6.17.22.png
 
Last edited:
  • Like
Reactions: Starplayr
I found out from my web host that APFS volumes do not support file shares over afp:// Not sure if this is 100% true yet as they said smb:// should work. And so far I cannot get smb:// to work, but it could be my ISP blocking that port.

But to test the HFS+ / Apple File Protocol (afp) theory, I created a RAMDisk on my server. Formatted it to HFS+ and needless to say it worked over afp:// but I have to include the username and password in the call to make it mount from a user. I tried the same syntax with smb:// and it did not work. I did make sure smb:// and afp:// were available. Apple gives no warnings whether you are using an APFS file system or not. I did see it uncheck things automatically and that was probably what they are doing on an APFS share.

afp remote syntax that I followed:

afp://username : password @ domain . suffix

No spaces ^^^^ :p is an emoji.

And for those who want to know how to make a RAMDisk:
diskutil erasevolume HFS+ "RAMDisk" 'hdiutil attach -nomount ram://2048'

Here diskutil and hdiutil are used on the same line which I did not know you could do.

I will add caution that if you lose power, you lose the RAMDisk. Unless of course you backed it up.

One cool thing is it's like having a thumb drive in the sky. I actually like it and will use it privately transfer tidbits of info or a small site update and it beats carrying a thumb drive around. I know it can crash but for temporary storage, but it's pretty cool. Your very own walled garden and if somehow someone does get in remotely, the can only steal a few megs, not your entire server.
 
Last edited:
The Silicon Valley call was today. It went well. The company is in its early stages this new position and they are still feeling things out. I was given some what if scenarios and had some pretty good real life examples. This is a public facing position dealing with their customers directly helping them with automation and doing things like TedTalks and writing blogs like on Medium. I may hear back from month to month and find out where they are at in the process.

After the call a wrote a nice Thank You letter giving a few additional details that I was not able to cover in the talk and proofread it 50 times before I sent it. The manager was very cool and he sounded like just like me. He mentioned first hand that he was in my area two weeks ago for a wedding and we started off talking about the weather here. He quickly switched gears and proceeded.

I was in my car and I forget to get some bottled water. My mouth was dry for the entire call. That was a challenge. It's almost like talking with peanut butter in your mouth. I hope he did not notice. I did not mention MacRumors or my handle. I felt I had enough material from past work experiences and I did not want a copywriter reviewing these posts.
 
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.
My CatWoman patcher for my card uses:

AirPortBrcm4331 version 8.0

this is my io reg:
"IOName" = "pci14e4,432b"
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.