Hervé

List of dropped platforms extends to Intel 7th gen. Kaby Lake this year, yet KBL graphics drivers are retained to support ABL graphics (2018 MacBook Air8,1). This is good omen for Kaby Lake platforms of course but especially for Skylake platforms that are able to re-use the same tricks used for Ventura, i.e. fake a KBL iGPU id and call on a KBL framebuffer. At least in this 1st beta version.... Bad news on the wireless front: IO80211FamilyLegacy kext is gone and, with it, native support for Broadcom cards based on BCM4350 and BCM4360 chipsets which includes DW1820A and all those Apple BCM94360xxx that we could use up to Ventura. We'll see if this can somehow be addressed through a patch of some sort. Interestingly enough, support for Broadcom Bluetooth appears to remain untouched, at least as far as the BT module of the Apple BCM94360CS2 card is concerned. Meantime, I called on an old TP-Link TL-WN725N v3 Wireless N Nano USB adapter that I had lying around. It's crap (802.11n 150Mbps) but will do for the moment. It's based on Realtek chipset RTL8188EUS (PCI id 0bda:8179). Other than that, nothing to report after just a brief spell with Sonoma 1st beta. Installation on my Skylake Latitude E7270 was pretty much painless: from Ventura, I updated Clover to r5151 (just in case), updated my add-on kexts to latest versions (Lilu & PlugIns mostly) and, in my Ventura Clover config, changed SMBIOS to MBP15,2 (necessary) and added boot arg -lilubetaall (also necessary). I then rebooted Ventura and launched the Sonoma installation package. Upon completion, I found that LAN, audio and external video outputs worked better if I used the combined boot args -lilubeta -wegbeta -alcbeta instead of single boot arg -lilubetaall. NB: Sonoma boots/works the same way if, instead of SMBIOS MBP15,2, I boot it with SMBIOS MBP13,1/MBP14,1 and add -no_compat_check boot arg. Avoid MBP15,1 on Skylake laptops, it prevents external video outputs for instance. Working: graphics acceleration with same KBL settings as in Ventura brightness control HDMI output mini-DP output touchscreen audio (incl. DP/HDMI audio) LAN Apple (Broadcom) BCM94360CS2 Bluetooth but a bit erratic at times (on startup and after wake) touchPad USB ports sleep wake but troublesome if hibernation is disabled so it's best to leave things untouched for the moment SD card reader Not working: Apple (Broadcom) BCM94360CS2 wireless

I've read the same at InsanelyMac. It's a beta version so who knows? Start by checking your video settings against the CML recommended settings in the WEG user manual. https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md#intel-uhd-graphics-610-655-coffee-lake-and-comet-lake-processors For instance, you chose to opt for CFL layout 0x3EA50004 when the recommended frame buffer for laptops is 0x3EA50009. Then there is the question of why you chose the connectors patches you apply: you patch con0, con1 and con2 with their vanilla values which is totally and utterly useless. It does no harm of course... Then you apply a stolenmem patch with value 0x01E00000, i.e. 30MB. If we add that to the fbmem patch you apply, i.e. 9MB, you're above the 32MB value often set for DVMT. If the laptop boots without KP with those settings, remove those 2 patches as they're clearly not required. The laptop's DVMT must be set to 64MB or more. UHD 630 iGPU of Intel i7-10510u carries ids 0x9B41/0x9BCC. As stated in the WEG user manual, macOS's CFL drivers support CML ids 0x9BC4, 0x9BC5 and 0x9BC8. Did you try those before faking CFL id 0x3EA5? As a reminder: ID: 3EA50004, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00E30B0A TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes) Model name: Intel Iris Plus Graphics 655 Camellia: CamelliaV3 (3), Freq: 0 Hz, FreqMax: 0 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000498 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000003C7 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP 00000800 02000000 98040000 01050900 00040000 C7030000 02040A00 00040000 C7030000 ID: 3EA50009, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00830B0A TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes) Model name: Intel HD Graphics CFL CRB Camellia: CamelliaV3 (3), Freq: 0 Hz, FreqMax: 0 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000001C7 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000001C7 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 C7010000 02040A00 00040000 C7010000 If you want a fully working system, maybe you should run 13.4 instead...

You may of course update to 10.6.8, it's totally safe. DW1395 is not natively supported and needs a Broadcom patched kext (or a kext patch) as indicated in the Wireless cards inventory for which I gave you a link earlier. You should find it on the forum through a search but here it goes... Broadcom43XXFamilyrev2.kext.zip Unzip the kext and place it in your /Extra/Extensions folder, then run myHack->myFix and reboot. You'll then have working wireless.

That's where you get it wrong. To apply the bootpack, you have to run myHack and load/apply it with myHack, it's one of the option in the pop-down menu (called "Install Extra" from memory). Copying/pasting it to the USB key won't do. Please note that T7250 is a little Merom CPU running at 2.0GHz and fitted with only 2MB L2 cache. Performance won't be great, even more so if you run off a mechanical HDD, whether 5400rpm or, preferably, 7200rpm.

As I said, 10.6.7 is no good, forget it. Only use 10.6(.0), 10.6.3 or 10.6.8. All the packs I posted all those years ago were tested like a million times so rest assured they're bullet proof. It must be something you do incorrectly with myHack. Remember that it's a 2 step process where you 1st build your USB installer, then add the bootpack to the USB installer. Do not miss that 2nd step. You still haven't replied: what CPU do you have in that D630?

Re: Snow Leopard, you can only use Retail versions to install it. All the others are recovery versions that lack the complete set of installation files and can only by used on real Mac computers but not for installation on a Hackintosh. There are only 3 retail versions: 10.6(.0), 10.6.3 and 10.6.8. It's not difficult to find one of those on the Net to be honest, mostly 10.6.3 with which my bootpack works and you'll be able to update straight to 10.6.8 thereafter. Lion (and Mountain Lion) is a different story since Apple released 10.7.5 for free only a couple of years ago. See here.

Just verified the bootpack and all is Ok afaik. Try and boot Chameleon with boot args -f -v. Just press a key when you see the initial Chameleon boot screen to obtain the prompt and type the boot args before pressing [ENTER]. Former arg will ensure you boot without cache.

Which pack did you use? What CPU do you have in your D630 (it'll show in BIOS settings)? What's the version of Snow Leopard you're installing? It probably ain't 10.6.8 but 10.6(.0) or 10.6.3.

Did you use myHack v3.1.2 as posted here? And the relevant Snow Leopard bootpack as posted here? Did you set your BIOS settings as posted here? What wireless card do you have inside your D630? If Intel 3945, remove it and replace it by a supported model as listed here. NB: you can't use myHack on any OS X/macOS version past Mavericks. Conti never updated it afterwards and got out of the Hackintosh scene.

You'd need a very old 32bit Clover version if you can find a suitable copy somewhere. Don't go re-inventing the wheel for such a totally obsolete laptop, just use myHack and the Snow Leopard bootpacks we posted years ago. But keep in mind that you won't be able to do much with Snow Leopard on a D630 in 2023. You won't even be able to browse the web properly because the browsers are so old. If you really want to run something decent on a D630, you have to use a model fitted with a Penryn CPU and the nVidia NVS 135M dGPU. The GMA version are good for nothing today as far as Hackintoshing is concerned.

i5-6200U CPU with HD520 graphics is not an issue per sé but Ventura has no native support for Skylake iGPUs. Make sure you follow the available documentation and use Kaby Lake KBL graphics settings + SMBIOS. Look at our archived Ventura beta threads if necessary.

ALC3235 = ALC293 (PCI id 10ec:0293). See the AppleALC wiki. All you need are: Lilu kext (which you should already have) its AppleALC PlugIn audio layout id 11 injected against the audio HDEF device (normally located @1F,3) in your bootloader's config. This will support built-in speakers + combo jack socket. HDMI audio will be supported if you inject HDMI type (i.e. 00080000) against connector con1 of the IGPU device (located @2).

Not beginner friendly? Those are complete step-by-step guides! And Clover is anything but obsolete by the way. Clover or OpenCore, it does not matter, you need to download the macOS installation app one way or another. This does not require to have a Mac if you care to search a little but, yes, those guides are geared towards users with access to a macOS platform (Mac, Hackintosh or VM). If you believe things are different with OpenCore, you're up for a surprise... I suggest you start by doing the minimum homework required. If you're looking for a method to build a USB installer from, say, Windows, I also suggest you use the forum Search facility and/or check our FAQ section. A vanilla installation requires an installation app of some sort, a bootloader and the appropriate bootpack (aka "EFI") for the target computer. In case you completely missed it, do consult the Dortania online documentation that provides complete guidance re: building an OpenCore-based USB installer. You may then apply the OpenCore bootpack posted in JakeLo's OpenCore guide so that you can properly boot the USB installer on your E7270 laptop. If you expect to find a ready-made bootable image that you'll simply restore on a bootable media, I'm afraid you won't find anything of the sort here.

Afaik, it was never fixed. OP ended up using a USB-C (DP)-to-HDMI adapter. I you need to use the HDMI port directly, you'll have to try and identify the associated connector (con1 or con2) and, probably, patch its characteristics (BusId, type, possibly flags). Vanilla characteristics of CFL framebuffer 0x3EA50009 are posted on p1.

@vanquybn you inject a screen's EDID. Is it that of your screen? Did you find you needed it or else black/corrupt screen?

@vanquybn woaw, what a set of patched ACPI tables! Are you sure you need all of those? Anyway, I'm tempted to say your issue could be related to conflicting ACPI info for your CML UHD630 iGPU. In IOReg, we can clearly see it registers against ACPI device "IGPU" but you inject at least 2 tables that keep referring to ACPI device called "GFX0". If you look at your PNLF device in IOReg, you'll see that its ACPI path refers to "IOACPIPlane:/_SB/PCI0@0/GFX0@20000/PNLF@0": Now, You're gonna say "so does my IGPU device in IOReg": I do things quite differently on my Hackintosh laptops and: rename iGPU device "GFX0" to "IGPU" in my Clover configs; I think you should do the same in your OC config. use a SSDT-PNLF patched table that refers to PCI0.IGPU and PCI0.IGPU.PNLF, not to GFX0 in any way. I think you should do the same in your SSDT-PNLF & SSDT-GFX0 patched tables. Bu I must say that I don't quite understand why you use the latter; it injects stuff you got in your OC config and it probably causes conflicts too. Here's my E7270 IGPU and PNLF IOReg data in comparison: At present, iGPU device appears under the name of IGPU but that's probably just renamed by WhateverGreen. I would suggest you apply the above 2 suggestions and disable that SSDT-GFX0 table of yours. Where did you obtain your OC EFI folder from? Or did you make it yourself?

What system is this? What iGPU? Are you referring to the Precision 7550 listed in your signature? Screenshots are next to useless, what you need to post are zipped copies of bootloader's EFI folder and IOReg. Copy of saved SysInfo always useful too. Also, you mentioned OC boot arguments but forgot to specify them so that's not useful neither. Please be specific if you want proper assistance. Ice Lake video settings would be useless too since they apply ICL platforms with Iris Plus graphics. Comet Lake graphics are fully supported with Coffee Lake (CFL) drivers. For references, I suggest you consult our dedicated thread about supported graphics available in our Technical Info forum section and the WhateverGreen user manual. In all likelyhood, you use incorrect CML settings and/or an unsuitable SSDF-PNLF table. Impossible to say more until you post the required troubleshooting material.

We have and old dedicated guide for brightness keys on these Latitude models. Look it up in our Technical Info->DSDT/SSDT forum section. It's got nothing to do with he version of macOS, it's an ACPI matter. Do think of using the forum Search facility before posting, you'd have found it with a simple search on "brightness keys"...

Great that you got your touchPad working. Removing forbidden link (please read our published rules) and renaming your thread since you're now engaging in sorting out new issues. Re: backlight control, you'll need to add a SSDT-PNLF to your folder for patched ACPI table. Affix, you could not require that ACPIBacklight kext you got in your Clover setup. Re: Bluetooth, it's an Atheros module so I don't believe you'll get that supported under Monterey. Only Broadcom devices are these days... Given that your Wireless card is an Atheros AR9485 model, something that was always fairly poorly supported and not natively so, I recommend you ditch it and replace it by a fully supported Broadcom card, ideally of apple origin. Given that this is an Ivy Bridge laptop, I guess it uses mini-PCIe cards (not NGFF/M.2) so you may want to consider an Apple BCM94360CD on a mini-PCIe adapter. Such card uses the same antenna connectors as regular mini-PCIe cards but it requires 4 antennas (3 for full 5GHz/867Mbps wireless and 1 for Bluetooth). It remains fully and natively supported to this day in current macOS Ventura. See our old dedicated thread on the matter for details.

My apologies, you're absolutely right on both fronts. Too tired, need to take a rest. HD4000 does indeed remain natively supported in Big Sur; just not with Ivy Bridge SMBIOS profile. Limitations of lines in signature does not apply to admin accounts but I've extended it to 5 for regular members. Beyond that, it'd get too big. Remember that you may just stick to the essentials in signature and may detail more than one system per line if you separate them properly.

Clearly the Intel kexts were not going to be of any help for your Broadcom card. I've seen other people reporting similar issues at InsanelyMac but those were using cards based on BCM4352 chipset. It looks like Apple have done changes to Bluetooth again so look or wait for updated Broadcom injector/firmware kexts. Maybe it's time to consider switching to a real Apple Card on an adapter.

You run with the config you used to install Big Sur on this unsupported platform which is using MBP11,1 SMBIOS. Whilst this allows you to keep Big Sur updated, my experience is that it prevents proper CPU power management. You should therefore make a backup of this config (for future use to update Big Sur) and revert SMBIOS to MBP9,2 or MBP10,2 and add boot flag -no_compat_check of course. Also make sure you've disabled hibernation as per the dedicated thread in our FAQ section. You may also have opted for something incorrect when you applied the OCLP patch. But only you can tell us what you did in that respect... NB: There is no limitation to 4 lines for your signature; you must be confusing OSXLatitude with InsanelyMac...

No, the problem is not with your laptop, it is with your USB installer. Until you can describe what you've done and post copies of what you used, no-one will be able to help. I suggest you consult existing threads and guides about the E5440.

How what? You're gonna have to be a little more explicit in your posts...

Seems you have a corrupt USB installer. Re-create it, maybe on a different USB key if you have another one. Use a genuine macOS copy of course (they're free), not a distro...