boot stuck with latest BIOS 309

[LeeBinder]

[solved]! Just download and apply the latest release from https://github.com/tctien342/Asus-Vivobook-S510UA-High-Sierra-10.13-Hackintosh

For details see here and f.f.

hey @tctien342 / saintno1997, how is it going.

Have you applied the latest BIOS yet? https://www.asus.com/vn/Laptops/ASUS-VivoBook-S15-S510UA/HelpDesk_BIOS/

I have --> stuck in boot: https://www.tonymacx86.com/threads/guide-new-voodooi2c-asus-vivobook-s15-x510uar-10-13.245445/page-39#post-1875587

regardless if with your latest hotpatch v.8 or original/ stock ReHabMan config_HD615_620_630_640_650.plist

What about you, either in High Sierra or in Mojave?

Greetings to Việt Nam
Lee/ B*gsB

Asus Vivobook S15 | I5 8250U + Intel UHD620 | x510UAR BIOS

[LeeBinder]

@tctien342 : I'm two steps further, see https://www.tonymacx86.com/threads/guide-new-voodooi2c-asus-vivobook-s15-x510uar-10-13.245445/page-39#post-1875587

[LeeBinder]

Another step further over at the tonymac thread: I attached the full debug_BIOS_308_GOOD.zip, + the manual_debug_BIOS_309_Black-Screen.zip with only the changed files, all other files already being present in debug_BIOS_308, so it's possible to have a look at what changed from 308 to 309 in the graphics related sections.

[LeeBinder]

I've done file-by-file diff compares of corresponding *.dsl pairs with Beyond Compare 308 --> 309.

Final findings:

DSDT: only two differences:

309, line 70 (added line):
External (_SB_.PCI0.GFX0.GLID, MethodObj) // 1 Arguments (from opcode)

then in both BIOSes, under Scope (_SB.PCI0.LPCB.EC0):

308, Line 40301:

Device (LID)
        {
            Name (_HID, EisaId ("PNP0C0D"))  // _HID: Hardware ID
            Method (_LID, 0, NotSerialized)  // _LID: Lid Status
            {
                Store (One, Local0)
                Store (RPIN (0x11), Local0)
                If (LEqual (Local0, Ones))
                {
                    Store (One, Local0)
                }

                Return (Local0)
            }
        }

was changed into
309, line 40263:

Device (LID)
        {
            Name (_HID, EisaId ("PNP0C0D"))  // _HID: Hardware ID
            Method (_LID, 0, NotSerialized)  // _LID: Lid Status
            {
                Store (One, Local0)
                Store (RPIN (0x11), Local0)
                If (LEqual (Local0, Ones))
                {
                    Store (One, Local0)
                }

                If (IGDS)
                {
                    ^^^^GFX0.GLID (Local0)
                }

                Return (Local0)
            }
        }

So all I see accdg. to Beyond Compare is a If (IGDS) condition inserted into Device (LID). Does that produce an incorrect lid state leading to a black screen?

Removed the 4 lines with the If (IGDS) condition, compiled, applied to Clover/ACPI/patched, rebooted --> black screen.

Applying the misc_LidPoll.txt work-around via MaciASL [misc] Poll for LID changes + ACPIPoller install --> reboot did NOT solve this, either.

[LeeBinder]

SSDTs: the 6 SSDTs SSDT-x.dsl and SSDT-x3_x.dsl are all exactly the same = did NOT change from 308 --> 309. Unless there is a graphics related change in one of the other SSDTs, ^^^^GFX0.GLID (Local0) is the culprit causing a black screen where the login screen should be, and simply commenting it out does not help any :roll2:

@tctien342 : any idea how to proceed from here?

[tctien342]

@LeeBinder yep, same result here =)), have to roll back 308 for work, seem to be firmware problem ? I'll try to fix it when free ! U can roll back by flash the bios file in bios EZ mode

[LeeBinder]

@tctien342 Glad you're still around :) Do you mean video/ graphics firmware? Separate from ACPI (DSDT, SSDTs etc.?)

[LeeBinder]

@tctien342 You might be absolutely right:

https://www.insanelymac.com/forum/topic/334899-intel-framebuffer-patching-using-whatevergreen/

https://www.insanelymac.com/forum/topic/335018-intel-fb-patcher-v168/

Yes, I have been back to 308 :) Good luck trying to fix this, it's beyond my scope :(

[tctien342]

@LeeBinder I think not the graphic problem, it about CPU power management problem, seem like only 10% of CPU have been use, very slow so that can't bootIn, if you boom to window the boot back to MacOS, it seem to be faster a little, enough for boot into screen but still suck!, using NullCPUPowerManagement can make it enough for web browsing... that all I found when in 309, will back to it in this weaken

[LeeBinder]

@tctien342 wow OK - with your findings things make more sense now.. I've been wondering why everything is slowed down and even sound stutters..

Very cool, you have a way better technical intuition for all this than I do. Awesome you'll be looking into it. So then, good luck with re-taming the CPU.

BTW someone over at baohiep's (hieplpvip) tonymac Zenbook thread updated his Zenbook to 309, and it's working without these issues..

(it really sucks they don't publish any BIOS update change log. Or you you know of any?)

[vasishath]

I am facing the same issue on my x510unr. Difference is I got this issue in bios version 308..

[LeeBinder]

@vasishath

1. what about BIOS 303 and 309?
2. which OS: 10.13.6 or 10.14.2?
3. have you rebooted with -f switch yet (Clover boot/ Options/ Enter/ End) -f --> Enter/ End/ Enter --> boot?
4. any difference when you apply NullCPUPowerManagement, reboot?

[vasishath]

1. My model got this update straight from 301 and 308 is the latest one currently.
2. 10.14.1
3. No changes with -f
4. I added nullintel also but no apparent different. I also have HWP enabled in my config.plist so I guess cpu pm is done inside cpu itself

Another thing I noted is if I somehow boot to desktop and try to change the brightness, it first shows a glitchy apple boot logo (with some artifacts from clover Xmas theme) and then logs out. Then I have to login again.

[LeeBinder]

Gotcha. Disable HWP, it does not help any. If this indeed is a power management bug, HWP might contribute to this bug.

[vasishath]

Oh.. I thought HWP is better. NVM will disable it. I think this is not a cpu only issue as brightness adjustment is also broken. I wonder if there is a graphics firmware in UEFI just like it bundles the Nvidia firmware..

[LeeBinder]

graphics firmware in UEFI: been wondering that myself..

[LeeBinder]

Hi @tctien342 . Did you have any chance and found out anything new about this?

[vasishath]

I found something new today. The screen is not frozen on apple logo.. the desktop is actually working but seems like the brightness for same is very less. One can see the desktop behind the apple logo.

[LeeBinder]

@vasishath : yes, I've been there. If you have an external monitor, plug it in, wait several seconds, unplug it - should should be fully there. But sluggish as hell.

@tctien342 : I think it would be wise to do these few edits on both, your readme here and on your tonymac topic:

1. Support: All BIOS
   -->
   Support: BIOS up to v.308 (working on 309 support)

and

Know problems:

1. BIOS 309 not supported yet (black login screen/ extreme system lag)

or something like that with your words

https://github.com/tctien342/Asus-Vivobook-S510UA-High-Sierra-10.13-Hackintosh/blob/master/README.md

https://www.tonymacx86.com/threads/guide-new-voodooi2c-asus-vivobook-s15-x510uar-10-13.245445/

Also I see your current release contains both, AptioMemoryFix-64.efi AND OsxAptioFixDrv-64.efi, even though AptioMemoryFix-64.efi is meant to REPLACE OsxAptioFixDrv-64.efi (never both together, can cause memory issues). I guess it slipped in accidentally with some Clover update. Best you remove OsxAptioFixDrv-64.efi from all places:

https://github.com/tctien342/Asus-Vivobook-S510UA-High-Sierra-10.13-Hackintosh/tree/master/EFI%20BQ414T/EFI/CLOVER/drivers64UEFI

https://github.com/tctien342/Asus-Vivobook-S510UA-High-Sierra-10.13-Hackintosh/tree/master/EFI%20OTHER/EFI/CLOVER/drivers64UEFI

Just curious, were you able to figure anything out yet about the 309 BIOS? If not, that's 100% fine, too. Just curious :)

[vasishath]

I am 99% sure this is a framebuffer issue..

[LeeBinder]

@vasishath @tctien342 : which would mean to apply the steps from https://www.insanelymac.com/forum/topic/334899-intel-framebuffer-patching-using-whatevergreen/

Unfortunately I have to study/ learn again, so if you want to go ahead.. the manual is very good.

[LeeBinder]

I just logged into my Asus account and sent a message to tech support, asking what exactly they changed from v.308 to v.309. Will share whatever they reply.

[vasishath]

I guess that won't work at all. Most of the support guys will hardly know what's a bios lol

[LeeBinder]

Need to fill out a form now for 2nd level tech support since 1st level as expected only has the info we have (internet). So something is happening :)

[LeeBinder]

Got a reply:

BIOS Version 309 | 2018/12/11 | 4.35 MBytes

Optimize system performance:

• Optimize post time
• Update Intel ME (Management Engine) firmware

No changes to HD 620 framebuffer. Optimize post time (the time the Laptop needs to turn on at the very beginning, right?) we can neglect, I would say. So @tctien342 , you are right about the firmware!

The Intel ME covers many modules, see https://en.wikipedia.org/wiki/Intel_Management_Engine#Firmware

What's possible is that 309 incorporated a buggy ME fw, and that by now Intel offered a more recent one, but that Asus is lagging behind. It is usually recommended to apply the always latest ME, not just for Windows and Linux but also for hackintosh, see here.

I'm out for winter vacation on Saturday and have tons of work until then so I don't have time to look into this right now, so here is a few links for any of you to follow:

Intel ME SA Detection Tools downloads

Intel Engine Firmware Analysis Tool (for MS Windows) by platomav (updated constantly)

Intel Engine Firmware Repositories

MEUpdateEasy by pal1000 (A script to ease the process of updating Intel ME firmware when)

That's all that's needed to get going - fingers crossed :)

[vasishath]

@LeeBinder great find. But before going any further there is one thing bugging me. Let's say we update to latest ME and then Asus launches another UEFI update but with the same older ME firmware. So will the downgrade process be fine ? I mean will it cause any issues ?

Edit: I updated my firmware successfully to latest v11.8 but still the issue persists :(

[vasishath]

And by the way I am really impressed with asus's tech support. I really didn't thought they would care to reply.

[vasishath]

And by the way I am really impressed with asus's tech support. I really didn't thought they would care to reply.

[LeeBinder]

And by the way I am really impressed with asus's tech support. I really didn't thought they would care to reply.

;) I used the shotgun principle: messages to Asus TW/ CN/ USA/ DE, all in both, English + native language translated via Google Translate. First received "we only know and see what you know and see" kinda replies, insisted on escalating the issue to 2nd level support and have them contact the appropriate compartment.

I let you guess which of the 4 native supporters actually did what I asked for and retrieved the answer :)

Edit: I updated my firmware successfully to latest v11.8 but still the issue persists :(

oh, bummer. Thanks for venturing ahead!

@vasishath , I would like to know: did you first check with platomav's Intel Engine Firmware Analysis Tool in Windows which 11.x IME FW your Vivobook was running with BIOS 308, and then with BIOS 309? Can you post the full numbers before and after comma?

[LeeBinder]

If the 308 and 309 IME versions are indeed different, does macOS behave normally when you flash IME 11.8 when running on BIOS 308?

Or the other way around, how does macOS behave when you flash the 308 IME version when running on BIOS 309?

We need to narrow down if this is indeed an IME issue. If it is, then we need to stick with the latest hackintosh compatible IME.

[vasishath]

My bios is 308 but I face same issue. I don't think my bios updated the ME firmware as when I initially checked with the SA00008 tool from Intel, it said my version was 11.7 which was vulnerable to security bugs discovered around 2017. After that, i found a me firmware updater from Asus which updated it to 11.8.50 (dont remember exact sorry). I rebooted after this but again it was the same.

Then I found a new version on winraid website which was 11.8.60. Updated to that firmware and rebooted again but same issue.

[LeeBinder]

@tctien342 OK

one more thing: in SMBIOS you now switched to MacBookPro11,1 (from originally 14,1 and with your current release 15,2). I have one purchased App registered with my 14,1 SN.

Can you share briefly which issues you have experienced with MacBookPro14,1, and if MacBookPro11,1 is mandatory for your config to work?

(wow, all switched to VirtualSMC + AsusSMC, very sweet 👍 🥇 )

[tctien342]

@LeeBinder switched to 11 fixed my slow password input, keep 14,1 still fine

[LeeBinder]

@tctien342 OK

Booted successfully, all looks very good! Will observe and report back to you.

Two suggestions:
in Clover/Boot,

• rename brcmfx-country=VN to brcmfx-country=
• add two more lines: -v so in case boot hangs, people can see why, and -f, so kext cache gets dropped (will prevent hang on 1st boot)

Have you found any tangible fan noise improvement with the ACPI-Poller kext ("developed to better control the system fan on HP 4x30s ProBook laptops") added? It's also rather old (2016-03-01).

### [EDIT] ###:

1. under Clover config/Devices, Add properties, have you seen all this Nvidia and ATI stuff? In your release(s) before, this section has been completely empty. Esp. all the ATi entries I guess can be removed (might possibly even cause some issues)?

2. Does HDMI audio still work? Can't test because don't have any device. I see some audio settings are not present anymore (use IntelHDMI, Inject: 3, ResetHDA). But maybe they are not necessary (anymore)?

3. what's your hibernatemode - 0,3, or 25? --> pmset -g
   Here are my values:

standby              1
 womp                 1
 halfdim              1
 hibernatefile        /var/vm/sleepimage
 proximitywake        1
 powernap             1
 gpuswitch            2
 networkoversleep     0
 disksleep            10
 standbydelayhigh     86400
 sleep                1 (sleep prevented by diskarbitrationd)
 autopoweroffdelay    28800
 hibernatemode        3
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         10
 highstandbythreshold 50
 standbydelaylow      10800
 hibernatemode        3

4. EDID injection: with this new release, have you tested if there is any effect on your Vivo if you injexct your EDID, or not? If there is a benefit in injecting, what is for you? (I never saw a difference maybe because my Vivo only has 1 GPU? But you were disabling the Nvidia if present anyway)

[leesureone]

@leesureone : I hope you haven't sold your Vivo yet (and won't for a little while)... can you please let me know if sound input works on yours with your EFI folder + kexts?

Yes, sound works.

[tctien342]

@LeeBinder
#1 this is test config so some un-needed properties still there
#2 HDMI audio work for me
#3 it 3 In my log
#4 still fine without EDID injection
The build I send to u not included SSDT GPU disabled, I will include it in commit build (SSDT-RP01_PEGP)

[LeeBinder]

OK.
Multiple sleep/ wake cycles by now in both, High Sierra and Mojave - no more KP's or black outs 👍🥇

Still, all former BIOS versions prove that our CPUs do NOT need TSC syncing. This was caused through a firmware update. As stated by others, in such a case a kext based approach like VoodooTSCSync should be looked at as a work-around. The solution would need to be as close to the firmware as possible, thus best via SSDT.

@tctien342 have you had a chance yet to re-generate the CPU SSDT for BIOS 309 without VoodooTSCSync active (I don't right now)

[arstasczak]

Had the same problem with my S510UN Vivo - with @tctien342 new EFI folder works perfect - finally I can use Mac OS as my daily OS, thank you so much :)

[LeeBinder]

@tctien342 @ALL: I've been wondering why trackpad motions and behavior are so terrible again and Beyond Compared yours and hieplpvip's VoodooI2C kexts. Results: both pairs (VoodooI2C.kext and VoodooI2CHID.kext respectively) are different, have different content incl. different binaries. Mind that hieplpvip did his own compile for Asus ELAN.

Also note that the 2.1.4 in general (regardless of Alexandre's or hieplpvip's) is still in beta phase and (apart from additional gestures) is inferior to Alexandre's 2.0.3 for our Asus ELAN 1300 in terms of smoothness. That's valid even for hieplpvip's compile which is somewhat better in regards to the scalable area but is still pretty bad. The Issues are (quoted from a post to Alexandre):

1. after any combined keyboard operation incl. a modifier key (cmd+ c copy, cmd + s save, cmd + x cut etc.), the mouse pointer is "paralyzed"/ like in stasis for maybe half a second (I think I read AlexandreD somewhere mentioning this is a unfortunate standard behavior of the MT driver? Or has this been fixed in the most current VoodooI2CHID?)

2. About 1/3 of the time, in a text file, instead of highlighting, the context menu appears, because the driver thinks I'm doing a double tap. "Click in bottom right corner" as secondary click instead is NOT an option.

Unfortunately Alexandre's 2.0.3 is NOT compatible with Mojave --> kernel panic, and accdg. to Alexandre would be way too much work to adapt for the latest macOS, therefore for Mojave, 2.1.4+ has to be used. Above listed annoying trackpad issues are the reason why I'm still using High Sierra as my main macOS !!!

Therefore for our Asus ELAN 1300 it is best to delete both VoodooI2C kexts out of the Clover/kexts/Other folder and copy hieplpvip's ones into 10.14, and the 2.0.3 kexts into 10.13 (and install into H.S. or M. /L/E accordingly, if wanted).

Here's the package, attached for you and anybody else who wants to correct and have a better trackpad experience in both, High Sierra and Mojave:

[EDIT: xiqin has made some tangible progress with the 2.1.4 for Mojave! At this point, for Mojave, use VoodooI2C.kext and VoodooI2CHID.kext from his compile here !! Still use the 2.0.3 for High Sierra here from its source or from my package)

Better VoodooI2C kexts for 10.13 & 10.14.zip

Again, smooth handability/ operation seems more important for the average user than a few more optional gestures - 1st things 1st :)

[hkitna]

Hi all, have any one replace DW1830 on F510UA / S510UA?
I am using the new EFI from tctien342 and I can install the macOS. But I had found I cannot connect with the wifi and I only can find 2.4Ghz wifi. I only connect the DW1830 using two antennas. Do I need to add one more antenna to connect the DW1830?

Thanks all.

[leesureone]

Hi all, have any one replace DW1830 on F510UA / S510UA?
I am using the new EFI from tctien342 and I can install the macOS. But I had found I cannot connect with the wifi and I only can find 2.4Ghz wifi. I only connect the DW1830 using two antennas. Do I need to add one more antenna to connect the DW1830?

Thanks all.

I’ve never needed more than just the two connectors. Is it possible you need to change which of the three you connected the antenna wires to? On the original wireless card there should be a number next to each little metal nub and the wires are either labeled or color coded. Maybe you already checked you are matching the original connections and that your connections are solid. Hooking the wires up to the little nub is an excercise in patience.... that and check for the Broadcom Kexts. Personally I use the airportbrcmfixup.kext in combination with the brcmfirmwarerepo.kext installed in library/extensions. I don’t load any kexts via Clover. Up to you though...good luck

[hkitna]

Hi all, have any one replace DW1830 on F510UA / S510UA?
I am using the new EFI from tctien342 and I can install the macOS. But I had found I cannot connect with the wifi and I only can find 2.4Ghz wifi. I only connect the DW1830 using two antennas. Do I need to add one more antenna to connect the DW1830?
Thanks all.

I’ve never needed more than just the two connectors. Is it possible you need to change which of the three you connected the antenna wires to? On the original wireless card there should be a number next to each little metal nub and the wires are either labeled or color coded. Maybe you already checked you are matching the original connections and that your connections are solid. Hooking the wires up to the little nub is an excercise in patience.... that and check for the Broadcom Kexts. Personally I use the airportbrcmfixup.kext in combination with the brcmfirmwarerepo.kext installed in library/extensions. I don’t load any kexts via Clover. Up to you though...good luck

Hi Ieesureone,

Thank you for your reply. I had connect with dw1830 with correct color. Black to black. White to white. Win10 can use the wifi and bluetooth. So I have some question on the kext. Do you only put airportbrcmfixup and brcmfirmwarerepo on the kext/other to install the macOS?

Thanks.

[leesureone]

You can, its not what I do but it should work. It sounds like that's where you have the rest of your kexts. If tried it already and it didn't work any better then it gets more complicated. I don't use tctien342 EFI folder, I tried it and I had some some noticeable delays accessing some functions. I also noticed there were some redundant and unneeded kexts but that's just my opinion.
I followed this guide: https://github.com/hieplpvip/ASUS-ZENBOOK-HACKINTOSH and it worked great for me. He has a config.plist file for a F/S510 model that worked perfectly. I think I tweaked a couple things but I don't remember now exactly what, sorry.

[leesureone]

I'm kind of duplicating information I sent to LeeBinder which is a little farther up in the the thread....without his and tctien342's guide and postings I wouldn't have gotten it going like it runs now. Just saying they both did a lot of work and asked a lot of questions and documented the answers making it easier for other folks like me. Good stuff!

[hkitna]

@leesureone Yes, I see. Thanks for your suggestions. I will try to rebuild my efi folder.

[LeeBinder]

Regarding Trackpad performance in Mojave: xiqin has made some tangible progress with the 2.1.4 for Mojave - smoothest kexts so far for our Asus ELAN 1300 in 10.14.3!!!! At this point, for Mojave, use VoodooI2C.kext and VoodooI2CHID.kext from his compile here !!

For High Sierra, still use the 2.0.3 from my package above.

[LeeBinder]

Regarding USB ports SSDT: SSDT-VIVO-USB.aml (in EFI/Clover/ACPI/patched) is incredibly blown-up (2 kb, 567 lines) and has all sorts of ports which are in there for other mainboards, NOT our Asus Vivobooks! I had already streamlined it before but it obviously got lost [..] so I attach it again (SSDT-UIAC-ALL.aml, 424 bytes, 139 lines):

SSDT-UIAC-ALL.aml.zip

Backup SSDT-VIVO-USB.aml and copy SSDT-UIAC-ALL.aml into EFI/Clover/ACPI/patched), reboot.

You can test yourself by (one after an other or at the same time) inserting one or three USB 2.0 mass storage device(s) to all USB ports, eject, then do the same with one or three USB 3.0 mass storage device(s) to all USB ports, and also a USB 3.0/ 3.1 device to the small USB-C port on the right.

If all mount, and the webcam (which is internally connected via a USB port, too) works, too, you're all fine.

Needless to say any less code which Clover will have to parse or even load into memory will make our HackBooks run smoother .. ;)

@tctien342

[LeeBinder]

@tctien342 : Regarding hieplpvip'S SSDT-S510-KabyLakeR.aml: it is also incredibly blown-up (13 kb, 2795 lines !!!) and has all sorts of entries in there which (as with SSDT-VIVO-USB.aml) are clearly NOT meant for our Vivobooks (all sorts of flavors of Intel Iris Graphics, Intel Iris Pro Graphics, Intel HD Graphics, Intel Graphics etc.pp). This SSDT should get streamlined, too, probably down to entries with only our Intel HD Graphics 620. I don't have any time right now to get into this, so tctien feel free to let us know if you are or plan to be working on this, or would like to delegate.

[LeeBinder]

I filed an inquiry to ReHabMan if his old ACPI-Poller kext which he developed "to better control the system fan on HP 4x30s ProBook laptops" makes any sense for our Laptops - if it can have any positive effect on fan noise for our Asus notebooks at all (link).

[LeeBinder]

RH's reply: "With correct ACPI patches to utilize it, ACPIPoller.kext can be useful for many situations, different hardware."

It's obviously not sufficient to throw in some kext and think it's an automatic "do-jobby" just by itself.

[LeeBinder]

Note: This pre-release's drivers64UEFI folder contains ApfsDriverLoader.efi and AptioMemoryFix.efi. Clover installer wants to upgrade these with ApfsDriverLoader-64.efi and AptioMemoryFix-64.efi.

Sounds rational, doesn't it? if indeed 32 bit drivers in the 64 bit folder are replaced with 64 bit versions.

[LeeBinder]

Reply from Rehabman re. ACPI-Poller.kext: for the kext to work, it is mandatory to "reverse engineer the related ACPI code".

[EDIT]: RH: in Clover/ACPI/patches, there needs to be a SSDT with a reworking of FCPU. And indeed, there is, SSDT-FAN-MOD.aml: Method (FCPU, 0, NotSerialized)
{..
So it all might be good :)

[LeeBinder]

tctien342 silently committed the final release already 5 days ago on March 6
https://github.com/tctien342/Asus-Vivobook-S510UA-High-Sierra-10.13-Hackintosh

without any mentioning neither here nor in the thread at Tonymac.

Beats me, I admit. Oh, well - thank you anyway.. Can apply later.

@tctien342 : can you please detail what you mean by "slow input password" with sys def 14,1? Do you mean at the login screen = booting takes significantly longer for you with sys def 14,1? Or whenever you need to input your PW for root elevation within macOS? Or after wake from sleep?

[solirjin]

Or whenever you need to input your PW for root elevation within macOS?

input your PW for root elevation within macOS.
Because i had installed the previous efi and seen it very slow to input. now i used new one and it disappears

[LeeBinder]

@solirjin @tctien342 : I don't experience that at all here with sys def MacBookPro14,1 as advised for our models by Rehabman because the 2017 14,1 is Core i5 Kaby Lake which is closest to our models (11,1 were late 2013 - mid 2014 Haswell/ Broadwell/ Crystalwell). See for yourself:
https://en.wikipedia.org/wiki/MacBook_Pro#Technical_specifications_3 (click onto [show] on the right)
https://en.wikipedia.org/wiki/MacBook_Pro#Fourth_generation_(Touch_Bar)

14,1 is the last one without Touchbar, which matches our Vivobooks.

I'd say that spoofing a sys def which does NOT match our hardware is "jerry-rigging" = a quick & dirty work-around not a solution.

Again, I don't have that issue at all. My specs:

• Vivobook w/o Nvidia, therefore SSDT-RP01_PEGP (GPU SSDT) disabled
• drivers64UEFI/ApfsDriverLoader.efi and AptioMemoryFix.efi replaced with ApfsDriverLoader-64.efi and AptioMemoryFix-64.efi
• optimized SSDT-UIAC-ALL.aml with only the ports our Vivobooks really have (see above)
• latest Clover 4895
• in Clover Configurator/ BOOT, boot with -f parameter
• 10.13.6 High Sierra but also OK in Mojave
• 2.0.3 VoodooI2C (not 2.1.4)
• ALL kexts correctly installed to /L/E (not just in Clover/kexts) as required by Rehabman, with KCPM Utility Pro, then in KCPM --> Maintenance: Repair file permissions & Rebuild caches
• in Clover Configurator/ SMBIOS, generated FULL definition via "Generate New" button

Hope that helps

[LeeBinder]

I don't have PW input delay either in Mojave with my slightly adapted config with sys def 14,1 ..

[LeeBinder]

New trackpad driver compile by andrewwyatt for Mojave (NOT working in High Sierra): VoodooI2C/VoodooI2C#132 (comment)

[solirjin]

New trackpad driver, compiled for Mojave (NOT working in High Sierra): alexandred/VoodooI2C#132 (comment)

it's not different from the last commit from tctien342, I also see a problem with imess and facetime. DId you fix it?

[LeeBinder]

New trackpad driver, compiled for Mojave (NOT working in High Sierra): alexandred/VoodooI2C#132 (comment)

it's not different from the last commit from tctien342, I also see a problem with imess and facetime. DId you fix it?

1. the compile is by andrewwyatt not by me.
2. tctien342's kexts from his March 6 commit here work in both, High Sierra AND Mojave. Andrew Wyatt's recent Mojave-only compile includes the latest patch and is different from tctien342's kexts. Just look at the byte counts...
3. Are you experiencing iMsg & facetime issues in Mojave with both kext sets, ctien342's and Andrew's, or just Andrew's?

Please head over to https://github.com/alexandred/VoodooI2C/issues, look if there already is an issue about iMessage or facetime, and if not, open one.