Hervé

My Vostro200 has a DSDT with working sleep in SL, L, ML and Mav. Try it, it should work on the Inspiron 530, they're more our less identical machines. From memory, sleep was not working in my Yosmite DP installations, but then my HDD failed and I haven't replaced it yet. So no mainstream Yosemite tests on this one yet.

Ok, that's what I thought. The MBA6,x profile seems to give only LFM and HFM + all turbo boost frequencies, whereas the MBP11,1 gives an extra intermediary step. So it's an [email protected] your have then, not an i5-4300u. Over time, you should see boost frequencies in the range 22 to 29/33 (depending on number of active cores).

Just install Chameleon. A recent release like r2395 or r2401 will do absolutely perfectly.

Hi Jake, what CPU multipliers do you get with MBA6,2 SMBIOS on this machine? Did you try the MBP11,1 to compare?

If you have an Intel wireless card (like the 3945 model often found in these laptops), disable it in BIOS or remove it. It'll need to be replaced by a supported card.

Ok, well I can only advise you to seek RampageDev's assistance then. My knowledge of AMD Radeon HD cards is very limited. You can try RampageDev's other DSDT injection if you want. As I said, it's all listed on his blog.

Why do you use PciRootUID=1 and npci=0x2000? PCI root is correctly set to Zero in the original DSDT. Try with GE set to No.

Can we stick to AMD Radeon 7970 here please? Did you try the DSDT?

Try the attached patched DSDT in /Extra; boot with option DSDT=/Extra/DSDT_Patched.aml and let us know the result. DSDT_Patched.aml.zip

Oh, is it the actual source file? Man! I did not even think of that! It sure works now... IonGeneral, did you boot with option GraphicsEnabler=Yes?

Sorry, that DSDT file can't be opened. It looks far too big too (500Ko). Can you try to extract it with DSDTEditor, then save it as a .dsl (source) file?

Check that your BIOS is configured as per recommended settings and you should be Ok with my Lion pack. Your D430 has a Core2Duo CPU, right?

If you need to inject the card characteristics to the OS via DSDT, please post a saved output from IORegistryExplorer (specify which version of the tool you've used, there are several). We'll then be able to extract the necessary data and prepare a DSDT patch. Of course, post your DSDT too. If you're not using any DSDT file, even better, extract your raw table from BIOS through tools like Chameleon Wizard or DSDTEditor. I also recommend you read this. It explains it all in great details.

Last line is "still waiting for root device", so PCI issues. Screen corruption suggests you're either runnong on a BIOS not below A13 or not using the correct graphics framebuffer. Check out for possible hints in this Mavericks guide: https://osxlatitude.com/index.php?/topic/6387-dell-latitude-e6330-intel-hd-4000-graphics-mavericks/

Use the attached pack; needs nothing further, it has everything... D630i_LoRes_Lion10.7.5.zip

Well, can you give us the specs of the LAN port and Wifi card (PCI vendor and device ids at a minimum)?

In my case it were indeed unecessary: I just patched the Info.plist file and it worked on my E6440. Less hassle... Otherwise, please note that all kext binary contents are normally in .kext/Contents/MacOS subfolder and the binary file usually bears the name of .

Don't use the MBR patch of myHack v3.3.1, there's a bug. It's detailed in several posts in the myHack section.

It's a Haswell CPU, so there's a good chance your sudden laptop reset is due to the unpatched kernel if you're not booting with the Haswell-patched version.

The idea is not to patch the binary, but the Info.plist of the kext so that it matches the id of your own SD card reader. https://osxlatitude.com/index.php?/topic/7346-applesdxc-sd-card-driver-on-e7440/

Sleep requires hibernation to be turned off. EDP normally has an option for that, well it certainly used to! Open up Terminal and check hibernatemode through Terminal command sudo pmset -g. It's probably set to 3. Change that to zero through command sudo pmset hibernatemode 0. Then remove the sleep file previously created through command sudo rm -f /var/vm/sleepimage. That's it, on reboot Sleep/Wake should work perfectly.

There is no specific guide that I am aware of. Just use the regular installation process detailed in the EDP-Documentation section of the web site. If by X1300 you mean an ATI Radeon Pro X1300, it'll work with a bit of tuning/patching and only with SL; it's not supported beyond. I wrote how to get it to work either in my Vostro200 guide or somewhere in the Dell-Desktop section in an Optiplex 755-related thread. Just do a search on the forum and you should find it somewhere. For later versions of OS X, you'll need to change your card for a supported one. Again, a GeForce G210 is a cheap and cheerful solution and exists in passive cooling form.

You may want to give my E6440 guide a shot in terms of kexts and DSDT patching. It's for Mavericks at the moment and Chameleon based but kexts + DSDT patches should still apply.

In your particular case, I know some ways to install OS X on your D630 without needing a Mac or a Hack. I'll give you details of a legitimate method that does not involve distros and piracy but requires you possess a retail Mac OS X installation media. It basically consists of good old Nawcom's modCD + Snow Leopard retail DVD 10.6/10.6.3/10.6.8. SL 10.6.8 could still be purchased from Apple not that long ago, I posted a thread about it: https://osxlatitude.com/index.php?/topic/5561-buying-older-mac-os-x-versions At less than $20/20€, not much hesitation to be had, it's less than a poor man's spending on a basic saturday night... Nawcom's modCD comes as an ISO image you can restore to a bootable CD. You can make such a CD from Windows. The CD provides a Chameleon-based bootable Snow Leopard installer. Once booted, the installer will expect a media with the Snow Leopard installation app. Eject the modCD, insert the Snow Leopard DVD, press F5, select the newly inserted SL media and proceed with Mac OS X installation. This particular SL installation does not have to be fully tuned therafter; the idea is that it serves as a temporary base for you to create full vanilla USB installers with tools like myHack for instance. You would then be able to re-create a fully vanilla installation on another partition of the HDD and that installation could be Lion or Mountain Lion or Mavericks (whatever your D630 model actually supports). You'll have probably understood that your temp installation will become that (infamous) pre-requisite Mac or Hack that'll become eligible to full deletion once you made a subsequent fully tuned OS X installation. If you're happy with SL, you can of course keep that modCD installation and tune it up.

There are many reasons why a Hack or a Mac is the recommended intermediary step to create a OS X installer. A PC cannot natively boot an OS X media, it needs a special bootloader for that. Today, the 2 main ones are Chameleon and Clover. Apple does not ship bootable OS X media any more; I think last time they shipped DVDs was for Snow Leopard. When Lion came out, Apple initially offered it on USB keys, then it was a downloadable dmg image only. With a bootable DVD or USB key, you could use DVD-based boot loader/vanilla installers such as Nawcom modCD. Nobody makes that anymore, especially as kernels sometimes have to be patched to boot the targeted system (e.g.: some Haswell laptops). Even if such tools existed, the trouble is that a PC can't simply boot the OS X installation application to install OS X. It does not work that way unfortunately, that'd be too easy... As a result, making a bootable OS X installer is not just a simple matter of restoring that OS X install application dmg image to a bootable HDD or USB key. First, the OS X installer media has to be formatted to the OS X format. You can't do that from Windows. Then, packages or sub-images have to be retrieved from deep inside the installation package and mounted for restoration to the installer media. Then additional packages and hidden files have to be extracted and copied, etc. It's not exactly like a fly-through installation. There are no readily-available tools to do all this with sufficient ease from within Windows. As an alternative to a real Mac or an existing Hackintosh, virtual machines are often a much better alternative. All newcomers to the Hackintosh world have trouble understanding these matters initially, it's perfectly normal. Why would anyone need a Mac or a Hack to build a Hack? It does not make easy sense... However they understand this much better after a few OS X installations once they get more familiar with the internals of the installation process and of OS X. In the early days and for several years, distros attempted to support Mac OS X installation through a directly bootable DVD or media. However, this was considered piracy since they actually contained illegal (i.e. not paid for) copies of the OS X software and often also included uncontrolled additional stuff (drivers or patches or apps) that would work only on some systems, not others. That's why distros, despite their claimed generic status, often caused more trouble than good. Distros somehow got a bad name because users can't fully control the installation and do not necessarily know what's actually installed. In the Hackintosh world, it's very important to know and control that. With the advent of Mavericks, the piracy aspect has gone somehow (OS X is now free) and only one or two distros remain today. They aim to be as vanilla as possible but I don't know how well they can be considered vanilla these days. I don't use distros, haven't since Leopard 10.5. All my Snow Leopard, Lion, Mountain Lion, Mavericks and Yosemite installations have been vanilla. Look at it this way: newcomers (newbies) love distros because things look easy, experienced hackintoshers do not (for reasons stated above) and prefer fully controlled vanilla installations by far and large.