Contribute
Register

Installing High Sierra on Alienware 15 R3

Status
Not open for further replies.
Did you do the install with VESA drivers, or did you get it to work with the KBL graphics drivers?

Note also...Keep in mind booting without proper graphics drivers is not quick.

I installed by using everything that was included in your guide for laptops. I'm guessing it was the VESA drivers.
 
I installed by using everything that was included in your guide for laptops. I'm guessing it was the VESA drivers.

If you followed my guide, then you used the KBL drivers with config_HD615_620_630_640_650.plist, unless you used an invalid ig-platform-id.

My advice: Don't guess... keep track of what you're doing/what works/what doesn't.
 
If you followed my guide, then you used the KBL drivers with config_HD615_620_630_640_650.plist, unless you used an invalid ig-platform-id.

I must have used KBL drivers then because I only changed the ig-platform-id after installation.
 
I must have used KBL drivers then because I only changed the ig-platform-id after installation.

Verify that is the case by booting into the installer again.
You can collect ioreg by running IORegistryExplorer.app from Terminal:
Code:
/path-to-where-IORegistryExplorer.app-is/IORegistryExplorer.app/Contents/MacOS/IORegistryExplorer
 
Last edited:
Verify that is the case by booting into the installer again.
You can collect ioreg by running IORegistryExplorer.app from Terminal:
Code:
open /path-to-where-IORegistryExplorer.app-is/IORegistryExplorer.app/Contents/MacOS/IORegistryExplorer

Wouldn't that not show which drivers I am using due to how I changed the platform id
Also, do I do that in the installer?
 
Last edited:
Wouldn't that not show which drivers I am using due to how I changed the platform id
Also, do I do that in the installer?

You will be able to save an ioreg from the macOS installer and attach it.
Yes, of course... you do it from the installer (you can run Terminal from within the installer... Terminal is on the Utilities menu).
That way we can verify your assertion that you had the framebuffer kexts working in the installer.

You will need to put IORegistryExplorer.app on the USB you're using for the installer.
 
You will be able to save an ioreg from the macOS installer and attach it.
Yes, of course... you do it from the installer (you can run Terminal from within the installer... Terminal is on the Utilities menu).
That way we can verify your assertion that you had the framebuffer kexts working in the installer.

You will need to put IORegistryExplorer.app on the USB you're using for the installer.

I can't get into the installer now, should I remake the usb to make it the same way I installed.
 
yes, of course (you should have kept it).

I remade the USB Installer and now I can't even get into the installer anymore. I end up here. I tried booting with FakeID changed for Intel graphics and platform-id changed to 0x12345678 one at a time.
 

Attachments

  • CLOVER.zip
    1.6 MB · Views: 54
  • 20171204_202152.jpg
    20171204_202152.jpg
    3.6 MB · Views: 65
I remade the USB Installer and now I can't even get into the installer anymore. I end up here. I tried booting with FakeID changed for Intel graphics and platform-id changed to 0x12345678 one at a time.

Your SSDT-DiscreteSpoof.aml is completely wrong.
It is an (almost) an attempt to spoof the integrated graphics device at _SB.PCI0.GFX0!
If that was something you'd want to do (it isn't), should have been coded as _SB.PCI0.GFX0._DSM.

But had it been coded with ._DSM, it would have no effect, because config.plist is renaming GFX0->IGPU, and as as result the _SB.PCI0.GFX0 path does not even exist. macOS ACPI runtime would have just ignored the file.

The discrete (Nvidia) device is at _SB.PCI0.PEG0.PEGP.
SSDT-DiscreteSpoof.dsl, therefore, should be coded:
Code:
// save as SSDT-DiscreteSpoof.aml
DefinitionBlock ("", "SSDT", 2, "hack", "spoof", 0)
{
    Method(_SB.PCI0.PEG0.PEGP._DSM, 4)
    {
        If (!Arg2) { Return (Buffer() { 0x03 } ) }
        Return (Package()
        {
            "name", Buffer() { "#display" },
            "IOName", "#display",
            "class-code", Buffer() { 0xFF, 0xFF, 0xFF, 0xFF },
        })
    }
}

Note: It is _exactly_ like the example in the guide:
https://www.tonymacx86.com/threads/...-only-ran-for-0-seconds-with-dual-gpu.233092/

After you correct the SSDT-DiscreteSpoof.aml, try again.

If it is not working, try using an invalid ig-platform-id (to keep native KBL kexts from loading).
Or try using Skylake spoofing (different config.plist... don't forget to enable the _DSM->XDSM patch).

On top of all that... you have no kexts in Clover/kexts/Other!
No chance of booting macOS without FakeSMC.kext. And you will likely need other kexts as recommended in the guide.
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/
 
Status
Not open for further replies.
Back
Top