Contribute
Register

[Guide] HP Elite 8300 & 6300 Pro (all form factors) using Clover UEFI hotpatch

Status
Not open for further replies.
Thank you @nguyendj and @trs96
HD2500 worked, I am surprised.
HD2500.png

Just make the following changes from "Config_HD2500.plist".
AAPL,ig-platform-id = 0x0166000A
device-id = 0x1061

Edit:device-id = 0x0161
The setting of AAPL, ig-platform-id was deleted because it is unnecessary.


Code:
           <key>PciRoot(0)/Pci(0x02,0)</key>
            <dict>
                <key>device-id</key>
                <data>YQEAAA==</data>
            </dict>

Append:
Please read # 659 which warns you that @itwas is a dangerous usage.
If you have experience with Windows, you probably don't want to use it with MacOS,
but you should avoid using it all the time.
 
Last edited:
It's best to use HD4000 instead of using HD2500. HD4000 has full support. Some of the CPUs with HD4000 don't really cost any more than ones with HD2500. The choice is easy. Buy a used/refurbished Intel i3-3225 and install it. Problem solved.
Thanks, I will try to find these CPUs
 
Finally I fixed my sleep issue! Upgraded to the latest version of Clover, and "upgraded" to Sniki's latest repo of kexts, removed the old versions (and FakeSMC), then went with the ssdt method of power management, and all is functional in Mojave. So happy with this system thus far, first with High Sierra, and now Mojave.

One question - I assume by using ssdtPRGen to create an SSDT.aml, that file should replace the SSDT-HP.aml from the repo? That's what I did, and on first boot I don't see issues, so I'm under the impression that the SSDT-HP isn't needed in the /EFI/CLOVER/ACPI/patched/ folder.
 
Thank you @nguyendj and @trs96
HD2500 worked, I am surprised.View attachment 430665
Just make the following changes from "Config_HD2500.plist".
AAPL,ig-platform-id = 0x0166000A
device-id = 0x1061

Code:
           <key>PciRoot(0)/Pci(0x02,0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>CgBmAQ==</data>
                <key>device-id</key>
                <data>YQEAAA==</data>
            </dict>

device-id 0x1061:8086 seems to be Ethernet Controller, your system overview also shows that the VRAM is 7MB, I wonder this setting is really working, randomly input something just disable loading the graphics device driver, you may check this is the IO registery.

the valid ivy bridge IGPU device-id should be (0x01528086, 0x01568086, 0x01628086, 0x01668086, 0x016A8086)

Screen Shot 2019-10-17 at 19.52.31.png
 
device-id 0x1061:8086 seems to be Ethernet Controller, your system overview also shows that the VRAM is 7MB, I wonder this setting is really working, randomly input something just disable loading the graphics device driver, you may check this is the IO registery.
@itwas Thank you very much.
Only the display on the screen is checked and other functions are not checked.
Since it is not possible to immediately verify the operation for the equipment currently in use, we will reply after confirming the time later.


There is no need to check the operation, and the description was wrong.
It works with the posted CODE.

device-id = 0x1061
device-id = 0x0161
 
Last edited:
the valid ivy bridge IGPU device-id should be (0x01528086, 0x01568086, 0x01628086, 0x01668086, 0x016A8086)
Currently, the GT640 is removed with the setting of 0x0161, and the operation test is underway.
At 0x0152, the screen is black with only cursor display.
HD2500.png
 
Currently, the GT640 is removed with the setting of 0x0161, and the operation test is underway.
At 0x0152, the screen is black with only cursor display.
View attachment 431312

again, device-id 0x0161 is invalid, no such Intel Ivy Bridge Graphics Device, you can't create something don't exist

That's why Hackintool can't look up what is this device -> 0x01618086, return the result "Intel ???"

Integrated GPU HD2500 must be working with a discrete GPU in macOS
macOS do not support HD2500 in normal mode

the graphics driver don't understand what is 0x0161

iMac13,2 use these CPU
Intel Core i5 (3470S) - 6M Cache, up to 2.90 GHz - 3.60 GHz, 65 W, Intel HD Graphics 2500 (0x152)
Intel Core i5 (3470) - 6M Cache, up to 3.20 GHz - 3.60 GHz, 77 W, Intel HD Graphics 2500 (0x152)
Intel Core i7 (3770) - 8M Cache, up to 3.40 GHz - 3.90 GHz, 65 W, Intel HD Graphics 2500 (0x162)
iMac13,1
Intel Core i5 (3225) - 3M Cache, 3.30 GHz, 55 W, Intel HD Graphics 4000 (0x152)
Intel Core i5 (3330S) - 6M Cache, up to 2.70 GHz - 3.60 GHz, 65 W, Intel HD Graphics 2500 (0x152)
Intel Core i5 (3470S) - 6M Cache, up to 2.90 GHz - 3.60 GHz, 65 W, Intel HD Graphics 2500 (0x152)
Intel Core i7 (3770S) - 8M Cache, up to 3.10 GHz - 3.90 GHz, 65 W, Intel HD Graphics 4000 (0x162)
 
again, device-id 0x0161 is invalid, no such Intel Ivy Bridge Graphics Device, you can't create something don't exist

That's why Hackintool can't look up what is this device -> 0x01618086, return the result "Intel ???"

Integrated GPU HD2500 must be working with a discrete GPU in macOS
macOS do not support HD2500 in normal mode

the graphics driver don't understand what is 0x0161
@itwas I don't know the intention of the story, but no one wants to use this feature.
If you use it when necessary, you can understand that it is a function whose operation cannot be guaranteed.

I would like to leave the use of the danger at your own risk to the free will of the person who uses it.
 
My Mojave install was running great, until I installed 10.14.5 via Software Update. For some reason it was suggesting .5 rather than .6; on my Macbook which was updated with 10.14.0 it suggested 14.6, so something was odd here. Well the system broke after that update and it won't boot. I'm paring it back to the bare minimum for booting, and starting over with Clover, as it seems the issue is USB-related with numerous USB overcurrent errors, which is where the boot stops functioning. There were duplicate entries in the EFI drivers section, as Clover moved to /UEFI and /drivers from /drivers64UEFI and /drivers64.

Update: I cleared everything from EFI and reinstalled an earlier version r4988. The folder structure is similar to the r5000+ versions, but this fixed my issues, which I believe were Clover-related in some way. I restored from backup, and it still wouldn't boot with 10.14.4, so made the EFI changes, installed r4988, and it booted without errors. Then I proceeeded to upgrade to .14.5, and .14.6, and all seems fine.

Sidenote: my CCC backup when I was at v 14.0 booted no problem. I cloned 14.3 to it, and hadn't tried to boot it, figuring it was fine. Well, the drive had not been upgraded to APFS, which I forgot..... so the install isn't recognized and can't be booted by Clover. It cloned over no problem to my main drive, which is APFS so I was able to boot that. Make sure that you upgrade your backup drive to APFS before cloning from CCC and trusting a backup later than 14.2, it seems that APFS is required.

Question: following @Sniki's guide exactly, all of the kexts are duplicated from /EFI and /Library/Extensions. From what I've read here, this doesn't appear to be good practice. It is better to have just what is needed to boot/restore, etc., in EFI, and keep the rest in /L/E
I'm wondering what are the bare minimum .kext files needed in /EFI/CLOVER/kexts/other for these HP 8300 builds?
 
Last edited:
First, I'd like to thank Sniki for this guide and all the helpful moderators and experts.

I followed the guide exactly, installed Mojave 10.14.6 and all possible updates until none left as of this posting.
The system specs should be on my profile but its:
HP Elite 8300 USDT
i7 3770s CPU
HD4000 GPU
8GB RAM
120GB SSD
USB Keyboard and Mouse
Displayport to VGA adaptor running a 17" LCD at 1280 x 1024

For the most part, everything works ok except:
- Once in a while the graphics drivers do not load, I know when it doesn't load when the dock isn't translucent and tabs on Safari are black.
- Some pages in Safari freezes the whole computer.

If anyone has a similar setup but do not have any of the issues, I'd like to know. I'm sort of new at hackintoshes so I'm not quite sure if this is normal behavior.
 
Status
Not open for further replies.
Back
Top