m.gbt

I've asked that here once and they told me the image is retail, i.e. there are no modifications to the system. It does help though all of us who didn't have a Mac to set the things up in order to having one... Anyway, the reason why I asked was that I couldn't boot with my own prepared version. First I tried the method of using a single command to put the Install OS X.app to the pendrive. Then I could boot to the installation "phase 1", but never to the "phase 2". Later I tried the other harder method where you have to go inside the app contents, pick up some files, restore an image to a pendrive... And then I couldn't boot at all (later I discovered that this manual part made the installation go directly to phase 2, as actually what the phase 1 does is exactly copying some files over). So... In the end, what was causing me errors was simply the Clover version. For some reason, in my particular laptop, Clover 2236 (the one installed in the 10.9 Olarila's image) works fine for booting from USB. More updated versions (I don't know since which one) can only boot from an internal HDD partition where I currently have the Mavericks install in case I want to reinstall. I just noticed that I was telling my adventures to another user just one post above here lol

I have... And what I can say is that there are many possible reasons for that. 1 - it could be a problem with your USB port. I tried all the USB ports so I thought that wasn't the problem. But a month before I could boot fine. I tried to remember all the steps I had done and finally came to the conclusion that the only difference was the Clover version. And indeed, I tested the older Clover I had used (2236) and then it worked. One detail: the device containing Clover should be the first boot device inside the BIOS advanced options. If I selected to boot that device from anywhere else, it didn't work. These things took me a whole day of work to discover so when I finally passed that screen, the first thing I did was to create an HDD partition for OS X installation and since then, I can use any Clover version to boot it from the HDD when I need to reinstall. 2 - it could be a problem with your USB device. Sometimes trying a different pendrive or external HDD solve the problem. 3 - Try to hit Spacebar over the install boot option in Clover, then select "boot without caches". See if it loads mach_kernel. Then after it lots of dots are going to appear, each dot represents one kext loaded. Here, it froze every single time at the same dot - later, I discovered that all kexts were being loaded and then the following step of the boot wasn't being executed because of the problems above related. But it might work for you. If you see what I said in number 3 (mach_kernel loads fine, and loading stops at the dots), then I suggest you to try this at first, because I strongly believe it will work: enter a Linux Live CD/USB and clone the OS X Install partition from the image you downloaded to an internal HDD partition (8GB is fine, formatted as HFS+). Then try to boot that instead of the one in the USB.

When your graphics card was being "recognized" as 64MB only, did your display work? If yes, try to boot the way you were doing before, and then run this in the terminal: ioreg -lw0 | grep IODisplayEDID If nothing appears, then you probably need EDID injection. What bootloader do you use? If Clover, you may try these instructions for injecting your EDID: http://Olarila.com/forum/viewtopic.php?f=31&t=3836&start=200#p38079

About performance I don't think so, at least I don't feel any difference. But a Clover developer told me it's better to install them to /S/L/E because the kexts injection may cause some bugs (people have already reported some, like not being able to shutdown or sleep [the computer] sometimes). Not a newbie question btw. Newbie questions are those you can find an answer for at Google's first page.

Searching for Mavericks Asrock Z87 on Google I found some successful cases, you may give them a try. Good luck!

Ninguém pode rodar o NovaBench no Mac e no Windows e comparar os resultados? Obrigado.

Você pode usar a key Hide Partition no org.chameleon.boot.plist http://www.macbreaker.com/2012/01/how-to-hide-hard-disks-on-chimera.html Também é interessante renomear essa partição do Windows com a key Rename Partition http://www.macbreaker.com/2012/02/rename-partitions-on-chameleon.html

Well you can't really compare RAM usage, they are different systems with different applications. In fact I upgraded my laptop from 4GB to 8GB because of Mavericks. About CPU Usage, that doesn't tell much either, for the same reasons. The battery might be a problem of power management, but as Mac seems to need more resources, it wouldn't surprise me that it drains more battery too. Now the temperature, that really should indicate a problem. After correctly setting up power management related stuff here, my Mac is actually running a lot cooler than Windows 8... The way to know if you are really experiencing power management issues during use is to check your CPU multiplier/frequency variation. You can try Intel Power Gadget to see the frequency, HWMonitor for multiplier and frequency, just to tell some easy solutions. Your clock speed is 2.5GHz so your base frequency is 1.25GHz, and your turbo frequency is 3.1GHz. That means you should get the frequency varying in steps of 0.1GHz from 1.25GHz up to 3.1GHz (that's why we call speed step). If you're only getting 1.25GHz or 2.5GHz, then your power management is not set up. By the way you forgot to add an M to your processor in your profile (i5-2450M). And your SMBIOS should be MacBookPro8,1, 8,3 would be for i7.

Thank you for reporting back and bringing us a solution! I tend to forget about the Clover drivers... Good to know! Let's keep the conversation in the topic you created: http://Olarila.com/forum/viewtopic.php?f=31&t=4293

Then your display is natively fully detected by Mac, that's why the Custom EDID doesn't make difference. You can take that out from your config.plist if you want to. The only possible solution I found for your problem with Intel HD 4600 was to try different values for IntelAzulFB in Chameleon. That doesn't exist in Clover so you can try different ig-platform-id. I don't know exactly how did you obtain the one you're currently using. Someone reported no more artifacts after setting IntelAzulFB to 12. I found this table, it relates IntelAzulFB values to (I believe) ig-platform-id values: See what happens if you try the id for 12. If that leads you to a black screen, probably the other ids are not the way to go (that might indicate I'm wrong to think the right values are ig-platform-id). If you can still reach the graphics but the artifacts persist, then you may try the other ones until you (hopefully) find one that solves your problem.

Boot with your current config.plist (with CustomEDID), then run in the terminal: ioreg -lw0 | grep EDID Save it in a text file. Then boot again, this time without injecting EDID (you don't need to modify config.plist for that, you can go into Clover options > Graphics > uncheck EDID injection), and repeat the process. Do you see any differences in the outputs? If not, can you post them here? This is just to certify that the EDID injection is working.

Qual o erro que ocorre ao tentar bootar com a SMBIOS?

Often, problems like that can be fixed in Clover by injecting your laptop display's EDID. It's a big code with a lot of meaning, it actually represents every detail about the operation of your display. Adapting from a guide I wrote elsewhere:

Já tentou UseKernelCache=No -f ? Acho interessante evitar qualquer cache depois de realizar modificações importantes, às vezes o sistema fica tentando carregar algum dado que não é mais válido, talvez seja o caso para o SMBios.

Se o shutdown funcionava sem DSDT, acredito que não precisa fazer patch de shutdown na DSDT. Já tentou sem?

Pessoal, alguém já buscou comparar a velocidade da memória RAM no Windows e no Mac? Eu testei com o Novabench. Antes eu usava apenas os 4GB 1333MHz stock do meu notebook, o resultado era em torno de 6000MB/s no Windows e 5100MB/s no Mac. Atualizei com um novo pente de 4GB 1600MHz (totalizando 8GB), no Windows o resultado foi impressionante, saltou para 7100MB/s. No Mac saltou para apenas 5800MB/s, coerente com os resultados anteriores (queda de +- 20% no desempenho) Gostaria de saber os resultados de vocês. Caso essa queda não seja normal, sei que devo buscar uma solução particular. Se for normal a queda, talvez seja de interesse de todos buscar igualar as velocidades... Obrigado, abraços!

Did you generate your SSDT using Pike's script? You can try first with DropOemSSDT (you're dropping all tables with this option), later we can optimise and drop only what is needed. If that's correct, check if your P-States are fine (maybe DPCIManager is the easiest way), you should have every state from 14 or 15 up to 36 (for your processor specifically). That will tell us your SSDT is good and loaded. Have you patched your DSDT? Take a look on the patches for Ivy Bridge here: http://Olarila.com/forum/patches.php The EHCI influences on sleep and is one of the very few patches I manually apply to my DSDT (most of them I apply with Clover) If all's correct, then you may try: http://clover-wiki.zetam.org/Configuration/ACPI#DropTables DSDT / SlpSmiAtWake DSDT / SuspendOverride Lastly... Attach here your Clover's config.plist if still not working.

artur, talvez nem a AppleHDA você precise trocar entre as builds, já verificaste esse método para utilização de uma dummy kext? http://pikeralpha.wordpress.com/2013/12/17/new-style-of-applehda-kext-patching/ Tenho aqui no meu sistema a AppleHDA vanilla junto com uma dummy criada de acordo com o método acima de apenas 16KB, que basta ser reinstalada num sistema atualizado. O patch necessário no binário da AppleHDA faço on-the-fly com o Clover. Caso sua ALC seja das 8xx, tem script pronto para criação da dummy kext: http://pikeralpha.wordpress.com/2014/01/19/new-style-of-applehda-kext-patching-take-iii/

Você pode abrir o arquivo /var/log/system.log e verificar as mensagens no momento do travamento. Quando travar, desligue o computador e deixe desligado por uns minutos para ficar bem claro, pelos horários, quando que travou. Essas mensagens podem ajudar a descobrir a causa. Seria importante também mencionar se ele trava em alguma atividade específica, ou se basta deixá-lo ligado por um tempo, sem fazer nada... Seu gerenciamento de energia já foi corrigido? Enfim, há muitas informações úteis que você pode trazer para cá.

Small update: Pike has changed ssdtPRGen.sh folder, command to download should now be: curl -o ssdtPRGen.sh https://raw.github.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh

Sim, toca ficha, vai de Mavericks mesmo Esclarecimento: nenhum laptop é 100% nativamente compatível com o Mac. Vai exigir algum trabalho até tudo funcionar como queres, mas o que interessa é que é possível. Em certos hardwares ninguém conseguiu progressos... Por exemplo, em várias placas WiFi, mas isto resolve-se facilmente. O crítico é o processador e o vídeo. Boa sorte!

Have you tried any of the existing guides on how to activate your graphics on older versions? It was never natively supported, but on older versions you can at least apply some patches to have it partially working. If you don't apply anything, unfortunately it won't work. Just google for Intel hd graphics 2000 Mac and choose your favorite guide. Good luck!

Claro, entendo, apenas uma ressalva a fazer é que, segundo um desenvolvedor do Clover, ele funcionará da mesma forma num sistema sem UEFI, e inclusive simula como se fosse UEFI. Eu imagino que a perda seja de desempenho, mas não de funcionalidade - de todo modo, ainda não posso garantir por mim mesmo, mas em breve vou tentar hackear uma máquina Legacy usando o Clover e poderei trazer novas conclusões Agora, de forma alguma o Clover foi mais "amigável", esta certamente não é uma das qualidades dele. O que aconteceu, na verdade, foi que nunca consegui entrar no Chameleon; a primeira vez que entrei num bootloader para instalar o Mac foi com o Clover, e por ali fiquei, estudando suas opções. Acabei notando ao longo do tempo o quanto isso foi bom para mim, pois vejo muitas pessoas solicitando algum suporte e eu não sei como ajudar se usam o Chameleon. Muitas vezes, precisam de um patch na DSDT, numa kext, no kernel, que eu nunca precisei fazer, apenas ativei alguma opção no Clover.

Esse erro parece quando falta algo que anule a AppleIntelCPUPowerManagement.kext, como o NullCPUPowerManagement.kext ou o Disabler.kext incluso no Clover da imagem. Com o Clover você não chegou a tentar? Caso esteja usando o Clover, pode entrar nas opções, e em Binaries Patching testar o Lapic, o AppleRTC e o AICPUPM... Embora, que eu saiba, isso só seria necessário caso rodando sem a Null ou a Disabler.

Olá, se a sua placa-mãe for esta do seu perfil, os patches para ela já estão prontos, basta baixar o txt associado a ela em http://Olarila.com/forum/packs.php