Hervé

If it's not already there, can you add the attached kext to /Extra/Extensions of your myHack USB installer and run myFix on it? lspcidrv.kext.zip Then, restart the installer and when you get to the installation screen, to to Utilities to open a Terminal command and type: lspci -nn. Then post the output of the command. Could you also confirm your BIOS version and check your settings against the recommend ones that are in the pinned thread? NB: On checking the boot pack, I saw that the SMBIOS plist is that of MBP5,1 now.

Glad to see it's all working. IntelCPUMonitor kext works with earlier release of FakeSMC such as v4.0. It's not required with newer versions published by Kozlek and in fact, clashes with them. I don't know what your IntelCPUController kext does. I don't have that on any of my D series laptops.

The guys used a retail version. The stuff you link to is only good for real Macs, though not all of them it would appear. I don't believe it provides the full packages of a retail version (it's mentioned in the comments) and those are required for a Hackintosh. For a retail version of ML, you can either sell your right arm and spend 18€ on AppStore or use Google, it's everyone's friend if you see what I mean... There must be tons of mountain river references these days. NB: EDP pages of this site offer a compatibility chart that you may want to consult re: your specs.

Audio, BT, wifi... it really all depends on the HW your have... Audio may work with a patched AppleHDA kext or with one of the recent VoodooHDA kexts (2.8.1 to 2.8.4 for e.g.). Have a look at Dinesh's dedicated threads in the forum Research section. BT may not be supported at all, it really depends on the chip used. I did not see any BT device in your lspci output dump. For wifi, you already know your Intel Centrino won't do. DW1510 works OOB but have a look at the (non-exhaustive) list of supported devices in our Research section. You'll find it has all the details you need for the listed models. SD card reader can be a bit of a lottery: some work OOB (like internal-USB models), some with SDHC kext, some not at all. Our compatibility chart in EDP pages should list all those HW features that are supported or not.

As far as I know, you cannot install ML (or any other recent Mac OS X version) that way. Recovery versions from rescue partition or even Mac OS X CD/DVD versions provided with real Macs cannot be used to install the OS on a PC. From memory (but I could be wrong of course), these recovery versions are just a minimal subset of the full system that allow to sort of boot a Mac and then grab the rest of the system off Apple's servers. I think it's explained here: http://www.apple.com/osx/recovery/ You need to use the retail versions, those available for purchase off AppStore. In the case of ML, the current shipping version is 10.8.4, but you can install any previous retail release from 10.8(.0) to 10.8.3. Whatever you use, it has to be retail.

There it is: https://osxlatitude.com/index.php?/topic/2864-solved-bootloader-not-working-on-4k-hdd/?hl=%2B4k+%2Bsector

When you're booted in Mac OS, try to download a new Chameleon package off the Net and install it. Alternatively, install Chameleon Wizard and try to update your HDD Chameleon to any version between v2248 and v2255 (these are known to work Ok on the laptop). Failing that, do a search on the forum about boot:0 error or 4k sector, you'll find a detailed procedure to fix 4k sector issues that can be encountered with newer HDDs. I just can't remember where it is off hand. Please note that you really should use GPT/GUID partitioning on your HDDs.

Which version are you trying to install? Snow Leopard? Lion? Mountain Lion? Are you sure you're using the right bootpack? I see a reference to MacBookPro5,1 in your very 1st picture and I don't believe there's any FakeSMC or SMBIOS plist that uses that model in the D830 bootpacks...

Yes, that is normal if you're not using the boot pack which should contain the lspci driver required for the command. You obviously have not done the EDP system build either. Well, if you do decide to proceed with the above and before rebooting, remember to remove any ATI X1300 and/or EvoEnabler kext that may remain in /Extra/Extensions, the re-run myFix (full). Alternatively, look for the graphics card ids in System Information (click Apple Menu and press Command (i.e. Alt or Windows) key). It'll be under PCI cards and/or Graphics/Displays.

Please guys, use the forum search facility before posting. Visible as very 1st post on main forum page (in Announcement & news section): https://osxlatitude.com/index.php?/topic/2870-read-up-boot-issue-kp-sl-installation-issue-with-myhack-32-beta8/&do=findComment&comment=21885

Try the following things: ensure you have BIOS A17 or A18 check your BIOS parameters and make sure they're set as per recommended settings in the pinned thread You say you've run EDP (I presume you meant doing a System Build) followed by myHack. What was the rationale behind that? Can you list the kexts you have in /Extra/Extensions? When you run EDP to do the System Build, you can actually modify the default settings as follows: in Kext/Drivers tab, set everything to OFF (that will get rid of nullCPUPowerManagement, SleepEnabler and Emulated SpeedStep) in Fixes tab, turn patched IOATAFamily to OFF (not necessary on D630) Then follow the instructions to enable native SpeedStep detailed here. Alternatively, use the files attached below, placing FakeSMC in /Extra/Extensions, SMBIOS.plist in /Extra and HWMonitor in Applications folder and re-run myFix to properly install the kext. FakeSMC_5.2.678_32-64bit.zip smbios.plist.zip HWMonitor_5.2.678.zip With MLPF, the kext cache generation can be problematic, so check what you have in /System/Library/Caches/com.apple.kext.caches/Startup. If you see no kextcache file, use the following Terminal command to try and generate it: sudo kextcache -system-prelinked-kernel. Regarding sleep, use Terminal command sudo pmset -g to check hibernation. If hibernate mode is set to 3 (or any non-zero value), use sudo pmset hibernatemode=0 to turn it off. That usually fixes sleep. Only reboot once you've done all this, then verify those troublesome items.

Yes, very nice: http://www.insanelymac.com/forum/topic/291614-intel-hd4000-and-haswell-inject-aaplig-platform-id/?do=findComment&comment=1942939

Look here for a non-exhaustive list of supported models: https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/

Oh well, I'm dry now!

->PM

If there's no DSDT difference between the 2 res models, then I'd strongly recommend that Ktbos switches back to BIOS A11. It appears that is the version you and osxjeff (and others) were/are running...

Watch out with BIOS. It's best to have same BIOS as those listed, especially with DSDT tables since they are extracted from BIOS. I would recommend you revert to version A11 if possible as DSDT tables appeared to work with that particular version.

Really? I would have thought his E6430s, BIOS A11, Intel HD 4000, 1366x768 & 1600x900 would be the same as yours, CPU and Lower res LCD excluded possibly. But since CPU does not matter for DSDT (contrary to SSDT), I would have expected his DSDT to work Ok. We could also compare DSDTs between 1366x768 and 1600x900 HD4000 models to check all possible differences.

Ok, I guess that if you changed to a lower res such as 1366x768 in your Cham boot plist, you'd get the same with the new res... I would say you have an issue either with the DSDT table in relation to screen definition or with the FrameBuffer. Did you try to boot in normal mode with display out to an external screen (HDMI or VGA, I don't know which you have/which works) ? You have the Intel HD4000-only model, I mean no NVS 5200M, right? Yes, you can delete kexts directly from SLE/myHack.kext PlugIns and boot without cache (-f UseKernelCache=No). That'll save you the myFix hassle during your testing phase. If you add kexts, you'll have to check permissions to ensure those added kexts are like the others. If need be, fix permissions with the following Terminal commands: sudo chmod -R 755 /S/L/E/myHack.kext sudo chown -R 0:0 /S/L/E/myHack.kext I'm wondering if we need to look at Jake's DSDT from here and see if there's something editable for the screen res...

It sounds like with the FrameBuffer, you get a dark screen right at the point where the OS switches to Mac OS desktop. When you boot in safe mode, yes, maybe the FrameBuffer is not loaded, so you could reach desktop with default unaccelerated graphics. This is quite similar to what you would get on a D630 Intel without proper DSDT (which contains correct graphics settings). With the D630, if you booted with display out to an external screen, it would revert back to LCD at the point where the OS switched to Mac OS desktop. You could try an external screen, but I doubt it'll do the same in your case. You say you boot with full screen resolution in safe mode but are you able to change res through the display pref pane? Thas is usually handled by the FrameBuffer. However, without FrameBuffer, if your boot plist specifies a specific resolution, the system can boot into that resolution without the ability to change it.

If this is a myHack installation, did you run myFix after deleting your kext(s)? Removing the kext from /E/E does not change anything until do this. You have to remember that myHack copies kexts from /E/E to place them in the PlugIns of myHack.kext (itself in /S/L/E) when myFix is run. This is the greatness of myHack in that it leaves /S/L/E totally vanilla and allows to bump/override any original /S/L/E kext that may be necessary without doing any modification to that kext. So basically, until you re-run myFix to update /S/L/E/myHack.kext (and also the cache), booting with or without kernel cache changes nothing.

Hi, Yes, the M4300 only comes with the nVidia card as far as I know since it is a Mobile Workstation model. Max. LCD resolution is usually supported OOB with any graphics card/chip that is supported by Mac OS (whether natively or with patched kext). With nVidia GPUs, I've never seen this being an issue. All Airport Extreme cards will work OOB, that's what Apple use in their own machine.

Ok, you're still doing this incorrectly. Do not update Chameleon on the myHack USB installer. Only update the Chameleon that is installed on your HDD partition after you have completed your installation. Create your 10.8 installer with myHack Install Extra with myHack, using the bootpack provided in the guide (i.e. choose "my own" and point towards the downloaded folder) Boot the myHack USB installer and install ML Then and only then, once you've passed the 1st boot configuration finalisation, you can update Chameleon bootloader (on your HDD, not the USB installer) to v2248 or above. Then continue with the guide. Which D620 model do you have? Also are you running the latest BIOS (A10) and did you set the parameters according to the recommended settings listed in the pinned thread?

Good stuff, glad you sorted it out. Could you provide a dump of a lspci -nn Terminal command (as shown in post above) to verify the PCI ids of that PNY card?

You need to obtain a proper retail copy of Mac OS X / ML installation app. The best solution is to spend the $20 it costs on AppStore; I know, it's a fortune... Otherwise, Google is your friend...