Contribute
Register

[Guide] HP ProBook/EliteBook/Zbook using Clover UEFI hotpatch

Status
Not open for further replies.

Attachments

  • compress file.zip
    2.2 MB · Views: 73
cdqrain said:
I have reinstall clover and check the EmuVariableUefi-64.efi and RC scripts, the screen brightness and volume still can not be saved.
Click to expand...

Your misc/preboot.log shows no nvram.plist being loaded.
Which either means you forgot to generate preboot.log (F2 as per "Problem Reporting"), or you didn't install the RC scripts (the RC scripts create nvram.plist in EFI root).
Also, your preboot.log shows no EmuVaribleUefi-64.efi installed:
Code: 
0:113  0:000  === [ LoadDrivers ] =======================================
0:114  0:000  Loading AppleImageCodec-64.efi  status=Success
0:115  0:001  Loading AppleKeyAggregator-64.efi  status=Success
0:116  0:001  Loading AppleUITheme-64.efi  status=Success
0:118  0:001  Loading DataHubDxe-64.efi  status=Success
0:120  0:002  Loading FirmwareVolume-64.efi  status=Success
0:121  0:001  Loading FSInject-64.efi  status=Success
0:122  0:001  Loading OsxAptioFixDrv-64.efi  status=Success
0:123  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
0:125  0:001  Loading SMCHelper-64.efi  status=Success
0:126  0:001  Loading HFSPlus.efi  status=Success
0:128  0:002   - driver needs connecting
0:128  0:000  Loading HPFanReset.efi  status=Success
0:220  0:091  HPFanReset: successfully set fan control to BIOS mode.
0:220  0:000  Loading CsmVideoDxe-64.efi  status=Success
0:221  0:001   - driver needs connecting
0:221  0:000  2 drivers needs connecting ...
0:221  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
0:221  0:000  HFS+ driver loaded
0:221  0:000  Video driver loaded: disconnect Success
1:301  1:079  Searching for invalid DiskIo BY_DRIVER connects:
1:301  0:000   - Handle 98D56C18 with DiskIo, is Partition, no Fs, BY_DRIVER Agent: 98C6C718, Disconnect: Success
1:356  0:054  CsmVideoDriverBindingStart
1:356  0:000  Controller is [030000]
1:356  0:000  Check for VBE
1:367  0:011   found Detail Timing 1920x1080
1:367  0:000   found Detail Timing 1920x1080
1:368  0:000    0 1280x1024 attr=9B - ok, edid-
1:368  0:000    1 1024x768 attr=9B - ok, edid-, 1024x768, working, highest, pref=1
1:368  0:000    2 640x480 attr=9B - ok, edid-, 640x480, working
1:369  0:000    3 800x600 attr=9B - ok, edid-, 800x600, working
1:370  0:000    4 1920x1080 attr=9B - ok, edid+, working, highest, pref=4
1:370  0:000  CsmVideo: New mode: 4 1920x1080 - set
1:594  0:224   - SetMode pref 4 (4) = Success
1:594  0:000  CsmVideoCheckForVbe - Success
1:595  0:000  CsmVideoDriverBindingStart end Success
1:794  0:199  CsmVideoDriverBindingStart
1:794  0:000  mixed support=0
2:002  0:207  Controller is [030200]
2:002  0:000  Check for VBE
2:014  0:011   found Detail Timing 1920x1080
2:014  0:000   found Detail Timing 1920x1080
2:014  0:000    0 1280x1024 attr=9B - ok, edid-
2:014  0:000    1 1024x768 attr=9B - ok, edid-, 1024x768, working, highest, pref=1
2:015  0:000    2 640x480 attr=9B - ok, edid-, 640x480, working
2:015  0:000    3 800x600 attr=9B - ok, edid-, 800x600, working
2:016  0:000    4 1920x1080 attr=9B - ok, edid+, working, highest, pref=4
2:016  0:000  CsmVideo: New mode: 4 1920x1080 - set
2:240  0:224   - SetMode pref 4 (4) = Success
2:240  0:000  CsmVideoCheckForVbe - Success
2:241  0:000  CsmVideoDriverBindingStart end Success
Also, it shows CsmVideoDxe-64.efi, which is not present in the EFI/Clover you attached.

So, either you're not booting from the EFI/Clover you attached, or you forgot to press F2 as requested in "Problem Reporting".

How To Enable Full Display Resolution in Clover without CsmVideoDxe ?
Click to expand...

Full resolution in Clover is not important.
 
RehabMan said:
Your misc/preboot.log shows no nvram.plist being loaded.
Which either means you forgot to generate preboot.log (F2 as per "Problem Reporting"), or you didn't install the RC scripts (the RC scripts create nvram.plist in EFI root).
Also, your preboot.log shows no EmuVaribleUefi-64.efi installed:
Code: 
0:113  0:000  === [ LoadDrivers ] =======================================
0:114  0:000  Loading AppleImageCodec-64.efi  status=Success
0:115  0:001  Loading AppleKeyAggregator-64.efi  status=Success
0:116  0:001  Loading AppleUITheme-64.efi  status=Success
0:118  0:001  Loading DataHubDxe-64.efi  status=Success
0:120  0:002  Loading FirmwareVolume-64.efi  status=Success
0:121  0:001  Loading FSInject-64.efi  status=Success
0:122  0:001  Loading OsxAptioFixDrv-64.efi  status=Success
0:123  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
0:125  0:001  Loading SMCHelper-64.efi  status=Success
0:126  0:001  Loading HFSPlus.efi  status=Success
0:128  0:002   - driver needs connecting
0:128  0:000  Loading HPFanReset.efi  status=Success
0:220  0:091  HPFanReset: successfully set fan control to BIOS mode.
0:220  0:000  Loading CsmVideoDxe-64.efi  status=Success
0:221  0:001   - driver needs connecting
0:221  0:000  2 drivers needs connecting ...
0:221  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
0:221  0:000  HFS+ driver loaded
0:221  0:000  Video driver loaded: disconnect Success
1:301  1:079  Searching for invalid DiskIo BY_DRIVER connects:
1:301  0:000   - Handle 98D56C18 with DiskIo, is Partition, no Fs, BY_DRIVER Agent: 98C6C718, Disconnect: Success
1:356  0:054  CsmVideoDriverBindingStart
1:356  0:000  Controller is [030000]
1:356  0:000  Check for VBE
1:367  0:011   found Detail Timing 1920x1080
1:367  0:000   found Detail Timing 1920x1080
1:368  0:000    0 1280x1024 attr=9B - ok, edid-
1:368  0:000    1 1024x768 attr=9B - ok, edid-, 1024x768, working, highest, pref=1
1:368  0:000    2 640x480 attr=9B - ok, edid-, 640x480, working
1:369  0:000    3 800x600 attr=9B - ok, edid-, 800x600, working
1:370  0:000    4 1920x1080 attr=9B - ok, edid+, working, highest, pref=4
1:370  0:000  CsmVideo: New mode: 4 1920x1080 - set
1:594  0:224   - SetMode pref 4 (4) = Success
1:594  0:000  CsmVideoCheckForVbe - Success
1:595  0:000  CsmVideoDriverBindingStart end Success
1:794  0:199  CsmVideoDriverBindingStart
1:794  0:000  mixed support=0
2:002  0:207  Controller is [030200]
2:002  0:000  Check for VBE
2:014  0:011   found Detail Timing 1920x1080
2:014  0:000   found Detail Timing 1920x1080
2:014  0:000    0 1280x1024 attr=9B - ok, edid-
2:014  0:000    1 1024x768 attr=9B - ok, edid-, 1024x768, working, highest, pref=1
2:015  0:000    2 640x480 attr=9B - ok, edid-, 640x480, working
2:015  0:000    3 800x600 attr=9B - ok, edid-, 800x600, working
2:016  0:000    4 1920x1080 attr=9B - ok, edid+, working, highest, pref=4
2:016  0:000  CsmVideo: New mode: 4 1920x1080 - set
2:240  0:224   - SetMode pref 4 (4) = Success
2:240  0:000  CsmVideoCheckForVbe - Success
2:241  0:000  CsmVideoDriverBindingStart end Success
Also, it shows CsmVideoDxe-64.efi, which is not present in the EFI/Clover you attached.

So, either you're not booting from the EFI/Clover you attached, or you forgot to press F2 as requested in "Problem Reporting".



Full resolution in Clover is not important.
Click to expand...

You tell me Delete CsmVideoDxe-64.efi for the sleep problem.
EmuVaribleUefi-64.efi and RC scripts should be installed. the screen shot is attached.
 

Attachments

  • Snip20171126_2.png
    Snip20171126_2.png
    158.8 KB · Views: 131
cdqrain said:
You tell me Delete CsmVideoDxe-64.efi for the sleep problem.
Click to expand...

Not necessarily.
It is just not according to the guide.
Any change from the guide should be eliminated in an effort to troubleshoot.

EmuVaribleUefi-64.efi and RC scripts should be installed. the screen shot is attached.
Click to expand...

You will need to provide "Problem Reporting" files as per post #1/FAQ.
Read it carefully.
It is not possible to tell from that image that you have the correct options for the Clover installer (for example, impossible to tell if you installed to EFI).
 
RehabMan said:
Not necessarily.
It is just not according to the guide.
Any change from the guide should be eliminated in an effort to troubleshoot.



You will need to provide "Problem Reporting" files as per post #1/FAQ.
Read it carefully.
It is not possible to tell from that image that you have the correct options for the Clover installer (for example, impossible to tell if you installed to EFI).
Click to expand...
 

Attachments

  • compress file.zip
    2.2 MB · Views: 92
cdqrain said:
...
Click to expand...

Check the values loading from nvram.plist to see if they make sense from your previous session (use nvram -p to list them before rebooting).
These are shown in your Clover bootlog:
Code: 
0:998  0:000   Adding Key: SystemAudioVolume: Size = 1, Data: 00
0:998  0:000   Adding Key: SystemAudioVolumeDB: Size = 1, Data: B6
0:998  0:000   Adding Key: backlight-level: Size = 2, Data: 36 03

It could be you have old data in your "real" NVRAM that is now interfering with "emulated" NVRAM.
If so, you can use the UEFI shell to delete all mac NVRAM variables (you will need to do some digging to find the guid Apple uses).
Or you can do CMOS reset (remove CMOS battery from the motherboard).

The problem likely stems from not using EmuVariableUefi-64.efi from the start (as per guide).
 
RehabMan said:
Check the values loading from nvram.plist to see if they make sense from your previous session (use nvram -p to list them before rebooting).
These are shown in your Clover bootlog:
Code: 
0:998  0:000   Adding Key: SystemAudioVolume: Size = 1, Data: 00
0:998  0:000   Adding Key: SystemAudioVolumeDB: Size = 1, Data: B6
0:998  0:000   Adding Key: backlight-level: Size = 2, Data: 36 03

It could be you have old data in your "real" NVRAM that is now interfering with "emulated" NVRAM.
If so, you can use the UEFI shell to delete all mac NVRAM variables (you will need to do some digging to find the guid Apple uses).
Or you can do CMOS reset (remove CMOS battery from the motherboard).

The problem likely stems from not using EmuVariableUefi-64.efi from the start (as per guide).
Click to expand...

Thanks, it contains much information, I should learn about the relation term first. :)
 
Have install 10.13.1 on hp elitebook 840 G3. Almost everything work perfect. Follow the fantastic [Guide] HP ProBook/EliteBook/Zbook using Clover UEFI hotpatch.

Needs help for the smal thing that doesn´t work.

1. Sleep

When I click sleep in the apple menu or close the lid, the screen turns gray, laptop screen can't wake up after sleep. With an extern monitor connected (DP to DVI), the monitor goes to sleep but can wake up from keyboard or mouse, but the laptop screen is still grey. The backlight is times to working on the laptop screen because the gray will be lighter or darker, but no wake.

Have read a lot on the forum and google, a lot talk about Fix EDID but it don’t know if its the right way or if I forgot to to install some SSDT for AppleBacklightinjectt.kext.

2. External headphone and mic. Headphone is most important for me.

Pls have som one idea or point me in some direction for a solution

And thanks for everything that works;-) its my best macbook ever.
  • built-in and usb keyboard
  • built-in trackpad and bluetooth mac mouse
  • DP port to DVI monitor
  • WiFi
  • Bluetooth (with handoff) using BCM94352Z
  • USB3, 2
  • Audio internal speaker
  • Volume control at keyboard
  • built-in mic, for Siri and FaceTime
  • built-in camera and FaceTime
  • battery status
  • backlight controls
  • wired Ethernet
  • Icloude, Mac App Store, iTunes, ibook,message
Not Tested
  • Card reader work, not tested, don’t show upp in USB
  • USB-C port, not tested
  • Change FCC and US mode to SE mode in wifi (53 45). Don’t know if it matter.
 

Attachments

  • Problem_reporting_folder.zip
    2.7 MB · Views: 78
TrashPro
GA-H97N-WiFi |  i5 4460 |  GTX 750ti
Hakantosh G5
GA-Z87X-UD3H |  i7 4770K |  HD 4600
Fest-is said:
Have install 10.13.1 on hp elitebook 840 G3. Almost everything work perfect. Follow the fantastic [Guide] HP ProBook/EliteBook/Zbook using Clover UEFI hotpatch.

Needs help for the smal thing that doesn´t work.

1. Sleep

When I click sleep in the apple menu or close the lid, the screen turns gray, laptop screen can't wake up after sleep.
Click to expand...

Read here:
https://www.tonymacx86.com/threads/readme-common-problems-in-10-13-high-sierra.233582/
(you need to create a display override file with patched EDID)

2. External headphone and mic. Headphone is most important for me.
Click to expand...

Try alternate layout-id as per post #1.
 
RehabMan said:
Check the values loading from nvram.plist to see if they make sense from your previous session (use nvram -p to list them before rebooting).
These are shown in your Clover bootlog:
Code: 
0:998  0:000   Adding Key: SystemAudioVolume: Size = 1, Data: 00
0:998  0:000   Adding Key: SystemAudioVolumeDB: Size = 1, Data: B6
0:998  0:000   Adding Key: backlight-level: Size = 2, Data: 36 03

It could be you have old data in your "real" NVRAM that is now interfering with "emulated" NVRAM.
If so, you can use the UEFI shell to delete all mac NVRAM variables (you will need to do some digging to find the guid Apple uses).
Or you can do CMOS reset (remove CMOS battery from the motherboard).

The problem likely stems from not using EmuVariableUefi-64.efi from the start (as per guide).
Click to expand...

the list of nvram -p is:
Code: 
fakesmc-key-BEMB-flag    %01
fakesmc-key-RPlt-ch8*    j130%00%00%00%00
fakesmc-key-RBr -ch8*    2016mb%00%00
EFILoginHiDPI    %00%00%00%00
fakesmc-key-#KEY-ui32    %00%00%00%12
SystemAudioVolumeDB    %b6
fakesmc-key-BATP-flag    %00
EmuVariableUefiPresent    Yes
fakesmc-key-MSTc-ui8    %00
LocationServicesEnabled    %01
fakesmc-key-BNum-ui8    %01
security-mode    none
OsxAptioFixDrv-RelocBase    %000%abz%00%00%00%00
csr-active-config    g%00%00%00
fakesmc-key-$Num-ui8    %01
fakesmc-key-MSFW-ui8    %01%00
fakesmc-key-MSPS-ui16    %00%03
fakesmc-key-REV -ch8*    %026%0f%00%00%97
fmm-computer-name    chendequan%e2%80%99s MacBook Pro
backlight-level    %00%00
bootercfg    (%00
fakesmc-key-$Adr-ui32    %00%00%03%00
fakesmc-key-EPCI-ui32    %09 %f0%00
bluetoothActiveControllerInfo    o!\%0a%00%00%00%00`%14%c4%8e%8f%fb%dd%98
fakesmc-key-MSAc-ui16    %00%00
fakesmc-key-MSLD-ui8    %00
SystemAudioVolume    %00
specialbootdevice    %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%02%00%00%00%00%00%04%01*%00%02%00%00%00%00H%0b%00%00%00%00%00%e0%a8,%0b%00%00%00%00%ed%90%85E)%81XG%81%c1%b0%b6pP%86R%02%02%7f%ff%04%00
fakesmc-key-RMde-char    A
fakesmc-key-BBIN-ui8    %01
flagstate    %00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
fakesmc-key-MSWr-ui8    %00

After remove CMOS battery, should I reset BIOS again?
delete all mac NVRAM variables is hard to me.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top