Jump to content

e13c7r0nic

Just Joined
  • Content count

    4
  • Joined

  • Last visited

About e13c7r0nic

  • Rank
    InsanelyMac Protégé
  1. Help with EVGA GeForce 9500 GT

    Did this work? I have the same computer. I haven't been able to get it to work with anything either. I've also tried everything, GraphicsEnabler, EFI strings, NVinject, NVkush, NVEnabler. I've flashed my card to get the NVCAP and generate a custom EFI string, etc. I've tried all of these one at a time so as to isolate the cause. It's an AMD system, so I've ran Marvin's AMD Utility to patch kexts with UUIDs and replace encrypted ones. What I'm going to try now is replacing NVDAResman and NVDANV50Hal with the ones from 10.5.5, which, I've read, worked. Anybody else been able to get CI/QE on this machine on 10.6.x?
  2. Dell Dimension E521 Working with Leo4AllV3!

    I'm also trying to get OS X running on a Dell Dimension E521. I was able to install 10.6.4, but I can't for the life of me get hardware acceleration for my video card. I've tried two cards and have gotten the same result. When I add my hardware ID to NVDAResman I get video through the boot sequence all the way until it load the window manager, i.e. the desktop is supposed to be displayed. At that point the monitor turns off. Has anyone been able to get CI and QE to work on an E521?
  3. GT 240 Woes

    When one uses EFI strings, is it still needed to patch NVDAResman and NVDANV50Hal (in my case)? And, if I'm not mistaken, I shouldn't have to used the PciRoot keyword in Chameleon either, right? The EFI string already contains information about the root PCI device, or should I also use it with device-properties? I've checked with Lizard and my PCI root is 1. I'm having a hell of a time making my EVGA GeForce 8400GS work with my NForce 430 motherboard. I've tried everything. The issue it's come down to is that whenever I patch NVDAResman with my card's device ID, aftert the initial boot sequence, the signal to my monitor stops when the UI/Desktop is supposed to be displayed, and so it just goes into that sleep kind of mode that monitors go into when one turns off or set one's computer to sleep to. NVEnabler was able to give me CI and QE, but at the cost of screwing up my USB mouse and keyboard. First the mouse was super sensitive and moved in the opposite direction than you moved it to and the keyboard wouldn't work at all. After a reboot, the mouse corrected itself, but the keyboard still didn't respond. Anyways, I have a feeling my issue is NVCAP related, so I'm going to try the method described at the beginning of this thread to create a custom EFI string with OSX86Tools.
  4. I have the same issue. I have an EVGA nVidia GeForce 8400GS on an NForce 430 chipset, device ID is 0x06e410de, and the monitor is connected to the VGA port. I've tried every single injector, NVinject, NVKush, NVEnabler, and other methods, e.g. EFI strings, GraphicsEnabler in Chameleon, everything. I would always get either the black screen, or the monitor would shut down after the initial boot process, i.e. loading of the kernel and extensions and stuff. I finally narrowed it down by process of elimination that the issue is with NVDAResman and when I edit it. When I insert my device ID properly and the drivers kick in, that's when I get the monitor turning off. I had some success with NVEnabler. I actually got CI and QE, but it broke the mouse and the keyboard. I would get that issue where the mouse becomes super sensitive and moves in the opposite direction than the one you move it in; the keyboard just doesn't respond. After a restart, the mouse works as it should, but it doesn't respond to any clicks and the keyboard still didn't work. I read somewhere that NForce and nVidia cards had some kind of conflict. They recommended to delete all the device IDs from NVDAResman and just leave the one for my card. Tried that. Didn't work. All this, and the fact that NVEnabler actually yielded CI/QE, leads me to believe that it's an NVCAP issue. I'm going to try EFI strings again with the two different output settings, DVI I/VGA and VGA/DVI I. I really don't understand the difference between those two, so if you can share any insight into that, that'd would be much appreciated. If either of those doesn't work, I'm going to try getting the NVCAP values for my card using this method. If anybody else has figured out this issue or has any good suggestions, please share.
×