Jump to content

[pre-release] macOS Catalina


1,679 posts in this topic

Recommended Posts

13 hours ago, lisai9093 said:

The sidecar option only shows up when connected to your ipad for first time. Also iPad need to signed into same iCloud account as your mac.

Thanks for detail and replying

Link to comment
Share on other sites

With the latest beta my computer still freezes when I try to play videos in Netflix or Amazon prime using Safari with the iMacPro 1,1 SMBios and the iGPU disabled :(

 

Can anyone play videos in Netflix using Safari with iMacPro 1,1, SMBios? my dGPU is a Sapphire Radeon RX 570 Nitro+ 4GB

Link to comment
Share on other sites

8 minutes ago, dvil said:

With the latest beta my computer still freezes when I try to play videos in Netflix or Amazon prime using Safari with the iMacPro 1,1 SMBios and the iGPU disabled :(

 

Can anyone play videos in Netflix using Safari with iMacPro 1,1, SMBios? my dGPU is a Sapphire Radeon RX 570 Nitro+ 4GB

Maybe you should switch to the correct SMBIOS for your CPU and chipset and not choose a SMBIOS based off GPU.

  • Like 1
Link to comment
Share on other sites

6 minutes ago, Pavo said:

Maybe you should switch to the correct SMBIOS for your CPU and chipset and not choose a SMBIOS based off GPU.

Hi Pavo,

 

Everything works perfectly in Mojave (including DRM support) with the iMacPro SMBIOS. If I choose the correct SMBIOS for my cpu (iMac 17,1) I loose DRM support with Safari in Mojave and I get in both, Mojave and Catalina, the "unsupported plugin" message in Netflix, even with the shikigva=32 and shiki-id=Mac-7BA5B2D9E42DDD94 parameters, so nothing is gained with the correct SMBIOS.

 

The freezing problem has been reported by other users before, but it seems there are no solution so far. I'll check again changing SMBIOS, but it seems to be a hardware decoding issue (T2?).

 

 Thanks.

  

Link to comment
Share on other sites

17 minutes ago, dvil said:

Hi Pavo,

 

Everything works perfectly in Mojave (including DRM support) with the iMacPro SMBIOS. If I choose the correct SMBIOS for my cpu (iMac 17,1) I loose DRM support with Safari in Mojave and I get in both, Mojave and Catalina, the "unsupported plugin" message in Netflix, even with the shikigva=32 and shiki-id=Mac-7BA5B2D9E42DDD94 parameters, so nothing is gained with the correct SMBIOS.

 

The freezing problem has been reported by other users before, but it seems there are no solution so far. I'll check again changing SMBIOS, but it seems to be a hardware decoding issue (T2?).

 

 Thanks.

  

Maybe this will give you a better idea on how to set your shikigva setting correctly:

// Aside generic DRM unlock patches, which are always on, Shiki also provides a set of patches
	// to workaround various issues with hardware video acceleration support.
	// These are set as a shikigva boot-arg bitmask.
	// For example, to enable ForceOnlineRenderer, ExecutableWhitelist, and ReplaceBoardID
	// you sum 1 + 8 + 32 = 41 -> and pass shikigva=41.
	enum ShikiGVAPatches {
		// Remove forceOfflineRenderer from AppleGVA Info.plist.
		// This is required to allow hardware acceleration on several mac models with discrete GPUs
		// when only IGPU is available.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		ForceOnlineRenderer        = 1,
		// Remve hweBGRA from AppleGVA Info.plist.
		// hweBGRA is not supported by NVIDIA GPUs, so the patch is sometimes required when using NVIDIA
		// in a mac model meant to be used with AMD or Intel.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		AllowNonBGRA               = 2,
		// Prior to 10.13.4 certain GPU+CPU combinations were not meant to provide hardware acceleration and had to be patched.
		// The overall problematic configuration list is: NVIDIA+BDW, NVIDIA+SKL, NVIDIA+KBL, AMD+IVB, NVIDIA+SNB.
		// Enabled automatically if shikigva is *NOT* passed on 10.13.3 and earlier. All are fixed in 10.13.4.
		ForceCompatibleRenderer    = 4,
		// Unlike 10.12.6 without security updates and earlier, on 10.13 and latest 10.12.6 AppleGVA patches
		// do not apply to all processes, and each process needs to be patched explicitly. This is a bug
		// in Lilu, which needs to be explored and fixed. For now this bit ensures that the processes present
		// in WHITELIST section of Patches.plist will definitely get the fixes even on 10.13 and 10.12.6.
		// On 10.12.6 and 10.13 this must be used if any of the following bits are used:
		// - ForceOnlineRenderer
		// - AllowNonBGRA
		// - ForceCompatibleRenderer
		// - ReplaceBoardID
		// - FixSandyBridgeClassName
		// It is enabled automatically on 10.12 and 10.13 if shikigva is *NOT* passed and ForceCompatibleRenderer or
		// FixSandyBridgeClassName are automatically enabled.
		AddExecutableWhitelist     = 8,
		DisabledUnused16           = 16,
		// Replace board-id used by AppleGVA and AppleVPA by a different board-id.
		// Sometimes it is feasible to use different GPU acceleration settings from the main mac model.
		// By default Mac-27ADBB7B4CEE8E61 (iMac14,2) will be used, but you can override this via shiki-id boot-arg.
		// See /System/Library/PrivateFrameworks/AppleGVA.framework/Resources/Info.plist for more details.
		ReplaceBoardID             = 32,
		// Attempt to support fps.1_0 (FairPlay 1.0) in Safari.
		// This should technically fix some very old streaming services in Safari, which rely on FairPlay DRM
		// similar to the one found in iTunes. Newer streaming services require FairPlay 2.0, which is hardware-only,
		// so nothing could be done about them.
		// Another way to enable this is to pass -shikifps boot argument.
		UnlockFP10Streaming        = 64,
		DeprecatedUnused128        = 128

 

Link to comment
Share on other sites

On 6/30/2019 at 1:32 PM, lisai9093 said:

First, AirportBrcmFixup has to be injected via Clover. No installation to /L/E or S/L/E works.

Second, AirportBrcmFixup need to be compiled from updated source. Version 2.0.2 works fine.

AirportBrcmFixup.kext.zip

Thank you, will try. Do you use any Clover Airport patch?

I downloaded the latest Debug version of Lilu (which is 1.3.6) from github repository and AirportBrcmFixup source code 

git clone https://github.com/acidanthera/AirportBrcmFixup

After that I put Lilu.kext inside of AirportBrcmFixup folder and tried to compile the source code with the command: xcodebuild

I have:

** BUILD FAILED **. 

/Users/val/Desktop/AirportBrcmFixup/AirportBrcmFixup/kern_start.cpp:50:17: error: no member named 'Catalina' in 'KernelVersion'

What am I doing wrong?

I am doing this on my Mojave system.

 

Thanks

On 6/30/2019 at 1:32 PM, lisai9093 said:

 

 

 

2 hours ago, Pavo said:

Maybe you should switch to the correct SMBIOS for your CPU and chipset and not choose a SMBIOS based off GPU.

 

Edited by valeryimm
Link to comment
Share on other sites

43 minutes ago, dvil said:

Hi Pavo,

 

Everything works perfectly in Mojave (including DRM support) with the iMacPro SMBIOS. If I choose the correct SMBIOS for my cpu (iMac 17,1) I loose DRM support with Safari in Mojave and I get in both, Mojave and Catalina, the "unsupported plugin" message in Netflix, even with the shikigva=32 and shiki-id=Mac-7BA5B2D9E42DDD94 parameters, so nothing is gained with the correct SMBIOS.

 

The freezing problem has been reported by other users before, but it seems there are no solution so far. I'll check again changing SMBIOS, but it seems to be a hardware decoding issue (T2?).

 

 Thanks.

  

 

i have same problem, i literally tried everything, nothing helped. i'm not using weg, just bare GPU, IGPU disabled.

Link to comment
Share on other sites

Update made, this time with the help of Mac Downloader, because my update gave me an error and didn't show any update... 

Thanks to the developer of Mac Downloader, kudos to you man...

Captura de ecrã 2019-07-02, às 21.53.31.png

Edited by MorenoAv
  • Like 3
Link to comment
Share on other sites

On 6/30/2019 at 1:32 PM, lisai9093 said:

First, AirportBrcmFixup has to be injected via Clover. No installation to /L/E or S/L/E works.

Second, AirportBrcmFixup need to be compiled from updated source. Version 2.0.2 works fine.

AirportBrcmFixup.kext.zip

Thank you, will try. Do you use any Clover Airport patch?

I downloaded the latest Debug version of Lilu (which is 1.3.6) from github repository and AirportBrcmFixup source code 

git clone https://github.com/acidanthera/AirportBrcmFixup

After that I put Lilu.kext inside of AirportBrcmFixup folder and tried to compile the source code with the command: xcodebuild

I have:

** BUILD FAILED **. 

/Users/val/Desktop/AirportBrcmFixup/AirportBrcmFixup/kern_start.cpp:50:17: error: no member named 'Catalina' in 'KernelVersion'

What am I doing wrong?

I am doing this on my Mojave system.

 

Thanks

Link to comment
Share on other sites

29 minutes ago, valeryimm said:

Thank you, will try. Do you use any Clover Airport patch?

I downloaded the latest Debug version of Lilu (which is 1.3.6) from github repository and AirportBrcmFixup source code 


git clone https://github.com/acidanthera/AirportBrcmFixup

After that I put Lilu.kext inside of AirportBrcmFixup folder and tried to compile the source code with the command: xcodebuild

I have:

** BUILD FAILED **. 

/Users/val/Desktop/AirportBrcmFixup/AirportBrcmFixup/kern_start.cpp:50:17: error: no member named 'Catalina' in 'KernelVersion'

What am I doing wrong?

I am doing this on my Mojave system.

 

Thanks

the GitHub Debug version under releases to now work for that version of AirportBrcmFixup repo. You must compile Lilu debug version yourself and use it to compile AirportBrcmFixup.

Link to comment
Share on other sites

2 hours ago, dvil said:

even with the shikigva=32 and shiki-id=Mac-7BA5B2D9E42DDD94 parameters, so nothing is gained with the correct SMBIOS.

  

Should work with these boot flags. Do you have IGPU enabled? If so, disable it and try again.

Link to comment
Share on other sites

It looks like beta 3 has solved my issue with excessive logging causing performance issues.

 

I think the debug level in Catalina beta 1 and 2 was set too high (or some kext's were compiled with excessive logging). For example I was getting log messages for every in report received by my KVM hid device:

2019-06-20 08:52:06.122905-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.152892-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.182884-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.212887-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.242914-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.272910-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.302911-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.319939-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x100000456] CompleteInReport actualByteCount:4
2019-06-20 08:52:06.332902-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.362919-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.392912-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.422917-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15
2019-06-20 08:52:06.423924-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x100000456] CompleteInReport actualByteCount:4
2019-06-20 08:52:06.452930-0700 localhost kernel[0]: (AppleUserHIDDrivers) [<private>:756][HIDDriverKit][0x10000045d] CompleteInReport actualByteCount:15

Edited by headkaze
  • Like 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...