HP Elitebook 1040 g3 i7 boot problem

RehabMan said:

Your copy of the github project is not up-to-date.

Click to expand...

Yes, I figured that out, and was about to tell you how stupid I am Thank you so much!
Now, as you will see I finished the guide and most of the things work now.

What works

- UEFI booting via Clover
- built-in keyboard (with special function keys)
- native audio with AppleHDA, including headphone
- built-in mic
- built-in camera
- native power management
- battery status
- backlight controls with smooth transitions, save/restore across restart
- wired Ethernet
- Mac App Store working

Not sure:
- accelerated graphics - how can I test this?

Not working:

Suddenly some things that worked before stopped working:

- built-in trackpad
- USB on the docking station. USB ports on the laptop work fine, but on the docking station they stopped.
- bluetooth. - it worked before.

Not working (before and after):

- WiFi
- Messages/FaceTime (I guess after I obtain a WIFI hardware it will work)

Could you please give me an advice about not working stuff. Again, I attach the flies/outputs. Thanks again.

better said:

- built-in trackpad

Click to expand...

Your trackpad is ALPS. Guide assumes Synaptics.
(it is possible/likely that some models come with Synaptics, some with ALPS).
You need different PS2 kexts, or a different configuration in the model specific SSDT.
Look at SSDT-1030-G1-Skylake.dsl for details (Mouse device needs to not be disabled).
I should probably do a bit of cleanup in there related to the VoodooPS2Mouse disable.

- USB on the docking station. USB ports on the laptop work fine, but on the docking station they stopped.

Click to expand...

USB customization issue. It is likely the USB customization data provided earlier was done without a docking station connected.
Read guide "USB customization", and submit the required ioreg.

- bluetooth. - it worked before.
- WiFi

Click to expand...

You must install compatible hardware.

- Messages/FaceTime (I guess after I obtain a WIFI hardware it will work)

Click to expand...

iMessage guide is linked from the ProBook guide.

RehabMan said:

Your trackpad is ALPS. Guide assumes Synaptics.
(it is possible/likely that some models come with Synaptics, some with ALPS).
You need different PS2 kexts, or a different configuration in the model specific SSDT.
Look at SSDT-1030-G1-Skylake.dsl for details (Mouse device needs to not be disabled).
I should probably do a bit of cleanup in there related to the VoodooPS2Mouse disable.



USB customization issue. It is likely the USB customization data provided earlier was done without a docking station connected.
Read guide "USB customization", and submit the required ioreg.

Click to expand...

OK, I managed to fix almost all issues. I found out, that when disabling USBInjectAll.kext in Library/Extension all USB ports work.
Trackpad works now, but only basic gestures. I would be happy if I can at least scroll with two fingers.

The issue that bothers me more is the secondary monitor. The secondary monitor works fine during the installation and following all the steps from the hot patch guide, but when I replace the config.plist with the final one - config_1040_G3_Skylake.plist and restart the system, the secondary monitor stops working. When I put back the previous config.plist the monitor works, but not the patches. I'm attaching all files/outputs again. Thanks in advance.

better said:

OK, I managed to fix almost all issues. I found out, that when disabling USBInjectAll.kext in Library/Extension all USB ports work.
Trackpad works now, but only basic gestures. I would be happy if I can at least scroll with two fingers.

The issue that bothers me more is the secondary monitor. The secondary monitor works fine during the installation and following all the steps from the hot patch guide, but when I replace the config.plist with the final one - config_1040_G3_Skylake.plist and restart the system, the secondary monitor stops working. When I put back the previous config.plist the monitor works, but not the patches. I'm attaching all files/outputs again. Thanks in advance.

Click to expand...

"Problem Reporting" files are incomplete.
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.

Note: The guide uses a custom SSDT to configure the ports for USBInjectAll.kext.
If you wish to add data to the SSDT, you must go through the procedures I mentioned earlier ("USB customization").
Please reply with the ioreg from that "USB customization" step.

RehabMan said:

"Problem Reporting" files are incomplete.
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.

Note: The guide uses a custom SSDT to configure the ports for USBInjectAll.kext.
If you wish to add data to the SSDT, you must go through the procedures I mentioned earlier ("USB customization").
Please reply with the ioreg from that "USB customization" step.

Click to expand...

Sorry, I forgot the EFI/Clover folder. Here it is.

I will go trough hat "USB customization" step later hopefully. I will be thankful if you would help me with the secondary monitor issue now. Thanks again.

better said:

Sorry, I forgot the EFI/Clover folder. Here it is.

I will go trough hat "USB customization" step later hopefully. I will be thankful if you would help me with the secondary monitor issue now. Thanks again.

Click to expand...

You will need to provide full "Problem Reporting" files for each of the two scenarios (external working, external not working). Because otherwise, I cannot know the differences between your two configurations.

Use the tool mentioned in the FAQ to collect the data.

In case it is not obvious, the ioreg collected should be captured with the external monitor connected.

RehabMan said:

You will need to provide full "Problem Reporting" files for each of the two scenarios (external working, external not working). Because otherwise, I cannot know the differences between your two configurations.

Use the tool mentioned in the FAQ to collect the data.

In case it is not obvious, the ioreg collected should be captured with the external monitor connected.

Click to expand...

OK, here are both files. In both cases the external monitor was connected.

better said:

OK, here are both files. In both cases the external monitor was connected.

Click to expand...

Might be SMBIOS choice.
MacBookPro13,3 is a poor choice.
Working case is using MacBookPro11,1.

Could also be framebuffer patches.
You can disable them from the Clover options and see what happens... but I really suspect the SMBIOS to be the problem.

RehabMan said:

Might be SMBIOS choice.
MacBookPro13,3 is a poor choice.
Working case is using MacBookPro11,1.

Could also be framebuffer patches.
You can disable them from the Clover options and see what happens... but I really suspect the SMBIOS to be the problem.

Click to expand...

This was a brilliant guess! MacBookPro11,1 works perfect. Thank you so much!!!
But what I saw just now:
When I close the lid and open it again, the internal monitor stays black. The external on the other hand works fine, I can see the mouse moving. Attached last debug report.

better said:

This was a brilliant guess! MacBookPro11,1 works perfect. Thank you so much!!!
But what I saw just now:
When I close the lid and open it again, the internal monitor stays black. The external on the other hand works fine, I can see the mouse moving. Attached last debug report.

Click to expand...

Read here regarding patched EDID in display override file:
https://www.tonymacx86.com/threads/readme-common-problems-in-10-13-high-sierra.233582/