Bootloader: Uses Super-UEFIinSecureBoot-Disk to bypass Secure Boot as this laptop has a BIOS password that cannot be removed
Hardware compatibility
What works
CPU power management
GPU acceleration and video codecs
SSD (SATA/NVME)
Wi-Fi (AirportItlwm.kext)
All USB ports
USB-C Video
Touchscreen (with gestures)
Trackpad
FN Keys
Webcam
Screen Brightness
Internal Audio (Speakers, Headphones)
Battery percentage
Thunderbolt
Tested with a CalDigit TS3 Plus, hotplug is working.
The PCIe Ethernet NIC on the dock causes system instability when a Ethernet cable is plugged in, disable the NIC by putting dk.e1000=0 e1000=0 into your boot-args.
The DisplayPort out has major performance issues (cursor updates at about 11fps). For some reason plugging in a USB-C to HDMI Adapter into a Thunderbolt port on the dock works fine. Possibly a firmware issue with the Thunderbolt controller?
Closing and Waking the Internal Display (when sleep is disabled)
Untested
iCloud Services
Bluetooth (no kext installed yet)
Not working
Sleep (Works if laptop is left idle and Power Nap is on, closing lid will induce a crash, under investigation)
Recommended to disable Sleep with sudo pmset -a disablesleep 1 otherwise the system will freeze when closing the lid
Facial Recognition IR Camera
Fingerprint Sensor
NFC
Smartcard
Internal Microphone
HDMI Out
Does not work under Linux/macOS because of HP Firmware issues.
Unfortunately, I was not able to repeat this with the sambow23 EFI. I do not understand USB mapping well enough to pinpoint the difference between the two EFIs. Perhaps you might have some insight as to why the jusufklncc USB port mapping somehow enables the docking bay's USB-A ports? Thank you
It is indicated that the HDMI suffers from HP firmware. HDMI out does not work with this EFI. How did you know that the firmware was faulty and where can I read more? How do you connect to an external monitor?
The EFI detects the docking bay's HDMI and max resolution is 2560X1440. What needs to be done to increase it up to 4K?
Greetings, have you tested BT with the Intel comms? I ask because if there is some reason it will never work, I would like to know before embarking on a snipe hunt. I realize that .md page indicates it is untested, however, I thought it made sense ask in case you have tested it since then. Thanks