Jump to content
obus

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

316 posts in this topic

Recommended Posts

19 hours ago, obus said:

Hi @fabiosun

Everything is working fine on my new rig and I am happy with the performance overall. You told me earlier that you have some experience with patching ASUS motherboard with locked mainboard BIOS MSR 0xE2 register.

Is it possible for you to help me with a patch for my mainboard? As I understand it I could get rid of booth Fake CpuId, PM-patch, xcpm_program_msrs (c) Pike R. Alpha-patch and TSCAdjustReset.kext.

With best regards

obus

The first thing you need to know is what name the file with bios firmware should have, since the file name is always special to motherboard. If you just put the file with firmware as it is - it won't be flashed. And "BIOS Flashback" is the only way to write modified firmware into you bios chip.

Also please note that I'm not responsible for any damage/data loss/whatever. You do it all on your own risk.

So you need to do:

  1. Contact ASUS support and ask them about firmware file name to use with BIOS Flashback. Or try to find it by yourself, but as for me, I wans't succesful and asked ASUS support.
  2. Download the latest firmware for your motherboard.
  3. Use latest UEFIPatch with patches.txt from KGP's guide to patch your firmware. These patches unlock MSR 0xE2 and disable writes to TSR, so you won't need Pike's patch and TSCAdjust. 
  4. Grab a USB flash drive which should not be larger than 8 GB. Format it to FAT32 and put a file with patched firmware to flash drive root. Make sure it has the proper name from p.1. I'd also suggest to prepare two flash drives where the second should contain unmodified firmware in order to be able to restore the original firmware if something goes wrong.
  5. Shut down your rig.
  6. Plug the flash drive from p.4 with patched firmware into a special BIOS Flashback USB slot. Refer to your motherboard manual to find it out.
  7. DO NOT POWER UP you rig.
  8. Press and hold BIOS Flashback button until a blue LED starts flashing. Wait until the LED goes off (3-5 min). 
  9. Unplug your rig from wall and wait for 1 min. Then open your rig case and press 'CLR_CMOS' button on your motherboard. Refer to your motherboard manual to find out the button and clear bios settings.
  10. Power on your rig and you are done.
2 hours ago, obus said:

The patched bios was installed without no problems

I don't think you actually have this installed.

Edited by joedm ru

Share this post


Link to post
Share on other sites
Advertisement

@obus, I also still don't get why you need FakeCPUID. Your Xeon has the CPUID exactly the same as my Core i9 has, and I never used FakeCPUID. Could you please attach your current EFI folder?

Share this post


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

@obus, I also still don't get why you need FakeCPUID. Your Xeon has the CPUID exactly the same as my Core i9 has, and I never used FakeCPUID. Could you please attach your current EFI folder?

Hi @joedm ru

When I flashed the patched (KGP's) bios earlier today I did exactly as you explain in your guide. I'm sure the bios was flashed correctly but as I said in my earlier post nothing changed. I still have to use my clover patch and FakeCpuid to boot. I tried with and without clover patches and FakeCpuid in several different combinations without success. I attach my config.plist only because I still can't upload a zipped EFI map without getting an upload error even if the file is smaller than 10 mb.

My EFI driver is standard clover 4411 AptioMemoryFix + latest APFS extracted with pacifist from my installation USB. Kext only FakeSMC,Lilu,AppleALC and TSCAdjustReset.

SSDT-XOSI in ACPI  Patched folder.

Thats it.

Any ideas?

Ps. I know the flash was lucky because I flashed a new "Welcome to iMacPro logo instead of the ASUS incredible or whatever...d.s 

config.plist

Edited by obus

Share this post


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

You are confusing some aspects related to a patched bios role in your hack
1) with a patched bios as you say to have, have you tested if msr is really unlocked?Simply also checking clover bootlog you can create inside clover configurator

2) you miss another part following guide for X type CPU, your is different

3) check in your actual bios  in advanced CPU parameter if you have some part related to CFG config or similar, then also check latest 0502 bios if it has this feature which could unlock some msr for you

and so also if you have an unlocked MSR 0xe2 register you should have the need of a msr program kernel patch to boot (only strangeness is broadwell EP fakecpuid you are using now)
for your information in my X99 Xeon I have to use Always MSR program kernel patch (also with a patched bios) so it could be normal also for you if you have tested well without mixing too many things

Also, we see your cpu acts in a different way from X cpu series , so you can try to use applecpuintelinfo to see some usefull stuff and to understand better.

These tests could be done only by you..and no one has a real experience on your Platform here ;)

 

Thank's for your answer fabiosun.

I will test a little bit more and contact ASUS Sweden tomorrow and ask if they could provide me with an unlocked bios.

ApplecCpuIntelInfo makes my os crash so it's not an option. 

I will come back with more info.

 

Share this post


Link to post
Share on other sites

@obus

Appleintelcpuinfo can crash also in supported system due very and old reasons

you can do a copy of text like you can see in my pictures here and post what is inside it in particular way take look at

0:100  0:000  BrandString = Intel(R) Xeon(R) CPU E5-2696 v4 @ 2.20GHz
0:100  0:000   The CPU supported turbo
0:100  0:000  MSR 0x35              16002C
0:100  0:000  MSR 0xE2 before patch 00008400
0:100  0:000  MSR 0xE2 is locked, PM patches will be turned on

0:100  0:000  MSR 0xCE              20080C3B_F2811600
0:100  0:000  MSR 0x1B0             00000000
0:100  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz

If your bios is patched it will be different

I would like also to advice you to try latest bios (0502) I see it in Asus site

Maybe there in advanced CPU option you can find a way to unlock MSR as I see in new X299 ASUS bios release

 

 

Screen Shot 2018-03-25 at 5.41.16 PM.png

4 hours ago, joedm ru said:

 

  1. Contact ASUS support and ask them about firmware file name to use with BIOS Flashback. Or try to find it by yourself, but as for me, I wans't succesful and asked ASUS support.
  2.  

You have to read your manual flashback name is inside chapter two in your case

 

Screen Shot 2018-03-25 at 5.54.20 PM.png

Share this post


Link to post
Share on other sites

and this is for @obus i think

 

Screen Shot 2018-03-25 at 5.57.41 PM.png

4 hours ago, joedm ru said:

@obus, I also still don't get why you need FakeCPUID. Your Xeon has the CPUID exactly the same as my Core i9 has, and I never used FakeCPUID. Could you please attach your current EFI folder?

Also with Broadwell E/EP cpu (E are not Xeon Ep are xeon) different behavior so ie 6900 could not use a fake Cupid and xeon 2696V4 must use
I have tried for @obus a non conventional way because all tries he was doing lead him to a ++++++++

 

Share this post


Link to post
Share on other sites

 

@fabiosun.

All this stuff with flashing my bios is not a problem for me. I know all about renaming .CAP file to WSCSE.CAP  already flashed a KGP patched bios successfully in terms of FLASHING but in terms of unlocking my mainboard with a NEGATIVE result as I wrote in my earlier post. I know the flashing was working because after the flash I had the new Welcome to iMacPro logo during preboot.

What I need to learn is which patch I need for unlocking just my specific mainboard.

I already tried the new bios 0502 and there is no difference in behaviour and no option in bios to unlock MSR. 

This is the text in my bootlog you asked for

0:100  0:000  BrandString = Intel(R) Xeon(R) W-2175 CPU @ 2.50GHz
0:100  0:000   The CPU supported turbo
0:100  0:000  MSR 0x35               E001C
0:100  0:000   TSC/CCC Information Leaf:
0:100  0:000    numerator     : 208
0:100  0:000    denominator   : 2
0:100  0:000   Calibrated ARTFrequency: 24003471
0:100  0:000  MSR 0xE2 before patch 00008402
0:100  0:000  MSR 0xE2 is locked, PM patches will be turned on
0:100  0:000  MSR 0xCE              00070A2C_F3811900
0:100  0:000  MSR 0x1B0             00000000
0:100  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz

Edited by obus

Share this post


Link to post
Share on other sites

what do you mean with a KGP patched bios?

Has he your same system?

When you patch your bios have you a similar output from uefipatch terminal?

Last login: Sun Mar 25 17:33:34 on console
fabios-iMac-Pro:~ fabio$ cd desktop
fabios-iMac-Pro:desktop fabio$ /Users/fabio/Desktop/UEFIPatch WS-C422-PRO-SE-ASUS-0502.CAP
parseImageFile: Aptio capsule signature may become invalid after image modifications
parseVolume: unknown file system 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A
parseFile: non-empty pad-file contents will be destroyed after volume modifications
parseFile: non-empty pad-file contents will be destroyed after volume modifications
patch: replaced 8 bytes at offset 4380h 81E10080000033C1 -> 9090909090909090
patch: replaced 8 bytes at offset 4380h 81E10080000033C1 -> 9090909090909090
patch: replaced 45 bytes at offset 1506h B9E20000000F328BC8BE0080000023CE0BCF75190BC6894424088954240C8B54240C8B442408B9E20000000F30 -> BA00000000B800000000B93B0000000F3090909090909090909090909090909090909090909090909090909090
patch: replaced 45 bytes at offset 1506h B9E20000000F328BC8BE0080000023CE0BCF75190BC6894424088954240C8B54240C8B442408B9E20000000F30 -> BA00000000B800000000B93B0000000F3090909090909090909090909090909090909090909090909090909090
Image patched
fabios-iMac-Pro:desktop fabio$ 

by the way if you want to check with yours file..this is a patched file for your MB (0502)

https://we.tl/IzdrZgkF28

use it if you Know what you are doing and obviously at own risk ;)

 

Share this post


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

other my question / curiosity is..

which problem do you have with your actual working config?

:)

 

My friend @fabiosun

None. I just want as little as possible in my EFI folder and in my config.plist. This is sickness since Osmozis time.:whistle:

Share this post


Link to post
Share on other sites

OK @fabiosun

Flashed the patched bios 0502 you provided.

KP after reboot without patch: xcpm_program_msrs (c) Pike R. Alpha and FakeCPUId.

Working with patch: xcpm_program_msrs (c) Pike R. Alpha and FakeCPUId

Log:

0:100  0:000  === [ GetCPUProperties ] ==================================
0:100  0:000  CPU Vendor = 756E6547 Model=50654
0:100  0:000   The CPU supported SSE4.1
0:100  0:000  BrandString = Intel(R) Xeon(R) W-2175 CPU @ 2.50GHz
0:100  0:000   The CPU supported turbo
0:100  0:000  MSR 0x35               E001C
0:100  0:000   TSC/CCC Information Leaf:
0:100  0:000    numerator     : 208
0:100  0:000    denominator   : 2
0:100  0:000   Calibrated ARTFrequency: 24003504
0:100  0:000  MSR 0xE2 before patch 00008402
0:100  0:000  MSR 0xE2 is locked, PM patches will be turned on
0:100  0:000  MSR 0xCE              00070A2C_F3811900
0:100  0:000  MSR 0x1B0             00000000
0:100  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz

Share this post


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

You have to read your manual flashback name is inside chapter two in your case

Thanks for pointing this! Unfortunately, I used my hardcopy motherboard manual and it doesn't contain this information. 

Share this post


Link to post
Share on other sites
11 minutes ago, obus said:

KP after reboot without patch: xcpm_program_msrs (c) Pike R. Alpha and FakeCPUId.

This is really weird. I suspect that the patches.txt file you use either incomplete or invalid. Indeed, try to contact ASUS support and ask them to provide firmware with unlocked 0xE2.

 

Share this post


Link to post
Share on other sites

@obus

so interferenc patches seem are not good for your bios

tomorrow i will use old patches with your bios if you want to try again

in my opinion also with a patched bios you couldnt avoid to use some patches in config

when you have some time post here images of cpu advanced section and cpu bios section of your bios motherboard

thank you

Share this post


Link to post
Share on other sites
5 minutes ago, fabiosun said:

@obus

so interferenc patches seem are not good for your bios

tomorrow i will use old patches with your bios if you want to try again

in my opinion also with a patched bios you couldnt avoid to use some patches in config

when you have some time post here images of cpu advanced section and cpu bios section of your bios motherboard

thank you

Thank's @fabiosun

I will test. I have all the time in the world (pension).

I will upload some pics from my bios.

Cheers!

 

Edited by obus

Share this post


Link to post
Share on other sites
5 hours ago, obus said:

I attach my config.plist only because I still can't upload a zipped EFI map without getting an upload error even if the file is smaller than 10 m

Could you please also provide original ACPI tables? Press F4 when Clover bootloader in on your screen. Then find the tables in Clover/ACPI/origin folder. I've got an idea how to get rid of FakeCPUID for you. If the forum doesn't allow you to attach it, please use any file share service like MediaFire or Dropbox.

Share this post


Link to post
Share on other sites
10 minutes ago, joedm ru said:

This is really weird. I suspect that the patches.txt file you use either incomplete or invalid. Indeed, try to contact ASUS support and ask them to provide firmware with unlocked 0xE2.

 

I will talk to ASUS sweden support tomorrow and ask for a firmware with unlocked 0xE2 register.

Share this post


Link to post
Share on other sites
5 minutes ago, joedm ru said:

Could you please also provide original ACPI tables? Press F4 when Clover bootloader in on your screen. Then find the tables in Clover/ACPI/origin folder. I've got an idea how to get rid of FakeCPUID for you. If the forum doesn't allow you to attach it, please use any file share service like MediaFire or Dropbox.

Here you go!

APIC.aml

BERT.aml

BGRT.aml

DBG2.aml

DBGP.aml

DSDT.aml

EINJ.aml

ERST.aml

FACP.aml

FACS.aml

FIDT.aml

FPDT.aml

HEST.aml

HPET.aml

LPIT.aml

MCFG.aml

MIGT.aml

MSCT.aml

NITR.aml

OEM1.aml

OEM2.aml

OEM4.aml

PCCT.aml

RASF.aml

RSDP.aml

RSDT-FACP.aml

RSDT-FACS.aml

RSDT.aml

SLIT.aml

SRAT.aml

SSDT-0-SSDT PM.aml

SSDT-1-A M I.aml

SSDT-2-sensrhub.aml

SSDT-3-PtidDevc.aml

SVOS.aml

UEFI.aml

VFCT.aml

WDDT.aml

WSMT.aml

XSDT.aml

Share this post


Link to post
Share on other sites
25 minutes ago, fabiosun said:

@obus

so interferenc patches seem are not good for your bios

tomorrow i will use old patches with your bios if you want to try again

in my opinion also with a patched bios you couldnt avoid to use some patches in config

when you have some time post here images of cpu advanced section and cpu bios section of your bios motherboard

thank you

Here you go!

180325195018.BMP

180325195026.BMP

180325195106.BMP

180325195008.BMP

180325194953.BMP

40 minutes ago, fabiosun said:

@obus

so interferenc patches seem are not good for your bios

tomorrow i will use old patches with your bios if you want to try again

in my opinion also with a patched bios you couldnt avoid to use some patches in config

when you have some time post here images of cpu advanced section and cpu bios section of your bios motherboard

thank you

Here are two more.

180325194944.BMP

180325194932.BMP

Share this post


Link to post
Share on other sites
52 minutes ago, obus said:

SSDT-0-SSDT PM.aml

Try to drop this table and remove fake cpuid. You don't need any cpu tables for HWP enabled mode. If there is a KP, capture it by your phone or any other camera.

Share this post


Link to post
Share on other sites
16 minutes ago, joedm ru said:

Try to drop this table and remove fake cpuid. You don't need any cpu tables for HWP enabled mode. If there is a KP, capture it by your phone or any other camera.

KP after preboot.

IMG_0483.jpg

Share this post


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

Hmm... strictly speaking this is not a KP, but boot.efi got stuck for some reason. OK, so far I'm out of ideas, sorry.

And now I have another problem with my new RX Vega 64.

Any comments?

 

Untitled.png

Share this post


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

 

for bios If you want try this

https://we.tl/DQFh5qSdp2

 

and see of msr is locked or not

this msr if also unlocked does not solve others "problem

It seems that your patch is working but I still needs "msr-patch" in clover and FakeCPUID.

This time I booted without any patch and CPUID and get KP after preboot.

preboot log is showing patching?

0:100  0:000  === [ GetCPUProperties ] ==================================
0:100  0:000  CPU Vendor = 756E6547 Model=50654
0:100  0:000   The CPU supported SSE4.1
0:100  0:000  BrandString = Intel(R) Xeon(R) W-2175 CPU @ 2.50GHz
0:100  0:000   The CPU supported turbo
0:100  0:000  MSR 0x35               E001C
0:100  0:000   TSC/CCC Information Leaf:
0:100  0:000    numerator     : 208
0:100  0:000    denominator   : 2
0:100  0:000   Calibrated ARTFrequency: 24003318
0:100  0:000  MSR 0xE2 before patch 00008402
0:100  0:000  MSR 0xE2 is locked, PM patches will be turned on
0:100  0:000  MSR 0xCE              00070A2C_F3811900
0:100  0:000  MSR 0x1B0             00000000
0:100  0:000  FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 

preboot.log

Edited by obus

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   0 members

    No registered users viewing this page.

×