Hervé

What do you mean by "also installed the AMD7000 kext" ? It's a native kext (in /S/L/E) from ML to Big Sur... Check your card's id against what the native kext supports. If you search the Net, you'll find some people who got it running under macOS by faking id 1002:683d and using AMD framebuffer Futomaki with a patch. So, experiment... https://www.insanelymac.com/forum/topic/334965-amd-firepro-w4100-high-cinebench-r15-opengl-if-first-run-under-windows/ Depending on the macOS version you run on your old and unsupported MacPro, you may want to consider a more compatible graphics card. https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/amd-gpu.html#hd-7000-series-7xxx https://www.techpowerup.com/gpu-specs/firepro-w4100.c2611

I'd say your SMBIOS setup is not complete and incorrect. Make sure to fully complete that part of the configuration process. https://dortania.github.io/OpenCore-Install-Guide/config.plist/kaby-lake.html#platforminfo

-> Moved to Desktop section since this is not a laptop. Please make sure you post in the right section. You probably just re-used a config you grabbed somewhere without knowing what it fully contains nor understanding everything on the matter. All of this is just cosmetic and in no way necessary. If you want to have all those inner hardware elements reflected in your list of PCI devices, you'll have to manually inject the properties through your bootloader config. They are neither automatically nor natively listed and you will have to revisit them one by one. There is no alternative to this.

Indeed, you could try and learn some of the basics of Clover... When at Clover main menu, select your target partition and press [SPACE]. Then use the menu option.

Afaik, you can no longer boot Clover without cache. I expect you'l have to resort to boot in single-use mode to remove your offending kext(s) and manually rebuild your cache with the usual commands (see FAQ section).

Did you actually enable Tap to Click in the TrackPad PefPane? It's disabled by default.

It's not a recent kext; last version is available off Rehabman's repo. You probably already have it. Of course you either use ACPIBatteryBattery (with FakeSMC) or SMCBatteryManager (with VirtualSMC), not both at the same time.

Did you install CodecCommander kext in /L/E to cache it?

What system? What version of OS X/macOS?

Of course SMBIOS MBP9,2/MBP10,2 trigger the unsupported platform error message (it'd be abnormal if it did not); that's why you have to use the -no_compat_check boot arg.

DW1550 is based on BCM4352. Just follow the usual patching process. It's not supported OOB.

@Jorge1964, you need to use a supported wireless card. Please refer to our FAQ and R&D->Wireless section where you'll see references of supported models. Yours is not, as long been indicated in our published inventories and needs to be replaced.

Start afresh bu following Dortania's guide for Comet Lake laptops: https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/coffee-lake-plus.html

Try the darwake boot arg, with its various values: darkwake=no/0/1/2/3/4/8/10

It'd be nice to consult the guides posted here to begin with.

Look up my E7250 guide and grab the PS2 controller kext from there. It's good old DrHurt's R6 for Alps hardware and it works perfectly on the E7x50 without the issue you mentioned. Can't see why you'd encounter such issue with wake. Make sure you've got the right CPU power management settings in place and hibernation disable (see our FAQ section if necessary). Of course, no kext or anything specific for Sleep & Wake apart from disabling hibernation. Lastly, configure your BIOS parameters as per the posted recommended settings. That about all we can say in the absence of any troubleshooting/debugging material from your part.

E5430 is Ivy Bridge, quite similar to E6x30 laptops. SMBIOS MacBookPro9,2 or MacBookPro10,2 required. I’d be surprised if we did not have existing boot packs somewhere on the forum.

Basic macOS functionalities... Use your Keyboard PrefPane to swap keys (like Option & Command).

What have you tried and achieved so far?

I don't recall ever creating a patched DSDT for an E6430; if you're using my E6230's patched DSDT on an E6430, don't be surprised to encounter issues. We've never recommended nor advocated using any given patched DSDT on a different computer model...

Try an post an IOReg when you boot your PixelBook with an inappropriate framebuffer value.

You're only seeing 8MB VRAM because you still do not have full graphics acceleration. Once you've sussed out the correct settings, VRAM will be automatically set to something like 1536MB. Post a zipped copy of your EFI folder.

iGPU device-id and framebuffer platform-id are 2 x seperate things and you do not derive latter from former. See WEG's manual.

Unless I'm mistaken, I saw iMac18,1 SMBIOS in your config file. That would obviously be quite wrong given that this was a Kaby Lake desktop Mac (granted it was fitted with i5-7360U mobile CPU) with Intel Iris Plus 640 graphics. What you really ought to use is MacBook10,1 SMBIOS, i.e. the profile of those mid-2017 last little MacBooks fitted with similar CPUs (i5-7Y54 & i7-7Y75) and Intel HD615 graphics. Regarding graphics, I believe you should use KBL framebuffer id 0x591e0000 or 0x591e0001, specified in reverse byte order. In your OC (or Clover) config, you'd therefore inject these as follows: AAPL,ig-platform-id 00001E59 DATA or AAPL,ig-platform-id 01001E59 DATA This is what is recommended as per Clover's and WEG's own documentation: https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md ID: 591E0000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000078B 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: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00040000 87010000 ID: 591E0001, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x002B0702 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 615 Camellia: CamelliaV2 (2), 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: 0x00000181 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000181 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 81010000 02040A00 00040000 81010000 If not, well, you'd have to experiment with other KBL framebuffer ids.

Congratulations. Now read what's written on the label (concentrate your attention on the top right corner) and head over to our Technical Info->Wifi forum section. Thank you.