Hervé

WWDC Keynote, June 9th, 2025. Apple unveiled macOS 26 Tahoe. 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. The major novelty is Liquid Glass that replaces Aqua. And the version numbering, of course, which Apple will now unify across the board (macOS, iOS, etc.). As expected, this is the very last macOS version to support Intel platforms; it will therefore put the final nail in the coffin of Hackintoshing on Intel platforms; after nearly 20 years, it will have been a good run! Tahoe drops all systems older than 9th gen. Coffee Lake, 10th gen. Comet Lake/Ice Lake and CascadeLake platforms, i.e. those 8th gen. Coffee Lake MacMini8,1/MacBookPro15,x/iMac19,x and Skylake iMacPro1,1 that had remained supported in Sequoia. Surprisingly, 10th gen. Ice Lake MacBookAir9,1 laptops appear dropped too but, given that 2020 ICL-based MBP16,2 remain supported, those last Intel MBA should nevertheless be able to run Tahoe too -to be confirmed-. Minimum Intel platform requirements are therefore: iMac20,x (10th gen. Comet Lake) MacBookPro16,1 (9th gen. Coffee Lake) MacBookPro16,2 (10th gen. Ice Lake) MacPro7,1 (Cascade Lake) View full article

Check whether Bluetooth is enabled or not in your BIOS settings. Could be disabled given that the MAC address of your module is not detected. No other Wifi/BT device in your E6440 that could interfere, right?

Hello, it's been some time since I last used a non-Apple Wifi/BT card but I noticed the 2 following elements in your OC config file. You don't inject the Bluetooth injector kext, having limited this to macOS Big Sur (20.9.9). Are you certain you don't need it? The BT chip used on the DW1550 is clearly present in the injector: <key>413c_8143</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport</string> <key>IOClass</key> <string>BroadcomBluetoothHostControllerUSBTransport</string> <key>IOProbeScore</key> <integer>3000</integer> <key>IOProviderClass</key> <string>IOUSBHostDevice</string> <key>idProduct</key> <integer>33091</integer> <key>idVendor</key> <integer>16700</integer> </dict> What does this NVRAM property do?

Released May 12th, 2025. Build 24F74. Bug fixes and security update. Safe to install on our Hackintosh platforms. Also released at the same time: macOS Sonoma Security Update 14.7.6 (Build 23H626) macOS Ventura Security Update 13.7.6 (Build 22H625) View full article

Not a guide! -> moved to support section. A zipped copy of your OpenCore EFI folder with indication of the OpenCore version you use would be useful.

Is the disk visible in BIOS Setup? DU should show all disks, no matter the partitioning/contents. Maybe your SSD has gone faulty and that's what caused the OpenCore error rather than the other way round. I take it that your E6430 is fitted with 2 disks: one in the usual SATA slot and the other in the modular bay, right? If so, maybe you can try to swap them around to check things out. Then, it'll depend on which one carried the bootstrap of course. If I remember correctly, disks fitted into the modular bay required a patch of some sort to be seen in OS X/macOS.

Where is your macOS Ventura partition supposed to be? On the internal disk labelled ST500LM021-1KJM52? What is shown/listed when you select that disk? It would also be most useful if you could list what you did in terms of actions re: "updating OCLP". Was it just the config file you modified or did you update your OpenCore and/or OCLP version?

Released March 31st, 2025. Build 24E248 Bug fixes and security update. Safe to install on our Hackintosh platforms. Also released at the same time: macOS Sonoma Security Update 14.7.5 (Build 23H527) macOS Ventura Security Update 13.7.5 (Build 22H527) View full article

Released January 27th, 2025. Build 24D60. Bug fixes and security update. Safe to install on our Hackintosh platforms. Also released at the same time: macOS Sonoma Security Update 14.7.3 (Build 23H417) macOS Ventura Security Update 13.7.3 (Build 22H417) Subsequently released on February 10th, 2025: macOS Sequoia Security Update 15.3.1 (Build 24D70) macOS Sonoma Security Update 14.7.4 (Build 23H420) macOS Ventura Security Update 13.7.4 (Build 22H420) View full article

Congrats.

That setup suggestion with a SKL setup + dummy framebuffer id then a SKL framebuffer + screen sharing/VNC then OCLP really is most complicated when you can directly opt for a KLB framebuffer + a faked KBL GPU id from the onset. All details have been available for some time in old threads such as this one or this one; in other words, the exact same graphics settings that are to be used since Ventura which dropped official support for SKL graphics. All details available here. In a nutshell, simply use a KBL laptop setup.

Released December 11th, 2024. Build 24C101. Bug fixes and security update. Safe to install on our Hackintosh platforms. Also released at the same time: macOS Sonoma Security Update 14.7.2 (Build 23H311) macOS Ventura Security Update 13.7.2 (Build 22H313) View full article

Not all computers are worthy Hackintoshes...

These cards were always best avoided. https://osxlatitude.com/forums/topic/11138-inventory-of-supportedunsupported-wireless-cards-2-sierra-ventura-beyond

You inject property: disable-external-gpu Does your Thinkpad have a dGPU? If so, HDMI may be wired to it.

https://mounty.app/#FAQs Have you tried contacting the tool's developer or reading the posted comments? I would also suggest that you check if the necessary driver got installed properly and not blocked by Gatekeeper. See our Sequoia beta 3 thread in the archive. You may need to upload a modified profile.

Sorry but I don't understand what you're saying about HDMI. IOReg shows that you most certainly did remove all the unnecessary stuff from your config but no external screen attached to con1 or con2. Were you trying to say that your laptop froze or crashed when you plugged in an HDMI cable/screen? If so, try and patch con1's pipe as follows: framebuffer-con1-pipe 12000000 DATA Re: camera not working, you probably need to remap your USB ports after changing SMBIOS.

I would personally never claim that that every manufacturer provided VGA in the manner you state and they certainly did not convert VGA to something else internally: it's the other way round: digital to analog conversion of the signal. Dell (and obviously some others) have indeed done so from a DP output. If it were the case in your Acer desktop, you'd already have VGA output. But you don't, so... As I said, you could try and bypass AGDP but you may also experiment with various patches of your 1st and/or 3rd connector knowing that port 0 is always LVDS/eDP but "standard" ports 5, 6 and 7 (i.e. connectors with indexes 1, 2 and 3) are used for other types. Of course, you can create your own connectors through various combinations of indexes and BusId. You use KBL FB 0x59120000 in which you simply patch con1/port6 to HDMI type: ID: 59120000, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000110B TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 115 MB, MAX OVERALL: 116 MB (122171392 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 01050900 00040000 87010000 02040A00 00040000 87010000 03060A00 00040000 87010000 To give you a practical example, as described in my initial Ventura beta early findings thread, I use KBL mobile FB 0x5916000 on my SKL Latitude E7270 laptop and just patch con1/port6 to HDMI type in order to obtain HDMI audio. ID: 59160000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00000B0B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 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: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00080000 87010000 KBL FB 0x591B0000 is the default one for laptops, according to the WEG user manual: ID: 591B0000, STOLEN: 38 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000130B TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 136 MB, MAX OVERALL: 137 MB (144191488 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 02040A00 00080000 87010000 03060A00 00040000 87010000 but, if I use it, I get no HDMI output unless I patch con1 to index 1, BusId 5 and pipe 9. DP output works with either port 6 or 7.