Contribute
Register
Status
Not open for further replies.
So I need to manually add Clover folder in this ZIP?

The gen_debug.sh tool is supposed to get it automatically.
You should check the output before uploading and add any missing data manually.
If you find a bug in the gen_debug.sh tool, report the bug to the author.
 
The gen_debug.sh tool is supposed to get it automatically.
You should check the output before uploading and add any missing data manually.
If you find a bug in the gen_debug.sh tool, report the bug to the author.
Solving problem after installing a software^^. Problem reporting files reattach below.
 

Attachments

  • Problem reporting files.zip
    1.9 MB · Views: 80
Solving problem after installing a software^^. Problem reporting files reattach below.

Your ioreg shows you're using an invalid ig-platform-id (0x12345678).
The purpose of an invalid id is to disable the graphics drivers.
You have the expected result...

You must use a valid ig-platform-id if you expect IGPU graphics to work.

Your kextcache shows a patched kext:
Code:
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleIntelBDWGraphicsFramebuffer.kext

Restore to vanilla.
 
Your ioreg shows you're using an invalid ig-platform-id (0x12345678).
The purpose of an invalid id is to disable the graphics drivers.
You have the expected result...

You must use a valid ig-platform-id if you expect IGPU graphics to work.
Yes, I used that id because that's the only way I can boot up Sierra normally(without QE/CI). When I use id "16260006" I got glitches after second stage boot.
 
Your ioreg shows you're using an invalid ig-platform-id (0x12345678).
The purpose of an invalid id is to disable the graphics drivers.
You have the expected result...

You must use a valid ig-platform-id if you expect IGPU graphics to work.

Your kextcache shows a patched kext:
Code:
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleIntelBDWGraphicsFramebuffer.kext

Restore to vanilla.
But I'll try restore AppleIntelBDWGraphicsFramebuffer.kext to its origin way and boot again. Post result soon
 
Yes, I used that id because that's the only way I can boot up Sierra normally(without QE/CI). When I use id "16260006" I got glitches after second stage boot.

What do you mean by "glitches"?
 
What do you mean by "glitches"?
Reattach new problem reporting files after restoring appleIntelBDWGraphicsFramebuffer.kext to its original configuration. After that, I reboot the computer with id "0x16260006" but still get the screen as depict in the picture(Please forgive me if I am using the wrong word.Not native speaker..). Right now I'm using id "0x12345678" to boot into Sierra.
 

Attachments

  • Screen.JPG
    Screen.JPG
    2.2 MB · Views: 63
  • Problem report.zip
    1.8 MB · Views: 71
Reattach new problem reporting files after restoring appleIntelBDWGraphicsFramebuffer.kext to its original configuration. After that, I reboot the computer with id "0x16260006" but still get the screen as depict in the picture(Please forgive me if I am using the wrong word.Not native speaker..). Right now I'm using id "0x12345678" to boot into Sierra.

Did you enable legacy boot/CSM as per guide?
 
Status
Not open for further replies.
Back
Top