Hervé

DSDT.aml = DSDT table extracted from BIOS for patching, i.e. modification. You can read up on the Internet about DSDT table, but it basically describes the system's hardware and some of the low-level operations like Sleep and/or Wake. Kext = Kernel EXTension, i.e. a driver in Apple Mac world.

Here is the code you would need to insert in your cleanly extracted DSDT table. If it's missing within the code, insert DTGP method at top (for instance, before or after _WAK method): Method (DTGP, 5, NotSerialized) { If (LEqual (Arg0, Buffer (0x10) { /* 0000 */ 0xC6, 0xB7, 0xB5, 0xA0, 0x18, 0x13, 0x1C, 0x44, /* 0008 */ 0xB0, 0xC9, 0xFE, 0x69, 0x5E, 0xAF, 0x94, 0x9B })) { If (LEqual (Arg1, One)) { If (LEqual (Arg2, Zero)) { Store (Buffer (One) { 0x03 }, Arg4) Return (One) } If (LEqual (Arg2, One)) { Return (One) } } } Store (Buffer (One) { 0x00 }, Arg4) Return (Zero) } Then look for Device (PCI1) and under a small section that will read something like xxxxxxx (_ADR, 00010000), add: Device (GFX0) { Name (_ADR, Zero) Method (_DSM, 4, NotSerialized) { Store (Package (0x24) { "AAPL,slot-name", "PCIe x16", "@0,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@0,display-cfg", Buffer (0x04) { 0x03, 0x01, 0x03, 0x00 }, "@0,device-type", Buffer (0x08) { "display" }, "@0,name", Buffer (0x0F) { "NVDA,Display-A" }, "@1,compatible", Buffer (0x0B) { "NVDA,NVMac" }, "@1,display-cfg", Buffer (0x04) { 0xFF, 0xFF, 0x00, 0x01 }, "@1,device-type", Buffer (0x08) { "display" }, "@1,name", Buffer (0x0F) { "NVDA,Display-B" }, "class-code", Buffer (0x04) { 0x00, 0x00, 0x03, 0x00 }, "vendor-id", Buffer (0x04) { 0xDE, 0x10, 0x00, 0x00 /* nVidia */ }, "device-id", Buffer (0x04) { 0x65, 0x0A, 0x00, 0x00 /* GeForce 210 */ }, "VRAM,totalsize", Buffer (0x04) { 0x00, 0x00, 0x00, 0x40 /* 1Go memory */ }, "NVCAP", Buffer (0x14) { /* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x03, 0x00, /* 0008 */ 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0A, /* 0010 */ 0x00, 0x00, 0x00, 0x00 }, "device-type", Buffer (0x0C) { "NVDA,Parent" }, "name", Buffer (0x08) { "display" }, "model", Buffer (0x11) { "Asus GeForce 210" }, "hda-gfx", Buffer (0x0A) { "onboard-1" } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } In fact, reboot without DSDT but with Chameleon boot option PciRoot=4 or with attached fixed boot plist in /Extra. I could bet you obtain full QE/CI! org.chameleon.Boot.plist.zip

Perfect, now I see everything I was hoping for and I can patch your DSDT! Except I'm not sure of your DSDT files. At the main level of your dropbox folder, there is a DSDT.dsl which does not compile and a DSDT.aml which is actually a DSDT dsl source code not a compiled DSDT table. So, sorry to appear like a pain, but can you again boot without any DSDT (but with PciRoot=4) and extract a clean DSDT with Chameleon Wizard or DSDT Editor? I'll then be 100% confident with my patch. Your GeForce G210 is actually a 1Go model, not 512Mo by the way.

Erm, I would have not expected the Vostro200/Inspiron530s DSDT to work on that machine; there's nothing in common at all. If any Dell DSDT were to be used (and I would never recommend that), it would be the D430's which bears some similarities with this HP's hardware (GM945 chipset, GM1950 graphics, ICH7-M controller, etc.) Try and list your lspci -nn specs to see if we can do anything. For Ethernet, the E1000 or E1000e kext might work...

Rules, what rules? What's free you can download, what's not free you have to pay to download... Apps on the AppStore cannot usually be found elsewhere. It's a complete economic concept.

When you saved your IOReg output, was that after a boot using a specific DSDT table or was it without a DSDT table? Ideally, I need the IOreg after a boot without any specific DSDT as the one you're using (found on the Net) may not reflect truly your hardware... I'm still not seeing what I expect for your graphics card, stuff is missing... Your DSDT.aml and DSDT.dsl, were they obtained when you had no DSDT used at all or did you extract them from say Windows with a tool like AIDA64? We need totally clean tables...

Tried those from myHack generic bootpack? You can access them by browsing within the myHack app itself (after right clicking on it), they're hidden somewhere but can't remember the exact path...

DW1395/DW1397 are actually Ok on clear networks, not on encrypted ones. It's the same issue as encountered from ML 10.8.4.

Haha, assuming that's what you meant by "editing", it's one thing to patch a plist and quite another to write a whole kext! However, if you're up to it: http://developer.apple.com/library/mac/documentation/Darwin/Conceptual/KernelProgramming/Extend/Extend.html

Actually, it's PciRoot, not PCIRoot; the syntax difference is very subtle but nonetheless very important, otherwise option is quite simply ineffective... Can you therefore modify your boot plist to that effect, reboot and redo and IORegistryExplorer? I'm not seeing all that I was expecting for your graphics card, like the NVCAP info... I had a quick look at your DSDT and it is quite similar to the table found to my Precision 670. They are really written in very similar fashion. I'll try and send you a patched DSDT later on. Meantime, you can have a look here for hints on DSDT patches. Also, please note that editing your Chameleon boot plist with tools such as Chameleon Wizard would overwrite the PciRoot parameter. So, if you use that tool, make sure to manually edit the plist afterwards to re-instate the option or you'd have to manually specify PciRoot=4 at boot time. As I found out on the Precision 670, you will never obtain full QE/CI unless your PCI root is set to the proper value. For Ethernet, use the attached kext (place in /Extra and run myFix (quick)). Intel82566MM.kext.zip

Always leave SLE untouched unless absolutely necessary. Cuda drivers are not required, no. Can you tell us the result of the following command (it's for your PCI root Id) after you remove PCIRootUID=3 from your Chameleon boot plist and reboot: ioreg -l | grep -15 "AppleACPIPCI\ " | grep UID ?

Have you ever written a device driver before? If not, well, it's a full time job...

Please give us details/specs so that we can add it to the list of supported devices. Thanks.

Can you please post your specs so that we can evaluate your system?

Are you running a myHack installation at all?

I'll see what I can do...

Ok, that confirms GeForce G210 graphics card, for which the boot option mentioned above should trigger full support natively. If not, post a copy of your DSDT + saved IORegistryExplorer output and we'll get the card injected into the DSDT. I don't see any Ethernet controller listed, it's probably disabled in BIOS...

Haswell platforms do not seem to support OS X too well for the moment...

This GeForce G210-based Asus EN210/DI/512MB graphics card? That should be Ok from SL to Mavericks! Are you using GraphicsEnabler=Yes boot option? Please give us an lpsci output with Terminal command lspci -nn !

You really need to identify that video card model, it's important in Mac OS X as it may or may not be supported and that totally impacts usability of the system. If the card proved to be unsupported, forget OS X until you replace it with a supported model. Did you try booting with option PciRoot=1/2/3/4 ? Did you try setting your SATA operation to RAID=On ?

Not PCIe? Wow, that must be a rare model, I only knew of PCIe x1 version outside of the usual PCIe x16, but it seems there were PCI versions too! So, it's one like this? May be that's not well supported by OS X... Try with the NVEnabler kext in/E/E (followed by myFix (quick) or course) though.

Yes, the usual method is our documented method you just mentioned, based on myHack + OSXL bootpack + post-installation tuning with EDP.

Sounds like a kernel issue. Please post your system specs so that we can try and help you more.

Haswell platform (and you have an unlocked CPU!) lacks decent support for the time being unfortunately. It's indeed highly likely to be a kernel issue... Try to boot with option -v to see if you can squeeze more info before it goes into reboot.

Can you please list your specs of that machine? CPU, chipset, graphics card, RAM, HDD, LAN, wireless, etc. You don't necessarily require AHCI setup to install and run ML (or OS X). Eg: Latitude D620 or many other systems that do not have specific SATA AHCI enabling facility in the BIOS, yet run ML without problem. What options do you have in BIOS, if anything at all? If you have RAID, you can try to use that instead (without creating any array of course). Did you try and boot your installation with Chameleon boot flag -v to see where it hangs?