Hervé

Hassle? What hassle?

Can't see why you'd have much trouble trying to install and run Sequoia beta on your E5470 or on a E7470.

No support for legacy Broadcom wireless cards for the moment. See our other dedicated thread on the matter.

Released June 24th, 2024.

Build 24A5279h.

 

Available through OTA with @Lorys89's version of RestrictEvents v1.1.4 of June 2024 as long as your Apple account is registered for beta updates. RestrictEvents.kext.zip

Failing that, install assistant package is available here.

 

 

Straight update; a bit long to complete. No changes to bootpack used for beta 1.

 

 

Just adapt any/your Sonoma build; it does not require much changes. See my "early feedback" thread where I've detailed things for my Skylake/HD520 E7270.

Updated for 2024.

Updated following release of macOS Sequoia 1st beta.

It should come as no surprise that the same issue that initially affected legacy Broadcom cards in macOS Sonoma now applies to freshly released macOS Sequoia beta. The OCLP tool will need to be updated for Sequoia.

Restoring support for dropped GPUs in macOS Sequoia.

 

It's early days but Sequoia 1st beta did not drop additional GPUs. As such, the same patches that applied to Ventura and Sonoma can be expected to apply to Sequoia. OCLP will require to be updated for macOS 15.

 

Meantime, for Skylake iGPUs, the same good old patches apply to obtain full graphics acceleration in Sequoia beta, i.e. fake KBL graphics.

-> moved to Sequoia beta section.

 

For your touchpad, if you use VoodooPS2Controller kext, you need to replace its VoodooInput plugin by 1Revenger1's version 1.1.5. See my "early feedback and findings" thread pinned in this very section.

List of dropped platforms only extends to Intel 8th gen. Amber Lake MacBookAir8,1 this year, all other platforms officially supported by Sonoma remaining supported in Sequoia.

 

Good news for Skylake platforms: since KBL graphics drivers are retained, SKL graphics remain supported through the same patches used for Ventura and Sonoma. On the wireless front, OCLP patcher will need to be updated for Sequoia so that legacy Broadcom cards are supported again.

 

Other than that, nothing much to report after just a brief spell with Sequoia 1st beta other than it feels a little more responsive than Sonoma and there are odd bugs (for example, an empty white window that may pop up at startup and cannot be closed or occasional mouse selection trailings).

 

Installation on my Skylake Latitude E7270 was very straightforward and totally painless: from Sonoma, I updated Clover to r5159 (revised to boot Sequoia), changed my Clover config's SMBIOS to MBP15,2 (necessary), disabled the BlockSkywalk kernel & kext patch (necessary) and added boot arg -lilubetaall (also necessary). I then rebooted Sonoma, downloaded the Sequoia beta installation package and launched the installation targeting a dedicated Sequoia volume (previously created in Disk Utility). That was it, after a couple of reboots, I was offered the Sequoia setup screens and was presented with the Sequoia desktop.

 

Resources:

• Sequoia beta 1 installation package can be downloaded here.
• Clover_r5159.pkg.zip
• E7270_Clover_pack_Seq_15.0.b1.zip

 

Working:

• graphics acceleration with same KBL settings as in Ventura/Sonoma
• brightness control
• HDMI output
• mini-DP output
• touchscreen
• touchpad (after replacing VoodooPS2Controller's PlugIn "VoodooInput" by 1Revenger1's version v1.1.5 due to changes in Sequoia as explained here. 1Revenger1_VoodooInput_v1.1.5.zip) 
• audio (incl. DP/HDMI audio)
• LAN
• Apple (Broadcom) BCM94360CS2 Bluetooth
• USB ports
• SD card reader
• full CPU power management
• sleep & wake (having disabled hibernation)

Not working:

• Apple (Broadcom) BCM94360CS2 wireless, as per Sonoma. We'll have to wait for the OCLP patcher to be updated for Sequoia. Meantime, it's important not to boot with the BlockSkywalk kernel & kext patch and/or with AMFI prevention or Sequoia will KP/fail to boot.

 

 

 

 

 

 

 

 

Things looking different in System Information->Software->Extensions: injected kexts are listed and everything is listed as loaded.

 

WWDC Keynote, June 10th, 2024.

Apple unveiled macOS 15 Sequoia.

As usual, 1st beta version was immediately made available to developers and 1st public beta will be available in July with a final release in the fall.

 

 

Very little in terms of (exciting) new features in Craig's presentation, apart from iPhone mirroring.

 

 

Surprisingly, Sequoia only drops support for 2018/2019 8th gen. Amber Lake MacBookAir8,1/8,2 thereby raising the minimum MacBook Air platform to final 2020 Ice Lake-based MBA9,1. The rest of the supported platforms remain identical to Sonoma so we can kind of thank Apple for the reprieve. Who knows whether Apple will chop it all next year or retain only 10th gen. Comet Lake/Ice Lake models next year in Sequoia's successor?

 

KBL graphics driver remain provided so that'll be good news to all owners of Skylake laptops who should all be able to run Sequoia with full acceleration through the SKL graphics patch required since Ventura.

 

Minimum platform requirements are therefore:

• iMac19,x (8th gen. Coffee Lake)
• iMacPro1,1 (Skylake Xeon)
• MacBookAir9,1 (10th gen. Ice Lake)
• MacBookPro15,x (8th gen. Coffee Lake)
• Macmini8,1 (8th gen Coffee Lake)
• MacPro7,1 (Cacade Lake)

View full article

12 hours ago, scram69 said:

[...]

It is not clear to me how to accomplish disabling RTC Memory Lock: "setup_var PchSetup 0x16 00 (RTC Memory Lock ->Disabled)"

Where do you enter this command?

[...]

You need to identify where the RTC memory lock variable/parameter is set in BIOS. You may use a BIOS inspection tool to do this and a tool like ModGrubShell or your bootloader shell (eg: Clover's) to change the parameter value once you've identified it. It should be similar to what is done to adjust DVMT size in BIOS. See here and/or here for pointers.

No, absolutely no support for VGA output with HD4000 graphics on the Ivy Bridge E6x30 series since early Mountain Lion versions. See here or here. You would have to use an active HDMI-to-VGA adapter for your VGA-only external screen (passive won't work).

BIOS setting maybe?

What do you have configured in terms of, say, USB Wake Support or Legacy ROM?

If you guys have Wake on USB/USB Wake Support (whatever this may be called) enabled inBIOS, disable it. It's known to cause immediate wake on sleep when mains are plugged in.

-> Moved to E7xxx support section. Nothing to do in the Lobby section.

Simply apply your patch under the condition of booting/running Mac OS X/OS X/macOS, i.e.:

If (_OSI ("Darwin"))
{
    // your patch here
}

or

If (_OSI ("Darwin"))
{
    // your patch here
}
Else
{
    // original ACPI code
}

 

Released May 13th, 2024.

Build 23F79

 

Enhancements, bug fixes ans security updates. Safe to install on our Hackintosh platforms.

No changes compared to Sonoma 14.4 (see dedicated update article), i.e. no kexts update for wireless services required this time.

 

Also released at the same time:

• macOS Ventura Security Update 13.6.7 (Build 22G720)
• macOS Monterey Security Update 12.7.5 (Build 21H1222)

View full article

Sorry, I've no idea what you did. You're gonna have to be a lot more specific. You've not even specified what you use in terms of bootloaders.

See here and use the latest versions of the kexts mentioned in the thread:

https://osxlatitude.com/forums/topic/13140-solved-dw1560-bluetooth-stopped-working

The GPU...

If you want to consider a suitable build with SSDTs only, I suggest you post the raw/vanilla DSDT extracted from BIOS and the patched one. We'll then be able to examine the differences between them and suggest SSDT alternatives to the patched DSDT.

I wouldn't bother to try and use OpenCore or follow the Dortania guidance for an old C2D laptop. OpenCore has no proper support for CPU power management on these platforms. Stick to Clover, knowing that using SSDTs only is not restricted to OpenCore at all and can of course be used with other bootloaders such as Clover.

It's just a matter of framebuffer and matching of connectors with physical outputs. On rare occasions, certain outputs may not work at all. Patching the HDMI port to type 00080000 is only required to gain HDMI output, it's not required for video output.

 

All I can suggest is that you experiment with the various CFL/CML framebuffers and check them all out for HDMI output.

That's entirely cosmetic and bears no influence on your Hackintosh. Furthermore, it probably only appears in an add-on application such as About this Hack. If you want the proper CPU model to be reported, inject its CPUID in your OC config.

Seems your HP 400 G6 is fitted with a Comet Lake CPU given that the reported iGPU id is 0x9BC8.

 

It's a desktop platform, yet you use mobile framebuffer 0x3E9B0000 which natively defines the following 3 ports:

[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
00000800 02000000 98000000
01050900 00040000 87010000
02040A00 00040000 87010000

This is not suitable given that 1st output port (i.e. connector con0) is defines as an LVDS port.

DP output appears to attach to 2nd connector con1 in your IOReg.

 

I would suggest you opt for the desktop framebuffer recommended in the WEG user Manuel, i.e. 0x3E9B0007 which defines the following 3 ports:

[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
[3] busId: 0x06, pipe: 8, type: 0x00000400, flags: 0x000003C7 - ConnectorDP
01050900 00040000 C7030000
02040A00 00040000 C7030000
03060800 00040000 C7030000

This should give you a better chance to obtain DP + HDMI output. If you do, identify which connector is DP and which connector is HDMI so that you may patch the HDMI one accordingly (i.e. set its type to 00080000) should you wish to enjoy HDMI audio.

 

You may also want to switch SMBIOS from iMac20,1 to MacMini8,1.