Hervé

Where do you see that? If in "About this Mac", a permissions repair through Disk Utility usually fixes this, otherwise if it's within a CPU monitoring tool, that would be CPU throttling.

1) make sure you have the latest copy of ModCD -> http://nawcom.com/osx86/ModCD/ 2) make sure you have a proper Retail SL 10.6.0/10.6.3/10.6.8 DVD (if you don't it's not difficult to get an image, but you'll have to restore it, either to a USB key or a DVD) Boot ModCD, swap disc, press F5. That's it, I've just done it on my D620 GMA950 LoRes and I get to the Snow Leopard installer without any problem. That is without any option and with default legacy kernel. Again, yes, update your BIOS to the latest version and configure it as per recommended settings, that'll put your system in the best possible configuration to support OS X and get support from this place.

Installing EDP must be followed by a System Build, otherwise your /Extra is more or less empty... EDP System builds also call on myHack/myFix, so if your system was not installed through myHack, you'd be calling for trouble trying to use EDP. If you want to revert to what you had before, simply reinstated the Extra that you will now find at the root of your HDD named "/Extra_backup..." and, assuming your system was built with myHack, simply run myFix (full) to repair permissions + caches. You would not normally use EDP unless your particular system has been integrated in it.

"Kill myself or quit building my mac?" -> The 1st option will directly result in the 2nd, so option #1 will suffice! Did you try the mach-kernel? Failing that, you could always reinstall that dodgy SLV1 ISO and restore to a USB key the image I made for you from the retail DVD yesterday. It was in the "To keep" folder on the desktop. I hope you did not delete it or wipe your HDD without copying its contents to a key or something... If not, yes, kill yourself. Once you have that SL key ready, you can simply copy the bootpack onto it and try to boot that key with ModCD. It should certainly be Ok with mach_kernel. I might try ModCD on my own D620 GMA950 tonight, but frankly, this is exhausting!

Make sure you have the lspcidrv kext in /E/E when you boot your installer, then once at installer screen, go to Utilities to open a Terminal window and type lspci -nn. That'll list your hardware specs as detected by the OS. Did you try to boot with the well-known patched IOATAFamily kext at all? I would also disable Bluetooth in BIOS if possible; that was known to cause keyboard/mouse issue with Lion which was looking for BT devices and ignoring built-in keyboard when BT was on. You never know...

Start again and DO NOT select ElliotRTC in the options... It's off by default and it's not a good idea to select everything out of ignorance (best recipe to fail). A little search on the forum could have led you here: https://osxlatitude.com/index.php?/topic/2880-d420-video-issues-w-multiple-osx-versions-what-am-i-doing-wrong-here/&do=findComment&comment=22054 or here: https://osxlatitude.com/index.php?/topic/147-dell-latitude-d430-thread/page-7&do=findComment&comment=9243 or many more... It's just a matter of reading: KP on ElliotRTC -> do not select ElliotRTC.

How about looking at your ATA controller id through lspci -nn command, then check the IOATAFamily kext for a potential patch?

Indeed. I encountered the same problem on an E6420. The HDD was not visible from the OS X installer, however, if I took it out and connected it to a USB adapter, I could install OS X on it. On checking the BIOS, I found the HDD mode to be set to RAID. So, check your BIOS settings...

EDP is not compatible with the method you used to install OS X on your machine. If you intend to use EDP, you have to install OS X with myHack.

Root = 1st level of your media (HDD, CD/DVD or USB pen). In Unix/Linux/Mac OS/etc. world, it is also referred by '/'. folders = branches files = leaves So you basically need to copy your custom/Atom kernel to the very 1st level of your USB pen. There are 2 things you can do: 1) rename your existing mach_kernel (i.e. the Mac OS original kernel) to something like old_mach_kernel (or whatever you like) and copy your Atom kernel as mach_kernel. By default Mac OS boots the Mach kernel... 2) leave your Mach kernel as is and copy your Atom kernel as atom_kernel (or whatever you like) at the root. Then open up Chameleon Wizard and update the boot plist tab to specify your newly copied atom_kernel (or whatever you named it) as bootable kernel. See example below. If you don't change your Chameleon boot plist, you will have to invoke the Atom kernel as boot option (enter the Atom kernel file name after the Chameleon ? prompt). That's it.

Actually, I would keep whatever settings are currently in place in the system works/boots fine. I would simply adjust the boot delay parameter as suggested above but that's it.

HD3000 is supported natively provided your DSDT is accurate. Did a brief ML install on my wife's company Latitude E6420 and that worked out straight away with the right DSDT.

Difficult to say until you can actually compare hardware specs. And that goes beyond CPU, RAM and graphics chip. Once comparison is feasible, you may re-use kexts, but not DSDT/SSDT, starting off with a Generic bootpack...

Point noted. There are other enhancements we need to do on these pages. Whenever we find the time...

The nVidia model is indeed the machine you should choose as it supports all recent Mac OS versions, from Snow Leopard 10.6 to the forthcoming Mavericks 10.9 in 32/64bit mode. The Crestline models can run Snow Leopard and Lion natively in 32bit mode and Mountain Lion in 32bit mode with a special Hack called MLPF. You can swap wireless cards, yes and you would have to as Intel cards are not supported by Mac OS. You need a system with SL 10.6 minimum. PB G4 running Tiger is no use. It is the latest version Apple commercialise at the moment. Mavericks should be released next month (and is fully supported by D630 nVidia). I believe Snow Leopard can still be ordered somehow -> might need to call your local Apple Rep for that. Lion is no longer available as far as I know. Please think of doing a search before posting a thread as most of these questions either been asked and answers provided or are covered in the various pages of the Web site.

Hi and welcome on OSXLatitude. Have a browse through the various sections of the forum, you'll find dedicated support sections for various systems, including the Latitude D Series.

Last update: 20 Jun 2023 Questions keep resurfacing, so let's try to clarify things again: minimum requirements for Snow Leopard: https://support.apple.com/kb/sp575?locale=en_US minimum requirements for Lion: https://support.apple.com/kb/sp629?locale=en_US minimum requirements for Mountain Lion: https://support.apple.com/kb/sp654?locale=en_US minimum requirements for Mavericks: https://support.apple.com/kb/sp702?locale=en_US minimum requirements for Yosemite: https://support.apple.com/kb/SP711?locale=en_US minimum requirements for El Capitan: https://support.apple.com/kb/sp728?locale=en_US minimum requirements for Sierra: https://support.apple.com/kb/sp742?locale=en_US minimum requirements for High Sierra: https://support.apple.com/kb/SP765?locale=en_US minimum requirements for Mojave: https://support.apple.com/kb/SP777?locale=en_US minimum requirements for Catalina: https://support.apple.com/kb/SP803?locale=en_US minimum requirements for Big Sur: https://support.apple.com/kb/sp833?locale=en_US minimum requirements for Monterey: https://support.apple.com/en-us/HT212551 minimum requirements for Ventura: https://support.apple.com/en-us/HT213264 Essential basics: Lion (and later) requires a 64bit Core2Duo minimum even though it may have to run in 32bit kernel mode (eg: for supported old Intel GMA graphics or old NVIDIA Curie graphics). From Mountain Lion, OS X runs a 64bit kernel only. 32bit kernel mode is abandoned, hence the drop of support for older GPUs for which only 32bit fully functional drivers are available (e.g.: Intel GMA 950/GMA X3100, nVidia GeForce 7xxx and derivatives). Sierra drops support for Broadcom BCM431x and BCM4321 wireless cards (no workaround). Sierra and later require SSE4-capable CPUs (SSE4 instructions set introduced in Penryn family C2D/C2Q/Xeon CPUs). Non-SSE4 platforms such as Conroe/Merom are limited to El Capitan. Mojave drops support for non SSE4.2-capable C2D/C2Q platforms (workaround exists). Mojave drops support fior Atheros wireless cards (workaround exists). Mojave and later require a Metal-compatible card (Kepler-only for nVidia (lack of Web Driver oblige), GCN1.0 and later for AMD, HD4000 and later for Intel). Mojave is last macOS version to support 32bit apps. Catalina and later support 64bit apps only. Catalina drops support for BCM4322 wireless cards (workaround exists). Big Sur drops support for Broadcom BCM4331 and BCM43224 wireless cards (workaround exists). Monterey drops support for Intel HD4000 and nVidia Kepler graphics (workaround exists). Workarounds for Broadcom and Atheros cards previously dropped no longer work. Ventura drops support for pre-Kaby Lake Intel iGPUs (workarounds exist for Skylake and older generations) and pre-Polaris AMD dGPUs. Sonoma beta1 drops support for Broadcom BCM4350, BCM4360 and BCM43602 "legacy" wireless chipsets, limiting support to Intel cards and compatible USB adapters. For Hackintoshing purposes: Netburst/revived P6/original Core 32bit platforms (Pentium 4/D/M, Yonah, etc.) are natively supported from Tiger 10.4.4/10.4.5 to Snow Leopard 10.6.8. Netburst and Core2 64bit platforms (Pentium 4/D, Conroe/Merom, Wolfdale/Penryn, etc.) are natively supported from Tiger 10.4.7/10.4.8. 1st gen Nehalem/Westmere platforms (Lynnfield, Clarkdale/Arrandale, etc.) are natively supported from Snow Leopard 10.6.2/10.6.3. 2nd gen Sandy Bridge platforms are natively supported from Snow Leopard 10.6.6. 3rd gen Ivy Bridge platforms are natively supported from Lion 10.7.5. 4th gen Haswell platforms are natively supported from Mountain Lion 10.8.5. 5th gen Broadwell platforms are natively supported from Yosemite 10.10.2/10.10.3. 6th gen Skylake platforms are natively supported from El Capitan 10.11.4. 7th gen Kaby Lake platforms are natively supported from Sierra 10.12.6. 8th gen Kaby Lake Refresh & Coffee Lake platforms are natively supported from High Sierra 10.13/10.13.1. Fully supported in 10.13.6. 8th gen Amber Lake Y (UHD617) platforms are supported from 10.14.1. 9th gen Coffee Lake Refresh and Whiskey Lake platforms are natively supported from Mojave 10.14.4/10.14.5. 10th gen Comet Lake and Ice Lake platforms are natively supported from Catalina 10.15.3 and are the last Intel platforms supported by macOS. 11th gen Tiger Lake & Rocket Lake platforms, 12th gen Alder Lake platforms and so on are not supported. Only desktops of such generations with a supported graphics card or laptops with a supported dGPU may run macOS with all appropriate settings/patching. No support whatsoever for Tiger Lake/Rocket Lake/Alder Lake and later iGPUs which is a complete show-stopper for laptops. NB: Here, "support" means official and native support by Apple OS, not potential support with/after patching.

No, you need a Core 2 Duo for Lion (and/or ML); with core Solo or Core Duo, you're limited to Snow Leopard. This being said, a T7200, T7400 or T7600 shouldn't be too hard to buy for very cheap these days...

If you have a bluetooth module, disable it if you can. If you can't, just plug your USB keyboard before you boot your Lion installer.

AppleHDADisabler.kext.zip

From memory, AppleHDADisabler can be found in the EDP audio kext packs in /Extra/Storage (the kext is installed in /E/E at EDP System Build if you choose VoodooHDA audio), but I can easily upload it here later on. I'll give you an example of a reason for not deleting or changing kexts in /S/L/E: your mods are overwritten at the next update! For instance, delete AppleHDA in 10.8.5, it'll come back in 10.8.6 and you'd be back to square one. On the contrary, handling kexts trough /E/E + myFix is protected during/after updates since those kexts are managed specifically through /S/L/E/myHack.kext.

Again, you should avoid doing such kext modifications in /S/L/E. You should have just copied VoodooHDA + AppleHDADisabler in /E/E and simply run myFix (full). Obviously that 2nd kext takes care of the VoodooHDA/AppleHDA kexts cohabitation issue...

Just installed Lion 10.7.2 on the D620 GMA950 on which I had previously fitted one of my WXGA+ LCD screens. I built my USB installer with myHack 3.1.2 + OSXL D620 GMA950 HiRes boot pack. All looks Ok, I do not get any black screen neither at installation, nor on 1st boot. All Ok after EDP System Build (important to apply GMA950 brightness fix). Conclusion: if you follow our usual installation process with your D620, everything will be Ok (D620 fitted with a (cheap and cheerful) 1.83GHz T5600 Core2Duo CPU).

Fair enough, but I'm no sure about kexts... I've had a good look at my D430 which as the optional built-in STMicroelectronics finger scanner and I believe it actually works without any apparent kext. To me, the software deals with the hardware directly. The hardware is reported as a Biometric Coprocessor in the System Report.

Even if the D620 BIOS reports something like "Intel 945GM graphics", the integrated graphics chip of that D620 remains nevertheless the GMA950. Have no doubts on that point, GMA945 does not exist per sé. http://en.wikipedia.org/wiki/GMA_900#GMA_900 -> Extract from Intel Mobile 945 Express chipset datasheet Yes, Lion is supported on that model, it's in the Compatibility chart and there's a boot pack for it. Having recently done various reinstalls on my D620 GMA950 LoRes, I can vouch that things do work for that model but I'll have to swap LCD to verify things with the HiRes version. You did use our OSXL D620 Intel GMA950 (1440x900) Lion bootpack, right? At this stage, you may suspect the DSDT but I'll have to verify a Lion installation with our bootpack to confirm this. Bear in mind that latest myHack (v3.2) bears the issue of booting in 32bit mode until you update Chameleon to v2248 or above. That may also be the cause of the problem (although unlikely) but there's a very easy way to verify that point: boot with option arch=x86_64. You won't have QE/CI in 64bit kernel mode, but that'll potentially help pinpoint the root cause of your black screen problem. Alternatively, stick to myHack v3.1.2.