Jump to content
InsanelyMac Forum

tomh117

Members
  • Content count

    11
  • Joined

  • Last visited

About tomh117

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  1. Okay nevermind, since I switched to High Sierra I also had way worse performance than before, apparently that's a common issue with 10.13 and nvidia? Either way, I decided to use my RX 580 from my other PC and WhateverGreen and everything instantly worked, weirdly enough even way smoother than ever before even though it's an overall weaker card. Sorry for the the post and wasted time, but thank you very much for the offered help!
  2. When I turn on my PC it will show Clover on the 1080p monitor and the other two DP monitors will go into standby, if I boot OSX like this then all monitors will black screen instead of showing the login screen. The DP monitors will go into an endless loop of trying to get a signal and saying "Display Port" like they do when looking for a singal and the 1080p DVI one will just display a black screen. The system is not hung, I can still ssh into it. The only way for me to successfully boot and have all 3 monitors work is either to: fully turn off both DP monitors, boot only with DVI until log in screen, then turn on both DP monitors manually turn on both DP monitors while booting but before it comes to the login screen, so they are not in standby But if I just let it start normally it without doing either it black screens. The same thing also happens when I'm already logged in and have it running successfully and turn off all monitors and come back later. Usually (8 out of 10 times) when I turn them all on it works again, but the other 2 times all of them start to black screen the same way. It seems the most consistent way to avoid that is to turn both DP monitors on at the same time. What I've tried so far: SMBIOS 14.2, 15.1, and MacPro 6.1 (the current one), none of that helped. Lilu.kext + NvidiaGraphicsFixup Patching AppleGraphicsDevicePolicy.kext/Contents/Info.plist and setting everything to none Switching the 1080p monitor to HDMI but that was the same, can't switch the DP monitors really since they are 4k and need DP. Nothing had any effect. My setup: i7 4790k, GA-Z97X-UD3H, 32gb 980Ti (reference card) driver 378.10.10.10.25.104 (should be the latest one) 2x Samsung 4k monitor (Display Port) 1x 1080p via DVI
  3. Been doing that for the past few days, it actually works quite well, things to note: In order to have sound in the VM you need an unpatched AppleHDA.kext, so be aware of that if you use a patched one to make your sound work natively. VMware tools when running on a native machine will constantly try and fail to load all the vmware kexts and keep spam your logs every 10 seconds, so it's probably a good idea to unload those: /Library//LaunchDaemons/com.vmware.launchd.tools.plist /Library/LaunchAgents/com.vmware.launchd.vmware-tools-userd.plist
  4. I have a fully working OSX 10.11.5 installed on my SSD, and now also installed Windows 10 to dualboot and play overwatch. Now I would like to boot my normal OSX from the physical drive with Vmware Workstation while in windows, to be able to have certain apps I need running even while on windows. I already tried that with a clean 10.11.1 install I still had from a few months ago on an old HDD, and to my surprise that booted perfectly in Vmware and seemed to work without much issues. So now I'm just worried about driver issues, crashes or corruption when running the same OSX both either natively or under a virtual machine sometimes. Does anyone here have experience with that, is there anything I should look out for specifically? (apart from lots of backups )
  5. tomh117

    980Ti hangs total system on certain games

    Unigine Heaven and CS:GO work perfectly. I now narrowed it down to 1 specific combination of minecraft mods. It has a bunch of missing textures warnings and other stuff, I guess something triggers a bug in the Nvidia OpenGL driver that causes it to lock up.
  6. Hi, I got a 980Ti last week and I'm running the latest nvidia web driver 346.03.03f02. Everything seems to work, I have a 4k screen connected with DP and a 1080p monitor over DVI with no issues. I've played normal minecraft for hours without any issues, however when I started a minecraft modpack with a launcher my system becomes completely unresponsive. I waited 10 mins but then forced a reboot. Dec 4 21:52:18 PC WindowServer[195]: _CGXRemoveWindowFromWindowMovementGroup: window 0x1c6e is not attached to window 0x1c8c Dec 4 21:52:39 PC java[96431]: 21:52:39.928 WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h. Dec 4 21:52:51 PC java[96431]: 21:52:51.924 WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h. Dec 4 21:52:52 PC WindowServer[195]: Surface testing disallowed updates for 10 sequential attempts... Dec 4 21:52:57 PC WindowServer[195]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness) Dec 4 21:53:15 --- last message repeated 3686 times --- Dec 4 21:53:15 PC watchdogd[412]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive Dec 4 21:53:15 PC WindowServer[195]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness) Dec 4 21:53:16 --- last message repeated 210 times --- Dec 4 21:53:16 PC watchdogd[412]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer) Dec 4 21:53:16 PC WindowServer[195]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness) Dec 4 21:53:35 --- last message repeated 4026 times --- Dec 4 21:53:35 PC watchdogd[412]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive Dec 4 21:53:35 PC WindowServer[195]: GPU Driver appears to be hung (over 5 continuous seconds of unreadiness) Dec 4 21:53:36 --- last message repeated 209 times --- I tried the same thing again to make sure minecraft is whats causing it and the exact same thing happend again. Is that just a driver bug, is it maybe because of my screen configuration and is there anything I can do to stop that from happening again?
  7. tomh117

    AMD 390x on 10.10.4 Problems

    Thanks for the help everyone. Couldn't get it to work, just in case someone else with the same problem finds this thread: I found this reddit post with someone in the comments having the same problem as me. He also installed with niresh 10.10.1 and updated and had the exact same issue I had. Some other people as well. It seems the niresh iso includes something that messes with the drivers or stops them from working. He said a clean install fixes it. Now to find out how to do a clean install on AMD without any distro.
  8. tomh117

    AMD 390x on 10.10.4 Problems

    Nope it doesn't, neither on 10.10.1 nor 10.10.4, tried every possible GraphicsEnalber,AtiConfig in chameleon and equivalent thing in clover as well without success. Always 3MB VRAM. I also tried backporting the 10.11 ones but managed to completely screw up my OS somehow and had to reinstall. No idea what to do now.
  9. tomh117

    AMD 390x on 10.10.4 Problems

    Ohh I assumed that the IOPCIMatch string was the device and revision field but it is the device and vendor field. Sorry you're right that is in the AMD8000 file by default, I'm an idiot. But if it's in the file by default why doesn't it work and how to I get it to work?
  10. tomh117

    AMD 390x on 10.10.4 Problems

    Okay I reset AMD8000 back to its original IDs and added mine to AMD9000, but still no luck. Do I still need to add the ID to AMDRadeonX4000 as well, cause that other post said so for the 290x? Also we are talking about editing the 10.10.4 kexts right? Not the 10.11 ones "backported" to 10.10.4? Cause currently I'm editing the 10.10.4 ones. But its not working. And kextstat still shows AMD8000 and AMDSupport as loaded, despite me triple checking that my ID is in 9000 and not in 8000 anymore. I have no clue why. I also installed them with KextWizrard and fixed permissions and rebuild cache to make sure it was okay. I also tried both GraphicsEnabler YES and NO with chameleon as well as various combinations with Clover. With InjectATI on and off and the original ID as well as modified IDs just to get it working but no luck either.
  11. tomh117

    AMD 390x on 10.10.4 Problems

    I'm having trouble getting my new 390x to work on 10.10.4. I have seen a ton of posts about the 290x but nothing about the 390x, which from my understanding is mostly the same thing. The id of the card is 67b0 0080, I tried adding that to the AMD8000Controller.kext AMDRadeonX4000.kext like suggested in another post but that didn't do anything. I'm booting in chameleon with kext-dev-mode=1 and tried both GrapicsEnabler=YES and NO (currently having issues with clover beachballing after login so I have to use chameleon for now). I couldn't see any issues with the kexts in the bootlogs, and I checked kextstat and it does show AMD8000 as loaded. But it just isn't using the card/driver. The system profiler tool only shows it with a few MB VRAM and everything is as clunky as before. No framebuffer patch, the way I understood this from another thread is that I don't need a framebuffer patch if I only have 1 monitor connected, and It should work out of the gate? But that might have been about the 290x. I also saw this post and understand that the 390x should be better supported on 10.11, but I'm on an AMD kernel so that's not an option. Any help and guidance would be greatly appreciated.
×