-
Posts
10013 -
Joined
-
Last visited
-
Days Won
560
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
I'd say it's as safe a usual; but keep a backup or a full image of your current 10.10.3 installation...
-
Last updated: 15 Jun 2024 We still get recurring questions about some well-known and older unsupported GPUs and graphics cards, so let's try and make a quick recap here. The list can be completed as required and necessary. The list will only apply to SL 10.6 and beyond, not before. Intel ----- Gen3 ----- GMA 900: unsupported since SL. GMA 950: supported in SL and Lion in 32bit kernel mode only; unsupported since ML. GMA 3100/3150: unsupported. ----- ----- Gen4 ----- GMA 3000/X3000: unsupported GMA X3100: supported in SL and Lion in 32bit kernel mode only; unsupported since ML. GMA 4500/4500M/4500MHD/4700MHD: unsupported. ----- ----- Gen5 ----- GMA HD/GMA 5700MHD/1st gen Intel HD (i.e. Ironlake of Clarkdale & Arrandale CPUs): partially (CI (i.e. screen resolution) only) or fully (full QE/CI) supported on laptops from SL 10.6.4 to High Sierra depending on built-in LCD connector (LVDS=full support, eDP=partial support); unsupported since Mojave. Refer to bible thread on the matter. Partial graphics support usually means platform is more or less unusable and therefore unsuitable as a Hackintosh. Special patches required for OpenGL-only support in Mojave and Catalina (and later?). ----- ----- Gen6 ----- Sandy Bridge Intel HD (GT1): unsupported. Sandy Bridge Intel HD 2000 (GT1): unsupported. Sandy Bridge Intel HD 3000 (GT2): supported from SL to High Sierra; unsupported since Mojave. Special patches required for OpenGL-only support in Mojave and Catalina (works very poorly in Big Sur/Monterey so best avoided). ----- ----- Gen7 ----- Ivy Bridge Intel HD (GT1): unsupported. Ivy Bridge Intel HD 2500 (GT1): unsupported; some unconfirmed reports of apparent support in ML from 10.8.3 and partial support (CI only) in El Capitan. Ivy Bridge Intel HD 4000 (GT2): supported from Lion to Big Sur; unsupported since Monterey but patch exists (see footnote). Bay Trail Intel HD (GT1): unsupported. Haswell Intel HD (GT1): unsupported. Haswell Intel HD 4x00/5000/Iris 5x00 (GT2/GT3): supported from ML 10.8.5 to Monterey. Unsupported since Ventura but patch exists (see footnote). ----- ----- Gen8 ----- Cherry Trail Intel HD/HD 4xx (GT1): unsupported. Braswell Intel HD/HD 4xx (GT1): unsupported. Broadwell Intel HD (GT1): unsupported. Broadwell Intel HD 5x00/6000/Iris 6x00 (GT2/GT3): supported from Yosemite 10.10.3 to Monterey. Unsupported since Ventura but patch exists (see footnote). ----- ----- Gen9 ----- Apollo Lake Intel HD 5xx (GT1): unsupported. Skylake Intel HD 510 (GT1): unsupported. Skylake Intel HD 515/520/530/Iris 5x0 (GT2/GT3/GT4): supported from El Capitan 10.11.4 to Monterey. Unsupported since Ventura but patch exists (see footnote). ----- ----- Gen9.5 ----- Kaby Lake Intel HD 610 (GT1): unsupported. Kaby Lake Intel HD 615/620/630/Iris+ 6x0 (GT2/GT3): supported from Sierra 10.12.6 to Sequoia. Kaby Lake R Intel UHD 620 (GT2): supported as per Kaby Lake with KBL framebuffer 0x59160000 and faking KBL iGPU id 0x5916. 8th gen Amber Lake Y Intel UHD 617 (GT2): supported from Mojave 10.14.1 to Sequoia (with KBL settings). ----- Coffee Lake Intel UHD 610 (GT1): unsupported. Coffee Lake Intel UHD 630/Iris+ 6x5 (GT2/GT3): basic support in High Sierra 10.13.6 from 1st Security Update build 17G2208 (iGPU ids 0x3E92/0x3E9B/0x3EA5); extended support from Mojave to Sequoia. Coffee Lake R Intel UHD 610 (GT1): unsupported. Coffee Lake R Intel UHD 630/Iris+ 6x5 (GT2/GT3): supported as per Coffee Lake with faking CFL id 0x3E92 up to Mojave 10.14.3; natively supported from Mojave 10.14.4 to Sequoia. Whiskey Lake Intel UHD 610 (GT1): unsupported. Whiskey Lake Intel UHD 620 (GT2): supported as per Coffee Lake with CFL framebuffer and faking CFL id 0x3EA5. Comet Lake/Comet Lake R Intel UHD Graphics for 10th gen. processor (GT1/GT2): supported from Catalina 10.15.4 to Sequoia with CFL settings. Caution must be exercised though given that Intel somehow recycled Coffee Lake UHD6x0 (itself a refresh of Kaby Lake R graphics). for desktop CPUs, Intel reused the UHD6x0 naming convention: Comet Lake UHD 610 (GT1): unsupported Comet Lake UHD 630 (GT2) supported as per Coffee Lake things differ quite a lot for mobile CPUs: generally speaking, UHD Graphics of mobile Comet Lake i3/i5/i7/i9 "U" CPUs is equivalent to UHD 620 (GT2); those have 23 (i3) to 24xEUs (i5/i7/i9) and are expected to be supported (not necessarily OOB). generally speaking, UHD Graphics of mobile Comet Lake i3/i5/i7/i9 "H" CPUs is equivalent to UHD 630 (GT2); those have 23 (i3) to 24xEUs (i5/i7/i9) and are expected to be supported (not necessarily OOB). as an exception to those rules, some mobile "U" and/or "H" CPUs (eg: i5-10200H) have an iGPU with 12xEUs only which is equivalent to UHD 610 (GT1) -> unsupported. all mobile Celeron and Pentium have a 12xEUs UHD Graphics, i.e. equivalent to UHD 610 (GT1) -> unsupported. known ids of CML iGPU with 12xEUs only: 0x9B21, 0x9BAA, 0x9BA4, 0x9BAC (+ desktop id 0x9BA8) -> unsupported. known ids of CML iGPU ids with 23 to 24xEUs: 0x9B41, 0x9BC4, 0x9BCA, 0x9BCC (+ desktop ids 0x9BC5, 0x9BC8) -> expected to be supported (not necessarily OOB). a recap of CML iGPUs is available in the following Intel document: Intel UHD Graphics Open Source. Programmer's Reference Manual.pdf.zip ----- ----- Note about GT1 iGPUs ----- Basically, from Gen6 HD 3000 to Gen9.5 UHD 6xx iGPUs, there is no support for low-end/entry-level GT1-based Intel HD/UHD graphics. ----- ----- Gen11 ----- Ice Lake Intel UHD (G1): apparently supported from Catalina 10.15.4 to Monterey by faking id of G4/G7 counterparts as stated here. Ice Lake Intel Iris Plus (G4/G7): supported from Catalina 10.15.4 to Sequoia. ----- ----- Later generations (Gen12 and beyond) ----- No support for subsequent iGPU generations to be expected, Apple having switched to M1 silicon after Ice Lake generation. Lots of iGPU info available here: https://en.wikipedia.org/wiki/Intel_Graphics_Technology nVidia GeForce 6x00 and similar (Curie NV4x): unsupported since SL 10.6.3 at least (some cards supported in early SL versions only). GeForce 7x00 and similar (Curie G7x): supported in SL and Lion in 32bit mode only; unsupported since ML. Tesla generation (G8x, G9x, GT2xx) supported SL -> High Sierra; unsupported since Mojave. Special patches required for OpenGL-only support in Mojave and later (see footnote). Fermi generation (GFxxx): supported Lion -> El Capitan; buggy/poorly supported in Sierra and High Sierra; unsupported since Mojave. Kepler generation (GKxxx): supported from Lion 10.7.5/ML 10.8.2 to Big Sur but cards based on GK106 chip are best avoided (driver memory leak issue); unsupported since Monterey, special patches required for Monterey and later (see footnote). Maxwell generation (GMxxx): supported from (late) Yosemite to High Sierra and only with the nVidia Web Driver; unsupported since Mojave (no Web Driver). Pascal generation (GPxxx): supported from (late) Sierra to High Sierra and with the nVidia Web Driver; unsupported since Mojave (no Web Driver). Turing generation (TUxxx) and later: unsupported. Support for Kepler cards was dropped in Monterey beta7, marking the end of official support for the last nVidia cards (i.e. Kepler) that remained usable/supported in macOS until then. Special patches apply thereafter (see footnote). ATI/AMD Radeon X300/X600/X700: unsupported. Radeon X800: apparently supported in SL and Lion; unsupported since ML. Radeon X1000: X1300/X1400/X15x0: supported up to SL; limited support (CI only) in Lion; unsupported since ML. X1600/X1900: supported in SL and Lion; unsupported since ML. ----- Radeon HD 2xxx: some models supported in SL up to High Sierra; unsupported since Mojave. Radeon HD 3xxx: some models supported in SL up to High Sierra; unsupported since Mojave. Radeon HD 4xxx: some models supported in SL up to High Sierra; unsupported since Mojave. Radeon HD 5xxx: many models supported in SL up to High Sierra; unsupported since Mojave. Radeon HD 6xxx: many models supported in SL up to High Sierra; unsupported since Mojave. Radeon HD 7xxx: many models supported from ML to Monterey; unsupported since Ventura. Radeon HD 8xxx: many models supported from ML to Monterey; unsupported since Ventura. ----- R7/R9: many models supported from Yosemite to Monterey; unsupported since Ventura. Polaris 10: Lexa unsupported. Baffin supported from Sierra to Sequoia. Ellesmere supported from Sierra to Sequoia. Careful with Radeon RX550 which exists in both Lexa and Baffin versions (needs to be 640SP and id 1002:67FF). Polaris 20/30: most models supported from Sierra to Sequoia. Vega 10: many models supported from High Sierra to Sequoia. Vega 20: some models supported from Mojave to Sequoia. Navi 10: many models supported from Catalina to Sequoia. Navi 20: unsupported. Navi 21: some models supported from Big Sur to Sequoia. Vavi 22: unsupported. Navi 23: some models supported from Monterey to Sequoia. Navi 24: unsupported. Navi 3x: unsupported. ----- APUs: unsupported. ----- Mojave and later require GCN1.0 cards minimum (i.e. HD 7000/HD 8000/ R7/ R9 Series). An excellent recap of things is available at Dortania's GPU buyer's guide (defunct one here). Not to be missed for detailed guidance on Intel graphics configuration: the WhatEverGreen user manual. An absolute must with complete documentation for Intel iGPUs. NB: Obsolete GPUs for which Apple dropped official support after Lion 10.7.5 (e.g.: GMA950/X3100, GeForce 7x00, ATI X1600) can be supported in ML with MLPF hack (essentially, a hack that runs pseudo ML in 32bit mode with DP1 32/64bit kernel and kexts). Details are available our ML with full QE/CI guides for old unsupported Latitude laptops in our Archives section. The work is based on the original R&D stuff covered in ML on unsupported Macs available at MacRumors.com. Older Intel and nVidia GPUs for which Apple dropped official support after High Sierra 10.13.6 (e.g.: 1st gen Intel HD, SNB HD3000, nVidia Tesla GPUs) can be supported in Mojave/Catalina in OpenGL-only mode by installing drivers from High Sierra and reverting some frameworks. More details in subsequent post below.. nVidia Tesla GPUs may be supported in OpenGL-only mode in Big Sur and later with OCLP patcher. See dedicated thread about Big Sur on unsupported Macs at MacRumors.com. Intel HD4000 graphics may be supported in Monterey and later with special patches. nVidia Kepler GPus may be supported in Monterey and later with special patches (official support was dropped from beta 7). Haswell, Broadwell and Skylake iGPUs were dropped in Ventura, however: Skylake HD 5x0 graphics are pretty much fully supported by faking KBL iGPU, using KBL framebuffer layouts, using WEG 1.6.1 or later and KBL SMBIOS Haswell and Broadwell graphics may be fully supported after patching with tools such as OCLP 0.5.1 and later.
-
Not sure it'll be of any use, but I made up a new Recovery partition logo/icon for the Chameleon bootloader so that those partitions can too enjoy their own icons. Haven't sussed out the correct file name that should be used specifically for recovery partitions, but the default HFS+ icons (Lion logo) can be used to that effect. Rename the existing default HFS+ files to keep a backup before installing this logo. Attached .png file is to be placed in the /Extra/Themes/Default folder. device_hfsplus.png.zip
-
Following up on the Yosemite logos, I made up new El Capitan logos/icons for the Chameleon/Enoch bootloader so that El Capitan partitions can too enjoy their own icons. Fits nicely along all the other icons. Attached .png files are to be placed in the /Extra/Themes/Default folder. ElCap_themes_logos.zip
-
Moving to Enoch Chameleon branch to get rid of Clover USB key to boot El Capitan. Enoch r2725 and above appear to boot 10.11 properly. Typing this, having booted DP4 from Enoch r2725, then r2737. Means we can go back to good old Chameleon method and re-use /Extra folder (from say Yosemite). Boot option kext-dev-mode=1 no longer required but keep option rootless=0 if you intend to modify systems files such as kexts in /S/L/E for instance. In a similar way to what was experienced with Clover, kexts no longer load when placed in /E/E. Instead, they must be placed either in /L/E or in /S/L/E, permissions repaired and cache rebuilt. Once that is done, everything is perfect and the little laptop boots fast. Warning: patched AICPUPM (or NullCPUPM) mandatory with Enoch/Chameleon since Clover Asus AICPUPM on-the-fly patch is no longer available.
-
Up to DB4 through AppStore update. This one appears different... Caution with this one as add-on kexts no longer load from the usual Clover EFI folder. This is critical for kexts such as FakeSMC and the kexts must be installed in /S/L/E or /L/E, followed by permissions repair + cache rebuild. As a precaution, you may opt to boot without cache on 1st reboot. DB4 appears more problematic than previous versions: I experience occasional minor or major graphics glitches (can be odd artefact or full garbled screen) + random freezes. Chameleon Wizard v4.4.1 keeps crashing at launch.
-
You have an IvyBridge CPU that requires the (MSR-)patched AICPUPM kext or, pending such patch, to use NullCPUPM. https://osxlatitude.com/index.php?/topic/7853-vanilla-and-patched-yosemite-kernels-patched-aicpupm-kexts/
-
-
Visit HP's web site, enter your model n° + serial n° and you should be able to retrieve your exact specs. You could also use the little app called CPUZ or any other available tool that can provide full system specs in understandable and readable terms. Because the above really is kind of... unusable.
-
Just follow the process detailed here and you can't normally go wrong. If you 1st boot using Clover, you should not need to manually create a /S/L/K folder and copy the kernel to it. That's only applicable to Chameleon if you use Chameleon directly on your USB key and never use Clover. I've separated the final process re: bootloaders to distinguish what needs to be done for Clover and for Chameleon.
-
Same answer... http://ark.intel.com/fr/products/59570/Intel-Celeron-Processor-B800-2M-Cache-1_50-GHz Get to know your hardware specs; it's not just a matter of CPU model and RAM quantity. Chipset, LAN card, wireless card, audio card, etc. all participate to the good or bad running of OS X.
-
Could you please try and post your pictures the right way up? Thanks.
-
"Extra" Folder for M4600 Setup for OS X Mavericks Setup
Hervé replied to Cyber_Redeem's topic in The Archive
There is no dedicated kext for that card. The vanilla nVidia kexts will support it, possibly with a patch, but I don't think that's required. What's the GPU chip of your card?- 20 replies
-
If the PC freezes at the BIOS splash screen, it's obviously a POST issue, not a USB installer/OS X issue. More like some inability for your PC to boot off the USB key or recognize/support it properly.
-
No confusion to be had about the kernel. If anything, the patched kernel posted name should be self-explanatory... Then use the posted pack and make sure to partition your HDD GUID/GPT and format your target partition "Mac OS X Extended (journaled)". It's just the basics, there really is no difficulty whatsoever installing Yos on the D630 nVidia. I really thought I had written an idiot's guide, so guys, please read it with all due attention.
-
If you could post better specs, we might be able to give suitable advice. Intel Pentium B950 appears to be a 64bit CPU, so that's Ok for Mavericks (or any Lion, ML or Yosemite installation to that effect). http://ark.intel.com/fr/products/55627/Intel-Pentium-Processor-B950-2M-Cache-2_10-GHz The CPU also appears to have Intel HD graphics, though I can't say if that is 1st gen Intel HD or not. Assuming it's 1st gen Intel HD like in Arrandale (1st Gen "i" Core CPUs), full graphics support will entirely depends on the cable connector (LVDS vs. eDP). Have a look at the excellent 1st gen. Intel HD graphics thread at InsanelyMac. For the rest, you need to read up on general Hackintoshing matters, from USB installer creation to actual installation. In your case, I'd recommend you use the recommended myHack-based method, as documented in our EDP pages (click in EDP button at top of forum/web page).
-
You won't gain improved GPU performance with a DSDT edit if you already have full graphics acceleration! It's AGPM and profile tuning you need sorted. Read the associated thread for the D6xx and follow the same principles.
-
Guys, reset your BIOS to default settings and set HDD mode to AHCI.
-
You would not need that PCI root parameter setting unless the UID of Device PCI0 was set to 4 in the default DSDT and, afaik, I don't believe this is the case on the Vostro 200 and/or the Inspiron 530s. You should only need option GE=Yes with a GeForce G210.
-
Follow the guide and use posted pack.
-
If you refer to my guide, consider that the work was suspended because my HDD crashed and never replaced to date (too many computers at home...). However, you can perfectly install and run Yosemite on the Vostro 200 using good old Chameleon (use version r2401, it works perfectly). Use the same installation procedure as those listed in my other guides (Latitude D630, E6220, E6440, etc.). Use the bootpack I posted for Mavericks but bear in mind that some kexts will not work from /E/E, only from /S/L/E; the Voodoo audio kexts for instance. But FakeSMC and keyboard/mouse kexts will load from /E/E. You can experiment and adjust as required.
-
Please, no jumping on a thread related to one particular machine for another. It defeats the purpose of clarity and information retrieval. Now, unless the Vostro220 has the exact same specs and BIOS (because of DSDT) as the Vostro200, the bootpack won't apply, no. Identify your specs, then try and derive your own bootpack from the existing Hackintosh literature. If you find that there are common components (say LAN card for instance), then you may reuse the associated kexts. But I'm pretty sure the Vostro 200 DSDT won't work on the Vostro 220. These are not models that came out at the same time unlike the Vostro 200 and the Precision 530/530s which are very close cousins.
-
Yes, mentioned several times before. Please do a Search on the forum and you'll find Jake's posts on the very matter.
-