Jump to content
Wayang-NT

[pre-release] macOS Mojave 10.14.4

194 posts in this topic

Recommended Posts

Thanks @PMheart

 

I tested same result.

 

Find            C1E30848 63D389D0 48C1EA20 
Replace         C1E308B8 00FF0000 31D29090 

 

Share this post


Link to post
Share on other sites
Advertisement
47 minutes ago, nmano said:

Thanks @PMheart

 

I tested same result.

 


Find            C1E30848 63D389D0 48C1EA20 
Replace         C1E308B8 00FF0000 31D29090 

 

That's kind of weird then, it should be the same as our old patch...

Share this post


Link to post
Share on other sites
3 minutes ago, PMheart said:

That's kind of weird then, it should be the same as our old patch...

Does using Bundle Executable rather than Bundle Identifier as a Name make any different related to KextInject?

On my case (for example), on 10.11.6 having no problem if:

<key>Name</key>
<string>AirPortAtheros40</string>

But since 10.12.x, I need:

<key>Name</key>
<string>com.apple.driver.AirPort.Atheros40</string>

// or these are OS dependant / Clover? Thanks.

Share this post


Link to post
Share on other sites
On 1/29/2019 at 7:09 AM, fusion71au said:

On my legacy Dell laptop (Geforce 8600M GT/tesla) using MBP7,1 SMBIOS and -no_compat_check boot flag, had same error as @macq - hang on message ioconsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0 after DSMOS arrives.

 

Maybe we need to do something with these?

14E174f.png

Share this post


Link to post
Share on other sites
38 minutes ago, Badruzeus said:

Does using Bundle Executable rather than Bundle Identifier as a Name make any different related to KextInject? 

On my case (for example), on 10.11.6 having no problem if:


<key>Name</key>
<string>AirPortAtheros40</string>

But since 10.12.x, I need:


<key>Name</key>
<string>com.apple.driver.AirPort.Atheros40</string>

// or these are OS dependant / Clover? Thanks.

Hmm, I don't know, to be honest. I am not a developer of Clover.

 

Well, I don't think KextToPatch has anything to do with KextInject. (Yet one thing to keep in mind is that KextToPatch also patches injected ones, e.g. imagine you patched FakeSMC for whatever reason and it is being injected, KextToPatch will handle it too.)

It looks like a bug, you may report it to Clover threads. Thanks!

Share this post


Link to post
Share on other sites
15 minutes ago, PMheart said:

Well, I don't think KextToPatch has anything to do with KextInject. (Yet one thing to keep in mind is that KextToPatch also patches injected ones, e.g. imagine you patched FakeSMC for whatever reason and it is being injected, KextToPatch will handle it too.)

It looks like a bug, you may report it to Clover threads. Thanks!

 

Yeah, no problem.. "BundleIdentifier" as a KextToPatch's Name is also working fine on my 10.11.6 upto 10.14.x.

Only, sometimes.. need to rebuild kernelcache && prelinkedkernel (I placed 3rd party kexts on \efi\clover\kexts #btw).

Share this post


Link to post
Share on other sites
1 minute ago, Badruzeus said:

 

Yeah, no problem.. "BundleIdentifier" as a KextToPatch's Name is also working fine on my 10.11.6 upto 10.14.x. 

Only, sometimes.. need to rebuild kernelcache && prelinkedkernel (I placed 3rd party kexts on \efi\clover\kexts #btw). 

Yes, you better always use BundleIdentifier as it is unique for each kext thus is more precise.

 

Well, Clover's KextToPatch is only able to patch those inside kernel cache, so you might use Lilu + plugins if there were any alternative.

Share this post


Link to post
Share on other sites
On 1/26/2019 at 7:35 AM, macq said:

Gt320m tesla, Actually can boot only with safe mode, in normal boot I reach to a point where it says io console something and then turns to blackscreen and cannot reach the desktop.

i have a similar issue with HD3000. i just tried to update to 10.14.4 beta1 and i get blackscreen unless i disable acceleration - safemode or inject gfx id 0x12345678. wonder if this is the end of the road for non-metal systems?

Share this post


Link to post
Share on other sites
0:106  0:000  Boot status=0
0:106  0:000  Running on: 'X299-WU8' with board 'X299-WU8-CF'
0:106  0:000  === [ GetCPUProperties ] ==================================
0:106  0:000  CPU Vendor = 756E6547 Model=50654
0:106  0:000   The CPU supported SSE4.1
0:106  0:000  BrandString = Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz
0:106  0:000   The CPU supported turbo
0:106  0:000  MSR 0x35              120024
0:106  0:000   TSC/CCC Information Leaf:
0:106  0:000    numerator     : 250
0:106  0:000    denominator   : 2
0:106  0:000   Calibrated ARTFrequency: 24003225
0:106  0:000  MSR 0xE2 before patch 00000403
0:106  0:000  MSR 0xCE              00070C2C_F3011E00
0:106  0:000  MSR 0x1B0             00000000
0:106  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz
0:106  0:000  MaxDiv/MinDiv: 30.0/12
0:106  0:000  Turbo: 42/42/42/42
0:106  0:000  Features: 0xBFEBFBFF
0:106  0:000  Threads: 36
0:106  0:000  Cores: 18
0:106  0:000  FSB: 100 MHz
0:106  0:000  CPU: 3000 MHz
0:106  0:000  TSC: 3000 MHz
0:106  0:000  PIS: 100 MHz
0:106  0:000  ExternalClock: 25 MHz

Hi @PMheart

I have X299-WU8 with i9-9980XE

I need xcpm_bootstrap  patched for this CPU

 

 

machdep.cpu.brand_string: Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz

 

CPU ID

0x050654

 

Thank you.

Edited by nmano

Share this post


Link to post
Share on other sites
On 1/31/2019 at 9:49 AM, nmano said:

0:106  0:000  Boot status=0
0:106  0:000  Running on: 'X299-WU8' with board 'X299-WU8-CF'
0:106  0:000  === [ GetCPUProperties ] ==================================
0:106  0:000  CPU Vendor = 756E6547 Model=50654
0:106  0:000   The CPU supported SSE4.1
0:106  0:000  BrandString = Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz
0:106  0:000   The CPU supported turbo
0:106  0:000  MSR 0x35              120024
0:106  0:000   TSC/CCC Information Leaf:
0:106  0:000    numerator     : 250
0:106  0:000    denominator   : 2
0:106  0:000   Calibrated ARTFrequency: 24003225
0:106  0:000  MSR 0xE2 before patch 00000403
0:106  0:000  MSR 0xCE              00070C2C_F3011E00
0:106  0:000  MSR 0x1B0             00000000
0:106  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz
0:106  0:000  MaxDiv/MinDiv: 30.0/12
0:106  0:000  Turbo: 42/42/42/42
0:106  0:000  Features: 0xBFEBFBFF
0:106  0:000  Threads: 36
0:106  0:000  Cores: 18
0:106  0:000  FSB: 100 MHz
0:106  0:000  CPU: 3000 MHz
0:106  0:000  TSC: 3000 MHz
0:106  0:000  PIS: 100 MHz
0:106  0:000  ExternalClock: 25 MHz

Hi @PMheart

I have X299-WU8 with i9-9980XE 

I need xcpm_bootstrap  patched for this CPU

 

 

machdep.cpu.brand_string: Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz 

 

CPU ID

0x050654 

 

Thank you.

Hi,

 

Firstly, X299 (CPUID 0x55) should be supported natively and thus no patch would be needed I guess.

 

Well, anyway, if you do need it... Here you go:

 

EDIT: Skylake-X (CPUID 0x55) is supported natively, no need to patch!

 

Edited by PMheart

Share this post


Link to post
Share on other sites
Just now, PMheart said:

Hi,

 

Firstly, X299 (CPUID 0x55) should be supported natively and thus no patch would be needed I guess.

 

Well, anyway, if you do need it... Here you go:


89 d8 04 c4 3c 22 77 22 -> 89 d8 04 cd 3c 22 77 22

Thanks @PMheart

xcpm_bootstrap_Skylake X © PMHeart

Its worked

Thank you.

 

Screen Shot 2019-01-30 at 11.06.51 PM.png

Edited by nmano

Share this post


Link to post
Share on other sites
2 hours ago, yapan4 said:

Hi, @PMheart

Any news for Xeon W-21xx users?  

Sorry, I don't know.

 

1 hour ago, nmano said:

 

Screen Shot 2019-01-30 at 11.06.51 PM.png

As I said, CPUID 0x55 should be supported natively (i.e without _xcpm_bootstrap patch), cannot you boot without it?

Edited by PMheart
typo

Share this post


Link to post
Share on other sites

Hi

I can’t run AppleIntelInfo.kext when kext load system panic.

I can’t run DarwinDumper if I thick CPU Information getting System panic.

Please advice how to fix this.

Thank you.

Share this post


Link to post
Share on other sites
4 minutes ago, nmano said:

Hi

I can’t run AppleIntelInfo.kext when kext load system panic.

I can’t run DarwinDumper if I thick CPU Information getting System panic.

Please advice how to fix this.

Thank you.

Well, AppleIntelInfo is maintained by Pike R. Alpha, who has quitted now... So the repo is almost dead unfortunately... :(

As for DarwinDumper, it's page is here, you may consider talking with the developers directly?

Share this post


Link to post
Share on other sites
Just now, PMheart said:

Well, AppleIntelInfo is maintained by Pike R. Alpha, who has quitted now... So the repo is almost dead unfortunately... :(

As for DarwinDumper, it's page is here, you may consider talking with the developers directly?

I can run without patch

I just test with only fake cpu ID not any Kernel patches.

Screen Shot 2019-01-31 at 1.03.29 AM.png

Share this post


Link to post
Share on other sites
9 minutes ago, nmano said:

I can run without patch 

I just test with only fake cpu ID not any Kernel patches. 

Screen Shot 2019-01-31 at 1.03.29 AM.png

No, X299 is supported NATIVELY, meaning that you should get everything running fine without any patch. Please try disabling all possible kernel patches and try

sysctl -n machdep.xcpm.mode

See if it returns 1.

Share this post


Link to post
Share on other sites
Just now, PMheart said:

No, X299 is supported NATIVELY, meaning that you should get everything running fine without any patch. Please try disabling all possible kernel patches and try


sysctl -n machdep.xcpm.mode

See if it returns 1.

Last login: Thu Jan 31 01:15:49 on console
Navaratnams-Mac-Pro-2:~ x58$ sysctl -n machdep.xcpm.mode
1
Navaratnams-Mac-Pro-2:~ x58$ 

I test now without FakecpuID

set in bios profile 1

overclock 4.2GHz

I need to get 10,000 more core score:)

I disable all kernel patches.

Thanks @PMheart

 

Screen Shot 2019-01-31 at 1.19.48 AM.png

Edited by nmano

Share this post


Link to post
Share on other sites
59 minutes ago, nmano said:

Last login: Thu Jan 31 01:15:49 on console
Navaratnams-Mac-Pro-2:~ x58$ sysctl -n machdep.xcpm.mode
1
Navaratnams-Mac-Pro-2:~ x58$ 

I test now without FakecpuID

set in bios profile 1

overclock 4.2GHz

I need to get 10,000 more core score:)

I disable all kernel patches.

Thanks @PMheart

 

Screen Shot 2019-01-31 at 1.19.48 AM.png

 you have loaded X86PlatformPlugin.kext?

 

Share this post


Link to post
Share on other sites
4 hours ago, tyufhl said:

 you have loaded X86PlatformPlugin.kext?

 

Yes

I thick Plugin Type in ACPI in the Clover config.

Screen Shot 2019-01-31 at 3.48.56 PM.png

Screen Shot 2019-01-31 at 3.45.10 PM.png

Share this post


Link to post
Share on other sites
6 hours ago, nmano said:

Last login: Thu Jan 31 01:15:49 on console
Navaratnams-Mac-Pro-2:~ x58$ sysctl -n machdep.xcpm.mode
1
Navaratnams-Mac-Pro-2:~ x58$ 

I test now without FakecpuID 

set in bios profile 1 

overclock 4.2GHz

I need to get 10,000 more core score:)

I disable all kernel patches.

Thanks @PMheart

 

Screen Shot 2019-01-31 at 1.19.48 AM.png

If you get machdep.xcpm.mode = 1 without any kernel patch, then it proves what I said (that X299 is supported natively).

Well, if the performance is somewhat low, try applying the "performance fix".

Share this post


Link to post
Share on other sites
1 hour ago, PMheart said:

If you get machdep.xcpm.mode = 1 without any kernel patch, then it proves what I said (that X299 is supported natively).

Well, if the performance is somewhat low, try applying the "performance fix".

I test performance fix patched same result.

 

 

 

Thanks @PMheart

 

Screen Shot 2019-01-31 at 5.58.18 PM.png

Share this post


Link to post
Share on other sites
1 hour ago, nmano said:

I test performance fix patched same result.

 

 

 

Thanks @PMheart

 

Screen Shot 2019-01-31 at 5.58.18 PM.png

Please try the "old, long patch" (as we did before), the "old way" and "new way" (as I posted days ago) as well.

 

Thanks a lot!

Share this post


Link to post
Share on other sites
3 hours ago, PMheart said:

Please try the "old, long patch" (as we did before), the "old way" and "new way" (as I posted days ago) as well.

 

Thanks a lot!

I tested long patched 10.14.2 same result

I will test tomorrow 10.14.4 with long patch.

Thanks.

Share this post


Link to post
Share on other sites
3 hours ago, nmano said:

I tested long patched 10.14.2 same result

I will test tomorrow 10.14.4 with long patch.

Thanks.

Well, the "long patch" varies from time to time, are you sure that you are using the correct one?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

×