You can add this to the list of cards that will work with no modification: 0612 - 9800 GTX+

Yes..but NV50Hal.kext would load for that card, not NV100Hal.kext.

I'm not sure how that actually works..maybe there's more to the identification than just the device ID.

Look at the device ID range in NV50Hal.kext, you should find the 9300 GE in the allowed range there.

I think I got it:

As far as I understand in those docs:

F means = keep the same, and

0 means = any value.

If I trust the first post and the mask are tolerency based it would be:

F = no tolerancy, the number has to be the same.

0 = full tolerancy, the number can be any.

E = the value can be +/- 1

D = the value can be +/- 2

C = the value can be +/- 3, etc...

So in this case:

"0x062010de&0xffe0ffff"

That would mean:

0620,

0620 -> 062F , (0 deviation in the first half of the second byte, and any number at the second half of the second byte)

0610 -> 061F , (-1 deviation in the first half of the second byte, and any number at the second half of the second byte)

0630 -> 063F (+1 deviation in the first half of the second byte, and any number at the second half of the second byte) and

That would make the 9600GT to load with gf50 since they are

0622.01 = "NVIDIA GeForce 9600 GT"

062D.01 = "NVIDIA GeForce 9600 GT "

062E.01 = "NVIDIA GeForce 9600 GT "

0637.01 = "NVIDIA GeForce 9600 GT "

**I going to try to apply my "theory" with the first line in the gf100 kext**0x06c010de&0xffe0ffff

Valid ranges:

06b0 -> 06bf

06c0 -> 06cf

06d0 -> 06df

**Now the second line 0x0dc010de&0xffc0ffff**Means it would load for all these ranges:

0DF0 -> 0DFF

0DE0 -> 0DEF

0DD0 -> 0DDF

0DC0 -> 0DCF ---

0DB0 -> 0DBF

0DA0 -> 0DAF

0D90 -> 0D9F

For the third line: 0x0e2010de&0xffe0ffff0E30 -> 0E3F

0E20 -> 0E2F ---

0E10 -> 0E1F

**The fourth line has no use since those are the only devices starting by 0E. Maybe future cards use additional id's in that range**

Also the fifth line has no coincidences with current Nvidia id's (probably is reserved for future cards).**The sixth line 0x104010de&0xffc0ffff ranges are: **1070 -> 107F

1060 -> 106F

1050 -> 105F

1040 -> 104F

1030 -> 103F

1020 -> 102F

1010 -> 101F

**Finally 0x124010de&0xffc0ffff ranges are:**1270 -> 127F

1260 -> 126F

1250 -> 125F

1240 -> 124F

1230 -> 123F

1220 -> 122F

1210 -> 121F

So let's do a quick recap of the cards which doesn't need plist modification in order to use the GF100 kext:

0x06c010de&0xffe0ffff
06C0 = "NVIDIA GeForce GTX 480"
06C4 = "NVIDIA GeForce GTX 465"
06CD = "NVIDIA GeForce GTX 470"
06D1 = "NVIDIA Tesla C2050 / C2070"
06D2 = "NVIDIA Tesla M2070"
06D2 = "NVIDIA Tesla X2070"
06D8 = "NVIDIA Quadro 6000"
06D9 = "NVIDIA Quadro 5000"
06DC = "NVIDIA Quadro 6000 "
06DD = "NVIDIA Quadro 4000"
06DE = "NVIDIA Tesla T20 Processor"
06DE = "NVIDIA Tesla S2050"
06DE = "NVIDIA Tesla M2050"
06DE = "NVIDIA Tesla X2070 "
06DF = "NVIDIA Tesla M2070-Q"
0x0dc010de&0xffc0ffff
0DC0 = "NVIDIA GeForce GT 440"
0DC4 = "NVIDIA GeForce GTS 450"
0DC5 = "NVIDIA GeForce GTS 450 "
0DC6 = "NVIDIA GeForce GTS 450 "
0DD8 = "NVIDIA Quadro 2000"
0DE0 = "NVIDIA GeForce GT 440 "
0DE1 = "NVIDIA GeForce GT 430"
0DDA = "NVIDIA Quadro 2000M"
0DF0 = "NVIDIA GeForce GT 425M"
0DF4 = "NVIDIA GeForce GT 540M "
0DF5 = "NVIDIA GeForce GT 525M"
0DF7 = "NVIDIA GeForce GT 520M"
0DFA = "NVIDIA Quadro 1000M"
0DE2 = "NVIDIA GeForce GT 420"
0DE5 = "NVIDIA GeForce GT 530"
0DF8 = "NVIDIA Quadro 600"
0x0e2010de&0xffe0ffff
0E22 = "NVIDIA GeForce GTX 460"
0E23 = "NVIDIA GeForce GTX 460 SE"
0E24 = "NVIDIA GeForce GTX 460 "
0x104010de&0xffc0ffff
1040 = "NVIDIA GeForce GT 520"
1050 = "NVIDIA GeForce GT 520M "
1056 = "NVIDIA NVS 4200M"
1057 = "NVIDIA NVS 4200M "
0x124010de&0xffc0ffff
1241 = "NVIDIA GeForce GT 545"
1243 = "NVIDIA GeForce GT 545 "
1244 = "NVIDIA GeForce GTX 550 Ti"
1245 = "NVIDIA GeForce GTS 450 "

Now if someone could confirm I'm right I would be quite happy

. So according to this list a GTX470 would be the best price/power card with direct support in Lion...but I heard powermanagement is not running so the card is always in 2d mode

.

I remember something similar happened on my GT 8600m, but it could be solved by forcing the screen to sleep.