Contribute
Register

How to enable 'Kaby Lake' Intel 6xx Graphics (10.12.6+)

Status
Not open for further replies.
Well, it's seems to be fixer by usine SMBIOS 18.3

Does anyone have HD630 only wake/sleep working ?

Hey, can you share what you did to "fix" it? Whenever I switch to the things to get me 4k, I end up with the flicker. It may be an hour into it, but the machine is unusable when it gets into that mode.

Ultimately, I want to know what fixed THIS for you:

But few seconds or minutes later, part of the screen starts to flicker, like a vraom or framebuffer issue.

i tried several DVMT setting in bios, it doesnt help (i trie 128M, 1024M for prealloc § and 128,256, MAX for DVMT ram)

Doe anyone have already see that flickering issue after a moment ?​
 
No idea what you mean by "no luck".
Need detailed description of the problem and problem reporting files.
No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the tool mentioned in the FAQ, that way it is less likely you'll omit something.
No idea what you mean by "no luck".
Need detailed description of the problem and problem reporting files.
No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the tool mentioned in the FAQ, that way it is less likely you'll omit something.


I used the tool. The zip is included. Thanks for the tip.

Sound, BT, USB, seems to work just fine

The problem is that I get no graphic hardware acceleration.
VRAM (Total): 5 MB when using 1600x900 (many glitches but usable)
VRAM (Total): 31 MB when using 1080 or 3840 (extremely slow)

If I boot with the incorrect device_id (ie. 12345678) boots fine, graphics are slow
If I boot with the correct device_id 0x59120000 (and GFX 0x59128086) I get a kernel panic.

Suspect was a DVMT problem so tried using the alternative to the minstolen patch (as shown in the attach config.list) following the instructions in the guide.

I used:
find:00030303 00006002 00000000
replace with:00030303 00005001 00009000

The machine boots, but the screen TV HDMI shows: unsupported mode
If I try that on VGA the monitor shows no signal.

Sound, BT, USB, seems to work just fine
 

Attachments

  • debug_28977.zip
    2.6 MB · Views: 61
I used the tool. The zip is included. Thanks for the tip.

Sound, BT, USB, seems to work just fine

The problem is that I get no graphic hardware acceleration.
VRAM (Total): 5 MB when using 1600x900 (many glitches but usable)
VRAM (Total): 31 MB when using 1080 or 3840 (extremely slow)

If I boot with the incorrect device_id (ie. 12345678) boots fine, graphics are slow
If I boot with the correct device_id 0x59120000 (and GFX 0x59128086) I get a kernel panic.

Suspect was a DVMT problem so tried using the alternative to the minstolen patch (as shown in the attach config.list) following the instructions in the guide.

I used:
find:00030303 00006002 00000000
replace with:00030303 00005001 00009000

The machine boots, but the screen TV HDMI shows: unsupported mode
If I try that on VGA the monitor shows no signal.

Sound, BT, USB, seems to work just fine

If you're using "config safe 12345678.plist", you're doing it wrong...
Must never use invalid FakeID.
Only invalid ig-platform-id.

Proper procedure:
never use "config safe 12345678.plist". It is wrong and not helpful.
Use only the config.plist you have.
When you want to boot with an invalid ig-platform-id, change it in the Clover GUI->Options->Graphics Injector. DO NOT change the FakeID!
Then rebuild cache:
Code:
sudo kextcache -i /

That gets the graphics kext into cache, where you can expect Clover to patch it (if the patch is valid/working). Then you can boot normally (with valid ig-platform-id), and expect that Clover can patch the kext as it is in cache.

Using an invalid FakeID throws the kext out of cache, and you can't expect Clover to patch something that is not in cache.

If still not working, then that particular ig-platform-id is not patchable (or you have some other problem) and you should probably try an ig-platform-id that has a concrete value for framebuffer size/cursor bytes (there aren't many).
 
If you're using "config safe 12345678.plist", you're doing it wrong...
Must never use invalid FakeID.
Only invalid ig-platform-id.

Proper procedure:
never use "config safe 12345678.plist". It is wrong and not helpful.
Use only the config.plist you have.
When you want to boot with an invalid ig-platform-id, change it in the Clover GUI->Options->Graphics Injector. DO NOT change the FakeID!
Then rebuild cache:
Code:
sudo kextcache -i /

That gets the graphics kext into cache, where you can expect Clover to patch it (if the patch is valid/working). Then you can boot normally (with valid ig-platform-id), and expect that Clover can patch the kext as it is in cache.

Using an invalid FakeID throws the kext out of cache, and you can't expect Clover to patch something that is not in cache.

If still not working, then that particular ig-platform-id is not patchable (or you have some other problem) and you should probably try an ig-platform-id that has a concrete value for framebuffer size/cursor bytes (there aren't many).


Got rid of all other .plist's.

I have just one question in order to send you a good problem report.

How do I boot with the parameters that end up with a black screen (not usable) and then reboot with an invalid device id (12345678) in order to make the machine usable, without messing the boot log? Because when i do this I can see the boot log in the report stating the last boot (with the invalid device id) which I guess is not the one needed.
 
Hey, can you share what you did to "fix" it? Whenever I switch to the things to get me 4k, I end up with the flicker. It may be an hour into it, but the machine is unusable when it gets into that mode.

Ultimately, I want to know what fixed THIS for you:

But few seconds or minutes later, part of the screen starts to flicker, like a vraom or framebuffer issue.

i tried several DVMT setting in bios, it doesnt help (i trie 128M, 1024M for prealloc § and 128,256, MAX for DVMT ram)

Doe anyone have already see that flickering issue after a moment ?​


When with smbios imac 18.2 i had glitches (tears and flickering), when 18.3 it works flawslessly at 4K@60hz :)

Remaining issue : sleep
 
Got rid of all other .plist's.

I have just one question in order to send you a good problem report.

How do I boot with the parameters that end up with a black screen (not usable) and then reboot with an invalid device id (12345678) in order to make the machine usable, without messing the boot log? Because when i do this I can see the boot log in the report stating the last boot (with the invalid device id) which I guess is not the one needed.

You can collect full problem reporting files by using an invalid ig-platform-id.
Then boot with correct ig-platform-id to collect verbose boot/panic photo.
 
Hello

i've got a Gibagyte Z270X Gaming 5 with HD630 on 7700k with displayport

I managed to boot up at 4K with 60hz on 10.13.2

But few seconds or minutes later, part of the screen starts to flicker, like a vraom or framebuffer issue.

i tried several DVMT setting in bios, it doesnt help (i trie 128M, 1024M for prealloc § and 128,256, MAX for DVMT ram)

Doe anyone have already see that flickering issue after a moment ?

Hey epalzeo! What are your settings that work?

I have iMac 18,3. I'm just wondering what OTHER settings you have. Reminder, this is what I'm currently trying:

First, here are the my current important settings:
  • -disablegfxfirmware
  • change GFX0 to IGPU
  • IntelGFX id: 0x59128086
  • Inject Intel
  • ig-platform-id: 0x59120000
  • FaceCPUID: 0x0506E3
  • SMBIOS: iMac18,3
  • FakePIID.kext, IntelGraphicsDVMTFixup.kext, IntelGraphicsFixup.kext, Lilu.kext
SO, before I had these settings I had the other IntelGFX id: 0x19168086
 
Hello same config, except, no FakePIID.kext, IntelGraphicsDVMTFixup.kext
 
Status
Not open for further replies.
Back
Top