Jump to content
vit9696

Lilu — kext and process patcher

356 posts in this topic

Recommended Posts

Advertisement

I installed Lilu 1.21 and intelgraphicsfixup to clover/oem/vendor/kext/othe. If I activated intel hd4600 next to my nvidia 1050ti i bios settings and then added "-igfxoff" to boot args, the intel gfx still is listed as cuda device in luxmark in 10.13.2. So disabling does not work. I see that the kext is loaded in kextstat.

 

Why?

 

EDIT: If I put lilu and intelgrpahicsfixup into /L/E instead, same result.

 

EDIT: Do I have to use -liluforce for 10.13.2?  Why is the github page not hosting lilu v1.2.2?

 

EDIT: Sorry, had the wrong ig-platform-id in my dsdt, thought that clover would overwrite it. That was not the case.

Share this post


Link to post
Share on other sites

So.... latest Lilu give fatal CPU fault on 10.12.3 beta 4, anyone running into this issue?

Latest Lilu (1.2.1 & 1.2.2), AppleALC (1.2.2), & WhateverGreen (1.1.4) worked perfectly at either DP or HDMI port at 10.13.1, 10.13.2, & 10.13.3.

But it got blank screen of AMD R9 290X GPU at DP port at previously working 10.10.5, 10.11.6, & 10.12.6 in my P6TSE hackintosh.

Rolling back to previous versions of Lilu/AppleALC/WEG can not fix it yet by CLOVER r.4359 or r.4369.

Thanks for vit9696 again !

 

[solved by myself]

1. AMD R9 290X GPU only working at HDMI port at 10.10.5, 10.11.6, & 10.12.6 in my P6TSE hackintosh, not working at DP port.

2. HDMI audio working again at 10.12.6, but not working at 10.10.5 or 10.11.6.

Edited by jsl

Share this post


Link to post
Share on other sites

The crash is caused by a memory corruption in Intel GPU acceleration DRM key/certificate handling code. Therefore, only Ivy+ GPUs are affected.

 

Are you 100% sure it is only affecting Ivy and Sandy? Because if I use my haswell igpu hd4600 with connector-full next to nvidia gpu, there will be a hard crash/reset in Final Cut. I have seen these patches do not match for haswell igpu... Or is this problem unrelated?

Share this post


Link to post
Share on other sites

Hi.

 

I am having trouble  with Kernel Panics after updating macOS Sierra 10.12.6 to the latest security update patch from the app store today.

 

So, Cyberdev told me that there was a new version of Lilu availaible. I also updated NvidiaGraphicsFixup.kext since I use a GTX 560 TI. ALC and FakeSMC were up to date already.

But I still got kernel panics. So I removed nvidiagraphicsfixup.kext and booted without nvidia drivers. That worked, So then I could update to the latest webdrivers (Version 378.05.05.25f06). 

 

 

Now I have the latest webdrivers installed but I cannot use NvidiaGraphicsFixup.kext because it results in kernel panics:

 

https://www.dropbox.com/s/na4vw2n3d9e4o1o/panic3.jpg?dl=0

 

Next, I tried using NVWebDriverLibValFix.kext again instead, which I used before, but that fix/kext doesn't work any more... the GPU just turns off after boot.

 

These are the Kexts I currently use:

 

https://www.dropbox.com/s/hndg0zomj9eq6cx/Kexts.png?dl=0

 

I don't know what to do, can you see what the problem is? Do I need that whatevergreen.kext?

 

Any help would be highly appreciated!

Share this post


Link to post
Share on other sites

Hi @vit9696,

With Xcode 8.2.1 uder OS X 10.11.6 I got this warning:

Unused Entity Issue:
~/Projects/XCode/Lilu-master/Lilu/Headers/kern_iokit.hpp:187:9: Unused variable 'name'

(Refers to this):
#187: auto name = service->getName(); //Unused variable 'name'

But Lilu.kext built succeeded. Thanks  :)

 

#EDIT: a same warning with AppleALC build, but I could ignore it.

Share this post


Link to post
Share on other sites

Is it possible to use Lilu for code injection? Ala CydiaSubstrate for iOS? It'd be enough to be able to provide a dynamic library that can be loaded into all processes and have its __attribute__((constructor)) called

Share this post


Link to post
Share on other sites

Hi, what do you need this functionality for?

In brief, it is possible and the code for this exists, yet primarily in private as a part of the project Lilu codebase is based on. Some parts were published with Shiki, some others found its way to the latest Lilu release. You in fact do not even need a dylib with Lilu, since everything could be done entirely in memory.

As I said, a reasonably large codebase (userspace sdk) remains private for several reasons. It is a discussible question whether it should be published or not, so I would like to hear the reasons you need this in detail.

Share this post


Link to post
Share on other sites

Hi!

Thanks for replying so quickly. I think the use cases for such an SDK are wide. You can find precedent of it if you search for the large community which formed around the Unsanity Haxie tools for 10.4 which provided code injection and an API to replace functions at runtime.

Personally, I have a number of projects which are in great need of a platform to handle injection and code replacement. You may refer to AutumnBoard (https://github.com/alexzielenski/AutumnBoard) - a tool to replace system app, extension, etc. icon files at runtime allowing for a rich packaged theming API. Unfortunately, development was dropped as the tools being used for code injection became outdated. Additionally there is dockify (https://github.com/alexzielenski/dockify_library) - a library which if developed fully could allow customization of dock appearance.

A system-wide runtime theming library could easily be achievable with your system. Note that many tweaks would require injection into processes filterable by bundle identifier, frameworks loaded, process name, or a wildcard.

Many other possibilities exist for patches of OS X user space functionality large and small. For instance, one might opt to remove the feature of OS X which lower's system audio during a FaceTime call; and can easily do so with a patch like this: https://github.com/ParasiteTeam/crucible/blob/master/examples/com.apple.audio.CoreAudio/SpeakerTime.plist if there was a stable code injection platform. The addition of this SDK would create a community of tweak developers not too different from that which formed around the iOS jailbreak scene.

Extensions which could probably be ported immediately include and any SIMBL bundle that was created for OS X. You may ask what benefit this product could offer over SIMBL bundles?

1. SIMBL does not allow you to filter by library/framework. (though; admittedly this could be added to its injection process)

2. SIMBL requires an agent which receives late notifications of process events (in many applications of code injection tweaks it is crucial to inject early into process lifetime)

3. SIMBL can only filter against Cocoa UI applications - (headless or terminal applications are not able to be injected into)

4. SIMBL does not include a standardized code replacement SDK

 

You mentioned that a dylib is not required since patches could be done in memory with a Lilu plugin, but I think it would be best load dylibs and keep the 3rd party code running in userland which does not need kernel privileges.

The best way to implement a system like this would be as a separate Lilu plugin, which would act as a trampoline for a dynamically loaded plugin system retrieving filters from user space or the filesystem.

Edited by jivhg

Share this post


Link to post
Share on other sites

Thanks for the links and notes. Just as you said, the use cases for such functionality could broadly vary.

4 years ago, when AppleALC was not even planned, Lilu prototype was actually a modern replacement to SIMBL. However, when it comes to software modification there are two points to think about:

  1. Security
  2. Target audience

SIMBL was pretty impressive several years ago, where numerous developers created their extensions to patch different things. Later on their enthusiasm disappeared, and even though SIMBL still works on modern macOS versions (with some hacks and SIP workarounds), its userbase is largely dead. Basically the same with Cydia Substrate and Jailbreak itself, which no longer belong to the common sense.

More than that, SIMBL or a working Lilu-based solution with a SDK opens a possibility for malware writers and similar shady people to write harmful software at no effort. And that's if we forget about other possible bugs.

Regarding the "kernel privileges and stuff". We followed the exact model you described during the creation of an initial prototype of MiniSubstrate with 07151129. And it was badly wrong. Making it possible to let the user to dynamically load an extension during the system runtime causes an extreme security risk, having a plugin management system injected in every process is an additional risk to system stability, and a possibility to swap one dylib with another is another great security risk. The only way it could actually appear (and is actually implemented in Lilu) is to have a kext that is bundled with all the extensions with a defined process list, which is only loaded at boot time. If you think of it, this is similar to how Cydia Substrate works with a 'respring'. Do not take me wrong though, obviously nobody executes any code with kernel privileges, it uses app privileges and is no different from any other dylib. As a bonus this approach is in fact more performant.

All in all, while I still consider a possibility of this project going live, I remain unconvinced about the existence of an audience, which would actually write useful plugins. Perhaps, more actual projects and demand could work better here, but such a revival will take time.

Share this post


Link to post
Share on other sites
On 1/11/2018 at 12:28 PM, jsl said:

Latest Lilu (1.2.1 & 1.2.2), AppleALC (1.2.2), & WhateverGreen (1.1.4) worked perfectly at either DP or HDMI port at 10.13.1, 10.13.2, & 10.13.3.

But it got blank screen of AMD R9 290X GPU at DP port at previously working 10.10.5, 10.11.6, & 10.12.6 in my P6TSE hackintosh.

Rolling back to previous versions of Lilu/AppleALC/WEG can not fix it yet by CLOVER r.4359 or r.4369.

Thanks for vit9696 again !

 

[solved by myself]

1. AMD R9 290X GPU only working at HDMI port at 10.10.5, 10.11.6, & 10.12.6 in my P6TSE hackintosh, not working at DP port.

2. HDMI audio working again at 10.12.6, but not working at 10.10.5 or 10.11.6.

My Intel HD 4600 and AMD RX 560 worked at 10.13.4 and 10.13.5 beta1 (15F35e), but got blank screen from RX 560 after updated to 10.13.5 beta2 and beta3.

Another issue was related to versions of Lilu/AppleALC/WhateverGreen.kext:

only Lilu & AppleALC (1.2.1) with WhateverGreen (1.1.2) worked at 10.13.4 & 10.13.5 beta1, newer versions still got blank screen from RX 560.

 

After repeated testing with different versions of WhateverGreen.kext I found that WEG version 1.1.5, 1.1.6 or 1.1.7 got blank screen from AMD RX 560 if Intel HD 4600 enabled at BIOS. Lilu (1.2.3) & AppleALC (1.2.6) are compatible with WEG (1.1.2 or 1.1.3) in my hackintosh.

Only version 1.1.3 or 1.1.2 got normal display from both AMD RX 560 and Intel HD 4600 at 10.13.4 & 10.13.5 beta1(10.13.5 beta 2 & 3 will broke it again !).

Edited by jsl2000
More testing with different versions

Share this post


Link to post
Share on other sites

Hi @vit9696 and everyone! Many thanks all for your continuing support on these kexts.

 

I originally wanted to ask you @vit9696 for your comment/support on your GitHub but saw your message there and thought of starting off here. First of all, please take some time to update the URLs in your automated message as the one pointing to "Lilu and its plugins" is not valid :D

 

I accidentally discovered last year your IntelGraphicsFixup kext that I started using together with AppleALC and Lilu, of course, when you switched to it some time ago. As I am using HD5000 it was handy for the boot glitch and those problems with Safari and video playback that you seem to have resolved (Safari was getting sluggish).

 

Recently, I am having my screen going randomly black -- monitor seems to lose sync, as I see on my Dell the icon for the port, meaning a signal was lost for a moment. I was trying to see since when this started, I suspect the latest Security Update 2018-003 or with Clover r4558. Not sure.

 

Running Sierra 10.12.6 with Security Update 2018-003 on my Intel NUC D54250WYKH and latest (today) Clover r4586; most of my fixes are patched AML files, my Intel HD 5000 Graphics [8086:0a26] is declared as 0x0a26000d (desktop) and my config.plist has no kext patches at all (i.e. no "boot glitch fix"). Finally, I use Lilu v1.2.3 and AppleALC v1.2.7 together with IntelGraphicsFixup v1.2.7 (that I removed, for now) all three placed in /Library/Extensions/ that ran fine until recently.

 

If I update to Lilu v1.2.4 do you think it may prove to be useful? What kind of logs/output do you think you may require to better identify the issue? I cannot say that monitor going black is reproducible as it's random, not sure even if it's related to Safari (I think not) as it happened when I had rebooted, too.

 

Thank you again for your time, if anyone encountered the same issue, your kind feedback/assistance is appreciated!

K.

 

 

Edited by MacKonsti

Share this post


Link to post
Share on other sites

Hi,

 

Regarding the links, it is kind of hard to keep everything in sync, so any pull requests will be welcome.

Regarding the signal loss, it is most likely a hardware issue or a new problem that is not addressed by the kexts <which I do not plan to research at the moment>. One thing to suggest is to make sure you do NOT use GuC (igfxfw=1 boot arg). At the moment it causes a lot of issues. Other than that I have few ideas.

 

Vit

Share this post


Link to post
Share on other sites
59 minutes ago, vit9696 said:

Regarding the signal loss, it is most likely a hardware issue or a new problem that is not addressed by the kexts <which I do not plan to research at the moment>. One thing to suggest is to make sure you do NOT use GuC (igfxfw=1 boot arg). At the moment it causes a lot of issues. Other than that I have few ideas.

I sure hope not a H/W problem with my NUC :D:D

OK I have updated both Lilu and AppleALC to latest, and reverted IntelGraphicsFixup tho the one available (from April). Rebooted and will see what happens.

No, I am not using any boot args, my setup is pretty much vanilla (even my config.plist) as most simple fixes are done as DSL/AML files in "patched" folder of Clover (studied @RehabMan and @sebinouse posts and Git files, when I got this older but compatible NUC last year).

Any ideas to investigate and report, are welcome! Many thanks again, mate.

 

config-2018-06-24.plist

Edited by MacKonsti

Share this post


Link to post
Share on other sites

Hi @vit9696,

Sorry, I got strange behavior with Lilu (plus it's PlugIns) under OS X El Capitan 10.11.6 (15G22010) if I boot with Clover UEFI << but with Legacy they're working just fine (10.11.6 && 10.14 Beta have no issue). It seems, Lilu is not loaded on my UEFI-system that prevents AppleALC to be loaded as well:

 

Spoiler

Last login: Fri Jul 13 13:23:55 on console
MacBookPro:~ badruzeus$ cat /private/var/log/system.log | egrep "Lilu|AppleALC"
Jul 13 13:23:21 localhost kernel[0]: Kext as.vit9696.AppleALC - library kext as.vit9696.Lilu not found.
Jul 13 13:23:21 localhost kernel[0]: Can't load kext as.vit9696.AppleALC - failed to resolve library dependencies.
Jul 13 13:23:21 localhost kernel[0]: Kext as.vit9696.AppleALC failed to load (0xdc00800e).
Jul 13 13:23:21 localhost kernel[0]: Failed to load kext as.vit9696.AppleALC (error 0xdc00800e).
Jul 13 13:23:21 localhost kernel[0]: Couldn't alloc class "AppleALC"
MacBookPro:~ badruzeus$ kextstat | egrep "Lilu|AppleALC"
MacBookPro:~ badruzeus$
MacBookPro:~ badruzeus$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.11.6
BuildVersion:	15G22010
MacBookPro:~ badruzeus$ bdmesg
.....  .....  ...
0:100  0:000  Starting Clover revision: 4598 on American Megatrends EFI
0:100  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/badruzeus/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.11.6 | XCODE: 8.2.1]
......  .....  ...
6:944  0:000  Boot redirected to Entry 1. 'OS X El Capitan'
6:944  0:000  EmuVariable UninstallEmulation: CloseEvent = Success, original var services restored
6:944  0:000  DefaultIndex=1 and MainMenu.EntryCount=12
7:067  0:123  GUI ready
24:207  17:140   boot with args: -liludbgall nvda_drv=1 -v 
24:208  0:000  Boot option Boot0000 not found
24:208  0:000  === [ StartLoader ] =======================================
24:208  0:000  Finally: ExternalClock=25MHz BusSpeed=99774kHz CPUFreq=2195MHz PIS: hw.busfrequency=100000000Hz
24:208  0:000  Loading boot.efi  status=Success
24:405  0:197  GetOSVersion: 10.11.6 (15G22010)
......  .....  ...
24:451  0:000  Beginning FSInjection
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 217CE18
24:465  0:013  Use origin smbios table type 1 guid.
24:465  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.11
24:465  0:000  Extra kext: EFI\CLOVER\kexts\10.11\RealtekRTL8111.kext (v.2.2.2)
24:514  0:048  Extra kext: EFI\CLOVER\kexts\10.11\IOath3kfrmwr.kext (v.1.2.1)
24:556  0:042  Extra kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext (v.1787)
24:625  0:068    |-- PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\LPCSensors.kext (v.1787)
24:832  0:207    |-- PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\GPUSensors.kext (v.1787)
24:860  0:027    |-- PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\CPUSensors.kext (v.1787)
24:881  0:020    |-- PlugIn kext: EFI\CLOVER\kexts\10.11\FakeSMC.kext\Contents\PlugIns\ACPISensors.kext (v.1787)
24:913  0:032  Extra kext: EFI\CLOVER\kexts\10.11\CodecCommander.kext (v.2.6.3)
24:962  0:048  Extra kext: EFI\CLOVER\kexts\10.11\CalDigitUSBxHCI.kext (v.1.3.8a2)
25:005  0:042  Extra kext: EFI\CLOVER\kexts\10.11\CalDigitFastIO.kext (v.2.6.1)
25:022  0:017  Extra kext: EFI\CLOVER\kexts\10.11\AsusACPIBackLightPanel.kext (v.1.7)
25:043  0:020  Extra kext: EFI\CLOVER\kexts\10.11\ApplePS2SmartTouchPad.kext (v.4.6.8)
25:156  0:112    |-- PlugIn kext: EFI\CLOVER\kexts\10.11\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Keyboard.kext (v.4.6.8)
25:187  0:031    |-- PlugIn kext: EFI\CLOVER\kexts\10.11\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Controller.kext (v.4.6.8)
25:210  0:023  Extra kext: EFI\CLOVER\kexts\10.11\AppleALC.kext (v.1.3.0)
26:408  1:197  Extra kext: EFI\CLOVER\kexts\10.11\ACPIBatteryManager.kext (v.1.81.4)
26:462  0:054  Custom boot screen not used because entry has unset use graphics

 

I attached my prebuilt Lilu && AppleALC (debug versions) plus preboot.log below. Thanks.

Lilu_AppleALC_dbg_A43SJ.zip

 

#EDIT: I use these /drivers64uefi (whole EFI Folder is on my sig):

 

AppleImageCodec-64.efi
AppleKeyAggregator-64.efi
AppleUITheme-64.efi
CsmVideoDxe-64.efi
DataHubDxe-64.efi
EmuVariableUefi-64.efi
FirmwareVolume-64.efi
FSInject-64.efi
OsxAptioFixDrv-64.efi
PartitionDxe-64.efi
SMCHelper-64.efi
VBoxHfs-64.efi

 

Edited by Badruzeus

Share this post


Link to post
Share on other sites
On 7/13/2018 at 1:53 PM, Badruzeus said:

Hi @vit9696,

Sorry, I got strange behavior with Lilu (plus it's PlugIns) under OS X El Capitan 10.11.6 (15G22010) if I boot with Clover UEFI << but with Legacy they're working just fine (10.11.6 && 10.14 Beta have no issue). It seems, Lilu is not loaded on my UEFI-system that prevents AppleALC to be loaded as well:

Oh, got it. I think the problem is from my EFI Partition; Fyi my Disk was converted to GPT from MBR using 3rd party app w/o reinstalling OS X (10.11.6). Then, I manually created 200MB EFI using gParted and set it as "boot, esp". gDisk seen my partition map as Pure GPT already, then macOS 10.14 was installed afterward. Sorry for confusing, I did some tests with creating Clover UEFI over USB, boot from it.. and got no issue at all with Lilu & PlugIns. Thanks anyway. :)

Share this post


Link to post
Share on other sites

Hi @vit9696, can Lilu patch info.plist? I have two info.plist patch in Clover, used to disable Apple's I2C kexts to load. But Clover can't patch kexts in recovery or installation, so I want to write a plugin to do that.

Share this post


Link to post
Share on other sites

@vit9696 hi.

i want to clean info for intelframebuffer of each gen in clover.

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/IntelFramebuffer.bt

can i use this in terminal for each framebuffer target?

 

previously, i followed cecekpawon's script for framebuffer in clover.

https://github.com/cecekpawon/OSXOLVED/blob/master/yod-GPUFramebuffers.php

 

thanks in advance

Share this post


Link to post
Share on other sites
1 hour ago, vit9696 said:

Hi, you need 010 Editor (https://www.sweetscape.com/010editor/) to run this script on each framebuffer kext. And for 10.14+ framebuffers you need to dump them first via -igfxdump boot argument via WhateverGreen.

 

okay. sorry friendly this program. first, open bt file in 010 editor and f7, join file. then open AppleIntelFramebuffer_8_18.0

but i didn't see any clean result.

 

also here is log on my system.

Sherlocksui-MacBook-Pro-2:~ sherlocks$ log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot
Filtering the log data using "process == "kernel" AND (composedMessage CONTAINS "WhateverGreen" OR composedMessage CONTAINS "Lilu")"
Skipping info and debug messages, pass --info and/or --debug to include.
Timestamp                       (process)[PID]    
2018-07-18 22:39:03.978102+0900  localhost kernel[0]: calling mpo_policy_init for Lilu
2018-07-18 22:39:03.978107+0900  localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.2.5 DEBUG build (Lilu)
2018-07-18 22:39:04.021559+0900  localhost kernel[0]: (kernel) WhateverGreen:     rad @ (DBG) not enabling CAIL_DisableDrmdmaPowerGating
2018-07-18 22:39:04.021565+0900  localhost kernel[0]: (kernel) WhateverGreen:     rad @ (DBG) not enabling CAIL_DisableGfxCGPowerGating
2018-07-18 22:39:04.021570+0900  localhost kernel[0]: (kernel) WhateverGreen:     rad @ (DBG) not enabling CAIL_DisableUVDPowerGating
2018-07-18 22:39:04.021574+0900  localhost kernel[0]: (kernel) WhateverGreen:     rad @ (DBG) not enabling CAIL_DisableVCEPowerGating
2018-07-18 22:39:04.021578+0900  localhost kernel[0]: (kernel) WhateverGreen:     rad @ (DBG) not enabling CAIL_DisableDynamicGfxMGPowerGating
2018-07-18 22:39:04.021583+0900  localhost kernel[0]: (kernel) WhateverGreen:     rad @ (DBG) not enabling CAIL_DisableGmcPowerGating
2018-07-18 22:39:04.021587+0900  localhost kernel[0]: (kernel) WhateverGreen:     rad @ (DBG) not enabling CAIL_DisableAcpPowerGating
2018-07-18 22:39:04.021591+0900  localhost kernel[0]: (kernel) WhateverGreen:     rad @ (DBG) not enabling CAIL_DisableSAMUPowerGating
2018-07-18 22:39:04.021598+0900  localhost kernel[0]: (kernel) WhateverGreen:   shiki @ (DBG) pre-config: online 0, bgra 0, compat 0, whitelist 0, id 0, stream 0
2018-07-18 22:39:04.098092+0900  localhost kernel[0]: (kernel) Lilu:     api @ force enabling NoTouchID (100) on an unsupported operating system due to beta flag
2018-07-18 22:39:04.225800+0900  localhost kernel[0]: (kernel) Lilu:     api @ force enabling BT4LEContiunityFixup (110) on an unsupported operating system due to beta flag
2018-07-18 22:39:04.250495+0900  localhost kernel[0]: (kernel) Lilu:     api @ force enabling AirportBrcmFixup (113) on an unsupported operating system due to beta flag
2018-07-18 22:39:11.277607+0900  localhost kernel[0]: (kernel) Lilu:    file @ VNOP_WRITE failed 14!
2018-07-18 22:39:11.277614+0900  localhost kernel[0]: (kernel) Lilu:    file @ failed to write /AppleIntelFramebuffer_8_18.0 file of 2166784 size
2018-07-18 22:39:11.277622+0900  localhost kernel[0]: (kernel) WhateverGreen:    igfx @ dumping framebuffer information to /AppleIntelFramebuffer_8_18.0
2018-07-18 22:39:11.277633+0900  localhost kernel[0]: (kernel) WhateverGreen:    igfx @ (DBG) Patching framebufferId 0x19160000 successful
2018-07-18 22:39:13.449851+0900  localhost kernel[0]: (kernel) WhateverGreen:     weg @ (DBG) failed to obtain display mode
2018-07-18 22:39:13.449869+0900  localhost kernel[0]: (kernel) WhateverGreen:     weg @ (DBG) failed to obtain display mode
2018-07-18 22:39:13.449876+0900  localhost kernel[0]: (kernel) WhateverGreen:     weg @ (DBG) failed to obtain display mode
2018-07-18 22:39:13.460326+0900  localhost kernel[0]: (kernel) WhateverGreen:    igfx @ (DBG) computeLaneCount: bpp = 24, available = 10
2018-07-18 22:39:13.489364+0900  localhost kernel[0]: (kernel) WhateverGreen:     weg @ (DBG) fb info 1: -2147479552:0 7680:0:32
2018-07-18 22:39:13.489372+0900  localhost kernel[0]: (kernel) WhateverGreen:     weg @ (DBG) fb info 2: 3:8 --------RRRRRRRRGGGGGGGGBBBBBBBB 0:1920:1080
2018-07-18 22:39:13.489397+0900  localhost kernel[0]: (kernel) WhateverGreen:     weg @ (DBG) attempting to copy...
2018-07-18 22:39:13.595898+0900  localhost kernel[0]: (kernel) WhateverGreen:    igfx @ (DBG) computeLaneCount: bpp = 24, available = 10
2018-07-18 22:39:13.637489+0900  localhost kernel[0]: (kernel) WhateverGreen:    igfx @ (DBG) computeLaneCount: bpp = 24, available = 10
2018-07-18 22:39:13.789014+0900  localhost kernel[0]: (kernel) WhateverGreen:    igfx @ (DBG) computeLaneCount: bpp = 24, available = 10

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically (see caveat below)
      - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can download the official release binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil IGPU = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Spoofing Intel CPU Gen
      If you need to spoof a different Intel CPU generation you can use the lilucpu=N boot flag. The N refers to the following Intel generations:
      4    SandyBridge 5    IvyBridge 6    Haswell 7    Broadwell 8    Skylake 9    KabyLake 10   CoffeeLake To spoof a CPU you will need to set a valid device-id in your GPU entry in Devices/Properties for the appropriate Intel generation.
       
      Eg. Spoofing Skylake (lilucpu=8 boot flag with device-id=0x16190000), Kaby Lake (lilucpu=9 boot flag with device-id=0x12590000).
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - S/L/E/AppleIntelSNBGraphicsFB.kext
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - device-id: 0x0102 0x0106 0x010A 0x0112 0x0116 0x0122 0x0126
      - AAPL,snb-platform-id (desktop): 0x00030010 (default)
      - AAPL,snb-platform-id (laptop): 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - S/L/E/AppleIntelFramebufferCapri.kext
      - Support started with OS X 10.8.x
      - device-id: 0x0152 0x0156 0x0162 0x0166
      - AAPL,ig-platform-id (desktop): 0x0166000A (default), 0x01620005
      - AAPL,ig-platform-id (laptop): 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - S/L/E/AppleIntelFramebufferAzul.kext
      - Support started with OS X 10.9.x
      - device-id: 0x0D26 0x0A26 0x0A2E 0x0D22 0x0412
      - AAPL,ig-platform-id (desktop): 0x0D220003 (default)
      - AAPL,ig-platform-id (laptop): 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - S/L/E/AppleIntelBDWGraphicsFramebuffer.kext
      - Support started with OS X 10.10.2
      - device-id: 0x0BD1 0x0BD2 0x0BD3 0x1606 0x160E 0x1616 0x161E 0x1626 0x1622 0x1612 0x162B
      - AAPL,ig-platform-id (desktop): 0x16220007 (default)
      - AAPL,ig-platform-id (laptop): 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - S/L/E/AppleIntelSKLGraphicsFramebuffer.kext
      - Support started with OS X 10.11.4
      - device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
      - AAPL,ig-platform-id (desktop): 0x19120000 (default)
      - AAPL,ig-platform-id (laptop): 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - S/L/E/AppleIntelKBLGraphicsFramebuffer.kext
      - Support started with macOS 10.12.6
      - device-id: 0x5912 0x5916 0x591B 0x591C 0x591E 0x5926 0x5927 0x5923 0x87C0
      - AAPL,ig-platform-id (desktop): 0x59160000 (default)
      - AAPL,ig-platform-id (laptop): 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - S/L/E/AppleIntelCFLGraphicsFramebuffer.kext
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - device-id: 0x3E9B 0x3EA5 0x3EA6 0x3E92 0x3E91 0x3E98
      - AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - AAPL,ig-platform-id (laptop): 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-camellia framebuffer-flags framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Framebuffer Dumps
      There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
       
      1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
       
      There are several ways of reading this dump:
      - Using 010 Editor along with the IntelFramebuffer.bt template
      - Using Hackintool File->Open menu
       
      2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
       
      There are several ways of reading this dump:
      - Using dump_platformlist.sh shell script
      - Using Hackintool File->Import->IOReg Dump menu
       
      3. Using Hackintool Framebuffer->macOS 10.14 menu
       
      Adjusting the brightness on a laptop
      1. Method 1
      Enable Clover DSDT fix AddPNLF. Enable SetIntelBacklight and SetIntelMaxBacklight. A specific value is not necessary - it will be automatically injected according to the processor installed.
      2. Method 2
      Use this ACPI table: SSDT-PNLF.dsl SSDT-PNLF.aml
      Do not use both methods at the same time!
       
      Digital Audio (HDMI / DVI / DP)
      To enable digital audio it is necessary to set the necessary properties and, usually, patch the connectors.
      To enable audio in general and HDMI in particular use WEG along with AppleALC.kext.
      On 10.10.5 and above, WEG automatically changes the connector-type of DP (00040000) to HDMI (00080000) if no custom patches are used.
      The actual connection may be of any type (HDMI / DVI / DP), but for the digital audio to function the connector-type must explicitly be HDMI.
       
      VGA support
      In most cases with Intel Skylake and newer it works by default.
      For Ivy Bridge and possibly other generations there are the options to patch your connectors with the following:
      06020000 02000000 30000000 // Option 1
      06020000 01000000 30000000 // Option 2
      On OS X 10.8.2 and newer it is impossible to have VGA on Ivy Bridge systems.
      Hot-plugging VGA usually does not work.
      In case this doesn't help - there are no other known solutions at this time.
       
      EDID
      EDID is usually correctly identified, so no actions are required. In rare cases, EDID needs to be injected manually.
      An EDID dump can be obtained, for example, with Linux. The correct EDID must be put into *AAPL00,override-no-connect* property for IGPU, where the second 0 stands for the display number.
      In some cases the EDID dump may be incompatible with macOS and leads to distortions. For some EDID in such cases you can use this script, which corrects a provided EDID and saves it to your desktop.
       
      HDMI in UHD resolution with 60 fps
      Add the enable-hdmi20 property to IGPU, otherwise you will get a black screen. Or instead of this property use the boot-arg -cdfon
       
      Disablng a discrete graphics card
      Add the disable-external-gpu property to IGPU. Or instead of this property, use the boot-arg -wegnoegpu
       
      Fix the invalid maximum link rate issue on some laptops (Dell XPS 15 9570, etc.)
      Add the enable-dpcd-max-link-rate-fix property to IGPU, otherwise a kernel panic would happen due to a division-by-zero. Or instead of this property, use the boot-arg -igfxmlr.
      You could also manually specify a maximum link rate value via the dpcd-max-link-rate for the builtin display.
      Typically use 0x14 for 4K display and 0x0A for 1080p display. All possible values are 0x06 (RBR), 0x0A (HBR), 0x14 (HBR2) and 0x1E (HBR3). If an invalid value is specified, the default value 0x14 will be used instead. If this property is not specified, same as above.  
      Fix the infinite loop on establishing Intel HDMI connections with a higher pixel clock rate on Skylake, Kaby Lake and Coffee Lake platforms
      Add the enable-hdmi-dividers-fix property to IGPU or use the -igfxhdmidivs boot argument instead to fix the infinite loop when the graphics driver tries to establish a HDMI connection with a higher pixel clock rate, for example connecting to a 2K/4K display with HDMI 1.4, otherwise the system just hangs (and your builtin laptop display remains black) when you plug in the HDMI cable.  
      1. General Notes
      For those who want to have "limited" 2K/4K experience (i.e. 2K@59Hz or 4K@30Hz) with their HDMI 1.4 port, you might find this fix helpful. For those who have a laptop or PC with HDMI 2.0 routed to IGPU and have HDMI output issues, please note that this fix is now succeeded by the LSPCON driver solution, and it is still recommended to enable the LSPCON driver support to have full HDMI 2.0 experience.  
      (You might still need this fix temporarily to figure out the connector index of your HDMI port. See the LSPCON section below.)
      LSPCON driver support to enable DisplayPort to HDMI 2.0 output on IGPU
      1. Brief Introduction
      Recent laptops (Kaby Lake/Coffee Lake-based) are typically equipped with a HDMI 2.0 port. This port could be either routed to IGPU or DGPU, and you can have a confirmation on Windows 10. Intel (U)HD Graphics, however, does not provide native HDMI 2.0 output, so in order to solve this issue OEMs add an additional hardware named LSPCON on the motherboard to convert DisplayPort into HDMI 2.0.
      LSPCON works in either Level Shifter (LS) or Protocol Converter (PCON) mode. When the adapter works in LS mode, it is capable of producing HDMI 1.4 signals from DisplayPort, while in PCON mode, it could provide HDMI 2.0 output. Some onboard LSPCON adapters (e.g. the one on Dell XPS 15 9570) have been configured in the firmware to work in LS mode by default, resulting a black screen on handling HDMI 2.0 connections.
      Starting from version 1.3.0, WhateverGreen now provides driver support for the onboard LSPCON by automatically configuring the adapter to run in PCON mode on new HDMI connections, and hence solves the black screen issue on some platforms.
       
      2. Before you start
      LSPCON driver is only applicable for laptops and PCs with HDMI 2.0 routed to IGPU. LSPCON driver is necessary for all newer platforms unless the new IGPU starts to provide native HDMI 2.0 output. Supported Intel Platform: Skylake, Kaby Lake, Coffee Lake and later.
      Skylake Case: Intel NUC Skull Canyon; Iris Pro 580 + HDMI 2.0 with Parade PS175 LSPCON.
      Coffee Lake Case: Some laptops, e.g. Dell XPS 15 9570, are equipped with HDMI 2.0 and Parade PS175 LSPCON. If you have confirmed that your HDMI 2.0 is routed to IGPU and is working properly right now, you don't need to enable this driver, because your onboard LSPCON might already be configured in the firmware to work in PCON mode.
      3. Instructions
      Dump your kernel log and you should also be able to see something simillar to lines below.
       
      // When you insert the HDMI 2.0 cable igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a868c000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Returns 0x0. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a869a000. igfx @ (DBG) SC:   LSPCON::probe() DInfo: [FB2] Found the LSPCON adapter: Parade PS1750. igfx @ (DBG) SC:   LSPCON::probe() DInfo: [FB2] The current adapter mode is Level Shifter (DP++ to HDMI 1.4). igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver has detected the onboard chip successfully. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver has been initialized successfully. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x01. igfx @ (DBG) SC: LSPCON::setMode() DInfo: [FB2] The new mode is now effective. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] The adapter is running in preferred mode [Protocol Converter (DP++ to HDMI 2.0)]. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Returns 0x0. // When you remove the HDMI 2.0 cable igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a868c000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Returns 0x0. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a869a000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver (at 0xffffff802ba3afe0) has already been initialized for this framebuffer. igfx @ (DBG) SC: LSPCON::setModeIfNecessary() DInfo: [FB2] The adapter is already running in Protocol Converter (DP++ to HDMI 2.0) mode. No need to update. igfx @ (DBG) SC: LSPCON::wakeUpNativeAUX() DInfo: [FB2] The native AUX channel is up. DPCD Rev = 0x12. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Returns 0x0. Additionally, you can find these properties injected by the driver under the corresponding framebuffer.
      (Only available in DEBUG version)
       
      fw-framebuffer-has-lspcon indicates whether the onboard LSPCON adapter exists or not.
      fw-framebuffer-preferred-lspcon-mode indicates the preferred adapter mode. 1 is PCON, and 0 is LS.
       
      Debug Output
      To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be located at /var/log/Lilu_*.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt Getting Help

      To help the users of this forum diagnose issues with your configuration please generate a Lilu debug log and then run gen_debug.sh to generate a folder of debug files you can attach to a forum post requesting help.

      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By monw3d
      hey everybody
       
      as title said lilu causing very long boot 5-6 mins on SSD
      my EFI is up to date and set properly, only usb3 not working looking for kext
       
      OS 10.14.5
      my mobo p61a-d3 with i5 2400
      when -liluoff is used bood time is under 30 seconds
       
      i have tried lilu 1.2.6 to 1.3.3 same results
       
      how can i get lilu bootlog?
      i dont know how to solve this problem
       
      edit - usb3 fixed and working
    • By noisegate
      Hi,
       
      I use AppleALC v1.3.5, I can see the device in system info but no sound. Any idea?
       
      Thanks!
       
    • By olvko
      As I found no binary kext for DiskArbitrationFixup Lilu plugin from https://github.com/Goldfish64/DiskArbitrationFixup, I compiled current version. Attached below, as it may be useful for other people.
       
      This Lilu plug-in disables error "The disk you inserted was not readable by this computer" after macOS boot in case you have eg. Linux partitions in the same computer.
       
      Compiled under macOS 10.14.3 without debugging symbols against Lilu 1.3.4 headers. Requires Lilu.kext (https://github.com/acidanthera/Lilu) alongside to work.
       
      I do not give any warranty for its work and I am not an author of original code.
      DiskArbitrationFixup-08032019.zip
    • By poles89
      Hi guys,
       
      Though native graphics acceleration is supported on i3 from Mojave, I'm not able to manage to get it.
       
      This is my system configuration :
      Motherboard:  Asus Prime H370-Plus
      CPU: i3-8100 (UHD 630)
      OS: Mojave 10.14.2
       
      I'm trying every possible way to get full graphics acceleration. But whatever I try it shows only 4MB video memory or leads to Kernal Panic. Here are some ways I have tried so far:
       
      Prerequisites: 
      Installed latest Lilu+WEG on L/E. set DMVT prealloc to 64MB on bios.  
      Option 1: IntelGFX-> 0x3E928086, ig-platform-id-> 0x3E9B0007, Inject Intel = true. Output:  Kernal Panic
      Option 2: Blank IntelGFX, blank ig-platform-id, Inject Intel = false Output:  Kernal Panic
      Option 3:  IntelGFX-> 0x3E928086, ig-platform-id-> 0x5912000, Inject Intel = true.  Output: Booted Successfully but no graphics acceleration.
                     I knew that ig-platform-id-> 0x5912000 doesn't work in mojave and its works only for high sierra but I set this because with this ig-platform-id I can boot. Another way I can boot it by
                     setting invalid Fake IntelGFX value like 0x12345678.
      Option 4:  Downloaded Intel FBPatcher & followed this guide. But as I opened the app, its shows like this:
       
                     
                    
                     It clearly indicates it neither can detect Intel CPU generation nor GPU memory (currently shows 0 MB). I changed to different PlatformId from the drop down but no improvement. Anyway I
                     applied a patch with SMBIOS ->Macmini8,1 by someione's recommendation . I attached a config file (config_fbpather.plist) for this. Output:  Kernal Panic
       
      I have tried the upper mentioned methods with SMBIOS like  iMac14,2 / iMac18[1,2,3]  and Macmini8,1. I'm using HDMI port for display output. Now I don't know whats wrong with theses methods but maybe someone can help me to figure out this problem. I have also attached those config.plist files.
       
      Thanks in advance.
       
      config_fakeid_0x3E928086.plist
      config_fbpatcher.plist
      config_fbpatcher_with_device_id.plist
      config_platform-id_0x59120000.plist
×