Bruxo Posted December 31, 2013 Share Posted December 31, 2013 As I said I am not on 10.9.2 yet. This _might_ be the source of my problems, at least parts of them. So maybe it's best to wait for 10.9.2 to be released. Did you see anything interesting in terms of USB? And I have latest BIOS 4701 But here is the output of ssdtPRGen.sh anyway: /* * Intel ACPI Component Architecture * AML Disassembler version 20100331 * * Disassembly of iASLo3ts1Y.aml, Tue Dec 31 21:36:37 2013 * * * Original Table Header: * Signature "SSDT" * Length 0x0000091F (2335) * Revision 0x01 * Checksum 0x8D * OEM ID "APPLE " * OEM Table ID "CpuPm" * OEM Revision 0x00007500 (29952) * Compiler ID "INTL" * Compiler Version 0x20130117 (538116375) */ DefinitionBlock ("iASLo3ts1Y.aml", "SSDT", 1, "APPLE ", "CpuPm", 0x00007500) { External (\_SB_.C00B, DeviceObj) External (\_SB_.C00A, DeviceObj) External (\_SB_.C009, DeviceObj) External (\_SB_.C008, DeviceObj) External (\_SB_.C007, DeviceObj) External (\_SB_.C006, DeviceObj) External (\_SB_.C005, DeviceObj) External (\_SB_.C004, DeviceObj) External (\_SB_.C003, DeviceObj) External (\_SB_.C002, DeviceObj) External (\_SB_.C001, DeviceObj) External (\_SB_.C000, DeviceObj) Scope (\_SB.C000) { Method (_INI, 0, NotSerialized) { Store ("ssdtPRGen version: 7.5 / Mac OS X 10.9 (13A603)", Debug) Store ("baseFrequency : 800", Debug) Store ("frequency : 3400", Debug) Store ("busFrequency : 100", Debug) Store ("logicalCPUs : 12", Debug) Store ("tdp : 130", Debug) Store ("packageLength : 32", Debug) Store ("turboStates : 5", Debug) Store ("maxTurboFrequency: 3900", Debug) Store ("machdep.xcpm.mode: 0", Debug) } Name (APLF, Zero) Name (APSN, 0x05) Name (APSS, Package (0x20) { Package (0x06) { 0x0F3C, 0x0001FBD0, 0x0A, 0x0A, 0x2700, 0x2700 }, Package (0x06) { 0x0ED8, 0x0001FBD0, 0x0A, 0x0A, 0x2600, 0x2600 }, Package (0x06) { 0x0E74, 0x0001FBD0, 0x0A, 0x0A, 0x2500, 0x2500 }, Package (0x06) { 0x0E10, 0x0001FBD0, 0x0A, 0x0A, 0x2400, 0x2400 }, Package (0x06) { 0x0DAC, 0x0001FBD0, 0x0A, 0x0A, 0x2300, 0x2300 }, Package (0x06) { 0x0D48, 0x0001FBD0, 0x0A, 0x0A, 0x2200, 0x2200 }, Package (0x06) { 0x0CE4, 0x0001E74A, 0x0A, 0x0A, 0x2100, 0x2100 }, Package (0x06) { 0x0C80, 0x0001D323, 0x0A, 0x0A, 0x2000, 0x2000 }, Package (0x06) { 0x0C1C, 0x0001BF5A, 0x0A, 0x0A, 0x1F00, 0x1F00 }, Package (0x06) { 0x0BB8, 0x0001ABEE, 0x0A, 0x0A, 0x1E00, 0x1E00 }, Package (0x06) { 0x0B54, 0x000198DF, 0x0A, 0x0A, 0x1D00, 0x1D00 }, Package (0x06) { 0x0AF0, 0x0001862B, 0x0A, 0x0A, 0x1C00, 0x1C00 }, Package (0x06) { 0x0A8C, 0x000173D2, 0x0A, 0x0A, 0x1B00, 0x1B00 }, Package (0x06) { 0x0A28, 0x000161D3, 0x0A, 0x0A, 0x1A00, 0x1A00 }, Package (0x06) { 0x09C4, 0x0001502D, 0x0A, 0x0A, 0x1900, 0x1900 }, Package (0x06) { 0x0960, 0x00013EE0, 0x0A, 0x0A, 0x1800, 0x1800 }, Package (0x06) { 0x08FC, 0x00012DEB, 0x0A, 0x0A, 0x1700, 0x1700 }, Package (0x06) { 0x0898, 0x00011D4D, 0x0A, 0x0A, 0x1600, 0x1600 }, Package (0x06) { 0x0834, 0x00010D06, 0x0A, 0x0A, 0x1500, 0x1500 }, Package (0x06) { 0x07D0, 0xFD14, 0x0A, 0x0A, 0x1400, 0x1400 }, Package (0x06) { 0x076C, 0xED77, 0x0A, 0x0A, 0x1300, 0x1300 }, Package (0x06) { 0x0708, 0xDE2E, 0x0A, 0x0A, 0x1200, 0x1200 }, Package (0x06) { 0x06A4, 0xCF39, 0x0A, 0x0A, 0x1100, 0x1100 }, Package (0x06) { 0x0640, 0xC096, 0x0A, 0x0A, 0x1000, 0x1000 }, Package (0x06) { 0x05DC, 0xB246, 0x0A, 0x0A, 0x0F00, 0x0F00 }, Package (0x06) { 0x0578, 0xA446, 0x0A, 0x0A, 0x0E00, 0x0E00 }, Package (0x06) { 0x0514, 0x9697, 0x0A, 0x0A, 0x0D00, 0x0D00 }, Package (0x06) { 0x04B0, 0x8938, 0x0A, 0x0A, 0x0C00, 0x0C00 }, Package (0x06) { 0x044C, 0x7C28, 0x0A, 0x0A, 0x0B00, 0x0B00 }, Package (0x06) { 0x03E8, 0x6F66, 0x0A, 0x0A, 0x0A00, 0x0A00 }, Package (0x06) { 0x0384, 0x62F1, 0x0A, 0x0A, 0x0900, 0x0900 }, Package (0x06) { 0x0320, 0x56CA, 0x0A, 0x0A, 0x0800, 0x0800 } }) Method (ACST, 0, NotSerialized) { Store ("Method C000.ACST Called", Debug) Store ("C000 C-States : 13", Debug) Return (Package (0x05) { One, 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, Zero, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x03, // Access Size ) }, 0x03, 0xCD, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000020, // Address 0x03, // Access Size ) }, 0x06, 0xF5, 0x015E } }) } Method (_DSM, 4, NotSerialized) { Store ("Method C000._DSM Called", Debug) If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "plugin-type", One }) } } Scope (\_SB.C001) { Method (APSS, 0, NotSerialized) { Store ("Method C001.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Store ("Method C001.ACST Called", Debug) Store ("C001 C-States : 7", Debug) Return (Package (0x05) { One, 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x03E8, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x03, // Access Size ) }, 0x02, 0x94, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000030, // Address 0x03, // Access Size ) }, 0x03, 0xC6, 0xC8 } }) } } Scope (\_SB.C002) { Method (APSS, 0, NotSerialized) { Store ("Method C002.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } Scope (\_SB.C003) { Method (APSS, 0, NotSerialized) { Store ("Method C003.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } Scope (\_SB.C004) { Method (APSS, 0, NotSerialized) { Store ("Method C004.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } Scope (\_SB.C005) { Method (APSS, 0, NotSerialized) { Store ("Method C005.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } Scope (\_SB.C006) { Method (APSS, 0, NotSerialized) { Store ("Method C006.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } Scope (\_SB.C007) { Method (APSS, 0, NotSerialized) { Store ("Method C007.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } Scope (\_SB.C008) { Method (APSS, 0, NotSerialized) { Store ("Method C008.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } Scope (\_SB.C009) { Method (APSS, 0, NotSerialized) { Store ("Method C009.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } Scope (\_SB.C00A) { Method (APSS, 0, NotSerialized) { Store ("Method C00A.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } Scope (\_SB.C00B) { Method (APSS, 0, NotSerialized) { Store ("Method C00B.APSS Called", Debug) Return (\_SB.C000.APSS) } Method (ACST, 0, NotSerialized) { Return (\_SB.C001.ACST ()) } } } Perfect! You should use this DSDT and SSDT Using SMBIOS the iMac13, 2 I put config.plist to clover! Use the latest kernel version 10.9.1 update Enjoy! Post a IOREG after changes! ACPI.zip Link to comment Share on other sites More sharing options...
frankiee Posted December 31, 2013 Share Posted December 31, 2013 Perfect! You should use this DSDT and SSDT Using SMBIOS the iMac13, 2 I put config.plist to clover! Use the latest kernel version 10.9.1 update Enjoy! Post a IOREG after changes! Sorry, does not boot. "fakeSMC: Fatal Failed to initialize SMC device" And I don't think that posing as an iMac will help me either in the long run. Imho, ultimately I must use new Mac Pro definitions, since this is the only Mac that also has LGA2011 socket. Link to comment Share on other sites More sharing options...
Bruxo Posted December 31, 2013 Share Posted December 31, 2013 Sorry, does not boot. "fakeSMC: Fatal Failed to initialize SMC device" And I don't think that posing as an iMac will help me either in the long run. Imho, ultimately I must use new Mac Pro definitions, since this is the only Mac that also has LGA2011 socket. Which version of sitema? Being the oldest in 10.9.1? FakeSMC put in folder 10.9 Clover! Which version of your FakeSMC? Link to comment Share on other sites More sharing options...
frankiee Posted December 31, 2013 Share Posted December 31, 2013 Which version of sitema? Being the oldest in 10.9.1? FakeSMC put in folder 10.9 Clover! Which version of your FakeSMC? 10.9.1 newest version of FakeSMC PS: boots without your DSDT / SSDT Link to comment Share on other sites More sharing options...
Bruxo Posted December 31, 2013 Share Posted December 31, 2013 10.9.1 newest version of FakeSMC PS: boots without your DSDT / SSDT boot Mac Pro or as Imac13? Try as iMac13 boot and see the results! Post an IOREG. Link to comment Share on other sites More sharing options...
frankiee Posted December 31, 2013 Share Posted December 31, 2013 Ah well, since iMac 13 was set in the clover config you provided, well I just used that. And I cannot post an ioReg simply bc I cannot boot with this config. Link to comment Share on other sites More sharing options...
Bruxo Posted December 31, 2013 Share Posted December 31, 2013 Ah well, since iMac 13 was set in the clover config you provided, well I just used that. And I cannot post an ioReg simply bc I cannot boot with this config. In Clover should be clear NVRAM! Open terminal and type "sudo nvram -c" without the quotes. Boot as Mac Pro! Use only DSDT Post IOREG! Link to comment Share on other sites More sharing options...
frankiee Posted January 1, 2014 Share Posted January 1, 2014 Cannot clear NVRAM via terminal, as I still cannot boot. But I deleted nvram.plist, but still same story. Must be something with your DSDT, as I never had FakeSMC probs before. Link to comment Share on other sites More sharing options...
Allan Posted January 1, 2014 Share Posted January 1, 2014 I have /efi/boot/bootx64.efi how would i make such an entry? bootx64.efi used to load Windows. Link to comment Share on other sites More sharing options...
Bruxo Posted January 1, 2014 Share Posted January 1, 2014 Loading wrong DSDT USBs Right now on Device SBME and USBE Method (_DSM, 4, NotSerialized) { Store (Package (0x02) { "AAPL,clock-id", Buffer (One) { 0x01 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Let you know what having your bios settings in UEFI ? ACPI-2.zip Link to comment Share on other sites More sharing options...
Lordadmiral Drake Posted January 1, 2014 Share Posted January 1, 2014 I meant: How do I create a firmware boot entry? Link to comment Share on other sites More sharing options...
apianti Posted January 1, 2014 Share Posted January 1, 2014 @frankiee, you can only use Mac pro for the reason you thought. And I'm pretty sure that it has to do with unsupported hardware and acpi problems. Unsure what you can really do at this point... We may find different behavior with 10.9.2. @Lordadmiral drake, are you sure you are selecting uefi boot? What firmware do you have? The version? You can create a boot entry through the efi shell command bcfg or Linux command efibootmgr. But my guess is you either don't have uefi or you have crippled efi that loads only Microsoft path, if it doesn't launch bootx64.efi. Link to comment Share on other sites More sharing options...
Bruxo Posted January 1, 2014 Share Posted January 1, 2014 @frankiee, you can only use Mac pro for the reason you thought. And I'm pretty sure that it has to do with unsupported hardware and acpi problems. Unsure what you can really do at this point... We may find different behavior with 10.9.2. OS System caring ACPI only! He injecting properties ACPI over a iMac13 and think that your processor is a family of Ivy, which is correct; You can try iMac13, 1 because this is config.plist iMac13, 2 Remember to have the last copilação Clover installed! Link to comment Share on other sites More sharing options...
frankiee Posted January 1, 2014 Share Posted January 1, 2014 Loading wrong DSDT USBs Right now on Device SBME and USBE Method (_DSM, 4, NotSerialized) { Store (Package (0x02) { "AAPL,clock-id", Buffer (One) { 0x01 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Let you know what having your bios settings in UEFI ? Listen your DSDT does simply not work, also not the newest one. Also could not install 10.9.2 beta "the installer encountered an error" So I am about to give up for now, it is getting so annyoing. Anyone, any idea left? Think I can ditch clover as well, simply does not work. Link to comment Share on other sites More sharing options...
Bruxo Posted January 1, 2014 Share Posted January 1, 2014 Listen your DSDT does simply not work, also not the newest one. Also could not install 10.9.2 beta "the installer encountered an error" So I am about to give up for now, it is getting so annyoing. Anyone, any idea left? Think I can ditch clover as well, simply does not work. Problem not be Clover, Apple 10.9.2 installer or the DSDT Being partition, buggy system! You use this partition for testing! And so much testing has been done on it, and it's buggy! Fassa another clean installation for testing!! Clover and works with DSDT and Chimera Chamelion DSDT universal bootloader! Link to comment Share on other sites More sharing options...
frankiee Posted January 1, 2014 Share Posted January 1, 2014 I cannot install 10.9.2 even without DSDT. And this is a more or less clean install. Don't have much more time to waste for today. And I am sure that waiting for 10.9.2 to be released is the only option that makes sense now. If it still does not work until then, I will really and truly regret building a hackintosh. Link to comment Share on other sites More sharing options...
Bruxo Posted January 1, 2014 Share Posted January 1, 2014 I cannot install 10.9.2 even without DSDT. And this is a more or less clean install. Don't have much more time to waste for today. And I am sure that waiting for 10.9.2 to be released is the only option that makes sense now. If it still does not work until then, I will really and truly regret building a hackintosh. Yes then repent: Rampage IV Extreme Asus Rampage IV Extreme All had success, because you would not have? Link to comment Share on other sites More sharing options...
apianti Posted January 1, 2014 Share Posted January 1, 2014 You seem to be confused bruxo, he has a fourth generation cpu, not a third generation. Ivy bridge is not ivy bridge-e. Just like Sandy bridge is not Sandy bridge-e. That is the issue not his chipset or such. Link to comment Share on other sites More sharing options...
frankiee Posted January 1, 2014 Share Posted January 1, 2014 Yes then repent: Rampage IV Extreme Asus Rampage IV Extreme All had success, because you would not have? Well, one big problem here is that while I appreciate any help, it makes no sense if people do not read what I actually say ... I do not know how many times I have stated in this thread alone, that I seem to have a DIFFERENT X79 REVISION. YES, there seems to be MORE than one X79 revision. And actually rampageDev was the one who found this - and if somebody really knows about such stuff, he is the one ... to be precise, when I checked my chipset using CPU-Z, it says "rev06". And this different revision also seems to cause the USB ports not behaving like they do with older revisions. A combination of (old style) clover patches used to solve this, but as pokenguyen found out, even these patches were not applied correctly, since my DSDT expects a different return param than what is actually inserted. And I also have stated this several times, but nobody seemed to even recognize. You understand why I am getting frustrated??? And this different revision MAY also be responsible for sleep problems, but of course that MAY also be my 4930K (or the combination of both). And yes, it even states in my sig that I have a 4930K ... *sigh*. So, while the USB problem seems to be similar to the age old HPET issue, it is not sure if the corresponding DSDT edit is actually the correct patch, as the information what INTEL has actually changed with their revision is still missing. Plus, it seems that you made at least one mistake with patching my DSDT. I do not know much about ACPI, but since I am a developer myself, I actually know a bit about computers ... So it seems that you deleted a lot of Processor (C010.... entries. But, these entries seem to count up using hex numbers. But what you did is leaving entries C010...C012 while deleting entries C00A to C00F. But since this is HEX, it seems you deleted actually the wrong entries. Of course I may be wrong, but this immediatly caught my attention. Also you seem to rename a lot of other entries, and I don't know if that also might be a problem. So I hope you understand now why I am having problems, and why I need some competent help here .... And I still think clover should also support the newer X79 revision! So I hope somebody who can actually read and understand what I am trying to communicate will finally care about this. Link to comment Share on other sites More sharing options...
joe75 Posted January 1, 2014 Share Posted January 1, 2014 Use an older build if it actually worked for this board! Im on build 1995.. You don't have to always use the latest build which is "usually" unstable and still being worked on. I don't understand why you guys drop so much money on deluxe boards with complicated chipsets and expect it to work on a hacked os. If you are going to regret building a hackint0sh at least search for compatible hardware before building it. 3 Link to comment Share on other sites More sharing options...
frankiee Posted January 1, 2014 Share Posted January 1, 2014 Use an older build if it actually worked for this board! Im on build 1995.. You don't have to always use the latest build which is "usually" unstable and still being worked on. I don't understand why you guys drop so much money on deluxe boards with complicated chipsets and expect it to work on a hacked os. If you are going to regret building a hackint0sh at least search for compatible hardware before building it. Listen, I actually DID choose my components very carefully. And I choose the R4E bc it was reported as working very reliably - which it surely does IF you don't have the newer revision. And tell me, how should I've known that? Nobody knew that the rev actually changed - that was simply never communicated by ASUS. So I'd call it "bad luck". But what is annoying is not that fact, but rather that nobody seems to really listen to what I say. And I am through about 5-6 different clover revisions, and none has worked reliably so far, at least in terms of sleep. So, now I am supposed to try each and every revision? Don't you think it would be better to properly analyse and actually solve this problem, instead of just playing "try and error"? And no, even IF that would work, I do not want to be stuck with an old clover version forever ... that is not a proper solution in my eyes at least. Link to comment Share on other sites More sharing options...
apianti Posted January 1, 2014 Share Posted January 1, 2014 Unsure why you think it's your chipset that is not supported, I don't think that's the case, as I have seen users with x79 report upgrade from an ivy bridge to an ivy bridge-e and it now fails to boot correctly. Also it would fail to get to the desktop at all in that case. It's far more likely that your usb controller is unsupported, or merely only has different device id. Your cpu is definitely unsupported. You probably should have done a little more research before buying such high end equipment if your goal was to build a hack. I bought what I knew would work oob with as little modification as possible, which is none. Lol, there is plenty of resources about, you may be frustrated but you can only be patient now and let stuff catch up since you choose to get untested bleeding edge. You may actually never have fully working system, and shouldn't get hopes up that you will. Haswell support was just added in the last few weeks, it usually takes longer for the more rare Xeon style cpus since they are more rare in the wild. Dude you seem to think that this works by magic, all this stuff NEEDS TO BE DISCOVERED. None of it is available openly, if it was it would be real easy to hackintosh, however it requires quite a bit of trial and error, and you don't seem to be listening to us, which is its not your chipset, it's the other components in the board itself. These often change you could order another and get an older revision, this is common among mobo oem. You should very well have known this if you're building your own machines. Link to comment Share on other sites More sharing options...
chris1111 Posted January 1, 2014 Share Posted January 1, 2014 Listen, I actually DID choose my components very carefully. And I choose the R4E bc it was reported as working very reliably - which it surely does IF you don't have the newer revision. And tell me, how should I've known that? Nobody knew that the rev actually changed - that was simply never communicated by ASUS. So I'd call it "bad luck". But what is annoying is not that fact, but rather that nobody seems to really listen to what I say. And I am through about 5-6 different clover revisions, and none has worked reliably so far, at least in terms of sleep. So, now I am supposed to try each and every revision? Don't you think it would be better to properly analyse and actually solve this problem, instead of just playing "try and error"? And no, even IF that would work, I do not want to be stuck with an old clover version forever ... that is not a proper solution in my eyes at least. Try this , can be help you HI hopes http://www.fichier-zip.com/2014/01/01/installer-pic/ Link to comment Share on other sites More sharing options...
frankiee Posted January 1, 2014 Share Posted January 1, 2014 Try this , can be help you HI hopes http://www.fichier-zip.com/2014/01/01/installer-pic/ As I said I have tried quite a number of different clover revisions already, 2377 being one of them. So unfortunately I am pretty sure this won't help. Link to comment Share on other sites More sharing options...
chris1111 Posted January 1, 2014 Share Posted January 1, 2014 As I said I have tried quite a number of different clover revisions already, 2377 being one of them. So unfortunately I am pretty sure this won't help. Its my build Installer try and report back This Installer made of couple Miracle Link to comment Share on other sites More sharing options...
Recommended Posts