Hervé

I already did and was a little scared...

Which Enoch version are you using? r2889? You've configured Enoch with boot parameter KernelBooter_kexts set to Yes but there is no Extensions folder with kexts inside your /Extra folder. You'll never inject kexts in that way. KernelBooter_kexts operates without cache so kexts placed in /L/E will be ignored. Where are your add-on kexts? You stated you used iMac17 SMBIOS, but that's only with Clover. Your /Extra folder shows MacBook9,1 SMBIOS (which I think is perfectly Ok if you have a laptop)... It would help if you would specify your exact Dell model and its hardware specs.

No. https://osxlatitude.com/index.php?/topic/9908-help-tuning-required-for-dell-inspiron-7548/page-3&do=findComment&comment=70944

Use the null (dummy) Ethernet kext. You can Google for it.

Nothing, you just have to repeat the touch + kextcache commands when you get that. But it seems you're missing the dummy ALC292 kext... It's available here in the bootpack and the ALC292 patch details are listed too. I'm using layout-id 1 on my E6440 (see post #7 of the thread). Audio kexts cannot be injected, they have to be cached if you want Clover on-the-fly patches to work Ok.

ALC3226 = ALC292. AppleHDA patching details are available off my E6440 guide if you want.

Last update: 18 Jan 2021 Specifications: BIOS v1.20 v1.70 with disk set to AHCI mode Intel Haswell-ULT Lynx Point LP (8 Series) chipset Intel dual-core Haswell-ULT i5-4210U @1.70GHz CPU (Turbo boost to 2.40GHz (2cores) or 2.70GHz (1core)) Integrated Intel HD4400 GPU 200MHz/1.00GHz (PCI ven id 0x8086, dev id 0x0a16) 15.6" 1366x768 WLED LCD 8Go DDR3L-1600 RAM Realtek RTL8168/8111 Gigabit Ethernet (PCI ven id 0x10ec, dev id 0x8168) Realtek ALC255 High-Definition audio (PCI ven id 0x10ec, dev id 0x0255) Realtek (internal-USB) RTS5129 SD card reader (PCI ven id 0x0bda, dev id 0x0129) Chicony Electronics (internal-USB) webcam HD (PCI ven id 0x04f2, dev id 0xb446) Intel Wireless-AC 3160NGW combo Wifi/Bluetooth card -> ideally replaced by a fully compatible card/USB adapter Alps V8 touchpad 2 x USB 3.0 ports (right side) 1 x USB 2.0 port (left side) 1 x VGA output 1 x HDMI output 1 x combo microphone/headphones jack port NB: No additional expansion slots inside that low-spec laptop other than the M.2 slot for wireless card. 2 x DIMM slots for RAM. Toshiba:~ admin$ lspci -nn pcilib: 0000:00:02.0 64-bit device address ignored. 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 0b) 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller [8086:0a0c] (rev 0b) 00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC [8086:9c31] (rev 04) 00:16.0 Communication controller [0780]: Intel Corporation 8 Series HECI #0 [8086:9c3a] (rev 04) 00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio Controller [8086:9c20] (rev 04) 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 4 [8086:9c16] (rev e4) 00:1c.1 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 3 [8086:9c14] (rev e4) 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series USB EHCI #1 [8086:9c26] (rev 04) 00:1f.0 ISA bridge [0601]: Intel Corporation 8 Series LPC Controller [8086:9c43] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series SMBus Controller [8086:9c22] (rev 04) 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10) 02:00.0 Network controller [0280]: Intel Corporation Wireless 3160 [8086:08b3] (rev cb) Toshiba:~ admin$ USB2 (EHC1) controller 8086:9c26 is only available when BIOS is in CSM (i.e. legacy) mode as shown above. In UEFI mode (required for OpenCore/Big Sur for instance), only the USB3 (XHC) controller 8086:9c31 is available. This does not affect ports operation in USB mode but does prevent detection/operation of Bluetooth module of combo wireless card.

1st screen defect (at Apple logo) is perfectly normal until you apply the IOGraphicsFamily patch. For the 2nd screen defect, with a resolution > 1600x900, you need to set DualLink to 1 in your Clover config. NB: Are you sure you have HD4000 graphics on an E5540? I'd have thought that was a Haswell platform with HD4200/4400/4600 graphics...

https://github.com/Piker-Alpha/ssdtPRGen.sh

E6220 only supports legacy mode as far as I know. Which method are you using: Clover-based method or Enoch-based method?

You should be able to identify the exact Broadcom card through DPCIManager app (Google for it) or by looking directly at the card once you remove the bottom plate. Then look up here and/or in the wireless forum sub-section. For audio, look up the Info page in your BIOS settings. Probably IDT 92HD93, in which case, it'll be same as E6x30 and you can re-use the same IDT dummy kext + AppleHDA patches. Details available here with dummy kext in the bootpack.

No need to re-install macOS at all. If version A02 is not available then go for A03 indeed (i.e. the oldest version available off Dell's web site) before re-upgrading to A12.

Revert to BIOS A02 to begin with, then to BIOS A12.

All my laptops run in BIOS legacy mode, I do not use UEFI, even on my E6220/E6230 or E6440. I don't use iMessage (which indeed needs clover to work) but FaceTime and other apps work perfectly.

You can always disable CoreStorage and revert to traditional disk mode. But I don't think it'll make any difference... More likely to be PWR related patches required in your DSDT.

A very large and regularly-updated set of Apple Macs ACPI/IOReg dumps is available at Applelife.ru here.

Following up on the Yosemite/El Capitan/Recovery/Sierra logos, I made up new High Sierra logos/icons for the Chameleon/Enoch bootloader so that High Sierra partitions can too enjoy their own icons. Fits nicely along all the other icons. Attached .png files are to be placed in the /Extra/Themes/Default folder. HighSierra_themes_logos.zip HighSierra_themes_logos_2.zip

Moving post to its own thread.

Quick note to confirm that Enoch r2885 boots High Sierra without as much as a cough. http://www.insanelymac.com/forum/topic/231075-chameleon-24svn-official-pkg-installer/page-211?do=findComment&comment=2447091

Please! https://osxlatitude.com/index.php?/topic/8696-is-my-wireless-card-compatible-with-os-x/

You could try CodecCommander kext or EAPDFix kext. NB: no double or multiple posting for the same matter please.

Correct. https://www.intel.com/content/www/us/en/support/graphics-drivers/000005556.html

Did you disable hibernation? You can check status with Terminal command pmset -g. Also check your EnergySaver PrefPane and disable any option that may wake the computer from time to time. Also make sure that BIOS parameters such as Wake on LAN are disabled. Difficult to say anything about your wireless until you specifiy the model of the card you use. No reason why you would not be able to regenerate a CPU PM SSDT but you can re-use the table you used in El Capitan. There's no need to regenerate a new table each time.

As stated in post #1, it's the IO address of the audio device. You'll find it in the DSDT or in IOReg via any explorer tool such as IOJones, IORegistryExplorer, ioreg command line (e.g.: ioreg | grep HDEF) or similar. * DSDT example: Device (HDEF) { Name (_ADR, 0x001B0000) // _ADR: Address [...] }`* IORegistryExplorer example: * command line example: E6230:~ admin$ ioreg | grep HDEF | | +-o HDEF@1B In the above examples, HDEF audio device is found at address 0x001B0000. In the Info.plist file, this will be reflected as follows: [...] <key>HDEFAddress</key><array> <string>1B</string> [...] If the device were at address 0x001F0003, the entry in Info.plist would be: [...] <key>HDEFAddress</key> <array> <string>1F,3</string> [...] Basically, it's written as a single byte (without heading zeroes) or a pair of comma separated bytes (without heading zeroes) if lower byte is not null (0x0000).

'says it all in the D630 thread: For models with Penryn CPUs only - - - - - - Please note that: Sierra requires a Penryn CPU with SSE4 instructions set [...]. Merom CPUs [...] do not have such instructions set and do not allow Sierra installation. - - - - - - As such, as long as your laptops have the required CPUs, you can proceed exactly the same way as for Yosemite and/or El Capitan, adjsting the SMBIOS if necessary.