-
Notifications
You must be signed in to change notification settings - Fork 58
EFI pre-v.10.1 for Asus Vivobook S15 #46
Comments
Please use this USBPorts.kext instead. It correctly matches against Models MBP11,1 14,1 15,2 and 15,4. |
wow great input @whatnameisit 👍 ! I already updated USBPorts.kext in both, the EFI zip and the USBPorts Issue (darn, had totally forgotten that it requires update after model change, oops). I'll test w/o KernelPm for a while before I also update the EFI. |
Have you run some statistics if you have better battery life with KernelPm disabled? |
I'm also wondering why KernelLapic is ENabled.. From https://sourceforge.net/p/cloverefiboot/wiki/KernelAndKextPatches/#kernellapic:
|
.. and @whatnameisit @tctien342 : any idea why SSD Trim is DISabled? It is enabled in fewt's Vivobook Flip repo. When I check in System Profiler/Hardware/SATA/NameOfMySSD: TRIM Support: No After ENabling it in Clover config, reboot -> it now reads TRIM Support: YES Pro 👍 SSD TRIM: What is SSD TRIM, why is it useful, and how to check whether it is turned on | Digital Citizen Next I run the Trim Enabler app - it reads for my SSD "Status: DISabled". I enable it, reboot -> it now reads "Enabled" in the app. [EDIT]: oh, Con : SSD TRIM.. : Caring for SSDs: TRIM, wear levelling and APFS – The Eclectic Light Company So what weighs more for our Vivo hacks, pro or con? |
You bring up many good things :) |
My TOSHIBA THNSNK256GVN8 is very most likely NOT a NVMe SSD, see Google Search results and series Pdf with specs. I know that @tctien342 did many changes from repo to repo and performance got better and better with each release. Maybe he remembers a few things rather than running redundant tests. What I can say is that I've gone through many reboot and sleep/ wake cycles with KernelLaptic & KernelPm DIS- and SSD TRIM ENabeld, and all is fine in Mojave, Catalina (and even High Sierra) :) |
Can I use it on my VivoBook s510un i7? |
@dayfly that's for you to find out. Nothing to lose. Just make a new partition on your SSD, give it a try and share your results :) |
I can boot, but I can't sleep. |
@dayfly congrats, if that is all that's not working (yet)... Questions to you - please answer both:
From my experience:
¹ VoodooTSCSync, VirtualSMC and Lilu must stay; WhateverGreen and NoTouchID should stay |
I am sorry for my lack of English skills. |
@dayfly please look at my posting in Korean. Also I recommend you use Google Translate Korean -> English ;). |
The release is 99% ready, just missing the final touches in the ReadME.md with instructions for best possible compatibility with most models. I'm off for a quick vacation now and hope to be able to update when I'm back Thursday or Friday. |
No sleep effect When you wake up and wake up, the screen stays black. Even if the battery is connected and the battery is not connected, the screen remains black when you wake up. |
@LeeBinder |
thanks @whatnameisit for your input! I included your hints into the new RC (but not uploaded yet, hoping for tomorrow). Hieplvip's new AsusSMC 1.2.1 works fine in 10.13.6 - 10.15.3 here together with most recent Lilu 👍 ! I made a one double-click installer for the daemon. I don't have the DW1560 but the FRU 04X6020 (which is a BCM94352Z NGFF M.2, too, just from Lenovo). Ever since acidanthera took over the Brcm[..] package., It does not require BrcmPatchRAMx (2 resp. 3 for Catalina) + BrcmFirmwareRepo anymore, but only BrcmBluetoothInjector (BrcmPatchRAMx & BrcmFirmwareRepo must be removed then). Works fine even after several sleep cycles, tested in Mojave and Catalina. From what I read the DW1560 should be fine with just the BrcmBluetoothInjector, too. Have you tested that yet? |
@dayfly: -> Google 번역 을 통해 한국어로이 게시물보기 <- When you write "No sleep effect": when you see the LED blink on the left side, it means that your Vivobook DOES sleep. When you then see a black screen on wake-up, it means you have a wake-up problem, not a sleep problem. When you try to put your Vivobook to sleep and the screen goes black, but you do NOT see the LED on the left side blink after a while, it means your Vivobook does NOT even sleep correctly. Also again, you would need to deactivate kexts one-by-one, reboot, etc. But maybe whatnameisit has been helping you already. |
@LeeBinder |
OK. So maybe I should make two entries in the Wi-Fi/ BT folder, one for the DW1560 and one for the FRU 04X6020, because the FRU 04X6020 has issues with acidanthera's BrcmPatchRAMs/ BrcmFirmwareRepo.
and
eek |
Just a bit of write-up left for the VoodooI2C section (tomorrow, getting too late now), then I can upload the final RC2 for the final review :) @whatnameisit can you try only BrcmBluetoothInjector.kext + /L/E/BrcmPatchRAM3 (BrcmFirmwareRepo removed) in Catalina with your DW1560 with BT on, do a couple of sleep/wake cycles and see if all is fine? |
@LeeBinder I don't know who said BrcmPatchRAM3 has to be installed to /L/E, but nowhere in Acidanthera's BrcmPatchRAM readme says so. It's always worked from /C/K/O for me(Injector, Data, RAM3). |
@whatnameisit good, fine work. Here's what I've been able to find out (surprise surprise ;)), at least for my Lenovo FRU 04X6020.. As per RehabMan (and taken over by Acidanthera at acidanthera/ BrcmPatchRAM):
RehabMan kept on insisting to please use the repo kext installed to L/E (vs. the data kext in C/k/O), so that's what I've always stuck with, with 100% success. What is not mentioned in the ReadMe but spread somewhere in the forums is that (at least for the FRU 04X6020), once one uses BrcmFirmwareRepo.kext from L/E, ANY OTHER necessary kext(s) from the BrcmPatchRAM package (10.11-10.14: BrcmPatchRAM2; 10.15: BrcmPatchRAM3 + BrcmBluetoothInjector) ALSO have to be installed to L/E, AND removed from C/k/O (except when inject kexts = no) - otherwise no BT! It'd be good to know if the same applies to the DW1560. A simple and telling test would be,
If that fails (as it does for my FRU 04X6020):
If you're also curious about this, it would be awesome if you could share your findings with your DW1560 - I would the instructions in the ReadMe :) 👍 |
@LeeBinder I have used both Repo and Data according to what's written in RehabMan's and Acidanthera's BrcmPatchRAM Readmes. |
Right on. I would just say "opt to upload" rather than "need to upload", but other than that, you nailed it as usual. For the release (aim: tonight) I will not include the kexts pre-established in C/k/O, but present L/E as location for manual installation - for two reasons:
(I know some in the h'tosh-verse suffer from L/E phobia, but that's a fantasized disorder I don't deal with .. ;) ) |
@whatnameisit EFI v.10.0 RC2 for Asus Vivobook S15.zip (21,2 MB) 👍 :) |
Nice!! |
Thanks. I already did several updates live in the repo incl. AR-CADE's "no keyboard backlight after sleep in Catalina" fix. For you to note: what fixed the erratic/ spastic pointer movements for me here with the ELAN 1300 were three separate things!! For me this only works in GPIO not in polling mode, even with your SSDT. I mirrored all of them in the repo so people with ELAN 1200 Vivobooks should preferably use your repo (first and try this repo only in case of issues). I thought it makes most sense to offer selective and distinct options. I'll actually link to your repo, too, from the ReadMe (later or tomorrow). You can read the details by following the first two links at [STICKY] TOUCHPAD » consolidated links to related issues. |
I haven't actually tested the EFI yet, but here's what I can say. |
wow - I really appreciate the in-depth explanation. As understandably as you write it I can even make sense of it 🥇 No matter what, there must be an error in the _CRS to XCRS patch. From what I remember, hieplvip shared it with tctien342. Last time I checked hieplvip's repo ReadMe, he was also mentioning something like "random erratic pointer movements". This is the only entry in ioreg when I search for GPIO: I do not know how to positively determine in ioreg if polling or GPIO mode is active for the touchpad. Do you know if the spot in the image is the correct one, or do I need to look elsewhere? Next I'll simply move SSDT-ELAN (= GPIO) out of ACPI/patched, reboot, look at ioreg again, and above all see if pointer movements remain 100% stable. Just can't do that right now but need to do it later. |
_CRS to XCRS itself does not complete the patch needed for VoodooI2C. If a new _CRS is added via an add-on SSDT(SSDT-ELAN.aml), it returns both SBFB and SBFG, and GPI0 is enabled(GPI0._STA to XSTA), then the trackpad is activated in interrupts mode. But Asus laptops have buggy GPI0 implementation, so interrupts mode may not work smoothly, and that probably is where he meant "random erratic pointer movements." |
mindblowing! I just have a minute now (will post log results of different configs in spoilers later): you are right, mode is reverted back down to polling with _CRS to XCRS patch DISabled even with GPIO SSDT ENabled, which is obviously not sufficient all by itself. I am now back on your SSDT-I2C1_USTP.aml + relevant (even though not mandatory as you wrote before) settings in clover.plist/ACPI - now observing performance. Bummer I have never been able to reliably reproduce the erratic movements on demand - they were always just happening at some point. More later. |
All below with VoodooI2C v.2.0.3 which I will stick with for now. I did not always copy/ paste all VoodooI2C related entries. I am now running and testing your SSDT-I2C1_USTP.aml + "ELAN: change USTP to XSTP" + "ELAN: disable I2C0" because from what I recall that's the only combo I had never run on so far with VoodooI2C v.2.0.3. So far so good :) click to expandSSDT-ELAN.aml + "ELAN: change Method(_STA,0,NS) in GPI0 to XSTA" (DISabled: "change Method(_CRS,0,S) in ETPD to XCRS"): GPIO entry in ioreg
and
SSDT-ELAN.aml + "change Method(_CRS,0,S) in ETPD to XCRS" + "ELAN: change Method(_STA,0,NS) in GPI0 to XSTA": GPIO entry in ioreg
Without any ELAN SSDT: "change Method(_CRS,0,S) in ETPD to XCRS" (DISabled: "ELAN: change Method(_STA,0,NS) in GPI0 to XSTA"): -> as expected no touchpad functionality at all + in sys prefs "No TP found" Without any ELAN SSDT + both DISabled, "change Method(_CRS,0,S) in ETPD to XCRS" / "ELAN: change Method(_STA,0,NS) in GPI0 to XSTA": as expected no GPIO entry in ioreg
SSDT-I2C1_USTP.aml + "ELAN: change USTP to XSTP to assign default values to SSCN and FMCN" + "ELAN: disable I2C0" (DISabled: "change Method(_CRS,0,S) in ETPD to XCRS" / "ELAN: change Method(_STA,0,NS) in GPI0 to XSTA"):
@whatnameisit, how did you see that w/o SSDT-I2C1_USTP.aml your battery was getting drained? Somewhere in Activity Monitor? |
ENAL: change \USTP to \XSTP is not needed as \USTP can be ignored and _SB.PCI0.I2C1.USTP is added via SSDT-I2C1_USTP.aml. |
allright, great info, will do tomorrow. What I had in mind from you re. "high CPU usage" was this from Dec 18, 2019:
|
Oh, I watched the CPU frequency go up in Intel Power Gadget and touchpad inputs only worked for a couple seconds. that's what I meant... Sorry for confusion. |
;) From this part of the globe: good night. |
Good night! |
LOL, suspicion acknowledged, I didn't understand what you meant, but so what.. So the I2C0 pci8086,9d60 cleared VoodooI2C might even help @dayfly with his "sleep not working" issue (unless this is resolved already) |
hey @whatnameisit , how's the testing been over there in Korea? I hope your Vivo didn't blow up, silencing you ever since .. ;) FYI, I just released the final v.10 https://github.com/tctien342/Asus-Vivobook-S510UA-Hackintosh/releases https://github.com/tctien342/Asus-Vivobook-S510UA-Hackintosh |
@LeeBinder |
thank you @whatnameisit for looking so thoroughly! USBPorts.kext: darn, it's also necessary to change the name inside a -XHC entry KernelPm: darn #2 - I had corrected that in my local config.plist and in the 15,2 one of the release. Maybe too late into the nite back then.. I applied both changes (+ Kernel LAPIC was still active in one of the configs - sigh). That's why we learn that quality control is indispensable LOL. Beta kexts: yes, I see them in Hackintool, but I decided to stick with stable release versions because everyone who decides to test macOS dev versions can update kexts themselves. OpenCore: I have been somewhat aware of that boot loader only out of the corners of my eyes and also saw that you offer it in your repo. What is its advantage in comparison with Clover - anything real-life tangible/ measurable like macOS speed, less memory footprint, cooler CPU, better battery life, stability ect.? |
@LeeBinder |
Gotcha, thanks for the offer. BTW, CodecCommander 2.7.2 does not work for me - my working combo has been CC 2.7.1 + AppleALC 1.4.6. No sound deactivating even across boots betw. 10.13/14/15. (CC is still necessary here for mike input even with AppleALC 1.4.6 from what I remember testing (haven't tested AppleALC 1.4.7 stand-alone yet)). |
I haven't tested AppleALC 1.4.5+. I will test 1.4.6 when I get home from work. AppleALC has not replaced CodecCommander for all hackintoshes because there are issues with AppleALC not being able to incorporate the verbs that CodecCommander used to send. It may become deprecated for Vivobooks with CX8050 if sound detection never fails and HDMI sound works with layout-id 3(input, output, HDMI used with CodecCommander) and 13(input, output, no HDMI used w/o CodecCommander) combined into a new layout-id. I don't know how to do that, but it should work. I hope someone comes in along and makes a new layout-id lol. |
Hey @LeeBinder
I thank you for directing people to look at my repo. It's true ELAN1200 works great on my X510UA, but my build isn't focused on ELAN1200, rather on cutting out unnecessary patches for X510 laptops without keyboard backlight and NVidia Graphics (and OpenCore). And your release 10.0 works great on my laptop, so there is really no need to reference my repo. I'm just worried people will start asking why the keyboard backlight wouldn't work or have sleep and screen issues (graphics related). Fenvi manufactured a M.2 NGFF A+E card based on the chipset BCM94360 which is native on macOS. It's name is BCM94360NG and its performance is very similar to DW1560 and the variants. The former is a lot cheaper than DW1560 and is native so should work without AirportBrcmFixup.kext or the BrcmPatchRAM package. This product is very new and there are not many reviews. Maybe you can wait and see how it turns out. One build and one discussion that I found: https://github.com/BrushXue/Z170i-Pro-Gaming-Hackintosh , osy/HaC-Mini#197 AppleALC 1.4.6 has not caused any sound deactivation so far. Thanks :) |
hey @whatnameisit - good to hear you're alive & kicking in South Korea!
My plan is to make a new 10.1 release incl. updated kexts shortly after the release of 10.15.4 final. |
#49 (comment) - (Un)Mount HDD.app :) |
https://github.com/alexandred/VoodooI2C/releases/tag/2.4
@whatnameisit in case you have not seen yet 👍 |
hi sir would u mind sharng your efi folder.I had been running catalina on my asus vivobook s15 s510u .But when wake from sleep t used to go to a black screen and stuck there.It would be great if you could share me the efi folder sir. |
@AbhishekRMX1901 try this here and report back, please. |
okayy sir thank you i will |
This repo has found a new home at the current maintainer's GitHub corner: https://github.com/LeeBinder/Asus-Vivobook-S510UA-Hackintosh/ If still interested, please download the latest release from over there, read the ReadMe completely at least once, and follow all instructions all the way to the end. In case an issue arises, please post it via the issues section over there. This issue will now be closed. |
UPDATE Mar. 1 2020:
This is work towards the upcoming v.10.1 release. It contains (among others) the following changes:
click to expand
The text was updated successfully, but these errors were encountered: