Hi all,
This is my first attempt at a post in this forum, and I hope someone might be able to help me.
I am running iDeneb 10.5.7 (upgraded to 10.5.8) with an EVGA GeForce 9600 GT 256 MB PCIx card. I started out with the NVKush injector, had some trouble there, and then ... here's what I've tried:
- NVKush: card listed as supported for Quartz Extreme and QuartzGL, but crashed all the time and often resulted in blurry display with smudged looking text on screen.
- NVInject: Quartz Extreme listed as not supported, more stable than NVKush, but couldn't run anything that required decent graphics
- NVEnabler: booted into a black clear screen (not a dead monitor signal), with a mouse pointer that I could move around the screen but do nothing with
- Adding EFI string (from OSX86Tools) to boot.plist, but same as above: black clear screen, with a mouse pointer that I could move but do nothing with
- Deleted all NV* kexts from Extensions, left EFI string in boot.plist, cleaned up permissions, and rebooted. Got VGA graphics and 1024x758 res on my Asus 24" widescreen (native is 1920x1080).
- Re-added EFI string to boot.plist, cleaned up, and rebooted. Still stuck in 1024x768, but Profiler does now display my card with actual model and actual vendor and device IDs. Profiler no longer shows my ASUS monitor model, which it used to:
Click to view attachment
What do I need to do to get a high res display back, without all the crashing?
Thanks for your help!
Full Version: Trouble With Geforce 7600 Gt In 10.5.8
Project OS X Forums > Previous Releases > Mac OS X Leopard 10.5 > Leopard Guides & Tutorials > New Users Discussion
I have the same card. You need NV* kexts and EFI Strings. Just try with many EFI Strings as you can. Sometimes the right string doesn't work, but a similar model string works.
QUOTE (slashack @ Nov 22 2009, 02:04 PM) 
I have the same card. You need NV* kexts and EFI Strings. Just try with many EFI Strings as you can. Sometimes the right string doesn't work, but a similar model string works.
Thanks slashack. I got an EFI string from the tool in OSX86Tools, and putting that in Boot.plist seems to give me just VGA, which I assume is not useful. What's a good resource for finding EFI strings? Is there any chance that your string would work with mine? My reported IDs are:Vendor: NVIDIA (0x10de)
Device ID: 0x0391
Revision ID: 0x00a1
QUOTE (deesto @ Nov 22 2009, 08:24 PM)
Thanks slashack. I got an EFI string from the tool in OSX86Tools, and putting that in Boot.plist seems to give me just VGA, which I assume is not useful. What's a good resource for finding EFI strings? Is there any chance that your string would work with mine? My reported IDs are:
Vendor: NVIDIA (0x10de)
Device ID: 0x0391
Revision ID: 0x00a1
Vendor: NVIDIA (0x10de)
Device ID: 0x0391
Revision ID: 0x00a1
I've got snow leopard now. But the problem is you've deleted NV* kexts. Don't delete any kext.
QUOTE (slashack @ Nov 23 2009, 10:18 AM)
I've got snow leopard now.
With this card? Did you upgrade from 10.5 or start over from scratch?QUOTE
But the problem is you've deleted NV* kexts. Don't delete any kext.
Well that's true, as I thought I'd read that as part of a possible solution ... but I was able to restore the NV* kexts from a backup OSX86 partition. The problem after restoring them is even with the EFI string, I get only VGA unless I add an injector kext, which means the EFI isn't working, and even then I am not getting GL support. I tried EFI Studio, which gave me the same exact EFI string as OSX86Tools, must be reading it from some static file or database.
QUOTE (deesto @ Nov 23 2009, 12:45 PM)
With this card? Did you upgrade from 10.5 or start over from scratch?
Well that's true, as I thought I'd read that as part of a possible solution ... but I was able to restore the NV* kexts from a backup OSX86 partition. The problem after restoring them is even with the EFI string, I get only VGA unless I add an injector kext, which means the EFI isn't working, and even then I am not getting GL support. I tried EFI Studio, which gave me the same exact EFI string as OSX86Tools, must be reading it from some static file or database.
Well that's true, as I thought I'd read that as part of a possible solution ... but I was able to restore the NV* kexts from a backup OSX86 partition. The problem after restoring them is even with the EFI string, I get only VGA unless I add an injector kext, which means the EFI isn't working, and even then I am not getting GL support. I tried EFI Studio, which gave me the same exact EFI string as OSX86Tools, must be reading it from some static file or database.
Started from iAtkos V7. Then updated to 10.5.8
Are you sure those kexts are from 10.5.8? Just make sure they are.
The solution it's easy. Start trying injectors or efi strings until they work. As I said before, if your graphic card model's efi string doesn't work, then try a different model. For example, for a 7200GT I used an efi string for 8200GT. The right one didn't worked.
7600GT Works. It just a matter of getting the right solution. Deleting KEXTs will never lead to get QE/CI working. NEVER delete kext's. Just move them to another place.
It's precised in NVEnabler topic that you might need to remove the display-cfg strings, and it looks it's the problem you got. Try again without and it should work fine.
Hi folks,
Thanks Krazubu. The problem with that theory is that I'm not using NVEnabler anymore.
I was just trying to go with the EFI string in the boot file. I shouldn't need an injector in addition to that, should I?
At any rate, the relevant stuff in the topic you mentioned is:
So, if I were to try NVEnabler again, would I remove the cfg values entirely, or replace them with one of these strings?
QUOTE (slashack @ Nov 23 2009, 08:52 PM)
Started from iAtkos V7. Then updated to 10.5.8
OK, but how did you get from there to Snow Leopard?QUOTE
Are you sure those kexts are from 10.5.8? Just make sure they are.
Not sure how to make sure they are specific to 10.5.8, but I copied them from a separate 10.5.8 OSX partition on another disk.QUOTE
The solution it's easy. Start trying injectors or efi strings until they work. As I said before, if your graphic card model's efi string doesn't work, then try a different model. For example, for a 7200GT I used an efi string for 8200GT. The right one didn't worked.
OK, tried 6 or 7 different strings last night ... which wasn't easy, as my system doesn't shut down or restart cleanly from OSX (if I'm lucky, I get a message "you can reboot this computer now"), and it takes 5-10 minutes to boot into OSX (90% or more of which is a black or blue screen). So far they all resulted in a black screen with a mouse pointer that moves.QUOTE
7600GT Works. It just a matter of getting the right solution. Deleting KEXTs will never lead to get QE/CI working. NEVER delete kext's. Just move them to another place.
I hope you're right! I wish I knew what that solution was. I haven't deleted anything I didn't have a backup for. But there is a suggested solution out there somewhere to 'rm -rf NV*', which is where I got the idea that this was necessary.QUOTE ( @ Nov 24 2009, 05:22 AM)
It's precised in NVEnabler topic that you might need to remove the display-cfg strings, and it looks it's the problem you got. Try again without and it should work fine.
Thanks Krazubu. The problem with that theory is that I'm not using NVEnabler anymore.
I was just trying to go with the EFI string in the boot file. I shouldn't need an injector in addition to that, should I?At any rate, the relevant stuff in the topic you mentioned is:
QUOTE
We are currently getting trouble with the display-cfg string. We don't know how it works at all so far. If you're having problems with NVEnabler, it's most probably because of that string (blue or black screen at boot, screen going off, wrong one on...).
We then suggest you to try different values in the plist, taken from real macs. That's all what we can do for the moment.
there's one string for each screen (@0,Display-cfg & @1,Display-cfg)
macbook pro 8600GT : 03010000 - ffff0001
macbook pro unibody 9400 : 03010300 - ffff0801
macbook pro white 9400 : 03010300 - ffff0201
mac pro 7300GT : ffff3600 - 00ff3e01
mac pro 8800GT : 03010000 - ffff0001
imac 24" 7600GT : 03035000 - ffff3601
Apple TV 7300Go : 01ff0000
powermac 6800GT : 00ff3e01 - 00ff3600
What we notice is that it always ends by 00 for Display-A and 01 for Display-B.
We know it affects outputs support.
We then suggest you to try different values in the plist, taken from real macs. That's all what we can do for the moment.
there's one string for each screen (@0,Display-cfg & @1,Display-cfg)
macbook pro 8600GT : 03010000 - ffff0001
macbook pro unibody 9400 : 03010300 - ffff0801
macbook pro white 9400 : 03010300 - ffff0201
mac pro 7300GT : ffff3600 - 00ff3e01
mac pro 8800GT : 03010000 - ffff0001
imac 24" 7600GT : 03035000 - ffff3601
Apple TV 7300Go : 01ff0000
powermac 6800GT : 00ff3e01 - 00ff3600
What we notice is that it always ends by 00 for Display-A and 01 for Display-B.
We know it affects outputs support.
So, if I were to try NVEnabler again, would I remove the cfg values entirely, or replace them with one of these strings?
I think I've tried just about everything possible, and I still keep getting the black screen of death, with movable mouse icon feature. The system log shows a bunch of FIFO "unknown method error" and "parse error" entries every second. windowserver.log shows this:
Is it possible that some display setting is being cached somewhere? I feel like I'm getting the same results no matter what I try.
CODE
Nov 24 20:51:45 [120] Server is starting up
Nov 24 20:52:45 [120] (iokit/common) I/O Timeout: IOKitWaitQuiet
Nov 24 20:52:45 [120] (iokit/common) I/O Timeout: Set a breakpoint at CGErrorBreakpoint() to catch errors as they are returned
Nov 24 20:52:47 [120] CGXMappedDisplayStart: Unit 0: no display alias property
Nov 24 20:52:47 [120] CGXMappedDisplayStart: Unit 1: no display alias property
Nov 24 20:56:47 [120] AGCAttach: Couldn't find any matches
Nov 24 20:56:47 [120] CGXPerformInitialDisplayConfiguration
Nov 24 20:56:47 [120] Display 0x1a493641: MappedDisplay Unit 1; Vendor 0x469 Model 0x24f3 S/N 68226; online enabled (0,0)[1920 x 1080], base addr 0x4800000
Nov 24 20:56:47 [120] Display 0x3f003c: MappedDisplay Unit 0; Vendor 0xffffffff Model 0xffffffff S/N -1; offline enabled (2944,0)[1 x 1], base addr 0x4800000
Nov 24 20:56:50 [120] GLCompositor: GL renderer id 0x0002240c, GL mask 0x00000003, accelerator 0x0000280f, unit 0, caps 0x00000003, vram 256 MB
Nov 24 20:56:50 [120] GLCompositor: GL renderer id 0x0002240c, GL mask 0x00000003, texture units 4, texture max 4096, viewport max {4096, 4096} extensions 0x0000000f
Nov 24 20:56:52 [120] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller Parallels Starter
Nov 24 20:57:14 [120] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller Shades
Nov 24 20:57:17 [120] kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application "Finder" for over 1 second. Server has re-enabled them.
Nov 24 20:52:45 [120] (iokit/common) I/O Timeout: IOKitWaitQuiet
Nov 24 20:52:45 [120] (iokit/common) I/O Timeout: Set a breakpoint at CGErrorBreakpoint() to catch errors as they are returned
Nov 24 20:52:47 [120] CGXMappedDisplayStart: Unit 0: no display alias property
Nov 24 20:52:47 [120] CGXMappedDisplayStart: Unit 1: no display alias property
Nov 24 20:56:47 [120] AGCAttach: Couldn't find any matches
Nov 24 20:56:47 [120] CGXPerformInitialDisplayConfiguration
Nov 24 20:56:47 [120] Display 0x1a493641: MappedDisplay Unit 1; Vendor 0x469 Model 0x24f3 S/N 68226; online enabled (0,0)[1920 x 1080], base addr 0x4800000
Nov 24 20:56:47 [120] Display 0x3f003c: MappedDisplay Unit 0; Vendor 0xffffffff Model 0xffffffff S/N -1; offline enabled (2944,0)[1 x 1], base addr 0x4800000
Nov 24 20:56:50 [120] GLCompositor: GL renderer id 0x0002240c, GL mask 0x00000003, accelerator 0x0000280f, unit 0, caps 0x00000003, vram 256 MB
Nov 24 20:56:50 [120] GLCompositor: GL renderer id 0x0002240c, GL mask 0x00000003, texture units 4, texture max 4096, viewport max {4096, 4096} extensions 0x0000000f
Nov 24 20:56:52 [120] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller Parallels Starter
Nov 24 20:57:14 [120] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller Shades
Nov 24 20:57:17 [120] kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application "Finder" for over 1 second. Server has re-enabled them.
Is it possible that some display setting is being cached somewhere? I feel like I'm getting the same results no matter what I try.
Any ideas, please? I am now considering just wiping out my system and starting over, which would suck, but I don't know what else to try.
What worked for me:
Chameleon boot loader => extra folder => boot.plist =>
<key>Kernel Flags</key>
<string>arch=i386</string>
<key>GraphicsEnabler</key>
<string>y</string>
On an otherwise vanilla install. I needed to boot 32bit because in 64bit I got KPs from the video card (7600GS).
Chameleon boot loader => extra folder => boot.plist =>
<key>Kernel Flags</key>
<string>arch=i386</string>
<key>GraphicsEnabler</key>
<string>y</string>
On an otherwise vanilla install. I needed to boot 32bit because in 64bit I got KPs from the video card (7600GS).
QUOTE (johnyates @ Nov 29 2009, 03:00 PM)
What worked for me:
Chameleon boot loader => extra folder => boot.plist =>
<key>Kernel Flags</key>
<string>arch=i386</string>
<key>GraphicsEnabler</key>
<string>y</string>
On an otherwise vanilla install. I needed to boot 32bit because in 64bit I got KPs from the video card (7600GS).
Chameleon boot loader => extra folder => boot.plist =>
<key>Kernel Flags</key>
<string>arch=i386</string>
<key>GraphicsEnabler</key>
<string>y</string>
On an otherwise vanilla install. I needed to boot 32bit because in 64bit I got KPs from the video card (7600GS).
Thanks johnyates. I'll give that a try, though I wasn't getting panics. At the moment, just so I could boot, I went back to a backup system config that I had before, which included NVKush and default NV* kexts modified to include my card's dev/mfr IDs. This seems to look okay:
Click to view attachment
... but several times a day, the text on screen gets distorted, and ends up at least once a day looking something like this:
Click to view attachment
The frustrating thing is that I know the rest of the system is still working despite the screwed up display. Is there a display reset command that I could use to refresh the screen when something happens, kind of like X's control+alt+backspace?
Not sure what else to try aside from that. How can I tell that the right drivers are configured and loaded? kextstat says:
CODE
[b]kextstat |grep -i nv[/b]
8 1 0x0 0x0 0x0 com.apple.iokit.IONVRAMFamily (9.8.0)
36 0 0x47b60000 0x9000 0x8000 com.nvidia.driver.AppleNForceATA (1.0.3) <35 17 12>
76 3 0x575f3000 0x25f000 0x25e000 com.apple.NVDAResman (5.4.4) <75 74 17 6 5 4 2>
77 0 0x57852000 0x1cb000 0x1ca000 com.apple.nvidia.nv40hal (5.4.4) <76 5 4>
84 0 0x57a1d000 0x254000 0x253000 com.apple.nvidia.nv50hal (5.4.4) <76 5 4>
89 0 0x41bc1000 0x3000 0x2000 com.DiaboliK.NVKush (4.20.2) <17 12>
8 1 0x0 0x0 0x0 com.apple.iokit.IONVRAMFamily (9.8.0)
36 0 0x47b60000 0x9000 0x8000 com.nvidia.driver.AppleNForceATA (1.0.3) <35 17 12>
76 3 0x575f3000 0x25f000 0x25e000 com.apple.NVDAResman (5.4.4) <75 74 17 6 5 4 2>
77 0 0x57852000 0x1cb000 0x1ca000 com.apple.nvidia.nv40hal (5.4.4) <76 5 4>
84 0 0x57a1d000 0x254000 0x253000 com.apple.nvidia.nv50hal (5.4.4) <76 5 4>
89 0 0x41bc1000 0x3000 0x2000 com.DiaboliK.NVKush (4.20.2) <17 12>
I guess it's time to give it up. Thanks anyway.
You have
simultaneously.
It is wrong.
QUOTE
CODE
77 0 0x57852000 0x1cb000 0x1ca000 com.apple.nvidia.nv40hal (5.4.4) <76 5 4>
84 0 0x57a1d000 0x254000 0x253000 com.apple.nvidia.nv50hal (5.4.4) <76 5 4>
84 0 0x57a1d000 0x254000 0x253000 com.apple.nvidia.nv50hal (5.4.4) <76 5 4>
simultaneously.
It is wrong.
QUOTE (Slice @ Dec 8 2009, 08:53 AM)
You have
simultaneously.
It is wrong.
Thanks Slice. How do I fix that? Not by deleting one of them, I assume?simultaneously.
It is wrong.
OK, is this better (after moving 'nv50'):
CODE
kextstat |grep -i nv
8 1 0x0 0x0 0x0 com.apple.iokit.IONVRAMFamily (9.8.0)
37 0 0x47b72000 0x9000 0x8000 com.nvidia.driver.AppleNForceATA (1.0.3) <36 17 12>
73 2 0x5814f000 0x25f000 0x25e000 com.apple.NVDAResman (5.4.4) <72 71 17 6 5 4 2>
74 0 0x583ae000 0x1cb000 0x1ca000 com.apple.nvidia.nv40hal (5.4.4) <73 5 4>
87 0 0x41b07000 0x3000 0x2000 com.DiaboliK.NVKush (4.20.2) <17 12>
8 1 0x0 0x0 0x0 com.apple.iokit.IONVRAMFamily (9.8.0)
37 0 0x47b72000 0x9000 0x8000 com.nvidia.driver.AppleNForceATA (1.0.3) <36 17 12>
73 2 0x5814f000 0x25f000 0x25e000 com.apple.NVDAResman (5.4.4) <72 71 17 6 5 4 2>
74 0 0x583ae000 0x1cb000 0x1ca000 com.apple.nvidia.nv40hal (5.4.4) <73 5 4>
87 0 0x41b07000 0x3000 0x2000 com.DiaboliK.NVKush (4.20.2) <17 12>
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.