Jump to content

Search the Community: Showing results for tags 'GPU'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 26 results

  1. Rampage Dev

    New Nvidia Retail Driver Install Solution

    New Nvidia Retail Driver Install Solution Posted on May 16, 2013by rampagedev about: New Nvidia Retail drivers have been released today. It introduces a new Preference Pane under System Preferences that allows you to enable the Nvidia Web Driver or OS X Default Driver The new drivers require information to be written to the NVram. Without this you will not be able to Meklort, who developed the NVram Module that we currently use, assisted me in understanding why the NVram information showed up on some systems and not others. If you are using my Recovery Partition And Enable All Features Of iCloud and iMessages fix you must remove nvram.log from /var/log/ before you can begin. If you plan to enable ECC, for a Nvidia card that support this feature, you must add the slot identification edit in your DSDT or the option to enable ECC on that card will not be available. Accreditation: Meklort for NVram Module and boot.plist Flag Originally posted here Guide: Part 1: Install 1. Download Mac OS X Driver Release 313.01.01 here 2. Install the drivers 3. Install the latest Bootloader found here 4. In your Extra folder if not present already create a folder called modules: 5. From i386/modules folder copy FileNVRAM.dylib into Extra/modules: 6. Continue to Part 2 Part 2: Fusion Drive Installs or Systems Without FileNVRAM 1. In your Extra folder open org.chameleon.Boot.plist: 2. Under Kernel Flags add nvda_drv=1: 3. Continue to Part 3 Part 3: Enabling 1. Go to System Preferences: 2. Go to Nvidia Driver Manager: 3. In the Preference Pane change the settings to match the following: 4. Restart 5. The new kexts should now be loaded: 6. If you are using my Recovery Partition And Enable All Features Of iCloud and iMessages fix please redo Parts 4-7 here
  2. Rampage Dev

    Patched Framebuffer Repository

    about: This is a Repository for ATI and AMD patched Framebuffers. Here you will find a complete list of successfully patched framebuffers for ATI and AMD Graphics Cards. This is not a support page so do not post questions on this page. Start a new topic if you have questions. Thank you for your cooperation. Framebuffer Editing Guides: BCC9′s post that can be found here Alexander Martinez’s post that can be found here Mucha’s post that can be found here Posting Guidelines: The following are the posting guidelines for this page. Failure to follow set guidelines will mean that the patched framebuffer will not be posted on the first post. Thank you for your cooperation. Graphics Card Model: Graphics Card Manufacture Name: Graphics Card Manufacture Part Number: Fixed by: Patched Framebuffer:
  3. Larry_The_Great

    SLI on hackintosh?

    Hello everyone, I am in the process of upgrading my hackintosh which duel boots OS X and windows. I currently have one GTX 760 in my build and it simply isn't powerful enough when I game on windows. I was thinking about getting two GTX 970's and running them in SLI because apparently two 970's run much better than one 980 and for only a little more money. I have heard that OS X doesn't support SLI natively so I was wondering if anyone knew of any drivers that would fix this, or if it would even boot with two cards in SLI? I'm hoping that if there is no way to support SLI then the hackintosh will automatically only use one of the GPU's and windows will use SLI. Can someone please clear this up for me as I want to buy the GPU's when they go on sale just before christmas. Thanks.
  4. Introduction With Whatevergreen.kext we already have a workaround for the AMD GPU wakeup issue which first arose with the release of El Capitan, but as a workaround is just a second class solution for a problem I decided to trace back the reason for the issue to it's origin and this post is the result of my research. As I used a R9 270X to do my research, which is the only AMD GPU I have, my patch has only been verified to work properly with this chip but according to the information sources I used, I have no reason to believe it won't work on other AMD GPU's too. In case there is still some uncertainty left in a particular point, I will mention this explicitly. Materials Used The Linux kernel sources of the Radeon driver in order to get a better understanding of the GPU's internals: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/radeon?h=next-20171013 A copy of the ACPI 6.0 specs in order to find out how to dump the chip's control register space. A disassembler, e.g. objdump in Terminal or the trial version of Hopper Disassembler. What I Did As it's been a well known fact that wakeup with AMD GPUs still works with El Capitan and Sierra provided you select the IGPU as primary GPU enabled CSM and use Legacy VBIOS of the AMD GPU in BIOS setup. I was wondering what is different with UEFI VBIOS and decided to I create dumps of the GPU's control register space while using Legacy VBIOS with CSM enabled and while using UEFI VBIOS with CSM disabled in order to find out. Comparing the register space contents it became obvious where the root of the problem lies and how it can be fixed with a DSDT patch. Technical Background Using Legacy VBIOS only the primary GPU is initialized by the VBIOS, i.e. only the IGPU is initialized while the AMD GPU is left untouched. When OS X boots up the framebuffer controller kext will find the AMD GPU in vanilla state, initialize it properly and wakeup will work as expected. That's also the reason why you have to blind boot in this configuration. Using UEFI VBIOS the AMD GPU will be initialized too, provided it has a display connected to one of it's ports. You'll see the BIOS splash screen and will be able to access the BIOS settings but unfortunately macOS's framebuffer controller kext will notice that the GPU has already been initialized and skips the basic setup so that the configuration made by the VBIOS will be used and this is the point where things start to go wrong because this configuration seems to be broken causing wakeup to fail. First of all you have to locate the AMD GPU in your DSDT. In my case it can be found at _SB.PCI0.PEG0.PEGP but it needs to be renamed to GFX0 for AppleGraphicsDevicePolicy.kext (AGDP) to work properly. This can be done manually or using a Clover patch (this is what I did) and I assume that this problem has been already solved before. The reason why I mention it explicitly here, is that you should be aware of it and don't get confused when your AMD GPU has a different name in the DSDT than in IORegistry. Second, we need to get access to the GPU's control register space. According to the Linux sources, PCI Base Address Register 2 (BAR2) is used to address the control register space on Radeon HD5000, HD6000 and HD7000 GPUs. It's a 64bit base address register but newer GPUs (BONAIRE and above, i.e. Radeon HD8000 and HD9xxx) are different as the use BAR5 instead of BAR2. Unlike BAR2, BAR5 is a 32bit base address register. On my R9 270X (PITCAIRN) BAR5 is zero so that I decided to use this as an indication to use BAR2 but I must confess that I haven't checked if it works for all supported GPUs too. In case my patch doesn't work for you, be aware that this might be a pitfall! The Radeon driver's source code tells us that the first display controller engine's registers can be found starting at offset 0x6800. It also tells us a lot about the meaning of the register contents. Using Legacy VBIOS my R9 270X's display controller engine's registers are still at their default values when macOS boots: 00006800 01 00 00 00 08 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006820 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | With UEFI VBIOS the display controller engine's registers look quite different. Using the Linux driver sources you can easily make sense out of these values and will discover that I've got a 4K display connected to my R9 270X which is configured to it's native resolution using 32 bits per pixel. 00006800 01 00 00 00 0a 80 00 0a 00 00 00 00 00 00 00 00 |................| 00006810 00 00 00 00 00 00 00 00 00 0f 00 00 f4 00 00 00 |................| 00006820 f4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006830 00 00 00 00 00 0f 00 00 70 08 00 00 00 00 00 00 |........p.......| 00006840 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006850 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 |................| 00006860 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006870 00 00 00 00 08 80 00 14 00 00 00 00 00 00 00 00 |................| 00006880 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00006890 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000068b0 00 00 00 00 10 00 00 00 00 00 00 20 00 00 00 20 |........... ... | 000068c0 00 00 00 20 10 00 00 00 00 00 00 20 00 00 00 20 |... ....... ... | 000068d0 00 00 00 20 00 00 00 00 00 20 00 00 00 00 00 00 |... ..... ......| 000068e0 00 00 00 20 00 00 00 00 00 00 00 00 00 20 00 00 |... ......... ..| 000068f0 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 20 |..... ......... | The rest was just a little bit of laborious work and trial and error, comparing register contents, understanding their meanings and see what happens when you reset these registers to their default values. If you try to play around with your GPU's control registers a little bit more, be prepared to get a garbled screen for a few seconds. After all I've managed to create a DSDT patch which fixes the wrong registers while preserving screen output during boot and, most important, solves the wakeup issue. The Patch Putting things together I created a DSDT patch to fix the incorrectly initialized registers. With this patch applied, I now have working wakeup with my R9 270X under Sierra (10.12.6) using UEFI VBIOS with CSM disabled in UEFI setup. No kext patches or additional kexts are needed anymore for sleep/wake to work properly with my R9 270X anymore. I can see the BIOS splash screen on my display and can access UEFI setup but the best of all is that there hasn't been a single wakeup issue since I applied this patch. Device (PEGP) { Name (_ADR, Zero) // _ADR: Address OperationRegion (PCIB, PCI_Config, Zero, 0x0100) Field (PCIB, AnyAcc, NoLock, Preserve) { Offset (0x10), BAR0, 32, BAR1, 32, BAR2, 64, BAR4, 32, BAR5, 32 } Method (_INI, 0, NotSerialized) // _INI: Initialize { If (LEqual (BAR5, Zero)) { Store (BAR2, Local0) } Else { Store (BAR5, Local0) } OperationRegion (GREG, SystemMemory, And (Local0, 0xFFFFFFFFFFFFFFF0), 0x8000) Field (GREG, AnyAcc, NoLock, Preserve) { Offset (0x6800), GENA, 32, GCTL, 32, LTBC, 32, Offset (0x6810), PSBL, 32, SSBL, 32, PTCH, 32, PSBH, 32, SSBH, 32, Offset (0x6848), FCTL, 32, Offset (0x6EF8), MUMD, 32 } Store (Zero, FCTL) Store (Zero, PSBH) Store (Zero, SSBH) Store (Zero, LTBC) Store (One, GENA) Store (Zero, MUMD) } } In case you have in-detail questions or need AML code for debugging (code to dump BARs or to dump the GPUs control register space) please let me know. I'm willing to share all my information in order support further research. Below you can find the register dumps I created attached to this post. FAQ Do I still have to select the IGPU as the primary display? No. Although I haven't tried this on my own, user chh1 confirmed that this is no longer required when using the patch (please see http://www.insanelymac.com/forum/topic/328549-tracing-back-the-amd-gpu-wakeup-issue-to-its-origin/?do=findComment&comment=2519884). Nevertheless I still recommend to select the IGPU as primary as there is absolutely no reason not to do so, in particular as the IGPU will be unusable for multimedia acceleration on Haswell based systems when it's not the primary one (IGPU's dev id is different when it's not the primary one). ​When I boot into macOS I always end up with a black screen. Does your patch solve this problem too? No, it doesn't. This patch solves the wakeup issue, nothin more and nothing less. The black screen after boot is either the result of a connector problem (please create a connector patch for your graphics card using the well-known methods) or the result of a problem with AGPM as certain system definitions (in particular recent iMacs) select special configurations for graphics power management. In order to achieve proper operation of AGPM it is crucial that your GPUs have correct names in the DSDT matching those listed in the AGPM configuration for the system definition (IGPU for the Intel GPU and GFX0 for the AMD GPU on iMac15,1, iMac17,1 and iMac18,x). You may patch your DSDT manually or use a Clover DSDT-patch to fix the device names. Credits vit9696 for developing Whatevergreen.kext and pointing me to the right direction. RehabMan for developing ACPIDebug.kext The Linux Radeon driver kernel developers for providing me with the background information I needed. Legacy.bin.zip UEFI.bin.zip
  5. Today i got this message for the first time from the new NVIDIA System Preferences pane that a new driver is available. I couldn't find this update on their site as a standalone- this could be the first direct update for users of the NVIDIA Web drivers. NVIDIA Web Driver 313.01.02f01 http://us.download.nvidia.com/Mac/Qu...3.01.02f01.pkg How to Install the Web Drivers: In order to flag the alternate drivers on a CustoMac, you must install the package and also add the flag manually to the chameleon.org.Boot.plist. For Chimera bootloader: 1. Open Finder 2. Navigate to /Extra/org.chameleon.Boot.plist 3. Open in TextEdit 4. Add nvda_drv=1 to Kernel Flags as shown: Example Usage: <key>Kernel Flags</key> <string>darkwake=0 nvda_drv=1</string> 5. Save and reboot You should be on the new NVIDIA drivers.
  6. I’ve got one last problem with my setup that I’m really hoping you guys can help me get sorted. Under OSX, after sleep, the GPU idle temp jumps to what I would call an unsafe level. For starters, this GPU runs quite hot anyway, which I’m led to believe is normal. Some people say it can safely go as high as 105° before starting to damage itself… but yeah, there’s no way I plan on ever running it that hot. With an ambient temp of about 25° it normally idles around the 55° mark under both Windows and OSX. But under OSX, once woken from sleep (until the next reboot), for whatever reason the idle temp dramatically jumps about 30°, putting it at almost 85! This is still okay for this card, if it were under heavy load that is, but no way should the idle temp ever be this high. As far as I know, only one thing can be going wrong here. For whatever reason, once woken from sleep, the correct signals aren’t getting through to the card to tell it to adjust the fan speed as necessary. I’ve tried flashing the card bios (NVflash) to set a higher minimum speed for the fan – it was 30, I set it to 80 – but the problem there is that in both in OSX (and Windows too for that matter), the drivers seem to be overriding this limit. I can tell just from what I can hear that the fan is not at 80% power right now. I’d really like to know what sleep is doing to mess up the GPU fan speed and see if we can fix this under OSX. GPU: Nvidia Quadro 4000 MB: GA-x79-UP4 (Sleep enabled with SleepEnabler.kext) OSX: 10.8.2 Anything else I can post to help, please let me know. Cheers.
  7. marcosviniciusf17

    Ajuda para editar SSDT

    Boa tarde pessoal, estou com meu hack quase completo (falta so o audio kkk). E quero testar uma possibilidade para meu note. Estou usando o MacIasl e quero inserir o patch para Nvidia q postei nessa SSDT so q ela n aceita e é´nessa msm que tem q colocar. estou tentando inseri-la manualmente mas n consigo. Preciso coloca-la no final da PEGP (\_SB.PCI0 > PEG0 > PEGP). Qualquer ajuda é bem vinda.
  8. Hi, I've found out recently that when both of my monitors are wired to the same graphics card, even when the card is idling, the performance drops by ~10%. So I moved one of my monitors to the IGP, where it would act as the secondary while the other is my main monitor. This is a perfectly working setup in Windows. On Hackintosh, it's causing me a lot of trouble. At first the IGP (HD 4600, 0x08060412 on 4770K) refused to be recognized by Yosemite until I put in vendor-id as 0x8086 and device-id as 0x0412. I'm still working on finding the best ig-platform-id but that's not the issue. When I did get the IGP enabled, the GPU stopped working! No output from the DVI and HDMI slots on the GPU, no HDMI on the IGP with the IGP enabled. So simply put, when one starts working, the other stops. That isn't to say the card stops being recognized. Both the GTX 770 and HD 4600 are recognized by OS X, but only the IGP is able to output a video signal when IGP is enabled. I've tried rerouting the _ADR to 0x00210000 on the IGP to stop it from conflicting with the GPU, but my DSDT doesn't have a GFX0 entry. It's referenced in the DSDT, so I assume it's floating in the SSDTs somewhere. Can someone help please? > < It's kind of painful using a computer on a vertical monitor only... DSDT.aml.zip
  9. I've been using two Hackintosh laptops and a Hackintosh desktop for one and a hour years. My first Hackintosh laptop, Rabook F660s, was hacked with paid service. And the guy who installed OSX10.11 on my laptop told me it was never possible to have my Nvidia GTX 870m (3GB RAM) working unless the integrated graphics (Intel HD 4600) could be disabled. I think it's true for most laptops but not for my Rabook F660s. In the laptop, the Nvidia card is plugged in the mainboard. The HDMI and DP video ports are on the Nvidia GTX 870m card rather than on the mainboard. The setting is close to a desktop. And I've proven both cards are working properly on OSX10.11 and OSX10.12 with Clover patch for Intel HD 4600 and web driver from Nvidia. Connecting a video cable enables the GTX 870m card for video display. If the video cable gets unplugged, the Intel HD 4600 card is back to life. I'm also able to use CUDA on the laptop and perform some scientific computation, whose performance is much better than the best Macbook pro. I think Rabook F series laptops are all able to function this way. You may consider this as a choice if you need.
  10. I got a copy of iLife 11 from eBay and i checked it to see if it is legit, and it was. So i mounted my drive to the VMWare to the Hackintosh Sierra and it loaded fine but i found out the GPU wasn't compatible. And i read that: VMWare is using a fake GPU emulation where it can't use the hosts GPU and tell that it might have Quartz thing on there so Mac's can't know if this hardware was used. So... Is there a great VM program for Windows? And yes i'm using Windows since i the PC's i have don't have compatible Wi-Fi drivers so the VM only was my choice to get online and use it as my daily basis.
  11. Hi everyone, first of all here are my specs: AMD FX-4100 quad Core a processor 3.6GHz Nvidia GeForce GTX 780 GPU 16GB RAM OSX 10.9.5 I have had some experience using Final Cut and notice it tends to get quite slow when there's a few extra bits and pieces in the timeline of my project etc... Could this be to do with my CPU or my GPU or maybe even RAM? I know Hackintosh is a lot better on Intel CPUs so I thought maybe this could be what is making things a little sluggish? Everything else works fine! Should I upgrade to Intel and go through the trouble of getting everything back up and running again, or could it be done by simply upgrading my RAM? Cheers!
  12. I have successfully been able to boot into 10.7.4 with my 660/680 GPUs, surpassing many KPs by finding solutions online but the resolution is in VGA mode which is depressing (lol, not really). From what I know, Apple doesn't plan on supporting older OSs with the newer hardware, so I am asking the help from the hackintosh community to lead me to a patch that would allow me to utilize the native resolution of the GTX 6XX in Lion. Any useful help is appreciated, thanks.
  13. So essentially, after many years I finally got enough new parts to build a new PC with a Quad Core CPU. I previously had a Core 2 Duo w/ a MSI 975x Platinum Power-Up Edition Board that I had successfully installed 10.4, 10.5,10.6, and 10.8. While using another hard drive to run windows. Now I have: ASUS Sabertooth P67 (rev 3.1) Core i5 3570k AMD Radeon HD 6970 I've come to learn that the Radeon HD 6790 is essentially not compatible with any Mac OS, which I can learn to live with. I was at least able to install a distro of Mavericks and boot into safe mode for now. My random thought was this.. I have an older Radeon HD 4670 now laying around without a home. Could I put both in the PC and then just disable the card depending on the OS? IE. Use the newer card in windows 8 or Windows 7 on the one hard drive, and then run Mac OS and have it disable the newer incompatible card? I tried plugging it in for kicks and giggles and was at least still able to boot in safe mode, but I don't see an easy way of disabling the problematic card short of removing it every time i want to use Mac Os which doesn't really sound great long term. Any thoughts or suggestions? I plan on getting rid of the distro and installing as vanilla as possible again If i can find some sort of solution for the graphics card. The only posts I found for disabling a graphics chip were from mac pro owners with the lemon units.
  14. SummerRain

    GPU PCIe Link Speed

    Hi, everyone. I am new to the Hackintosh community. I am not sure if I am posting in the right forum. I apologize for that. I just got Yosemite (Clover) running on my PC with the following spec: CPU: Intel Xeon E5-2695 v2 MB: Asus X79-DELUXE GPU: EVGA GeForce GTX 770 SC 2GB I was checking the performance of my GPU using CUDA-Z and found out that my GPU is only running at PCIe 2.0 speed (80GB/s = 5.0GB/s x 16). My GPU is PCIe 3.0 and the MB supports PCIe 3.0 as well. What am I missing? Thank you.
  15. My graphic card is NVidia 560ti (Gigabyte). I have it works well with AGMP enabled (played WoW, Skyrim, etc..) However sometimes when I played those big games my system freeze. I am trying to figure out why and I guess it's something to do with the GPU. In NovaBench it gets Okay performance but scores is very low. I see others' reports with same performance, the Graphics Tests Score should be around 1200. But mine is only 400+. Does anyone know why?
  16. Hi guys, First post here. Hope I'm posting on the right place. I've been looking all over for this but can't find a decent answer. We're running Davinci Resolve system on a MacPro 5,1 with a PCI expansion chassis. We have two GTX Titan Black cards and we can't find a way to have them working properly. Resolve crashes all the time with no visible pattern. We guess it's a matter of web driver/CUDA/OSX Version combination but we really can't find one that works. So please guys if you can help me it would be much appreciated since we're going kind of crazy with this!! I'm sending the error report that we have after Davinci Crashes, hope it helps: Anonymous UUID: D06C9AF5-3DB3-6EB4-E4C3-FA6BB23F6880 Thu Mar 26 19:45:25 2015 *** Panic Report *** panic(cpu 2 caller 0xffffff7f96661635): NVRM[0/10:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x81000000 0xffffff82ed709000 0x0f10c0a1, D0, P2/4 Backtrace (CPU 2), Frame : Return Address 0xffffff82cfff3580 : 0xffffff8013b2fe41 0xffffff82cfff3600 : 0xffffff7f96661635 0xffffff82cfff36c0 : 0xffffff7f96755d99 0xffffff82cfff3710 : 0xffffff7f96755e23 0xffffff82cfff3780 : 0xffffff7f976f8f77 0xffffff82cfff37d0 : 0xffffff7f976f868c 0xffffff82cfff3840 : 0xffffff7f96781477 0xffffff82cfff3860 : 0xffffff7f96667f11 0xffffff82cfff3910 : 0xffffff7f96665744 0xffffff82cfff3b20 : 0xffffff7f96604e3c 0xffffff82cfff3b50 : 0xffffff7f966049ee 0xffffff82cfff3b60 : 0xffffff80141010cf 0xffffff82cfff3bc0 : 0xffffff80140fe9c3 0xffffff82cfff3d00 : 0xffffff8013be4a87 0xffffff82cfff3e10 : 0xffffff8013b33f8c 0xffffff82cfff3e40 : 0xffffff8013b18a93 0xffffff82cfff3e90 : 0xffffff8013b293bd 0xffffff82cfff3f10 : 0xffffff8013c059fa 0xffffff82cfff3fb0 : 0xffffff8013c36ea6 Kernel Extensions in backtrace: com.nvidia.web.NVDAResmanWeb(10.0.3)[1DB6D56A-64F7-3588-8B69-8B6E239AFCD7]@0xffffff7f965ff000->0xffffff7f968fffff dependency: com.apple.iokit.IOPCIFamily(2.9)[56AD16B5-4F29-3F74-93E7-D492B3966DE2]@0xffffff7f94324000 dependency: com.apple.iokit.IONDRVSupport(2.4.1)[E5A48E71-70F5-3B01-81D3-C2B037BBE80A]@0xffffff7f94bf0000 dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[619F6C9F-0461-3BA1-A75F-53BB0F87ACD3]@0xffffff7f94ba9000 dependency: com.apple.AppleGraphicsDeviceControl(3.8.6)[957EB27F-7D07-3C40-91F5-9B54652F06EE]@0xffffff7f95968000 com.nvidia.web.NVDAGK100HalWeb(10.0.3)[F174A468-22FA-3822-B973-B9C09D02818D]@0xffffff7f97600000->0xffffff7f977b2fff dependency: com.nvidia.web.NVDAResmanWeb(10.0.3)[1DB6D56A-64F7-3588-8B69-8B6E239AFCD7]@0xffffff7f965ff000 dependency: com.apple.iokit.IOPCIFamily(2.9)[56AD16B5-4F29-3F74-93E7-D492B3966DE2]@0xffffff7f94324000 BSD process name corresponding to current thread: Resolve Boot args: nvda_drv=1 Mac OS version: 14C109 Kernel version: Darwin Kernel Version 14.1.0: Mon Dec 22 23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64 Kernel UUID: DCF5C2D5-16AE-37F5-B2BE-ED127048DFF5 Kernel slide: 0x0000000013800000 Kernel text base: 0xffffff8013a00000 __HIB text base: 0xffffff8013900000 System model name: MacPro5,1 (Mac-F221BEC8) System uptime in nanoseconds: 2077571857892 last loaded kext at 564412906118: com.apple.driver.AppleFireWireStorage3.5.1 (addr 0xffffff7f977c0000, size 16384) last unloaded kext at 770079959914: com.apple.driver.AppleUSBCDC4.2.2b5 (addr 0xffffff7f977b3000, size 16384) loaded kexts: com.nvidia.CUDA1.1.0 com.nvidia.web.NVDAGK100HalWeb10.0.3 com.nvidia.web.GeForceWeb10.0.3 com.nvidia.web.NVDAResmanWeb10.0.3 com.apple.driver.AudioAUUC1.70 com.apple.driver.AppleHWSensor1.9.5d0 com.apple.driver.AppleTyMCEDriver1.0.2d2 com.apple.driver.AGPM100.15.5 com.apple.driver.AppleOSXWatchdog1 com.apple.iokit.IOBluetoothSerialManager4.3.2f6 com.apple.filesystems.autofs3.0 com.apple.driver.AppleMikeyHIDDriver124 com.apple.driver.AppleMikeyDriver269.25 com.apple.driver.AppleUpstreamUserClient3.6.1 com.apple.driver.AppleMCCSControl1.2.11 com.apple.kext.AMDFramebuffer1.3.0 com.apple.iokit.IOUserEthernet1.0.1 com.apple.driver.AppleHDA269.25 com.apple.AMDRadeonX30001.3.0 com.apple.Dont_Steal_Mac_OS_X7.0.0 com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport4.3.2f6 com.apple.driver.AppleHWAccess1 com.apple.driver.AppleLPC1.7.3 com.apple.kext.AMD5000Controller1.3.0 com.apple.driver.AppleHV1 com.apple.driver.ACPI_SMC_PlatformPlugin1.0.0 com.apple.driver.XsanFilter404 com.apple.iokit.IOAHCIBlockStorage2.7.0 com.apple.iokit.SCSITaskUserClient3.7.3 com.apple.driver.Oxford_Semi3.5.1 com.apple.AppleFSCompression.AppleFSCompressionTypeDataless1.0.0d1 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib1.0.0d1 com.apple.BootCache35 com.apple.driver.AppleFWOHCI5.5.2 com.apple.driver.Intel82574L2.6.7b2 com.apple.driver.AppleUSBHub705.4.2 com.apple.driver.AirPort.Brcm4331800.20.24 com.apple.driver.AppleRAIDCard401 com.apple.driver.AppleAHCIPort3.1.0 com.apple.driver.AppleUSBEHCI705.4.14 com.apple.driver.AppleUSBUHCI656.4.1 com.apple.driver.AppleRTC2.0 com.apple.driver.AppleHPET1.8 com.apple.driver.AppleACPIButtons3.1 com.apple.driver.AppleSMBIOS2.1 com.apple.driver.AppleACPIEC3.1 com.apple.driver.AppleAPIC1.7 com.apple.driver.AppleIntelCPUPowerManagementClient218.0.0 com.apple.nke.applicationfirewall161 com.apple.security.quarantine3 com.apple.security.TMSafetyNet8 com.apple.driver.AppleIntelCPUPowerManagement218.0.0 com.apple.iokit.IOSerialFamily11 com.apple.kext.triggers1.0 com.apple.iokit.IOSurface97 com.apple.driver.DspFuncLib269.25 com.apple.kext.OSvKernDSPLib1.15 com.apple.iokit.IONDRVSupport2.4.1 com.apple.iokit.IOAcceleratorFamily2156.6 com.apple.driver.AppleSMBusController1.0.13d1 com.apple.iokit.IOBluetoothHostControllerUSBTransport4.3.2f6 com.apple.iokit.IOBluetoothFamily4.3.2f6 com.apple.iokit.IOFireWireIP2.2.6 com.apple.driver.AppleHDAController269.25 com.apple.iokit.IOHDAFamily269.25 com.apple.iokit.IOAudioFamily203.3 com.apple.vecLib.kext1.2.0 com.apple.driver.AppleSMBusPCI1.0.12d1 com.apple.iokit.IOUSBUserClient705.4.0 com.apple.kext.AMDSupport1.3.0 com.apple.AppleGraphicsDeviceControl3.8.6 com.apple.iokit.IOGraphicsFamily2.4.1 com.apple.driver.AppleSMC3.1.9 com.apple.driver.IOPlatformPluginLegacy1.0.0 com.apple.driver.IOPlatformPluginFamily5.8.1d38 com.apple.driver.AppleUSBHIDMouse185.3 com.apple.driver.AppleHIDMouse185.3 com.apple.driver.AppleUSBHIDKeyboard176.2 com.apple.driver.AppleHIDKeyboard176.2 com.apple.iokit.IOUSBHIDDriver705.4.0 com.apple.driver.AppleUSBMergeNub705.4.0 com.apple.iokit.IOUSBMassStorageClass3.7.1 com.apple.driver.AppleUSBComposite705.4.9 com.apple.iokit.IOFireWireSerialBusProtocolTransport2.5.1 com.apple.iokit.IOFireWireSBP24.2.5 com.apple.iokit.IOFireWireFamily4.5.6 com.apple.iokit.IO80211Family710.55 com.apple.iokit.IONetworkingFamily3.2 com.apple.iokit.IOSCSIParallelFamily3.0.0 com.apple.iokit.IOSCSIBlockCommandsDevice3.7.3 com.apple.iokit.IOSCSIArchitectureModelFamily3.7.3 com.apple.iokit.IOAHCIFamily2.7.5 com.apple.iokit.IOUSBFamily710.4.14 com.apple.driver.AppleEFINVRAM2.0 com.apple.driver.AppleEFIRuntime2.0 com.apple.iokit.IOHIDFamily2.0.0 com.apple.iokit.IOSMBusFamily1.1 com.apple.security.sandbox300.0 com.apple.kext.AppleMatch1.0.0d1 com.apple.driver.AppleKeyStore2 com.apple.driver.AppleMobileFileIntegrity1.0.5 com.apple.driver.AppleCredentialManager1.0 com.apple.driver.DiskImages396 com.apple.iokit.IOStorageFamily2.0 com.apple.iokit.IOReportFamily31 com.apple.driver.AppleFDEKeyStore28.30 com.apple.driver.AppleACPIPlatform3.1 com.apple.iokit.IOPCIFamily2.9 com.apple.iokit.IOACPIFamily1.4 com.apple.kec.corecrypto1.0 com.apple.kec.Libm1 com.apple.kec.pthread1 Model: MacPro5,1, BootROM MP51.007F.B03, 12 processors, 6-Core Intel Xeon, 2.66 GHz, 24 GB, SMC 1.39f11 Graphics: ATI Radeon HD 5870, ATI Radeon HD 5870, PCIe, 1024 MB Graphics: NVIDIA GeForce GTX TITAN Black, NVIDIA GeForce GTX TITAN Black, PCIe, 6143 MB Graphics: NVIDIA GeForce GTX TITAN Black, NVIDIA GeForce GTX TITAN Black, PCIe, 6143 MB Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x33364A535A4631473732505A2D3147344431 Memory Module: DIMM 2, 8 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x33364A535A4631473732505A2D3147344431 Memory Module: DIMM 3, 8 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x33364A535A4631473732505A2D3147344431 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 ( Bluetooth: Version 4.3.2f6 15235, 3 services, 27 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en2 Serial ATA Device: Samsung SSD 850 PRO 256GB, 256,06 GB USB Device: External USB 3.0 USB Device: SecureLock USB Device: USB 2.0 Hub [MTT] USB Device: USB 2.0 Hub [MTT] USB Device: element-Tk USB Device: Keyboard Hub USB Device: Apple Optical USB Mouse USB Device: Apple Keyboard USB Device: element-Kb USB Device: element-Bt USB Device: element-Mf USB Device: USB DONGLE USB Device: BRCM2046 Hub USB Device: Bluetooth USB Host Controller FireWire Device: built-in_hub, Up to 800 Mb/sec FireWire Device: Device 00, G-SPEED Q - RAID Protected Storage, Up to 800 Mb/sec FireWire Device: JMicron H/W RAID0, OWC, Up to 800 Mb/sec Thunderbolt Bus: THANKS GUYS!!
  17. wildboarcharlie

    Full Resolution on R9 290X

    Hey guys, I've gotten most of my setup to work, but my R9 290X won't give me full resolution on my Ultrawide 21:9 display... I'm connected using HDMI and it gives me 1920x1080 which is not the full 2560x1080 my display can take. I fiddled with System Preferences and even SwitchResX and can't get it to work. I also noticed that HDMI audio doesn't work either. What can I do?
  18. Hello! I'd like to ask for some help with the installation of OS X 10.11.6 on a Dell latitude E5430. The problem is, that I can't get to the installation screen. More precisely, when I get there the screen glitches out so I can't even start the installation. After connecting the laptop to an external monitor the install screen appears with a cursor but the screen is still completely unreadable... I'm not an expert but I think the problem is somewhere in the video support... So I've tried several guides and fixes but none of them worked for me. (I managed to get past a missing IOBluetooth panic by using a patched dsdt) With a combination of different config settings, dsdts and kexts I managed to reach the installation screen but only without any input at all... After fixing the input problem the screen was gone again... Do you have any similar experience? Please help if you have any idea for a solution! Thank you in advance, MadFive SPECS: model: Dell latitude E5430 resolution: 1366 x 768 CPU: Intel Core i5 3320M / 2.6 GHz (SandyBridge?) GPU: Intel HD Graphics 4000 memory: 8GB Boot Loader: Clover 4128 files: https://drive.google.com/open?id=0Bxw0nqNU5VKFUDF0OUFUM0dSY0k
  19. I've searched for viable information, benchmark tests for GPU utilization for mac. More Specifically in the video conversion department. So without comprising quality, the CPU is currently the only way of increasing video handling performance. With the addition of CUDA and other direct GPU accelerators, I would like to know what other members are using with good performance. For testing with a GForce 9400 (supposedly a CUDA enabled, but mixed information on that, maybe only the 9400M) CUDA driver installed, but no performance feedback on the CUDAZ app.. Why does apple seem to hold back in the graphics dept on everything except a $3000.00 Mac Pro...? Are we really still sharing memory with the system??? I think that my first IBM Think Pad had that?? lol Thanks Folks!!!
  20. I recently installed a GTX 960 in my system running 10.10.3. Shortly after installing the new card, I started experiencing an issue in which the system would randomly close out all running applications and drop to the login screen. This was happening several times a day, and without any discernible rhyme or reason (it happened both while running graphics intense apps as well as normal system operation). Based on my review of the logs, it looks like the WindowServer process was crashing, with numerous references to both the OS X and nVidia drivers in the crash logs. Last night I put my old GTX 650 card back in the system and uninstalled the nVidia web drivers (I was running the latest version - 346.01.02f03). I have yet to experience the issue again, leading me to believe that it was probably related to the nVidia web drivers. Has anyone else experienced the same thing? I would really like to use the GTX 960 in my system, but the sporadic logouts are definitely a deal-breaker. Any thoughts or insight would be greatly appreciated!
  21. Hello! Does anyone know if R9 285 or R9 280 work OOB in Yosemite?I know for sure that R9 280X does,but I'm not sure about these two cards..I haven't found many topics in which they are mentioned, and I want to be sure that HDMI and DVI work OOB..has anyone tested them?I don't want to buy a graphics card and then have to return it and buy another one..
  22. I have long been running Snow Leopard on my Dell Precision M4400. However, I irrevocably destroyed my HacOS install when I upgraded to 10.6.8. I thought it was the "PCI Configuration End" error, but it turns out that removing AppleHDA.kext solves a lot of problems. I also reverted to IOPCIFamily and AppleAPCI kexts from a previous version to get 10.6.8 working. However, with a similar setup for 10.7.0-.2, the GUI simply never loads. I am about to try NVEnabler.kext. Does anyone have any suggestions? This machine is similar to the Latitude E6500, but it has an Nvidia Quadro FX1700M GPU. Best, Nightalon in NYC
  23. Hi guys, wanted to install OS X El Capitan on my desktop PC using the Clover bootloader. That worked with a slightly modified standard config.plist from TonyMacx86 guide for Yosemite with Clover. Just for your information, my hardware components: The used config.plist is appended. The installation worked, but when I come to my desktop after a short period of time always the screen turns black (not when I am in safe mode, but I can not mount partitions in this mode, etc.). Well, obviously this seems to be a GPU related problem so I tried already different things to solve this issue: 1. In Clover configurator I added the Fake ID "0x67B01002" under devices in "ATI". 2. Under "Graphics" I enabled "LoadVBios" and pasted my .ROM (I exported that for my video card approx. 1 week ago with GPU-Z under windows) under EFI/CLOVER/ROM in the right format (in my case 1002_67B0.rom) (also attached). Unfortunately, all of this measures could not solve my issue. Would appreciate your help, thanks! EDIT: I could solve that issue. For my GPU it was necessary to insert under "Graphics" in "FBName" "kBaladi" and now it works. configPlist.zip GPU-UEFI.zip
  24. Please, excuse my poor English. My GTX560Ti works fine AGPM(AppleGraphicsPowerManagement) with ONE monitor. GPU core frequencies, voltages work well according to g-state's changes. But, with dual monitors, GPU's frequencies and voltages are no change.. My card always clocks up to its maximum performance even if it's not under load. (core 880MHz, shader 1760MHz, memory 2100MHz, and voltages 1.00V) As soon as I unplugged secondary monitor, it clocked down to 50MHz, within seconds. I've done a lot of testing(changing system identifies, modification info.plist in AGPM, etc), my logs show that GPU switches g-states as it should, however the GPU clock never changes. Of course, under Windows 8, GPU clocks and voltages change very well in dual monitors. My question is: Is it impossible that fermi card controls GPU power management in dual monitors?
  25. Osira

    mac pro geforce 8800 GTS

    Been a while since me and a pal managed to turn a couple of dell mini 9s into leopard netbooks and then kill them with 10.5.8 and thus it's so good to see there is still a thriving community here ... hoping you can help me Does anyone know if your group's nvidia webdriver updater will successfully flash the ROM in the non-approved (by Apple!) 8800 GTS (the GT was approved, but not the GTS) - so it will work in a mac pro 3,1 with El Capitan ? (by 'work' I mean 100% fully work - not just login screen but all boot screen options) May seem an odd thing to do but amongst my other projects keeping this behemoth (3,1 intel xeon 8 core 8GB RAM 2008/9) mac pro with bootcamp running as something more than just a home NAS (4x4TB drives in the bays) and file server is high up my list and I am never going to be able to stump up the cash for an apple $$$ approved card Things I think I know, but suspect some folk here will have found a way around or know better; 1) without flashing, I will never get the options at boot, or be able to see SUDO or recovery options 2) I can use screen sharing / VNC viewer / Vine to remote into the mac at the login screen, and use startup disk prefs to switch between bootcamp and OSX, but not OSX DVDs on an external DVD over USB 3) I have been pointed at netkas but they seem to be down currently ... and when last up appear to be focused on flashing just the high end newer PC gaming cards (1GB VRAM and up) - this 8800 GTS is just a 320mb) Any info will be much appreciated, hate binning kit like this .... cheers Andy