Hervé

I'd say the bootpack is totally inadequate for old Lion. I suggest/recommend you look up old threads with bootpacks for old and obsolete GMA950 computers. I doubt lilu & its PlugIns are of any use in Lion for old GMA950 graphics. SSDT-EC, that's for Catalina & later... Lion needs replacement of AppleACPIPlatform kext by that of Snow Leopard's origin or you'll get a KP. I expect you'll also need the patched AppleRTC kext and you may need the patch Intel (GMA) framebuffer kext to fix a brightness issue that used to affect most GMA950 Hacks. Lion need to boot in 32bit kernel mode or you won't have graphics acceleration but you know that and did setup OC in i386 kernel mode. I'd forget OpenCore and use good old Chameleon with myHack tool to make your USB installer. You're the one who published a version that was modified to run on macOS versions. Put an old AMD HD2000/3000/4000/5000/6000 series or nVidia Tesla series PCIe graphics card in this old desktop and you should be able to run OS X El Capitan. You may not do much with El Capitan but you sure won't do anything with Lion which is totally deprecated/obsolete.

IOReg with HDMI plugged in please. I take it you do reset NVRAM when you reboot after changing your config, right?

Then you may want to retry without the fbmem/stolenmem injections. You never know, your laptop may be set with 64MB or more of DVMT. Do that with a USB key as you don't want to break your Hack.

Again, I recommend you remove all that crap you've got for the connectors and stick to the 2 lines I posted above. At this stage, your HDMI screen does not even appear in IOReg which can't be a surprise. For the rest, it would appear you followed the Dortania recommendations, at least as far as the OC configs concerned.

The graphics properties you inject look overly complicated to me; I'd be surprised if you need more than a third of them. You've opted for CFL framebuffer 0x3E9B0000: ID: 3E9B0000, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000130B 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: CamelliaDisabled (0), 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: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00040000 87010000 It's not the recommended framebuffer for laptops, the default (recommended?) one in the WEG user manual being 0x3EA50009: 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 Maybe you can explain why: you opted for framebuffer 3E9B0000 you patch con1 in such a way you patch con2 in such a way you inject con3 properties in a framebuffer that has no such connector (and in which you do not even add this connector hence nothing in IOReg!) Personally, I'd have just changed connector con1 type to HDMI: framebuffer-con1-enable framebuffer-con1-type 00080000 so I recommend you start by removing all the non-sense you currently have for con1, con2 and con3. Note that injecting properties that bear the save values as the native ones is completely useless; though it does no harm of course, other than complicate a lot more your configuration. You also need to remove boot arg -igfxsklaskbl from your NVRAM settings; that's completely inadequate. It's for Skylake laptops and for an older version of macOS under very specific conditions. A total non-sense on your 10th gen (CML?) platform with UHD620 iGPU. It would be useful if you could specify the exact model of i7 CPU fitted in your ThinkPad x390. And if you have doubt about the connector linked to the HDMI output, please take an IOReg when your HDMI screen is connected to your laptop.

Updated for macOS Sequoia.

Did it work OOB or with an add-on driver in Sonoma?

Answers available in our Hardware Technical Information section. Do search the forum/consult these sections before posting. https://osxlatitude.com/forums/topic/2998-platforms-compatibility-requirements-for-os-xmacos https://osxlatitude.com/forums/topic/8238-supportedunsupported-gpus-graphics-cards Not really worth the effort and time you'll have to put in it but if you really want to try and install one of those totally obsolete OS X versions (with which you won't do much) on your P4 dinosaur, the best you can hope for is Leopard. Don't expect much support if you require assistance, Tiger and Leopard are just too old and you'll have trouble finding people who know about it now. I very much doubt that your 22 years old AGP Rage6 ATI Radeon 345M will be supported but you never know... You can always check the device ids of the oldest supported ATI/AMD platforms in the relevant drivers of Leopard combo update to begin with. I expect it would be old ATIRadeon.kext. Your GPU id should be 1002:4337. You may also consult everymac.com and look for very ancient pre-Intel Apple Mac computers that may have been fitted with GPUs of that generation/family/architecture and the latest OS X version that supports them (probably Tiger 10.4.11) but know that the oldest 2006 Intel MacBook/MacBook Pro/iMac were fitted with Intel GMA950 and ATI X1600 GPUs.

Sorry that injecting EDID value did not work. You could also try experimenting with a different KBL frame buffer; like 0x59160000 or 0x591b0000.

Yes, that's what I was expecting. Your graphics config looks spot on. If you inspect the screen's EDID information, you will notice that the reported data differs between HDMI output and USB-c Dock output: HDMI: <00 ff ff ff ff ff ff 00 05 e3 78 27 d7 00 00 00 09 1b 01 03 80 3c 22 78 2a a5 95 a6 56 50 a0 26 0d 50 54 bf ef 00 d1 c0 b3 00 95 00 81 80 81 40 81 c0 01 01 01 01 56 5e 00 a0 a0 a0 29 50 30 20 35 00 55 50 21 00 00 1e 00 00 00 fd 00 32 4c 1e 63 1e 00 0a 20 20 20 20 20 20 00 00 00 fc 00 32 37 37 38 58 0a 20 20 20 20 20 20 20 00 00 00 ff 00 47 4a 4c 48 33 48 41 30 30 30 32 31 35 01 fc 02 03 1e f1 4b 10 1f 05 14 04 13 03 12 02 11 01 23 09 07 07 83 01 00 00 65 03 0c 00 10 00 02 3a 80 18 71 38 2d 40 58 2c 45 00 55 50 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 55 50 21 00 00 18 8c 0a d0 90 20 40 31 20 0c 40 55 00 55 50 21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6d> Dock (both): <00 ff ff ff ff ff ff 00 05 e3 90 27 64 1f 00 00 34 1c 01 04 a5 3c 22 78 3a 48 15 a7 56 52 9c 27 0f 50 54 bf ef 00 d1 c0 b3 00 95 00 81 80 81 40 81 c0 01 01 01 01 56 5e 00 a0 a0 a0 29 50 30 20 35 00 55 50 21 00 00 1e 00 00 00 fd 00 32 4c 1e 63 1e 01 0a 20 20 20 20 20 20 00 00 00 fc 00 51 32 37 39 30 0a 20 20 20 20 20 20 20 00 00 00 ff 00 47 51 4d 4a 43 48 41 30 30 38 30 33 36 01 9a 02 03 1e f1 4b 01 03 05 14 04 13 1f 12 02 11 90 23 09 07 07 83 01 00 00 65 03 0c 00 10 00 02 3a 80 18 71 38 2d 40 58 2c 45 00 55 50 21 00 00 1e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 55 50 21 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 55 50 21 00 00 18 8c 0a d0 90 20 40 31 20 0c 40 55 00 55 50 21 00 00 18 f0 3c 00 d0 51 a0 35 50 60 88 3a 00 55 50 21 00 00 1c 00 00 00 00 00 00 00 77> I would suggest you try and inject the HDMI EDID value as additional property in your graphics configuration. Target AAPL02,override-no-connect since this external screen should be 2nd display out of FB@2 and specify the EDID value as DATA type without any space between the bytes. Refer to the Whatevergreen user manual if need be. Can't remember if the AAPL0x unit digit must match the connector's number. You'll be able to check that out in IOReg after reboot (under FB@2->display->AppleDisplay). Can't be AAPL00 for sure as that would be your built-in screen. You may also try to patch connector con2 to HDMI type as per connector con1 though I'm not convinced this will take effect and change anything.

'tempted to say it's a likely EDID issue but you opted to post screenshots of your IOREg rather the IOReg themselves as asked.

Sonoma dropped support for all remaining Broadcom "legacy" cards that were supported up to Ventura, this including those based on BCM4360 chipset family. See our 2023 home page articles + Articles/News/Tech/Our Picks threads + Wireless cards inventory about this. https://osxlatitude.com/forums/topic/18228-macos-sonoma-140-beta-1-early-feedback-and-findings https://osxlatitude.com/forums/topic/19519-macos-sonoma-is-out https://osxlatitude.com/forums/topic/20369-support-for-broadcom-wireless-cards-in-sonoma-later-clover-and-opencore https://osxlatitude.com/forums/topic/19730-wifi-in-sonomasequoia-patching-for-legacy-broadcom-wireless-cards/ https://osxlatitude.com/forums/topic/11138-inventory-of-supportedunsupported-wireless-cards-2-sierra-ventura-beyond Forum offers a search facility in top right corner, don't hesitate to use it before posting as stated in our posted rules. Thank you.

Seems more to be an issue with the USB-c output. Post an IOReg with Dock plugged in and screen set to 1080p + screen set to 1440p.