Contribute
Register

macOS Catalina Public Beta is Now Available

Status
Not open for further replies.
does this include 780m like in iMac 27 2013?
Sorry for the late reply but I think that only difference is that one is mobile and the other one is desktop.
But, as long as the chip is Kepler, then it should work.
Also, if is a real Mac, then it has to be supported.
The last Nvidia cards or chips, which apple used on their Mac, is there Kepler cards.
 
Apple right back at Nvidia again. Well, it seems that the Side Car option is not going to work with Nvidia cards.
Unless the reason why the option refuses to load or work with a Nvidia card its because we are still on early PB1.

But I think that Apple is using another strategy to forced whatever is left of Nvidia users,
in others words, giving them a another reason to switch to AMD.

If you want Side Car to work and if you want to use the feature, then get a AMD card.
Mr. Tim Cook at his best.

The only way I get, show mirroring options in the menu bar to load in catalina, is by disabling the Nvidia card.
That will make the mirror option appears in the menu bar, but then I only get 7mb in About My Mac which disables graphic acceleration.

When I don't use nv_disable to load the card the normal way, then I get 2 GB in About My Mac. But then the mirror option refuses to load or to appears on the menu bar.

Weird right?

Well, if this problem is not because is an early beta "a bug", then I'm sure this is being done on purpose by Apple.
That feature might not work with Nvidia cards even if the card has support for everything else in the system is like Nvidia is being excluded from the feature.
Really not a surprise here.

I will love to see how this story end when apple finally releases Catalina.
Will a Nvidia card would work with the side card feature or not?

I'm sure a AMD card will work just fine.

“We didn’t start off to have a war with Flash. We just made a technical decision.”
We ask Adobe to make this thing fast but they never got back to us.

It seems like history repeating itself.
“We didn’t start off to have a war with Nvidia. We just made a technical decision.”
We ask Nvidia to make this thing fast but they never got back to us.
 
Apple right back at Nvidia again. Well, it seems that the Side Car option is not going to work with Nvidia cards.
Unless the reason why the option refuses to load or work with a Nvidia card its because we are still on early PB1.

But I think that Apple is using another strategy to forced whatever is left of Nvidia users,
in others words, giving them a another reason to switch to AMD.

If you want Side Car to work and if you want to use the feature, then get a AMD card.
Mr. Tim Cook at his best.

The only way I get, show mirroring options in the menu bar to load in catalina, is by disabling the Nvidia card.
That will make the mirror option appears in the menu bar, but then I only get 7mb in About My Mac which disables graphic acceleration.

When I don't use nv_disable to load the card the normal way, then I get 2 GB in About My Mac. But then the mirror option refuses to load or to appears on the menu bar.

Weird right?

Well, if this problem is not because is an early beta "a bug", then I'm sure this is being done on purpose by Apple.
That feature might not work with Nvidia cards even if the card has support for everything else in the system is like Nvidia is being excluded from the feature.
Really not a surprise here.

I will love to see how this story end when apple finally releases Catalina.
Will a Nvidia card would work with the side card feature or not?

I'm sure a AMD card will work just fine.

“We didn’t start off to have a war with Flash. We just made a technical decision.”
We ask Adobe to make this thing fast but they never got back to us.

It seems like history repeating itself.
“We didn’t start off to have a war with Nvidia. We just made a technical decision.”
We ask Nvidia to make this thing fast but they never got back to us.

It's probably supported on real Macs with NVIDIA cards (ie 2012-2014 MacBook Pros with NVIDIA gpus).

For example on my end (see specs in signature) I don't see SideCar at all with the iMac Pro SMBIOS. Probably a beta bug.
 
It's probably supported on real Macs with NVIDIA cards (ie 2012-2014 MacBook Pros with NVIDIA gpus).

For example on my end (see specs in signature) I don't see SideCar at all with the iMac Pro SMBIOS. Probably a beta bug.
I use the same smbios iMac Pro, that's nice system you got there
thanks for the info
:thumbup:
 
I have Sidecar showing on my iMac Pro hackintosh. But it shows up with a 401 error after it connects to my iPad. Hopefully, later betas fix it or the MacPro7,1 SMBIOS when it comes out. Have my RTX card disabled but the error still shows with only the Vega plugged in.
 
I have Sidecar showing on my iMac Pro hackintosh. But it shows up with a 401 error after it connects to my iPad. Hopefully, later betas fix it or the MacPro7,1 SMBIOS when it comes out. Have my RTX card disabled but the error still shows with only the Vega plugged in.
That is very good info. Because, if is not working for you with a Vega, then is not just with Nvidia cards like I first suspected. So it is has to be an early bug.

:headbang:
 
That is very good info. Because, if is not working for you with a Vega, then is not just with Nvidia cards like I first suspected. So it is has to be an early bug.

:headbang:

I’m really hoping it doesn’t require the T2 chip for iMac Pro SMBIOS but we’ll see... Apple hasn’t released officially supported devices yet
 
Last edited:
1st try went well. Only Bluetooth now working. :crazy:
Check out my fork of BrcmPatchRAM with Catalina support.

headkaze said:
Now that we don't have IOCatalogue::addDrivers, IOCatalogue::removeDrivers and IOCatalogue::startMatching methods to switch from using the uploader driver to native macOS driver we have to use BrcmBluetoothInjector.kext instead.

Brief instructions:
1. Download BrcmPatchRAM_Catalina.zip
2. Copy BrcmBluetoothInjector.kext, BrcmFirmwareData.kext and BrcmPatchRAM2.kext to EFI/CLOVER/kexts/Other
3. Reboot
4. Check About This Mac->System Report...->Bluetooth for "Firmware Version". If it's 4096 then the upload has failed
5. Successful upload should show something like the following in your log:
Code:
2019-06-29 12:25:57.923689-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0.
2019-06-29 12:25:57.940191-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Unknown new Darwin version 19.0, using possible compatible personality.
2019-06-29 12:26:17.208045-0700  localhost kernel[0]: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM20702A1_001.002.014.1443.1572_v5668".
2019-06-29 12:26:17.217894-0700  localhost kernel[0]: (kernel) BrcmPatchRAM: Decompressed firmware (29651 bytes --> 70012 bytes).
2019-06-29 12:26:17.218331-0700  localhost kernel[0]: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware.
2019-06-29 12:26:17.218435-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: USB [184F32F341D4 v274] "BCM20702A0" by "Broadcom Corp"
2019-06-29 12:26:17.820577-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: Firmware upgrade completed successfully.
2019-06-29 12:26:18.135008-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 21.599 seconds.
2019-06-29 12:26:18.151797-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0.
2019-06-29 12:26:20.168330-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: BrcmPatchRAMResidency does not appear to be available.
2019-06-29 12:26:20.192004-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: uploadFirmware could not open the device!
2019-06-29 12:26:20.207301-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 2.40 seconds.
You can use Hackintool to help get the log (see screenshot)
 

Attachments

  • BrcmFirmwareLog.png
    BrcmFirmwareLog.png
    452.5 KB · Views: 160
Last edited:
Check out my fork of BrcmPatchRAM with Catalina support.



Brief instructions:
1. Download BrcmPatchRAM_Catalina.zip
2. Copy BrcmBluetoothInjector.kext, BrcmFirmwareData.kext and BrcmPatchRAM2.kext to EFI/CLOVER/kexts/Other
3. Reboot
4. Check About This Mac->System Report...->Bluetooth for "Firmware Version". If it's 4096 then the upload has failed
5. Successful upload should show something like the following in your log:
Code:
2019-06-29 12:25:57.923689-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0.
2019-06-29 12:25:57.940191-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Unknown new Darwin version 19.0, using possible compatible personality.
2019-06-29 12:26:17.208045-0700  localhost kernel[0]: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM20702A1_001.002.014.1443.1572_v5668".
2019-06-29 12:26:17.217894-0700  localhost kernel[0]: (kernel) BrcmPatchRAM: Decompressed firmware (29651 bytes --> 70012 bytes).
2019-06-29 12:26:17.218331-0700  localhost kernel[0]: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware.
2019-06-29 12:26:17.218435-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: USB [184F32F341D4 v274] "BCM20702A0" by "Broadcom Corp"
2019-06-29 12:26:17.820577-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: Firmware upgrade completed successfully.
2019-06-29 12:26:18.135008-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 21.599 seconds.
2019-06-29 12:26:18.151797-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0.
2019-06-29 12:26:20.168330-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: BrcmPatchRAMResidency does not appear to be available.
2019-06-29 12:26:20.192004-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: uploadFirmware could not open the device!
2019-06-29 12:26:20.207301-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 2.40 seconds.
You can use Hackintool to help get the log (see screenshot)

Confirmed, these kexts works fine in Mojave too without storing them to L/E.
Great !
 
Check out my fork of BrcmPatchRAM with Catalina support.



Brief instructions:
1. Download BrcmPatchRAM_Catalina.zip
2. Copy BrcmBluetoothInjector.kext, BrcmFirmwareData.kext and BrcmPatchRAM2.kext to EFI/CLOVER/kexts/Other
3. Reboot
4. Check About This Mac->System Report...->Bluetooth for "Firmware Version". If it's 4096 then the upload has failed
5. Successful upload should show something like the following in your log:
Code:
2019-06-29 12:25:57.923689-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0.
2019-06-29 12:25:57.940191-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Unknown new Darwin version 19.0, using possible compatible personality.
2019-06-29 12:26:17.208045-0700  localhost kernel[0]: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM20702A1_001.002.014.1443.1572_v5668".
2019-06-29 12:26:17.217894-0700  localhost kernel[0]: (kernel) BrcmPatchRAM: Decompressed firmware (29651 bytes --> 70012 bytes).
2019-06-29 12:26:17.218331-0700  localhost kernel[0]: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware.
2019-06-29 12:26:17.218435-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: USB [184F32F341D4 v274] "BCM20702A0" by "Broadcom Corp"
2019-06-29 12:26:17.820577-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: Firmware upgrade completed successfully.
2019-06-29 12:26:18.135008-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 21.599 seconds.
2019-06-29 12:26:18.151797-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.0.
2019-06-29 12:26:20.168330-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: [0a5c:216f]: BrcmPatchRAMResidency does not appear to be available.
2019-06-29 12:26:20.192004-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: uploadFirmware could not open the device!
2019-06-29 12:26:20.207301-0700  localhost kernel[0]: (kernel) BrcmPatchRAM2: Processing time 2.40 seconds.
You can use Hackintool to help get the log (see screenshot)

You're da mannn! Thank you so much @headkaze
Screenshot 2019-07-03 at 9.25.49 am.png
 
Status
Not open for further replies.
Back
Top