Contribute
Register

GTX 690 Issues

Status
Not open for further replies.
Joined
Oct 21, 2012
Messages
118
Motherboard
Hackintosh/PC
CPU
i5 3570K
Graphics
GTX 690
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Afternoon people,

I just upgraded to a GTX 690 from a GTX 210. Initially the system hung completely, I had to use the flags "PCIRootUID=1 npci=0x3000 -x" if I don't use the "-x" it will crash once I get to the desktop. From this I assume that it is a particular kext causing the issues?

Should I be installing any MultiBeast options now I have this 600 series card or is it fully supported naturally?


Kind Regards,

Dan.
 
You shouldn't need to install anything from MultiBeast, if you read the description you'l see that none of the patches apply to your card. Have you changed GraphicsEnabler=No in the org.chameleon.Boot.plist? I'm running a 660Ti and that is the only setting needed.
 
I have tried GraphicsEnabler=No, that didn't help. I the method I mention in my OP no longer works since changing the SysDef from mac mini 5,1 to mac pro 3,1 when I was last in the OS. Really odd.
 
Ok I'm back in using cpus=1 and -x

The -x is vital currently. Total boot arguments are PCIRootUID=1 npci=0x3000 cpus=1 -x
 
I have the best luck using macpro5,1. Here is my boot.plist if you want a look...

Code:
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>EthernetBuiltIn</key>
    <string>Yes</string>
    <key>GenerateCStates</key>
    <string>Yes</string>
    <key>GeneratePStates</key>
    <string>Yes</string>
    <key>GraphicsEnabler</key>
    <string>No</string>
    <key>Graphics Mode</key>
    <string>1920x1080x32</string>
    <key>Kernel</key>
    <string>mach_kernel</string>
    <key>Kernel Flags</key>
    <string>npci=0x3000 darkwake=No</string>
    <key>Legacy Logo</key>
    <string>Yes</string>
    <key>Timeout</key>
    <string>2</string>
    <key>Boot Banner</key>
    <string>No</string>
    <key>UseKernelCache</key>
    <string>Yes</string>
    <key>Rename Partition</key>
    <string>"/" Arch</string>
</dict>
</plist>

I don't need PCIRootID, so you might want to add it if you need.
 
No improvement. Kernel Panic text is as below when I login without -x

8470E958-3185-404F-A0ED-CA653ECFC0C9-6819-0000044B768968F4.jpg


before this GFX Card I didn't have to use cpus=1 or npci=0x3000. I did use PUCRootUID but it was 0 and now I use 1.
 
No improvement. Kernel Panic text is as below when I login without -x

8470E958-3185-404F-A0ED-CA653ECFC0C9-6819-0000044B768968F4.jpg


before this GFX Card I didn't have to use cpus=1 or npci=0x3000. I did use PUCRootUID but it was 0 and now I use 1.

You have a couple of issues there...
your calling PCIRootUID 2x? it should be either 0 or 1. ncpi should be 0x3000. Darkwake is either Yes or No, not 0. Do you have a fusion drive setup? I assume so given you boot argument "boot-uuid=xxxxx... and rd=*uuid. Try getting rid of those flags.
 
Good spot, but I have no idea where those arguments are coming from. My org.chameleon.boot.plist can be seen below;

BAA76219-14BE-488F-A56B-0132E7D4E31A-6924-00000457A6C51484.jpg


the only additions I use when I boot with UniBeast USB is cpus=1 and -x

I do not have a FusionDrive, 2 SSD's, one with 10.8.2 and one with Windows 7.

As for darkwake I am pretty sure it is 0, this was put in there by MultiBeast? It hasn't caused an issue with my previous setup. This system was perfect in every way until the 690 was installed.
 
The extra arguments seemed to be being injected by the UniBeast stick. I think this because If i remove the UniBeast stick and allow the system to boot without it I no longer see the duplicate arguments but I do have the same out come. system only boots with -x

I have looked for a panic log but cannot find one anywhere, console app, library/log, var/log. Any ideas where I might find it?


EDIT:

i used debug=0x100 and got this;

15FC0CCC-E17C-4995-BB7B-54DBD1594773-6924-00000460874AE13E.jpg
 
No improvement. Kernel Panic text is as below when I login without -x

8470E958-3185-404F-A0ED-CA653ECFC0C9-6819-0000044B768968F4.jpg


before this GFX Card I didn't have to use cpus=1 or npci=0x3000. I did use PUCRootUID but it was 0 and now I use 1.

Don't mean to derail, but how do you have a photo in the BG of your bootscreen?
 
Status
Not open for further replies.
Back
Top