Contribute
Register

[solved]MSI GE62 with i7-5700HQ CPU and HD5600 Graphic card, no QI/CE

Status
Not open for further replies.
lisizhe1987 said:
So you think the problem is DVMT?
but I set it to at least 64M, and with 0x16260006, I can not boot which is shown in the last post. #30
Click to expand...

Looks like maybe a CPU PM related panic. Did you implement native power management correctly?
 
RehabMan said:
Looks like maybe a CPU PM related panic. Did you implement native power management correctly?
Click to expand...

How to implement native power management correctly? I put Nullcuppowermanegement.kext in the kext folder of clover, but it seems no effect either.
In addition, if I boot with safe mode, it can boot successfully, and I have 1536M graphic memory, but no QE/CI. if I boot normally (verbose mode or without injected kext and cache), always have such panic.
 
lisizhe1987 said:
How to implement native power management correctly?
Click to expand...

http://www.tonymacx86.com/el-capita...01-guide-native-power-management-laptops.html

In addition, if I boot with safe mode, it can boot successfully, and I have 1536M graphic memory, but no QE/CI. if I boot normally (verbose mode or without injected kext and cache), always have such panic.
Click to expand...

QE and CI are separate things.

1536m gfx memory indicates CI is working.
Safe mode disables the kexts responsible for QE.
 
Hey, RehabMan,

Sorry to trouble you again.
After several unsuccessful attempts for driving my graphic card (HD5600) by injecting the appropriate ig-platform-id, I decided to switch to patch dsdt for the same purpose, but when I put my modified dsdt in the patched file of clover and tried to boot, there is a prohibition sign when booting.
Detailed pictures and EFI without themes were shown as below. (OS X10.11.3)

In addition, I would like to explain some settings:
1, AHCI mode is enable.
2, I also set HFS partition ID=48465300-0000-11AA-AA11-00306543ECAC.
3, Clover files was put in my EFI partition of HDD (not in USB disk).
4, The attempts of removing all kexts in Clover except FakeSMC.kext were invalid ,and totallyFixStillWaiting.kext was also of no effect.
5, Delete /System/Library/CoreServices/PlatformSupport.plist was also noneffective.

It would be very kind of you for solving this problem, I'm always learning and accumulate so much expericence of hackintosh from you.
Really gratefull for your helpful assistance.
 

Attachments

  • EFI without themes.rar
    3.1 MB · Views: 159
  • IMG_7062.jpg
    IMG_7062.jpg
    584 KB · Views: 171
  • IMG_7063.jpg
    IMG_7063.jpg
    1,000.8 KB · Views: 157
  • IMG_7064.jpg
    IMG_7064.jpg
    844.5 KB · Views: 184
lisizhe1987 said:
Hey, RehabMan,

Sorry to trouble you again.
After several unsuccessful attempts for driving my graphic card (HD5600) by injecting the appropriate ig-platform-id, I decided to switch to patch dsdt for the same purpose, but when I put my modified dsdt in the patched file of clover and tried to boot, there is a prohibition sign when booting.
Detailed pictures and EFI without themes were shown as below. (OS X10.11.3)

In addition, I would like to explain some settings:
1, AHCI mode is enable.
2, I also set HFS partition ID=48465300-0000-11AA-AA11-00306543ECAC.
3, Clover files was put in my EFI partition of HDD (not in USB disk).
4, The attempts of removing all kexts in Clover except FakeSMC.kext were invalid ,and totallyFixStillWaiting.kext was also of no effect.
5, Delete /System/Library/CoreServices/PlatformSupport.plist was also noneffective.

It would be very kind of you for solving this problem, I'm always learning and accumulate so much expericence of hackintosh from you.
Really gratefull for your helpful assistance.
Click to expand...

Since you neglected to press F4 in Clover, it is not possible to compare your patched DSDT.aml against native DSDT.aml in order to see what you changed.

Note: It is generally a mistake to combine config.plist/ACPI/DSDT/Fixes with a manually patched DSDT.aml.
 
RehabMan said:
Since you neglected to press F4 in Clover, it is not possible to compare your patched DSDT.aml against native DSDT.aml in order to see what you changed.

Note: It is generally a mistake to combine config.plist/ACPI/DSDT/Fixes with a manually patched DSDT.aml.
Click to expand...
I think you misunderstand my description, the attached dsdt is modified based on the native dsdt which is generated from Clover by pressing F4, and I fixed almost all mistakes and patched only graphic parts manually.

please have a look for my efi, thanks. Any suggestion are appreciated.
 
lisizhe1987 said:
I think you misunderstand my description, the attached dsdt is modified based on the native dsdt which is generated from Clover by pressing F4, and I fixed almost all mistakes and patched only graphic parts manually.
Click to expand...

But you did not provide the ACPI/origin files, so how am I to know what you changed from native?
 
RehabMan said:
But you did not provide the ACPI/origin files, so how am I to know what you changed from native?
Click to expand...
The attachment is origanl DSDT and SSDT.
Please check, thanks.
 

Attachments

  • ACPI-original.rar
    38.4 KB · Views: 112
lisizhe1987 said:
The attachment is origanl DSDT and SSDT.
Please check, thanks.
Click to expand...

The _DSM method you added to DSDT.aml at _SB.PCI0.GFX0._DSM conflicts with an existing OEM provided _DSM at the same path, defined in SSDT-9.dsl. It will cause SSDT-9 to be rejected by OS X.

Do not use the _T_x->T_x rename patch. It is not needed. Patches that aren't needed should not be applied.

This change is invalid:

original:
Code: 
                Method (_PS0, 0, Serialized)  // _PS0: Power State 0
                {
                    If (LEqual (DVID, 0xFFFF))
                    {
                        Return (Zero)
                    }

                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS0X))
                    {
                        PS0X ()
                    }
                }

                Method (_PS2, 0, Serialized)  // _PS2: Power State 2
                {
                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS2X))
                    {
                        PS2X ()
                    }
                }

                Method (_PS3, 0, Serialized)  // _PS3: Power State 3
                {
                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS3X))
                    {
                        PS3X ()
                    }
                }

To:
Code: 
                Method (_PS0, 0, Serialized)  // _PS0: Power State 0
                {
                    If (LEqual (DVID, 0xFFFF))
                    {
                        Return (Zero)
                    }

                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS0X))
                    {
                        Return (PS0X)
                    }
                }

                Method (_PS2, 0, Serialized)  // _PS2: Power State 2
                {
                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS2X))
                    {
                        Return (PS2X)
                    }
                }

                Method (_PS3, 0, Serialized)  // _PS3: Power State 3
                {
                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS3X))
                    {
                        Return (PS3X)
                    }
                }

Had you disassembled your files correctly in the first place, you wouldn't have found yourself modifying that code.

Why this change?
Code: 
            Method (_HRV, 0, NotSerialized)  // _HRV: Hardware Revision
            {
                Return (^^LPCB.CRID)
            }

To:
Code: 
            Method (HRV, 0, NotSerialized)
            {
                Return (^^LPCB.CRID)
            }

And... there are many more examples of unnecessary (and wrong) changes... so many that I stopped looking.

See guide for correct ACPI patching procedures: http://www.tonymacx86.com/el-capitan-laptop-support/152573-guide-patching-laptop-dsdt-ssdts.html
 
RehabMan said:
The _DSM method you added to DSDT.aml at _SB.PCI0.GFX0._DSM conflicts with an existing OEM provided _DSM at the same path, defined in SSDT-9.dsl. It will cause SSDT-9 to be rejected by OS X.

Do not use the _T_x->T_x rename patch. It is not needed. Patches that aren't needed should not be applied.

This change is invalid:

original:
Code: 
                Method (_PS0, 0, Serialized)  // _PS0: Power State 0
                {
                    If (LEqual (DVID, 0xFFFF))
                    {
                        Return (Zero)
                    }

                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS0X))
                    {
                        PS0X ()
                    }
                }

                Method (_PS2, 0, Serialized)  // _PS2: Power State 2
                {
                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS2X))
                    {
                        PS2X ()
                    }
                }

                Method (_PS3, 0, Serialized)  // _PS3: Power State 3
                {
                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS3X))
                    {
                        PS3X ()
                    }
                }

To:
Code: 
                Method (_PS0, 0, Serialized)  // _PS0: Power State 0
                {
                    If (LEqual (DVID, 0xFFFF))
                    {
                        Return (Zero)
                    }

                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS0X))
                    {
                        Return (PS0X)
                    }
                }

                Method (_PS2, 0, Serialized)  // _PS2: Power State 2
                {
                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS2X))
                    {
                        Return (PS2X)
                    }
                }

                Method (_PS3, 0, Serialized)  // _PS3: Power State 3
                {
                    If (CondRefOf (\_SB.PCI0.XHC.RHUB.PS3X))
                    {
                        Return (PS3X)
                    }
                }

Had you disassembled your files correctly in the first place, you wouldn't have found yourself modifying that code.

Why this change?
Code: 
            Method (_HRV, 0, NotSerialized)  // _HRV: Hardware Revision
            {
                Return (^^LPCB.CRID)
            }

To:
Code: 
            Method (HRV, 0, NotSerialized)
            {
                Return (^^LPCB.CRID)
            }

And... there are many more examples of unnecessary (and wrong) changes... so many that I stopped looking.

See guide for correct ACPI patching procedures: http://www.tonymacx86.com/el-capitan-laptop-support/152573-guide-patching-laptop-dsdt-ssdts.html
Click to expand...

thank you very much for your remind, I will carefully read the thread and fix again.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top