Jump to content

Search the Community: Showing results for tags 'CPU'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 13 results

  1. Trying to install on a Lenovo A740 Dualbooting macOS Sierra / Windows 10. Stuck on installing macOS Sierra. Once choosing the USB Boot able Disk, Showign up the Appel Logo getting following message: panic(cpu 0 caller 0xffffff801a6d6db4): "Unable to find driver for this Platform: \"ACPI"\".\n"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.70.16/iokit/Kernel/IOplatformExpert.ccp:1672 Debugger called: (panic) Backtrace (CPU 0), Frame : Retunr Address HEX-Nubers... BSD Process name corresponding to current thread: Unkow Boot Args: dart=0 nv_disable=1 Mac OS Version: not yet set Kernel Versino: Darwin Kernel Version 16.7.0: ... ... System uptime in nanoseconds: 767758761 What I already Tried: Boot Args: acpi=off Checkboxing/DeCheckbosing ACPI Patches... ready tons of Forums and Article about this issue... Until now nothing worked. Anyone has an Idea to solve this problem? Thanks in advance for your Preciouse time! System Spec: Intel Core i7-5557U Processor (4M Cache, 3.1GHz), Turbo Boost 2.0 (3.4GHz) 8GB, PC3-12800 1600MHza7 DDR31, 2 x 204-pin SODIMM sockets, 8GB Intel Iris 6100 in processor and NVIDIA GeForce® GTX 950A, 2GB memory 27" Quad HD (2560x1440), frameless, 300 nits, 16:9 aspect ratio, 1000:1 contrast ratio, wide viewing angle (from -5 to 90°) multi-touch 1 x USB 3.0 Power connector Ethernet (RJ45) Audio combo jack HDMI-in, HDMI-out 2 x mini PCIe 3 x USB 3.0 Media card reader HDMI connector
  2. Hello, I am attempting to setup a Virtual Machine for Mac Os Sierra and I am having some trouble setting up the operating system to boot on VMware. I had already tried CPU masking which made the kernel panic on the picture and without says the CPU is Disable by the Guest Operating System. I had tried researching this problem but everything dates back to Snow Leopard or it does not work for me. Specs: Intel Q6600 4 Gbs Ram P5G41T-M LX PLUS Motherboard GTX 1050 Ti Vmx file:
  3. Olá Pessoal GUIA ATUALIZADO - Foi adicionado patch XCPM para 10.10 Antes de tudo é muito bom que tenhamos uma versão atualizada do Chameleon, então por favor pegue essa versão mais atualizada bem aqui no tópico oficial: http://www.insanelymac.com/forum/files/download/59-chameleon-22-svn/ Desde 10.7.4 para os CPUs SandyBridger e IvyBridger os P e C States - que são responsáveis pelo bom funcionamento de energia - não são mais fornecidos pelo Chameleon, ou seja, somente ativar GeneratePStates e GenerateCStates não adiatam mais... Uma saída rápida é a utilização da kext NullCPUPowermanagement, mas eu não recomendo a utilização continua dessa kext, pois ela desabilita a kext AppleIntelCPUPowermanagement que é pelo gerenciamento de energia. A solução mais viável e recomendada que lhe proporcionará um gerenciamento de energia bom, é a criação de uma SSDT que irá contem todos os P-States e C-States. Passo-a-Passo Criando a SSDT Crie sua SSDT baseada no script do Pike R. Alpha Rode no terminal esses comandos curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh chmod +x ssdtPRGen.sh ./ssdtPRGen.sh Após roda-lo você precisa colocar a Frequência Máxima e o Máximo TDP do seu CPU... veja essas infos sobre seu CPU aqui: http://ark.intel.com/ Esse é um exemplo de um i7 2600 que possui 3800Mhz(3,8Ghz) de frequencia maxima e 95 de TDP sudo ./ssdtPRGen.sh 3800 95 Coloque a SSDT na pasta Extra e renomeie ssdt_pr para SSDT Obs: Alguns CPUs já são auto-detectados pelo script, simplesmente o script já detecta a frequência máxima e o TDP, então se simplesmente após rodar o primeiro comando você for avisado para salvar a SSDT na pasta Extra(não pedindo para digitar sua max frequenc. e TDP como o guia manda), não se preocupe com isso, apenas confirme, pois o script já detectou tudo e criou sua SSDT e no momento já está pedindo para salvar o arquivo. Patch na AppleIntelCPUPowermanagement Nas mobos mais antigas é necessário patchear a kext AICPUPM para possibilitar a gravação na Bios, caso contrário você receberá um Kernel Panic por não poder gravar na Bios... Faça o download do patch:AICPUPMpatch Rode no terminal cd ~/Downloads/AICPMPatch Apenas encontre e liste... sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement Depois dê patch no wrmsr para possibilitar a gravação na Bios sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement --patch Após isso é necessário atualizar o cache sudo touch /System/Library/Extensions Kernel Patch para Haswell CPU(Kernel XCPM) Desde a versão 10.8.5 um novo kernel foi implementado no OSX, ele se chamada XNU kernel(Xnu Cpu Power Management(xcpm)) Esse kernel tem o gerenciamento de energia movido para dentro dele, no passado usávamos a kext AppleIntelCPUPowermanagement para o controle do gerenciamento de energia e algumas Bios eram travadas, ou seja, não era permitido gravar informações nela, por isso foi criado o patch para a kext AICPUPM para solucionar esse problema(veja acima como patchear a kext AICPUPM Mas com o gerenciamento movido para dentro do kernel(XNU kernel)a kext AICPUPM não é mais carregada e por isso o mesmo erro que estávamos tendo no passado com a kext AICPUPM(Kernel Panic)estamos tendo agora com o XNU kernel em alguns modelos de CPU haswell(principalmente modelos portáteis, alguns modelos Desktop não precisam de patch) Para solucionar esse problema é necessário aplicar um patch no kernel. Para 10.10 você precisa abrir o terminal e digitar: cd /Volumes/Nome do seu HDD/System/Library/Kernels/ Note que em 10.10 o diretório do kernel foi alterado. Copie esse código perl, isso é para a versão 10.10, coloque linha por linha sudo perl -pi -e 's|\xe2\x00\x00\x00\x02\x00\x00\x00|\x00\x00\x00\x00\x02\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x4c\x00\x00\x00|\x00\x00\x00\x00\x4c\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x90\x01\x00\x00|\x00\x00\x00\x00\x90\x01\x00\x00|g' kernel Para 10.9.x e 10.8.5 você precisa rodar esse comando no terminal: cd /Volumes/Nome do seu HDD/ Agora, copie esse código perl se você usa as versão 10.9.x sudo perl -pi -e 's|\x74\x6c(\x48\x83\xc7\x28\x90\x8b\x05..\x5e\x00\x85\x47\xdc)\x74\x54(\x8b\x4f\xd8\x45\x85\xc0\x74\x08\x44\x39\xc1\x44\x89\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x99(\x5d\xc3)\x90{7}|\x74\x73${1}\x74\x5b${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x92${5}|g' mach_kernel ou esse outro código perl se você usa a versão 10.8.5 sudo perl -pi -e 's|\x74\x69(\x48\x83\xc7\x28\x90\x8b\x05\xfe\xce\x5f\x00\x85\x47\xdc)\x74\x51(\x8b\x4f\xd8\x45\x85\xc0\x74\x05\x44\x39\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x9c(\x5d\xc3)\x90{7}(\x90{3})|\x74\x70${1}\x74\x58${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x95${5}${6}|g' mach_kernel Por último atualize o cache sudo touch /System/Library/Extensions Pronto! Kernel patcheado e o XCPM está trabalhando perfeitamente em seu CPU haswell OBS1: XCPM só trabalha nos CPUs Ivy Bridger e Haswell, sendo que, os CPUs Ivy Bridger utilizam por padrão o gerenciamento de energia dado pela kext AICPUPM, para usar o gerenciamento de energia dado pelo kernel XCPM é necessário ativar essa flag(Chameleon)/argumento(Clover): -xcpm Os CPUs Haswell utilizam o gerenciamento XCPM por padrão e não mudam. O gerenciamento XCPM não suporta os CPUs Sandy Bridger, então quem usa SB pode ficar tranquilo acerca disso. OBS2: Mesmo patcheando o kernel XCPM, você irá precisar patchear a kext AICPUPM, caso a sua BIOS seja trancada para gravação. OBS3: Caso você não tenha nenhum problema com KP, não é necessário patchear o kernel, mas, em alguns casos, patchear o kernel ajudou em adicionar alguns states de energia. OBS4: O Clover bootloader já tem o patch embutido, você só precisa editar o config.plist para habilitar o patch <key>KernelAndKextPatches</key> <dict> <key>KernelPm</key> <true/> </dict> Então, se você habilitar isso no Clover não é necessario patchear o kernel, porque o Clover irá fazer isso para você Ajustes finais Para fazer com que o Chameleon reconheça a sua SSDT, habilite DropSSDT no org.chameleon <key>DropSSDT</key> <string>Yes</string> Não instale a NullCPUPM e não habilite P e C States no org.chameleon... Não se esqueçam de futuramente criar uma DSDT para auxiliar no gerenciamento de energia OBS: Para quem está com dificuldades com gerenciamento de energia... dê uma olhada para ver se as kexts: X86PlatformPlugin, ACPI_SMC_PlatformPlugin, AppleLPC estão carregadas, rode kextstat no terminal para ver... Boa sorte para todos que tentarem este guia, eu somente juntei tudo em um único tutorial para facilitar a compreensão sobre gerenciamento de energia em Sandy e Ivy Bridger, mas todos os créditos vão para os respectivos donos das ferramentas maravilhosas que possibilitam o gerenciamento de energia em nossas CPUs Créditos: Pike R. Alpha flAked RevoGirl ReHabMan: http://www.insanelymac.com/forum/topic/302376-guide-patching-the-kernel-for-haswell-cpus-xcpm-early-reboot/
  4. Greetings all, i just finished my installation of OS X Mountain Lion 10.8.4 using this fantastic guide. Had a couple of hick ups forcing me to do most part in Safe Mode (-x), but I managed to boot from the HD onto the desktop. Eventually got my Realtek card set up and went on like a fool to download the latest graphics card drivers. I installed the drivers by running the package (can´t remember the exact name - it was something along the lines of macbookpro bla bla .pkg), which I know realize was insanely stupid. Before this (having removed most .kext files related to drivers) I could boot into desktop using -v dart=0. Now however, I can't get into the desktop at all, having tried various combinations of commands. All I keep getting now is the following: https://www.dropbox.com/s/owdx1efkviojneb/2013-07-02%2000.16.14.jpg 1) How do I solve this? I'm guessing I have to remove the drivers from the system by using the terminal in the OS X installer (via USB) 2) How would I go on about installing my drivers properly? System specifications Intel Core i7-3770 Kingston DDR3 HyperXblu 1600Mhz 16GB MSI Z77A-G43 Asus GeForce 680GT
  5. I got a couple of used XServes for super cheap on eBay. I am going to use one as a VMWare Server for remote employees. The other will be a simple file server since I can do both SMB and AFP as opposed to our Win SBS 2011 server which can only do SMB. The one that will be for virtual machines I felt that I would need a little more power to handle the out of office employees. I bought a pair of Xeon e5345 CPUs for $40.00 on eBay and they certainly did the trick. Here are the before and after Geekbench results Before - http://browser.primatelabs.com/geekbench2/1814845 After - http://browser.primatelabs.com/geekbench2/1533559 Quite an improvement in my opinion. Went from four total cores to eight. As temps go; idle temps are around 35-42c. I also used Arctic Silver 5. OSX System Profiler does not recognize the CPU name. It gets the number of cores and speed right but it lists "Unknown" as the name. However, Geekbench and the virtual machines both see the CPU speed and name correctly. For $40 this was a great upgrade.
  6. RandomMixTape

    CoolBook

    Does CoolBook fix issues with Intel Speedstep such as CPU downscaling?
  7. Hello folks! GUIDE UPDATED - Added support for 10.10 XCPM kernel First of all it is very good that we have an updated version of Chameleon, so please take this most updated version right here in the official thread: http://www.insanelym...ameleon-22-svn/ Since 10.7.4 for CPUs and SandyBridger IvyBridger P and C States - that are responsible for the proper functioning of energy - are no longer provided by Chameleon, in others words, only activate GeneratePStates and GenerateCStates doesn't work any more. A quick exit is to use the kext NullCPUPowermanagement, but I don't recommend continued use of this kext because it disables AppleIntelCPUPowermanagement kext which is responsible for power management The most viable and recommended solution that will give to you a good power management is the creation of a SSDT which will contain all P-States and C-States. Step-by-Step Creating the SSDT Create your SSDT based on the script Pike R. Alpha Run these commands in terminal curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh chmod +x ssdtPRGen.sh ./ssdtPRGen.sh After you run it you need to put the Maximum Frequency and Maximum TDP of your CPU ... see these information about your CPU in here: http://ark.intel.com/ This is an example of one i7 2600 that has 3800MHz(3.8 Ghz) of maximum frequency and 95 of TDP sudo ./ssdtPRGen.sh 3800 95 Place the SSDT in Extra folder and rename ssdt_pr for SSDT Note: Some CPUs are auto-detected by the script, the script just now detects the maximum frequency and TDP, so if simply after running the first command you are prompted to save the SSDT in Extra folder(not asking to enter your max frequenc. and TDP as the guide teach),don't worry about it, just to confirm, because the script already detected everything and created the SSDT and the time is already asking to save the file. Patch AppleIntelCPUPowermanagement In older mobos is necessary to patch the kext AICPUPM to enable recording in Bios, otherwise you will get a kernel panic because it can't write to the Bios ... Download the patch: AICPUPMpatch Run in terminal cd ~/Downloads/AICPMPatch Just find and list ... sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement Then give patch in wrmsr to enable recording in Bios sudo perl AICPMPatch.pl /System/Library/Extensions/AppleIntelCPUPowerManagement.kext/Contents/MacOS/AppleIntelCPUPowerManagement --patch After that you need to update the cache sudo touch /System/Library/Extensions Kernel Patch for Haswell CPU(Kernel XCPM) Since version 10.8.5 a new kernel was implemented on OSX, he called XNU kernel(XNU CPU Power Management(xcpm)). This kernel has the power management moved down into it, in past we used AppleIntelCPUPowermanagement kext to control power management and some Bios were lockeds, in others words, were not allowed to write information on it, so the patch was created for kext AICPUPM to solve this problem (see above how to patch the kext AICPUPM). But with the power management moved down into the kernel(XNU kernel) AICPUPM the kext isn't loaded and so the same mistake that we were having in the past with AICPUPM kext(Kernel Panic)are having now with the XNU kernel in some models CPU haswell(mainly in portable models, some Desktop models doesn't need patch) To solve this problem it is necessary to patch the kernel. For 10.10 you need Open the terminal and type: cd /Volumes/Name of your HDD/System/Library/Kernels/ Note that in 10.10 kernel directory was changed. Copy this perl code is for 10.10 version, put line by line sudo perl -pi -e 's|\xe2\x00\x00\x00\x02\x00\x00\x00|\x00\x00\x00\x00\x02\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x4c\x00\x00\x00|\x00\x00\x00\x00\x4c\x00\x00\x00|g' kernel sudo perl -pi -e 's|\xe2\x00\x00\x00\x90\x01\x00\x00|\x00\x00\x00\x00\x90\x01\x00\x00|g' kernel For 10.9.x and 10.8.5 you need run this command in terminal: cd /Volumes/Name of your HDD/ Now copy this perl code if you use version 10.9.x sudo perl -pi -e 's|\x74\x6c(\x48\x83\xc7\x28\x90\x8b\x05..\x5e\x00\x85\x47\xdc)\x74\x54(\x8b\x4f\xd8\x45\x85\xc0\x74\x08\x44\x39\xc1\x44\x89\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x99(\x5d\xc3)\x90{7}|\x74\x73${1}\x74\x5b${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x92${5}|g' mach_kernel or that other perl code if you use version 10.8.5 sudo perl -pi -e 's|\x74\x69(\x48\x83\xc7\x28\x90\x8b\x05\xfe\xce\x5f\x00\x85\x47\xdc)\x74\x51(\x8b\x4f\xd8\x45\x85\xc0\x74\x05\x44\x39\xc1)\x75\x44(\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x57\xf8\x48\x8b\x47\xe8\x48\x85\xc0\x74\x06\x48\xf7\xd0\x48\x21\xc2\x48\x0b\x57\xf0\x49\x89\xd1\x49\xc1\xe9\x20\x89\xd0\x8b\x4f\xd8\x4c\x89\xca)(\x0f\x30\x8b\x4f\xd8\x0f\x32\x89\xc0\x48\xc1\xe2\x20\x48\x09\xc2\x48\x89\x17\x48\x83\xc7\x30\xff\xce)\x75\x9c(\x5d\xc3)\x90{7}(\x90{3})|\x74\x70${1}\x74\x58${2}\x75\x4b${3}\x66\x81\xf9\xe2\x00\x74\x02${4}\x75\x95${5}${6}|g' mach_kernel Finally update the cache sudo touch /System/Library/Extensions Ready! XCPM patched kernel and is working perfectly on your CPU haswell Note1: XCPM only works in Ivy Bridge and Haswell CPUs, and the CPUs Ivy Bridger use by default the power management given by AICPUPM kext, to use the power management provided by the kernel XCPM you must enable this flag(Chameleon)/argument(Clover): -xcpm Haswell CPUs use XCPM management by default and doesn't change.The management XCPM not support CPUs Sandy Bridger, so who uses SB can stay quiet about it. Note2: Even Patching the kernel XCPM, you will need to patch the kext AICPUPM if your BIOS is locked for writing. Note3: If you have no problem with KP, it isn't necessary to patch the kernel, but in some cases, helped to patch the kernel to add some energy states. Note4: Clover bootloader already has this patched built-in, you just need edit config.plist to enableir it <key>KernelAndKextPatches</key> <dict> <key>KernelPm</key> <true/> </dict> So, if you enable it in Clover isn't necessary patch kernel, because Clover will make this for you Final adjustments To make the Chameleon recognize your SSDT, enable DropSSDT in org.chameleon <key>DropSSDT</key> <string>Yes</string> Don't install the NullCPUPM and don't enable P and C States in org.chameleon ... Don't forget to create a DSDT in future to help the power management Note: For those who are having difficulty with power management ... take a look to see if the kexts: X86PlatformPlugin, ACPI_SMC_PlatformPlugin, AppleLPC are loaded, type kextstat the terminal to see ... Good luck to all who try this guide, I just put it all together in a single tutorial to facilitate the understanding of power management in Sandy and Ivy Bridger, but all credits go to the respective owners of the wonderful tools that enable power management in our CPUs Credit: Pike R. Alpha flaked RevoGirl ReHabMan: http://www.insanelymac.com/forum/topic/302376-guide-patching-the-kernel-for-haswell-cpus-xcpm-early-reboot/
  8. Hello, i have a Lenovo Y410p Hackintoshed with Yosemite 10.10.2 using Clover, already followed the native power management guide; i've been using it a while, but i felt the cpu too hot, these are the temps: CPU: Core 1 - 83 ºC Core 2 - 84 ºC Core 3 - 78 ºC Core 4 - 76 ºC CPU Package 85 ºC --------------------- CPU Package Frecuency 3.07 GHz! -- I don't understand why!, my cpu basic frecuency is 2.4, turbo is 3.4, but... i never overclocked it! CPU Package Average 3.01 GHz! --------------------- CPU MONITOR --------------------- RAM MONITOR Is it right that osx uses almost all the ram?
  9. Hi, I'm successfully running (Niresh) Mavericks 10.9.4 in a VirtualBox VM on a Windows 8.1 host. Most things work there, so I decided to download and try to install the latest Yosemite Public Beta 2 (20 August,2014). Running the Yosemite Installer App, results in what seem successful update, but when the installer finishes and reboots, I get a crash. Shutting down the VM in the regular way and rebooting you'd think it would try to reboot in the same way, but no, instead it boot right back up into Mavericks. WTF!? I'm new to everything that is Apple so I'm really at loss here. So I tried a second method. I took the Yosemite PB2 App and made both an ISO and an DMG using detailed instructions from this site and others. I.e. Using sparse methods etc. Now I mounted either of these images as an external CD/DVD from virtual box and they appear and run in Mavericks. However, this time, when I try to run the installer I get this picture. Any ideas what's going on, and why I can run this from withing Mavericks as an installer App, but not as a ISO/DMG image? Is there a way to circumvent this?
  10. Desde a primeira geração do CPUs Intel (Nehalem) e até a linha Haswell, temos a função Turbo Boost. Nada mais é do que um "Overclock" automático, que só será usado quando determinada tarefa exija mais do CPU, como renderização de imagens e videos. Mas quando estamos usando somente a bateria, esse processo pode consumir rapidamente a energia, e obrigando o user a correr para a tomada mais próxima. Trago uma solução para isso, que é uma kext chamada DisableTurboBoostBattery, ela desabilita o Turbo Boost quando o Laptop está usando somente a bateria, mas quando estiver carregando a bateria, o sistema automaticamente detecta que o Laptop está conectado em uma fonte (tomada), e dai seu Turbo Boost voltará a funcionar. Mas isso é arriscado? Não, dependendo do que vai fazer claro.Pela logica, quando estiver com essa kext instalada, não espere todo o desempenho do CPU quando estiver renderizando algo, e o mesmo estiver com a bateria. Esse método é apenas para salvar você para não depender de alguma tomada. Por isso, se for fazer algo que exija do seu CPU, esteja conectado a uma tomada mais próxima. Informações adicionais. Quando estiver com essa kext e somente fazendo uso da bateria, seu CPU vai ficar com o clock normal. Ex: Uso o CPU i5 3210M, o clock dele normal é 2.5GHz, e maximo 3.10GHz. Então, quando estou usando a bateria, o maximo é 2.5GHz, mas quando volto pra tomada, dai sim tenho meu Turbo Boost - 3.10GHz. Download da kext: DisableTurboBoostBattery.kext.zip Como verificar o clock do meu Hack? Baixe o app oficial da Intel, o Intel® Power Gadget. Com ele você pode verificar a frequência do seu CPU, temperatura e uso da energia. Nota: Esse app só funciona para CPUs Intel SandyBridge e mais avançados, para a primeira geração, pode usar o HWSensors. Download do app: Intel® Power Gadget Veja mais aqui: Turbo Boost 2.0
  11. So I recently made a bootable USB with OS X El Capitan 10.11.5 on it. I didn't change anything on the USB. I just formatted it under Disk Utilities, made a bootable USB with [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] and that's it. I put the USB in one of my USB-ports of the PC and I boot directly from the USB in UEFI-Bootmode. Coming in the Bootmenu I choose the USB to boot from. The Apple logo comes for like 4-5 seconds. After that the following message pops up at the upper display: "panic(cpu 0 caller 0xffffff8004d1caa6): „zone_init: kmem_suballoc failed“«Library Caches com.apple.xbx Sources xnu xnu3248". Just some miliseconds later it reboots. I changed almost everything. I booted with "nv_disable=1" "-x" "-v"... Here's a video how it looks like. I recorded it so yeah... My Specs: CPU: Intel i5-4460 @ 3.20 GHz GPU: NVIDIA GeForce GTX 750 RAM: 1x8GB DDR3 Motherboard: Medion H81H3-EM2 (I know. Self-build PC is better...) In the BIOS i just turned off Intel Virtualization Technology and choose UEFI-bootmode. That's it...
  12. leonvmetcalf

    Kernel Panic in Safe Mode

    Hey guys! I somehow received this kernel panic upon boot. It happened after I removed NullCPUPowerManagement because I wanted to enable Native CPU power management. I was using a .aml file and it was in the /Extra folder. Unfortunately, I cannot even boot into safe mode to delete the file and put the NullCPUPowerManagement.kext file back. I get this kernel panic. Any ideas? Thanks. Larger Image:
  13. Hello all, I've been gone for awhile and am wondering with the holidays coming up should I upgrade my badass Hackintosh entirely, or should I just upgrade a couple of things? Some of my specs are in my signature. I need more Hard Drive space and currently I have a option to upgrade my storage by either getting a card to expand my IDE capacity or taking one of my two DVD drives out. What I have in the Signature is actually my backup HD. The ones I have Inside are 160GB, 120GB, and 2 TB. I have slow 667mhz memory in here. Would it tremendously help if i upgraded to the O.C. which is 1066 or higher to 1366? I need to be able to keep Snow Leopard functionality because of older games I refuse to let go just to go to lion or mountain lion. I also want to make sure video games like WoW or Starcraft which are the ones I usually play will not make my system a minimum specs for awhile. I'm going through college and I don't have allot of money to spend on other things besides school so any help that is not tough on my wallet would be great. If anyone can say if my board and graphics card is supported in mountain lion and lion that'd be great!
×