- Joined
- Feb 15, 2012
- Messages
- 84
- Mac
- Mobile Phone
Hi, was hoping someone could help me… I currently have a (pretty much) working setup using Clover v. 1974. Before upgrading the machine to Mavericks though, I wanted to make sure I was using the latest of everything; the central component being Clover. Problem is, that even after "translating" the config to the new syntax of newer Clover versions, I can't get the system to boot. It works as long as I use my native SSDT tables, but once I drop in an ssdtPRGen-generated file, or let Clover generate C- and P-states, the OS won't start. I've gathered as much information as I can, but I'm afraid I don't know enough about hardware to figure out where things go wrong, so I could really use some pointers as to what I should try next.
My current setup:
Now, when I use a new version of Clover, it all kind of breaks down. Using the exact same DSDT and SSDT files, OS X gets stuck in the boot process. I'm not getting any explicit error messages, and it all looks fine when booting in verbose mode – it just kind of stops. So my guess is the window server can't be launched for some reason…? The behavior is exactly the same whether I'm booting the current 10.8.4 install, or the Mavericks installer.
This is what works/doesn't work, using Clover 2428:
So basically, everything works, until C and P states are specified manually somehow. Does anyone know what might be wrong here? Seems so weird to me that it should stop working with a newer version of Clover… I'm attaching some files that may or may not be of use (DSDT/SSDT files, ssdtPRGen output, Clover config, IOJones files for old/new setup, etc). Please let me know if there is any other information that might be useful.
My current setup:
- Asus P8Z77-M Pro
- Intel i5-3570k (slightly overclocked using Asus' auto-tuning utility, chugging along perfectly ever since I built the machine)
- NVIDIA GTX780
- BIOS patched using DPCIManager
- Fresh DSDT patched with PJALM's patches using MacIASL
- SSDT generated by ssdtPRGen (using the target clock of 4200 to match my overclock)
- Clover 1974
- SMBios settings for MacBookPro10,1
- OS X 10.8.4
Now, when I use a new version of Clover, it all kind of breaks down. Using the exact same DSDT and SSDT files, OS X gets stuck in the boot process. I'm not getting any explicit error messages, and it all looks fine when booting in verbose mode – it just kind of stops. So my guess is the window server can't be launched for some reason…? The behavior is exactly the same whether I'm booting the current 10.8.4 install, or the Mavericks installer.
This is what works/doesn't work, using Clover 2428:
- Works: Boot using only DSDT, either dropping or not dropping any native SSDT tables
- Works: Save the native tables as files, put those in the ACPI/patched folder for clover, and boot using those
- Doesn't work: Boot using DSDT and ssdtPRGen-generated SSDT file, either dropping or not dropping any native SSDT tables
- Doesn't work: Boot using DSDT and have Clover generate C and P States
So basically, everything works, until C and P states are specified manually somehow. Does anyone know what might be wrong here? Seems so weird to me that it should stop working with a newer version of Clover… I'm attaching some files that may or may not be of use (DSDT/SSDT files, ssdtPRGen output, Clover config, IOJones files for old/new setup, etc). Please let me know if there is any other information that might be useful.