Hervé

Dell's DW360 BT module will work OOB. For wireless, all older BCM431x-based cards such as Dell DW1390 / DW1490 / DW1505 or Atheros cards such as AR5B91 / AR5BXB92 / AR5BXB112, etc. will work too. Basically, any card that was supported under Lion and ML will do. https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/

I guess it'll be because the Broadcom & Bluetooth fat-binary kexts from ML DP1 do not support the Broadcom BCM94360CS2 whilst the vanilla 64bit kexts from ML 10.8.5 do... For instance, you'll find 2 x PlugIns of /S/L/E/IO80211Family.kext v5.0 under MLPF'd ML: AirPortBrcm4331.kext (v6.0) AppleAirPortBrcm43224.kext (v5.0) and these don't support any BCM4360 cards (14e4:43a0). Broadcom BCM94360CS2 is supported by AirportBrcm4360 kext and that's an additional PlugIn of the IO80211Family kext of vanilla ML 10.8.5 for instance. It's not present under MLPF'd ML. Little choice but change that card by an older model under 32bit MLPF'd ML, sorry.

You need to replace the IOGraphicsFamily patch in Clover config and enable it. In High Sierra, the patch is: Find: 0100007522 Replace by: 010000EB22 ` Now that you have Optimus enabled again in BIOS, can you post a new IOReg output? 'seems the dGPU would be RP05.PEGP@1C,4...

I would not expect this to be an issue but did you keep the unified display & computer sleep or revert to the separate settings as described here?

You should be able to do this through DSDT/SSDT patching where you basically permanently set the associated ACPI device (usually something like PEG0.PEGP or similar) to off. 1st check in IOReg which device corresponds to your nVidia dGPU which you'll find at address 0x00010000 (iGPU is located at address 0x00020000). Looking at your DSDT and SSDT-5-SaSsdt tables, it certainly appears that: your iGPU is device GFX0 your dGPU is PEG0.PEGP or PEG0.NVID Try this patched DSDT where I have: declared external method _SB.PCI0.PEG0._ON_OFF (defined in above SSDT table) declared a new _INI method to turn the PEG0 device off External (_SB_.PCI0.PEG0._ON_._OFF, MethodObj) // 0 Arguments (from opcode) Method (_INI, 0, NotSerialized) // _INI: Initialize { \_SB.PCI0.PEG0._ON._OFF () } DSDT.aml.zip

It's already up to v4414 anyway... http://www.insanelymac.com/forum/files/file/347-clover-efi-bootloader/ http://www.insanelymac.com/forum/files/file/937-clover-4414/

This old card is not supported beyond ML. All other BCM431x cards were last supported in El Capitan 10.11 and dropped from Sierra 10.12. You'll have to replace your ancient DW1397 with something supported and, ideally, more recent. See our wireless cards inventory published in this very section. You can also revert to your vanilla IO80211Family kext.

It's sudo pmset -a hibernatemode 0not sudo pmset -a hibernate mode 0which won't be accepted. "-a" flag is optional.

If you're talking about generating a SSDT with Pike R Alpha's script, yes, that's always been specifically for CPU power management, nothing else so no hope to be had with that... If anything, you'd have to look at patching the DSDT further or adding a tailored-made SSDT for your MediaBay device. Info posted above states that the MediaBay is accessible depending on SMBIOS. What you can do with that is: experiment with SMBIOS profiles to identify those that provide visibility andor access to your MediaBay drive grab the IOReg + ACPI dumps posted on the web for those Mac models (there's a dedicated thread for this in the OS X/macOS forum subsection) compare those IOReg + DSDT/SSDT files with those of your own E6430

Please consult the FAQ regarding permissions and cache; It's all there, it's a very frequent question, hence the answers in a dedicated thread posted in the Frequently Asked Questions...

You can try and add the usual WWAN patch tuned for the DW5570, either into FakeSMC or in CellPhoneHelper; just not in both... You can refer to the guidance and general principles detailed in this recent High Sierra-related thread: https://osxlatitude.com/index.php?/topic/9560-dw5809e-how-can-i-use-the-wwan/ If it worked for the DW5809e, no reason why it would not work for the DW5570... Original Yosemite patch details remain available here: https://osxlatitude.com/index.php?/topic/8006-sierra-wireless-qmi-modules-mcem73xx77xx8805etc-dell-dw557058085809etc/ I had offered a Sierra patch here: https://osxlatitude.com/index.php?/topic/9403-using-dw5570-under-sierra/ Obviously, setting the card to the correct QMI mode remains fully applicable.

Indeed: Dell Wireless 1810 802.11a/b/g/n/ac based on Atheros QCNFA435/QCA9377 (168c:0042) chip. Most definitely not supported OOB, if at all... Atheros40 kext patch or DSDT injection (for compatibility with supported Atheros model) would need to be tried I guess.

For the record, Enoch does fully support High Sierra. However, it does not support installation of High Sierra nor its upgrades. I wish I can add "yet" because I hope it's only a matter of time before Chameleon/Enoch are updated to the double-phased approach introduced with 10.13. Regretfully, ErmaC appears the be more or less the only dev left who still works on this great bootloader. Clover has therefore confirmed its lead and method of choice re: High Sierra installation (and subsequent updates). As such, even though I still run all my Hacks on Enoch, I've had to call on Clover for initial High Sierra installation and still need to call on the Clover-based USB installer to complete the updates.

AppleHDA audio level is indeed a little quieter than with VoodooHDA. I'm not aware of any adjustment settings to set AppleHDA volume level on a par with Voodoo's.

The tool does the exact same thing as the /writeromfile option when applied to the Dell system's BIOS exec. I therefore suggest the OP proceeds that way with the T7500 BIOS available off Dell's web site. http://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=2WN85

It should be with Bronxteck-compiled R6 version available here.

In other words, it's a 16bit (2 x bytes) value to be expressed in Hexadecimal in the range 0 to 65535.

Re: USB audio, I can vouch for this cheap & cheerful device... Not buzzy and very reliable; works OOB from Leopard 10.5 to High Sierra 10.13! https://osxlatitude.com/index.php?/topic/2061-dell-precision-470-670-workstation-snow-leopardlionmountain-lionmavericksyosemite/page-3&do=findComment&comment=48104

From memory, E6430s can be fitted with 2 x different Webcam models. One model works OOB, the other one not at all. Look a the displayed model and vendor/device id in your SysProfiler and post the details.

You have a 4th gen Haswell laptop (i7-4700MQ) so make sure to activate the Clover KernelPm patch, otherwise you're indeed likely to encounter system reset as kernel loads. Use latest version of Clover Configurator app to prepare and tune your Clover config file.

This method dates a little and used to be applicable to old Dell laptops of the 2005-2008/2009 era (eg: Latitude Dx20/Dx30 Series, Precision Mx300, Inspiron 6xxxx, etc.). It's not applicable to more recent Dell laptops, for instance E6x20/E6x30/E6x40 models. In addition, the method, as detailed in this LinkedIn page, is somehow erroneous: 1) no need to remove the CMOS battery 2) on plugging the power cable, the [END] key must only be pressed a couple of seconds max when the power led lits in orange; if the key is pressed more than that, no attempt will be made to load BIOS off the plugged-in USB media This method was described several times on the forum several years ago. Ex: https://osxlatitude.com/index.php?/topic/7691-problems-with-dell-d630-no-qe-ci-bios-a09/&do=findComment&comment=47171 MyDigitalLife forum has a dedicated thread on BIOS recovery for all sorts of computers; OP should have a look there: https://forums.mydigitallife.net/threads/bios-recovery-procedures.870/ You could give the following Dell method a go, but it probably won't work as they say it's only applicable to systems from 2015/Skylake chipsets... https://www.dell.com/support/article/fr/fr/frdhs1/sln300716/bios-recovery-options-on-a-dell-pc-or-tablet?lang=en#faqs Another apparent method: https://www.cnet.com/forums/discussions/bad-bios-update-recovery/ Good luck!

https://osxlatitude.com/index.php?/topic/10386-solved-e6230-sierra-kp-after-security-update/

Clover config attached in your debug archive appears empty. Normal?

Boot in single-user mode, delete the offending kext, rebuild your cache and you should be back in business.

All you need is Rehabman's ACPIBatteryManager kext. You'd find it in the Guides's bootpacks if you followed them...