Administrators Bronxteck Posted July 25, 2018 Administrators Share Posted July 25, 2018 for wifi you could probably just use the lilu plugin instead of fakepcid. that's what I use on my broadcom wifi. to figure out your chipset you can try using DPCIManager app Link to comment Share on other sites More sharing options...
tikizondo94 Posted July 25, 2018 Author Share Posted July 25, 2018 Well Ive been playing around with the new WhateverGreen and Lilu methods, and adding flags to the Devices/Properties section. Ive had alot of help over at IM. Still though im unable to get QE/CI working. For some reason WhateverGreen still shows in debugging logs that its try for 59178086 PlatformID. Which is not an OSX ID. So im still stuck at this point. Ive attached a copy of my current clover. This thing has been a real pain. lol. l CLOVER 3.zip Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted July 25, 2018 Administrators Share Posted July 25, 2018 yes there have been daily changes with concern to the lilu project. have you considered just doing a fresh install on a test drive with your latest changes. Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted July 25, 2018 Moderators Share Posted July 25, 2018 Had you tried patching the LVDS port to eDP? Name: com.apple.driver.AppleIntelKBLGraphicsFramebuffer comment: change LVDS to eDP find : 02 00 00 00 98 00 00 00 to replace: 04 00 00 00 98 00 00 00 Link to comment Share on other sites More sharing options...
tikizondo94 Posted July 25, 2018 Author Share Posted July 25, 2018 @Jake Lo Does kext to patch in KBL framebuffer still work with the latest 10.14 beta and the new WhateverGreen And lilu.kexts? Or do i have to do it within Devices/Properties? Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted July 25, 2018 Administrators Share Posted July 25, 2018 most likely in device properties now of clover config but I think according to the Russian link about WEG... WEG might automatically use HDMI or LVDS for eDP I have been following your progress at IM. Link to comment Share on other sites More sharing options...
tikizondo94 Posted July 25, 2018 Author Share Posted July 25, 2018 Now its figuring out how to add the correct properties in Devices/Properties to set the patch lol. Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted July 25, 2018 Administrators Share Posted July 25, 2018 did you look at the clover gen-config plist let it regenerate with your current config to see if you see your device id in it you can also try one with 0x12345678 and see if you see it then pass that on to your current config with the device id you wish to test it might be bit flipped you can use calculator app in programmer mode in hex mode or just reread the hardcode patching here https://www.insanelymac.com/forum/topic/334899-guide-intel-framebuffer-patching-for-mojave/ I guess you add it to second line Link to comment Share on other sites More sharing options...
tikizondo94 Posted July 26, 2018 Author Share Posted July 26, 2018 Heres the generated config clover output for me. It did add a few different properties in Devices/Properties. config-generate.plist.zip Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted July 26, 2018 Administrators Share Posted July 26, 2018 <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data> AAAWWQ== </data> <key>framebuffer-con0-enable</key> <data> AQAAAA== </data> <key>framebuffer-con0-flags</key> <data> kAAAAA== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> </dict> </dict> AAAWWQ== EQUALS 00001659 is that correct? Link to comment Share on other sites More sharing options...
Recommended Posts