Menu
TL;DR - Bootéd Leopard (10.5.4ish) and overclocked 3.2GHz to 3.32GHz after that cozy reboot into 10.13.6 and retained overclocking. I know it isn't a massive quantity and likely will end up being an 'unfelt modification' but it't still fun.
So the various other day I was poking around the net and ran into the actually old threads about overclocking the cMP (back again when it had been the most recent machine). I acquired earlier overclocked my MacPró3,1 2.8Ghz 8 core machine to something aróund 3.1Ghz, but as it relied on 32bit KEXT it didn't work dependably after Leopard sincé 64bit kernel grew to become all the rage, and while some could obtain it to function making use of 32bit kernel in Lion (10.7) others could not really. I used to be able to make use of it in Lión in 32bit kernel mode, however that no longer functions for reasons I'm not sure of.
(the app says i'meters not using a supported system as there is certainly no response from the smbus control name probe that it does). The time/time clock skew issue also converted some people off from this as just the 3,1 got a method around this (comfortable reboot helps to keep OC but corrects the clock skew and allows you to boot any various other OS and retain OC) I began playing around with obtaining an outdated 32bit kernel OS to boot, Lion has been my 1st selection as it had been the most recent one with 32bit kernel choice. Obtained it installed and terminated up the ZDNét app to possess it inform me thát it wásn't a supported platform. Then made a decision to consider Leopard rather as that has been brand-new when this app had been new and thought it would end up being the best possibility. I had been really questioning if this wasn't functioning as I had swapped my processors a few years ago with the dual quad 3.2GHz ones replacing the double quad 2.8GHz types I purchased brand-new. After some problems obtaining Leopard to shoe, (MP3,1 I think requires 10.5.2 in purchase to shoe without panic) and my personal hardware adjustments (additional SATA3 control, extra RAID credit cards, GTX650) I ended up with á 10.5.4-ish setup, kernel from 10.5.8 and the AHCI kext from 10.5.8 included to the 10.5.4 foundation, along with elimination of aIl NVDA and GéForce kexts / plugins. Not performing this just meant anxiety or obtaining stuck at the finish of the boot procedure as it couldn't weight graphics correctly (GTX650 assistance didn't arrive until 10.7.4) Man Leopard is certainly FAST on SSD also when simply using Software renderer for the GPU, shoe is insane quick and GUI can be loaded 'now'.
It most likely requires 10x longer to shoe 10.13 vs . 10.5 on the exact same hardware.
I furthermore got the pleasure of listening to the delightful video (didn't screen since I wear't have GPU accel) while I has been heading through the preliminary setup wizard, man possess things changed there (we utilized to have all kinds of various install products and simply a much better UX / UI in my viewpoint). So cross types Leopard packed the overclock.kext without concern and the app detected my MacPro properly. I experienced many hangs and panics attempting to get the overclock going as higher as I could. It appears finicky, signifying if I can obtain it to 408MHz on FSB then I can get to 415MHz (providing 3.32GHz effective clock) I possess to slowly phase up the regularity it seems, obtaining over the 407/408 stage can be panic vulnerable. (incidentally found out that Apple blocks stress reviews from 10.5 from getting received on their finish) I did deal with to get over the 415MHz stage once but wasn't capable to repeat it. I perform have got 3 densities of Memory set up (1G, 2G, 4G) all of differing brands, which most likely will be where the problems arrive from, in one stress record it was machine check out exception (directing at ECC that wasn'capital t able to become recovered) I'd wager with much better / constant RAM setup I could get higher. RAM gets OC'd along with CPU and FSB with this technique of OC.
Now in 10.13 you can't appear to find any proof that you have a increased than stock clock rate. All varieties of benchmark apps seem to see 3.2GHz. I did manage to find one sysctl that shows the higher price (showing the sleep of the regularity information for posterity). Onderwerp nieuw msn-messenger for mac os x. Code: macpro-osx: Iudacrisvp$ sysctl -a grép freq hw.busfréquency: hw.busfréquencymin: hw.busfréquencymax: hw.cpufréquency: hw.cpufréquencymin: hw.cpufréquencymax: hw.tbfrequency: machdép.tsc.regularity: And oddly plenty of the Gain10 VM views the increased clock rate, but my Linux VM doesn'capital t.
Zdnet Clock: Overclocking For Mac Windows 10
I've only distributed 3 cores with Get 10 (mcafee on-access scanning device is usually pegging Central processing unit): Geekbench doesn'capital t discover the clock change either. I'meters not sure how to set FSB viá grub2 (I'vé not really had grub in my boot chain for several years, just rEFInd at this point). Hp printer driver for mac os x el capitan. Would that possibly be a more reliable / easier way to OC? Making use of this device from OSX methods the frequency up ón MHz at á period and if you have got it proceed too fast you risk panic / stop owing to storage errors that may not occur if one has been doing it at shoe time vs inside an active OS. And consequently be able to make use of a increased clock perfect out of the gate (probably I could 'cold' boot with a 425MHz FSB setting -or actually to 450Mhz that somebody claimed getting a even though back- but going to it can't occur dependably inside the Operating-system for illustration). I'll have to find some time later on to boot windows natively and appear into SetFSB, but probably some of this details is exposing for those that understand more than I do (I'm no expert but I discover byte 10 becoming transformed for clock velocity and byte 12 getting changed in the beginning - probably this enables the worth of byte 10 to become updated on-the-fly).
Zdnet Clock: Overclocking For Mac Pro
Code: Sep 3 00:18:28 ludacrisvps-mac-pro authexec160: executing /Users/ludacrisvp/Desktop/ZDNét Clock.app/Contents/Resources/initkernel Sep 3 00:18:28 ludacrisvps-mac-pro kernel0: ZDNet.para: MacPro/Xserve overclocking kernel expansion - Version 1.0 Sep 3 00:18:28 ludacrisvps-mac-pro kernel0: ZDNet.de: Copyright (chemical) 2008 CNET Systems Deutschland GmbH Sép 3 00:18:28 ludacrisvps-mac-pro kernel0: ZDNet.de: Writer Christoph L. Hochstaetter (ZDNetClock@ZDNétLabs.DarkTech.org) Sép 3 00:18:28 ludacrisvps-mac-pro kernel0: ZDNet.de: Overclocking KEXT loaded successfully. Sep 3 00:18:28 ludacrisvps-mac-pro authexec167: carrying out /usr/sbin/sysctI Sep 3 00:18:29 ludacrisvps-mac-pro kernel0: ZDNet.para: Probing SMBus control.found. Sep 2 21:11:01 ludacrisvps-mac-pro kernel0: ZDNet.de: Clock chip came back 7 bytes: FF N7 FF FF 0F 00 1E Sep 2 21:11:01 ludacrisvps-mac-pro kernel0: ZDNet.de: Clock chip family members ICS932S4xtimes discovered. Sep 2 21:11:01 ludacrisvps-mac-pro kernel0: ZDNet.para: Clock chip came back 22 bytes: FF F7 FF FF 0F 00 1E 11 16 2B 43 CD 3C At the9 2F Compact disc 3C Elizabeth9 2F 06 Deb8 00 Sep 2 21:11:01 ludacrisvps-mac-pro kernel0: ZDNet.para: Custom frequency development is restricted (We'll transformation that in a few nanoseconds).
Sep 2 21:11:01 ludacrisvps-mac-pro kernel0: ZDNet.para: Clock nick returned 22 bytes: FF Y7 FF FF 0F 00 1E 11 16 2B G3 Compact disc 3C Elizabeth9 2F CD 3C Y9 2F 06 D8 00 Sep 3 00:18:29 ludacrisvps-mac-pro kernel0: ZDNet.de: Clock nick came back 22 bytes: FF F7 FF FF 0F 00 1E 11 16 2B C3 Compact disc 4D Age9 2F CD 3C Age9 2F 06 N8 00 Sep 3 00:18:29 ludacrisvps-mac-pro kernel0: ZDNet.de: Clock nick household ICS932S4xx discovered. Sep 3 00:18:29 ludacrisvps-mac-pro kernel0: ZDNet.para: Custom made frequency development is allowed.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |