ProjectOSX

Welcome Guest!

Returning User? Login here.

Want membership privileges? Register here.

40 Pages V  « < 31 32 33 34 35 > »   
Start a new topic Add Reply
> Nvenabler Testing And Discussion, new universal kext for nVidia
Krazubu
post Nov 15 2011, 08:59 PM
Post #641
I'd start by removing any mention to the intel IGP, or better, use stuff that explicitely disables it, if such things exist (need to check that in the ACPI v4 doc).
For the nVidia card, try to add the basic stuff required for GFX (kind of copy the intel part by adapting it).
From my experience, OSX doesn't rely much on DSDT, most of the data it contains is dropped once the GUI is reached, so don't bother pushing details.
However the basic parts are still considered (ie. the device path).
We could also attack from BIOS side by killing the intel ROM and some optimus code but we can't play like that if you don't have a reliable way to recover trashed BIOS.
Mido
post Nov 16 2011, 06:16 PM
Post #642
QUOTE (Krazubu @ Nov 15 2011, 10:59 PM) *
I'd start by removing any mention to the intel IGP, or better, use stuff that explicitely disables it, if such things exist (need to check that in the ACPI v4 doc).
For the nVidia card, try to add the basic stuff required for GFX (kind of copy the intel part by adapting it).
From my experience, OSX doesn't rely much on DSDT, most of the data it contains is dropped once the GUI is reached, so don't bother pushing details.
However the basic parts are still considered (ie. the device path).
We could also attack from BIOS side by killing the intel ROM and some optimus code but we can't play like that if you don't have a reliable way to recover trashed BIOS.


you want to disable IGPU
but from my reading igpu is needed for rendering !!
also lvds & vga output is connected to IGPU
so i think disabling IGPU isn't good idea

i am thinking on that data on gfx0 isn't complete so card couldn't work

here is gfx0 of macbookpro 8.2 (secondary gfx card )

CODE
                Device (GFX0)
                {
                    Name (_ADR, 0x00)
                    Name (BRTN, Package (0x12)
                    {
                        0x50,
                        0x32,
                        0x00,
                        0x07,
                        0x0D,
                        0x14,
                        0x1B,
                        0x21,
                        0x28,
                        0x2F,
                        0x35,
                        0x3C,
                        0x43,
                        0x49,
                        0x50,
                        0x57,
                        0x5D,
                        0x64
                    })
                    Device (LCD)
                    {
                        Name (_ADR, 0x0110)
                        Method (_BCL, 0, NotSerialized)
                        {
                            Return (BRTN)
                        }
                        Method (_BCM, 1, NotSerialized)
                        {
                            Store (Arg0, BRTL)
                            Divide (Add (Multiply (Arg0, 0x03), 0x02), 0x14, Local1,
                                Local0)
                            ShiftLeft (Local0, 0x04, Local0)
                            Or (Local0, 0x04, Local0)
                            Acquire (MUTX, 0xFFFF)
                            Store (Local0, SSMY)
                            Store (0xBF, SSMP)
                            Release (MUTX)
                        }
                        Method (_BQC, 0, NotSerialized)
                        {
                            Return (BRTL)
                        }
                    }
                    Device (LCD1)
                    {
                        Name (_ADR, 0xA420)
                        Method (_BCL, 0, NotSerialized)
                        {
                            Return (BRTN)
                        }
                    }
                    Method (_DOD, 0, NotSerialized)
                    {
                        Return (Package (0x02)
                        {
                            0x0110,
                            0x8000A420
                        })
                    }
                    Name (ATIB, Buffer (0x0100) {})
                    Method (ATIF, 2, Serialized)
                    {
                        If (LEqual (Arg0, 0x00))
                        {
                            Return (AF00 ())
                        }
                        If (LEqual (Arg0, 0x01))
                        {
                            Return (AF01 ())
                        }
                        If (LEqual (Arg0, 0x02))
                        {
                            Return (AF02 ())
                        }
                        Else
                        {
                            CreateWordField (ATIB, 0x00, SSZE)
                            CreateWordField (ATIB, 0x02, VERN)
                            CreateDWordField (ATIB, 0x04, NMSK)
                            CreateDWordField (ATIB, 0x08, SFUN)
                            Store (0x00, SSZE)
                            Store (0x00, VERN)
                            Store (0x00, NMSK)
                            Store (0x00, SFUN)
                            Return (ATIB)
                        }
                    }
                    Method (AF00, 0, NotSerialized)
                    {
                        CreateWordField (ATIB, 0x00, SSZE)
                        CreateWordField (ATIB, 0x02, VERN)
                        CreateDWordField (ATIB, 0x04, NMSK)
                        CreateDWordField (ATIB, 0x08, SFUN)
                        Store (0x0C, SSZE)
                        Store (0x01, VERN)
                        Store (0x0C, NMSK)
                        Store (0x03, SFUN)
                        Return (ATIB)
                    }
                    Method (AF01, 0, NotSerialized)
                    {
                        CreateWordField (ATIB, 0x00, SSZE)
                        CreateDWordField (ATIB, 0x02, VMSK)
                        CreateDWordField (ATIB, 0x06, FLGS)
                        Store (0x0A, SSZE)
                        Store (0x03, VMSK)
                        Store (0x01, FLGS)
                        Return (ATIB)
                    }
                    Method (AF02, 0, NotSerialized)
                    {
                        CreateWordField (ATIB, 0x00, SSZE)
                        CreateDWordField (ATIB, 0x02, PSBI)
                        CreateByteField (ATIB, 0x06, EXPM)
                        CreateByteField (ATIB, 0x07, THRM)
                        CreateByteField (ATIB, 0x08, THID)
                        CreateByteField (ATIB, 0x09, FPWR)
                        CreateByteField (ATIB, 0x0A, FPID)
                        CreateByteField (ATIB, 0x0B, SPWR)
                        CreateByteField (ATIB, 0x0C, PBBL)
                        Store (0x0D, SSZE)
                        Store (0x08, PSBI)
                        Store (0x00, FPWR)
                        Store (GPLT, FPID)
                        Return (ATIB)
                    }
                    Name (_PRW, Package (0x02)
                    {
                        0x09,
                        0x04
                    })
                    OperationRegion (PEGH, PCI_Config, 0x00, 0x40)
                    Field (PEGH, ByteAcc, NoLock, Preserve)
                    {
                        VID0,   16,
                        DID0,   16
                    }
                    OperationRegion (GBAR, SystemMemory, 0xE0008000, 0x0100)
                    Field (GBAR, DWordAcc, Lock, Preserve)
                    {
                                Offset (0xB0),
                            ,   4,
                        LNKD,   1,
                                Offset (0xB2),
                            ,   4,
                        LSTS,   6,
                            ,   1,
                        LTRN,   1
                    }
                    Method (PWRD, 1, NotSerialized)
                    {
                        If (Arg0)
                        {
                            Store (0x01, LNKD)
                            Sleep (0x64)
                            Return (0x00)
                        }
                        Else
                        {
                            Store (0x00, LNKD)
                            While (LTRN)
                            {
                                Sleep (0x0A)
                            }
                            If (LEqual (LSTS, 0x08))
                            {
                                Return (0x00)
                            }
                            Else
                            {
                                Return (0x01)
                            }
                        }
                    }
                    Method (_DSM, 4, NotSerialized)
                    {
                        If (LEqual (Arg0, Buffer (0x10)
                                {
                                    /* 0000 */    0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44,
                                    /* 0008 */    0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B
                                }))
                        {
                            If (LNotEqual (And (VID0, 0xFFFF), 0xFFFF))
                            {
                                Store (Package (0x02)
                                    {
                                        "hda-gfx",
                                        Buffer (0x0A)
                                        {
                                            "onboard-2"
                                        }
                                    }, Local0)
                                DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                                Return (Local0)
                            }
                        }
                        Return (0x80000002)
                    }
                }


i am thinking on modifying this device for my card !!

PC : AMD Phenom ii x4 955 / ASUS M5A97 / Sapphire HD 6850 / 2x2 1333 KingSton Ram / 2*500GB + 640GB HDD / Thermaltake 500 W
NB : DELL INSPIRON N5110 : CORE I5 2410M / 4GB 1333 Nanya Ram / Intel HD Graphics 3000 + Nvidia GeForce 525M / 640 HDD / DELL Wireless 1702
mjw
post Nov 22 2011, 06:40 AM
Post #643
Hi Krazubu:

I little while back you helped me modify NVEnabler64 to work with my Zotac GTX460 graphics card (and thanks very, very much!). It had something to do with non-standard monitor outputs, that was forcing the card to boot to a black screen under SL using the cards DVI ports. Here is a link to the old thread

http://www.insanelymac.com/forum/lofiversi...hp/t254930.html

I recently tried to do a clean install of Lion on the same machine and using the same modified NVenabler64, but am now having the same black screen boot issue.

Here is a link to the modified info.plist file in my dropbox account:

http://dl.dropbox.com/u/28874618/NVEnabler...ents/Info.plist

Is there anything going on with Lion that would cause this modified kext not work as it did with SL? If so, is there any way you can help?

Thanks so much!

Michael
Krazubu
post Dec 6 2011, 01:09 PM
Post #644
Hi, sorry for the late reply. I don't see any reason for your problem beside the usual things.
Ensure dev IDs are ok, ensure that chameleon doesn't conflict with NVE (GraphicsEnabler and video ROM load), etc...
flAked
post Dec 12 2011, 09:33 PM
Post #645
Hey Guys,

I'm having some troubles with my Asus ENGTS250 DK keeping me from fully migrating to Lion.

The GTS250 is of course just a rebranded GTX9800+ and should work out of the box with GraphicsEnabler and full acceleration.

In fact I do get the card into QE/CI mode but get horrible flickering (most noticeable on grey/dark-grey patterns), that is almost unbearable after a few minutes.
The output configuration is DVI/VGA/HDMI and the DVI-port works fine in Windows and Linux.

On SnowLeopard the only way (to my knowledge and testing) to circumvent the flickering was to connect it via a HDMI-DVI-cable - that is, using the HDMI-output of the card and the DVI-input of my LCD.

However, using the same EFI injection as I'm using right now in 10.6.8 doesn't work in Lion anymore. For my various projects (SpeedStepper, ..) I did multiple Lion installations beginning with the first RC up until 10.7.3 (11D24) in the hope that a new nvidia driver will fix this issue. Sadly not so far.

So I now did a fresh install and updated to 11D24, trying NVEnabler with vbios injection in the hope that you have an idea on what might be the cause for this.

Attached File  GTS250.ROM.zip ( 40.8K ) Number of downloads: 5
(extracted in DOS)

Attached File  ioreg_efi_sl.txt.zip ( 85.2K ) Number of downloads: 1
IOReg of my working 10.6.8

Attached File  NVEnabler_ioreg_2.txt.zip ( 146.44K ) Number of downloads: 4
IOReg of NVEnabler64 loaded up in 10.7.3 (no settings)

Attached File  NVEnabler_ioreg_with_vbios_inject.txt.zip ( 146.38K ) Number of downloads: 7
IOReg of NVEnabler64 in 10.7.3 with vbios

If you need more information please let me know.

Thanks!
Gringo Vermelho
post Dec 12 2011, 10:51 PM
Post #646
Flickering on websites with gray gradient background is a long standing issue with nvidia cards, you can find vintage posts on InsanelyMac describing it. My 7600 GT AGP and my 9800 GTX+ did it, and now my GTX 460 does it. 10.5.2 to 10.6.8.
It's interesting that it doesn't happen when using HDMI.

This post has been edited by Gringo Vermelho: Dec 12 2011, 10:53 PM
ASUS P8Z77-V Pro - EVGA GTX 660 - i5-3570K - 10.9.1 retail - Chameleon 2.2 svn r22xx
flAked
post Dec 13 2011, 01:35 AM
Post #647
Hmm I'm not sure if it's the same effect, I never noticed it before on gradients, is it a pure OSX issue? Do you mean when scrolling a website?

In my case the whole screen flickers constantly, I can see it on uniform backgrounds as well. I notice the eye-strain right away and a head-ache comes 5 minutes later. It looks like an old CRT driven by the wrong frequency.

I'm not sure if I could capture it with my DSLR, maybe in burst-mode and make a gif out of it...

Anyways, it's strange that this work-around via HDMI did work in SL and not in Lion, I presume it's a driver change?
Krazubu
post Dec 19 2011, 07:58 AM
Post #648
flAked
Your display-cfg values are not injected for each output.

Try those :
for Display-A :
ffff0000

for Display-B :
00ff0101 if you wish to use VGA
00ff0301 if you wish to use DVI/HDMI
mantu
post Dec 19 2011, 11:35 AM
Post #649
just a simple question...
how can i know if my geforce fx 5200 pci is supported by nvenabler?
it's a week i'm trying to get it work on a lion retail install...
but now my suspect is that maybe it isn't supoprted...

many thank's in advice
kossak
post Dec 19 2011, 05:11 PM
Post #650
Hello there.

First of all, great work on NVEnabler.

I need some help setting up Graphics of my Laptop.

I'm using NVEnabler on a HP Elitebook 8540p with a NVidia NVS 5100M. I'm running Lion with most of the stuff working. Graphics are accelerated and the resolution is correct (only NVEnabler active, no other injector/loader).

However I can't get my secondary display to turn on. First things first, my laptop has the following video outputs:

- DisplayPort
- Analog VGA
- DVI (on docking station)
- Displayport (on docking station)
- Analog VGA (on docking station)

I have a samsung syncmaster 226BW connected via DVI (docking station) and it's not being recognized)

Can you help? Attached is the ioreg output and NVEnabler logs.

never mind the "DEBUG Setting property @1,display-cfg", I tried to set display-cfg but I still haven't found a good plist editor so I'm editing the Plist manually and the hex string is being incorrectly inserted. However I dont believe thats the correct value, regardless.

EDIT: I just used Plist Edit Pro to set @0,display-cfg to ffff0000 and @1,display-cfg to 00ff0301. The values are injected ok, but the display still fails to start.

Could these be the display-cfg values for my ports? EDIT: just found out they are not. I read this post but I still can't figure out what values go to display-cfg, or even if I can get it working with editing just those (maybe an NVEnabler patch?)

CODE
12/19/11 4:55:34.000 PM kernel: NVEnabler: Raw DCB entry 0: 01000313
12/19/11 4:55:34.000 PM kernel: NVEnabler: Raw DCB entry 1: 08015392
12/19/11 4:55:34.000 PM kernel: NVEnabler: Raw DCB entry 2: 08014382
12/19/11 4:55:34.000 PM kernel: NVEnabler: Raw DCB entry 3: 02027362
12/19/11 4:55:34.000 PM kernel: NVEnabler: Raw DCB entry 4: 02026362
12/19/11 4:55:34.000 PM kernel: NVEnabler: Raw DCB entry 5: 02049300


Please help and thanks in advance.

EDIT: I'm running 64 bit kernel with NVEnabler64.

Argh, for some reason my attachments aren't showing, can anyone help?

This post has been edited by kossak: Dec 21 2011, 04:24 PM
mantu
post Dec 19 2011, 11:45 PM
Post #651
QUOTE (mantu @ Dec 19 2011, 12:35 PM) *
just a simple question...
how can i know if my geforce fx 5200 pci is supported by nvenabler?
it's a week i'm trying to get it work on a lion retail install...
but now my suspect is that maybe it isn't supoprted...

many thank's in advice



attached is my ioreg:
Attached File  NVEnabler_ioreg_dump_mantu.txt ( 709.57K ) Number of downloads: 3


and here is an extract of kernel.log

CODE
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: init : begin
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: probe : probe
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: probe : ROM shadow enable
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: probe : patch PRAMIN
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: dcb table at offset 0xae74
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: dcb numentries 0
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: numentries = 0 num_outputs = 0
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: Channel 1: 00
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: Channel 2: 00
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG Model found: GeForce FX 5200
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG VRAM: 256
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG Setting property @0,name
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG Setting property @1,name
Dec 20 00:29:20 host518 kernel[0]: NVEnabler: DEBUG Setting property device_type
Dec 20 00:29:20 host518 kernel[0]: NVEnabler::probe fails
Dec 20 00:29:20 host518 kernel[0]: NVDA,Display-B: Not usable


someone can please help me?

the graphic card seems to be correctly recognized but i can only use 1024x768 resolution...
many thank's in advice

This post has been edited by mantu: Dec 19 2011, 11:46 PM
kossak
post Dec 21 2011, 04:34 PM
Post #652
I'm sorry about this but my attachments are missing from the post above so please bear with me.

I'll attach here my ioreg dump and also my video BIOS which I extracted from DOS using nvflash.exe

I already tried about 10 or 20 different display-cfg combinations. I think the problem is that a certain instruction is needed to force detection on the output ports. In windows I press FN+F4 to do that. "detect displays" on OSX does absolutely nothing.

See 2 posts above for my original problem.

Maybe someone could patch my ROM or something? I attached it in base64 since I cant seem to upload binary files.

I've been trying to use chimera and its GraphicsEnabler also, injecting display-cfg strings via boot.plist.

Please help, I'll donate.

Attached File  NVEnabler_ioreg_dump_kossak.txt ( 1.27MB ) Number of downloads: 5

Attached File  NVEnabler.log.txt ( 1.95K ) Number of downloads: 2
Gringo Vermelho
post Dec 22 2011, 02:26 AM
Post #653
QUOTE (mantu @ Dec 19 2011, 09:35 AM) *
how can i know if my geforce fx 5200 pci is supported by nvenabler?

NVEnabler is not the problem here, the problem is that your video card is too old, it is not supported by the OS X Nvidia drivers.
ASUS P8Z77-V Pro - EVGA GTX 660 - i5-3570K - 10.9.1 retail - Chameleon 2.2 svn r22xx
Clubber_77
post Dec 22 2011, 10:49 AM
Post #654
how to disable debug mode in 64bit version?
Krazubu
post Dec 22 2011, 12:06 PM
Post #655
Clubber_77
No way

kossak
I'll look into your ROM
I need some more details on your output table. Your list seems to be quick n dirty.
You tell me you have 2 VGA, I only see one in the ROM, you tell you have 1 DVI, I see 4 DVI/HDMI capable outputs.
Please list exactly all the supported outputs, including those using some passive adapter (like DP to DVI).
I'll have to kill all the docking station outputs to make the built-in ones work.

EDIT : here's a trial, don't know what it's worth Attached File  nvs5100patched.rom.zip ( 45.29K ) Number of downloads: 15

Use this NVCAP : 04000000 00000300 7c000000 0000000a 00000000
This display-cfg : for display A : ffff0100
for display B it will depend on the output you try, there are 3 DVI capable ones in the current BIOS, you'll have to try each : 00ff0901 or 00ff0601 or 00ff0001
kossak
post Dec 23 2011, 12:26 AM
Post #656
QUOTE (Krazubu @ Dec 22 2011, 12:06 PM) *
kossak
I'll look into your ROM
I need some more details on your output table. Your list seems to be quick n dirty.
You tell me you have 2 VGA, I only see one in the ROM, you tell you have 1 DVI, I see 4 DVI/HDMI capable outputs.
Please list exactly all the supported outputs, including those using some passive adapter (like DP to DVI).
I'll have to kill all the docking station outputs to make the built-in ones work.

EDIT : here's a trial, don't know what it's worth Attached File  nvs5100patched.rom.zip ( 45.29K ) Number of downloads: 15

Use this NVCAP : 04000000 00000300 7c000000 0000000a 00000000
This display-cfg : for display A : ffff0100
for display B it will depend on the output you try, there are 3 DVI capable ones in the current BIOS, you'll have to try each : 00ff0901 or 00ff0601 or 00ff0001


Thanks! I'm at home now, so I can't test DVI (I don't have a displayport adapter, so I'm using a standard vga analog).

I tested your rom with a simple analog VGA monitor and still no dice. used your NVCAP and ffff0100 for display-a and 00ff0001 for display b. No image on external monitor (primary is fine), and "detect displays" seems to be doing nothing.

I'll let you know tomorrow what happens with a DVI monitor connected to the docking station.

Just to be clear:

This laptop has:
- A primary monitor (doh smile.gif)
- A standard analog VGA port
- A DisplayPort

Then the docking station has:
- A standard DVI port
- A standard analog VGA port (might be converted from DVI, but I can't tell)
- A non standard DisplayPort connector (I believe its the standard for non mobile equipment).

Here are the specs for the docking station. you can see the full specs of it here:

http://h30094.www3.hp.com/product/sku/1021...2FNZ223AA%23ABA

I'll also attach the following extra information:

- My current DSDT.aml: this might be important because I extracted it from the laptop and had to comment out a specific portion that didn't compile. This portion is related to display detection routines, I believe. I'll also attach the original extracted DSDT so you can see what I did (I deleted all references to an externalint VGDD). What seems to happen is that the key combo to force detection (FN-F4) does nothing after I boot this DSDT. I usually can cycle through screens using that combo even on POST, but after the DSDT load I have to cold boot the PC to do that again.
- my bdmesg and dmesg.

Thanks again. Hope to hear from you soon and have a nice Chrismas btw smile.gif
kossak
post Dec 23 2011, 12:58 AM
Post #657
Update: I GOT SIGNAL! biggrin.gif

patched rom (krazubu)
NVCAP: 04000000000003007c0000000000000a00000000
DISPLAYA: FFFF0100
DISPLAYB: 00FF0601

I can use analog VGA out using this config on Chimera 1.7. It works great! detection doesn't work after boot (it has to be plugged in on boot).

I'll try tomorrow with DVI. This is progress! Thanks!

If DVI works I'll switch to NVEnabler. Chimera is great to test but I think they are missing a lot of injects. My card has the "chirping" sound and is not working at full performance, I think because its in the lowest mode of power saving.

EDIT: DVI works perfectly also with the above parameters. Looks like the Laptop's analog VGA port is passively converted from digital signal.

I'm a happy camper! Now I just need to:

- Patch AppleHDA (VoodooHDA gives me a lot of kernel panics on boot in 64 bit mode)
- Get sleep to work and remove a nagging delay on shutdown and reboot (probably need to clean my DSDT for this)
- Get Nvidia power states going (NVPM maybe, also probably related to sleep not working)
- Get my Broadcom 43224AG wifi card working (I might need to remove whitelist BIOS from my 8540p and modify the subvendor ID, not sure yet.)

Thanks krazubu for your help!

This post has been edited by kossak: Dec 23 2011, 02:34 PM
mantu
post Dec 29 2011, 08:20 AM
Post #658
QUOTE (Gringo Vermelho @ Dec 22 2011, 03:26 AM) *
NVEnabler is not the problem here, the problem is that your video card is too old, it is not supported by the OS X Nvidia drivers.


so.... no way to use old kexts?
raultaboraz
post Dec 29 2011, 07:14 PM
Post #659
Attached File  9600GSO.rom.zip ( 40.07K ) Number of downloads: 0
Hi all,

I have 10.6.0 *working* perfect installation with 2 x DVI output with 9600 GSO card 512 Mb (QE / CI, perfect, all res, double DVI outputs).
When I update to 10.6.8 or even 10.7.0, it works BUT only with 1 DVI out. When I turn on second screen all is going to a a black screen...

Then:
  1. Using 2 DVI Outputs (cinema Projector + Samsung LCD) = blackscreen
  2. Using 1 DVI Output only (Samsung LCD only) = works! (QE / CI, perfect, all res, double DVI outputs)

I have read that this card works *native* ok when I can't get it working.

And also I extracted ROM (uploaded to Megaupload here) using a USB-portable Windows XP and nvflash --new and I get a lot of info about my 9600 GSO. With this NVCAP code I generated a hex string using OSXtools, but I am getting blackscreen again...

And also I have used NVenabler kext, it is detected well, but it does not work sad.gif

Do you know what would be cause for this weird problem?? I really need to update my system (because some software requeriments) but I am not sure if I need to boy another GFX card

Thank you very much!

This post has been edited by raultaboraz: Dec 29 2011, 07:16 PM
Gringo Vermelho
post Dec 30 2011, 01:21 AM
Post #660
QUOTE (mantu @ Dec 29 2011, 06:20 AM) *
so.... no way to use old kexts?

No. Nvidia drivers and OpenGL framework from 10.5.5 will definitely not work on Lion.

This post has been edited by Gringo Vermelho: Dec 30 2011, 01:23 AM
ASUS P8Z77-V Pro - EVGA GTX 660 - i5-3570K - 10.9.1 retail - Chameleon 2.2 svn r22xx

40 Pages V  « < 31 32 33 34 35 > » 
Add Reply Start a new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members: