Help installing HighSierra on Xeon W-2175 and Asus WS C422 mobo

March 14, 2018

I did some test for you

You have an hang there because you have an option actvated to do not reboot on panic

I am pretty sure you will pass that KP only using kernel patch I shared in previous config.plist (it was known as piker alpha reboot fix)

without it..my old xeon hangs in same way!;)

Edited March 14, 2018 by Guest

obus · March 14, 2018

8 hours ago, jaraheel said:

try with the attached drivers64UEFI, and config.plist. Remove the SmallTree kext, and disable your network controller in BIOS, and other settings I previously mentioned. Also try a different USB port, as others have suggested.

drivers64UEFI.zip

config.plist

Ok @jaraheeleel

I tested with your driver and config.plist with no success.

I tested in 4 different USB ports USB 2.0 and 3.0.

In think the problem is that I get a kp straight after preeboot.

preboot.log

jaraheel · March 14, 2018

try with bootflags -v -x -f -v darkwake=0 npci=0x2000 kext-dev-mode=1 keepsyms=1 debug=0x100

obus · March 14, 2018

5 minutes ago, fabiosun said:

@obus

I did some test for you

You have an hang there because you have an option actvated to do not reboot on panic

I am pretty sure you will pass that KP only using kernel patch I shared in previous config.plist (it was known as piker alpha reboot fix)

without it..my old xeon hangs in same way!;)

Thank's for trying to help me out @fabiosun.

Could you precise more exactly witch patch you mean. At the moment I have so many config.plist so I need to start from some basic again.

If you please could send me the patch you mean I should be really happy. Im on may way out and back on friday for more testing.

Best regards

obus

March 14, 2018

obus

I attached all you need in my previous posted where I have quoted your message

Take a look there

March 14, 2018

8 minutes ago, jaraheel said:

try with bootflags -v -x -f -v darkwake=0 npci=0x2000 kext-dev-mode=1 keepsyms=1 debug=0x100

this bootflag are not useful for his problem

His system hangs (as @SammlerG said in his message) for a known register problem

This problem could be solved in different way

Simple and without risk only adding a "reboot fix patch"

obus · March 14, 2018

12 minutes ago, jaraheel said:

try with bootflags -v -x -f -v darkwake=0 npci=0x2000 kext-dev-mode=1 keepsyms=1 debug=0x100

Thanks for your effort @jaraheel.

Tried the new bootlflags and unfortunately the same result.

preboot.log

Edited March 14, 2018 by obus

obus · March 14, 2018

3 minutes ago, fabiosun said:

obus

I attached all you need in my previous posted where I have quoted your message

Take a look there

Ok I will do that.

I will reply as soon as I'm back.

Best regard

obus

March 14, 2018

obus

try this config

also you hve to choose a less sofisticated guide to start!:)

and if you start from this your hang

myconfig will help you to pass it

Edited March 14, 2018 by Guest
add some infos

SammlerG · March 14, 2018

for my X99, it was a problem with 2 or 3 msr calling of the xcpm routines when i disabled Piker Alphas xcpm patches.

I had do disable some msr.

jaraheel · March 14, 2018

1 hour ago, fabiosun said:

this bootflag are not useful for his problem

His system hangs (as @SammlerG said in his message) for a known register problem

This problem could be solved in different way

Simple and without risk only adding a "reboot fix patch"

oh thanks for enlightening me :). I am a bit of a noob myself

joedm ru · March 14, 2018

On 13.03.2018 at 9:33 PM, surfinchina said:

I'm not using the MSR patch. The Gigabyte boards thankfully don't need them.

Actually they do. My former X299 Aorus Gaming 3 went to panic on wake if MSR 0xE2 was not unlocked or without Pike's kernel patch applied. Not sure how sleep mode works for you.

surfinchina · March 14, 2018

23 minutes ago, joedm ru said:

Actually they do. My former X299 Aorus Gaming 3 went to panic on wake if MSR 0xE2 was not unlocked or without Pike's kernel patch applied. Not sure how sleep mode works for you.

That's funny, I don't use the bios patch and it's clearly unlocked. No kernel patch. Sleep works fine.

5aa988f1d0024_Screenshot2018-03-1509_40_40.png.6c80612a37f968105caaeba0ec001792.png

joedm ru · March 14, 2018

@surfinchina, well, perhaps Gaming 9 has it unlocked. But I spent days with Gaming 3 trying to figure out why sleep mode goes panic on wake until I applied Pike's patch preventing writing to that MSR.

yapan4 · March 15, 2018

How about Aspeed VGA onboard controller? It is disabled by jumper settings?

Also this mobo has some other specific HW, configured by jumpers...

yapan4 · March 15, 2018

Also check that you disable all CSM-legacy in BIOS setup for native UEFI boot

yapan4 · March 16, 2018

18 hours ago, iamyapan said:

Also check that you disable all CSM-legacy in BIOS setup for native UEFI boot

...now see in you jpg.pdf - all OK.

obus · March 16, 2018

On 3/14/2018 at 10:57 AM, fabiosun said:

@obus

I did some test for you

You have an hang there because you have an option actvated to do not reboot on panic

I am pretty sure you will pass that KP only using kernel patch I shared in previous config.plist (it was known as piker alpha reboot fix)

without it..my old xeon hangs in same way!;)

Hey @fabiosun.

I tested with your config.plist, efi drivers and only three kext ( FakeSMC.kext ,SmallTree-Intel-211-AT-PCIe-GBE.kext ,TSCAdjustReset.kext)

First I tested with only "xcpm_core_scope_msrs © Pike R. Alpha"-patch

and then I tested with only "xcpm_program_msrs (c) Pike R. Alpha"-patch.

Booth tests failed with a KP.

This is the text in preboot.log after test one and two:

19:538 0:000 - [00]: xcpm_core_scope_msrs © Pike R. Alpha :: [OS: 10.12 | MatchOS: All | MatchBuild: no] ==> allowed by OS
19:538 0:000 - [01]: xcpm_program_msrs (c) Pike R. Alpha :: [OS: 10.12 | MatchOS: 10.13.x | MatchBuild: no] ==> disabled by user

10:082 0:000 - [00]: xcpm_core_scope_msrs © Pike R. Alpha :: [OS: 10.12 | MatchOS: All | MatchBuild: no] ==> disabled by user
10:082 0:000 - [01]: xcpm_program_msrs (c) Pike R. Alpha :: [OS: 10.12 | MatchOS: 10.13.x | MatchBuild: no] ==> not allowed by OS

I've red somewhere you need to make sure to set KernelPm=true and KernelAndKextPatches/AppleIntelCPUPM=true. That's where MSR 0xE2 is used as well.

Any thoughts?

preboot_2.log

preboot_1.log

Edited March 16, 2018 by obus

March 16, 2018

It seems from your log msr program patch is not allowed

this patch should allow you to pass +++++ step

if you can try to delete in matchos 10.13.x and leave it blank

you should also restore a no patched biis if you are using a patched one

Edited March 16, 2018 by Guest

obus · March 16, 2018

7 minutes ago, fabiosun said:

It seems from your log msr program patch is not allowed

this patch should allow you to pass +++++ step

if you can try to delete in matchos 10.13.x and leave it blank

you should also restore a no patched biis if you are using a patched one

Hi @fabiosun.

Please clarify what you mean. Delete what/where?

I'm not using a patched bios for the moment.

As I understand it I need TSCAdjustReset.kext for a non patched bios. Do I need anything else?

March 16, 2018

please

for now forget guide you have followed in the past
That kext is not useful for your problem..and maybe it will be useful when you have a success in first installation to refine your system

try attached config

config.plist.zip

March 16, 2018

7:616  0:000  === [ StartLoader ] =======================================
7:616  0:000  Finally: ExternalClock=25MHz BusSpeed=100000kHz CPUFreq=2200MHz QPI: hw.busfrequency=100000000Hz
7:616  0:000  Loading boot.efi  status=Success
7:682  0:065  GetOSVersion: 10.13.3 (17D2104)
7:682  0:000  CSR_CFG: CSR_ALLOW_UNTRUSTED_KEXTS | CSR_ALLOW_UNRESTRICTED_FS
7:682  0:000  Filtering KextPatches:
7:682  0:000   - [00]: com.apple.iokit.IOPCIFamily (10.12-10.13::IOPCIConfigurator for X99, (credit Brumbear)) :: BinPatch :: [OS: 10.13.3 | MatchOS: All | MatchBuild: All] ==> allowed
7:682  0:000   - [01]: com.apple.driver.usb.AppleUSBXHCIPCI (Change 15 port limit to 24 in XHCI kext 10.13) :: BinPatch :: [OS: 10.13.3 | MatchOS: 10.13.3 | MatchBuild: All] ==> allowed
7:682  0:000   - [02]: IOAHCIBlockStorage (NoLabel) :: BinPatch :: [OS: 10.13.3 | MatchOS: All | MatchBuild: All] ==> allowed
7:682  0:000   - [03]: com.apple.driver.usb.AppleUSBXHCI (limit 10.13.4) :: BinPatch :: [OS: 10.13.3 | MatchOS: 10.13.4 | MatchBuild: All] ==> not allowed
7:682  0:000  Filtering KernelPatches:
7:682  0:000   - [00]: xcpm_assert_perf_max (c) okrasit :: [OS: 10.13.3 | MatchOS: 10.13.3 | MatchBuild: no] ==> allowed by OS
7:682  0:000   - [01]: xcpm_program_msrs (c) Pike R. Alpha :: [OS: 10.13.3 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS
7:682  0:000   - [02]: xcpm_idle patch by Pike R. Alpha :: [OS: 10.13.3 | MatchOS: All | MatchBuild: no] ==> disabled by user
7:682  0:000   - [03]: PM :: [OS: 10.13.3 | MatchOS: 10.13.4 | MatchBuild: no] ==> not allowed by OS
7:682  0:000  Will not patch boot.efi

I do not understand also why you have 10.12 OS before match OS you should have similar to one I quoted here

Have you a 10.13.3 usb boot pen drive?

obus · March 16, 2018

9 minutes ago, fabiosun said:

please

for now forget guide you have followed in the past
That kext is not useful for your problem..and maybe it will be useful when you have a success in first installation to refine your system

try attached config

config.plist.zip

33:473 0:000 - [00]: xcpm_core_scope_msrs © Pike R. Alpha :: [OS: 10.12 | MatchOS: All | MatchBuild: no] ==> allowed by OS
33:473 0:000 - [01]: xcpm_program_msrs (c) Pike R. Alpha :: [OS: 10.12 | MatchOS: All | MatchBuild: no] ==> allowed by OS

preboot.log

EFI.zip

obus · March 16, 2018

3 minutes ago, fabiosun said:


7:616  0:000  === [ StartLoader ] =======================================
7:616  0:000  Finally: ExternalClock=25MHz BusSpeed=100000kHz CPUFreq=2200MHz QPI: hw.busfrequency=100000000Hz
7:616  0:000  Loading boot.efi  status=Success
7:682  0:065  GetOSVersion: 10.13.3 (17D2104)
7:682  0:000  CSR_CFG: CSR_ALLOW_UNTRUSTED_KEXTS | CSR_ALLOW_UNRESTRICTED_FS
7:682  0:000  Filtering KextPatches:
7:682  0:000   - [00]: com.apple.iokit.IOPCIFamily (10.12-10.13::IOPCIConfigurator for X99, (credit Brumbear)) :: BinPatch :: [OS: 10.13.3 | MatchOS: All | MatchBuild: All] ==> allowed
7:682  0:000   - [01]: com.apple.driver.usb.AppleUSBXHCIPCI (Change 15 port limit to 24 in XHCI kext 10.13) :: BinPatch :: [OS: 10.13.3 | MatchOS: 10.13.3 | MatchBuild: All] ==> allowed
7:682  0:000   - [02]: IOAHCIBlockStorage (NoLabel) :: BinPatch :: [OS: 10.13.3 | MatchOS: All | MatchBuild: All] ==> allowed
7:682  0:000   - [03]: com.apple.driver.usb.AppleUSBXHCI (limit 10.13.4) :: BinPatch :: [OS: 10.13.3 | MatchOS: 10.13.4 | MatchBuild: All] ==> not allowed
7:682  0:000  Filtering KernelPatches:
7:682  0:000   - [00]: xcpm_assert_perf_max (c) okrasit :: [OS: 10.13.3 | MatchOS: 10.13.3 | MatchBuild: no] ==> allowed by OS
7:682  0:000   - [01]: xcpm_program_msrs (c) Pike R. Alpha :: [OS: 10.13.3 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS
7:682  0:000   - [02]: xcpm_idle patch by Pike R. Alpha :: [OS: 10.13.3 | MatchOS: All | MatchBuild: no] ==> disabled by user
7:682  0:000   - [03]: PM :: [OS: 10.13.3 | MatchOS: 10.13.4 | MatchBuild: no] ==> not allowed by OS
7:682  0:000  Will not patch boot.efi

I do not understand also why you have 10.12 OS before match OS you should have similar to one I quoted here

Have you a 10.13.3 usb boot pen drive?

Yes I saw that too. I have created this USB boot stick after the guide by KGP here: https://www.insanelymac.com/forum/topic/331658-how-to-build-your-own-imac-pro-successful-buildextended-guide/

Is there another way to make an installations USB for iMac Pro? Because I need a special edition of 10.13.3 17D2047 if I am correct informed.

I have a disk connected to my rig with this version already installed but if I try to boot to that disk with my EFI on my USB I have the same result with Kp and ++++++++++

March 16, 2018

I see different disk with an EFI on it

To install you do not need of a special iMac version but for your cpu it is advised then to have it

Could you try to boot with only USB pen attached?

OS 10.12 I see in your log is very weird..

maybe there is a mixing of things in your boot sequence

Help installing HighSierra on Xeon W-2175 and Asus WS C422 mobo

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites