search

tctien342 / Asus-Vivobook-S510UA-Hackintosh

Asus VivoBook S510UA running macOS 10.15/.14/.13
100 stars 58 forks source link

boot stuck with latest BIOS 309 #16

Closed LeeBinder closed 5 years ago

LeeBinder commented 5 years ago

[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

vasishath commented 5 years ago

Lol.. I never suspected this to be the reason. Honestly, I thought this kext was a dependency of PS2 or trackpad kext.

LeeBinder commented 5 years ago

Ditto. Questions remain: 1) why can't Asus disclose right away in the BIOS update descriptions that they changed or added the Time Stamp Counter? This does not seem security relevant at all, but rather related to more efficient CPU usage thus energy efficiency related, doesn't it? 2) Why couldn't/ didn't the Asus tech guys in the Taiwan HQ pass on the correct information, but instead passed on wrong information (Intel ME)? 3) Why did they change something about the TSC?

Oh well, we'll never know..

I now hope that 309 is as stable as 308 was 👍

astone1 commented 5 years ago

I notice that sleep on the 309 bios causes a kernel panic quite frequently while using VoodooTSCSync. On 308 sleep works perfectly, does anyone have this problem? I feel that it is related from this kext after looking at KP logs.

LeeBinder commented 5 years ago

@astone1 : I need to admit that ever since my update to 309 + VoodooTSCSync I have hardly ever put my Vivo to sleep because of constant boots between High Sierra, Mojave and Windows.

Would you please specify:

  1. your exact OS version, like 10.13.6 or 10.14.3, or both
  2. if you have your kexts incl. VoodooTSCSync only present in Clover/kexts/other, or also correctly installed to L/E? If only in C/k/O, please install all kexts to L/E, and observe again.

I just now remember one instance where I thought I had left macOS in sleep mode but was greeted with the Asus boot logo when hitting the power key. Certainly going to have any eye on it.

LeeBinder commented 5 years ago

@astone1 : darn, I need to confirm these KPs :(

High Sierra 10.13.6. Not tested in Mojave yet. Kexts installed to /L/E.

To start debugging I removed HibernationFixup.kext, set pmset to 0 and activated NeverHibernate in Clover, but all that did not help.

I noticed that the sleep LED is blinking till right before I open the lid, so the KP occurs on wake. Might be helpful for getting VoodooTSCSync to work at some point.

Unfortunately RehabMan only ever published this one version of VoodooTSCSync, and denskop (whose code he used) never published a compile of his (https://github.com/denskop/VoodooTSCSync), so now the question is how to continue debugging..

vasishath commented 5 years ago

@LeeBinder I can compile the kext u mentioned. But I can do it only in a few days.

LeeBinder commented 5 years ago

@vasishath Great. However, read below @all first, please. And.. - do you get sporadic kernel panics on wake-up from sleep, too?

@all: I'm still not at home, so whoever wants to help debug please look at the following links first, in order as listed:

  1. what we might much rather need could be a new SSDT for the 308/ 309 BIOSes using Pike R Alpha's well-known generator: https://www.insanelymac.com/forum/topic/311144-wake-up-from-sleep-and-usb-issues-10112/?tab=comments#comment-2219455

  2. alternative but seems not so sleek (and would need to be compiled because no release, either) https://github.com/interferenc/TSCAdjustReset

  3. https://www.insanelymac.com/forum/files/file/744-voodootscsync-configurator/

We'll get this going, I'm positively confident 👍 :)

leesureone commented 5 years ago

Instead of posting on tonymac this made more sense being I used suggestions found here. I have not had any issues with sleep as you are describing so I though it might be of interest. I followed the guide provided by hielpvp checking and installing various kexts and drivers after downloading and of course the appropriate config.pist for your model. (https://github.com/hieplpvip/ASUS-ZENBOOK-HACKINTOSH). It worked on my vivobook and a zen book I have as well

LeeBinder commented 5 years ago

Thanks @leesureone for reporting no issues with wake-up from sleep on your Vivobook F510UAR even with latest BIOS with hielpvp's method. When I asked him which of his Zenbook models we should choose for a Vivobook S15, he replied that they are too different and that I shouldn't try! So obviously you are a step or two ahead of everybody else 👍

Can you please zip up your Vivobook EFI folder minus themes folder (and if you prefer edit out your Serial # in SMBIOS) and attach it in your reply so we can check if your EFI folder works on Vivobooks other than yours, too?

That would be awesome.

Also it would be very interesting to learn from you which of his models you chose as closest match for a Vivobook S15 - either UX330 or UX430 I guess, both Kaby Lake R?

Great collaboration here!

leesureone commented 5 years ago

EFI F510UA.zip

Nice clarification on what I was trying to say. hielpvp includes a config.plist for a model 510 in the build folder you get when you download form his GitHub page. I may have edited the version in my EFI folder a little in Xcode, I forget, but regardless it is a very close. I'm sending you screen shots of the clover drivers and entire list of kexts installed in Library/ Extensions for your reference as well. Works like a dream....hope it does for you as well!

Library Extentions.pdf Clover Drivers.pdf

LeeBinder commented 5 years ago

awesome @leesureone !

Three questions:

  1. The only difference between your Clover drivers64UEFI folder and the screenshot pdf seems to be VirtualSMC.efi, which we'd need to add, right?

  2. Should we use configvivo.plist rather than config.plist?

  3. Did you add the VoodooTSCSync.kext, or was it already present in hieplvip's package?

I might have a bit of time to apply your EFI folder tomorrow, so if anybody else here wants to go ahead .. @astone1 @vasishath :)

BTW, you can keep all your kexts in Clover/kexts/Other, too (in addition to them in /L/E), because as soon as FakeSMC.kext is present in /L/E (legacy: in /S/L/E), no kexts in Clover/kexts/Other get loaded - Clover disregards them.

leesureone commented 5 years ago
  1. Yes, I would add it.
  2. Please use the config.plist, not the configvivo.plist
  3. I added VoodooTSCync.kext based on your progress in trying to get bios version 309 to boot. Worked great, no affect on sleep either.
LeeBinder commented 5 years ago

Okay, thanks. I hope to get to it tonight finally.

VoodooTSCync: I wonder why baohiep/ hieplpvip who's also running his Zenbook on 309 BIOS never mentioned that kext when I asked him. My guess is because he created a 100% correct CPU SSDT. Remember, for our CPUs we should not need VoodooTSCync.kext, which by some is considered a work-around patch rather than the real issue-resolution.

"I'll be back' :)

LeeBinder commented 5 years ago

[EDIT] see below

After downloading, in Clover config.plist Boot section:

e.g. via Clover Configurator

LeeBinder commented 5 years ago

A few findings re. above package v._2019-02-21_00.16:

So for now I'll use @leesureone 's package + tctien's config plist with -v + SSDT-CONXEANT-FIX.aml and see how that goes.

BTW, only in High Sierra I was getting a sporadic kernel panic on wake-up from sleep, but in Mojave a black screen.

LeeBinder commented 5 years ago

@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?

LeeBinder commented 5 years ago

After quite some merging of leesureone's and tctien's packages back and forth I always reach some dead end at some point, with something new or more not working anymore (in addition to the regressions mentioned above: "No Trackpad found" in Sys Prefs, or no wake-up from sleep at all anymore)...

I need to take a time & effort break from this now and suggest you folks do some task splitting on the basis of tctien's package here:

Contributor 1: create a custom CPU SSDT with Pike R Alpha's generator (be aware: our CPUs are unknown to that script and data needs to be inputted manuall) - first WITH VoodooTSCSync for ease of creation, apply, booth w/o VoodooTSCSync. If issue persists then recreate SSDT w/o VoodooTSCSync active.

Contributor 2: compile https://github.com/interferenc/TSCAdjustReset in XCode. Note that this was made for a Skylake-X CPU on a X299 board

Let me know what you think, if you have more ideas, and what you (hopefully) find out.

tctien342 commented 5 years ago

First, thanks guys for found the main problem!!! Use this package, after 1 week tested, no problem until now !! I will commit this soon, sorry for reply late, too much work need to be done in my company :'( CLOVER.zip

LeeBinder commented 5 years ago

hooray, our Guru is back 🥇 !! Thanks for being diligent in the background!

Will apply right now and reboot!

Suggestion: wait a few more days before commit to get some feedback from us with all our slightly different Vivobooks :)

LeeBinder commented 5 years ago

@tctien342 : should we keep the big /EFI/APPLE folder with EXTENSIONS/Firmware.scap and FIRMWARE/IM142.scap when replacing our current Clover folder with yours, or start with none (remove or rename it)?

tctien342 commented 5 years ago

@LeeBinder keep or none both OK, =)), u should backup your worked EFI for safe

LeeBinder commented 5 years ago

@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 commented 5 years ago

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

LeeBinder commented 5 years ago

@tctien342 OK

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

Two suggestions: in Clover/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 commented 5 years ago

@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 commented 5 years ago

@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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

@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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

LeeBinder commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

@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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

@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:

Hope that helps

LeeBinder commented 5 years ago

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

LeeBinder commented 5 years ago

New trackpad driver compile by andrewwyatt for Mojave (NOT working in High Sierra): https://github.com/alexandred/VoodooI2C/issues/132#issuecomment-473577421

solirjin commented 5 years ago

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 commented 5 years ago

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.