Jump to content

cwestpha

Members
  • Content Count

    212
  • Joined

  • Last visited


Reputation Activity

  1. Like
    cwestpha got a reaction from STLVNUB in Updated information Nvidia For Mojave   
    Unfortunately, I don't think this is really anything new. It doesn't answer the questions at hand we have had since the release...
     
    1) Did Nvidia decide to unbundle the CUDA support from the web drivers to get Apple on board? Or did Apple decide to change its stance on CUDA and unsupported APIs?
    2) These drivers could have been ready to go since Mojave release, so is this further along since it seems Apple has been rejecting fully signing and bless the driver so long as CUDA is still being pushed. [see above]
  2. Like
    cwestpha got a reaction from UltraLaser in Mojave : Nvidia web driver petition   
    Yah, it's hard to blame Apple this time when its because NVIDIA is forcing the use of their own unsupported proprietary API. I signed, but it shouldn't be on Apple to tell Nivida to write their drivers for the platform and stop making it a poison pill to extend CUDA to more platforms. That being said, maybe 2019 will see the return of a flexible and expandable Mac platform. Nvidia is right they shouldn't have to use webdrivers for all of their GPUs, but they also shouldn't expect an OS to be crafted around their CUDA APIs like they are demanding.
  3. Like
    cwestpha got a reaction from Leader86 in Nvidia Web Driver updates for macOS High Sierra (UPDATE Nov 13, 2020)   
    10.13.4 (17E199) with iMac 17,1 SMBIOS.
    106 or 105 patched to run worked fine. .30.103  drivers cause graphics crash loop when initializing the displays. the Fix Kext [LILU and Graphics Fixup], manual editing of graphics display kext [to clear out custom display configs], clearing of nvram all don't fix. Have to roll back to the 105 or 106 release for 10.13.2 to get it working.
    Still can't get the native Skylake SMBIOS and Nvidia Web drivers to work together with my GTX 1080.
  4. Like
    cwestpha got a reaction from Fergarth in Security issues in High Sierra   
    I am starting to think High Sierra is turning into the Vista of the Mac world. x.x
    This security vulnerability, odd compatibility issues tracing back to 32-bit process handling changes, the annoying changes to SIP breaking web drivers even more than ever. It's just plain annoying. Had 3 engineers at work roll back their systems to 10.12 already because hardware and services started breaking.
  5. Like
    cwestpha got a reaction from sl0wtarget in Nvidia Web Driver updates for macOS High Sierra (UPDATE Nov 13, 2020)   
    1080 GTX with 10.13 DP5 /w the 10.12.6 drivers. Can confirm not working. :-(
    modified the version checker to match 10.13 DP5's build and took care of the graphics device policy edit. Black screen and no window server (can't even ARD into it) with the webdrivers enabled.
     
    As for the prior discussion with the Apple vs Nvidia conflict... no surprise. but Apple doesn't have the ability to restrict or prevent Nvidia from releasing kexts for their OS... the only leverage Apple would have is to not work with Nivida and not include their products in their macs in the future. aka the current status quo. If Nvidia wanted to they could engineer and distribute web drivers all they wanted for OS X, they just won't get the cooperation of Apple. Its not like there is documentation for how these features work in Macs... Apple just isnt timely in releasing it in advance unless you are a partner (often it comes a few months after OS X goes gold). In theory, even without Apple's help, their OS X market would be larger under 10.13 with the thunderbolt 3 enclosures than they have today (just old macpros being updated and a few enthusiasts doing... unsupported activities).
    Really, I think Nvidia wants to try and get its Quadros as an option for the Mac Pro in 2018. ^.~
  6. Like
    cwestpha got a reaction from Balamut in [pre-release] macOS High Sierra   
    I am interested in the versions for the GPU Kexts. I am wondering if they are getting ready to do entirely new branches for High Sierra considering how dependent the windowserver will be on Metal. I don't think Metal could be considered robust under existing 10.12 kexts. Metal 2 makes me nervous, even with all of the announcements about middleware support, with how bad the current Metal situation is.
     
    APFS will be interesting, about time they got off of HFS+. Though the 64-bits full file system talk was hilarious. Just remembering back to the talk way back about ZFS support (a 128-bit fs) and how they dropped that when they realized it would require engineering.
     
    Update:
    Since I am not going to risk my main hack with the first DP release I decided to take a look at VR support. Not sure if I am hitting an issue with the Nvidia WebDrivers or a USB device limit, but SteamVR won't initialise the display on my MTC Vive using the current Steam VR Beta. It still just views it as a single display that only outputs to the right eye. Oh well.
  7. Like
    cwestpha got a reaction from Gigamaxx in NVIDIA - new beta Pascal drivers   
    I wouldn't say that. Its an f "final" release branch but it seems like the Pascal frame buffers might still have quirks I don't think Nvidia would consider release quality. So I think it's just like the said in the original press release. The Pascal support is non-final in its quality and testing. They just wanted to get it out in people's hands. We have been waiting a loooong time and they might have gotten sick and tired of hearing us complain and wanted to show Apple they can still make a kext. ^.~
    On the plus side, all I see so far is some Metal bugs so far. Haven't done anything CUDA/OpenCL yet though.
  8. Like
    cwestpha got a reaction from TheRacerMaster in OSX Driver for GTX 1080 aka 'Pascal'   
    Most likely won't happen. They will be focusing their few macOS resources to the new version, so the best you can hope for is support in a Sierra beta web driver release. Soonest would be a month or two from now. As stated before normally its 6 months.
  9. Like
    cwestpha got a reaction from Mr___G in [GUIDE] USB Fix El Capitan 10.11   
    I am trying to get my Z77 USB ports worked out correctly before moving onto trying to fix my highPoint RocketU 1144D (4 usb 3.0 ports) and the onboard ASmedia USB 3.0 controller (2-ports). Basically things that can be fixed with DSDT or injector KEXTs instead of needing third-party drivers which are forthcoming.
    so...
    In total, the Z77 controller feeds 6 USB 2.0 ports and 4 USB 3.0 ports. one of those USB 3.0 ports is being seen as a separate USB 2.0 bus (the one with the G19 off of it) despite the other three ports being seen properly. From my understanding this means the bus is missing in the XHCI while being properly in the EHCI list (since all USB 3.0 buses are USB 2.0 buses with an extra controller for the xhci speed/capabilities)... or something like that. I also missing two USB 2.0 ports as only a total of 4 can be seen by OS X. I so wish my motherboard manual had a proper schematic of how the USB subsystem is laid out because I just can't read all of these dumps to figure out where/how to start.
  10. Like
    cwestpha got a reaction from jericane1 in Apple has seeded the first 10.11.2 beta   
    USB 3.1 on Z170 is not done natively by the PCH (ASMedia ASM1142) and Apple doesn't have anything that supports USB 3,1. SATA support seems to be linked to something Apple did, highly doubtful Apple will just flip a switch back since it works for their Skylake based macs and doesn't work for hack macs. I would love to be wrong for the latter though.
  11. Like
    cwestpha got a reaction from Fljagd in Nvidia Web Driver updates for El Capitan (UPDATE 07/11/2018)   
    One thing to remember is, if you are using something that allows OS X to have an emulated NVRAM or partial access to your real system NVRAM, nvda_drv=1 and similar can be added your NVRAM locations. This can cause interesting side effects with your clover or other NVRAM emulating/aware loaders. For example: you can have nv_disable=1 in the clover options at boot but the nvda_drv=1 flag can still be in the NVRAM from the web drivers installer. It can make some false alarms/interesting reboots since OS X boot is not always 100% reliable for dealing with conflicting boot flags. 
  12. Like
    cwestpha got a reaction from Nasco in Clover with Mac skylake CPU support?   
    Also remember the 10.11.1 beta is a beta. So everything may not have landed yet for Z170 support since I doubt Apple isn't going to do a proper update until 10.11.1 for Z170. If you remember back a few years there were builds of OS X that were segmented between the new and old platform for more than just a single .1 release after launch. Apple is extremely inconsistent about updates and their support for anything that's not critical to them (ie what they themselves utilize).
    Also, remember there is a fusion drive build of both iMacs that use SATA.
     
    Almost forgot to add:
    There can also be platform triggers for support. So you may need to wait for Clove to catch up to Z170 OS X (that is it can fake the iMac17.1 complete with S/N, board ID, etc) or you will have to do it yourself. Plus the new USB system can always be fighting you. So many places hacks can now fail.
  13. Like
    cwestpha got a reaction from Fljagd in Nvidia Web Driver updates for El Capitan (UPDATE 07/11/2018)   
    One thing to remember is, if you are using something that allows OS X to have an emulated NVRAM or partial access to your real system NVRAM, nvda_drv=1 and similar can be added your NVRAM locations. This can cause interesting side effects with your clover or other NVRAM emulating/aware loaders. For example: you can have nv_disable=1 in the clover options at boot but the nvda_drv=1 flag can still be in the NVRAM from the web drivers installer. It can make some false alarms/interesting reboots since OS X boot is not always 100% reliable for dealing with conflicting boot flags. 
  14. Like
    cwestpha got a reaction from donald1976 in Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]   
    tried your build, black screen then reboot due to kernel panic. used kext utility to instal, repair permissions, and rebuild. Also tried booting in safemode with same results. Can only boot using nv_disable flag.
  15. Like
    cwestpha got a reaction from Dogma36 in Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]   
    not recently but I did do some benchmarks a while back including some GW2 shots in the 970 GTX compatibility thread. This was 10.10 DP4 with the then binary drivers
     
    Unigine Heaven 4.0 Extreme preset @ 1600x900 8xAA windowed
    60.3 FPS (min 8.6 Max 120.2)
    Score 1519
     
    Unigine Valley Extreme preset @ 1600x900 8xAA windowed
    59.6 FPS (min 25.2 Max 94.3)
    Score 2438 
     
    http://www.insanelymac.com/forum/topic/300923-gtx-970-compatibility/?p=2066970
  16. Like
    cwestpha got a reaction from AlekT in Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]   
    Depends on who gives Apple the best deal while being able to support 3 4K streams and good OpenCL performance. The latter is why AMD won last round since Nvidia tends to be less focused on OpenCL performance and more on its own CUDA. Maxwell is already prepared to head out, AMD is delayed because Apple, Samsung, and Qualcom are taking all of the fab capacity for the finer process. However its up to Apple and Intel when the Mac Pro gets refreshed and it all depends on the timing if AMD will have a solution ready in time. I assumed the 8xx series (a slight refinement of the 7xx series) would get into the last macbook pro but I was wrong there. I would think mid 2015 before we start seeing macs with the maxwell graphics architecture.
    Apple and the different vendors have a lot to go through when it comes to graphics. They are several years behind in OpenGL implementation and there is a large room for improvement when it comes to driver quality. They really don't care that much about anything other then compute and accuracy (for HiDPI) when it comes to graphics.
  17. Like
    cwestpha got a reaction from Dogma36 in Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]   
    Everything for 9xx support is a WiP. full proper CUDA support along with OpenCL 1.2 has issues with it. Some are OS X issues like texture pop issues in 10.10.1 but others are just developing maturity of the 9xx frame buffer. Remember there is no 9xx Apple GPUs out there so we are an after thought with no direct Q&A verification against our setups. So it will work or not, hopefuly they will improve GM204 support once those mobile GPUs of this architecture start hitting iMacs and MacBook Pros
  18. Like
    cwestpha got a reaction from Dogma36 in Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]   
    Hmm, well there are many things that could be causing those issues. The Mac Pro 2,1 has a EFI32 based bootloader where as the 570 has BIOS and I think UEFI64. Aside from the 9xx & 7xx line I don't have much experience with NVIDIA aside from the way back 8800GT & 285 GTX I had in my old Mac Pro 3,1. I went AMD with my builds then went back to Nvidia only with my recent 970.
    You can keep using the Fantomas1 drivers, but I don't think there would be much of an improvement at this time for an older card such as your own with web drivers. You are just using them to get around an issue, not necessarily any other issues inherit in the drivers like missing support (that I can tell) or fixes for your card. The new updates mostly deal with Nvidia building out support for the 9xx, 750 TI series and a few driver bugs. For the most part you 570 is old enough its driver code is rather stable and established so aside from OS compatibility and not getting that back screen you shouldn't have to worry to much. You can try of course, but dont be suprised if you have to boot with an nv_disable=1 flag and roll back the web drivers.
     
    Nvidia is working on some clocking and other issues that have cropped up in its drivers. Yosemite and their most recent branch of drivers lined up in such a way that they have had issues. Also why you dont see 9xx and other newer architectures being back-ported to 10.9 in official channels. Nvidia is trying to line up its Windows, OS X, and Linux work the last year or so and these just happen to be the results. They want to push forward for OS X and Linux because of smaller market share, not have to keep testing backwards like they do with Windows. Then again Apple goes out of its way to make it a pain to go back and supply updates to "old" versions since they often want nothing to do with them outside of security patches.
     
    no. Use the built in drivers if they work.
     
    Yep, fixed a few issues for my 970. Still quite a few issues to go, but its good to see them making regular progress. Also these drivers should soon start showing initial support for other 900 series devices as they are getting close to release.
  19. Like
    cwestpha got a reaction from Dogma36 in Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]   
    OS X default drivers are the ones Apple includes in the OS release. Unlike Windows, Apple doesn't require your device to use the internet to grab the most recent drivers, easier for Apple since they have such a tiny amount of core hardware to support. However the result is then your stuck to Apple's release and Quality Assurance requirements to get updates fixed. Also you are either included out of the box, or you need to look elsewhere for drivers (i.e. the apple printer driver system or device maker websites). Since games tend to not come out nicely timed with Apple OS updates some companies like Nvidia use a side system to allow quicker updates for fixing issues with software (Web Drivers) or adding capability Apple doesn't allow bundled with their software (CUDA framework). Also some people, like myself, use a architecture newer then what the apple included drivers support, and until Apple releases something that supports the newer architecture (ie GTX 9xxm series graphics cards) they have no reason to support us poor folks that built hacks. (To which I say then sell a f**king mac that fills my needs for a desktop ^.~) 
    For your situation I don't have enough information to make a judgement call. what OS version are you sitting at right now?
  20. Like
    cwestpha got a reaction from Dogma36 in Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]   
    OS X default drivers are the ones Apple includes in the OS release. Unlike Windows, Apple doesn't require your device to use the internet to grab the most recent drivers, easier for Apple since they have such a tiny amount of core hardware to support. However the result is then your stuck to Apple's release and Quality Assurance requirements to get updates fixed. Also you are either included out of the box, or you need to look elsewhere for drivers (i.e. the apple printer driver system or device maker websites). Since games tend to not come out nicely timed with Apple OS updates some companies like Nvidia use a side system to allow quicker updates for fixing issues with software (Web Drivers) or adding capability Apple doesn't allow bundled with their software (CUDA framework). Also some people, like myself, use a architecture newer then what the apple included drivers support, and until Apple releases something that supports the newer architecture (ie GTX 9xxm series graphics cards) they have no reason to support us poor folks that built hacks. (To which I say then sell a f**king mac that fills my needs for a desktop ^.~) 
    For your situation I don't have enough information to make a judgement call. what OS version are you sitting at right now?
  21. Like
    cwestpha got a reaction from Dogma36 in Nvidia Web Driver updates for Yosemite [UPDATE: 07/21/2017]   
    the drivers for 10.10.1 (the F03 release) is for 10.10.1 only. At any time during a testing release Apple can alter the way things behave in unexpected ways and introduce regressions at any time. Unless there is something in the testing branches you should stick with the most recent stable OS X update and then use the stable Nvidia web driver ONLY if you need something you cant get from the included standard drivers (i.e. 9xx support). Nvidia generally will do mostly stable web update releases for stable OS X builds but is under no requirement or obligation to stay up to date to Apple changing things every few weeks with testing releases.
     
    Remember: stable OS X release means most recent "stable" web driver release. Testing OS X release means, at best, in development web driver release.
  22. Like
    cwestpha got a reaction from p.H in Any news on 10.9?   
    Most likely 10.9 development has taken a hit as Apple recently redirected some development assets from it to get iOS7 out the door faster. I think Apple is afraid that with Android's pace of development and now a few Android tablets starting to penetrate the market enough to be development targets they need to refresh their mobile OS ASAP before they lose more marketshare in their core business. I just hope they dont decide to change the underlaying core OS to much again and just focus on user facing and fixing what they broke in ML.
    Graphics drivers are still problematic, OpenGL is out of date with oddities laying around, the USB subsystem behaves strangely since the xhci code has been added to it, and there are plenty of general bugs still hanging around. Besides; they need to clean out the last of their Java, X11, and other projects they are relegating to third-party support so we can get rid of these mixed implementations that still have old out of date garbage laying around.
    Apple has a ton of work to get 10.9 where 10.8 should have been all along I just hope they start taking OS X seriously again.
  23. Like
    cwestpha reacted to Slice in Clover General discussion   
    Did you see what properties is injected for your LAN in both cases? "built-in"?
×