bikinifarm Posted January 21, 2010 Share Posted January 21, 2010 Well spotted! I don't have any firewire devices so it's never on my radar. The update with FWHD & FRWR. Tried it out, but unfortunately does not bring back the FW800. I think we may have to visit posts #850-#857 where we resolved this last time. Thanks also for explaining the OperationRegion thing. Curious thing. Clearing out the CMOS did not do the trick I guess. (ie. remove the battery, or use the jumper on the board) Last time I replaced a chip, I had to painfully repair a bunch traces with hair fine wire. Damn things are so small these days. In the olden days, we would just replace the chip with a socket. :-) DB1_v3.4_FWR_dsdt_Q6600.dsl.zip Link to comment Share on other sites More sharing options...
taney Posted January 21, 2010 Share Posted January 21, 2010 Hi! I currently have the P5K-VM board with 1001 BIOS Version. The rest of my specs are in signature. I installed via snow leopard universal 3.5 with 10.6.0 (10A432). I removed dsmos.kext and installed FakeSMC 2.5 kext. It boots up, it works. My video runs in vesa mode (not supported in osx yet) and my x-fi doesn't work. integrated audio works as 2.1 with voodooHDA. I'm still fairly new to the hackintosh world. I was wondering if you guys could point me in the right direction. how are your setups? i've noticed you guys have custom dsdt and packages. what are you recommendations for me? thanks soo much! I feel like such a newb in osx. i apologize. hope to hear from you guys soon. Link to comment Share on other sites More sharing options...
BlackCH Posted January 21, 2010 Share Posted January 21, 2010 Hi! I currently have the P5K-VM board with 1001 BIOS Version. The rest of my specs are in signature.I installed via snow leopard universal 3.5 with 10.6.0 (10A432). I removed dsmos.kext and installed FakeSMC 2.5 kext. It boots up, it works. My video runs in vesa mode (not supported in osx yet) and my x-fi doesn't work. integrated audio works as 2.1 with voodooHDA. I'm still fairly new to the hackintosh world. I was wondering if you guys could point me in the right direction. how are your setups? i've noticed you guys have custom dsdt and packages. what are you recommendations for me? thanks soo much! I feel like such a newb in osx. i apologize. hope to hear from you guys soon. Best is to install via retail disk using a boot CD (see my signature). Those 10.6 distributions are not clean; you never know what files it will install and that will become a problem when things are not working and you want to troubleshoot. We are using retail disks with 100% success. To see about all setup details read from page 35 on; you'll find everything you need on those pages. You cannot be sure your graphic card will be ever supported. You might want to get a Nvidia card PD: Hello everybody! Im back!.... How's going? Link to comment Share on other sites More sharing options...
DB1 Posted January 21, 2010 Share Posted January 21, 2010 Tried it out, but unfortunately does not bring back the FW800. I think we may have to visit posts #850-#857 where we resolved this last time. Your right, though I updated v3.2 in my back copy of v3.3 I had not updated hence missing it in v3.4. I've rectified that now so heres yours updated for Q6600. You will notice I modified slightly your PSS as it was looking a little odd to me, let me know if it's ok. V3.4_Q6600_DSDT.zip And an update of the general v3.4 dsdt.dsl DB1_v3.4_Updated_dsdt.dsl.zip In the olden days, we would just replace the chip with a socket. :-) I remember those times! Before much longer these things will be so small we will not be able to see them let alone solder them on! @BlackCH - good to see you back, you haven't missed that much. UPDATE: See later post for updated files Link to comment Share on other sites More sharing options...
bikinifarm Posted January 21, 2010 Share Posted January 21, 2010 Your right, though I updated v3.2 in my back copy of v3.3 I had not updated hence missing it in v3.4. I've rectified that now so heres yours updated for Q6600. You will notice I modified slightly your PSS as it was looking a little odd to me, let me know if it's ok. Unfortunately, FW800 is still not working. I noticed AR13 in the Device (PCI0) section is missing. Not really sure whether that is the culprit. I also noticed that with dsdt 3.4, the CPU is idling around 58°C (104°F) as opposed to 50°C (90°F) with version 3.3. This is regardless of whether I am using the the newly modified PSS section or the original PSS section. Thanks. Link to comment Share on other sites More sharing options...
DB1 Posted January 21, 2010 Share Posted January 21, 2010 Unfortunately, FW800 is still not working. I noticed AR13 in the Device (PCI0) section is missing. Not really sure whether that is the culprit. I also noticed that with dsdt 3.4, the CPU is idling around 58°C (104°F) as opposed to 50°C (90°F) with version 3.3. This is regardless of whether I am using the the newly modified PSS section or the original PSS section. Thanks. Doh! I remember it was the IRQ thing try this one. Q6600.zip AR13 is not needed. Updated General dsdt. DB1_v3.4_dsdt.dsl.zip Link to comment Share on other sites More sharing options...
bikinifarm Posted January 21, 2010 Share Posted January 21, 2010 Doh! I remember it was the IRQ thing try this one. Q6600.zip AR13 is not needed. Updated General dsdt. Unfortunately, still no dice. This one actually made the internal FW port go MIA as well. Link to comment Share on other sites More sharing options...
Master Chief Posted January 21, 2010 Share Posted January 21, 2010 @bikinifarm: That's because the following code snippet: Device (FRWR) { Name (_ADR, 0x00020000) Name (_GPE, 0x18) Method (_DSM, 4, NotSerialized) { Store (Package (0x02) { "fwports", Buffer (0x04) { 0x02, 0x00, 0x00, 0x00 } }, Local0) MCDP (Arg2, RefOf (Local0)) Return (Local0) } } was moved out of Device (PCIB). Moving it back will cure this. Edit: And looking at PCI0/_PRT which appears to be the root cause of your PCI FireWire card issue. Adding back one line should do the trick, but I cannot remember which one it is. Have a look at the address of the card (@3 or whatever) and them add back the line with the required IRQ. That alone should do the trick. Link to comment Share on other sites More sharing options...
DB1 Posted January 22, 2010 Share Posted January 22, 2010 Unfortunately, still no dice. This one actually made the internal FW port go MIA as well. Edit: And looking at PCI0/_PRT which appears to be the root cause of your PCI FireWire card issue. Adding back one line should do the trick, but I cannot remember which one it is No I cant remember either - its a pain not having a firewire device to debug these kind of issues. Try this I've put some stuff back in PCI0 PRT & FRWR is back in PCIB Updated (thanks to assistance from MC) v3.4_Q6600.zip Link to comment Share on other sites More sharing options...
taney Posted January 22, 2010 Share Posted January 22, 2010 Best is to install via retail disk using a boot CD (see my signature). Those 10.6 distributions are not clean; you never know what files it will install and that will become a problem when things are not working and you want to troubleshoot. We are using retail disks with 100% success. To see about all setup details read from page 35 on; you'll find everything you need on those pages. You cannot be sure your graphic card will be ever supported. You might want to get a Nvidia card PD: Hello everybody! Im back!.... How's going? THANK YOU SO MUCH BlackCH! I read through 10 pages of stuff, it's hard to understand it without actually doing it. After thoroughly reading your guide, it makes so much more sense. I think your custom boot disk is amazing! I have yet to try it. I'm awaiting drivers for my graphics card to be released or maybe wait till Apple supports a video card that supports DirectX11. I'm subscribed to this thread and will hope to hear exciting updates. Maybe one day I can contribute some, but I'm definitely learning more about hackintosh and the workarounds. THANK YOU all! EDIT: I CAN'T FORGET TO SAY THANKS DB1, bikinifarm, Master Chief, Freaky Chokra! Link to comment Share on other sites More sharing options...
Master Chief Posted January 22, 2010 Share Posted January 22, 2010 No I cant remember either - its a pain not having a firewire device to debug these kind of issues. See post #852: His PCI card is at address 0 and needs IRQ 10. And you moved Device (FRWR) into the brackets of Device (PCIB) correct? Edit: I checked your attachment (the one from post #934) but I either get the wrong file, or you attached the wrong file? Device (PCIB) { Name (_ADR, 0x001E0000) Name (_PRT, Package (0x09) // PCI Routing Table AR01 (ACPIspec30a.pdf / 6.2.11 / page 204). { Package (0x04) { 0xFFFF, Zero, Zero, 0x10 }, Package (0x04) { 0xFFFF, One, Zero, 0x11 }, Package (0x04) { 0xFFFF, 0x02, Zero, 0x12 }, Package (0x04) { 0xFFFF, 0x03, Zero, 0x13 }, Package (0x04) { 0x0001FFFF, Zero, Zero, 0x11 }, Package (0x04) { 0x0001FFFF, One, Zero, 0x12 }, Package (0x04) { 0x0001FFFF, 0x02, Zero, 0x13 }, Package (0x04) { 0x0001FFFF, 0x03, Zero, 0x10 }, Package (0x04) { 0x0002FFFF, Zero, Zero, 0x14 } }) Name (_PRW, Package (0x02) { 0x0B, 0x04 }) [color="#FF0000"]} Remove this one![/color] Device (FRWR) { Name (_ADR, 0x00020000) Name (_GPE, 0x18) Method (_DSM, 4, NotSerialized) { Store (Package (0x02) { "fwports", Buffer (0x04) { 0x02, 0x00, 0x00, 0x00 } }, Local0) MCDP (Arg2, RefOf (Local0)) Return (Local0) } } [color="#FF0000"]} And add this one![/color] @bikinifarm: You should be able to fix this yourself now. Correct? Link to comment Share on other sites More sharing options...
DB1 Posted January 24, 2010 Share Posted January 24, 2010 Edit: I checked your attachment (the one from post #934) but I either get the wrong file, or you attached the wrong file? Thanks Chief, my mistake updated post 934. Is anyone have idea how to configure 7.1 channel sound, it is working in 5.1 now ??????????????? Read this topic, it should help you sort it out. How to - 5.1 Surround and multi track input I've not read much as I have no need but it also mentions 7.1 so I guess the principals are same. Link to comment Share on other sites More sharing options...
bikinifarm Posted January 25, 2010 Share Posted January 25, 2010 @DB1 and MasterChief; Alright, got it working with a little bit of work starting with the version that DB1 posted on post #934 (the newer one), which is labeled for Q6600, but it actually is not for Q6600. After adding the Q6600 code, changing the OperationRegion parameter, and correcting the minor bug on line #136 Name (_PRT, Package (0x23) as Name (_PRT, Package (0x17) the dsdt does indeed work. A couple of observations specifically for Q6600: - The Q6600 seems to be running 8-9°C (14-15°F) warmer at idle (dsdt 3.4 vs. 3.3) - I could not get the PSS section recommended by DB1 on post #929 to work. Name (PSS, Package (0x05) // Q6600 Quad Core { Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x0A27, 0x0A27}, Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x0924, 0x0924}, Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x0821, 0x0821}, Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x071E, 0x071E}, Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x061B, 0x061B} }) Instead, the original from DB1 still does work. Name (PSS, Package (0x05) // Q6600 Quad Core { Package (0x06) {0x0A6B, 0x00015BA8, 0xA0, 0x0A, 0x0A27, 0x0A27}, Package (0x06) {0x0960, 0x00013498, 0xA0, 0x0A, 0x0924, 0x0924}, Package (0x06) {0x0855, 0x00011558, 0xA0, 0x0A, 0x0821, 0x0821}, Package (0x06) {0x074B, 0xF618, 0xA0, 0x0A, 0x071E, 0x071E}, Package (0x06) {0x0640, 0xD6D8, 0xA0, 0x0A, 0x061B, 0x061B} }) DB1 and MasterChief, many thanks to both of you. Working Q6600 dsdt 3.4 is attached. v3.4_Q6600.zip Link to comment Share on other sites More sharing options...
DB1 Posted January 25, 2010 Share Posted January 25, 2010 and correcting the minor bug on line #136 Thanks for pointing to the error, this of course should be the hex value as you have below. Name (_PRT, Package (0x17) { Package (0x04) { 0x0001FFFF, Zero, Zero, 0x10 }, Package (0x04) { 0x0001FFFF, One, Zero, 0x11 }, Package (0x04) { 0x0001FFFF, 0x02, Zero, 0x12 }, Package (0x04) { 0x0001FFFF, 0x03, Zero, 0x13 }, Package (0x04) { 0x001FFFFF, Zero, Zero, 0x12 }, Package (0x04) { 0x001FFFFF, One, Zero, 0x16 }, Package (0x04) { 0x001FFFFF, 0x02, Zero, 0x12 }, Package (0x04) { 0x001DFFFF, Zero, Zero, 0x17 }, Package (0x04) { 0x001AFFFF, 0x02, Zero, 0x12 }, Package (0x04) { 0x001BFFFF, Zero, Zero, 0x16 }, Package (0x04) { 0x0019FFFF, Zero, Zero, 0x14 }, Package (0x04) { 0x0019FFFF, One, Zero, 0x15 }, Package (0x04) { 0x001DFFFF, One, Zero, 0x13 }, Package (0x04) { 0x001DFFFF, 0x02, Zero, 0x12 }, Package (0x04) { 0x001DFFFF, 0x03, Zero, 0x10 }, Package (0x04) { 0x001AFFFF, Zero, Zero, 0x10 }, Package (0x04) { 0x001AFFFF, One, Zero, 0x15 }, Package (0x04) { 0x0002FFFF, Zero, Zero, 0x10 }, Package (0x04) { 0x0002FFFF, One, Zero, 0x11 }, Package (0x04) { 0x001CFFFF, Zero, Zero, 0x11 }, Package (0x04) { 0x001CFFFF, One, Zero, 0x10 }, Package (0x04) { 0x001CFFFF, 0x02, Zero, 0x12 }, Package (0x04) { 0x001CFFFF, 0x03, Zero, 0x13 } I had it reduced to 17 packages previous but when you lost firewire I put back what i removed. I'm now at these (16) Name (_PRT, Package (0x10) { Package (0x04) {0x0001FFFF, Zero, Zero, 0x10}, Package (0x04) {0x0001FFFF, One, Zero, 0x11}, Package (0x04) {0x0001FFFF, 0x02, Zero, 0x12}, Package (0x04) {0x0001FFFF, 0x03, Zero, 0x13}, Package (0x04) {0x001FFFFF, Zero, Zero, 0x12}, Package (0x04) {0x001FFFFF, One, Zero, 0x16}, Package (0x04) {0x001FFFFF, 0x02, Zero, 0x12}, Package (0x04) {0x001DFFFF, Zero, Zero, 0x17}, Package (0x04) {0x001AFFFF, 0x02, Zero, 0x12}, Package (0x04) {0x001BFFFF, Zero, Zero, 0x16}, Package (0x04) {0x001DFFFF, One, Zero, 0x13}, Package (0x04) {0x001DFFFF, 0x02, Zero, 0x12}, Package (0x04) {0x001AFFFF, Zero, Zero, 0x10}, Package (0x04) {0x001AFFFF, One, Zero, 0x15}, Package (0x04) {0x001CFFFF, Zero, Zero, 0x11}, Package (0x04) {0x001CFFFF, One, Zero, 0x10} It may not work for you and theres no harm done leaving it as is if everything working. But if you try it confirm please if ok. the dsdt does indeed work. A couple of observations specifically for Q6600: - The Q6600 seems to be running 8-9°C (14-15°F) warmer at idle (dsdt 3.4 vs. 3.3) - I could not get the PSS section recommended by DB1 on post #929 to work. That was a trial to see if it would work, "Zero, Zero" works for my cpu but i don't use AGPM or SMC fix kexts - using smbios identifier as iMac9.1 speed stepping works for me. Name (PSS, Package (0x05) // Q6600 Quad Core { Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x0A27, 0x0A27}, Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x0924, 0x0924}, Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x0821, 0x0821}, Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x071E, 0x071E}, Package (0x06) {Zero, Zero, 0xA0, 0x0A, 0x061B, 0x061B} }) Instead, the original from DB1 still does work. Stick with this if it's better Name (PSS, Package (0x05) // Q6600 Quad Core { Package (0x06) {0x0A6B, 0x00015BA8, 0xA0, 0x0A, 0x0A27, 0x0A27}, Package (0x06) {0x0960, 0x00013498, 0xA0, 0x0A, 0x0924, 0x0924}, Package (0x06) {0x0855, 0x00011558, 0xA0, 0x0A, 0x0821, 0x0821}, Package (0x06) {0x074B, 0xF618, 0xA0, 0x0A, 0x071E, 0x071E}, Package (0x06) {0x0640, 0xD6D8, 0xA0, 0x0A, 0x061B, 0x061B} }) Link to comment Share on other sites More sharing options...
bikinifarm Posted January 25, 2010 Share Posted January 25, 2010 No mistake actually there are 23 packages Yep, but I think you need to represent 23 in Hex, which is 17. Most recent version of iASLMe (1.2, December, I think) gives the following error: 136: Name (_PRT, Package (0x23) Remark 5048 - Initializer list shorter than declared package length ^ (Note: Older version iASLMe 1.0 does not give this error message.) When corrected to 17 (Hex), the error in compilation goes away. For the power management, let me see whether now I need to use iMac9,1 instead of MacPro3,1. Thanks once again for all the help. Edit: I do confirm that Name (_PRT, Package (0x16) { Package (0x04) {0x0001FFFF, Zero, Zero, 0x10}, Package (0x04) {0x0001FFFF, One, Zero, 0x11}, Package (0x04) {0x0001FFFF, 0x02, Zero, 0x12}, Package (0x04) {0x0001FFFF, 0x03, Zero, 0x13}, Package (0x04) {0x001FFFFF, Zero, Zero, 0x12}, Package (0x04) {0x001FFFFF, One, Zero, 0x16}, Package (0x04) {0x001FFFFF, 0x02, Zero, 0x12}, Package (0x04) {0x001DFFFF, Zero, Zero, 0x17}, Package (0x04) {0x001AFFFF, 0x02, Zero, 0x12}, Package (0x04) {0x001BFFFF, Zero, Zero, 0x16}, Package (0x04) {0x001DFFFF, One, Zero, 0x13}, Package (0x04) {0x001DFFFF, 0x02, Zero, 0x12}, Package (0x04) {0x001AFFFF, Zero, Zero, 0x10}, Package (0x04) {0x001AFFFF, One, Zero, 0x15}, Package (0x04) {0x001CFFFF, Zero, Zero, 0x11}, Package (0x04) {0x001CFFFF, One, Zero, 0x10} works with length declaration at 0x10 (Hex). (Firewire 800 drives are visible) Also, using iMac9,1 as identifier does not bring temperature levels back down to where they were with dsdt 3.3. Could it be how the sensors are read? Link to comment Share on other sites More sharing options...
Moby30 Posted January 25, 2010 Share Posted January 25, 2010 Here is another problem on 3.4: After a totally clean install (retail SL, supported by BlackCH's bootdisc + 3 additional kexts in E/E:p5kvm, fakesmc, osxrestart), volumes on my desktop are in orange (removable devices). and another: speedstepping, freq., voltages in voodoomonitor seems to be ok, but temp at idle is even higher than before(3.3), and PSS's copied from there, so there is no differences in PSS sections. Weird thing. Link to comment Share on other sites More sharing options...
DB1 Posted January 26, 2010 Share Posted January 26, 2010 Yep, but I think you need to represent 23 in Hex, which is 17. Most recent version of iASLMe (1.2, December, I think) gives the following error: Dohh! How stupid of me - of course they are hex values. Need to check my IASLMe version as I was not getting the errors to remind me, it must just be correcting for the aml. Edit: I do confirm that Name (_PRT, Package (0x16) { Package (0x04) {0x0001FFFF, Zero, Zero, 0x10}, Package (0x04) {0x0001FFFF, One, Zero, 0x11}, Package (0x04) {0x0001FFFF, 0x02, Zero, 0x12}, Package (0x04) {0x0001FFFF, 0x03, Zero, 0x13}, Package (0x04) {0x001FFFFF, Zero, Zero, 0x12}, Package (0x04) {0x001FFFFF, One, Zero, 0x16}, Package (0x04) {0x001FFFFF, 0x02, Zero, 0x12}, Package (0x04) {0x001DFFFF, Zero, Zero, 0x17}, Package (0x04) {0x001AFFFF, 0x02, Zero, 0x12}, Package (0x04) {0x001BFFFF, Zero, Zero, 0x16}, Package (0x04) {0x001DFFFF, One, Zero, 0x13}, Package (0x04) {0x001DFFFF, 0x02, Zero, 0x12}, Package (0x04) {0x001AFFFF, Zero, Zero, 0x10}, Package (0x04) {0x001AFFFF, One, Zero, 0x15}, Package (0x04) {0x001CFFFF, Zero, Zero, 0x11}, Package (0x04) {0x001CFFFF, One, Zero, 0x10} works with length declaration at 0x10 (Hex). (Firewire 800 drives are visible) Also, using iMac9,1 as identifier does not bring temperature levels back down to where they were with dsdt 3.3. Could it be how the sensors are read? Yes, by the cpu from what assigned in PSS not by the changes in PRT. Did you try this _PRT with your original PSS configuration and iMac9.1 identification and then with MacPro & kexts? The reason for the reduced PRT is that there appeared to be unused values (IRQ settings) and I just needed confirmation it did not harm the Firewire 800 detection. It maybe that some cpu's are more fickle than others it terms of the declaration they need in PSS, which could also explain why some need the added kexts where others don't to closer match cpu with the OS expectancy. i.e. core 2 duo is used in iMacs where Quads are in MacPro,s. I can actually have speed stepping without PSS declaration and just _CST or without both, but it only shows 3 steps. Here is another problem on 3.4: After a totally clean install (retail SL, supported by BlackCH's bootdisc + 3 additional kexts in E/E:p5kvm, fakesmc, osxrestart), volumes on my desktop are in orange (removable devices). Not sure what the P5KVM kext has included but the orange icon problem is SATA device id swap to ICH10 identifier. v3.4 dsdt has no device id changes as these I take care of via efi strings in com.apple.Boot.plist along with Audio and Video. I think I posted the device id's string previous. Device id hex and another: speedstepping, freq., voltages in voodoomonitor seems to be ok, but temp at idle is even higher than before(3.3), and PSS's copied from there, so there is no differences in PSS sections. Weird thing. Hmmm! I'll do a back check on what I removed for v3.4 to see if anything there is causing these temperature increases. Strange I have none of these issues! Link to comment Share on other sites More sharing options...
bikinifarm Posted January 26, 2010 Share Posted January 26, 2010 Dohh! How stupid of me - of course they are hex values. Need to check my IASLMe version as I was not getting the errors to remind me, it must just be correcting for the aml. No sweat. I only found out about it because of the error message. I just downloaded the January version of iASLMe from this thread Did you try this _PRT with your original PSS configuration and iMac9.1 identification and then with MacPro & kexts? Yes, and FW800 works. Using iMac9,1 or MacPro3,1 does not make a difference. The newer _PRT causes KP. Link to comment Share on other sites More sharing options...
DB1 Posted January 27, 2010 Share Posted January 27, 2010 No sweat. I only found out about it because of the error message. I just downloaded the January version of iASLMe from this thread Yes, and FW800 works. Using iMac9,1 or MacPro3,1 does not make a difference. The newer _PRT causes KP. I suggest anyone having problems with 3.4 should revert back to 3.3 if that more stable and providing full range of functionality. I've been running 3.4 for over a month before releasing and did so on basis I had no problems. I have tried to rectify the issues with the help of bikinifarm (thanks mate) but to no avail so it seems sensible to stick with what works flawless. There are of course a multitude of other variables involved e.g I'm using bleeding edge development of chameleon booting which might be resolving problems you are experiencing without me knowing and at the end of the day we just need everything to work which it was in 3.3. Thanks for feedback and assistance and keep an eye on the thread as there are some revolutionary changes about to take place soon with new releases from the chameleon team particularly associated with multi disk, partition and and multi boot set up management. 10.6.3 is due soon and Master Chief is in process of further development of "revolution". Link to comment Share on other sites More sharing options...
Hassan Rai Posted January 27, 2010 Share Posted January 27, 2010 Thanks for feedback and assistance and keep an eye on the thread as there are some revolutionary changes about to take place soon with new releases from the chameleon team particularly associated with multi disk, partition and and multi boot set up management. 10.6.3 is due soon and Master Chief is in process of further development of "revolution". Great help guys... thanks for sharing the progress. I cannot wait for the said revolutionary changes... esp looking fwd to compatibility with new gfx cards. as a side-note, our beloved Asus P5K-VM is getting on a bit now... god forbid if i lost mine to failure, i won't be able to replace it... is there any other board (from the current crop) with the kind of streamlined support we have got? Meaning, what BlackCH has done is quite unbelievable really... i wonder if such 'plug and play' support exists for any newer generation board on which people like DB1, BlackCH, Master Chief, Bikinifarm are working... Link to comment Share on other sites More sharing options...
navmessier63 Posted January 30, 2010 Share Posted January 30, 2010 Hello Guys, I have done something cosmetic. It will not enhance your motherboard performance. But it used to good if system profiler show proper device under Pci Card. So i make a device-id-plist by which system profiler show exact information which we want to show under PCI Cards. I have checked it with dsdt 3.4 provided by DB1 and use osx86 tool to create efi string. Thanks For DB1 for devic-id file. Plz change graphic string part with your's (Thanks db1 for mention.......) DevID.plist.zip Link to comment Share on other sites More sharing options...
DB1 Posted February 1, 2010 Share Posted February 1, 2010 Hello Guys, I have done something cosmetic. It will not enhance your motherboard performance. But it used to good if system profiler show proper device under Pci Card. So i make a device-id-plist by which system profiler show exact information which we want to show under PCI Cards. I have checked it with dsdt 3.4 provided by DB1 and use osx86 tool to create efi string. Thanks For DB1 for devic-id file Nice contribution - though I don't bother that much about cosmetics. It would be worth commenting that users will need to change the GFX0 to suit their own cards otherwise some lesser experienced users will download and say it don't work for them. Did you get your 7.1 surround working? Link to comment Share on other sites More sharing options...
navmessier63 Posted February 1, 2010 Share Posted February 1, 2010 Did you get your 7.1 surround working? oh! ya , I figured out that, was a simple affair( I m a dumb actually..) . And I don't think that someone who can create EFI-String and use your dsdt with own cpu stepping can't fiqured it out that wht should be changed. But anyway i agree with you that, i should have to mention it (I m a dumb actually.......now it sured .). If someone can't fiqured it out i m ready to help........... Link to comment Share on other sites More sharing options...
bikinifarm Posted February 6, 2010 Share Posted February 6, 2010 The Trust 15542-02 BT dongle seems to be receiving good functionality reports also. @DB1, I finally got a chance to try out the Trust 15542-02 bluetooth dongle to see whether that will wake up the computer through bluetooth keyboard or mouse input (both Apple), and the answer is still no. So; - ASUS USB-BT21 - works fine but no wake. No 'Allow BT devices to wake this computer' in BT advanced control panel. - D-Link DBT-120..B4 - same as above - Trust 15542-02 BT - same as above Wired keyboard or mouse continue to work fine in waking the computer. Non-bluetooth wireless mouse also works fine in waking. So the conclusion is that unless we are able to enable 'Allow Bluetooth Devices to wake this computer', BT will never wake it up based on swapping BT dongles. I guess we can put this to bed at this time. Link to comment Share on other sites More sharing options...
DB1 Posted February 7, 2010 Share Posted February 7, 2010 @DB1, I finally got a chance to try out the Trust 15542-02 bluetooth dongle to see whether that will wake up the computer through bluetooth keyboard or mouse input (both Apple), and the answer is still no. So; - ASUS USB-BT21 - works fine but no wake. No 'Allow BT devices to wake this computer' in BT advanced control panel. - D-Link DBT-120..B4 - same as above - Trust 15542-02 BT - same as above Wired keyboard or mouse continue to work fine in waking the computer. Non-bluetooth wireless mouse also works fine in waking. So the conclusion is that unless we are able to enable 'Allow Bluetooth Devices to wake this computer', BT will never wake it up based on swapping BT dongles. I guess we can put this to bed at this time. Thanks for the confirmation, it's no big deal to have to wake via power button but it would have been nice to have to give 100% mac clone. Link to comment Share on other sites More sharing options...
Recommended Posts