Jump to content

[pre-release] macOS High Sierra


3,737 posts in this topic

Recommended Posts

You're welcome :)

 

Yes it's from 2016 but it will make more sense now that we can test it and use it first hand.

 

Watching it now. :) And yeah, with APFS, cloning doesn't take up extra space. Well, it does, but it's just a fraction of the initial size.

  • Like 1
Link to comment
Share on other sites

Oops. This could be catastrophic.

 

You can try with more longer & unique pattern to make it sure.. I finally found the way to determine exact kernel size from Pike LZVN and going to implement this into my other project, to let user choose to patch the whole prelinked or just the kernel. You can change Clover max range (KERNEL_MAX_SIZE = 40000000) to more accurate size to prevent those catastrophic..

  • Like 4
Link to comment
Share on other sites

Watching it now. :) And yeah, with APFS, cloning doesn't take up extra space. Well, it does, but it's just a fraction of the initial size.

I downloaded it and but haven't watched it completely, but I will watch it tonight ;)

Link to comment
Share on other sites

ACPIBatteryManager was loaded on my laptop HS PB3.

I checked all with debug log. Log is good. It seems same log like sierra.

FYi... for Battery issue, it also happened on some Real MBPs since DP1 I guess. So, it looks like Apple bugs with Beta... hmmb.  :rolleyes:

post-826765-0-15380300-1499992938_thumb.jpg

  • Like 2
Link to comment
Share on other sites

Hi, I don't know whether this is somewhat off-topic, if so, feel free to contact me and delete the post.

 

As for XCPM for unsupported CPUs patches of 10.13, please try this one:

 

1) Patch for _cpuid_set_info:

The disassembled code looks like this:

ffffff80003a1326	8a 05 21 5d 75 00 	movb	0x755d21(%rip), %al
ffffff80003a132c	04 72 	addb	$0x72, %al
ffffff80003a132e	3c d0 	cmpb	$-0x30, %al
ffffff80003a1330	77 50 	ja	0xffffff80003a1382

Alright, so that add is what we want to patch, and it's only needed for Broadwell-E CPUs, the patch will be:

75 00 04 72 3c d0 77 50 0f b6 c0
to
75 00 04 6a 3c d0 77 50 0f b6 c0

2) Patch for _xcpm_bootstrap:

The disassembled code looks like this:

ffffff80003d08c3	89 d8 	movl	%ebx, %eax
ffffff80003d08c5	04 c4 	addb	$-0x3c, %al
ffffff80003d08c7	3c 22 	cmpb	$0x22, %al
ffffff80003d08c9	77 22 	ja	0xffffff80003d08ed

And the patch will be:

89 d8 04 c4 3c 22 77 22
to
89 d8 04 xx 3c 22 77 22

Note: The xx is your exact platform CPUID, for example, the default one is 0x3C and I want it to be Ivy Bridge which is 0x3A, and the desired patch is:

89 d8 04 c4 3c 22 77 22
to
89 d8 04 c6 3c 22 77 22

3) Instant reboot fix

Look at these ones:

ffffff80003d107e	48 8d 3d 9b e1 65 00 	leaq	_xcpm_pkg_scope_msrs(%rip), %rdi
ffffff80003d1085	be 07 00 00 00 	movl	$0x7, %esi
ffffff80003d108a	31 d2 	xorl	%edx, %edx
ffffff80003d108c	e8 8f fc ff ff 	callq	0xffffff80003d0d20
ffffff80003d1091	83 fb 00 	cmpl	$0x0, %ebx
ffffff80003d1094	74 05 	je	0xffffff80003d109b
ffffff80003d1096	45 20 e5 	andb	%r12b, %r13b
ffffff80003d1099	74 13 	je	0xffffff80003d10ae
ffffff80003d109b	48 8d 3d ce e2 65 00 	leaq	_xcpm_core_scope_msrs(%rip), %rdi
ffffff80003d10a2	be 03 00 00 00 	movl	$0x3, %esi
ffffff80003d10a7	31 d2 	xorl	%edx, %edx
ffffff80003d10a9	e8 72 fc ff ff 	callq	0xffffff80003d0d20
ffffff80003d10ae	48 8d 3d 4b e3 65 00 	leaq	_xcpm_SMT_scope_msrs(%rip), %rdi
ffffff80003d10b5	be 0b 00 00 00 	movl	$0xb, %esi
ffffff80003d10ba	31 d2 	xorl	%edx, %edx
ffffff80003d10bc	e8 5f fc ff ff 	callq	0xffffff80003d0d20

Alright, so the patches will be:

# _xcpm_SMT_scope_msrs
be 0b 00 00 00 5d e9 08 00 00 00 -> be 0b 00 00 00 5d c3 90 90 90 90
and
be 0b 00 00 00 31 d2 e8 5f fc ff ff -> be 0b 00 00 00 31 d2 90 90 90 90 90

# _xcpm_core_scope_msrs
be 03 00 00 00 31 d2 e8 72 fc ff ff -> be 03 00 00 00 31 d2 90 90 90 90 90

# _xcpm_pkg_scope_msrs
be 07 00 00 00 31 d2 e8 8f fc ff ff -> be 07 00 00 00 31 d2 90 90 90 90 90

And if you want to disable the calls/jumps entirely, you should ret this offset:

ffffff80003d0d20	55 	pushq	%rbp  // Change this '55' to 'c3'

The patch is:

BE 0B 00 00 00 5D E9 08 00 00 00 0F 1F 84 00 00 00 00 00 55 48 89 E5 41 57 -> BE 0B 00 00 00 5D E9 08 00 00 00 0F 1F 84 00 00 00 00 00 C3 48 89 E5 41 57

EDIT @ 22/06/17: Removed redundant bytes for 10.13 DP2 compatibility

 

@PMheart, please would you be so kind and also provide the correct 10.13 _cpuid_set_info and _xcpm_bootstrap KernelToPatch entries for unsupported Haswell-E and Ivy-Bridge processors? I am sure many people would be interested! Many thanks in advance!

 

KGP

 

P.S.: My Broadwell-E System is up and successfully running XCPM! Many thanks for the correct 10.13 xcpm KernelToPatch entries for this kind of processor architecture.

Link to comment
Share on other sites

@PMheart, please would you be so kind and also provide the correct 10.13 _cpuid_set_info and _xcpm_bootstrap KernelToPatch entries for unsupported Haswell-E and Ivy-Bridge processors? I am sure many people would be interested! Many thanks in advance!

 

KGP

 

P.S.: My Broadwell-E System is up and successfully running XCPM! Many thanks for the correct 10.13 xcpm KernelToPatch entries for this kind of processor architecture.

Hi. Sure. Here you are:

First of all. Both Haswell-E and Ivy Bridge don't need to patch _cpuid_set_info().

 

# Haswell-E

# _xcpm_bootstrap
89 d8 04 c4 3c 22 77 22 -> 89 d8 04 c1 3c 22 77 22

# Ivy Bridge

# _xcpm_bootstrap
89 d8 04 c4 3c 22 77 22 -> 89 d8 04 c6 3c 22 77 22

And also, don't forget to add necessary instant reboot fix patches!

  • Like 2
Link to comment
Share on other sites

Hi. Sure. Here you are:

First of all. Both Haswell-E and Ivy Bridge don't need to patch _cpuid_set_info().

 

# Haswell-E

# _xcpm_bootstrap
89 d8 04 c4 3c 22 77 22 -> 89 d8 04 c1 3c 22 77 22

# Ivy Bridge

# _xcpm_bootstrap
89 d8 04 c4 3c 22 77 22 -> 89 d8 04 c6 3c 22 77 22

And also, don't forget to add necessary instant reboot fix patches!

 

Where I can find "Instant reboot fix patches". Thanks.

Link to comment
Share on other sites

Yes. That's enough.

 

Sorry for my english.

 

I wanted just to know if these patches were really interesting or indispsensable for my config under macOS 10.13

Link to comment
Share on other sites

Sorry for my english.

 

I wanted just to know if these patches were really interesting or indispsensable for my config under macOS 10.13

Well, the patch for _xcpm_bootstrap() is indispensable to enable XCPM. And instant reboot fix could not be obligatory. On my E3 1230 v2 I just need the patch for _xcpm_pkg_scope_msr

I'm stuck here, any suggestion?

DB1, DB2, DB2U1 works for me but DB3 stuck here.

a2f98b95f621e97688ab2febf3807055.jpg9d0066a8dc73f1f29d1472d9d8ddbafc.jpg

 

Sent from my HTC One M9 using Tapatalk

I guess USB problems.

  • Like 1
Link to comment
Share on other sites

Well, the patch for _xcpm_bootstrap() is indispensable to enable XCPM. And instant reboot fix could not be obligatory. On my E3 1230 v2 I just need the patch for _xcpm_pkg_scope_msr

I guess USB problems.

I'm trying to install from internal hdd, not from usb.

Link to comment
Share on other sites

I see. Sorry. Try removing FakeSMC sensors/plugins then.

Ok, now I have only FakeSMC without plugins in kexts/other and removed all usb devices and got the same problem.

becb847c6424cea31b684410e020c114.jpg

 

Sent from my HTC One M9 using Tapatalk

Link to comment
Share on other sites

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