Contribute
Register

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

example from my config.plist via my guide
Makes sense, only enable the ones that you'll actually use on a regular basis. What does the OC boot menu look like when all of these are enabled ?
 
Makes sense, only enable the ones that you'll actually use on a regular basis. What does the OC boot menu look like when all of these are enabled ?
looks nasty... :)

just a row of options really, i have the boot picker turned off on my laptop but if I need to see the boot picker, i hold down the alt button when turning on and i just see the three options, macOS, Recovery and Clear NVRAM. i don't bother or have a need for the rest of the Tools :)
 
The maxim I wrote is a promotion phrase for sake, so if you ask a Japanese person you know, you will answer "There is no such maxim" if you do not know it, and if you know it, you will laugh and explain.

By the way, I feel that the cause of the non-operation is not the created EFI but another cause.

1. Catalina is now working fine from the internal SSD using CLover r5126.
2. Created on a USB2.0 32GB stick for installing Bug Sur.

If my perception is incorrect, please point out what is different.

If my perception above is correct:
1. Insert the USB created with the power turned off into USB2.0 on the entire surface.
2. Turn on the power and press F9 on the keyboard repeatedly to display the BIOS boot selection. (If you do not do it with full keyboard, it will fail)
3. Select the USB stick to display the OpenCore boot menu.
4. Select NVRAM Rest and the OpenCore boot menu will reappear.
5. Select the SSD currently in use from the menu.

Make sure Catalina starts with this procedure.

Replace the CPU Power Management you created with Sniki's EFI/OC/ACPI/SSDT.aml and rename it.
View attachment 497891

Delete iGPU settings.
View attachment 497892

Set up Platforminfo according to the guide (SystemProductName = MacPro6.1).

View attachment 497893
Thanx for you effort,
maybe i did not get your maxim, cause i am not a english Native speaker ;-)

I did exactly what you described ;-)
also SMBIOS with correct Serial via the GenSMBIOS-master, and proofed / edit via ProperTree-master

The first Hang was because there where some things left in NVRAM.
I can not Push that enough:

Clear NVRAM when Changing EFI Folder for Boot,
as i have to do, leaving my Catalina working......

Also OC Pushed itself as first Boot Device, as Windows did...... overiding Bios Defaults !


Second Error, after the Install first reboot, is probably due to a faulty Old SSD..........
 
Last edited by a moderator:
Attach EFI, so we can take a look what you did, i can't blind guess the problem but best advice first would be to go to Config.plist > NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 > Boot-Args > add these:
Code:
keepsyms=1 -v
This will enabled Verbose Boot and attach screenshot where it hangs.
 
Thanx Sniki, but what helped me to get over the previous ERROR, is:

CLEAN NVRAM ( never have read that anywhere )

After that, it runs the Installer through the first Restart, just to hang again ;-)

3) If you are using a Dedicated GPU: iMacPro1,1 or
iMac13,2 ( is not supported ? got that Message some Time before )

But that is maybe cause i do not want to change my current Catalina to iMacPro1,1 to generate SSDT, anyway

Ivy Bridge System Definitions:
Mac-00BE6ED71E35EB86:iMac13,1
Mac-FC02E91DDD3FA6A4:iMac13,2
Mac-031AEE4D24BFF0B1:Macmini6,1
Mac-F65AE981FFA204ED:Macmini6,2
Mac-4B7AC7E43945597E:MacBookPro9,1
Mac-6F01561E16C75D06:MacBookPro9,2
Mac-C3EC7CD22292981F:MacBookPro10,1
Mac-AFD8A9D944EA4843:MacBookPro10,2
Mac-66F35F19FE2A0D05:MacBookAir5,1
Mac-2E6FAB96566FE58C:MacBookAir5,2
Mac-F60DEB81FF30ACF6:MacPro6,1

are the Only ones working........

but somewhere i have read:

delete SSDT.aml !!!!!!!!!!!

i took my old one, generating a new is impossible without changing internal SMBIOS, or is there a Option on the Piker Script to force that -> different to the actual System SMBIOS ?

I have a I5-3570 can somebody send me a SSDT.aml ?
for the iMacPro1,1 pleaaaaaze........
BR
Is it a 3.4GHz i5-3570K?
 
Second Error, after the Install first reboot, is probably due to a faulty Old SSD..........
The fact that Catalina can be started and operated with Sniki's EFI means that there is no problem
in creating your EFI.
It may be that you or my Old SSD seems to be the cause of the problem.

Next, format the Old SSD on which you are installing Big Sur with Catalina.
1. Start DiskUtilities and select "Show All Device" from the View Icon on the upper left.
2. Select the old SSD device name from the guide on the left
3. Select the Erase Icon above
4. Click the Erase button in the settings of the attached image
5. Connect the formatted Old SSD to the internal disk.
6. Insert the USB Stick into the USB 2.0 on the front
7. When the installer launches, select Disk Utilities and reformat it with APFS.

Check to see if the Big Sur installation is complete.

Erase.png
 
Last edited:
The fact that Catalina can be started and operated with Sniki's EFI means that there is no problem
in creating your EFI.
It may be that you or my Old SSD seems to be the cause of the problem.

Next, format the Old SSD on which you are installing Big Sur with Catalina.
1. Start DiskUtilities and select "Show All Device" from the View Icon on the upper left.
2. Select the old SSD device name from the guide on the left
3. Select the Erase Icon above
4. Click the Erase button in the settings of the attached image
5. Connect the formatted Old SSD to the internal disk.
6. Insert the USB Stick into the USB 2.0 on the front
7. When the installer launches, select Disk Utilities and reformat it with APFS.

Check to see if the Big Sur installation is complete.

View attachment 498062

Well, Thanx for your Help, i apreciate that !

@Sniki
Add Nvram String is looking Like Smbios ?!
keepsyms=1 where does it store that image ? will try that......

@LisaAlterEgo
Nope, it´s the Standart I5-3570, but internal Graphics Disabled in Bios........

@Asural
I DO NOT START CATALINA WITH SNIKI´S EFI, CAUSE THEN MY SMBIOS MACPRO 7,1 WOULD CHANGE AND I HAD TO REACTIVATE APPLE ID, AS TO RE ACTIVATE GUUID BASED PROGRAM LICENSE...............

THE SYSTEM HAS REALTIME RESPONSIVNESS, WICH NO HIGH END MAC HAS, MAYBE THAT 7,1 IN REAL WORLD
AND IT IS A DAMMN OLD CPU AND CHIPSET FROM 2012 ;-) I HAVE A DOMAIN BASED ON SERVER 2019 HP 8300!
IT NEVER CRASHED ! INTERSTINGLY BLENDER CRASHED ON WINDOWS, BUT NEVER ON CATALINA.

THIS WITHOUT NVME SSD

did the formatting the exact same whay, as i do allways.....
The SSD Information is Verify and 2% Used of end to Life, but...... that thing is old ;-)
And is influenting Other SSD Behavier if used on internal Sata Ports....
My New one is on the way ;-)

Let You Now then wat is going with it;-)

To Clarify:

SATA 0 Catalina Crucial 1TB MX500 SSD - CLOVER 5126 EFI
SATA 1 Windows 10 Crucial 500GB MX500 SSD - WINDOW EFI
SATA 2 BigSur Old Crucial Chip SSD 128GB - OC SNIKI EFI - Deactivated in Bios ( Sorry, Upload of EFI later, was at the Dentist, and need my Mashine Today..... )

USB Stick 16GB SanDisk Cruizer on USB 2 Port on Front - OC 0.6.3

I CAN START ANYTHING WITH ANYTHING THAT WAY ;-)

Bios:
Uefi Only no Security
PCI Disabled
Internal USB Ports Disabled
Front USB only 2 of 4 Enabled
Back USB Only First 3 USB 3 PORTS ENABLED
NO PXE BOOT

ASUS PCE-AC68 WLAN CARD OOB WAS ABLE TO CONNECT IN THE INSTALLER TO 5GHZ NET
AMD WX4100 GRAFIC CARD OOB - RX560 TYPE

Finally made it ;-)

but had to Deactivate SATA Ports, with 3 SSD´s on it become sluggish........
Bit Slow, but could be due to some Post Tasks.......

Will work on that later........
Boot with 5126 was not possible, ( SMBIOS 7,1 ;-)
 
Last edited by a moderator:
USB Stick 16GB SanDisk Cruizer on USB 2 Port on Front
Big Sur need 32GB USB

I have no knowledge of how to use it in a multi-boot environment, so it will not help you.
 
Last edited:
I did the testing yesterday on my HP Elite 8300 SFF on latest macOS Big Sur and everything is working except DRM.
VDA Decoded = Failed.
@Sniki,

Sorry for the delay in DRM testing.

I prepared the following chart for Opencore 0.6.3 and Catalina 10.15.7. For an
AMD DGPU, it seems to make little difference in the shikigva settings, whether
the SMBIOS is iMacPro1,1 or MacPro6,1 for AppleTV decoding. Although I assumed
that the iMacPro1,1 would not need the shikigva flag in bit 4 (i.e 16 in the sum)
both IMP11 and MP61 need it for full AppleTV functionality, and the best setting
is shikigva=144 (128+16) for AppleTV. With Big Sur, both MP61 and IMP11 are
mostly dysfunctional, and mostly regardless of shikigva setting, one can first
download and then play media content in m4v content, but one cannot play HLS
video in any form and one cannot stream HLS or mv4.

With Opencore 0.6.3 and Catalina 10.15.7 with an Nvidia, it works mostly for
AppleTV with shikigva=288 and an appropriate shiki-id setting. 288=256+32.
The 256 tells it to use software decoding and the 32 tells it to substitute a
different board-id for video. I've successfully used Nvidia shiki-id's as indicated
by Dortania's OpenCore SMBIOS page, such as shiki-id=Mac-FC02E91DDD3FA6A4
(emulating iMac13,2) and shiki-id=Mac-2BD1B31983FE1663 (emulating MacBookPro11,3)
with the SMBIOS set to MP6,1. It may only successfully stream AppleTV (HLS and 4v)
and not work with Quicktime or downloaded media.

With Opencore 0.6.3 and Big Sur, MP61 and IMP11 seem to mostly assume that the
IGPU is off. I've had some luck with Big Sur SMBIOS set to iMac18,3 and a fully featured
IGPU enabled with AAPL,ig-platform-id set to <0A006601>. AppleTV still fails,
but Hackintool reports VDA Decoder fully supported, VideoProc reports 4K in H264
and HEVC, and Sony's Swordsmith and Food Fizzle play smoothly.

The last two screen captures are from the iMac18,3 SMBIOS with an RX560 and IGPU
enabled. The first shows an oral Siri inquiry. You can see from Intel Power Gadget
that the IGPU is enabled, and throttles up as Siri processes. Without the IGPU enabled,
Siri takes a little longer to start up. The second shows LuxMark 3.1 running a stress
test with the IGPU enabled. You can see the HD4000 graphics fully throttled up.

I'm using AGPMInjector with some changed values for the IGPU and Nvidia AGPM.
I'm attaching a zip of the experimental info.plist.
 

Attachments

  • TV result chart PNG.png
    TV result chart PNG.png
    181.5 KB · Views: 73
  • Screen Shot 2020-11-23 at 7.10.39 PM.png
    Screen Shot 2020-11-23 at 7.10.39 PM.png
    83.7 KB · Views: 61
  • Screen Shot 2020-11-23 at 5.51.38 PM.png
    Screen Shot 2020-11-23 at 5.51.38 PM.png
    1.4 MB · Views: 69
  • Info.plist.zip
    1.4 KB · Views: 39
Last edited:
@LisaAlterEgo Amazing.
Thank you for all of that work.

So in short words:
1. Shikigva=144 is the one we should use for DGPU users as the default one whether it is MacPro6,1 or iMacPro1,1.
Am i correct ?

2. Big Sur still broken, no perfect solution, right ?

3. What about IGPU users only, what do you suggest as the best option ?

4. Do you have a Github account ?
 
Back
Top