Hervé

See previous post; but since problem persists when you disable or remove the card, we can rule that out now.

No, the ASPM that needs to be set to 0 to prevent system freeze. It's all detailed in the BCM4350 guide, look it up.

You would be able to do both but I'm pretty sure an unsupported SMBIOS will not let you upgrade from within the macOS version you currently run. I made a fresh installation over my old Mojave build with -no_compat_check boot arg and that upgraded the old installation Ok (all apps and data kept as before). No reformatting or deletion of the Mojave partition before of course! I'll post a detailed guide tomorrow but in a nutshell: made the Big Sur USB installer with usual createinstallmedia command line and followed Dortania's guide for Ivy Bridge laptop to the letter erased all data from USB key's EFI partition and copied the default OC 0.6.3 EFI folder there copied existing DSDT + CPU power management SSDT to the ACPI folder and all existing add-on kexts to kexts folder copied sample config file to OC folder and opened it with ProperTree did a clean snpashot to prefill the config, then adjusted it as per dortania's guidance booted the Big Sur installer and went ahead with the installation Note that it'll take some time (about 1hr) and will require 4 reboots to complete. Edit: E6230 guide now updated for Big Sur.

Ok, just got got Big Sur 11.0.1 (20B29) installed on the E6230 with OC 0.6.3. So far all appears to run Ok. Full acceleration on HD4000. Kept the MBP10,2 SMBIOS with -no_compat_check boot arg.

So add the usual properties to inject HDMI type to iGPU connector #1: framebuffer-con1-enable 1 NUMBER framebuffer-con1-type 00080000 DATA And add the required property for your SD card reader once you've identified its location in IOReg. Everything is in the Arbitrary tab of your Clover config Devices section/tab... Didn't you look at it or know about it? Use IORegistryExplorer app to identify the exact I/O location in replacement of the PCI debug string used in your Clover config.

Sorry, my brain doesn't have a built-in Base64 decoder so I'm not going to waste a second on that. Post a directly English-readable version please. There are very useful things called Xcode or Clover Configurator you know... You're even allowed to post a zipped copy of your Clover config as you did for OpenCore in post #1. This being said, the property keys you inject relate to the framebuffer general settings not the connectors (i.e. display outputs/ports) and, if you encounter HDMI-related issues, you should probably inject the usual connector type 00080000 for the relevant connector (probably #1). Refer to WhateverGreen's manual for guidance.

I don't think that relevant either. Bear in mind that the last iMac with nVidia Kepler cards were late 2013/early 2014 Haswell iMac 14,x. You may have to set your SMBIOS to one of those or pick a Coffee Lake SMBIOS that you may try and bastardized with the board-id of a Kepler-fitted iMac14,x.

I fail to see the likely relation between the error message you get and the GT730 card. Looking at your Clover config through Clover Configurator, I see an incomplete and incorrect SMBIOS section so you probably ought to correct that. iMac18,1 is a Kaby Lake platform and you have a Coffee Lake computer. Use CC to properly select and use a suitable SMBIOS.

I aim to try it out soon and post a detailed guide thereafter as usual. MBP10,2 is not a platform supported by Big Sur so it obviously cannot and will not install on the E6230 with that SMBIOS without one of the usual workarounds (eg: patched PlatformSupport.plist or -no_compat_check boot arg) or changing the SMBIOS to that of a supported Mac.

Answer is no as stated many many times on the forum. NVS 4200M is Fermi and Fermi graphics are not properly supported beyond OS X El Capitan/macOS Sierra. On the E6x20 laptops, you just cannot get them supported past El Capitan 10.11. If you add to that the fact that nVidia support for Metal starts at Kepler cards, that pretty much closes the discussion re: Fermi cards on Mojave or later. In addition -and again, this has been stated numerous times over the last couple of years-, Intel HD3000 was last officially supported in macOS High Sierra. 'dropped in Mojave and later. Workarounds exist for Mojave and Catalina through patches that basically install missing SNB graphics kext from High Sierra and replace some graphics-related frameworks. Process was easy and worked Ok in Mojave and Catalina up to 10.15.3 but things got complicated from 10.15.4 and now require to use dosdude1's patcher; we've posted about this in the Graphics forum section and you may also Google for this. All in all, I'm of the opinion that it's not a great idea to run Catalina or later version on HD3000 laptops, given that this iGPU was already buggy past Yosemite (since El Capitan, everyone experiences glitches, pixelisation and black horizontal lines across the screen over time). There is no known and definitive solution but having 8GB of RAM and a therefore a minimum of 512MB VRAM does somehow improve things a little. My personal experience is that the buggy behaviour happens and worsens the longer you use the laptop without reboots and the more you repeat the sleep/wake cycles. With regards to audio, what you describe is well-known and it's long been stated that you need to cache (not inject) CodecCommander kext from /L/E (or /S/L/E if you must). Do think of using the forum Search facility before posting; all these points have been discussed at great length and answered before.

As I said, Kepler-based GT730 is fully and natively supported...

Device properties indeed but not ig-platform-id per sé (that's the framebuffer id), the other properties you'd have had in your Clover config, including the binary patch for HDMI connector type. If you kept a copy, check it out with Clover configurator, if not download the Clover pack of any E5x50 or E7x50 guide. No property injection for connector #1 in your OC config... Re: card reader, look into the Card Reader forum section. Again, no property injection for the device in your OC config...

You need to switch to OpenCore. You're highly unlikely to succeed booting the BS installer with Clover r5126.

You may have missed some property injections that were present in Clover; typically, the SD card reader of those Latitude Exx50 works OOB as long as you fake the Broadcom id that's been listed in our dedicated thread on the matter. As long as you do the same in OC, no reason why it would not work.

I'm already aware of your setup details, you posted them in your previous BS beta-related thread. You can install a 2242 NVME SSD in a 2280 slot, you just won't be able to secure it properly (or use a piece of tape); but it'll work fine for testing purposes. I've done such a thing in my Latitude 7490.

It's probably a consequence of running a NVME x2 SSD in a WWAN x1 slot. Or it's another NVME model that's poorly supported... Why don't you remove your other SSD temporarily and try this WD model in the proper slot as a test?

Well, had you gone all the way down to the bottom of the page...

You could have checked the site directly... https://github.com/OpenIntelWireless/itlwm/releases/tag/v1.1.0

Kepler-based GT730 is fully and natively supported in Catalina and Big Sur.

'goes without saying.

Released November 12th, 2020 as announced. Version 11.0.1, build 20B29 Officially, this drops support for Ivy Bridge systems with Intel HD4000 graphics to raise the minimum requirements to Haswell graphics. Yet, as per all beta versions, Big Sur 11.0.1 still provides all the drivers required to support HD4000 graphics so it can be installed and run on such platforms with full graphics acceleration. nVidia Kepler graphics remain fully supported. A notable exception to these specifications appears to apply to the iMac14,1/2/3 (Haswell models with Iris Pro 5200 or Kepler GT7x5M graphics) that all appear officially unsupported. Also released at the same time: High Sierra 10.13.6 Security Update 2020-006 (build 17G14042), which should be the last one, High Sierra reaching end of support. Mojave 10.14.6 Security Update 2020-006 (build 18G6042). View full article

See our FAQ topic on the matter, nothing's changed. It's quite usual that Power Management settings are defaulted after an update.

Dell support web site can also provide all the necessary details based on serial #/tag #. This is E6430 with Intel HD4000 only and originally shipped with a dual core i5-3380M CPU: https://www.dell.com/support/home/en-us/product-support/servicetag/0-ZGFhbVBiWmh3SER2MTcwSEJCdnZZdz090/overview Please note the following points: you may update your BIOS to the latest version A24. apply the HD4000 Capri framebuffer patch/property injection to reduce the FB memory size from 16MB to 8MB and avoid garbled display. See my E6230 Guide for details. given that your E6430 is fitted with a 1600x900 LCD, you must use the HiRes Capri layout 0x01660004, not the (default) LoRes layout 0x01660003. given that the HiRes Capri layout only natively supports a single LVDS display output, you'd have to apply the necessary (and documented) patch/properties injection to support additional outputs (DP, HDMI). See the HD4000/Capri dedicated thread in our Graphics forum section for details. Depending on the exact model fitted to your E6430, the Intel wireless card may be unsupported and require replacement by a (Broadcom) supported card. See our FAQ and/or Wireless forum section(s) for details. If the Advanced-N 6205 card this E6430 was originally shipped with is still in place, you're out of luck as it's not supported at all.

No issues installing this update (build 19H15) on my Latitude E6230, Latitude 7490 and Vostro200. However, since this update was installed, my Vostro 200 regularly reports having run out of RAM despite being fitted with 8GB. It could be the same kind of gremlins experienced by so many people with the bugged Mojave update initially released alongside 10.15.7. Apple had to release yet another Mojave update a short time after to fix the memory bug.