Jump to content

ReddestDream

Members
  • Content count

    40
  • Joined

  • Last visited

About ReddestDream

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

879 profile views
  1. Yeah. I've only been able to see it reproducibly in Chrome/Chromium/Electron apps, but there have been lots of reports of sporadic corruption in other places: https://github.com/lvs1974/NvidiaGraphicsFixup/commit/2548a94bce9fe38e855ca17f19bea05978938cd7#commitcomment-28524006
  2. I've been able to reproduce image (PNG and GIF for sure; seems to involve transparency and animation) corruption on 10.13.4 with the latest Webdriver and NvidiaGraphicsFixup in Chrome/Chromium/Electron apps on Maxwell/Pascal cards, but I can't confirm it on Kepler . . . Anyone else have any ideas? Corruption does not occur on AMD or pre-Maxwell cards it seems . . . I don't think it's the fault of vit's new patches in NvidiaGraphicsFixup, but it might be something that needs to be tweaked for Maxwell/Pascal in NvidiaGraphicsFixup or Shiki to account for Chrome/Chromium/Electron apps and their weirdness . . .
  3. ReddestDream

    nVidia GPUs and the infamous lag issue, Why is that happening?

    New NvidiaGraphicsFixup + 387.10.10.10.30.103 is a miracle. Lag is gone. Even gl water test is good now. Performance is where I'd expect it to be for a 1080ti now. Wow.
  4. It is well-known that systems with Haswell and earlier CPUs don't seem to suffer from the lag. However, it's not the SMBIOS, CPUID, Nvidia GPU Family (like Pascal/Maxwell vs Kepler), or anything easy to fake that is being checked somewhere. Many tests have proven this . . . :/ It's possible that Nvidia has left out/changed the decoders and something isn't being triggered correctly because newer CPUs have some feature or whatnot. I suspect that we are going to have to figure out what to patch/fix to improve the driver performance on newer CPUs. Doesn't look like Nvidia will be fixing it, not with Nvidia eGPU not being officially supported. I'm probably going to end up picking up an AMD GPU for macOS and Linux and just take the hit on games in Windows once there's an AMD GPU available, maybe some "Vega 128," with power comparable to the 1080ti . . .
  5. ReddestDream

    Clover General discussion

    This isn't about updating an already installed system. It's about new USB-based macOS installers based on 10.13.4. Clover isn't detecting the macOS installer on the USB correctly. See here: https://www.insanelymac.com/forum/forums/topic/333560-macos-high-sierra-10134-is-out/?page=2&tab=comments#comment-2606462
  6. ReddestDream

    Clover General discussion

    Clover's probably going to have to start checking bless status to make this determination, which is how a real mac does it . . . In HFS+, this is done by checking the volume header for the inode of the Blessed System File and Folder. I'm not sure how it works on APFS . . . https://bombich.com/kb/ccc4/what-makes-volume-bootable Should probably get sleep. This may end up being complex to fix . . . Yay!
  7. ReddestDream

    Clover General discussion

    But that's the same path an "installed" macOS uses: L"\\System\\Library\\CoreServices\\boot.efi" Now you can't tell if it's an installer or an OS that has already been installed . . .
  8. ReddestDream

    Clover General discussion

    Whether it will work or not is a different question. The Clover devs need to find another way to distinguish between installers and installed OSes since they are using hardcoded paths and not bless like a real mac . . . https://bombich.com/kb/ccc4/what-makes-volume-bootable
  9. ReddestDream

    Clover General discussion

    L"\\System\\Library\\CoreServices\\boot.efi" "Library" and "CoreServices" are misspelled in yours.
  10. ReddestDream

    Clover General discussion

    Not to nitpick again, but "Libray" and "CoreSevices" are also missing "r"s . . . "Library" and "CoreServices" Also the line above the new one needs a comma.
  11. ReddestDream

    Clover General discussion

    Just FYI, UEFI uses backslashes like DOS/Windows, not Unix style: L"\\System\\Library\\CoreServices\\boot.efi" Is the correct formatting.
  12. ReddestDream

    nVidia GPUs and the infamous lag issue, Why is that happening?

    Awesome! Thanks for the info! Looks like 10.13.4 has improved things! Would be cool tho if someone could confirm this on UEFI and with an iMac SMBIOS (maybe 18,3 like mine) tho . . . The cards I'd hope to pair are my 1080ti in the top slot and RX 480 in the bottom in my Z270, 7700K build. But I'd rather that Nvidia just fix the drivers because it's unnecessary heat generated and power drawn. But it would be nice to at least have the option if the Nvidia drivers don't get fixed . . .
  13. ReddestDream

    nVidia GPUs and the infamous lag issue, Why is that happening?

    Cool. Thank you. And that's fine. I plan to update to 10.13.4 once it is released anyway, so if it's better than I expect, that's great!
  14. ReddestDream

    nVidia GPUs and the infamous lag issue, Why is that happening?

    AFAIK, Maxwell and later cards do show in Displays, at least on Sierra, even with no driver or monitor installed. They have incomplete info because of the missing driver, but they do appear to be detected by the VESA driver and they can operate in VESA mode w/o the Webdriver. Also, AFAIK, the bug is caused by having a discrete VESA adapter that is not attached to a monitor. And all the reports I've read of people on Reddit and elsewhere attempting AMD+Nvidia configs on High Sierra have ended in gioscreenlockstate bug tears. I believe that hiding the card is necessary, at least on 10.13-10.13.3. Not sure if 10.13.4 has improved anything. I believe it is in fact a bug new in High Sierra in the VESA detection process that leads to the gioscreenlockstate lockup. It did not happen prior to High Sierra AFAIK. To perform the hiding you must add the Nvidia properties here, turn on Inject Nvidia, and make the AMD card primary in the BIOS, and have no monitors attached to the Nvidia card, only the AMD one. You'll need WhateverGreen/RadeonDeInit or whatever you use because the Nvidia card won't be able to help you since it will disappear as soon macOS sets up the graphics. https://github.com/RehabMan/OS-X-Clover-Laptop-Config/commit/9b8610f32098ce224af044c4e482d2b3da2abae0 See the question is, I'm not sure if bogus properties + Inject Nvidia will make the VESA driver hang up on /all/ dGPUs or just that Nvidia one if it detects the Nvidia card first. I can only fit the Nvidia card in my first slot and the AMD one in my second . . . :/
  15. ReddestDream

    nVidia GPUs and the infamous lag issue, Why is that happening?

    Has anyone here tried running both an AMD and an Nvidia GPU at once, hiding the Nvidia GPU from macOS's VESA driver using Inject Nvidia and bogus properties to avoid the gioscreenlockstate bug in High Sierra when a headless dGPU is present? Such a method works on Optimus laptops, but I'm not sure if it would on a Desktop quite the same way. I have been able to use it to hide the Nvidia card in order to use only the Intel graphics on my Desktop. But I'm wondering if anyone has tried it in an Nvidia+AMD dual dGPU config . . . If I am forced by Nvidia's horrible drivers to use AMD in macOS and Linux, at least this way I can keep my Nvidia card for gaming in Windows . . . :/ https://github.com/RehabMan/OS-X-Clover-Laptop-Config/commit/9b8610f32098ce224af044c4e482d2b3da2abae0
×