Jump to content
InsanelyMac Forum

starbot

Members
  • Content count

    8
  • Joined

  • Last visited

About starbot

  • Rank
    InsanelyMac Protégé
  1. Wow. This is embarassing. Turns out I'm an idiot and didn't realize that my drive letters were changed after I re-connected my platter drives. My programs that were slower than usual were installed there... sighhhh.
  2. Here's a bizarre question. I successfully created a dual-boot setup for OSX ML and Windows 7. Has anyone noticed slower performance on their Windows 7 partition? I used to run my SSD only with Windows 7 and gaming was very smooth. However, now that I dual boot and boot into Windows 7 with Chameleon, I've noticed that performance has become significantly choppier. Not sure if there's something else, but I was wondering if anyone else noticed this issue or had any thoughts of how to address this.
  3. GTX 460 - Stuck at 1024x768 in 10.7.4

    Just a follow-up. Installing Mountain Lion solved my graphic issues. Card works out of the box (even installation has full resolution) and power management issue is native now (no longer need AGPM.kext modifications).
  4. GTX 460 - Stuck at 1024x768 in 10.7.4

    I still haven't managed to find a solution yet, but I'm planning to try again once Mountain Lion comes out. From what I've read, it looks like nVidia drivers are easier to access and don't require much beyond a GraphicsEnabler=Yes.
  5. GTX 460 - Stuck at 1024x768 in 10.7.4

    Ah...so I'm still at the issue of loading the extensions. That would make sense because the very first time I installed my GTX 460 it was displayed as Unknown, yet it had full acceleration. I might be making some progress, but this is a strange issue. I managed to update the drivers without touching anything else, but I'm not able to get into my system. It's now hanging on "MACX_SWAPON SUCCESS", and I can't find a way around it. Booting into -x, 32-bit, -f, various graphic flags doesn't do anything. What does this particular message mean?
  6. GTX 460 - Stuck at 1024x768 in 10.7.4

    This is a really strange issue. I've tried multiple methods to set up the card in 10.7.4, including injecting my edits (with Graphics Enabler = No) into the chameleon.Boot.plist and adding device IDs in NVDAGF100Hal.kext. In all cases, I am able to get OSX to identify my card (card shows in in Apple > About as the correct name and not as Unknown). The problem is that it still refuses to use it. The most I can set my resolution at is 1280x1024 (adding Graphics Mode in the plist), but it's far from complete hardware acceleration that I was able to get the very first time. I thought there may have been something else wrong with my computer, so I plugged in an old video card (GTS 250), and everything loaded perfectly with Graphics Enabler = Yes. I shut down the system, plugged my GTX 460 back in, and the same issue returns with low resolution an no hardware acceleration. I'm at the point where I'm either considering to not use this computer as a Hackintosh (dedicated Windows computer), or if I should hold off to see if Mountain Lion 10.8 gives me a second chance at getting this card to work.
  7. GTX 460 - Stuck at 1024x768 in 10.7.4

    Thanks for the response Gringo. I tried PciRoot=1 (along with GraphicsEnabler=Yes) and was able to get back into my system, but it's still showing up with a 1024x768 resolution. I went ahead and downloaded the May update from nVidia and enabled OpenGL+OpenCL again. Although I didn't do this before, I added my device ID into the NVDAGF100Hal.kext > Info.plist (0x120510de&0xffe0ffff). I then repair system permissions and rebooted. Unfortunately, same result when OSX loaded again, and I'm still trying to figure out what I did wrong. The system still shows that it recognizes the card in Apple > About, so am I not loading the next properly? What's a recommended tool to enable OpenGL+OpenCL? Just throwing this out there in case this has any effect. Do the SATA ports matter once the install and boot loader are complete? I'm trying to see if there's any difference in my hardware configuration as before, and I'm wondering if it's because I plugged the SATA cable into a different port (still the main blue SATA ports and not the white ports). Other drives have been disconnected except for my DVD drive.
  8. Hello there! Long-time lurker that has finally surfaced because of a mystery that I haven't been able to solve for the past few weeks. I'm hoping some of you brilliant people can help me out with this issue that I ran (and fell flat on my face) into. First off, here are my system stats: i5 750 2.66 : GIGABYTE GA-H55M-USB3 F11 4GB - G.SKILL Ripjaws Series 4GB : Crucial m4 SSD 512GB MSI GTX 460 1GB v2 All hardware has worked well before, so I wasn't expecting any issues. I recently bought a SSD and decided to reinstall everything instead of cloning the drive. The first time I installed, everything seemed to be fine (dual boot: Win7 and 10.7.4 on SSD drive). However, due to a preference in partition size, I started from scratch. I did the usual process of partioning, installing Windows 7, then OSX 10.7.4. Now, here's where I started running into problems. Normally after installing Chimera/Chameleon, installing a DSDT, and setting GraphicsEnabler=Yes, I immediately see full resolution and have QE/CI with my GTX 460 (at this point, I normally just improve stability/smoothness by modifying my AGPM). I believe this is due to the latest fermi drivers already being bundled into 10.7.4, whereas in older versions I needed to download an nvidia driver. What's strange is that during this round of installing, my OSX is stuck at 1024x768. Even after several attempts and formats, I can't seem to get my system to show full resolution and hardware acceleration. Information in "Apple > About" shows that OSX is recognizing my card, but it doesn't seem to want to use it. I've added the usual tags (npci=0x2000, npci=0x3000, PCIUID=0/1, GraphicsEnabler=Yes/No, etc), but nothing will get OSX to use the GTX 460 properly. I've run the OpenGL+OpenCL enabler (I believe this patches NVDAGF100HAL and the GeForce.bundle), but this seems to cause a KP. I don't have a snapshot available, but the last message during a verbose boot hangs at "Sound Assertion in AppleHDADriver at line ####" (this confuses me because I wasn't yet working on audio kexts). It still boggles my mind that I've succeeded before with the exact same hardware, yet now I'm running into this issue (maybe I'm bordering on insanity and missing a critical step). Any advice? I appreciate any comments as I'm completely stumped.
×