testubabe Posted June 13, 2019 Share Posted June 13, 2019 58 minutes ago, anmool said: It worked for me also thanks Fine, you're welcome Link to comment Share on other sites More sharing options...
Djlild7hina Posted June 13, 2019 Share Posted June 13, 2019 7 hours ago, Rockey12 said: Sidecar support on older Macs Not every Mac that supports macOS Catalina will support the Sidecar feature. I could not find any official info, but here are my own findings. There’s an explicit check that the Mac is newer than these models: MacBook, MacBook Air: Early 2015 MacBook Pro: Mid 2015 iMac: Late 2015 Mac mini: Late 2014 Mac Pro: Late 2013 I managed to make Sidecar work with my Mid 2014 MacBook Pro work and iPad Pro. It’s great in terms of minimal lag, but the image quality is bad. I guess the limitation is about hardware HEVC encoding which requires Intel Core 6th gen processoHere’ If you need this feature on an older Mac despite low image quality I suggest filing a bug report with Apple. A hidden option to disable such hardware check would be great. That requires disabling System Integrity Protection and editing SidecarCore private framework to exclude your Mac model from the blacklist. Edit: To enable unsupported Mac and "display" devices use this Terminal command: defaults write com.apple.sidecar.display AllowAllDevices -bool true; defaults write com.apple.sidecar.display hasShownPref -bool true; open /System/Library/PreferencePanes/Sidecar.prefPane I had discovered the AllowAllDevices settings before writing this post, but for some reason it did not have effect at first so I resorted to patching the files. Looks like the patching is not needed. Still doesn't work. I already had sidecar in system preferences but whenever it tries to connect to the iPad it just shows a black screen then error code -401. Will keep checking on later betas. Thanks though! Link to comment Share on other sites More sharing options...
Riley Freeman Posted June 13, 2019 Share Posted June 13, 2019 Any hope of getting a BCM4322 wifi card (14e4:432b) working with Catalina? It was supported natively up to Mojave but with the Brcm4331 kext gone it's no longer detected. I tried adding the device ID to AirportBrcmFixup but it panicked on boot. Link to comment Share on other sites More sharing options...
Rocky12 Posted June 13, 2019 Share Posted June 13, 2019 finally i got it the first test macOS Cat this was a hugh pain to installing on a branded machine but i did it 1 Link to comment Share on other sites More sharing options...
chris1111 Posted June 13, 2019 Share Posted June 13, 2019 Intel HD 3000 Works again 2 Link to comment Share on other sites More sharing options...
Sherlocks Posted June 14, 2019 Share Posted June 14, 2019 Intel HD 3000 Works again mojave too from your catalina package?나의 SM-N960N 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
chris1111 Posted June 14, 2019 Share Posted June 14, 2019 (edited) 14 hours ago, Sherlocks said: mojave too from your catalina package? 나의 SM-N960N 의 Tapatalk에서 보냄 Mojave I have a différant package because I don't whant mixed OS both package available here HD 3000 Package Edited June 14, 2019 by chris1111 both package available 1 Link to comment Share on other sites More sharing options...
Roboter Posted June 14, 2019 Share Posted June 14, 2019 Something odd happens now on my CustoMac. Both Mojave, which was super stable, and Catalina don't work properly anymore. By that I mean that my monitors randomly black out while being in use. I have two same model monitors connected to RX580 dGPU. One monitor is connected via DP port, the other via HDMI. The monitor that is connected with DP blacks out more often and more frequent. I'm not sure if this is caused by some of the latest clover patches or if there is a kext issue on my machine. Has anyone experienced similar issues or know how or what I can investigate? Link to comment Share on other sites More sharing options...
Vinbie Posted June 14, 2019 Share Posted June 14, 2019 Hi - I'm new here, so thanks in advance for all the help you're all giving! It's very appreciated. I have an 8th gen i5 Intel NUC that I'm trying to get Catalina on to, but keep running into an issue. It seems to be linked to APSF, like a previous comment posted, however I was always using FakeSMC (never VirtualSMC). I am largely using the files provided in RehabMan's guide, but with small updates that were made to make it compatible with 10.14.5. I am using Clover 4964. Any help would be greatly appreciated. Thanks! config.plist Link to comment Share on other sites More sharing options...
Joshua60 Posted June 14, 2019 Share Posted June 14, 2019 5 hours ago, Vinbie said: Hi - I'm new here, so thanks in advance for all the help you're all giving! It's very appreciated. I have an 8th gen i5 Intel NUC that I'm trying to get Catalina on to, but keep running into an issue. It seems to be linked to APSF, like a previous comment posted, however I was always using FakeSMC (never VirtualSMC). I am largely using the files provided in RehabMan's guide, but with small updates that were made to make it compatible with 10.14.5. I am using Clover 4964. Any help would be greatly appreciated. Thanks! config.plist looks like apfs.efi is missing Link to comment Share on other sites More sharing options...
telepati Posted June 14, 2019 Share Posted June 14, 2019 7 hours ago, Roboter said: Something odd happens now on my CustoMac. Both Mojave, which was super stable, and Catalina don't work properly anymore. By that I mean that my monitors randomly black out while being in use. I have two same model monitors connected to RX580 dGPU. One monitor is connected via DP port, the other via HDMI. The monitor that is connected with DP blacks out more often and more frequent. I'm not sure if this is caused by some of the latest clover patches or if there is a kext issue on my machine. Has anyone experienced similar issues or know how or what I can investigate? 2 I have the same problem a very long time and I didn't find any solution for that. I have one display and I am losing my screen randomly while working. I tried too many things but it never fixes. I even upgrade my all systems but nothing helped. But, I think yours is turning black mine is turning grey while in use. I even found a way how to investigate this problem I always making force restart from the case. Link to comment Share on other sites More sharing options...
Vinbie Posted June 14, 2019 Share Posted June 14, 2019 2 hours ago, Joshua60 said: looks like apfs.efi is missing It was my understanding that APFSDriverLoader was to be used instead of this. If I'm wrong, where is your what suggestion to obtain the newest copy of apfs.efi? Thanks! 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted June 15, 2019 Share Posted June 15, 2019 6 hours ago, Vinbie said: It was my understanding that APFSDriverLoader was to be used instead of this. If I'm wrong, where is your what suggestion to obtain the newest copy of apfs.efi? Thanks! Navigate to /usr/standalone/i386/ Copy apfs.efi in /Volumes/EFI/EFI/CLOVER/drivers64UEFI/ Remove Verbose Text Open Terminal sudo perl -i -pe 's|\x00\x74\x07\xb8\xff\xff|\x00\x90\x90\xb8\xff\xff|sg' /Volumes/EFI/EFI/CLOVER/drivers64UEFI/apfs.efi 1 Link to comment Share on other sites More sharing options...
headkaze Posted June 15, 2019 Share Posted June 15, 2019 (edited) On 6/7/2019 at 6:20 PM, Sherlocks said: did you say this issue to rehabman? I thought I would spend some time to investigate the issue with BrcmPatchRAM first. Please check out the following post and let me know if it works for you. I have linked to it on GitHub so RehabMan can hopefully see it. Edited June 15, 2019 by headkaze 5 Link to comment Share on other sites More sharing options...
izo1 Posted June 15, 2019 Share Posted June 15, 2019 56 minutes ago, Matgen84 said: Navigate to /usr/standalone/i386/ Copy apfs.efi in /Volumes/EFI/EFI/CLOVER/drivers64UEFI/ Remove Verbose Text Open Terminal sudo perl -i -pe 's|\x00\x74\x07\xb8\xff\xff|\x00\x90\x90\xb8\xff\xff|sg' /Volumes/EFI/EFI/CLOVER/drivers64UEFI/apfs.efi You don't need the apfs.efi anymore, APFSLoader is fine. Works ok here. 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted June 15, 2019 Share Posted June 15, 2019 32 minutes ago, izo1 said: You don't need the apfs.efi anymore, APFSLoader is fine. Works ok here. I answer to Vinble, quote his post. Please 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted June 15, 2019 Share Posted June 15, 2019 I thought I would spend some time to investigate the issue with BrcmPatchRAM first. Please check out the following post and let me know if it works for you. I have linked to it on GitHub so RehabMan can hopefully see it. thanks a lot.you did place both kexts in other folder.was there no problem after wakeup?rehabman said that he recommend place both files in S/L/E to upload firmware.actually, i experienced fail upload firmware with other folder when wakeup나의 SM-N960N 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
Joshua60 Posted June 15, 2019 Share Posted June 15, 2019 12 hours ago, Vinbie said: It was my understanding that APFSDriverLoader was to be used instead of this. If I'm wrong, where is your what suggestion to obtain the newest copy of apfs.efi? Thanks! ok, fine, now: -lilubetaall is not needed if you use kexts in post #1 of this thread 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted June 15, 2019 Share Posted June 15, 2019 (edited) Hi Need help please! I've issue with latest WEG 1.3.0 on my config i7 9700K - RX 580. Catalina start only if I block WEG with Clover Any solutions Edited June 15, 2019 by Matgen84 Link to comment Share on other sites More sharing options...
chris1111 Posted June 15, 2019 Share Posted June 15, 2019 4 minutes ago, Matgen84 said: Hi Need help please! I've issue with latest WEG 1.3.0 on my config i7 9700K - RX 580. Catalina start only if I block WEG with Clover Any solutions try to add -wegbeta Link to comment Share on other sites More sharing options...
Matgen84 Posted June 15, 2019 Share Posted June 15, 2019 Just now, chris1111 said: try to add -wegbeta I already try: don't work Link to comment Share on other sites More sharing options...
polyzargone Posted June 15, 2019 Share Posted June 15, 2019 5 hours ago, Sherlocks said: thanks a lot. you did place both kexts in other folder. was there no problem after wakeup? rehabman said that he recommend place both files in S/L/E to upload firmware. actually, i experienced fail upload firmware with other folder when wakeup 나의 SM-N960N 의 Tapatalk에서 보냄 It works fine from Other on my rig (Acer Aspire V3 772G - Azurewave Broadcom Bcm94352hmb/Bcm94352). 1 Link to comment Share on other sites More sharing options...
gengik84 Posted June 15, 2019 Share Posted June 15, 2019 @Matgen84 have you tried the compiled version? You can find link at first post In case without -lilubetaall Link to comment Share on other sites More sharing options...
abdouoi Posted June 15, 2019 Share Posted June 15, 2019 (edited) On 6/8/2019 at 7:56 AM, abdouoi said: @PMheart, @Sherlocks or someone specialized with kernel panics. Please help me Edited June 15, 2019 by abdouoi 1 Link to comment Share on other sites More sharing options...
chris1111 Posted June 15, 2019 Share Posted June 15, 2019 1 minute ago, abdouoi said: @PMheart or someone specialized with kernel panics. Please help me Please post complet EFI folder Link to comment Share on other sites More sharing options...
Recommended Posts