Contribute
Register

[solved] can only boot using cpus=1

Status
Not open for further replies.

Feartech

Moderator
Joined
Aug 3, 2013
Messages
32,233
Motherboard
Asus N752VX-OpenCore
CPU
i7-6700HQ / HM170
Graphics
HD 530 1920 x 1080
Mac
  1. iMac
Mobile Phone
  1. iOS
As the title says...

This is only happening using 10.13.4 all previous versions have been fine, i can boot only using cpus=1 or using safe mode

IMG_0771.jpg


When i use cpus=1 the next line that comes up is waiting for DSMOS which will then carry on booting up

Was wondering if anyone had any insight?
 

Attachments

  • debug_27118.zip
    1.6 MB · Views: 101
As the title says...

This is only happening using 10.13.4 all previous versions have been fine, i can boot only using cpus=1 or using safe mode

View attachment 332487

When i use cpus=1 the next line that comes up is waiting for DSMOS which will then carry on booting up

Was wondering if anyone had any insight?

I think this has been shown to be a C-State issue, some can change in BIOS and fix it.
You might also try VoodooTSCSync.kext.
 
I think this has been shown to be a C-State issue, some can change in BIOS and fix it.
You might also try VoodooTSCSync.kext.
ahh thanks, i will check that out
 
I think this has been shown to be a C-State issue, some can change in BIOS and fix it.
You might also try VoodooTSCSync.kext.
there doesn't seem to be an option in the BIOS to change any settings for C-State

i installed VoodooTSCSync.kext to system and i get one line further from the above screen shot:

Waiting for DSMOS...

which i understand that normally means a lack of FakeSMC.kext which i already have installed though

i have attached new PR files hoping a fresh pair of eyes can see something i may have missed

(can still only boot using cpus=1 argument)
 

Attachments

  • debug_7332.zip
    1.7 MB · Views: 81
there doesn't seem to be an option in the BIOS to change any settings for C-State

i installed VoodooTSCSync.kext to system and i get one line further from the above screen shot:

Waiting for DSMOS...

which i understand that normally means a lack of FakeSMC.kext which i already have installed though

i have attached new PR files hoping a fresh pair of eyes can see something i may have missed

(can still only boot using cpus=1 argument)

You might try with MacBookPro11,1.
 
You might try with MacBookPro11,1.
still the same issue, i have gone back to 10.13.3 from my backup

thanks for taking a look though!
 
there doesn't seem to be an option in the BIOS to change any settings for C-State

i installed VoodooTSCSync.kext to system and i get one line further from the above screen shot:

Waiting for DSMOS...

which i understand that normally means a lack of FakeSMC.kext which i already have installed though

i have attached new PR files hoping a fresh pair of eyes can see something i may have missed

(can still only boot using cpus=1 argument)

Hi I noticed a few things that may affect your booting. In ACPI you have CSR 0x67 which is for Sierra most people now using 0x03EF or 0x03FF for CSRActiveConfiguration setting in High Sierra. I made a few config.plist changes that might fix boot issues. Check it out to see if these changes work.
 

Attachments

  • config.plist.zip
    3.6 KB · Views: 134
Hi I noticed a few things that may affect your booting. In ACPI you have CSR 0x67 which is for Sierra most people now using 0x03EF or 0x03FF for CSRActiveConfiguration setting in High Sierra. I made a few config.plist changes that might fix boot issues. Check it out to see if these changes work.
ahh, thanks for that!

i will setup my other hard drive and check that out probably tomorrow now

(i may have to set InjectKexts back to Detect as I have all my kexts installed to system though :) )
 
there doesn't seem to be an option in the BIOS to change any settings for C-State

If you could determine which C-states need disabling, you might be able to disable them via patches to ACPI (eg. patching to _CST methods).
 
If you could determine which C-states need disabling, you might be able to disable them via patches to ACPI (eg. patching to _CST methods).
The only reference I found for _CST in:
Code:
SSDT-x4_2-Cpu0Cst.dsl
SSDT-x4_3-ApCst.dsl

would i then use the following code:

Code:
Name (CSTF, Zero)
        Method (_CST, 0, Serialized)  // _CST: C-States
        {
            {
            Return (0)
        }
 

Attachments

  • SSDT-x4_2-Cpu0Cst.dsl
    7.4 KB · Views: 137
  • SSDT-x4_3-ApCst.dsl
    2.9 KB · Views: 133
  • debug_19528.zip
    2.2 MB · Views: 89
Status
Not open for further replies.
Back
Top