Contribute
Register

"Cold boot" reboot problem

Status
Not open for further replies.
Joined
Jul 5, 2016
Messages
15
Motherboard
Gigabyte GA-Z170X-UD3
CPU
i7-6700K
Graphics
GTX 950
Mac
  1. iMac
  2. MacBook Pro
Classic Mac
  1. Power Mac
Hello!

A year ago I build my first hackintosh with the help of this wonderful site and following the guide here (thanks to Cnrd and the rest of the people who collaborated):
https://www.tonymacx86.com/threads/guide-el-capitan-on-the-ga-z170x-ud3.180618/

They helped me with some other issues:
https://www.tonymacx86.com/threads/guide-el-capitan-on-the-ga-z170x-ud3.180618/page-39

, but this one remained unsolved (thought i´ve been searching A LOT on the web).

Everything is working ok since then, except for this strange behavior that´s driving me crazy. When I do a "cold boot" (after more than 20 minutes aprox. since my last complete shut down) the computer reboots just after the apple logo and the progress bar disappears. Sometimes it reboots one, two or three times, sometimes it gets to the desktop for a moment and freezes, but it always needs at least one complete reboot after the logo to be stable.

After that, no problem at all, all working fine, and I can reboot as many times as needed without a problem. But when I shut down the system for a period, it need again at least one reboot to work properly.

Nvidia web drivers installed and working.When I do a «cold boot» in clover´s verbose mode there´s no error shown, it just reboots, and no log is generated in console app. If I try to "cold boot" with verbose, nv_disable=1 (no nvidia web drivers) and «don´t reboot on panic», it shows every time a different «cpu caller» panic (cpu 0, cpu3, cpu2, cpu1…), like the attached ones, but no idea what it means.

I´ve tried a lot of different clover options (-xcpm, darkwake, alcoff…) and other options I found in the web in similar situations (returned to imac17 profile, Mac Pro6,1 profile, use nullcpupowermanagement.kext, uninstall audio kexts, using different audio patching, Agdpfix, uninstall nvidia drivers, updating bios to the latest f23b, recreate ssdt to my 6700k power management…) but no luck at all.

I´ve tried reinstalling El capitan from zero, but at the end I get the same results.

I´m using two monitors, one dp one dvi, but the problem persists with only one monitor too.

I´m kind of accustomed to the two or three boot processing, but I´d LOVE to be able to have a full funcional system, and to know WHY is it failing this way.

Any help or indication will be highly appreciated.

Thanks in advance.
 

Attachments

  • IMG_20170811_021229.jpg
    IMG_20170811_021229.jpg
    1.9 MB · Views: 214
  • IMG_20170811_112010.jpg
    IMG_20170811_112010.jpg
    1.8 MB · Views: 188
  • IMG_20170812_183938.jpg
    IMG_20170812_183938.jpg
    1.8 MB · Views: 187
Thanks Pilgrim.
Complete Efi folder, only Serial number deleted.
 

Attachments

  • EFI.zip
    2.3 MB · Views: 155
When you successfully boot, does the verbose boot show your CPU as being unsupported? If yes, have you considered using FakeCPUID in Clover?
 
When you successfully boot, does the verbose boot show your CPU as being unsupported? If yes, have you considered using FakeCPUID in Clover?

Thanks Going Bald, but everything seems to be ok in the verbose log (as fas as my knowledges go), and the system info is showing the apropiate data to my CPU:

0:103 0:000 === [ GetCPUProperties ] ==================================
0:103 0:000 CPU Vendor = 756E6547 Model=506E3
0:103 0:000 The CPU supported SSE4.1
0:103 0:000 The CPU supported turbo
0:103 0:000 BrandString = Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
0:103 0:000 TSC/CCC Information Leaf:
0:103 0:000 numerator : 334
0:103 0:000 denominator : 2
0:103 0:000 Calibrated ARTFrequency: 24003317
0:103 0:000 MSR 0xE2 before patch 00008000
0:103 0:000 MSR 0xE2 is locked, PM patches will be turned on
0:103 0:000 MSR 0xCE 00080838_F1012800
0:103 0:000 MSR 0x1A0 00850089
0:103 0:000 corrected FLEX_RATIO = E0000
0:103 0:000 FSBFrequency = 100 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz
0:103 0:000 MaxDiv/MinDiv: 40.0/8
0:103 0:000 Turbo: 40/40/40/42
0:103 0:000 Features: 0xBFEBFBFF
0:103 0:000 Threads: 8
0:103 0:000 Cores: 4
0:103 0:000 FSB: 100 MHz
0:103 0:000 CPU: 4000 MHz
0:103 0:000 TSC: 4000 MHz
0:103 0:000 PIS: 100 MHz
0:103 0:000 ExternalClock: 25 MHz


I´m also attaching a complete Clover bootlog, just in case i´m missing something.
 

Attachments

  • bootlog.log.txt
    29.9 KB · Views: 283
Thanks Pilgrim.
Complete Efi folder, only Serial number deleted.
Why are you booting with nv_disable=1 ?

Try this modified version of your config.plist :
 

Attachments

  • config.plist
    5.7 KB · Views: 289
Why are you booting with nv_disable=1 ?

Try this modified version of your config.plist :


Hello and thanks Pilgrim,
I´m booting with nv_disable=1 only to see the cpu caller panic message, because it usually just goes to black and reboot. I usually boot with nv_disable unchecked, as in the config.plist I uploaded.

I´m going to try your config.plist, what´s different from mine?

Thanks.
 
@studiocubico
New method to disable/enable web drivers for vNidia cards is to not use nv_disable, but to use the parameters argument NvidiaWeb = false/true like so:

<key>SystemParameters</key>
<dict>
<key>InjectKexts</key>
<string>Detect</string>
<key>InjectSystemID</key>
<true/>
<key>NvidiaWeb</key>
<true/>
</dict>

nv_disable=1 is used only as a temporary argument at boot to turn off the Mac OS nVidia driver if it causes a KP.
 
nv_disable=1 is used only as a temporary argument at boot to turn off the Mac OS nVidia driver if it causes a KP.

Yes, I´m aware of that (thanks anyway), so i´m using it as a temporary argument only to see what´s happenning and to be able to send you the pictures of the panic.

Usually nv_disable=1 it´s unchecked and only use NvidiaWeb=true, as in the config.plist I uploaded. Or i´m doing something wrong?
Thanks
 
Yes, I´m aware of that (thanks anyway), so i´m using it as a temporary argument only to see what´s happenning and to be able to send you the pictures of the panic.

Usually nv_disable=1 it´s unchecked and only use NvidiaWeb=true, as in the config.plist I uploaded. Or i´m doing something wrong?
Thanks
If the web driver is working why disable it to boot? Simple -v in the boot-args will show you what is happening during the boot.
There is no need to disable the GPU so far as I know. Are you getting a black screen during boot with the driver enabled?
 
Status
Not open for further replies.
Back
Top