Jump to content

amadeusex

Members
  • Content Count

    74
  • Joined

  • Last visited

About amadeusex

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL
    https://www.facebook.com/mitrentsis

Profile Information

  • Gender
    Male
  • Location
    Athens Greece

Recent Profile Visitors

1,204 profile views
  1. As far as I can remember it's not destructive but it's invasive - there has to be at least one pin of the bios chip unsoldered and soldered again. Here's the link from the HP forum. Message 60 from the thread: ‎06-19-2015 03:58 AM It has been DONE! Simple but requires patience and hardware skills ... I removed the Flash chip (see elsewhere in this thread for the location), read out the contents with an external programmer, replaced the Boot Block (0xFF0000 to 0xFFFFFF) with the one from the Boot Block from that in a recent (v3.65) BIOS Softpack binary, reprogrammed the Flash chip with updated binary (original code from 0x000000 to 0xFEFFFF plus new Boot Block), and then soldered it back on the motherboard. Works like a charm ... all the MAC addresses and ATM remain intact. Takes a while but with the cost of a new board, well worth the effort. Procedure step by step Any Electronics repair shop should be able to do that, I even had an appointment here in Athens to do it for 20 euro. What the procedure actually does is to upgrade the boot block which prevents the v1 version to update the necessary code to recognize the Ivy xeons. You can downgrade Bios as You wish.
  2. @WoodCabin Well done Could You post Your EFI folder ? There is a possibility to upgrade the Bios of the v1 820 to use Ivy bridge Xeons ...
  3. @WoodCabin Great news man What was the culprit ?
  4. I'm in a similar situation ... Did some migration with Win 10 from my older z820 v1 and then went back to MacOs only to discover that pm is not working anymore - mind You, I didn't change a thing besides adding a DSP card (UAD-2 duo). Insane situation - I'll try to get to the bottom of the cause but I'm slowly running out of patience here ...
  5. I'm on tour now as mentioned earlier. I'll check the IOreg readings when I get back. As far as I remember though they show up just fine while clover boots for whatever reason. Man I'm used to really weird stuff and a lot of times I think it has to do with Voodoo. But it's also fun and just looking at a working system gives you the satisfaction to justify all the hassle
  6. Yeah I guess the 1 CPU with 32 threads is the most plausible explanation but to be honest, after all those hours wasted I couldn't care less about why it works right now.
  7. Finally ... z820v2 with 3.92 Bios dual Xeon E5 2687W v2 64GB ram and a Radeon Red Devil RX-580 8 GB My EFI Folder - EFI.zip My aicpupm.kext AICPUPM.kext My patched LegacyX86PlatformPlugin.kext LegacyX86PlatformPlugin.kext Put both Kexts to S/L/E and repair permissions. ssdrPRGen command used : ./ssdtPRGen.sh -m custom (ssdt-1.aml provided by @bilbo renamed to SSDT.aml and placed to Desktop together with APIC.aml) What did the trick was to use both patches mentioned in bilbos guide under point 28 ! What remains now is to reinstall High Sierra on a bigger disk or maybe even just restore the one i have to another SSD (i know bilbo doesn't like the idea but this is going to save a lot of time). Thanks to @bilbo for the excellent guide and all the effort and to @hugodlc for taking the time and all the back and forth tinkering !
  8. Now here's the catch ... Turns out the SSDT-1.aml i've used is the one bilbo provided (the one with the many scopes). The system was sluggish already and i just kept it on an older SSD as a backup so it's difficult to judge from here about the what causes it. I've just replaced it with the one i've edited and am stuck again without any c-states whatsoever. Right now i have to get some sleep bc i promised to take my daughter to the beach and will be on tour (Wednesday till Sunday) so no more tinkering for now. We're closing in i guess ... somehow hahaha Take care and thanks a lot Here's geekbench 4 without c-states btw ...
  9. Now if this isn't going to drive me crazy I don't know what is ... I had a HDD failure while trying to get working PM. I also had an old SSD with High Sierra from my other machine z820 v1 with the dual sandy bridge 2670 v1. Now ... I thought it is worth a shot and booted up with the USB drive and copied the EFI from the z820 v2 to the SSD. The elaborate SSDT and DSDT combo didn't work of course so i tried an earlier combo and take a guess - C-states are still not working but the CPU now runs up to 3.8 GHz. My best guess is that (i remember reading somewhere about it but can't remember where) the 2687w v2 needs the also the sandy-bridge patch (step 1 of stinga's tutorial - step 28 of bilbo's guide) because i left the AICPUPM.kext i've patched for the 2670v1 (<- Sandy Bridge CPU) untouched on purpose. Strange though is that albeit the single-core performance climbed from 3100 to 3500 in geekbench 4 the multicore sacked to 26700 (from 37-38k). ... to be continued - sigh !
  10. Which was wrong - here's another one. SSDT-1.aml
  11. - that's why You end up with \_SB.C010 and \_SB.C110 instead of \_SB.C00F and \_SB.C10F when You start with \_SB.C001 / C101. Well - I've tried what you suggested but still no c-states working. I really have wasted a couple of days trying and editing and whatnot. Multicore results aren't that bad - slightly better than on Win 10 so i guess in general the machine is working. Single core is way lower though (3100 vs 3670 in Win 10) but looking at the bright side here and not worrying so much. On another note I've edited Your SSDT-1.aml because there was something i've noticed with the scopes. Here's the (supposedly) corrected SSDT-1.aml SSDT-1.aml
  12. Hi Well that's not that easy to answer - according to HW Monitor there's activity on the Graph but the nominal readouts stay at 3.37 GHz - Have a look. The 1st screenshot is Idle with Chrome open. - the 2nd shows a cinebench multicore run (@ 2/3 in the graph timeline ) Turbo gets never activated - even with the cinebench single core bechmark the frequency never goes over 3.37. (dropdown screenshot) IDLE CINEBENCH RUN In the non-graph the readout of the cpu CPU cores 1-8 stays always at x34 and 3.37 GHz. Only Cpu-Package average and the Power Consumption readouts fluctuate.
  13. @hugodlc Man, You've made my day - there's hope to get pm working here. I've tried to use the modified SSDT-1.aml to generate the SSDT and edited the resulting DSDT to include all 16 cores. The problem that persists though is an "Out of control with CPU numbers error" in the clover boot-log. I suspect that the reason for that is the unique problem with the Ivy-Bridge E5 2687w v2 which needs to have cpu-scopes from Scope (\_SB.C001) to Scope (\_SB.C010) and Scope (\_SB.C101) to Scope (\_SB.C110) instead of Scope (\_SB.C000) to Scope (\_SB.C00F) and Scope (\_SB.C100) to Scope (\_SB.C10F). Attached are the files I've tried. Maybe someone could point me in the right direction here since I don't have a clue how to change them properly. SSDT-1.aml SSDT.aml bootlog.txt
  14. @gawdemmet Yeah the benchmarks don't look that good but they're just that - benchmarks. With win 10 I get a single core mark around 3700 and 36-38 K multi-core. What's more important though is the performance gain in applications which is around plus 30% compared to my 2670v1 (in win10). I don't believe the clock readings (2147THz !) I get here so there's either some more tinkering to be done to get power management working or it stays the way it is. To be honest all the applications I need are also available for Win 10 which runs just fine. At this point the macOs environment is a nice 'add-on' but not essential anymore. The OCD in me wants to make it work but I guess the fact that the 2687w is a special case is going to prevent a perfect working power management.
  15. Hi guys .. I finally took the plunge and went ahead to install High Sierra on my z820 with the 2687w v2 ... What's the problem here ? The sensors ? Is Power management working ?
×