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

[LisaAlterEgo]

I'm using the HP8300CMT i7-3770 RX570 SMBIOS = iMacPro1.1 OpenCore 0.6.5 to test Big Sur.

ADD:
I tested the operation with SMBIOS = MacPro7.1, but when I started up, I received a warning that the memory configuration was different, and the status of TV + did not change and the green screen remained.

I have a very similar system with i5-3570K RX 570 SMBIOS IMP11 OC 0.6.5

With IGPU off, I can download AppleTV mpeg files, and then play them afterwards.
I can't stream or play AppleTV HLS files. VideoProc shows 4K HEVC and H264.
Hackintool says VDADecoder is fully supported. HEVC files, like Swordsmoth,
play smoothly.

 

[palmereldrich]

Update from Catalina 10.5.7, with OC 0.6.4. Smooth and no worries. Only a KP after second reboot. No need to do nothing. It runs ahead directly to login. All done and all working fine!

 

[LisaAlterEgo]

New Big Sur DRM Method in OC 0.6.5! (updated twice 1/11)

This is new and not thoroughly tested, but we have a new WEG DRM
method for Big Sur.

I first got it working with an i5-3570K HP 8300 CMT with a MSI 4 GB
RX 560 LP graphics card, configured with SMBIOS of iMac15,1. I tested
it again today in a second machine, an i5-3570K HP 8300 CMT with an
Asus ROG Strix 4 GB RX 570 graphics card configured with SMBIOS
set to iMacPro1,1.

In both cases, playing DRM-protected video worked best with the
IGPU disabled in BIOS.

What works with IGPU disabled:
Quicktime player on mpeg4 and HEVC files
VDADecoder Fully supported on Hackintool
H264 and HEVC reported as enabled at 4K in VideoProc
Streaming of DRM-protected HLS and mpeg4 in AppleTV
Smooth playing of HEVC files like Food Fizzle and Swordsmith
Playing previously downloaded mpeg4 and HLS video in AppleTV

If its working, in IORegister under IOService:/->Root-><Machine SMBIOS name>
you'll see a new "hwgva-id" set to the iMacPro1,1 board-id ending in DDD94.

All of the testing with my IMP11 machine was done with IGPU disabled.
I tested the iMac15,1 with IGPU disabled, headless, and with a connector-full
framebuffer. It worked as above with IGPU disabled. It worked second best
with a connector-full IGPU.

For connector-full, I tested with the IGPU enabled and set to primary in BIOS,
with PciRoot(0x0)/Pci(0x2,0x0) device properties:

AAPL,ig-platform-id: data 00006601
device-id: data 66010000
model: string Intel HD Graphics 4000
hda-gfx: string onboard-1
AAPL,slot-name: string Internal@0,2,0
igfxpavp: number 1

and PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) device properties:

unfairgva: data 05000000
hda-gfx: string onboard-2

What works in iMac15,1 machine with connector-full framebuffer:
Quicktime player on mpeg4 and HEVC files
VDADecoder Fully supported on Hackintool
H264 and HEVC reported as enabled at 4K in VideoProc
DRM streaming of HLS and mpeg4 in AppleTV
Smooth playing of HEVC files like Food Fizzle and Swordsmith

What doesn't work so far in iMac15,1 connector-full:
playing previously downloaded mpeg4 in AppleTV hangs

I removed the PciRoot(0x0)/Pci(0x2,0x0) device properties and
set IGPU to secondary. WEG defaulted to AAPL,ig-platform-id
of headless 07006201 and device-id 52010000.

What works in iMac15,1 machine with headless framebuffer:
Quicktime player on HEVC non-iDRM files
VDADecoder Fully supported on Hackintool
H264 and HEVC reported as enabled at 4K in VideoProc
DRM streaming of HLS and mpeg4 in AppleTV
Smooth playing of HEVC files like Food Fizzle and Swordsmith

What doesn't work so far headless:
Playing previously downloaded DRM files in AppleTV or Quicktime crashes.

For the IGPU disabled or headless, I had one device property for
PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0),

unfairgva: data 05000000

No default settings for com.apple.AppleGVA or com.apple.coremedia in
either machine for any tests.

I used Pavo's ocbuilder to download and compile the latest debug versions
of kexts and installed debug Lilu 1.5.1 and WEG 1.4.7, which has the new
"unfairgva" subsections instead of shikigva.

 

[Asural]

New Big Sur DRM Method in OC 0.6.5! (updated twice 1/11)

I used Pavo's ocbuilder to download and compile the latest debug versions
of kexts and installed debug Lilu 1.5.1 and WEG 1.4.7, which has the new
"unfairgva" subsections instead of shikigva.

I just checked the display of AppleTV +, it is displayed, thank you very much.
I plan to investigate the setting value of unfairgva.

 

[LisaAlterEgo]

I just checked the display of AppleTV +, it is displayed, thank you very much.
I plan to investigate the setting value of unfairgva.
View attachment 504709

If you look at the section of top-level code called kern_weg, you'll see that in Big Sur,
the two sections of code called kern_cdf and kern_shiki are bypassed, and kern_unfair
is run instead.

Kern_cdf manages the cdfon boot option and enable-hdmi20 device properties (no longer
available in Big Sur) and the shiki settings are no longer invoked in Big Sur. Kern_unfair.cpp
and kern_unfair.hpp show what the unfairgva settings do. Its also mentioned in the Changelog.

 

[Asural]

If you look at the section of top-level code called kern_weg, you'll see that in Big Sur,
the two sections of code called kern_cdf and kern_shiki are bypassed, and kern_unfair
is run instead.

Kern_cdf manages the cdfon boot option and enable-hdmi20 device properties (no longer
available in Big Sur) and the shiki settings are no longer invoked in Big Sur. Kern_unfair.cpp
and kern_unfair.hpp show what the unfairgva settings do. Its also mentioned in the Changelog.

I did only the operation test, it seems that "Spider-Man: Far From Home" cannot be played with the setting value of "unfairgva = 0x05000000 or 0x0D000000".
It seems that it is simply different from the Shikigva setting, so he will check the WEG side with the information given.

ADD:
"GVA bitmask as specified in unfairgva boot argument / property." Was defined in kern_unfair.hpp.
All DRM tests were playable with the setting "unfairgva = 0x01000000".

Isn't it possible to play the file downloaded by removing hda-gfx and unfairgva = 0x03000000?

 

[Supiter]

Still waiting for a

HP Elite 8300 & 6300 Pro Big Sur Installation Guide using OC​

Or should I get a new Mac mini?

Edit: Corrected a typo

 

[trs96]

Installation Guide using OT

OT = Off Topic. Do you mean OC OpenCore ?

 

[Feartech]

Still waiting for a

HP Elite 8300 & 6300 Pro Big Sur Installation Guide using OT​

Or should I get a new Mac mini?

yes, buy a new mac, or learn opencore

 

[67BGTEV]

Still waiting for a

HP Elite 8300 & 6300 Pro Big Sur Installation Guide using OT​

Or should I get a new Mac mini?

This is what I followed for OC and it is working fine on 8300CMT w/ RX580 running Big Sur and 8300SFF w/ HD4000 running Catalina.