Contribute
Register

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

Status
Not open for further replies.
Yes, those Quadro K600s are really a great value for budget Catalina graphics. Now that 4K monitors are lower in price it makes 4K easier to implement. With the high resolution Catalina Wallpapers that must be great to look at on that monitor. What differences have you noticed by moving all kexts to the other folder ? Smoother boot ups ? Better graphics performance etc.

A friend paid for some work with a monitor so getting something that's budget and works is good, plus LP AMD options are unobtainium in Aus. Wow, so much detail, the Mojave sand dunes are simply stunning!

With the kexts, I did a whole bunch of stuff at the same time like learning and fixing my EFI folder so it was hard to measure. I'm still running the original Clover_v2.4k_r4972 :D

But, start-ups are quick, it's just under 30 seconds from pushing the power button to login screen completely hands-off. It's solid as a rock and everything has installed fine. Minor and major updates, Webroot, Adobe CC, fonts, etc. It all just works. Wifi, BT, iMessage and handover stuff also works fine with the Fenvi FV-HB1200. To be fair, I might not have picked up a latent problem yet, but for everyday stuff, it's great.
 
Last edited:
Created my USB with Mojave on it (want to upgrade from Sierra) and this the Clover install screen:
1.jpg


Once I click on the install, this screen appears and stays static - any troubleshooting ideas?
2.jpg


created the USB drive via the RehabMan instructions on page 1 of this topic using "HFS+J" with "GPT Partition Table"

followed step 5 clover custom settings

completed these:

Into EFI/Clover/ACPI/Patched, add the SSDT-EC.aml from my repo
Into EFI/Clover/Drivers/UEFI, make sure to add HFSPlus.efi (click on it to download it)
Into EFI/Clover/Drivers/UEFI, make sure to add VirtualSMC.efi (included on the downloaded zip of VirtualSMC)
Into EFI/Clover/kexts/Other, make sure to add the following kexts listed down below:

Lilu.kext
VirtualSMC.kext
SMCProcessor.kext

WhateverGreen.kext
AppleALC.kext
IntelMausi.kext
USBPorts.kext (included on the HP8300-HP6300 Github Project zip with the rest of the other files)

Used Clover V2.5 r5103
 
Last edited:
I have an 8300 with an i7-3770. Is the macmini6,1 still the best SMBIOS choice for me, or should I stick with iMac13,2? What if I want to add a Radeon RX580 and want full HEVC hardware acceleration — macmini6,1 or imac13,2 or imacpro1,1?

Thanks for the great guide!

Edit: It looks like if I choose imacpro1,1 and then inject imac13,2 frequency vectors via CPUFriend.kext I can get full hardware acceleration and proper CPU power management. Any downsides to this approach?
 
Last edited:
Once I click on the install, this screen appears and stays static - any troubleshooting ideas?
Try booting verbose so you get some specific info on why it stops loading at that point. You can post a picture here of the point on your screen where it stops.
 
I have an 8300 with an i7-3770. Is the macmini6,1 still the best SMBIOS choice for me, or should I stick with iMac13,2? What if I want to add a Radeon RX580 and want full HEVC hardware acceleration — macmini6,1 or imac13,2 or imacpro1,1?

Thanks for the great guide!

Edit: It looks like if I choose imacpro1,1 and then inject imac13,2 frequency vectors via CPUFriend.kext I can get full hardware acceleration and proper CPU power management. Any downsides to this approach?

@Lonelytanker,

I don't have an i7-3770, so I can't give a very educated opinion if you want to
run your machine without a graphics card. This guide works out a lot of the issues
for a Macmini6,1 in that mode, and its not clear how an iMac13,2 as recommended
by the @trs96 guides would compare. Sniki has settings for better HD4000 graphics in
the device properties and boot arguments of his sample config.plist.

Generally, it seems an iMac13,2 SMBIOS might be preferred if you are using an
Nvidia card, since they came with Nvidia graphics originally, and because you might
have Nivdia dGPU power management pre-configured. See Toleda's native dGPU power
management guide.

I think you only get HEVC hardware acceleration with an iMacPro1,1 or MacPro7,1 SMBIOS.
MacPro7,1 issues memory configuration error messages, although it seems to work ok.
Generally it seems the preferred mode for HEVC is with IGPU disabled. See shuhung's
Standalone RXXX guide for details, and he is the one who asserts the limitation on HEVC model
numbers.

To me its not clear what I get out of using CPUfriend. An older version of ssdtPRGen.sh complained
if you used an iMacPro1,1 SMBIOS with an Ivy processor, but the new version produces the
same file, without complaint with SMBIOS set to iMacPro1,1 whether you use the command

./ssdtPRGen.sh -b Mac-FC02E91DDD3FA6A4 -target 1 -t 77

or the command

./ssdtPRGen.sh -target 1 -t 77 -x 1.

It could be that I simply don't know how to use CPUfriend correctly, but these PRGen power management
ssdt's already give the minimum 1600 to the maximum turbo of 3600 (i5-3470) or 3800 (i5-3570).
I don't think you can get HWP working on the Ivy processors. If you get any CPUfriend benefits, please
let us know what to look for and how to accomplish it.

Another question you may encounter is setting up native power management for your RX580 with
iMacPro1,1. I'm using a modified dGPM.kext from Toleda with an added iMacPro1,1 IOkitpersonality
for my RX560 card. I'm not sure how much I'm getting out of it, but I can see Sony Food Fizzle cranking
up from an idle consumption of about 20W to 67W playing HEVC file Sony Food Fizzle.

You may want to use VideoProc cautiously, because it does not always give accurate reports whether
HEVC is working correctly. However, VideoProc gives higher (4K) resolution scores for me with an
iMacPro1,1 SMBIOS than for a MacMini or iMac13,2 profile in H264, and also 4K for HEVC.

Hope this helps,
Lisa
 
...created the USB drive via the RehabMan instructions on page 1 of this topic using "HFS+J" with "GPT Partition Table"
...Used Clover V2.5 r5103

Are you plugging the USB stick into a USB2 port? Icon is SS so I'm assuming USB3?

You've got multiple disks showing with MacOS and recovery so I'm assuming you've got an old system already installed? It's best to do a clean install of the OS. You may be erasing once in the installer of course.

Hope that helps!
 
I have an 8300 with an i7-3770. Is the macmini6,1 still the best SMBIOS choice for me, or should I stick with iMac13,2? What if I want to add a Radeon RX580 and want full HEVC hardware acceleration — macmini6,1 or imac13,2 or imacpro1,1?

Thanks for the great guide!

Edit: It looks like if I choose imacpro1,1 and then inject imac13,2 frequency vectors via CPUFriend.kext I can get full hardware acceleration and proper CPU power management. Any downsides to this approach?

@Lonelytanker,

I don't have an i7-3770, so I can't give a very educated opinion if you want to
run your machine without a graphics card. This guide works out a lot of the issues
for a Macmini6,1 in that mode, and its not clear how an iMac13,2 as recommended
by the @trs96 guides would compare. Sniki has settings for better HD4000 graphics in
the device properties and boot arguments of his sample config.plist.

Generally, it seems an iMac13,2 SMBIOS might be preferred if you are using an
Nvidia card, since they came with Nvidia graphics originally, and because you might
have Nivdia dGPU power management pre-configured. See Toleda's native dGPU power
management guide.

I think you only get HEVC hardware acceleration with an iMacPro1,1 or MacPro7,1 SMBIOS.
MacPro7,1 issues memory configuration error messages, although it seems to work ok.
Generally it seems the preferred mode for HEVC is with IGPU disabled. See shuhung's
Standalone RXXX guide for details, and he is the one who asserts the limitation on HEVC model
numbers.

To me its not clear what I get out of using CPUfriend. An older version of ssdtPRGen.sh complained
if you used an iMacPro1,1 SMBIOS with an Ivy processor, but the new version produces the
same file, without complaint with SMBIOS set to iMacPro1,1 whether you use the command

./ssdtPRGen.sh -b Mac-FC02E91DDD3FA6A4 -target 1 -t 77

or the command

./ssdtPRGen.sh -target 1 -t 77 -x 1.

It could be that I simply don't know how to use CPUfriend correctly, but these PRGen power management
ssdt's already give the minimum 1600 to the maximum turbo of 3600 (i5-3470) or 3800 (i5-3570).
I don't think you can get HWP working on the Ivy processors. If you get any CPUfriend benefits, please
let us know what to look for and how to accomplish it.

Another question you may encounter is setting up native power management for your RX580 with
iMacPro1,1. I'm using a modified dGPM.kext from Toleda with an added iMacPro1,1 IOkitpersonality
for my RX560 card. I'm not sure how much I'm getting out of it, but I can see Sony Food Fizzle cranking
up from an idle consumption of about 20W to 67W playing HEVC file Sony Food Fizzle.

You may want to use VideoProc cautiously, because it does not always give accurate reports whether
HEVC is working correctly. However, VideoProc gives higher (4K) resolution scores for me with an
iMacPro1,1 SMBIOS than for a MacMini or iMac13,2 profile in H264, and also 4K for HEVC.

Hope this helps,
Lisa
Thanks, @LisaAlterEgo !
This power management stuff is confusing. I'm hoping to get my hack moved over to Mojave in the next few weeks. I was waiting for the stable version of WEG 1.3.6 to be released -- it looks like that happened last night so I should start working on this soon. I'll report back with any issues I come across.
 
Just a little heads up: Following this guide (thanks!) and noticed the 2 days ago released VirtualSMC 1.1.0 doesn't include VirtualSMC.efi (anymore or for good :think:). It can be found in the previous release 1.0.9.
 
Just a little heads up: Following this guide (thanks!) and noticed the 2 days ago released VirtualSMC 1.1.0 doesn't include VirtualSMC.efi (anymore or for good :think:). It can be found in the previous release 1.0.9.
Use VirtualSMC 1.1.0 and ignore the story of VirtualSMC.efi.
VirtualSMC.efi is no longer needed.

Don't expect the guide to be modified.
 
Use VirtualSMC 1.1.0 and ignore the story of VirtualSMC.efi.
VirtualSMC.efi is no longer needed.

Don't expect the guide to be modified.
Hmm. Just wanted to let people following this guide know about this and if @Sniki wants to modify the guide, it will of course be at his/her discretion.
 
Status
Not open for further replies.
Back
Top