Hervé

Add CodecCommander to your set of kexts. You should not require those old FakePCIIDxxx kexts; they're all deprecated nowadays. HDMI audio is normally available through AppleALC + iGPU framebuffer patch to set HDMI output port connector to HDMI.

Target macOS release: Big Sur 11.x This is an OpenCore-based installation, completed as an upgrade of an existing Catalina installation as detailed below. Working: full graphics acceleration on GT730 OOB with macOS native driver multi-display (with Lilu + WEG): DVI & HDMI OOB, VGA with NVCAP value 050000000000FFFFFFFF00000000000E00000000 audio, including HDMI, microphone input and headset output (with AppleALC + all layouts or VoodooHDA) FastEthernet LAN connection (with 82566MM or AppleIntelE1000 kext, patched if necessary for PCI id 8086:10c0) 19in-1 card reader OOB CD/DVD RW drive OOB front and rear USB ports (OOB) partial CPU power management with OpenCore, legacy Core2Duo platform oblige (LFM + HFM only since OpenCore does not generate C States/P States) sleep (Energy Saver settings, Apple menu, PWR button) & wake (PWR button, USB keyboard/mouse) USB or Wireless keyboard and mouse (with IOHIDFamily's isSingleUser function OpenCore patch) Not working: N/A Not tested: N/A GeekBench v4.4.4 (64bit) gives a 3900+ rating: This old desktop PC only operates in legacy BIOS mode, not UEFI. This is a problem for installing Big Sur from scratch with a USB installer because, in legacy BIOS mode, OpenCore does not appear capable to dynamically obtain the volume UUID of the temporary MacOS installer partition/volume (created during the installation process) and properly define an essential parameter called msu-product-url. This causes the installation process to fail proper execution and, instead, triggers computer reset + continuous boot loop of the temporary volume, the installation therefore never reaching completion. A workaround to this problem is to install Big Sur as an upgrade of an existing Catalina installation. When installing Big Sur as an upgrade of Catalina, the temp installation will be created on the existing Catalina Data volume whose UUID can be readily obtained and passed through NVRAM parameter msu-product-url to the installation process. This was described in this thread by pac-man at InsanelyMac, credits to him. Basically, the UUID of the Catalina Data volume is obtained through the diskutil line command and the resulting value is used to create a fully-defined path for the temp installation volume that is stored in NVRAM parameter msu-product-url. This NVRAM parameter is essential to complete the installation process. Please note that installing Big Sur on this old desktop PC takes a substantial amount time to complete (even on a SATA SSD) so set aside a few hours... 1) Preparation OpenCore needs to be setup in legacy mode to boot the Vostro 200 computer, lack of UEFI BIOS mode oblige. This is well documented on the Dortania OpenCore GitHub repo which I invite everyone to refer to. the following OC 0.6.5 EFI folder may be used on the existing disk's EFI partition or on a USB key as bootloader to reboot the system during the Big Sur installation phases, then boot Big Sur once it has been fully installed: OC_0-6-5_EFI_Vostro200_BigSur.zip key elements to note in that config are: the IOHIDFamily kext patch applied to the _isSingleUser function; it's required to obtain working USB keyboard & mouse, they don't work without the patch. This is detailed in the Dortania's documentation. additional msu-product-url parameter added under NVRAM->7C436110-AB2A-4BBB-A880-FE41995C9F82 UUID UUID as per pac-man's thread at InsanelyMac. 2) 11.x installation from an existing Catalina installation (can be a Clover-based one), download a copy of Big Sur installation package. ensure you have emulated NVRAM working and define msu-product-url parameter as follows through Terminal: sudo nvram msu-product-url="msu-product-url://$(diskutil info /System/Volumes/Data | grep "Volume UUID" | awk '{print $3}')/macOS%2520Install%2520Data" run the Big Sur installation package and proceed with installation on your Catalina disk/volume/partition as offered by the installer app. the Big Sur files will be copied over and this may take a lot of time (could be anything from 40mins to 1hr). on 1st and all subsequent reboots, make sure to use OpenCore and the EFI folder/config setup offered above. the whole installation process will normally require 3 or 4 reboots to complete and this make take anything like 1hr. 3) Post-installation tuning once the Big Sur installation has completed and Big Sur first boots, complete the initial configuration tuning. Here too, this may take an unusual and very long time; just hang in there. once at the Big Sur desktop, mount your disk's EFI partition and copy the OpenCore EFI folder as necessary/appropriate in order to boot Big Sur via OpenCore. proceed with usual macOS fine-tuning (wireless setup, hibernation disabling, refresh of serial numbers, etc.). NB: Contrary to pac-man's suggestion to remove the msu-product-url from NVRAM after installation, I strongly recommended to retain it because it'll be required for each Big Sur update. Edit #1: ------- For a fresh installation of Big Sur, proceed as follows to obtain the UUID value to inject in NVRAM as msu-product-url: Boot your Big Sur installer and initiate installation or launch the Big Sur installation package from an existing macOS build. At 1st reboot, boot the Big Sur installer again and type the following in Terminal: diskutil info /Volumes/<target disk or partition name"> | grep "Volume UUID" | awk '{print $3}' Make a note of the returned UUID Edit your OC config and add the following parameter in NVRAM section against UUID 7C436110-AB2A-4BBB-A880-FE41995C9F82: msu-product-url <obtained UUID>/macOS%2520Install%2520Data String Reboot and Reset NVRAM before booting your temp Macintosh HD partition For instance, if installing Big Sur on a disk or partition called "macOS_BigSur_11": In Terminal, type: diskutil info /Volumes/macOS_BigSur_11 | grep "Volume UUOD" | awk '{print $3}' say it returns UUID value 4B9B8623-B1B4-3DC8-841A-D57C824B0067. set key msu-product-url with value 4B9B8623-B1B4-3DC8-841A-D57C824B0067/macOS%2520Install%2520Data and type String in the OC config. reboot, reset NVRAM and boot your temp installation partition to complete the installation.

Afaik, no need to patch framebuffer memory (fbmem) or stolen memory (stolenmem) for Haswell HD4x00 graphics. Only cursor memory (cursormem) is to be patched to 9MB if glitches are experienced.

If you're using OpenCore, just follow the detailed guidance posted at Dortania. It works perfectly. Win10 can be on an existing partition before you install macOS or be installed afterwards. It makes no difference and the process remains the same. Bear in mind that OpenCore settings apply to all OS you may boot so don't be surprised of potential side effects in Windows, like some unknown devices in Device Manager. It's usually without impact however. No such side effects with Clover.

You can start by identifying your wireless card's model then checking its likely compatibility in our FAQ + Wireless forum sections... And guys, please post your system's specs in signature!

HDMI works OOB out of the E6230. HDMI connector patch required for HDMI audio. The laptop usually drives/controls the output resolution on cable connection, at least on the 3 x TVs + the few monitors I've hooked my E6230 to. Could be a damaged/unsuitable cable, bad connection or a damaged HDMI port on either side. Start by removing video mirroring on the Hack to avoid potential resolution-related issue on the TV screen. I recommend using Display Menu app for immediate access off the Finder's bar. https://osxlatitude.com/forums/topic/2366-finders-bar-display-tool/?tab=comments#comment-17779 Rest assured it's not a Hackintosh or macOS issue.

With MBP11,1 (which is the desired target), use the -no_compat_check boot arg depending on the version of Big Sur you try to install. I've cleaned up your OC config. Try it out: config.plist.zip

Quite surprising and strange that your OS version is stated as unknown... Are you using a full vanilla installation or a distro of some sort? I have to say that I strongly suspect latter rather than former. And what are these boot args? chunklist-security-epoch=0 -chunklist-no-rev2-dev Did you disable hibernation? If not, expect trouble with sleep and wake, especially if you kept settings such as Power Nap or Wake on Network Access enabled. Please consult out FAQ section regarding Sleep/Wake settings.

There are probably a few things to review given that your config looks like a mix of Dortania's settings + stuff carried over from a previous Catalina setup. For instance: SSDT-EC (which injects a separate EC device), yet your rename device ECDV to EC in your config file. You may also want to revisit those ACPI patches you appear to have carried over in relation to HPET, RTC and TIMR.

No double post on the forum please, especially if you double post for support matters in the Guides section! I don't know what you mean but "error" given that you have no driver installed for your LAN card... According to your Aida64 report, it's a Realtek RTL8139/810x Fast Ethernet Adapter with PCI id 10ec:8136 so clearly a Realtek RTL810x card. It's not natively supported but it may work with this old kext that does cater for 10ec:8136: AppleRTL8169Ethernet.kext.zip Possible alternatives: the RTL8139 driver mentioned here with a patch to add id 8136 or change id 8139 to 8136 (but chance that it'll work is low) Rehabman's oldish RTL8169 kext available here (will probably need same patching too and agin, low chance that it'll work) Failing that, Google for an OS X/macOS driver for 10ec:8136. Good luck. NB: you appear to have a Haswell/HD4x00 laptop so you can remove AppleCpuPmCfgLock kernel quirk, it applies to Sandy Bridge/Ivy Bridge platforms. Also, unless your laptop is fitted with quad-core CPU -but you've not bothered to post your system specs-, you should use MBA6,2 or MBP11,1 SMBIOS.

Post a zipped copy of your EFI folder so that we check your settings.

Do you use a valid payable subscription or one of those free offers with the purchase of an Apple device? If latter, could be the reason...

Last update: 21 Jan 2021 Here are BIOS settings that are known to work on the Satellite Pro R50-B-116 (4th gen. Haswell CPU with Intel HD4400 graphics) under Big Sur. These settings were tested and verified with BIOS v1.70. Security . BIOS Password: * User: Not Registered or set * Supervisor: Not Registered or set . HDD/SSD Password: * Mode: Master+User or User Only * User: Not Registered or set * Master: Not Registered or set . Secure Boot: Disabled . TPM: Enabled or Disabled . Hide TPM: Yes or No Power Management . Wake-up on LAN = Disabled . Wake-up on LAN on Battery = Disabled . Wake-up on Keyboard = Enabled . Critical Battery Wake-up: Enabled . Panel Open - Power On: Enabled to support wake on opening the lid or Disabled . Power on by AC: Enabled to support wake on plugging AC or Disabled . Dynamic CPU Frequency Mode: Dynamic Switch . Core Multi-Processing: Enabled . Intel Turbo Boost Technology: Enabled . Intel Display Power Management: Enabled . SATA Interface setting: Performance BIOS Power Management . Battery Save Mode: Full Power Advanced . Execute-Disable Bit Capability: Available . Virtualization Technology: Disabled or Enabled . Beep Sound: Medium or any other value . USB Power in Off State: Enabled . USB Legacy Emulation: Enabled System Configuration . Built-in LAN: Enabled . Wireless LAN = Enabled . Auto Wireless LAN RF Switching: Disabled . SD Host Controller: Enabled . Memory Performance Mode: Enabled . Boot Mode: UEFI Boot (may be set to CSM (i.e. legacy) for Chameleon/Enoch or Clover and older OS X/macOS versions) . Power On Display: Auto-Selected . Boot Up NumLock Status: ON . Function Keys Mode: Standard F1-F12 mode

No difference between OpenCore and Clover in the respect of audio, keyboard/trackpad or graphics settings. If you follow the Dortania's guidance, you'll clearly see it. No further hint to provide until you post your config.

You're using Lilu v1.5.0 and I read it could cause issues. Try with the previous version.

It's been said before and you'll find a few old threads here and at InsanelyMac on the matter: mSATA SSD do not work in mini-PCIe slots. Whilst the slots physically look the same, they're not electrical identical. So, mSATA drives work in mSATA slots only. In the case of the E6x40, the slot supports 3 x usage: PCIe, mSATA and USB. But that's a fairly rare combination. With regards to Big Sur and OpenCore, the differences are minimal between version 0.6.3 and 0.6.5 as far as any config goes. If you need further assistance, just do the needful, i.e. post your stuff. There are existing threads relating to running Big Sur on this Latitude E mode so you should have been able to re-use existing stuff posted in those threads.

For the benefits of other people, please detail the changes you made.

Big Sur supports most mainstream Intel iGPUs from Ivy Bridge HD4000 to Ice Lake Iris Plus as long as they meet the minimum requirement of GT2 specs. You may refer to Dortania's GPU buying guide for further info on the matter. Haswell HD4600 iGPU has been supported since OS X ML 10.8.5/Mavericks and remains fully and natively supported in Big Sur. There should be no graphics issue on your E6540. Your setup may be incorrect and, with regards to glitches, the Haswell cursor memory patch (increase from 6MB to 9MB) aims to address this though I must say I never needed it on my E6440 when I had it. Post a zipped copy of your OpenCore EFI folder if you want further assistance. NB: Your signature indicates an M.2 SSD in your E6540; strange and rather confusing given that the E6x40 only offered traditional SATA and combo PCIe/USB/mSATA slots... Unless your using an M.2 SATA SSD in a 2.5" SATA adapter of course.

Your config contains an error for the HD4x00 cursor memory patch; you incorrectly entered: framebuffer-cursor 00009000 STRING when it should be framebuffer-cursormem 00009000 DATA Probably proves you don't need that patch.... I invite you to consult the WEG manual for guidance on the syntax of framebuffer patches. Then watch out with Big Sur and that MBP11,1 SMBIOS. Better to switch to MBA6,2. https://osxlatitude.com/forums/topic/14367-big-sur-1101-regression/?tab=comments#comment-104569

Why don't you start by consulting and reading Dortania's documentation for guidance on the OpenCore configuration?

Target macOS release: Big Sur 11.x This is an OpenCore-based installation (on a SATA-III 6Gb/s SSD) using the standard vanilla method detailed below: Working: full graphics acceleration on Intel HD4400 graphics (with Lilu v1.5.0 v1.6.0 + WEG v1.4.6 v1.5.8 + usual Azul FB properties injection) multi-display on VGA (OOB) + HDMI (with injected connector patch) brightness control with Fn-Ins/Fn-PgDn (with Dortania's SSDT-PNLF); keys remapping required here audio, including combo jack microphone input/headphones output (with VoodooHDA v2.9.2 + AppleHDADisabler); manual output selection required between speakers and headphones. I was only able to get audio with AppleALC (layout 13) if I booted with Clover. HDMI audio (with ACPI renaming of B0D3 to HDAU) GigEthernet LAN (with Mieze's RealtekRTL8111 v2.4.0d6) wireless with any compatible card integrated webcam (OOB) Realtek USB-internal SD Card reader (with Firewolf's RealtekCardReader v0.9.6) full CPU power management 0.8->1.7GHz, including Turbo boost 1.8->2.7GHz (with Dortania's SSDT-PLUG.aml) sleep & wake (with Hackintool's SSDT-UIAC): sleep with Battery PrefPane settings, Apple menu, PWR button but not through lid closing wake with PWR button, keyboard key, mouse/trackpad, lid opening, AC plugging partial battery management (with Rehabman's ACPIBatteryManager v1.90.1); no auto-detection of AC plugging/unplugging (except after sleep/wake) but battery charge % Ok keyboard & basic TrackPad functionalities (with Rehabman's VoodooPS2Controller v1.9.2) all USB ports Not working: AC charger plugging/unplugging; proper status only reflected at startup or after wake Bluetooth; not seen/detected due to likely USB-related issue; in fact, Bluetooth no longer appears/works in Windows after having booted macOS with OC GeekBench v4.4.x (64bit) results: 1) 11.x USB installer creation Using a USB key of 16GB minimum, create a Big Sur USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Big Sur installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_16GB) The process will take several minutes. Once completed: Setup your BIOS for UEFI mode if not already done so (installation won't work in CSM mode). Recommended BIOS settings available here. mount the EFI partition of your USB installer and, if applicable, erase the partition through Disk Utility or delete all of its existing contents. Tools such as Mount EFI or apps such as Clover Configurator or EFI Mounter may be used to that effect. Failing that, the simple diskutil mount command does the trick once you've identified your EFI partition with diskutil list command: sudo diskutil list (shows list of disks and partitions) sudo diskutil mount /dev/<identified disk> (eg: sudo diskutil mount /dev/disk0s1) uncompress the following Satellite Pro R50-B-116 Big Sur OpenCore pack and copy the EFI folder to the mounted EFI partition: OC_0.6.5_EFI_R50-B-116_BigSur.zip OC_0.8.0_EFI_R50-B-116_BigSur.zip Please note that, to modify your OpenCore config, you should use the following ProperTree app (see Dortania's documentation for details on this) though I must say that I've never encountered any issues with OpenCore Configurator app and OC: ProperTree.zip 2) 11.x installation boot the Big Sur USB installer at the OpenCore main menu, select the "Install macOS Big Sur" partition and press [ENTER] at Big Sur main installation screen, select Disk Utility to create & format the target Big Sur partition/disk. Note that I could not begin installation unless my target partition/disk was formatted HFS+ exit DU and return to Big Sur main installation screen, then proceed with installation the installation process will twice reboot a temporary macOS installer partition to complete the installation. This overall installation process takes much longer (~1hr) than what was experienced with previous macOS versions so be patient. Don't be frightened by the 2nd reboot which show things never seen with previous macOS versions a 3rd reboot will boot your target named Big Sur partition/disk and will be quickly followed by a 4th and final reboot of that same target Big Sur partition/disk each time, reboot via your USB installer. 3) Post-installation tuning Once the finalised Big Sur installation has booted, complete the 1st boot configuration tuning Once at the desktop, mount the EFI partition of your Big Sur disk Copy the EFI folder of the OpenCore R50-B-116 Big Sur pack to the mounted EFI partition You may then reboot and verify that Big Sur boots off your disk through OpenCore You may then disable verbose mode by removing -v flag from NVRAM->7C436110-AB2A-4BBB-A880-FE41995C9F82->boot-args in the OpenCore config file. You may then modify your SMBIOS info under PlatformInfo->Generic section and ensure you have unique numbers or unique combination of numbers. Use GenSMBIOS tool (available here) to generate new MLB, ROM, SystemSerialNumber and SystemUUID. Refer to Dortania's documentation for further info and guidance. Alternatively, you may use OpenCoreConfigurator app given that it is generally Ok too these days. Complete any additional fine-tuning such as disabling hibernation, disabling GateKeeper, etc. Please note that if you use a DW1820A card in this laptop, make sure to: enable AirportBrcmFixup parent kext (not the PlugIns) in the Kernel section of your OC config uncomment the compatible, pci-aspm-default and model properties against device located at PciRoot(0x0)/Pci(0x1c,0x1)/Pci(0x0,0x0) in the PropertiesInjection section Please note that, after any significant change to your Big Sur setup requiring to modify your OpenCore configuration, it's usually required to execute a Reset NVRAM from OpenCore main menu (aka Picker) in order for the change(s) to be taken into account. At time of writing (Jan 2021), this remains work in progress in order to address: AC charger connection/disconnection status Audio with AppleALC when booting with OpenCore TrackPad better recognition and gestures Brightness keys remapping Bluetooth off compatible M.2 combo card - - - - - - - - - - Edit #1: 30 May 2022 Revised OC 0.8.0 pack with support for Realtek card reader

What panic message are you getting? What do you use to install Catalina? Clover? Opencore? What versions? How did you make your USB installer, using what procedure? Please post zipped copy of EFI folder.

Of course, it's one of the Broadcom chipsets dropped in Big Sur as indicated in our Wireless cards inventory last December...

Just check the card's PCI id in IOReg with IORegistryExplorer or DPCIManager.

Apple Airport Card is pretty meaningless. You'll have to state the exact card model to get a proper answer. As Jake said, Big Sur dropped support for even more cards than Mojave & Catalina did so you may have one of those. As usual, please consult our wireless cards inventory.