Jump to content

SMBIOS change causes black screen instead of loginwindow

randomusername00
 Share
8 posts in this topic

Recommended Posts

randomusername00
randomusername00
Posted
Posted

Hi,

for a few days I have been trying to chase my "failed to load stepper" issue

 

Turns out, changing my SMBIOS settings in Clover's config.plist from MacPro3,1 to either MacPro6,1 or iMac15,1 cause my monitor to stop receiving signal when the system goes from the boot screen to the loginwindow UI

 

Having the screen connected over DVI or HDMI seems to make no difference - either works with MP3,1 and either fails with MP6,1 (I only tried DVI with iM15,1)

 

Configuration:

- Asus Z97 deluxe

- i7 4790k

- MSi GTX 970 w/ nVidia web drivers

- Yosemite 10.10.3

 

Questions:

- Is any of this expected?

- Is there a fix?

- Should I expect better CPU power management if I manage to change my SMBIOS?

- Should I just not worry about it since the MP3,1 configuration works for me?

Link to comment
Share on other sites
anonymousnbs
anonymousnbs
Posted
Posted

Hi,

for a few days I have been trying to chase my "failed to load stepper" issue

 

Turns out, changing my SMBIOS settings in Clover's config.plist from MacPro3,1 to either MacPro6,1 or iMac15,1 cause my monitor to stop receiving signal when the system goes from the boot screen to the loginwindow UI

 

Having the screen connected over DVI or HDMI seems to make no difference - either works with MP3,1 and either fails with MP6,1 (I only tried DVI with iM15,1)

 

Configuration:

- Asus Z97 deluxe

- i7 4790k

- MSi GTX 970 w/ nVidia web drivers

- Yosemite 10.10.3

 

Questions:

- Is any of this expected?

- Is there a fix?

- Should I expect better CPU power management if I manage to change my SMBIOS?

- Should I just not worry about it since the MP3,1 configuration works for me?

haswell > iMac 14,2 

 

2. GTX 970 > install with web driver

3. Patch DSDT and patch AGPM 

​4. MacPro 3.1 install web driver don't Incompatible with haswell

 

https://www.youtube.com/watch?v=CjdJKhlWDWk

Link to comment
Share on other sites
randomusername00
randomusername00
Posted
  • Author
Posted

Thanks anonymousnbs

I applied your patches to config.plist & the SSDT (my audio worked already so I left that part out)

 

I don't get the stepper failure anymore - and this is my AICPUPMI log:

 

4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: v3.3 Copyright © 2012-2014 Pike R. Alpha. All rights reserved

4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: logMSRs............................: 1
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: logIGPU............................: 0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: logCStates.........................: 1
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: logIPGStyle........................: 1
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MWAIT C-States.....................: 270624
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35)  : 0x40008
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE)  : 0x80838F3012800
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2)  : 0x1E000400
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4)  : 0x21814
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7)  : 0x23367C7D9C
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: IA32_APERF.................(0xE8)  : 0x240F6F7F24
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xE0000
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x23A400002A00
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2C00
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x883F0000
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2A2B2C2C
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x1
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x4005F
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA0E03
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0x428370001A82C0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x4C2E156
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x8842
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x8873
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x8891
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x10141400000348
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x25BAC04
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_CONFIG_TDP_NOMINAL.....(0x648) : 0x28
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL1......(0x649) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_CONFIG_TDP_LEVEL2......(0x64a) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_CONFIG_TDP_CONTROL.....(0x64b) : 0x80000000
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_TURBO_ACTIVATION_RATIO.(0x64c) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 800 MHz
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 4000 MHz
4/20/15 11:28:52.000 AM kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 4400 MHz
4/20/15 11:28:53.000 AM kernel[0]: AICPUPMI: CPU P-States [ 41 42 (43) ]
4/20/15 11:28:53.000 AM kernel[0]: AICPUPMI: CPU C3-Cores [ 2 5 6 7 ]
4/20/15 11:28:53.000 AM kernel[0]: AICPUPMI: CPU C6-Cores [ 1 2 3 5 6 ]
4/20/15 11:28:53.000 AM kernel[0]: AICPUPMI: CPU C7-Cores [ 1 2 3 5 6 ]
4/20/15 11:28:54.000 AM kernel[0]: AICPUPMI: CPU P-States [ 38 41 42 43 (44) ]
4/20/15 11:28:54.000 AM kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 5 6 7 ]
4/20/15 11:28:54.000 AM kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 5 6 7 ]
4/20/15 11:28:54.000 AM kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 5 6 7 ]
4/20/15 11:28:55.000 AM kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 5 6 7 ]
4/20/15 11:28:55.000 AM kernel[0]: AICPUPMI: CPU C7-Cores [ 0 1 2 3 4 5 6 7 ]
4/20/15 11:28:55.000 AM kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 ]
4/20/15 11:28:55.000 AM kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 ]
4/20/15 11:29:03.000 AM kernel[0]: AICPUPMI: CPU P-States [ 38 (40) 41 42 43 44 ]
4/20/15 11:29:04.000 AM kernel[0]: AICPUPMI: CPU P-States [ 36 38 (40) 41 42 43 44 ]
4/20/15 11:29:05.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 34 36 38 40 41 42 43 44 ]
4/20/15 11:29:05.000 AM kernel[0]: AICPUPMI: CPU P-States [ 8 34 36 38 39 (40) 41 42 43 44 ]
4/20/15 11:29:06.000 AM kernel[0]: AICPUPMI: CPU P-States [ 8 34 35 36 38 39 (40) 41 42 43 44 ]
4/20/15 11:29:07.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 21 34 35 36 38 39 40 41 42 43 44 ]
4/20/15 11:29:08.000 AM kernel[0]: AICPUPMI: CPU P-States [ 8 19 21 34 35 36 38 39 (40) 41 42 43 44 ]
4/20/15 11:29:09.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 19 21 23 34 35 36 38 39 40 41 42 43 44 ]
4/20/15 11:29:12.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 19 21 23 24 34 35 36 38 39 40 41 42 43 44 ]
4/20/15 11:29:12.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 23 24 34 35 36 38 39 40 41 42 43 44 ]
4/20/15 11:29:15.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 23 24 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:21.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 23 24 31 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:25.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 23 24 29 31 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:27.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 23 24 28 29 31 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:31.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 23 24 27 28 29 31 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:32.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 23 24 27 28 29 31 33 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:34.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 23 24 27 28 29 31 32 33 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:35.000 AM kernel[0]: AICPUPMI: CPU P-States [ 8 17 19 21 23 24 25 27 28 29 31 32 33 34 35 36 37 38 39 (40) 41 42 43 44 ]
4/20/15 11:29:44.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 22 23 24 25 27 28 29 31 32 33 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:45.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 22 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:49.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:51.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 ]
4/20/15 11:29:56.000 AM kernel[0]: AICPUPMI: CPU P-States [ (8) 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 ]
 
I see a lot of P-States, but looks like only a couple of those actually end up being used
Link to comment
Share on other sites
MacUser2525
MacUser2525
Posted
Posted

Gotcha!

 

I was reading that there's BIOS settings one can tamper with to get more P-states, but I don't care enough to go above and beyond a real iMac

My turbo works, and I get a low-power idle. Good enough for me

 

Thanks everyone!

 

Indeed more trouble than it is worth, if you install the HW Monitor program you will find that for the vast majority of the time it is sitting at the idle state anyways.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...