Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About smolderas

  • Rank
    InsanelyMac Sage

Profile Information

  • Gender
  1. FileVault 2

    Let me get back to you on that tomorrow. I’m not on my computer right now.
  2. FileVault 2

    I can’t read Russian and I’m not using clover menu, just fast booting. what should I check?
  3. FileVault 2

    I meant from the EFI console. /dev/disk6 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +119.8 GB disk6 Physical Store disk2s2 1: APFS Volume Macintosh HD 98.0 GB disk6s1 2: APFS Volume Preboot 43.1 MB disk6s2 3: APFS Volume Recovery 1.0 GB disk6s3 4: APFS Volume VM 24.6 KB disk6s4 I must say, MacOS updates won't complete. I always need to choose "Preboot to macOS install" to complete the macOS updates. Here is some more detailed output: APFS Container (1 found) | +-- Container disk6 AA7592E9-ED6D-4EF7-B7DE-E78931D69CF6 ==================================================== APFS Container Reference: disk6 Size (Capacity Ceiling): 119824367616 B (119.8 GB) Minimum Size: 120075382784 B (120.1 GB) Capacity In Use By Volumes: 99079000064 B (99.1 GB) (82.7% used) Capacity Not Allocated: 20745367552 B (20.7 GB) (17.3% free) | +-< Physical Store disk2s2 159588F2-432D-4C37-A81C-5B788C3AA48A | ----------------------------------------------------------- | APFS Physical Store Disk: disk2s2 | Size: 119824367616 B (119.8 GB) | +-> Volume disk6s1 C035E33B-7D9E-44C0-82FA-9868355B0AA4 | --------------------------------------------------- | APFS Volume Disk (Role): disk6s1 (No specific role) | Name: Macintosh HD (Case-insensitive) | Mount Point: / | Capacity Consumed: 97871056896 B (97.9 GB) | FileVault: Yes (Unlocked) | +-> Volume disk6s2 8272592C-D1D9-4315-85E5-FBD28A73FDF0 | --------------------------------------------------- | APFS Volume Disk (Role): disk6s2 (Preboot) | Name: Preboot (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 43134976 B (43.1 MB) | FileVault: No | +-> Volume disk6s3 734D0FC9-1C30-4C06-AC88-036BAC0A294E | --------------------------------------------------- | APFS Volume Disk (Role): disk6s3 (Recovery) | Name: Recovery (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 1038520320 B (1.0 GB) | FileVault: No | +-> Volume disk6s4 DF8560DE-6A29-40BF-9E8C-645941F0737B --------------------------------------------------- APFS Volume Disk (Role): disk6s4 (VM) Name: VM (Case-insensitive) Mount Point: /private/var/vm Capacity Consumed: 24576 B (24.6 KB) FileVault: No
  4. FileVault 2

    I could help you, if you tell me how to list them up...
  5. Clover General discussion

    Yeah, I conditioned that with my previous command "svn up edk2", so it didn't copied over. I removed the condition and it build... Thanks
  6. Clover General discussion

    Is this known: clover/src/edk2/MdeModulePkg/Library/DxeCapsuleLibNull/DxeCapsuleLibNull.inf [X64] [CC] DxeCapsuleLibNull [CC] AuthVariableLibNull [CC] TpmMeasurementLibNull [CC] DxeServicesTableLib [CC] InternalGetSpinLockProperties clover/src/edk2/MdePkg/Library/UefiLib/UefiLib.c:1530:19: error: passing an object that undergoes default argument promotion to 'va_start' has undefined behavior [-Werror,-Wvarargs] VA_START (Args, Iso639Language); ^ clover/src/edk2/MdePkg/Library/UefiLib/UefiLib.c:1517:19: note: parameter of type 'BOOLEAN' (aka 'unsigned char') is declared here IN BOOLEAN Iso639Language, ^ [CC] RuntimeLib 1 error generated. make: *** [clover/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiLib/UefiLib/OUTPUT/UefiLib.obj] Error 1 build.py... : error 7000: Failed to execute command make tbuild [clover/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiLib/UefiLib] build.py... : error F002: Failed to build module clover/src/edk2/MdePkg/Library/UefiLib/UefiLib.inf [X64, XCODE8, RELEASE] - Failed - Build end time: 16:49:23, Apr.13 2018 Build total time: 00:00:44 Somehow I can't edit my previous reply. I'm with NASM_VER: 2.13.03, edk2 @26797 and clover @4439
  7. Core Graphics should be running. Are you using your graphics card properly, or just some VMware driver for your VM?
  8. Clover General discussion

    Even though I don't think it is necessary, I did rebuild cache. It doesn't work with this message: 4:005 0:000 === [ StartLoader ] ======================================= 4:005 0:000 Finally: ExternalClock=25MHz BusSpeed=100294kHz CPUFreq=4300MHz PIS: hw.busfrequency=100000000Hz 4:005 0:000 Loading boot.efi status=Success 4:079 0:074 GetOSVersion: 10.13.3 (17D102) 4:079 0:000 Filtering KextPatches: 4:079 0:000 - [00]: com.apple.iokit.IOGraphicsFamily (Boot screen fix) :: BinPatch :: [OS: 10.13.3 | MatchOS: All | MatchBuild: All] ==> allowed 4:079 0:000 Will not patch boot.efi 4:079 0:000 EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success
  9. Clover General discussion

    It says that, but does it really patch? The following doesn't work anymore after r4291 (I think)... <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>Boot screen fix</string> <key>Find</key> <data>AQAAdSI=</data> <key>Name</key> <string>com.apple.iokit.IOGraphicsFamily</string> <key>Replace</key> <data>AQAA6yI=</data> </dict> </array>
  10. shutdown and sleep problem

    I found the culprit (at least mine). It was the GenericUSBXHCI.kext, which prevented shutdown for me...
  11. Try this defaults -currentHost write -globalDomain AppleFontSmoothing -int 3 Don't forget to logoff or better restart.
  12. Clover General discussion

    Thanks for the advice, I was just curious to read out the version.. According to specification, the drivers (should) have versions...
  13. Clover General discussion

    It is possible to print out the versions of loaded drivers in LoadDrivers() too?
  14. shutdown and sleep problem

    I have the same issue and it is new with the latest update (or before that). Up until that point shutdown worked correctly here...
  15. 1G Network-Ethernetcard (PCIe) for El Capitan

    Such issue tend to get fixed with a bios update from the vendor, if you haven't already report it.