Hervé

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?

Mavericks is fully supported on nVidia models only. Just refer to the compatibility chart. There are no specific issues or bugs. You need to proceed with brand new installation using the usual process and you can install over your existing ML setup to keep your existing files and apps. Mavericks will run just as well as ML 10.8.5 on that laptop.

It's not a compatibility issue with the D620, the issue you encountered is a bug with myHack 3.3.1 for SnowLeopard installers. I've been able to confirm that myself, especially if using it from an existing SL installation (it actually overwrote the installation it was run from). There is no known issue with myHack v3.3.1 for Lion/ML/Mavericks on any machine we support here. If you want to install SL on your D620, try and use and older version of myHack such as v3.1.2.

It's totally stable, have you read anywhere that it wasn't? As far as performance is concerned, I would personally say that it's better with SL than Lion. SL is ever so snappy, quicker to boot and it's a blast to shut down! Make a backup beforehand, but you can normally install a new OS X version over an existing one and it keeps all your files and apps. It certainly worked for me on my D630n when I installed ML over Lion, then Mav over ML. You could always try out Lion from a USB key or an external USB HDD before you make a final decision...

No problem to install & run 10.9.1.

You need a retail copy of Snow Leopard DVD and there are only 3 such versions: 10.6.0, 10.6.3 and 10.6.8. Once you have that, installation is a piece of cake. To purchase a copy of SL 10.6.8, look here. Failing that, Google is your friend...

I made some additional DSDT edits for the (unsupported) built-in Adaptec SCSI controller + AC'97 audio. . For Adaptec Ultra-320 adapter, within PCI2, I added: Device (SCSI) { Name (_ADR, 0x000E0000) Method (_DSM, 4, NotSerialized) { Store (Package (0x0C) { "AAPL,slot-name", Buffer (0x09) { "Internal" }, "class-code", Buffer (0x04) { 0x00, 0x04, 0x01, 0x00 }, "model", Buffer (0x2A) { "Adaptec AIC-7901 Ultra320 SCSI Controller" }, "name", Buffer (0x15) { "RAID SCSI Controller" }, "device-id", Buffer (0x04) { 0x8F, 0x80, 0x00, 0x00 }, "vendor-id", Buffer (0x04) { 0x05, 0x90, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } . For AC'97 audio, within PCI0, I added: Device (HDEF) { Name (_ADR, 0x001F0005) Method (_DSM, 4, NotSerialized) { Store (Package (0x10) { "AAPL,slot-name", Buffer (0x09) { "Internal" }, "class-code", Buffer (0x04) { 0x00, 0x01, 0x04, 0x00 }, "codec-id", Buffer (0x04) { 0x74, 0x53, 0x44, 0x41 /* ADS74 */ }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x11) { "Audio Controller" }, "model", Buffer (0x21) { "AC'97 (AD1981B) Audio Controller" }, "device-id", Buffer (0x04) { 0xd5, 0x24, 0x00, 0x00 }, "vendor-id", Buffer (0x04) { 0x86, 0x80, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } This is all cosmetic, but I like it...

It can also help to remove the NVRAM plist from /Extra (if you use the NVRAM module). The file is automatically recreated afterwards.

Well, you don't have any graphics kext loaded for your card, so no graphics acceleration, hence no graphics support. Look no further, that's where you problem comes from. You probably need to patch your DSDT to inject your card details or patch your nVidia kext. Look at RampageDev's blog, I believe he has a post about some GTX card. Of course, you can also head over to nVidia's web site for a driver (maybe a Cuda driver); most people don't even think about that!!!

No problem with 10.9.1, I updated my initial 10.9 installation and had no subsequent problem. Maybe you should just reinstall Mavericks...