Jump to content

djblastyfone

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About djblastyfone

  • Rank
    Private
  1. djblastyfone

    D630 - El Capitan

    Sure, here you go: DSDT_D630n.aml.zip
  2. djblastyfone

    D630 - El Capitan

    Hi Jief, I have two D630's, one low-res x3100 running Lion + SL and one high-res nVidia model running Mavericks, sorry for the confusion (bought the nVidia one off eBay and they sent me the Intel, which the seller let me keep after sending me the correct one since it "wasn't worth the cost of shipping"). The X3100 model on Lion puts up the power dialogue when the power button is pressed, the nVidia model on Mavericks does not unless I hold Ctrl at the same time. I've attached the DSDT for the x3100 D630 if you still want to take a look! DSDT_D630i.aml.zip
  3. djblastyfone

    D630 - El Capitan

    I have the same issue with my D630n running 10.9.5, using Hervé's latest "Extra" folder for my model from the stickied thread in the D630 forum. Power dialog pops up fine with just the power button on my X3100 D630 on both Lion and SL, but it won't work unless I'm holding Ctrl on this machine. Do the power button methods differ between the D630 intel and D630 nvidia DSDTs?
  4. A warning to anyone thinking of picking up the Atheros AR5BXB112 (which seems to be the only 802.11n option for laptops with a full-height slot and 3 antennas): some of the cards being sold on eBay have defective firmware and will not work properly in OS X (they will, however, work in Windows, making the case for a getting a replacement card to the seller difficult). They show up as "{none}" under Wi-Fi device in BIOS (D630n, A17) and gives the device ID "168c:abcd" in DPCIManager (should be 168c:0030), and are not recognized even when the device ID is edited into the relevant kext. A quick Google search of the defective Device ID shows several threads with people encountering the same problem on both hackintosh and linux forums with this card. It seems to be an issue with the BIOS not properly initializing it. Also, from what I've read, I don't think it's possible to flash them with the correct EEPROM either, as the tools to do this don't appear to support the AR93xx chipset. Just a heads-up!
×