Jump to content


  • Content count

  • Joined

  • Last visited

About BadKarma

  • Rank
    InsanelyMac Protégé
  1. Thank you (Obrigado) so much kind Sir. The new DSDT fixed the subject problem. Can you post/share what you did?
  2. Greetings, I have the following message displayed during boot I was able to find a DSDT patch that is supposed to address this error, however I'm not sure how to make it work for my DSDT, which does not contain _ADR, 0x001D0007. Patch: # Fix for "AppleUSBEHCI::CheckSleepCapability - controller will be unloaded across sleep" # into method label _DSM parent_adr 0x001D0007 remove_entry; into device name_adr 0x001D0007 insert begin Method (_DSM, 4, NotSerialized)\n {\n Store (Package (0x04)\n {\n "AAPL,clock-id",\n Buffer (0x01)\n {\n 0x01\n },\n "device_type",\n Buffer (0x05)\n {\n "EHCI"\n }\n }, Local0)\n DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n Return (Local0)\n } end; into method label _DSM parent_adr 0x001A0007 remove_entry; into device name_adr 0x001A0007 insert begin Method (_DSM, 4, NotSerialized)\n {\n Store (Package (0x04)\n {\n "AAPL,clock-id",\n Buffer (0x01)\n {\n 0x02\n },\n "device_type",\n Buffer (0x05)\n {\n "EHCI"\n }\n }, Local0)\n DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))\n Return (Local0)\n } end Hoping someone can help me modify the patch to work for my DSDT. Thanks in advance. This is for a Dell Dimension 9200 w/ Core2 Duo E6600 processor and Nvidia 9600 GT 512mb Graphics. 8086,2836 Intel 82801H (ICH8 Family) USB2 EHCI Controller #1 8086,283a Intel 82801H (ICH8 Family) USB2 EHCI Controller #2 Attached: DSDT & IOReg Archive.zip
  3. Rampage Dev .... I was just comparing your edited DSDT with the one I attached in my original post, I didn't find WAK method removed. I did a search for "WAK" through both DSDT and nothing was changed in terms of Method WAK. Again I noticed Method PSW was gone from Device EUSB. Not sure if I understand correctly terms used, or simply I'm mistaken. I totally agree w/ you, Sleep and SSDT seem to be the biggest huddles for most people from what I have read and experiencing. Anyways, I do sincerely appreciate you taking the time to assist me. On another note, I visited your blog and planning on submitting my raw DSDT.aml for the EVGA Z68 FTW motherboard. Again, Thanks for all the great work you do.
  4. Thanks Rampage! I'll test it out, once I get home and let you know. Can you let me know what was changed? Just trying to learn. Thanks again. Rampage Dev .... just got done testing your edited DSDT. The problem still exists. I noticed you removed Method (_PRW, 0, NotSerialized) from Device EUSB. I've actually done that before too, but no joy. Don't know if there were any other edits, but the problem still remains. From Terminal: Last login: Wed Sep 12 21:20:16 on console Nelsons-Mac-Pro:~ Nelson$ syslog |grep -i "Wake Reason" Sep 12 21:20:38 Nelsons-Mac-Pro kernel[0] <Debug>: Wake reason: GBE EUSB Nelsons-Mac-Pro:~ Nelson$ Let me know if you have any other suggestions or let me know what additional information I could provide to help my cause. Thanks again.
  5. Greetings. I'm currently lost in finding a solution to how to address my current problem with my system immediately Waking From Sleep. Some System Details: MB: EVGA Z68 FTW CPU: Intel i7 2600K OCed 4.2 GHz BIOS A05 DSDT: Patched w/ DTGP, IRQs, SMBUS, HDEF, ACL889, _T_x Rename, Possible Operator Timeout is ignored (Compiles w/ no errors or warnings) Current OS: Mountain Lion 10.8.1 From: Cassio at Olarila.com Quote: If the system goes to sleep and wakes immediately, look for "Wake reason" in kernel log and edit method _PSW or remove _PRW from that device in DSDT. Nelsons-Mac-Pro:~ Nelson$ syslog |grep -i "Wake Reason" Aug 30 09:12:19 Nelsons-Mac-Pro kernel[0] <Debug>: Wake reason: GBE EUSB Aug 30 22:48:20 Nelsons-Mac-Pro kernel[0] <Debug>: Wake reason: GBE EUSB Aug 31 08:26:24 Nelsons-Mac-Pro kernel[0] <Debug>: Wake reason: GBE EUSB Nelsons-Mac-Pro:~ Nelson$ When the system wakes from sleep the following error message appears. "Because a USB device was drawing too much power from your computer, one or more of your USB devices have been disabled. To prevent damaging your computer, the USB device drawing too much power has been disabled. Other devices may have also been disabled. When you disconnect the device drawing too much power, your other USB devices will be enabled again." I have tried the following: Code: ------------------------------------------------------------------------------------- delete from here Method (_PRW, 0, NotSerialized) { Return (GPRW (0x0D, 0x04)) } ------------------------------------------------------------------------------------- to here Still problem with waking from sleep. As Cassio from Olarila.com, suggested Quote: before removing _PRW try applying USB patches (EHCI, UHCI) for your chipset. _PSW edit is to make it always store zero, remove the condition on arg0 http://olarila.com/f...=19&t=301#p2860 I can't locate EHCI or UHCI on my DSDT. My USB seem to show as Device EUSB. When using DSDTSe, I'm able to locate UHCI, but it appears as Device EUSB on my DSDT. I took a look at all the patches and they seem to be directed at "Name (_ADR, 0x001D0007)" my device is listed w/ "Name (_ADR, 0x001D0000)", hence I did not try any of the patches. In regards, to Editing method_PSW I'm confused as how to add this method since the information I found thus far reference Devices as i.e.. USB2,USB3 and such. UxEN, which are not found on my DSDT. http://www.insanlynac.com/forum/inde...entry1533492 Any help would greatly be appreciated. DSDT2.aml.zip
  6. Thank you Gringo! That's not the best news, but appreciate the definite answer thus I can end my search. Craig: It may benefit you to view the following thread: http://www.insanelymac.com/forum/index.php?showtopic=271917&st=0&p=1770590&hl=facetime%20error&fromsearch=1entry1770590 And review the attachments to view the changes made and hopefully it will provide you with the solution to this problem. Thanks again, Gringo. I'll look into purchasing a new compatible NIC.
  7. I'm experiencing the same problem. Which bootloader along with version are you using? I've read that this may be solved with updating or reinstalling the bootloader. In addition, you can try to remove NetworkInterfaces.plist from //Library/Preferences/SystemConfiguration and reboot. Need to also confirm the Ethernet is (en0). Though this did not work for me, it did solve the problem for many others. Much like you I have found numerous tweaks or suggested solutions, but have yet solve this issue. Currently I can only connect via Wifi, since I don't have Ethernet, which is making it much more difficult to isolate the problem or test suggested solutions. Hope to hear additional recommendations.