Alienware 17 R4 (kaby lake) installation problems

[vatsa131]

the text should stop scrolling to get a perfect photo.

But it stops at the end, which might be of no use.


If you cannot read it from above images, this is how it happens:

Waiting for DSMOS...
000003.731006 HSB1@14100000: AppleUSBHostPort::forcePowerGated: kPowerStateSleep completed with 0x00000000 after 1184ms
000003.979664 AW1517@14400000: IOUSBHostDevice::setConfigurationGated compliance violattion: failed to enable remote wake
pid 1 exited -- exit reason namespace2 subcode 0x8, description none
panic(cpu 0 caller 0xffffff800076b46f) initproc exited - exit reason namespace 2 subcode 0x8 description none
Debugger called: <panic>

uuid info:
0x10d3d2000 uuid = <322c06b7-8878-311d-888c-c8fd2ca96ff3>
0x1079ca000 uuid = <0ac314b8-c89c-3912-8bb7-e3f92c847169>

Thread 13 crashed

Then starts thread dump.

 

[RehabMan]

I cannot reproduce the KP I sent you above. I am getting this using both clover on usb3.0(with port limit patch) and usb2.0 & even using invalid ig-platform-id, but is still something related to usb.

Image is distorted but still text can be read when looking closely.

From your "Problem Reporting" files last attached, preboot.log in EFI/Clover/misc is too old (from July 31).
Please attach EFI/Clover as per FAQ, "Problem Reporting".

Make sure you're using an invalid ig-platform-id to avoid graphics issues (and take it out of the equation). You should set it in config.plist so you don't forget.

 

[vatsa131]

If you cannot read it from above images, this is how it happens:

Waiting for DSMOS...
000003.731006 HSB1@14100000: AppleUSBHostPort::forcePowerGated: kPowerStateSleep completed with 0x00000000 after 1184ms
000003.979664 AW1517@14400000: IOUSBHostDevice::setConfigurationGated compliance violattion: failed to enable remote wake
pid 1 exited -- exit reason namespace2 subcode 0x8, description none
panic(cpu 0 caller 0xffffff800076b46f) initproc exited - exit reason namespace 2 subcode 0x8 description none
Debugger called: <panic>

uuid info:
0x10d3d2000 uuid = <322c06b7-8878-311d-888c-c8fd2ca96ff3>
0x1079ca000 uuid = <0ac314b8-c89c-3912-8bb7-e3f92c847169>

Thread 13 crashed

Then starts thread dump.

 

[RehabMan]

...

The preboot.log and files in ACPI/origin in this ZIP are still dated July 31.

 

[vatsa131]

I didn't press F2. files Updated.

 

[RehabMan]

I didn't press F2. files Updated.

Things look fine here.
Problem might originate at a corrupt USB installer.
Are you creating the USB installer on an Apple Mac?

Otherwise out of ideas for you.

 

[vatsa131]

Are you creating the USB installer on an Apple Mac?

I dont have one, I used my Hackintoshed Dell Laptop.

 

[RehabMan]

I dont have one, I used my Hackintoshed Dell Laptop.

Does that Dell laptop have correctly configured USB?

 

[vatsa131]

Does that Dell laptop have correctly configured USB?

You need to create a custom SSDT for USBInjectAll.kext. You can find the guide linked from the FAQ.
I think it is to disable the EHCI controllers and use xHCI only, if possible.

I dont know, you suggested to make custom SSDT, but it seemed working just fine so I never cared.
Attaching Dell's clover and ioreg

Also this guy was having same problem and he managed to solve it. (Alienware 17 r4 & Alienware 15 r3 have almost same internals)
https://www.tonymacx86.com/threads/dell-alienware-15-r3.219685/

 

[RehabMan]

I dont know, you suggested to make custom SSDT, but it seemed working just fine so I never cared.
Attaching Dell's clover and ioreg

USB is not configured correctly.

Also this guy was having same problem and he managed to solve it. (Alienware 17 r4 & Alienware 15 r3 have almost same internals)
https://www.tonymacx86.com/threads/dell-alienware-15-r3.219685/

You and "this guy" might want to compare notes.