Slice Posted December 29, 2016 Share Posted December 29, 2016 The message usually appears when you boot other system with other password. It sees other volume which requires password you didn't enter yet. Link to comment Share on other sites More sharing options...
kernelpanicd Posted December 29, 2016 Share Posted December 29, 2016 The message usually appears when you boot other system with other password. It sees other volume which requires password you didn't enter yet. I'm not sure I understand this. "diskutil corestorage list" only shows 1 volume which is encrypted/requires password. Are you saying I might have entered the wrong password? Link to comment Share on other sites More sharing options...
smolderas Posted December 29, 2016 Share Posted December 29, 2016 I'm not sure I understand this. "diskutil corestorage list" only shows 1 volume which is encrypted/requires password. Are you saying I might have entered the wrong password? Did you by any chance change your password mid encryption of the disk? Link to comment Share on other sites More sharing options...
bs0d Posted December 29, 2016 Share Posted December 29, 2016 still no credits ok enjoy. 1 Link to comment Share on other sites More sharing options...
kernelpanicd Posted December 29, 2016 Share Posted December 29, 2016 Did you by any chance change your password mid encryption of the disk? I did not. The steps were 1. Turn on FileVault 2 in Preferences 2. It reboots 3. Enter password (booting OS from Recovery partition as it should) 4. Get that error from verbose log Link to comment Share on other sites More sharing options...
superkurz Posted January 23, 2017 Share Posted January 23, 2017 Hey folks! First of all: thank you so much for all your work so far. Unfortunately i can not get FV2 working. My machine: Intel i3-3100, 16GB RAM, 512 GB SSD, Gigabyte GA-110M-S2H Mainboard with a AMI UEFI BIOS Here is what i did: Fresh OSX El Capitan install, everything working fine, no problems. All USB ports working. Updated Clover to the newest version (downloaded from Sourceforge) Reboot back into the System, mount the EFI partition, copied the AptioInputFix.efi to the drivers folder (see Pic1), reboot again Enable Filevault2, system goes for a reboot but then it crashes and get this stop sign thingy.... (i booted with -v for log) (see Pic2 + 3) From googling i think it is some typ of USB issue. I tried booting with the keyboard (Original Apple USB Keyboard) in different USB ports and always rebooted, but nothing worked. Any ideas? Link to comment Share on other sites More sharing options...
Slice Posted January 23, 2017 Share Posted January 23, 2017 Try to use UsbKbDxe.efi instead of InputAptioFix because you have USB keyboard. Link to comment Share on other sites More sharing options...
vit9696 Posted February 12, 2017 Author Share Posted February 12, 2017 AptionInputFix was updated in the first message with a version with debug messages disabled. Thanks go to @savvas. 2 Link to comment Share on other sites More sharing options...
D-an-W Posted February 12, 2017 Share Posted February 12, 2017 Cheers vit9696 (& savvas!), Is it just a case of renaming AsAmiShim.efi to AptionInputFix.efi or is renaming not required? Link to comment Share on other sites More sharing options...
TheRacerMaster Posted February 12, 2017 Share Posted February 12, 2017 You shouldn't need to rename anything. 1 Link to comment Share on other sites More sharing options...
vit9696 Posted February 12, 2017 Author Share Posted February 12, 2017 TL;DR TheRaceMaster is right, any name would do. AsAmiShim is the original codename and the project name. I forgot to rename the files in the archive for consistency but whatever they are the driver would work fine. 1 Link to comment Share on other sites More sharing options...
eelet Posted February 20, 2017 Share Posted February 20, 2017 Hi everyone, i succesfully enabled FV2 on my Asus F750LN Notebook (from Signature), I'm currently running Clover 2.4k r4012, i post also a screenshot of my drivers64UEFI folder. It works all pretty good, except i get some graphical issues (e.g. debug code) into the Login Screen. Can you help me to solve it please? I can currently access to macOS, however i found some bugs in AptioInputFix (Inverted CMD button, when i insert my password i have to Release Shift Key to get Upper-Case chars and i have to insert it very slowly because double-letters don't works if i do it fast). So i can accept this bugs, but what means is to solve these Graphical Issues on Login Screen. Secure boot is enabled in uefi and works with no problem. You made a very good work! Congrats guys Link to comment Share on other sites More sharing options...
Slice Posted February 21, 2017 Share Posted February 21, 2017 I see no Graphical issue on your attached picture. Link to comment Share on other sites More sharing options...
eelet Posted February 21, 2017 Share Posted February 21, 2017 You right sorry, i post photos of the graphical issue on login screen Link to comment Share on other sites More sharing options...
Slice Posted February 21, 2017 Share Posted February 21, 2017 Looks like you didn't install SMCHelper.efi? Link to comment Share on other sites More sharing options...
eelet Posted February 21, 2017 Share Posted February 21, 2017 Slice look at the image attached in post #87, i have it! Link to comment Share on other sites More sharing options...
eelet Posted February 21, 2017 Share Posted February 21, 2017 Is there any chance to fix the issue? Link to comment Share on other sites More sharing options...
Slice Posted February 22, 2017 Share Posted February 22, 2017 Is there any chance to fix the issue? Try to boot without verbose and without KextPatches debug. I don't remember why the messages was appeared and I have no more testing machine. Link to comment Share on other sites More sharing options...
eelet Posted February 22, 2017 Share Posted February 22, 2017 Ok with no verbose on boot i don't get this messages on FV2 Login Screen, hovewer is there a Graphical Issue after i insert my password, but i can accept this as compromise. You know if the KextPatches for IntelFrameBufferAzul are the same between El Capitan and Sierra? Maybe it can depends from it? Link to comment Share on other sites More sharing options...
smolderas Posted February 22, 2017 Share Posted February 22, 2017 Ok with no verbose on boot i don't get this messages on FV2 Login Screen, hovewer is there a Graphical Issue after i insert my password, but i can accept this as compromise. You know if the KextPatches for IntelFrameBufferAzul are the same between El Capitan and Sierra? Maybe it can depends from it? That graphical issue exists on real Macs too IMHO. You could use following kext patch, which helped me in Sierra: <dict> <key>Comment</key> <string>Boot screen fix</string> <key>Find</key> <data>AQAAdSU=</data> <key>Name</key> <string>IOGraphicsFamily</string> <key>Replace</key> <data>AQAA6yU=</data> </dict> Link to comment Share on other sites More sharing options...
eelet Posted February 22, 2017 Share Posted February 22, 2017 Thanks smolderas, i try it now and i come back to report! EDIT: Always same graphical issue after password insert, no debug codes but the background of Sierra become like a mosaic, however when it loads and i enter on macOS no problems! Link to comment Share on other sites More sharing options...
stemayer Posted February 23, 2017 Share Posted February 23, 2017 I think I am missing some of the basics here. Where can I find the EFI files mentioned in the original post? What is the UsbKbDxe and where does it go? Thanks, Steve Link to comment Share on other sites More sharing options...
Slice Posted February 24, 2017 Share Posted February 24, 2017 I think I am missing some of the basics here. Where can I find the EFI files mentioned in the original post? What is the UsbKbDxe and where does it go? Thanks, Steve In the Clover official package. Link to comment Share on other sites More sharing options...
savvas Posted February 26, 2017 Share Posted February 26, 2017 You right sorry, i post photos of the graphical issue on login screen If you want to hide boot.efi debug messages – disable verbose boot mode Link to comment Share on other sites More sharing options...
Slice Posted February 26, 2017 Share Posted February 26, 2017 If you want to hide boot.efi debug messages – disable verbose boot mode There is another question, why those SMC are needed? Link to comment Share on other sites More sharing options...
Recommended Posts