StoneTemplePilots Posted September 25, 2014 Share Posted September 25, 2014 Ok, i was in same situation with i5-3570k ivy bridge. I think you need to play with this option: -workarounds for Ivy Bridge [0/1/2/3] 0 = no workarounds 1 = inject extra (turbo) P-State at the top with maximum (turbo) frequency + 1 MHz 2 = inject extra P-States at the bottom 3 = both i will post tomorrow the differences of my ssdt between xcpm and noxcpm if it can help. Fred thanks Fred Link to comment Share on other sites More sharing options...
FredWst Posted September 26, 2014 Share Posted September 26, 2014 thanks Fred Look at Name (APSN, 0xyy) and Name (APSS, Package (0xyy) which are different according to using -xcpm or not For cpu i5-3570K ssdt xcpm Name (APLF, 0x08) Name (APSN, 0x04) Name (APSS, Package (0x1F) { Package (0x06) { 0x0ED8, 0x00012CC8, 0x0A, 0x0A, 0x2600, 0x2600 }, Package (0x06) { 0x0E74, 0x00012CC8, 0x0A, 0x0A, 0x2500, 0x2500 }, Package (0x06) { 0x0E10, 0x00012CC8, 0x0A, 0x0A, 0x2400, 0x2400 }, Package (0x06) { 0x0DAC, 0x00012CC8, 0x0A, 0x0A, 0x2300, 0x2300 }, Package (0x06) { 0x0D48, 0x00012CC8, 0x0A, 0x0A, 0x2200, 0x2200 }, Package (0x06) { 0x0CE4, 0x000120A0, 0x0A, 0x0A, 0x2100, 0x2100 }, Package (0x06) { 0x0C80, 0x000114B0, 0x0A, 0x0A, 0x2000, 0x2000 }, Package (0x06) { 0x0C1C, 0x000108F8, 0x0A, 0x0A, 0x1F00, 0x1F00 }, Package (0x06) { 0x0BB8, 0xFD77, 0x0A, 0x0A, 0x1E00, 0x1E00 }, Package (0x06) { 0x0B54, 0xF22D, 0x0A, 0x0A, 0x1D00, 0x1D00 }, Package (0x06) { 0x0AF0, 0xE719, 0x0A, 0x0A, 0x1C00, 0x1C00 }, Package (0x06) { 0x0A8C, 0xDC3B, 0x0A, 0x0A, 0x1B00, 0x1B00 }, Package (0x06) { 0x0A28, 0xD192, 0x0A, 0x0A, 0x1A00, 0x1A00 }, Package (0x06) { 0x09C4, 0xC71F, 0x0A, 0x0A, 0x1900, 0x1900 }, Package (0x06) { 0x0960, 0xBCDF, 0x0A, 0x0A, 0x1800, 0x1800 }, Package (0x06) { 0x08FC, 0xB2D4, 0x0A, 0x0A, 0x1700, 0x1700 }, Package (0x06) { 0x0898, 0xA8FC, 0x0A, 0x0A, 0x1600, 0x1600 }, Package (0x06) { 0x0834, 0x9F58, 0x0A, 0x0A, 0x1500, 0x1500 }, Package (0x06) { 0x07D0, 0x95E6, 0x0A, 0x0A, 0x1400, 0x1400 }, Package (0x06) { 0x076C, 0x8CA7, 0x0A, 0x0A, 0x1300, 0x1300 }, Package (0x06) { 0x0708, 0x8399, 0x0A, 0x0A, 0x1200, 0x1200 }, Package (0x06) { 0x06A4, 0x7ABD, 0x0A, 0x0A, 0x1100, 0x1100 }, Package (0x06) { 0x0640, 0x7212, 0x0A, 0x0A, 0x1000, 0x1000 }, Package (0x06) { 0x05DC, Zero, 0x0A, 0x0A, 0x0F00, 0x0F00 }, Package (0x06) { 0x0578, Zero, 0x0A, 0x0A, 0x0E00, 0x0E00 }, Package (0x06) { 0x0514, Zero, 0x0A, 0x0A, 0x0D00, 0x0D00 }, Package (0x06) { 0x04B0, Zero, 0x0A, 0x0A, 0x0C00, 0x0C00 }, Package (0x06) { 0x044C, Zero, 0x0A, 0x0A, 0x0B00, 0x0B00 }, Package (0x06) { 0x03E8, Zero, 0x0A, 0x0A, 0x0A00, 0x0A00 }, Package (0x06) { 0x0384, Zero, 0x0A, 0x0A, 0x0900, 0x0900 }, Package (0x06) { 0x0320, Zero, 0x0A, 0x0A, 0x0800, 0x0800 } }) ssdt apm Name (APLF, 0x08) Name (APSN, 0x05) Name (APSS, Package (0x20) { Package (0x06) { 0x0ED9, 0x00012CC8, 0x0A, 0x0A, 0x2700, 0x2700 }, Package (0x06) { 0x0ED8, 0x00012CC8, 0x0A, 0x0A, 0x2600, 0x2600 }, Package (0x06) { 0x0E74, 0x00012CC8, 0x0A, 0x0A, 0x2500, 0x2500 }, Package (0x06) { 0x0E10, 0x00012CC8, 0x0A, 0x0A, 0x2400, 0x2400 }, Package (0x06) { 0x0DAC, 0x00012CC8, 0x0A, 0x0A, 0x2300, 0x2300 }, Package (0x06) { 0x0D48, 0x00012CC8, 0x0A, 0x0A, 0x2200, 0x2200 }, Package (0x06) { 0x0CE4, 0x000120A0, 0x0A, 0x0A, 0x2100, 0x2100 }, Package (0x06) { 0x0C80, 0x000114B0, 0x0A, 0x0A, 0x2000, 0x2000 }, Package (0x06) { 0x0C1C, 0x000108F8, 0x0A, 0x0A, 0x1F00, 0x1F00 }, Package (0x06) { 0x0BB8, 0xFD77, 0x0A, 0x0A, 0x1E00, 0x1E00 }, Package (0x06) { 0x0B54, 0xF22D, 0x0A, 0x0A, 0x1D00, 0x1D00 }, Package (0x06) { 0x0AF0, 0xE719, 0x0A, 0x0A, 0x1C00, 0x1C00 }, Package (0x06) { 0x0A8C, 0xDC3B, 0x0A, 0x0A, 0x1B00, 0x1B00 }, Package (0x06) { 0x0A28, 0xD192, 0x0A, 0x0A, 0x1A00, 0x1A00 }, Package (0x06) { 0x09C4, 0xC71F, 0x0A, 0x0A, 0x1900, 0x1900 }, Package (0x06) { 0x0960, 0xBCDF, 0x0A, 0x0A, 0x1800, 0x1800 }, Package (0x06) { 0x08FC, 0xB2D4, 0x0A, 0x0A, 0x1700, 0x1700 }, Package (0x06) { 0x0898, 0xA8FC, 0x0A, 0x0A, 0x1600, 0x1600 }, Package (0x06) { 0x0834, 0x9F58, 0x0A, 0x0A, 0x1500, 0x1500 }, Package (0x06) { 0x07D0, 0x95E6, 0x0A, 0x0A, 0x1400, 0x1400 }, Package (0x06) { 0x076C, 0x8CA7, 0x0A, 0x0A, 0x1300, 0x1300 }, Package (0x06) { 0x0708, 0x8399, 0x0A, 0x0A, 0x1200, 0x1200 }, Package (0x06) { 0x06A4, 0x7ABD, 0x0A, 0x0A, 0x1100, 0x1100 }, Package (0x06) { 0x0640, 0x7212, 0x0A, 0x0A, 0x1000, 0x1000 }, Package (0x06) { 0x05DC, Zero, 0x0A, 0x0A, 0x0F00, 0x0F00 }, Package (0x06) { 0x0578, Zero, 0x0A, 0x0A, 0x0E00, 0x0E00 }, Package (0x06) { 0x0514, Zero, 0x0A, 0x0A, 0x0D00, 0x0D00 }, Package (0x06) { 0x04B0, Zero, 0x0A, 0x0A, 0x0C00, 0x0C00 }, Package (0x06) { 0x044C, Zero, 0x0A, 0x0A, 0x0B00, 0x0B00 }, Package (0x06) { 0x03E8, Zero, 0x0A, 0x0A, 0x0A00, 0x0A00 }, Package (0x06) { 0x0384, Zero, 0x0A, 0x0A, 0x0900, 0x0900 }, Package (0x06) { 0x0320, Zero, 0x0A, 0x0A, 0x0800, 0x0800 } }) Link to comment Share on other sites More sharing options...
StoneTemplePilots Posted September 26, 2014 Share Posted September 26, 2014 yeah, adressing is different and one package state 0x2700 is missing: Package (0x06) { 0x0ED9, 0x00012CC8, 0x0A, 0x0A, 0x2700, 0x2700 }, but why? Link to comment Share on other sites More sharing options...
FredWst Posted September 26, 2014 Share Posted September 26, 2014 yeah, adressing is different and one package state 0x2700 is missing: Package (0x06) { 0x0ED9, 0x00012CC8, 0x0A, 0x0A, 0x2700, 0x2700 }, but why? One for XCPM and one different for APM. If i try ssdt xcpm with APM it does not work. If i try ssdt APM with XCPMt does not work. So for ivy-bridge ssdth for XCPM and APM must be different. Don't know why maybe Pike will be able to answer that. Fred Link to comment Share on other sites More sharing options...
StoneTemplePilots Posted September 26, 2014 Share Posted September 26, 2014 One for XCPM and one different for APM. If i try ssdt xcpm with APM it does not work. If i try ssdt APM with XCPMt does not work. So for ivy-bridge ssdth for XCPM and APM must be different. Don't know why maybe Pike will be able to answer that. Fred I read he recommends removing some of the higher turbo states until the warning is gone. Link to comment Share on other sites More sharing options...
WinstonAce Posted September 27, 2014 Share Posted September 27, 2014 It's seems that I can't get OzmosisDefaults to load from OZ directory where exactly should it be? Link to comment Share on other sites More sharing options...
Aigors Posted September 27, 2014 Share Posted September 27, 2014 It's seems that I can't get OzmosisDefaults to load from OZ directory where exactly should it be? Have you delete all nvram contents? Link to comment Share on other sites More sharing options...
FredWst Posted September 27, 2014 Share Posted September 27, 2014 It's seems that I can't get OzmosisDefaults to load from OZ directory where exactly should it be? Hi, il must be name defaults.plist. And you must clear nvram. boot in Gui and press CMD+ALT+P+R Fred 1 Link to comment Share on other sites More sharing options...
WinstonAce Posted September 27, 2014 Share Posted September 27, 2014 Hi, il must be name defaults.plist. And you must clear nvram. boot in Gui and press CMD+ALT+P+R Fred Thanks that did the trick Link to comment Share on other sites More sharing options...
griven Posted September 28, 2014 Share Posted September 28, 2014 Are there any news about Raid0 and FusionDrive support ? 1 Link to comment Share on other sites More sharing options...
ivanwinkel Posted September 28, 2014 Share Posted September 28, 2014 The only way it will work right now, is when you reinstall on your fusion drive(or raid) Link to comment Share on other sites More sharing options...
kan2905 Posted September 28, 2014 Share Posted September 28, 2014 I just upgraded my BIOS to the latest rev. of ozmosis I used to boot directly into WIN, have to go into boot menu to selct the OSX HD Now I can't find (in BIOS) or boot into my windows HD. it boots automatically into OSX Do I have to reinstall windows or is there a way to reactivate it ? Link to comment Share on other sites More sharing options...
Aigors Posted September 28, 2014 Share Posted September 28, 2014 I just upgraded my BIOS to the latest rev. of ozmosis I used to boot directly into WIN, have to go into boot menu to selct the OSX HD Now I can't find (in BIOS) or boot into my windows HD. it boots automatically into OSX Do I have to reinstall windows or is there a way to reactivate it ? In which way have you installed windows? in efi mode or in legacy mode? check your boot settings in your bios and set boot to legacy and efi mode, OSX boot only in efi mode, if you have installed windows in legacy mode, you have to set up you CSM to even legacy mode. Link to comment Share on other sites More sharing options...
Aigors Posted September 28, 2014 Share Posted September 28, 2014 Hi, for what you know, can i use CSMVIDEO from quo bios on Z97 chipset? Link to comment Share on other sites More sharing options...
Kynyo Posted September 29, 2014 Share Posted September 29, 2014 In which way have you installed windows? in efi mode or in legacy mode? check your boot settings in your bios and set boot to legacy and efi mode, OSX boot only in efi mode, if you have installed windows in legacy mode, you have to set up you CSM to even legacy mode. There is no fix for this. The Win7 video drivers require the CSM, even in UEFI mode. The video driver will not function properly when the CSM is disabled. If you want to use Win7 on your system, you have to leave the CSM enabled. EDIT: I installed W7 in UEFI mode with only CSM enabled. This is my setup. (UEFI only, NOT UEFI & Legacy) Link to comment Share on other sites More sharing options...
Aigors Posted September 29, 2014 Share Posted September 29, 2014 as i say, enable CSM and set boot type to uefi and legacy mode if dont even install windows in uefi mode. Link to comment Share on other sites More sharing options...
joe75 Posted September 29, 2014 Share Posted September 29, 2014 If you guys can't see your windows installs either uefi or legacy the first thing to try is to disable boot entries filter. For graphics, CSM/GOP is only for start up (pre-boot environment), OS drivers are not part of this. 1 Link to comment Share on other sites More sharing options...
Kynyo Posted September 29, 2014 Share Posted September 29, 2014 The rule of CSM/GOP does not apply for Windows 7. It rulls just CSM UEFI mode. If CSM it's disabled, Windows boots, but no image displayed on monitor. 1 Link to comment Share on other sites More sharing options...
StoneTemplePilots Posted September 29, 2014 Share Posted September 29, 2014 imessage fixed by the way: http://www.insanelymac.com/forum/topic/299372-how-to-solve-imessage-login-problem/?p=2064771 Link to comment Share on other sites More sharing options...
HBP Posted September 29, 2014 Share Posted September 29, 2014 Are there any news about Raid0 and FusionDrive support ? yes, I resolved this, go into the EDKii shell and then go to the 3rd partition on the first drive of your Raid/fusion drive and drop down into until you get to the Boot.efi, and run it, after that it will always be in the menu. look at my previous post for the location of that file. HBP Link to comment Share on other sites More sharing options...
HBP Posted September 29, 2014 Share Posted September 29, 2014 anyone else having this issue? the only difference is that I have hard coded the ROM value into the OzmosisDefaults on the EFI so it shouldn't change. when attempting to reset it in Yosemite I get a garbled mess. Yosemite 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM %2574%25d4%2535%2518%2512%25ea Mavericks 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM %74%d4%35%18%12%ea HBP Link to comment Share on other sites More sharing options...
StoneTemplePilots Posted September 29, 2014 Share Posted September 29, 2014 anyone else having this issue? the only difference is that I have hard coded the ROM value into the OzmosisDefaults on the EFI so it shouldn't change. when attempting to reset it in Yosemite I get a garbled mess. Yosemite 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM %2574%25d4%2535%2518%2512%25ea Mavericks 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM %74%d4%35%18%12%ea HBP I noticed the same but that's why I stored the decoded value directly in Defaults.plist which is a static OzmosisDefaults.ffs in my case. Read my last post above. Link to comment Share on other sites More sharing options...
HBP Posted September 29, 2014 Share Posted September 29, 2014 I noticed the same but that's why I stored the decoded value directly in Defaults.plist which is a static OzmosisDefaults.ffs in my case. Read my last post above. decoded? how so, even using the Defaults.plist I get the same thing. OzmosisDefaults.ffs value is ROM %74%d4%35%18%12%ea I am thinking that somewhere in the logic Yosemite is adding or modifying the ROM value... HBP Link to comment Share on other sites More sharing options...
StoneTemplePilots Posted September 29, 2014 Share Posted September 29, 2014 decoded? how so, even using the Defaults.plist I get the same thing. OzmosisDefaults.ffs value is ROM %74%d4%35%18%12%ea I am thinking that somewhere in the logic Yosemite is adding or modifying the ROM value... HBP when I set sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=%77%77%77%77%77%77 and then I printed the value I get nvram -p 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM wwwwww I mean wwwwww is the decoded value, that's what I set in Defaults.plist using %77%77%77%77%77%77 I'm getting the same scrambled values as you posted with 25. Link to comment Share on other sites More sharing options...
modbin Posted September 29, 2014 Share Posted September 29, 2014 The percent sign % is 0x25 1 Link to comment Share on other sites More sharing options...
Recommended Posts