D-an-W Posted October 30, 2016 Share Posted October 30, 2016 Should I be able to update Clover that is installed to the ESP once FV2 is enabled as currently when I try it installs it to the root of the booted drive? Link to comment Share on other sites More sharing options...
smolderas Posted October 30, 2016 Share Posted October 30, 2016 Should I be able to update Clover that is installed to the ESP once FV2 is enabled as currently when I try it installs it to the root of the booted drive? It is a completely different volume, so yes. Link to comment Share on other sites More sharing options...
dgsga Posted October 30, 2016 Share Posted October 30, 2016 I have found the same issue too. The Clover installer when run on an encrypted FV2 volume installs to the root partition and not the EFI partition... 1 Link to comment Share on other sites More sharing options...
vit9696 Posted October 30, 2016 Author Share Posted October 30, 2016 You need to update clover installer scripts in a similar way to current rc scripts: https://sourceforge.net/p/cloverefiboot/code/3860/ And submit a patch to slice to get it added to trunk. Link to comment Share on other sites More sharing options...
Slice Posted October 30, 2016 Share Posted October 30, 2016 Yes. EDIT: Do I see it wrong or is UsbKbDxe placed in drivers64 for legacy boot? What sense does that make? Just replace the TianoCore one in the DUET image, that will solve the issue of having to reconnect the keyboard on every boot... The work in progress. Legacy boot Clover contains a driver BiosKeyboard witch is not ready yet for FV2. But I didn't propose to replace it with UsbKbDxe because the last one is not working with PS2 keyboard. Link to comment Share on other sites More sharing options...
mhaeuser Posted October 30, 2016 Share Posted October 30, 2016 The work in progress. Legacy boot Clover contains a driver BiosKeyboard witch is not ready yet for FV2. But I didn't propose to replace it with UsbKbDxe because the last one is not working with PS2 keyboard. Nevermind, it has been done by now, seems like the users were using an old Clover build. Link to comment Share on other sites More sharing options...
mrmacdi2 Posted October 30, 2016 Share Posted October 30, 2016 So, just to clarify to be sure that I understand everything right: in case I have Clover in legacy mode (BIOS + clover on ESP) on my laptop (PS2 kb) , do I need to install UsbKbDxe&HashServiceFix-64.efi? Link to comment Share on other sites More sharing options...
mhaeuser Posted October 30, 2016 Share Posted October 30, 2016 So, just to clarify to be sure that I understand everything right: in case I have Clover in legacy mode (BIOS + clover on ESP) on my laptop (PS2 kb) , do I need to install UsbKbDxe&HashServiceFix-64.efi? HashFix is only for AMI Aptio... for UsbKbDxe, if I'm reading the code right, you should not need to install it separately, but I am not using Clover, so cannot confirm. EDIT: Nvm, HashFix is for any firmware not implementing the Hash protocol for SHA1. Link to comment Share on other sites More sharing options...
mrmacdi2 Posted October 30, 2016 Share Posted October 30, 2016 Thx, works just fine OOB on PC. Link to comment Share on other sites More sharing options...
Slice Posted October 31, 2016 Share Posted October 31, 2016 I am not sure HashServiceFix is really needed. I seems have success without it. Link to comment Share on other sites More sharing options...
vit9696 Posted October 31, 2016 Author Share Posted October 31, 2016 At this point HashServiceFix is indeed optional. What it does is: a) Overwrites broken SHA1 hash implementation if it finds it; Installs new SHA1 hash implementation if nothing is found. This allows boot.efi to access more files in FirmwareVolume and thus request SHA1(ArrowCursor_2x) file, which is for HDPI screens. If no file was found, then the default cursor image will be used. For this reason it is currently optional, however, there is no proof that it is not going to change soon. Link to comment Share on other sites More sharing options...
mrmacdi2 Posted October 31, 2016 Share Posted October 31, 2016 Unfortunately, on my laptop USB kb is not working - tried Logitech and A4tech standart keyboards: not possible to enter the pass. But caps lock and num lock work: indicators on my laptop are changing, so kb is connected... Link to comment Share on other sites More sharing options...
Slice Posted October 31, 2016 Share Posted October 31, 2016 Unfortunately, on my laptop USB kb is not working - tried Logitech and A4tech standart keyboards: not possible to enter the pass. But caps lock and num lock work: indicators on my laptop are changing, so kb is connected... Did you use this new UsbKbDxe? Link to comment Share on other sites More sharing options...
mrmacdi2 Posted October 31, 2016 Share Posted October 31, 2016 I'm using UsbKbDxe from Clover 3882 package. The same clover 3882 legacy is installed on my hackintosh PC and it works fine - I unlock FV2 w/o any problems. P.S. Additionally Ctrl-Alt-Del works - it reboots my laptop Link to comment Share on other sites More sharing options...
vit9696 Posted October 31, 2016 Author Share Posted October 31, 2016 Added a new AptioInputFix version: — fixed numpad keys (might require enabled numlock in bios); — added a workaround for keyrepeat and missed keys, should work with Clover's AppleKeyAggregator now (will require at least Partial Usb Initialisation in Fast Boot section); — fixed rare system startup freezes; — improved z87 mouse behaviour. 1 Link to comment Share on other sites More sharing options...
jqqqqq Posted November 1, 2016 Share Posted November 1, 2016 I'm using UsbKbDxe from Clover 3882 package. The same clover 3882 legacy is installed on my hackintosh PC and it works fine - I unlock FV2 w/o any problems. P.S. Additionally Ctrl-Alt-Del works - it reboots my laptop I tried all of these efis above, and UsbKbDxe found in clover work for my external keyboard, you have to unplug and plug in again to make it work still waiting for internal ps2 keyboard working 1 Link to comment Share on other sites More sharing options...
oSxFr33k Posted November 1, 2016 Share Posted November 1, 2016 With AptioInputFix do I just need to remove UsbKbDxe-64.efi or I can have both in drivers64UEFI? If I need to remove it are there any others to remove that the newer versions of clover installs. Not using FV Thanks Link to comment Share on other sites More sharing options...
savvas Posted November 1, 2016 Share Posted November 1, 2016 With new version of AmiShim, I got to work all hotkeys (cmd+s/cmd+r/cmd+v/shift) Link to comment Share on other sites More sharing options...
vit9696 Posted November 1, 2016 Author Share Posted November 1, 2016 With AptioInputFix do I just need to remove UsbKbDxe-64.efi or I can have both in drivers64UEFI? If I need to remove it are there any others to remove that the newer versions of clover installs. Not using FV Thanks You should remove UsbKbDxe and only that. With new version of AmiShim, I got to work all hotkeys (cmd+s/cmd+r/cmd+v/shift)Nice, looks like it was accidentally broken in the previous one. 1 Link to comment Share on other sites More sharing options...
mrmacdi2 Posted November 1, 2016 Share Posted November 1, 2016 I tried all of these efis about, and UsbKbDxe found in clover work for my external keyboard, you have to unplug and plug in again to make it work still waiting for internal ps2 keyboard working I've unplugged and plugged it many times: tried different usb ports, even via usb hub Caps lock, num lock, Ctrl alt del work thats it.Can it happen because my laptop has Phoenix TrustCore bios? In Clover GUI this usb kb works fine. Link to comment Share on other sites More sharing options...
jqqqqq Posted November 1, 2016 Share Posted November 1, 2016 I've unplugged and plugged it many times: tried different usb ports, even via usb hub Caps lock, num lock, Ctrl alt del work thats it. Can it happen because my laptop has Phoenix TrustCore bios? In Clover GUI this usb kb works fine. AppleImageCodec-64.efi HashServiceFix-64.efi NTFS.efi AppleKeyMapAggregator.efi OsxAptioFix2Drv.efi AppleUITheme-64.efi OsxFatBinaryDrv-64.efi AptioInputFixB2.efi PartitionDxe-64.efi DataHubDxe-64.efi SMCHelper-64.efi UsbKbDxe-64.efi FSInject-64.efi FirmwareVolume-64.efi HFSPlus.efi i put all of these efis into clover, and it works..... it won't work without usbkbdxe though i don't know if there're conflicts, but my internal keyboard cannot work properly BTW, my laptop is Phoenix BIOS too Link to comment Share on other sites More sharing options...
Slice Posted November 1, 2016 Share Posted November 1, 2016 I think AptioInputFix will not be even started on Phoenix BIOS. Link to comment Share on other sites More sharing options...
mrmacdi2 Posted November 1, 2016 Share Posted November 1, 2016 AppleImageCodec-64.efi HashServiceFix-64.efi NTFS.efi AppleKeyMapAggregator.efi OsxAptioFix2Drv.efi AppleUITheme-64.efi OsxFatBinaryDrv-64.efi AptioInputFixB2.efi PartitionDxe-64.efi DataHubDxe-64.efi SMCHelper-64.efi UsbKbDxe-64.efi FSInject-64.efi FirmwareVolume-64.efi HFSPlus.efi i put all of these efis into clover, and it works..... it won't work without usbkbdxe though i don't know if there're conflicts, but my internal keyboard cannot work properly BTW, my laptop is Phoenix BIOS too I have the same except for NTFS.efi.BTW on my PC the same config with the same USB kb works fine with FV2. Looks like Phoenix and Phoenix TrustedCore are really different things. Link to comment Share on other sites More sharing options...
mrmacdi2 Posted November 3, 2016 Share Posted November 3, 2016 [GUIDE] How to revert FileVault 2 if you are not able to enter your password: for example, USB keyboard is not working. 1. Boot into Recovery HD (where you can restore macOS, have Disk Utility) 2. Select Terminal (top menu) 3. diskutil corestorage list 4. Look for Logical Volume XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXXXXXX and copy XXX...XXXX (NOT from Logical Volume Family!) 5. diskutil corestorage unlockVolume UUID (paste copied UUID from step 4) 6. diskutil corestorage revert UUID (paste copied UUID from step 4) 7. 7.1) If it's your first boot after you've enabled FileVault 2, then type reboot in Terminal and boot macOS as usual. 7.2) If it's NOT the first boot after you've enabled FileVault 2, then diskutil corestorage list and check conversion status, type reboot ONLY when diskutil corestorage list shows you NO encrypted volumes! Done 4 Link to comment Share on other sites More sharing options...
Slice Posted November 3, 2016 Share Posted November 3, 2016 Since rev 3905 hibernation works on FileVault2 volume. In this case password is not asked. Explanations followed. Link to comment Share on other sites More sharing options...
Recommended Posts