Contribute
Register

[SOLVED] Cannot boot 10.13

Status
Not open for further replies.
Joined
Apr 4, 2014
Messages
104
Motherboard
GA-Z87MX-D3H
CPU
i7-4770K
Graphics
Gigabyte GeForce GTX 780 OC
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. Android
Hi,

Since I've updated to high sierra I've problems of any some kind. For some time I could boot the system, everything worked ok, with the exception of sound and sleep.

Now I'm back to point 0. I can't boot. TO be honest I don't know what was changed since then, the only thing I've done differently was to install a game on a window disk (I've 2 ssd one for windows and other for osx) so I'm a bit sceptical that this could be the cause.

The same kernel panic I've now I've experienced this in the past but could get over it by reinstalling the system. I've tried the same but without success.

To list the things I've tried:

- toggle between some config.plist I've
- boot without GPU (physically removed)
- boot with nv_disable=1
- boot with -x
- check all BIOS settings
- reinstall the os (today I've done this 5 times, the second time I could boot, I logged in, saw a update to Nvidea drivers, updated but got again the kernel panic after boot for the first time). Since then I could not boot again
- rebuilding kernel cache (from the recover partition):
Code:
touch /Volumes/OSX/System/Library/Extensions && sudo kextcache -u /Volumes/OSX/
(I saw some errors on the output so I'm not sure if this completed correctly)

Right now I'm a bit in anger and frustrated since I'm quite sure that I've no clue of what am I doing.

I though that I could post the EFI/CLOVER folder, since all configuration goes there.

Hope some one could peak there and find what could I be doing wrong.

Many thanks
 

Attachments

  • CLOVER.zip
    15.9 MB · Views: 101
  • IMG_20180610_234518.jpg
    IMG_20180610_234518.jpg
    199.1 KB · Views: 123
Hope some one could peak there and find what could I be doing wrong.
I take it that you mean peek not peak ?

Take a peek yourself at your /EFI/CLOVER/kexts/ folder, the only one that should be populated is /EFI/CLOVER/kexts/Other/ and that only with kexts that are essential to the boot process. You have kexts in many of the /EFI/CLOVER/kexts/10.* folders which is wrong, you should delete all of the 10.* folders leaving only /EFI/CLOVER/kexts/Other/.

Try this edited version of your config.plist :
 

Attachments

  • config.plist
    7.9 KB · Views: 216
Thank you @P1LGRIM

Yes I meant peek :)

I thought that kexts should be inside the os version I'm trying to boot... I fixed that, so all folders are clean like you said, with the exception of other, were I left:

- FakeSMC
- Lilu

I've updated the Lilu to the latest version, just in case I was missing that.

Now with the config.plist I see more being logged, I've attached the log.

Many thanks!
 

Attachments

  • IMG_20180611_015430.jpg
    IMG_20180611_015430.jpg
    556.1 KB · Views: 109
I fixed that, so all folders are clean like you said, with the exception of other, were I left:

- FakeSMC
- Lilu

I've updated the Lilu to the latest version, just in case I was missing that.

Now with the config.plist I see more being logged, I've attached the log.
Not too much to go on there but I fancy that the problem may be related to the Lilu.kext.
Try either removing it or booting with -liluoff.
 
It's not about luck but more about the correct configuration.

I bet it is, but honestly for me is about to be lucky enough to have someone that can guide me through ;) since I've serious doubts of what I'm doing.

Access to the recovery partition requires FakeSMC.kext in /EFI/CLOVER/kexts/Other/.

I can confirm that I've that kext there. If I boot in recovery using the config.plist you provided it won't boot, using the config.plist I'd before it does.
 
If I boot in recovery using the config.plist you provided it won't boot, using the config.plist I'd before it does.
Then use the config.plist that works for you, not that I understand your desire to boot from the recovery partion at this stage.
 
Then use the config.plist that works for you, not that I understand your desire to boot from the recovery partion at this stage.

None of the configs boot the os.

I was adding info, most probably it not relevant.

And currently I've no ideas what I could try next.
 
Status
Not open for further replies.
Back
Top