mg100796 Posted January 21, 2010 Share Posted January 21, 2010 Ok, I have 2 GTS 250s. One is a PNY and one is a BFG Tech. I have followed numerous guides on dual graphics card GFX strings, and I believe that I am really close. I can get each of the card to boot up with the correct amount of VRAM and QE enabled it's just when I try to start up with both cards I get kernal panic when it tries to switch to GUI mode.. Any ideas on what I need to do now? Here's my in.plist : <?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>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0) - 2</key> <dict> <key>@0,compatible</key> <string>NVDA,NVMac</string> <key>@0,device_type</key> <string>display</string> <key>@0,name</key> <string>NVDA,Display-A</string> <key>@1,compatible</key> <string>NVDA,NVMac</string> <key>@1,device_type</key> <string>display</string> <key>@1,name</key> <string>NVDA,Display-B</string> <key>NVCAP</key> <data>BAAAAAAAAwAMAAAAAAAABwAAAAA=</data> <key>NVPM</key> <data>AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data> <key>VRAM,totalsize</key> <string>0x40000000</string> <key>device_type</key> <string>NVDA,Parent</string> <key>model</key> <string>nVidia GeForce GTS 250</string> <key>name</key> <string>display</string> <key>rom-revision</key> <string>nVidia GeForce GTS 250 OpenGL Engine [EFI]</string> </dict> <key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)</key> <dict> <key>@0,compatible</key> <string>NVDA,NVMac</string> <key>@0,device_type</key> <string>display</string> <key>@0,name</key> <string>NVDA,Display-A</string> <key>@1,compatible</key> <string>NVDA,NVMac</string> <key>@1,device_type</key> <string>display</string> <key>@1,name</key> <string>NVDA,Display-B</string> <key>NVCAP</key> <data>BAAAAAAAAwAMAAAAAAAABwAAAAA=</data> <key>NVPM</key> <data>AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==</data> <key>VRAM,totalsize</key> <string>0x40000000</string> <key>device_type</key> <string>NVDA,Parent</string> <key>model</key> <string>BFG nVidia GTS 250</string> <key>name</key> <string>display</string> <key>rom-revision</key> <string>BFG nVidia GTS 250 OpenGL Engine [EFI]</string> </dict> </dict> </plist> And here's it's HEX output with my configuration: c40400000100000002000000600200000d00000002010c00d041030a000000000101060000030101 060000007fff04001e00000072006f006d002d007200650076006900730069006f006e0000002e000 0006e5669646961204765466f7263652047545320323530204f70656e474c20456e67696e65205b45 46495d22000000400030002c006400650076006900630065005f00740079007000650000000b00000 0646973706c6179100000004e00560043004100500000001800000004000000000003000c00000000 000007000000000e0000006e0061006d00650000000b000000646973706c617914000000400030002 c006e0061006d0065000000120000004e5644412c446973706c61792d41100000006d006f00640065 006c0000001a0000006e5669646961204765466f72636520475453203235300e0000004e005600500 04d000000200000000100000000000000000000000000000000000000000000000000000014000000 400031002c006e0061006d0065000000120000004e5644412c446973706c61792d422000000040003 1002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616322 0000005600520041004d002c0074006f00740061006c00730069007a0065000000080000000000004 020000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e564441 2c4e564d616322000000400031002c006400650076006900630065005f00740079007000650000000 b000000646973706c61791c0000006400650076006900630065005f00740079007000650000000f00 00004e5644412c506172656e74580200000d00000002010c00d041030a00000000010106000007010 1060000007fff04001e00000072006f006d002d007200650076006900730069006f006e0000002a00 0000424647206e56696469612047545320323530204f70656e474c20456e67696e65205b4546495d2 2000000400030002c006400650076006900630065005f00740079007000650000000b000000646973 706c6179100000004e00560043004100500000001800000004000000000003000c000000000000070 00000000e0000006e0061006d00650000000b000000646973706c617914000000400030002c006e00 61006d0065000000120000004e5644412c446973706c61792d41100000006d006f00640065006c000 00016000000424647206e566964696120475453203235300e0000004e00560050004d000000200000 000100000000000000000000000000000000000000000000000000000014000000400031002c006e0 061006d0065000000120000004e5644412c446973706c61792d4220000000400031002c0063006f00 6d00700061007400690062006c00650000000e0000004e5644412c4e564d616322000000560052004 1004d002c0074006f00740061006c00730069007a0065000000080000000000004020000000400030 002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d6163220 00000400031002c006400650076006900630065005f00740079007000650000000b00000064697370 6c61791c0000006400650076006900630065005f00740079007000650000000f0000004e5644412c5 06172656e74 Thanks Link to comment Share on other sites More sharing options...
mg100796 Posted January 21, 2010 Author Share Posted January 21, 2010 Ok, here are a few pictures of my kernel panic: Can anyone make anything out of it?? Link to comment Share on other sites More sharing options...
lastowl Posted February 1, 2010 Share Posted February 1, 2010 are they sli'd if so it causes more problems try with them both just not being sli'd Link to comment Share on other sites More sharing options...
Jocelyn84 Posted February 1, 2010 Share Posted February 1, 2010 are they sli'd if so it causes more problems try with them both just not being sli'd Actually the bridge means nothing to OSX. Anyway, I struggled with this for about a week and also tried many solutions such as the aquamac dual card thread and others. I then ran into this thread http://www.insanelymac.com/forum/index.php...83349&st=20 After reading everything Kdawg had to say, and following the DSDT edit he has in post #29 everything works like a breeze with my two 260's, bridge and all. Needless to say, you'll want to edit card name and memory amount appropriately, but after you make those DSDT edits it won't matter which peg or which card your using for to display off of. It should probably look like the following.. Note* (40's marked in after VRAM,totalsize assume you have 1GB cards, if they're 512MB change this to 20 on each entry) Device (PCI0) { Device (PEG1) { Name (_ADR, 0x00030000) Device (GFX1) { Name (_ADR, Zero) Name (_SUN, One) Method (_DSM, 4, NotSerialized) { Store (Package (0x16) { "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@1,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@1,device_type", Buffer (0x08) { "display" }, "@1,name", Buffer (0x0F) { "NVDA,Display-B" }, "NVCAP", Buffer (0x18) { /* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00, /* 0008 */ 0x38, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x40 }, "device_type", Buffer (0x0D) { "NVDA,GeForce" }, "model", Buffer (0x17) { "nVidia GeForce GTX 250" }, "rom-revision", Buffer (0x25) { "nVidia GeForce GTX 250 OpenGL Engine" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } Device (PEG2) { Name (_ADR, 0x00070000) Device (GFX2) { Name (_ADR, Zero) Name (_SUN, One) Method (_DSM, 4, NotSerialized) { Store (Package (0x16) { "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,device_type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@1,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@1,device_type", Buffer (0x08) { "display" }, "@1,name", Buffer (0x0F) { "NVDA,Display-B" }, "NVCAP", Buffer (0x18) { /* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, 0x00, /* 0008 */ 0x38, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x07, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x40 }, "device_type", Buffer (0x0D) { "NVDA,GeForce" }, "model", Buffer (0x17) { "nVidia GeForce GTX 250" }, "rom-revision", Buffer (0x25) { "nVidia GeForce GTX 250 OpenGL Engine" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } After editing, use iASLme to kick out your DSDT.aml making sure there are no errors. It'll be in the sessions folder wherever the original DSDT.dsl originally was when you drop it off onto iASLme. Then it should look like the below, only with 250's instead of 260's and with the SLI bridge might I add Link to comment Share on other sites More sharing options...
mg100796 Posted February 2, 2010 Author Share Posted February 2, 2010 Alright, I have a few questions. First off.. How can I add this to my current dsdt.aml file? I already depend on it to work my all the cores in my i7 so..yeah. BTW: Here's my current dsdt.aml file- http://mattsmarket.com/wp-content/uploads/2010/02/dsdt.txt Yeah, it's a long one. My other question is: Will this require any kexts? I ask this because I deleted some aparently "important" kexts which is why I am now out of QE. Also I was jacking with some of them, so the I doubt that the ones I have are factory defualt. Oh well.. Hopefully these are easy questions for you so that I can stop using Windows and getting headaches! Thanks! Link to comment Share on other sites More sharing options...
Jocelyn84 Posted February 2, 2010 Share Posted February 2, 2010 Alright, I have a few questions. First off.. How can I add this to my current dsdt.aml file? I already depend on it to work my all the cores in my i7 so..yeah. BTW: Here's my current dsdt.aml file- http://mattsmarket.com/wp-content/uploads/2010/02/dsdt.txt Yeah, it's a long one. My other question is: Will this require any kexts? I ask this because I deleted some aparently "important" kexts which is why I am now out of QE. Also I was jacking with some of them, so the I doubt that the ones I have are factory defualt. Oh well.. Hopefully these are easy questions for you so that I can stop using Windows and getting headaches! Thanks! Well.... I'd create a separate partition, name it test and do a fresh installation on it. If you have a .aml, you just drop it off on iASLme and it'll kick out a .dst in the same location as the .aml. After you've made the above edits, throw it in iASLme again and it'll put the new .aml in a folder called "sessions". Mind you, I am running on P55/1156 not 1366, but I used no other kexts whatsoever. It took me almost a week to put all this together >.> lol. The DSDT edits above just force your motherboard to take control and give the orders for your GPU's, and then mac os picks up from there. It probably couldn't hurt to read through the thread I linked, but Kdawg's posts were the ones I used, not the OP's. Also, I doubt if it matters, but I have no string like stuff in my com.apple.Boot.plist. I do, however, have GraphicsEnabler=Yes listed under Kernal Flags (Not sure if this matters). Edit: I just looked at your file and in case you weren't sure, the top line of the code linked above is the bottom one listed below (Below is form your file). That's where you'd pick up at Alias (PRSA, PRSC) Alias (PRSA, PRSD) Alias (PRSA, PRSE) Alias (PRSA, PRSF) Alias (PRSA, PRSG) Alias (PRSA, PRSH) Device (PCI0) Edit: My bad, I forgot to change Name (_ADR, 0x00050000) to (_ADR, 0x00070000) for the second card. Its fixed now! Link to comment Share on other sites More sharing options...
mg100796 Posted February 2, 2010 Author Share Posted February 2, 2010 That clears up about everything except for two last problems. 1. Where do I stop? I know that is should be when that bracket ends, but to me it seems as if it goes on for quite a while.. and then 2. When ever I try to "compile" just the code you gave me I get this output: - Simple GUI for ASL Optimizing Compiler - -- iasl Me -- v1.0 © cVad 2009. www.applelife.ru Task: Compile "/Darwin/test.dsl" to "/Darwin/Sessions/2010-02-01-210258/test.aml" Start working... Compiling ... Done. Intel ACPI Component Architecture ASL Optimizing Compiler version 20080926 [Oct 4 2008] Copyright (C) 2000 - 2008 Intel Corporation Supports ACPI Specification Revision 3.0a /Darwin/test.dsl 1: Device Error 4095 - ^ syntax error, unexpected PARSEOP_DEVICE, expecting PARSEOP_DEFINITIONBLOCK ASL Input: /Darwin/test.dsl - 2 lines, 6 bytes, 1 keywords Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations All done. Enjoy ... Not sure whats up with that... But again thanks so much for your help! Link to comment Share on other sites More sharing options...
Jocelyn84 Posted February 2, 2010 Share Posted February 2, 2010 That clears up about everything except for two last problems. 1. Where do I stop? I know that is should be when that bracket ends, but to me it seems as if it goes on for quite a while.. and then 2. When ever I try to "compile" just the code you gave me I get this output: - Simple GUI for ASL Optimizing Compiler - -- iasl Me -- v1.0 © cVad 2009. www.applelife.ru Task: Compile "/Darwin/test.dsl" to "/Darwin/Sessions/2010-02-01-210258/test.aml" Start working... Compiling ... Done. Intel ACPI Component Architecture ASL Optimizing Compiler version 20080926 [Oct 4 2008] Copyright (C) 2000 - 2008 Intel Corporation Supports ACPI Specification Revision 3.0a /Darwin/test.dsl 1: Device Error 4095 - ^ syntax error, unexpected PARSEOP_DEVICE, expecting PARSEOP_DEFINITIONBLOCK ASL Input: /Darwin/test.dsl - 2 lines, 6 bytes, 1 keywords Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations All done. Enjoy ... Not sure whats up with that... But again thanks so much for your help! That one error might not matter... Are you using a good editor like BBEdit?? And np Attach your actual .dsl for me and I'll try to add these edits accordingly. Link to comment Share on other sites More sharing options...
mg100796 Posted February 2, 2010 Author Share Posted February 2, 2010 I uploaded my original DSDT.dsl file. I don't know if you need this information but my cards are GTS 250's (duh..) each with 1GB of memory. That should be all you need to know right? dsdt.dsl.zip Link to comment Share on other sites More sharing options...
mg100796 Posted February 4, 2010 Author Share Posted February 4, 2010 I keep getting an error at the "Local0" part when I compile... Any ideas? Link to comment Share on other sites More sharing options...
Jocelyn84 Posted February 6, 2010 Share Posted February 6, 2010 I keep getting an error at the "Local0" part when I compile... Any ideas? Yeah I'm getting that single error as well. I'd try a seperate install with that dsdt or maybe change your pegs to 1 and 2 instead of 0 and 1? I think only gigabyte uses 0 and 1 anyway... Might want to ask some MSI X58 users about this as I'm not as familiar with those boards... Link to comment Share on other sites More sharing options...
mg100796 Posted February 7, 2010 Author Share Posted February 7, 2010 Yeah I'm getting that single error as well. I'd try a seperate install with that dsdt or maybe change your pegs to 1 and 2 instead of 0 and 1? I think only gigabyte uses 0 and 1 anyway...Might want to ask some MSI X58 users about this as I'm not as familiar with those boards... Yeah thats my main problem... I lost my Snow Leopard disc so a clean install is out of the question, and in my DSDT the pegs were already 1 and 2... Could it have something to do with when the local0 is initialized? Link to comment Share on other sites More sharing options...
lastowl Posted February 8, 2010 Share Posted February 8, 2010 actually the sli bridge matter if your using nvidia cards since on the vga boot up it searches for the second gpu to see if it can synchronise so the bridge has caused memory problems ect the drivers just fully optimise it like what happens with multi core cpu's Link to comment Share on other sites More sharing options...
mg100796 Posted February 9, 2010 Author Share Posted February 9, 2010 actually the sli bridge matter if your using nvidia cards since on the vga boot up it searches for the second gpu to see if it can synchronise so the bridge has caused memory problems ect the drivers just fully optimise it like what happens with multi core cpu's So... Do I need the bridge in? Link to comment Share on other sites More sharing options...
lastowl Posted February 11, 2010 Share Posted February 11, 2010 if it doesnt cause KP then leave it in incase anyone writes stuff to use then in true sli, well osx sli, a while ago netkas looked in dsdt patching it so sli works correctly but if your having problems remove the bridge Link to comment Share on other sites More sharing options...
mg100796 Posted February 11, 2010 Author Share Posted February 11, 2010 Yeah, I don't have it in right now Link to comment Share on other sites More sharing options...
mg100796 Posted February 15, 2010 Author Share Posted February 15, 2010 Any other ideas? Link to comment Share on other sites More sharing options...
InToGraphics Posted February 25, 2010 Share Posted February 25, 2010 Yeah thats my main problem... I lost my Snow Leopard disc so a clean install is out of the question, and in my DSDT the pegs were already 1 and 2... Could it have something to do with when the local0 is initialized? Not exactly a fresh install, but you can make an exact duplicate of your existing installation, and restore it to another partition/drive. At least you can experiment without breaking your current installation. The SuperDuper trial has NO restrictions on backup, clone and restore : http://www.shirt-pocket.com/SuperDuper/Sup...escription.html Link to comment Share on other sites More sharing options...
mg100796 Posted March 3, 2010 Author Share Posted March 3, 2010 Alright, at this point I'm offering $20 via PayPal to the first person to get my second video card working. Tutorial, video, anything! I am pretty smart with computers, but this is getting ridiculous... Link to comment Share on other sites More sharing options...
InToGraphics Posted March 14, 2010 Share Posted March 14, 2010 - Simple GUI for ASL Optimizing Compiler - -- iasl Me -- v1.0 © cVad 2009. www.applelife.ru Task: Compile "/Darwin/test.dsl" to "/Darwin/Sessions/2010-02-01-210258/test.aml" Start working... Compiling ... Done. Intel ACPI Component Architecture ASL Optimizing Compiler version 20080926 [Oct 4 2008] Copyright (C) 2000 - 2008 Intel Corporation Supports ACPI Specification Revision 3.0a /Darwin/test.dsl 1: Device Error 4095 - ^ syntax error, unexpected PARSEOP_DEVICE, expecting PARSEOP_DEFINITIONBLOCK ASL Input: /Darwin/test.dsl - 2 lines, 6 bytes, 1 keywords Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations All done. Enjoy ... I might be wrong. But to me it looks like you're missing your device name. "Device" always comes like "Device (PCI0)", or "Device (PWRB)", or "Device (DMA1)", or "Device (HPET)", etc, etc, you get it. Maybe you accidentally deleted the bit in parenthesis. So effectively you do not have a device specified, and the compiler doesn't recognise it. When the compiler doesn't recognise a device name it would throw an error similar to what you've seen. For example : dsdt.dsl 3283: Device (DMA1) > Error 3283 - ^ syntax error, unexpected > PARSEOP_DMA1, expecting PARSEOP_NAMESEG or PARSEOP_NAMESTRING Go back to your unmodified DSDT, or extract a new one and compare the 2 lines. It's worth a try. Also, your compiler is quite old. You might want to update it to the latest 2010 version. Link to comment Share on other sites More sharing options...
cinemalone Posted March 15, 2010 Share Posted March 15, 2010 I might be wrong. But to me it looks like you're missing your device name. "Device" always comes like "Device (PCI0)", or "Device (PWRB)", or "Device (DMA1)", or "Device (HPET)", etc, etc, you get it. Maybe you accidentally deleted the bit in parenthesis. So effectively you do not have a device specified, and the compiler doesn't recognise it. When the compiler doesn't recognise a device name it would throw an error similar to what you've seen. For example : dsdt.dsl 3283: Device (DMA1) > Error 3283 - ^ syntax error, unexpected > PARSEOP_DMA1, expecting PARSEOP_NAMESEG or PARSEOP_NAMESTRING Go back to your unmodified DSDT, or extract a new one and compare the 2 lines. It's worth a try. Also, your compiler is quite old. You might want to update it to the latest 2010 version. Hey what's the update with this? I am going to be attempting the same thing, two 250 gts 1gb in sli, one PNY the other Gigabyte. The 512mb cards in dual setup appears to be supported... Link to comment Share on other sites More sharing options...
mg100796 Posted March 21, 2010 Author Share Posted March 21, 2010 I might be wrong. But to me it looks like you're missing your device name. "Device" always comes like "Device (PCI0)", or "Device (PWRB)", or "Device (DMA1)", or "Device (HPET)", etc, etc, you get it. Maybe you accidentally deleted the bit in parenthesis. So effectively you do not have a device specified, and the compiler doesn't recognise it. When the compiler doesn't recognise a device name it would throw an error similar to what you've seen. For example : dsdt.dsl 3283: Device (DMA1) > Error 3283 - ^ syntax error, unexpected > PARSEOP_DMA1, expecting PARSEOP_NAMESEG or PARSEOP_NAMESTRING Go back to your unmodified DSDT, or extract a new one and compare the 2 lines. It's worth a try. Also, your compiler is quite old. You might want to update it to the latest 2010 version. I used the new updated complier without anymore luck. Here's the output: -- iASL Me v1.2 2009 by cVad -- - (De)Compiling ASL <-> AML files - - ASL Optimizing Compiler version 20100304 [Mar 9 2010] inside - www.applelife.ru www.torrentmac.ru ProductName: Mac OS X ProductVersion: 10.6.2 BuildVersion: 10C540 Kernel: Darwin Kernel Version 10.2.0: Tue Nov 3 10:35:19 PST 2009 Bootargs: boot-uuid=63EDC902-CEE4-35D5-A11D-6D0881B65414 rd=*uuid platform=ACPI -v -s Model ID: TeknoJunkie Mac Pro 3,1 CPU TYPE: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Core: 2708(2708) MHz x 20.3(20.3) Bus: 133 MHz FSB: 532 MHz RAM: 6148 Mb SwapUsage: total = 64.00M used = 0.00M free = 64.00M HibernateMode: 0 User: Matt on matt-desktop.home Start working: Sun Mar 21 14:54:23 CDT 2010 MAC OS X "Snow Leopard" detected ... Task: Compile "/Darwin/dsdt.dsl" to "/Darwin/Sessions/2010-03-21-145423/dsdt.aml" Start working ... Compiling ... Done. Intel ACPI Component Architecture ASL Optimizing Compiler version 20100304 [Mar 9 2010] Copyright (c) 2000 - 2010 Intel Corporation Supports ACPI Specification Revision 4.0 /Darwin/dsdt.dsl 2709: DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Error 4064 - Object does not exist ^ (DTGP) /Darwin/dsdt.dsl 2794: DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Error 4064 - Object does not exist ^ (DTGP) /Darwin/dsdt.dsl 3365: CreateWordField (CRS, \_SB.PCI0.SBRG.SIOR._Y00._MIN, GP10) Optimize 6058 - NamePath optimized ^ (^_Y00._MIN) /Darwin/dsdt.dsl 3366: CreateWordField (CRS, \_SB.PCI0.SBRG.SIOR._Y00._MAX, GP11) Optimize 6058 - NamePath optimized ^ (^_Y00._MAX) /Darwin/dsdt.dsl 3367: CreateByteField (CRS, \_SB.PCI0.SBRG.SIOR._Y00._LEN, GPL1) Optimize 6058 - NamePath optimized ^ (^_Y00._LEN) /Darwin/dsdt.dsl 3375: CreateWordField (CRS, \_SB.PCI0.SBRG.SIOR._Y01._MIN, GP20) Optimize 6058 - NamePath optimized ^ (^_Y01._MIN) /Darwin/dsdt.dsl 3376: CreateWordField (CRS, \_SB.PCI0.SBRG.SIOR._Y01._MAX, GP21) Optimize 6058 - NamePath optimized ^ (^_Y01._MAX) /Darwin/dsdt.dsl 3377: CreateByteField (CRS, \_SB.PCI0.SBRG.SIOR._Y01._LEN, GPL2) Optimize 6058 - NamePath optimized ^ (^_Y01._LEN) /Darwin/dsdt.dsl 3385: CreateWordField (CRS, \_SB.PCI0.SBRG.SIOR._Y02._MIN, GP30) Optimize 6058 - NamePath optimized ^ (^_Y02._MIN) /Darwin/dsdt.dsl 3386: CreateWordField (CRS, \_SB.PCI0.SBRG.SIOR._Y02._MAX, GP31) Optimize 6058 - NamePath optimized ^ (^_Y02._MAX) /Darwin/dsdt.dsl 3387: CreateByteField (CRS, \_SB.PCI0.SBRG.SIOR._Y02._LEN, GPL3) Optimize 6058 - NamePath optimized ^ (^_Y02._LEN) /Darwin/dsdt.dsl 3654: CreateWordField (CRS1, \_SB.PCI0.SBRG._Y03._INT, IRQM) Optimize 6058 - NamePath optimized ^ (_Y03._INT) /Darwin/dsdt.dsl 3655: CreateByteField (CRS1, \_SB.PCI0.SBRG._Y04._DMA, DMAM) Optimize 6058 - NamePath optimized ^ (_Y04._DMA) /Darwin/dsdt.dsl 3656: CreateWordField (CRS1, \_SB.PCI0.SBRG._Y05._MIN, IO11) Optimize 6058 - NamePath optimized ^ (_Y05._MIN) /Darwin/dsdt.dsl 3657: CreateWordField (CRS1, \_SB.PCI0.SBRG._Y05._MAX, IO12) Optimize 6058 - NamePath optimized ^ (_Y05._MAX) /Darwin/dsdt.dsl 3658: CreateByteField (CRS1, \_SB.PCI0.SBRG._Y05._LEN, LEN1) Optimize 6058 - NamePath optimized ^ (_Y05._LEN) /Darwin/dsdt.dsl 3678: CreateWordField (CRS2, \_SB.PCI0.SBRG._Y06._INT, IRQE) Optimize 6058 - NamePath optimized ^ (_Y06._INT) /Darwin/dsdt.dsl 3679: CreateByteField (CRS2, \_SB.PCI0.SBRG._Y07._DMA, DMAE) Optimize 6058 - NamePath optimized ^ (_Y07._DMA) /Darwin/dsdt.dsl 3680: CreateWordField (CRS2, \_SB.PCI0.SBRG._Y08._MIN, IO21) Optimize 6058 - NamePath optimized ^ (_Y08._MIN) /Darwin/dsdt.dsl 3681: CreateWordField (CRS2, \_SB.PCI0.SBRG._Y08._MAX, IO22) Optimize 6058 - NamePath optimized ^ (_Y08._MAX) /Darwin/dsdt.dsl 3682: CreateByteField (CRS2, \_SB.PCI0.SBRG._Y08._LEN, LEN2) Optimize 6058 - NamePath optimized ^ (_Y08._LEN) /Darwin/dsdt.dsl 3683: CreateWordField (CRS2, \_SB.PCI0.SBRG._Y09._MIN, IO31) Optimize 6058 - NamePath optimized ^ (_Y09._MIN) /Darwin/dsdt.dsl 3684: CreateWordField (CRS2, \_SB.PCI0.SBRG._Y09._MAX, IO32) Optimize 6058 - NamePath optimized ^ (_Y09._MAX) /Darwin/dsdt.dsl 3685: CreateByteField (CRS2, \_SB.PCI0.SBRG._Y09._LEN, LEN3) Optimize 6058 - NamePath optimized ^ (_Y09._LEN) /Darwin/dsdt.dsl 3922: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0A._MIN, GP00) Optimize 6058 - NamePath optimized ^ (^_Y0A._MIN) /Darwin/dsdt.dsl 3923: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0A._MAX, GP01) Optimize 6058 - NamePath optimized ^ (^_Y0A._MAX) /Darwin/dsdt.dsl 3924: CreateByteField (CRS, \_SB.PCI0.SBRG.RMSC._Y0A._LEN, GP0L) Optimize 6058 - NamePath optimized ^ (^_Y0A._LEN) /Darwin/dsdt.dsl 3930: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._MIN, GP10) Optimize 6058 - NamePath optimized ^ (^_Y0B._MIN) /Darwin/dsdt.dsl 3931: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._MAX, GP11) Optimize 6058 - NamePath optimized ^ (^_Y0B._MAX) /Darwin/dsdt.dsl 3932: CreateByteField (CRS, \_SB.PCI0.SBRG.RMSC._Y0B._LEN, GP1L) Optimize 6058 - NamePath optimized ^ (^_Y0B._LEN) /Darwin/dsdt.dsl 3940: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0C._MIN, GP20) Optimize 6058 - NamePath optimized ^ (^_Y0C._MIN) /Darwin/dsdt.dsl 3941: CreateWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0C._MAX, GP21) Optimize 6058 - NamePath optimized ^ (^_Y0C._MAX) /Darwin/dsdt.dsl 3942: CreateByteField (CRS, \_SB.PCI0.SBRG.RMSC._Y0C._LEN, GP2L) Optimize 6058 - NamePath optimized ^ (^_Y0C._LEN) /Darwin/dsdt.dsl 3948: CreateDWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0D._LEN, TML1) Optimize 6058 - NamePath optimized ^ (^_Y0D._LEN) /Darwin/dsdt.dsl 3949: CreateDWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0D._BAS, TMB1) Optimize 6058 - NamePath optimized ^ (^_Y0D._BAS) /Darwin/dsdt.dsl 3950: CreateDWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0E._LEN, TML2) Optimize 6058 - NamePath optimized ^ (^_Y0E._LEN) /Darwin/dsdt.dsl 3951: CreateDWordField (CRS, \_SB.PCI0.SBRG.RMSC._Y0E._BAS, TMB2) Optimize 6058 - NamePath optimized ^ (^_Y0E._BAS) /Darwin/dsdt.dsl 4013: CreateDWordField (CRS, \_SB.PCI0.SBRG.HPET._Y0F._BAS, HPT) Optimize 6058 - NamePath optimized ^ (^_Y0F._BAS) /Darwin/dsdt.dsl 4164: CreateDWordField (CRS, \_SB.PCI0.PCIE._Y10._BAS, BAS1) Optimize 6058 - NamePath optimized ^ (^_Y10._BAS) /Darwin/dsdt.dsl 4165: CreateDWordField (CRS, \_SB.PCI0.PCIE._Y10._LEN, LEN1) Optimize 6058 - NamePath optimized ^ (^_Y10._LEN) /Darwin/dsdt.dsl 4210: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y11._LEN, ML01) Optimize 6058 - NamePath optimized ^ (^_Y11._LEN) /Darwin/dsdt.dsl 4211: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y11._BAS, MB01) Optimize 6058 - NamePath optimized ^ (^_Y11._BAS) /Darwin/dsdt.dsl 4212: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y12._LEN, ML02) Optimize 6058 - NamePath optimized ^ (^_Y12._LEN) /Darwin/dsdt.dsl 4213: CreateDWordField (CRS, \_SB.PCI0.SBRG.OMSC._Y12._BAS, MB02) Optimize 6058 - NamePath optimized ^ (^_Y12._BAS) /Darwin/dsdt.dsl 4218: CreateDWordField (CRS1, \_SB.PCI0.SBRG.OMSC._Y13._LEN, ML03) Optimize 6058 - NamePath optimized ^ (^_Y13._LEN) /Darwin/dsdt.dsl 4219: CreateDWordField (CRS1, \_SB.PCI0.SBRG.OMSC._Y13._BAS, MB03) Optimize 6058 - NamePath optimized ^ (^_Y13._BAS) /Darwin/dsdt.dsl 4220: CreateDWordField (CRS1, \_SB.PCI0.SBRG.OMSC._Y14._LEN, ML04) Optimize 6058 - NamePath optimized ^ (^_Y14._LEN) /Darwin/dsdt.dsl 4221: CreateDWordField (CRS1, \_SB.PCI0.SBRG.OMSC._Y14._BAS, MB04) Optimize 6058 - NamePath optimized ^ (^_Y14._BAS) /Darwin/dsdt.dsl 4269: CreateDWordField (CRS, \_SB.RMEM._Y15._BAS, BAS1) Optimize 6058 - NamePath optimized ^ (^_Y15._BAS) /Darwin/dsdt.dsl 4270: CreateDWordField (CRS, \_SB.RMEM._Y15._LEN, LEN1) Optimize 6058 - NamePath optimized ^ (^_Y15._LEN) /Darwin/dsdt.dsl 4271: CreateDWordField (CRS, \_SB.RMEM._Y16._BAS, BAS2) Optimize 6058 - NamePath optimized ^ (^_Y16._BAS) /Darwin/dsdt.dsl 4272: CreateDWordField (CRS, \_SB.RMEM._Y16._LEN, LEN2) Optimize 6058 - NamePath optimized ^ (^_Y16._LEN) /Darwin/dsdt.dsl 4273: CreateDWordField (CRS, \_SB.RMEM._Y17._LEN, LEN3) Optimize 6058 - NamePath optimized ^ (^_Y17._LEN) /Darwin/dsdt.dsl 4274: CreateDWordField (CRS, \_SB.RMEM._Y18._BAS, BAS4) Optimize 6058 - NamePath optimized ^ (^_Y18._BAS) /Darwin/dsdt.dsl 4275: CreateDWordField (CRS, \_SB.RMEM._Y18._LEN, LEN4) Optimize 6058 - NamePath optimized ^ (^_Y18._LEN) /Darwin/dsdt.dsl 4317: Name (_WDG, Buffer (0x14) Warning 1099 - Unknown reserved name ^ (_WDG) /Darwin/dsdt.dsl 4340: Name (^NATA, Package (0x01) Optimize 6033 - Integer optimized to single-byte AML opcode ^ (One) /Darwin/dsdt.dsl 7871: CreateDWordField (CRS, \_SB.PCI0._Y19._MIN, MIN5) Optimize 6058 - NamePath optimized ^ (_Y19._MIN) /Darwin/dsdt.dsl 7872: CreateDWordField (CRS, \_SB.PCI0._Y19._MAX, MAX5) Optimize 6058 - NamePath optimized ^ (_Y19._MAX) /Darwin/dsdt.dsl 7873: CreateDWordField (CRS, \_SB.PCI0._Y19._LEN, LEN5) Optimize 6058 - NamePath optimized ^ (_Y19._LEN) /Darwin/dsdt.dsl 7874: CreateDWordField (CRS, \_SB.PCI0._Y1A._MIN, MIN6) Optimize 6058 - NamePath optimized ^ (_Y1A._MIN) /Darwin/dsdt.dsl 7875: CreateDWordField (CRS, \_SB.PCI0._Y1A._MAX, MAX6) Optimize 6058 - NamePath optimized ^ (_Y1A._MAX) /Darwin/dsdt.dsl 7876: CreateDWordField (CRS, \_SB.PCI0._Y1A._LEN, LEN6) Optimize 6058 - NamePath optimized ^ (_Y1A._LEN) /Darwin/dsdt.dsl 7877: CreateDWordField (CRS, \_SB.PCI0._Y1B._MIN, MIN7) Optimize 6058 - NamePath optimized ^ (_Y1B._MIN) /Darwin/dsdt.dsl 7878: CreateDWordField (CRS, \_SB.PCI0._Y1B._MAX, MAX7) Optimize 6058 - NamePath optimized ^ (_Y1B._MAX) /Darwin/dsdt.dsl 7879: CreateDWordField (CRS, \_SB.PCI0._Y1B._LEN, LEN7) Optimize 6058 - NamePath optimized ^ (_Y1B._LEN) Elapsed time for major events Miscellaneous compile statistics 14225 : Parse nodes 3151 : Namespace searches 913 : Named objects 229 : Control methods 670 : Memory Allocations 2812067 : Total allocated memory 0 : Constant subtrees folded ASL Input: /Darwin/dsdt.dsl - 8540 lines, 264054 bytes, 3282 keywords Compilation complete. 2 Errors, 1 Warnings, 0 Remarks, 63 Optimizations All done. Enjoy ... Link to comment Share on other sites More sharing options...
InToGraphics Posted March 21, 2010 Share Posted March 21, 2010 Changing compiler was the least important of what I mentioned. You are obviously not using the exact same DSDT file. The error message with the missing device name is apparently gone/fixed. Which can only be done by specifying it, or start from scratch with a new DSDT. The error message you are having now also indicates that you started from scratch, because you forgot to add/copy the definition of the subroutine/function DTGP, which you are calling from lines 2709 and 2794. (Or maybe you gave it another name.) Link to comment Share on other sites More sharing options...
mg100796 Posted March 22, 2010 Author Share Posted March 22, 2010 Changing compiler was the least important of what I mentioned. You are obviously not using the exact same DSDT file. The error message with the missing device name is apparently gone/fixed. Which can only be done by specifying it, or start from scratch with a new DSDT. The error message you are having now also indicates that you started from scratch, because you forgot to add/copy the definition of the subroutine/function DTGP, which you are calling from lines 2709 and 2794. (Or maybe you gave it another name.) I'm 99% sure that I didn't start from scratch, but I added the block of code for the DTGP and it all compiled well (with one error i think). So I took out my GFX string and rebooted, but it didn't work! It didn't regonize either card or anything...any ideas? Link to comment Share on other sites More sharing options...
mg100796 Posted May 12, 2010 Author Share Posted May 12, 2010 Ok well I've been working very hard to get it working this past week and I believe I'm very close. I have created an an EFI string by combining the string for one card with another, but it will only work while one card is plugged in (it doesn't matter which, they both work) So I decieded to give DSDT another shot. I spent a while researching and stuff and I came up with a DSDT file that compiles without any warnings or errors or anything so I load it into Chameleon, and it doesn't seem to do anything. I don't know wheather or not it loaded. I don't even know if my i7 is working "fully". So any other ideas on Dual GTS 250's? How do I know if it has loaded or not? Is my DSDT right? (It's attached to this post) Please please..it's been 5 months and I still haven't had success DSDT.zip Link to comment Share on other sites More sharing options...
Recommended Posts