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

LeeBinder commented 5 years ago

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

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

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

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

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

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

LeeBinder commented 5 years ago

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

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

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

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

LeeBinder commented 5 years ago

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

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

vasishath commented 5 years ago

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

graphics firmware in UEFI: been wondering that myself..

LeeBinder commented 5 years ago

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

vasishath commented 5 years ago

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. img_20190106_125155

LeeBinder commented 5 years ago

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

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

LeeBinder commented 5 years ago

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

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

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

LeeBinder commented 5 years ago

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

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

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

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

vasishath commented 5 years ago

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

LeeBinder commented 5 years ago

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

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

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

sorry vasishath, it dropped out of my mind that you don't own a S510UA as tctien342 & I do but a S510UN with x510unr BIOS for which 308 2018/11/16 is the latest

https://www.asus.com/Laptops/ASUS-VivoBook-S15-S510UN/HelpDesk_BIOS/

My model got this update straight from 301

was macOS working fine for you with 301, or did you experience the black screen etc. on first hackintosh install even with 301?

(just in case you did not see it: if you click onto 'Show all' below the BIOS 308 download, you can then download 301 and 300 and re-apply)

If 301 or 300 are macOS compatible for you, next steps would seem to be to:

I also think it might be helpful to test-install High Sierra, to see if on your S510UN this is a Mojave-only issue.

GOOD LUCK !!!

vasishath commented 5 years ago

sorry vasishath, it dropped out of my mind that you don't own a S510UA as tctien342 & I do but a S510UN with x510unr BIOS for which 308 2018/11/16 is the latest

https://www.asus.com/Laptops/ASUS-VivoBook-S15-S510UN/HelpDesk_BIOS/

My model got this update straight from 301

was macOS working fine for you with 301, or did you experience the black screen etc. on first hackintosh install even with 301?

(just in case you did not see it: if you click onto 'Show all' below the BIOS 308 download, you can then download 301 and 300 and re-apply)

If 301 or 300 are macOS compatible for you, next steps would seem to be to:

  • determine the version of its IME
  • extract it/ back it up
  • apply the 308 update
  • downgrade to that IME version just for testing
  • boot macOS and see what's happening and share the result.

I also think it might be helpful to test-install High Sierra, to see if on your S510UN this is a Mojave-only issue.

GOOD LUCK !!!

Yes macos mojave was working fine on bios 301. M not sure how to determine the IME version in bios. I used ME_Analyzer and when i drag the bios file in it, it says "this file does not contain ME firmware".

M not willing to downgrade my bios as it has fixed an important issue on this laptop.

LeeBinder commented 5 years ago

Looking at your S510UN's symptoms with the 308 BIOS you're describing incl. the semi-transparent black Desktop, I think you are experiencing something different. I think you should try the latest static patch Clover config.plist and patch your DSDT manually. Look if tctien342 still provides a static patch Clover config.plist in his repo here.

LeeBinder commented 5 years ago

Well now I'm pissed! Took a few minutes, which I guess I shouldn't have done because now I'm in a bad mood:

INTEL-SA-00086 & SA-00125 Detection Tools - RESULTS:

Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz

ME Firmware Information:

X510UAR 303: 11.7.0.3290 SVN: 1

X510UAR 308: 11.7.0.3290 SVN: 1

X510UAR 309: 11.7.0.3290 SVN: 1

👎

LeeBinder commented 5 years ago

more: after official Asus 11.8.50.3399 Intel ME update (MEUpdate_C0_LP_V2.0.0.4.zip) for Vivobook X510UAR, applied to 309 BIOS: 11.8.50.3399 SVN: 3 System Status: This system is not vulnerable

and sure enough, macOS does not boot past the black screen by itself..

Next, downgraded to 308, booted Windows, ran the ME Detection Tool: X510UAR 308: 11.8.50.3399 SVN: 3

grrmpf, clearly none of the recent BIOS versions contains any Intel ME update, and the guy at the Asus HQ was full of sh*t..

Booted macOS High Sierra 10.13.6 with 308 BIOS: still fine, despite of Asus latest IME 11.8.50.3399.

This is BS.

@tctien342 san, any input?

LeeBinder commented 5 years ago

I provided Asus with above information and requested they please supply the correct information regarding the 309 BIOS changes...

vasishath commented 5 years ago

I noticed one more thing yesterday. I was able to boot into installer using the same EFI partition. But i guess maybe since gpu acceleration is disabled in installer that's why it booted. I suspect we should thoroughly check out our additional ssdts. Maybe disabling one or two would have the key.

LeeBinder commented 5 years ago

I booted with no SSDTs in ACPI/patched - no difference.

LeeBinder commented 5 years ago

@vasishath , here's something you can try:

  1. open System Report, Save (to Desktop or wherever)

  2. insert your Mojave installer volume

  3. duplicate /System/Library/Extensions

  4. empty /System/Library/Extensions (remove ALL content - kexts, plugins, bundles - to trash, but don't empty trash!)

  5. copy all content from /InstallerVolume/System/Library/Extensions to /System/Library/Extensions

  6. set working permissions using the script I attached. In that script, simply edit the name in the top to match your volume name

  7. reboot and see if Mojave behaves normally, most likely w/o graphics acceleration. If so:

  8. tag all files in /System/Library/Extensions with a color, e.g. green, to indicate these files are good

  9. re-add all bundles from the duplication, re-run my script, reboot, verify

  10. re-add all plugins from the duplication, re-run my script, reboot, verify

  11. open saved System Report; go to Software --> Extensions

  12. sort by loaded, so you see all with 'Yes' on top

  13. re-add kexts which used to be loaded in bulk (e.g. everything with graphics/ gpu etc.) or one-by-one until you find the conflicting one

From there on debugging would be much easier.

set S-L-E perms & repair perms.zip

LeeBinder commented 5 years ago

I edited my posting above. Please use the new script upload (the 1st/ old script had an error).

vasishath commented 5 years ago

Ohk thanks.. I will try.

Btw can you upload the full diff of dsdt between 308 and 309 ?

LeeBinder commented 5 years ago

the DSDT diff 308 <> 309 is only minor, see my posting at either insanelymac or tonymac, and does not cause this issue, as I could ascertain with cross-testing.

Further on, all SSDTs are the same. I could've compared all additional .dsl files in Clover ACPI origin dump but stopped at that point, because even the ACPI is just part of the BIOS.

In the meantime I got a reply from Asus 2nd level tech support, that they do not disclose high security related changes to any BIOS, on the level of Spectre or Meltdown backdoor fixes, and don't even disclose if a BIOS might contain any such fix, or not...

vasishath commented 5 years ago

I tried a couple of things today.

  1. Used previous clover folder with static patched dsdt which was known to work with only select few new kexts to get it to boot.

  2. Removed all but fakesmc and whatevergreen/lilu

  3. Removed all ssdts

  4. Took a complete diff of all files dumped by clover in acpi origin folder. Only ssdts have significant differences. Dsdt has only 3 lines changed as u said earlier.

  5. Copied original ssdts of previous working clover folder to new hotpatch based clover patched folder.

  6. Tried several framebuffer patches.

  7. Couldn't boot into installer either again. I guess that was just luck by chance.

None out of these had any effect on the issue.

vasishath commented 5 years ago

I guess some bios expert needs to look into this as this is beyond basic fixes now.

LeeBinder commented 5 years ago

oh my, you obviously tried what you could. I came to the same conclusion and hit a solid wall.

I'm in the mountains for several days and will see afterwards (next weekend or so) to bump my topis at insanelymac & tonymac then.

Cheers, Lee

LeeBinder commented 5 years ago

@vasishath , YEE-HAAH - S U C C E S S here with in High Sierra with 309 BIOS!!! With the EFI folder from Olarila's Mojave 10.14.3 installer I can boot into my regular 10.13.6 install, and it's behaving completely normal :)!!

So that you don't need to download the entire installer, I attached just the EFI folder for you (also updated to latest Clover 4871):

EFI Olarila Mojave 10.14.3.zip

In Clover GUI, via Options (O on the keyboard), configs, you can choose two configs. Both work for me.

Please try with your 308 BIOS. Thumbs up, knocking on wood for you !!!

(I have not had any time yet to start restoring tctien342's patches one-by-one to see what the culprit is)

@tctien342 : you might wanna try this EFI folder, too .. ;)

vasishath commented 5 years ago

@LeeBinder thank you so much. I will definitely try later this evening. And I will indeed find the culprit. Thanks a lot again.. you have solved a big problem of mine.

vasishath commented 5 years ago

Yup, it works for me as well. I copied my SSDTs, kexts and config plist as previous and its booting just fine. I guess either its some extra kext or maybe new clover/clover driver version which fixed it.

LeeBinder commented 5 years ago

@vasishath that's awesome, congratulations! I haven't had any time to delve into deeper (and most likely won't have till after the weekend), but I can exclude new Clover version because I tried that first even before switching to Olaria EFI. Kexts can only be the possible source of the trouble if you have not copied any kexts to /L/E except CodecCommander.kext, because remember, as soon as FakeSMC is present in /L/E, no kexts at all from Clover/kexts get loaded but are ignored by Clover! Have you?

So really as per your list, the only difference left can be drivers in drivers64UEFI. My topmost culprit candidate is SMCHelper-64.efi added via Clover updates (neither present in Olaria's nor in @tctien342 's EFI).

Feel free to share any additional findings. I'll be off to a family gathering in the morning and might not have time to respond.

Anyway, enjoy Mojave on your Vivobook finally 👍

LeeBinder commented 5 years ago

@tctien342 @vasishath : So it IS an additional kext the most recent BIOS updates require: https://github.com/RehabMan/VoodooTSCSync

VoodooTSCSync

Fork of VoodooTSCSync by RehabMan

A kernel extension which will synchronize the TSC (Time Stamp Counter) on any Intel CPUs.

This version automatically attaches to the last CPU automatically. Different from previous versions, no need to modify the Info.plist, just install and use.

https://en.wikipedia.org/wiki/Time_Stamp_Counter