Jump to content

alfaSZ

Members
  • Content count

    26
  • Joined

  • Last visited

About alfaSZ

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  1. Try slide=128 in boot params Sent from my iPhone using Tapatalk Pro
  2. Hi have you made any progress in this topic? Namely how to boot the installer with nvidia drivers and and bypass Library validation for the WindowServer process?
  3. alfaSZ

    Clover General discussion

    @Slice KernelPM->False is the old style patch for a single MSR that used to not work even under Haswell-E if I recall from memory. So unless the new Broadwell-E patches depend on this flag, which I believe they don't, I doubt it would be of any help. But maybe we can redefine its meaning, and make the new patches dependent on it too! Sent from my iPhone using Tapatalk
  4. alfaSZ

    Clover General discussion

    I would second that - we need a way to disable automatic patching for Broadwell-E, because it is not perfect. If I had the time I would propose fixes for inclusion in the code but right now I can't so am being forced to stick to older versions or build my own suitably modified which is not ideal. It seems there are multiple users who have same need. Sent from my iPhone using Tapatalk
  5. alfaSZ

    "Service only ran for 0 seconds"

    Yeah but I don't want to dismantle water loops etc. Also I do not understand how the same drivers can load once the system is installed but don't load properly during installation phase - I can demonstrate for instance the nvidia webdrivers loading from a live installer usb and still getting a blank screen... Do you know how to debug this if I wanted to get to the bottom of it just out of sheer curiosity? There are no visible error messages once the drivers load and I don't have access to a terminal prompt to see what the installer log is. EDIT: The answer is of course here: https://github.com/mologie/NVWebDriverLibValFix/issues/6, i.e. patched nvidia drivers to sort out the MacPro6,1 blank screen issue will still fail Library Validation checks when the WindowServer process tries to load, so the NVWebDriverLibValFix.kext will still be required in this case. I was thrown off by a/ seeing the drivers themselves load during boot and b/ a message that appeared in the github repository for NVWebDriverLibValFix.kext claiming that this kext is unneccesary for High Sierra - which is true, but ONLY for untainted drivers. Lilu on-the-fly patching DOES taint them.
  6. alfaSZ

    "Service only ran for 0 seconds"

    Yes this is an issue that has been bugging many people since HS developer beta 6 or so. It seems to affect only people with dual Nvidia cards (I have 2 GTX1080s) and I am stuck too. As explained by Rehabman over at the forum that shall not be named, IONDRVSupport.kext fails to load and then the WindowServer process ends up failing to load, and launchd gets stuck trying to respawn it forever. This is the VESA mode driver for nvidia cards that don't work out of the box (maxwell and pascal basically). I have built a live USB installer using the "restore directly from BaseSystem.dmg" technique, and I have copied nvidia webdrivers over and rebuilt kernelcaches etc. When I boot I can watch them load and get registered (once for each card), and then the screen tries to change graphics mode and screen goes blank but stays powered on forever - so this is not the usual AGDP/MacPro6,1 issue (have taken care of it using existing well-known solutions) but a new issue as has been described multiple times already in this forum e.g. by fabiosun. I don't get a moving mouse pointer though, have never seen that. To sum up even trying to install with nvidia webdrivers loaded fails. I even used Rehabman's tricks to only load the webdrivers for one card, still failed with same blank screen. Obviously deleting IONVDRVSupport.kext altogether is not a solution either as it seems to be necessary to load the webdrivers and without it the boot process gets stuck in console mode. In short even with nvidia drivers baked in there is no way I can see to make the installer work. Only solution at this stage seems to be to remove one card from the motherboard ...
  7. alfaSZ

    [pre-release] macOS High Sierra

    yes indeed - will look into that as soon as I get some time
  8. alfaSZ

    [pre-release] macOS High Sierra

    Fair point - I thought of it too but would rather not dismantle my waterloop etc if I don't absolutely have too so am waiting for a workaround and using 12.6 in the meantime (which has proper drivers to begin with...)
  9. alfaSZ

    [pre-release] macOS High Sierra

    Sure #3486 Sent from my iPhone using Tapatalk
  10. alfaSZ

    [pre-release] macOS High Sierra

    Thanks but what I really have is "WindowServer process keeps respawning" issue (during installation of dp6+) This was just a test to see if the two are somehow linked
  11. alfaSZ

    [pre-release] macOS High Sierra

    Nope - no joy using MacPro5,1 to avoid the AGDP/black screen issue
  12. alfaSZ

    [pre-release] macOS High Sierra

    So in other words this is just a different manifestation of the usual MacPro6,1 AGDP issue? I'll try booting with MacPro5,1 to check .. Sent from my iPhone using Tapatalk
  13. alfaSZ

    [pre-release] macOS High Sierra

    Yes I had been using them until dp5. But even without them I could go through the high sierra install using basic vga drivers, and install them afterwards Sent from my iPhone using Tapatalk
  14. alfaSZ

    [pre-release] macOS High Sierra

    Hmm interesting. I guess I'm out of luck with two GTX 1080s then?.. They did work up until dp6 is the annoying thing Sent from my iPhone using Tapatalk
  15. alfaSZ

    [pre-release] macOS High Sierra

    I have the same problem but I only have 2 discreet GPUs - no internal Intel HD to fall back on. It appeared around dp5 or dp6 just like for the earlier cases mentioned... Do we know what exactly is causing it? Anyone else care to comment?
×