Hervé

DW1395 is not natively support. Did you install the pre-patched kexts or patch the vanilla IO80211Family kext. It's required; consult our Wireless card inventory thread. As stated in the MLPF v0.3 thread I linked above, airportd deamon also needs to be replaced. It's mentioned in our Wireless card inventory thread too. MLPF takes care of that but you chose to go your own way, so... Good luck with the rest. I'm sure you'll find the existing answers.

Tuh, tuh, tuh, exactly what I was saying: you're doing it wrong. The new/separate/temp installer has to be an MLPF installer, not a vanilla one on which you run MLPF. So, just follow the guide's very detailed steps 3 to 10 of phase 2 and: from the booted vanilla/unaccelerated ML installation, run MLPF app and create an MLPF installer, either on your USB key or on a small partition of your internal disk copy the bootpack (Extra folder) to the root of that MLPF installer boot that MLPF installer with boot args/flags DSDT=/Extra/DSDT.aml arch=i386 -f that you'll type at the prompt at the bottom of the screen after you've interrupted the bootloader process at the delay bar by pressing a key once this MLPF installer has booted up, do not install anything but click on Utilities menu of the Finder's bar and select MLPostFactor once MLPF app loads, click Continue until you're offered to select a destination volume under the HDD icon, make sure to: select your original vanilla/unaccelerated ML installation (not your MLPF installer partition) select/tick ML 10.8.4 in the list of ML versions given that your initial vanilla/unaccelerated ML installation should be 10.8.5 with all security updates installed click Install MLPostFactor once it's all done, click Quit MLPostFactor reboot your (now modified) initial ML installation with boot arg/options -f arch=i386 you should then reach a fully accelerated ML desktop from which you may now finish your MLPF'ed installation (steps 11 to 13 of phase 2) You need to thoroughly follow the process and not derive from it, otherwise you see what happens... NB: you say you create an OS X installer with asr. What's that?

It has to be something you're not doing properly. Can't see why the tool would not be able to write to your USB media. It's always worked flawlessly. And there is no patching of the kernel, it's plain replacement of kernel, kexts and graphics libraries by older fat binary versions from ML Developper Preview #1. Remember that you cannot boot the initial full vanilla ML installation in 32bit mode, the kernel does not support it. I reckon this is what you're doing. You have to boot the MLPF installer, whether you've made it on a USB key/disk or on a small partition of the internal disk as the guide suggests to do. When Chameleon (or Enoch) kicks in, you have to interrupt the process by pressing a key when you see the delay bar at the bottom of the screen, then choose the MLPF partition to boot. I think this is where you go wrong; that or you've not created the MLPF partition properly.

Hello, you're not really on the right track, no... For Sonoma (not Sanoma), go directly to the Sonoma guide, which is currently the last post of the entire thread; it's based on OpenCore v0.9.5 bootloader/tool hence the attached bootpack E7470_EFI_OC_0.9.5 (which you need to unzip before use). Just skip the El Capitan-related post at the top of the thread and all the subsequent ones for other macOS versions that do not apply. You obviously did not understand that each post was a guide in itself for a specific macOS version and that each guide contained its own Clover or OpenCore bootpack. Then, as a newcomer, do consult our FAQ section where you'll find answers to some of those questions like creating a USB installer from Windows.

I've updated my MLPF guide given that it was written in April 2013, i.e. before the release of ML versions 10.8.4 and 10.8.5. It's a step-by-step guide so you can't go wrong normally.

This comes out a little late (but better late than never) but there's been a couple of recent inquiries re: MLPF for installing and running ML on old laptops with GPUs dropped by OS X 10.8. After more than 10 years and given that MLPF was deleted from its original thread at MacRumors and that the authors have long moved on, I feel it's pretty harmless to post a copy of this old tool here for those who may be interested to use it. So here we go, MLPF v0.3: https://drive.google.com/file/d/1IXQAnhMBTLhJ7cFc0IXILmfMNu3cgwBi/view?usp=sharing The tool never got updated for ML 10.8.5 but it's only a cosmetic matter and it's totally safe to apply it as it is on 10.8.5. Upon completion, update file /System/Library/CoreServices/SystemVersion.plist to adjust reported ML version from 10.8.4 to 10.8.5. My recommendation for Hackintosh is to install ML 10.8.5 + all updates in initial (and slow) vanilla unaccelerated mode before applying MLPF for 10.8.4 on the installation. This will include reverting airportd to pre-10.8.4 version as newer one caused issues with certain wireless networks, as stated in the footer note #1 here.

Win7 fully supported GMA X3100. I ran it on my old D630 with Intel graphics without specific issues. I'm pretty sure I was able to run Win10 on it too before I sold it off a several years ago. I may have used the Win7 drivers, I can't remember. With regards to Lion 10.7, I never personally experienced the gremlins so many people complained about. We're now in 2024 so the D630, dating back to 2007, is going to be 17years old; that's... ancient, as are Lion (2011) and Mountain Lion (2012). No particular reason why MLPF would no longer work as it did back in 2012/2013. Remember that you need to have a legit copy of the Mountain Lion installation package, that's all. Apple made Lion and ML readily available a few years ago, so all is well on that front. For the rest, things should be exactly as per the guide I posted back in April 2013. Never tried any of the subsequent crap thingies that came out afterwards for Mavericks and later (MPF, etc.). In my opinion, MLPF was the best tool to use. Remember that all it does is revert back ML to DP1 kernel + kexts + other goodies and that it's not bug free (network related issues). With regards to installation, my recommendation is as follows: install ML and all updates to the latest Security Update for 10.8.5. This will be a little slow due to lack of graphics acceleration. install and apply MLPF for 10.8.4 (the tool was never updated for 10.8.5 but it's just cosmetic and all you need to do is modify the OS X system version plist afterwards) use MyHack v3.3.1 to build your ML USB installer. You may grab a copy of it here. you may grab the recommended versions of Chameleon and/or Enoch bootloaders here. a link to the Apple URL for downloading Mountain Lion 10.8.5 is available here. I've just uploaded MLPF v0.3 here given that it was deleted from its original MacRumors thread back in 2015. This being said, it's going to be difficult to give you much support for this after more than 10 years. It's all deprecated not to say totally obsolete and not many people still have D Series Hackintosh laptops today.

With a regular/standard installation, yes you need to use the SMBIOS of a supported Mac model for the target macOS version. You may then change to the SMBIOS that normally suits your laptop (here MBP8,1) and boot with boot arg -no_compat_check. OCLP takes care of that on the other hand.

With BIOS in UEFI mode, you can boot macOS on the E6220 once it has been installed but you cannot boot a USB installer. I think I had stated that in my old E6220 guide and/or the E6220 BIOS settings thread. Of course, you can always consider creating your installer on a small partition of your internal SATA disk. That should work but I can't remember if I ever tried that.

You cannot fake CFL graphics on s Skylake platform; stick to faking KBL graphics, the kexts are still provided in Sonoma so they remain natively supported for reasons explained before (see our Sonoma related threads). Have a look at my Sonoma guide for the E7270 for guidance.

Either your Touchscreen is not USB-based in which case it could be I2C or PCIe based and you'll need an adequate kext, or your USB ports are not properly mapped and the device is not properly detected. Can you post a zipped IOReg extract?

You can either: install macOS using a regular OpenCore method knowing that: you'll need to proceed with a config using the SMBIOS of a supported model you won't initially have graphics acceleration then revert to MBP8,1 SMBIOS, boot with -no_compat_check boot arg and manually proceed with OCLP patching with carefully selected parameters (OCLP is not made for Hackintosh but for real Macs) or you can indeed create a USB installer through the OCLP patcher and everything will be ready from the onset (still with carefully selected parameters).

Hi, it's old stuff now and I sold my E6220 a long time ago now but to answer your questions: yes, running Catalina with dosdude1's patcher is not without limitation and/or bugs. Today, given the development of the OpenCore Legacy Patcher since the Catalina and dosdude1's patcher days, you may want to consider a more recent macOS version (Big Sur and later) with OpenCore and OCLP given that this patcher is a lot more sophisticated and efficient than all tools that preceded it. Afaik, it fully supports the E6220 SMBIOS target model, i.e. MacBookPro8,1 with HD3000 graphics. You may check the Release Notes of all recent versions on the OCLP GitHub repo. no reason why the built-in microphone would not work; check that it's not disabled in your BIOS settings.

Check the equipment listed under USB in About this Mac->SysInfo. Eg. with my E7270 touchscreen:

Those specs aren't much helpful to sort out your predicament, are they? What about the touchscreen? As for your zip file, it's not downloadable...

In all likelihood, it's USB related. Post your full hardware specs and bootloader's EFIif you want support.

No such thing as an E7480 -> moving this thread from the E7xxx section to the 7xxx section.

No need to spoof KBL graphics for SKL iGPU in Monterey; SKL graphics remain fully and natively supported in macOS 12. You do not need any SSDT generated by Pike R Alpha's old script. All you need for Skylake CPU's default power management is to enable PlugIn type. SSDT-PLUG.aml.zip

Try and experiment with other SKL framebuffer layouts. I don't have a MacBook9,1 IOReg dump so can't say which layout it uses. Other important thing: you're using CPUFriend with its data file; did you make sure the data file was made for your CPU? I'd 1st run without those CPU tuning kexts, jut with basic default CPU Power Management.

Renaming this thread as, even if there were an issue, it would in no way be a "Dell bug" ! Not seeing the basic specs of your selected Mac model under the "MacBook Pro" line (like size, year and TB ports) is likely to be linked to your bootloader settings. Do check them out. Nothing to do with laptop's BIOS for sure. Can't say more, you've not bothered to post any details of your Hackintosh setup whatsoever. This being said, it's such a minor matter, I wouldn't waste much time on it...

As specified in our wireless cards inventory: No ! Those Qualcomm cards have poor support in OS X/macOS anyway. Go for a fully supported Broadcom card or, better, an Apple Card BCM94360CD on an mini-PCIe adapter board. Look-up our existing threads about this.

Derived from here I guess:https://osxlatitude.com/forums/topic/18153-latitude-5310-touchpad-gpi0-pinning-fix For the 3310, there's probably quite a lot to take from your 5310 contributions @hidematu5310. https://osxlatitude.com/forums/topic/18159-latitude-5310-small-fix-and-cleaning-up https://osxlatitude.com/forums/topic/18133-solved-latitude-5310-need-help-brightness-keys-f6-and-f7

REMINDER: As stated here, Sonoma drops all official support for Broadcom "legacy" wireless cards previously natively supported up to Ventura, the only hardware remaining natively supported being based on Apple proprietary Broadcom SOCs that aren't available to PCs/Hackintosh platforms. The only way to obtain wireless services on older Broadcom or Atheros cards is to patch Sonoma with OCLP patcher and apply all necessary/relevant properties & kext injections. Details available here. Intel cards are not impacted by this and require same 3rd party arrangement as before (ITLWM). As a result, this inventory will no longer be updated past Ventura which effectively froze the situation.

https://wikidevi.wi-cat.ru/Broadcom_BCM943228HMB Do consult our dedicated thread on Wireless cards in the R&D->Hardware technical info forum section. Do think of using the forum Search facility before posting. It would have led you to pages like this one, this one or this one or even this one... If @MaLd0n gave you this piece of advice, he was surprisingly misinformed or he misunderstood you because it's been known for at least 10 years that Broadcom BCM43228 chipset (PCI id 14e4:4359) is totally unsupported. You'll have to replace your card by a supported model. Above ASM code/properties injection applies to BCM4350-based cards (eg: DW1820A) as detailed here.

Lookup existing HP 640/650/840 G1 threads. Follow the Dortania guidance. Given that you have an existing Monterey setup, all you need to do is update your add-on kexts to latest versions (Lilu & PlugIns specifically), then make the necessary adjustments to your bootloader (version, config parameters such as quirks or boot settings).