Jump to content

vit9696

Developers
  • Content count

    413
  • Joined

  • Last visited

  • Days Won

    24

vit9696 last won the day on September 20

vit9696 had the most liked content!

About vit9696

  • Rank
    InsanelyMac Sage

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. vit9696

    Clover problems report & features request

    — Doctor, doctor, it hurts when I do like this, please help me. — Alright, do not do it like this, and it will not hurt Really, if you have some hidden love in FV2 drivers, it could be understood, but the only thing you do is taking devs' time trying to understand wtf your issue is. Do not use the drivers until you really need FV2. End of the story.
  2. vit9696

    AptioMemoryFix

    Your BIOS does not have NVRAM variable whitelist, so the problem is elsewhere. Most likely in some BIOS configuration (check AptioMemoryFix github README for recommendations) or in your hardware. For example, there were precedents of boards with <= 4 GB of RAM having not working NVRAM on APTIO V due to memory allocation problems.
  3. vit9696

    FileVault 2

    The lastest AptioInputFix and AppleUiSupport from master (pre-release versions one should compile oneself) provide support for certain laptops, which previously had issues reaching the login ui. Should be thanking bratwurstinhalator, who worked hard with me and Savva to nail the issue down. AptioInputFix (planned to be released under R24 tag) got the first large update after two years, which is intended to fix missed keys on APTIO V and UEFI Shell. As a side change AptioInputFix got generic input protocol support (SimpleTexInput and SimpleTextInputEx), which was necessary for virtual machine debugging. While it means that practically any machine with any UEFI firmware can work with AptioInputFix, just like with AptioMemoryFix, non-APTIO firmwares are supported unintentionally. Use at your own risk and submit patches if something is broken.
  4. vit9696

    AptioMemoryFix

    STLVNUB, do not post nonsense when you are unaware of the basics. It confuses people to the very least. ellaosx, name your board and link to the bios, might check a patch for it in the future.
  5. vit9696

    VirtualSMC — SMC Emulator

    This is your magic formula: 1. Always stay with the latest binary releases of all kexts 2. Do not download or upload binary releases yourself 3. Let the official binary releases stay for a day or two before updating all kexts If you are building from master, well, you are supposed to know a word or two how macOS kernel drivers work, how to read logs, how to troubleshoot your system. The reason for this should be troubleshooting some bug or implementing a new feature. The latter ie expected from any person making oneself a hackintosh, in case you are unqualified and are not interested in educating, http://store.apple.com is your friend. Or at least do not whine about things .
  6. vit9696

    Clover problems report & features request

    Thanks for the signal. Indeed it was logical to remove AppleEvent protocol support from Clover, as it is not "core" functionality and is supposed to be provided by FV2 drivers. I guess Apple changed something and it is now unfortunately required even for a normal boot. I reverted some of the changes to make Clover install dummy AppleEvent if no other implementation is present. Let me know whether it works. AppleEventFallback.zip
  7. vit9696

    VirtualSMC — SMC Emulator

    @fabiosun, try increasing the timeout in code.
  8. vit9696

    AppleALC — dynamic AppleHDA patching

    @jaymonkey, I can confirm that your problem is similar. But most likely different in its cause. I changed the way Lilu reports device information, and ask you to redo the log. Also, unfortunately a lot of information is missing from the log, so try liludelay=1000 and record a video of the screen. Upload here or just PM.
  9. vit9696

    FileVault 2

    Yes, that should do the trick in Dell. To be completely sure it may be worth running drivers in UEFI Shell and checking the list for BIOS[INT 10] entry. It should disappear. Our main idea with Savva now is to apply several patches on boot.efi (Clover supports making them on the fly) to see where exactly it hangs by e.g. forcing an instant reboot. Will you be around for an hour or two to run these tests? Also, I think it is best to move to PM not to distract other people.
  10. vit9696

    FileVault 2

    Erm, a quick glance at your EFI folder shows that you have 3 input drivers at once. That will not work (as stated in the first message). Remove: AppleKeyFeeder.efi, AptioInputFix-64.efi Also remove other stuff: DataHubDxe-64.efi, Fat-64.efi, FSInject-64.efi, NvmExpressDxe-64.efi. Additionally remove BooterConfig from your config.plist, which is a misunderstanding of how the variable works. Not promising for anything to fix, but that is certainly a required change necessary to be done first of all.
  11. vit9696

    FileVault 2

    Hmm, So we are at a step where we need to rethink everything and debug the problem more precisely. I got most from Savva, but let us clarify some stuff: — The problematic machine is the one from your signature Dell XPS 13 9360. — You have macOS 10.13.6 build 17G65 (somewhat important) with a File Vault 2 encryption enabled. — Your current Mac model is MacBookPro13,1 and in drivers64UEFI you only have VirtualSmc.efi, AppleUiSupport.efi, AptioMemoryFix.efi, VboxHfs.efi and nothing else. In fact, it may be reasonable to upload the EFI folder in case something important has been forgotten about. — What you see when you have -v in boot arguments is this: https://www.insanelymac.com/forum/uploads/monthly_2018_09/IMG_20180902_114418.jpg.bd05843bdfec9814658b5e3aa23adbb5.jpg. I.e. Start LoginWindowInitialize is the last message, and nothing happens afterwards, it just hangs like that until you force shutdown/reboot. — You had never seen the EFI login user interface previously on that machine. — Resetting NVRAM did not help to the problem. Answering these questions may be obvious and annoying, but it may help us ensure we work with we assume. Thanks. Afterwards I think we should try debugging, and a good start will be to try the Clover and driver Savva has just attached.
  12. vit9696

    AppleALC — dynamic AppleHDA patching

    fusion71au, are you sure that both alc-layout-id and layout-id are necessary? If that is the case, I suspect that I know what the issue is all about. The property reader/writer fails, and you have to manually simulate it via device properties. What is most likely the cause of a failure, is a bug in Lilu, which caused device detection failure, and effectively prevented all the device discovery: https://github.com/acidanthera/Lilu/commit/7eab62a9c4ed56b2a1375f530f8c981dd44f2fa0 Does upgrading to master Lilu version work? With just layout-id set to 7, and alc-layout-id removed. If it does not, then I would like to a have your ioreg and a log with -liludbg liludelay=1000 (the boot process will be slow) that will contain all the pci device detection code (i.e. "creating device info" message and onwards). You may obtain it with the following command after booting; log show --info --debug --last boot | grep Lilu If the message I mentioned is dropped, you may consider recording the video.
  13. vit9696

    VirtualSMC — SMC Emulator

    SMC dumps have nothing to do to VirtualSMC functioning. Thy are mainly reference material to the research to help us make improvements of the emulated keys. Obviously, only real macs are of interest.
  14. vit9696

    VirtualSMC — SMC Emulator

    Same thing, as lid switch (MSLD) is implemented in SMCLightSensor based on light sensor input.
  15. vit9696

    VirtualSMC — SMC Emulator

    Slice, uwat, how are developers related to users not reading FAQs? Just that borked user has ACPI0008 (Light Sensor device) present in system, which resulted in AppleSMCLMU.kext matching against that device and demanding SMC keys for LightSensor. However, SMCLightSensor.kext plugin was not installed, and the thus the keys are missing, reporting SmcKeyNotFound. Why should developers be responsible for users not even understanding what they have onboard.
×