Jump to content


Popular Content

Showing content with the highest reputation since 10/28/20 in all areas

  1. 3 points
    Target macOS release: Big Sur 11.0.x This is an OpenCore-based installation using the standard vanilla method detailed below: Working: full graphics acceleration on Intel HD4000 graphics (with Lilu v1.4.9 + WEG v1.4.4) multi-display with HDMI OOB audio, including jack microphone input and headset output (with AppleALC v1.5.4 & layout 12 + CodecCommander v2.7.1) HDMI audio (with Capri Framebuffer properties injection) built-in GigEthernet LAN connection (with AppleIntelE1000e v3.1.0 or latest IntelMausiEthernet kext) wireless and bluetooth with any compatible card integrated webcam (OOB) full CPU power management, including Turbo boost (with CPU-specific generated ssdt) sleep (Lid, Energy Saver settings, Apple menu, Fn-F1, PWR button) & wake (Lid, PWR button) battery management (with ACPIBatteryManager v1.90.1) SD card reader (with DSDT patch or property injection ,for compatibility with Apple's default reader) keyboard (with Dr Hurt's VoodooPS2Controller R6 + DSDT patch for brightness control) touchpad including tap-to-click (with Dr Hurt's VoodooPS2Controller R6) left combo eSATA/USB2.0 + right USB3.0 ports (with Hackintool's generated USBPorts; optional FakePCIID kexts for multiplexing) ExpressCard slot OOB Not working: VGA output unsupported Not tested: SmartCard reader fingerprint scanner GeekBench v4.4.x (64bit) results: 1) 11.0 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 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 E6230 Big Sur OpenCore pack and copy the EFI folder to the mounted EFI partition: OC_0.6.3_EFI_E6230_BigSur.zip OC_0.6.3_EFI_E6230_BigSur_#2.zip OC_0.6.3_EFI_E6230_BigSur_#3.zip If your E6230 is fitted with a different CPU than the i7-3540M, please replace the Power Management SSDT of the pack by one applicable to your model (whether an existing SSDT or your own generated one). Please note that, to modify your OpenCore config, you should use the following ProperTree app (see Dortania's documentation for details on this): ProperTree.zip 2) 11.0 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 APFS the target Big Sur partition/disk. Note that installation won't work if target partition/disk is 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. Please note that your USB installer will probably register as an OpenCcore entry in the E6230 UEFI list displayed after pressing [F12] 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 E6230 Big Sur OpenCore 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 NB: Nov 15th, 2020 - - - - - - - - - - - - - - The OpenCore pack provided here was built by rigorously following Dortania's published guidance for Ivy Bridge laptops. It was 1st tuned for the E6230 laptop adding same patched DSDT, patched SSDT and same (but updated) kexts used for previous macOS versions. Property injection was used where on-the-fly patches were previously used with Clover. The OpenCore configuration of the pack was subsequently tuned to support things such as OpenCore GUI and startup Chime. These are disabled in the config of the pack but can be enabled by changing: Misc->Boot->PickerMode from Builtin to External UEFI->Audio->PlayChime from False to True It should also be noted that this OpenCore pack would gain from further tuning/optimisation on matters such as DSDT, SSDTs, ACPI settings or Property injection in the config. A revised and optimised pack can therefore be expected in a not too distant future. 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. Edit: Nov 26th, 2020 - - - - - - - - - - - - - - - New optimised pack #3: Revised OC config to fix incorrect CPU power management-related Kernel Quirks that were root cause of freeze on wake.
  2. 3 points
    Big Sur - OpenCore Download MacOS Big Sur app Create USB installer using well known createinstallmedia command Mount EFI partition of installer Replace / Add attached EFI Folder (Rename as EFI) Note: Replace Config.plist with Config-IntelWifi.plist if you have an Intel combo card Install Heliport.app to enable/Configure Intel Wi-Fi HeliPort.app.zip E7440_OC_0.6.3.zip
  3. 3 points
    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.
  4. 2 points
    Thank you @Jake Lo and @Chicken07 Now trackpad is working with your help. Changed my config based on your EFI and all is OK. Tap to Click : OK Two finger Scroll : OK My next steps try to find solution for multi finger gestures.
  5. 2 points
    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.
  6. 2 points
    Big Sur - OpenCore Download MacOS Big Sur app Create USB installer using well known createinstallmedia command Mount EFI partition of installer Replace / Add attached EFI Folder (Rename as EFI) E7450_OC_0.6.3.zip
  7. 1 point
    @NTHT1MD The files I posted should work with full graphics but looks like you'll need to set the DVMT preallocation 1st See here for instruction You can skip the 1st 4 steps Set with the following command setup_var 0x432 0x3
  8. 1 point
    remove this from the boot arg under NVRam in the config file -igfxvesa
  9. 1 point
    You may also use Clover Configurator and its SMBIOS + RtVariables tabs to generate your SMBIOS data.
  10. 1 point
    @NTHT1MD Looks like it might be a graphics issue. So in the boot arg, add this to get the installation going. Remove it after installation -igfxvesa Here's the edited Config file from your attachment with the boot arg added config.plist.zip
  11. 1 point
    Hi, I have a e7470 and got the following error during the Update. I use Clover the 5126. Have somebody the same issue
  12. 1 point
    Instead of replacing kext(s) from older MacOS, try injecting with this modified kext(s). No need to delete or replace IO80211Family.kext https://www.insanelymac.com/forum/files/file/1008-io80211family-modif/
  13. 1 point
    Try this to see if it'll run in Mojave before upgrading to Big Sur Replace the whole EFI folder in the EFI partition or create and USB boot disk with this EFI folder (rename the attached folder to EFI) Note: If you have the Intel Wifi /BT computer, replace Config with Config-IntelWifi 7370_OC_063.zip
  14. 1 point
    EFI partitions can be mounted with apps such as EFI Mounter or Clover Configurator or a few others. But it's just as quick and easy to use Terminal... Just identify the partition disk/volume and mount it! diskutil list sudo diskutil mount /dev/<identified disk> Example: lat-7490:~ admin$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *512.1 GB disk0 1: EFI BOOT 523.2 MB disk0s1 2: Microsoft Reserved 134.2 MB disk0s2 3: Microsoft Basic Data Windows 398.0 GB disk0s3 4: Windows Recovery 972.0 MB disk0s4 5: Apple_APFS Container disk1 112.5 GB disk0s5 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +112.5 GB disk1 Physical Store disk0s5 1: APFS Volume Mojave - Data 53.2 GB disk1s1 2: APFS Volume Preboot 154.5 MB disk1s2 3: APFS Volume Recovery 529.0 MB disk1s3 4: APFS Volume VM 1.1 MB disk1s4 5: APFS Volume Macintosh 11.3 GB disk1s5 lat-7490:~ admin$ sudo diskutil mount /dev/disk0s1 Volume BOOT on /dev/disk0s1 mounted
  15. 1 point
    Proceed with caution; preferably on a separate disk or partition. Use OC off a USB key rather than overwrite your existing Clover EFI partition. But that's a matter for a separate thread.
  16. 1 point
    No need to take out kexts, you can disable/block them by pressing the spacebar at the Clover GUI.
  17. 1 point
    v4910 might not be able to boot catalina 10.15.7 Replace your USB Clover files with my generic Clover file v5119. Just keep your kexts/ACPI folder and Config.plist
  18. 1 point
  19. 1 point
    As I said, the connector properties, not the framebuffer properties. I suggest you read the WEG documentation to familiarise yourself with the matter. https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md
  20. 1 point
    Clover's full compatibility with Big Sur remains etchy. You should really consider a switch to OpenCore instead. There are now several threads related to installing Big Sur on the E7x70, including an update of JakeLo's guide with a full OpenCore EFI folder.
  21. 1 point
    Hi. Although I experienced this problem too, unfortunately the trackpad didn't work for me either, so I started to delete the kexts that I haven't used during the clover so far and watched when a change happens. When I realized the mistake, I could only laugh at it! : D Solution: Delete "SMCDellSensors.kext" from "config.plist / Kernel" and it will work!
  22. 1 point
    It's long been reported and stated that unless you stick to BIOS at or below version A12, you'll get glitchy or corrupt graphics; culprit is Capri framebuffer 0x01660003's default memory size being set to 16MB. Once it is reduced to 8MB, graphics problems disappear. This can be done through binary patching on the Capri framebuffer kext itself or through property injection, which is what you ought to do with OC: framebuffer-patch-enable 1 NUMBER framebuffer-fbmem 00008000 DATA With regards to the patched tables and kexts, I meant those from your previous (or current) installation, be it Mojave or Catalina; basically, you re-use the same stuff.
  23. 1 point
    Kepler-based GT730 is fully and natively supported in Catalina and Big Sur.
  24. 1 point
    Hello guys, I also have HP 840 G3 I installed Big Sur beta 11. I saw a video on youtube, the person used the same laptop. So I used his files and I did not change his files, because is same laptop. But now I can not get Intel Wifi and Bluetooth to work. I really do not understand the kexts files etcetera. Can somebody help me please?
  25. 1 point
    External monitor audio is control from the monitor, not MacOS as are on real Mac computers.
  26. 1 point
    Oh, never heard this (very) old Out Of the Box TLA? You can Google for this sort of things.
  27. 1 point
    Everything Seems to be working almost! (Thanks to @[email protected] [email protected]é..) - The laptop's Trackpad itself and also the Gestures stopped working when updating to Big Sur I uploaded my EFI folder below Because i want the Trackpad working with all the mac gestures, instead of TrackStick usability, I am using this: VoodooPS2Controller-R6Bronxteck.kext: https://osxlatitude.com/forums/topic/8285-refined-alps-touchpad-driver/ Instead of ApplePS2Controller, or this: VoodooPS2: https://github.com/acidanthera/VoodooPS2/releases I updated to the newest version of OpenCore from here: https://github.com/acidanthera/OpenCorePkg/releases I downloaded the Newest Versions of Kexts, and replaced the old ones before the upgrade (from Catalina): Lilu: https://github.com/acidanthera/Lilu/releases WhateverGreen: https://github.com/acidanthera/WhateverGreen/releases VirtualSMC: https://github.com/acidanthera/VirtualSMC AppleALC: https://github.com/acidanthera/AppleALC/releases AirportBrcmFixup: https://github.com/acidanthera/AirportBrcmFixup/releases E7450 OC EFI Backup - OpenCore0.6.3 (Change SN, UUID, MBSN & ROM).zip
  28. 1 point
  29. 1 point
    true , if I use higher than r5122, I can't boot anymore on my dell 5570
  30. 1 point
  31. 1 point
    HibernationFixup should not be required. E7450 normally sleeps & wakes Ok with hibernation disabled (see our FAQ section for details) and proper native CPU power management. Brightness keys should also be fully working with either the DSDT patch detailed in my E7250 guide or the SSDT-BRT6 table provided by JakeLo in numerous threads.
  32. 1 point
    @Justin Wallis, please use the Reply box at the bottom of the pages rather than use the quoting facility to post replies. Former is expected, latter is most annoying. Off-topic, by exception: Apple do not release alpha versions, only betas. So far 11 x betas for Big Sur since June. GM or final release expected next week. End of off-topic.
  33. 1 point
    Specifications: BIOS Version: 01.11.01 Intel 8th gen i7-8550U, 1.8GHz CPU Integrated Intel UHD620 graphics Dedicated Nvidia GeForce 930MX (disabled) 15.6" 16:9 1920 x 1080 pixel 141 PPI, AUO41ED, IPS LED 16GB DDR4-2400 RAM NVME M.2 KXG50ZNV512G TOSHIBA 512GB: Win 10 Home SSD SATA 256GB Toshiba: Catalina 10.15.6 (supported by CtlnaAHCIPort.kext) External USB 3.0 SATA case with Fujittsu MHZ2160BH FF 160GB HDD 5400rpm: Big Sur Beta 4 RTL8xxx Gigabit Ethernet Conexant CX8200 audio layout 21 WiFi Card+BT: BCM94352Z (14e4:43a0), M.2, 802.11ac/b/g/n 2.4/5GHz 867Mbps + BT 4.1, BCM20702A0 chipset 1 x 3.5mm universal jack (combo audio) 1 x USB Type C port 3.1 1 x USB 2.0 ports Type-A 2 x USB 3.0 ports Type-A 1 x HDMI port 1 x VGA port 1 x Realtek RTS522A PCI Express Card Reader Working: All the components except fingerprint sensor (no Touch ID support) Trackpad with full gestures supported | a little bit laggy at time of writing OpenCore 0.6.0 Big Sur Beta 4 (first public beta) Big Sur Beta 5 (20A5354i) installed through software updates Big Sur Beta 6 (20A5364e) installed through software updates Big Sur Beta 7 (20A5374g) installed through software updates Big Sur Beta 9 (20A5384c) installed through software updates DSDT hotpatch: credits RehabMan (since Mojave guide) SSDT patch: credits RehabMan (since Mojave guide), JakeLo, dortania, acidanthera team Many thanks to all osxlatitude team for the great support! PB-450G5-OC060.zip
  34. 1 point
    No, those are needed, do not delete anything. The uuidgen you generate goes into Platforminfo along with serial # etc
  35. 1 point
    You actually don't need to generate a SSDT. SSDT-PLUG.aml is all you need and it'll work for both i5 and i7. No changes needed. If you are using a generated SSDT, then remove SSDT-PLUG. You'll also need to generate a different SSDT for i7. IGPU only model means it only has an Intel HD graphics. Some model comes with discrete graphics like an Nvidia or AMD, which are not supported anyway and must be disable via SSDT patching. If your model has it, it should show in the BIOS under graphics. It is safe to upgrade to the latest BIOS, as the hot patched SSDT are not BIOS dependent. Yes, follow the same BIOS setting from Hervé's BIOS guide. With ApplePS2Controller, you should have 2 fingers scrolling, tab to drag (enable via Accessibility/Pointer Control. Trackstick should work as regular mouse, but with assistance from SmartScroll, you'll be able to scroll with the middle mouse. Not sure what version of VoodooPS2Controller you're referring to. With acidanthera, you probably only have keyboard and touchpad, I don't think it's made for Alps touchpad which is what you have for this model. You'll need the version (same name) by Dr. Hurt, you can find here in this forum or one by 1revenger1 which is another version for Alps you can find in Dortania's OC guide. For me non of the Alps version works well for me. I continue using ApplePS2Controller, only issue with that version is that you'll need to double tab the Caps key to enable and twice to disable. In the end, it's up to you which version works best for you.
  36. 1 point
    hey @Max.1974 I am currently running my laptop on Catalina using the EFI provided. I have the same specs as you but for some reason I cannot get my trackpad to work, What did you do? should I edit my config plist? config.plist.zip
  37. 1 point
    Yes, that's correct. Some cloning software might not clone the EFI partition, so just install Clover and copy the EFI folder over.
  38. 1 point
    Yes and you can look that up, it's well documented in numerous places/threads/posts. Your Crucial model is not affected.
  39. 1 point
    Justin, I tried using OC on an external hard drive with USB caddy. I left my primary internal SSD untouched. I was curious to try OC and it was a good mess, honestly. I recommend you to firstly solve your issues with clover, to read carefully dortania's OC guide (read it all, many times) and finally, if you feel quite brave try to "adjust" your files to OC. I suggest also to test your future OC files using an external drive/stick before trying with your primary drive. But, unfortunately, I'm not able to understand your issue. Apologize
  40. 1 point
    This is for an ASUS ROG Strix Z390-I Gaming mini atx box... I have been able to get Beta 3 (not Beta 4?!?!?) to install using the attached OC EFI configuration. BUT Safari crashes upon launch, even with a bare bones Admin user. Not sure why Beta 4 does not install. Not sure why Safari crashes upon launch. Can someone examine this OC EFI folder and point me in the right direction. EFI.zip
  41. 1 point
    Personally on my T480, it works really well. Well... as well as it can be on a non apple device right. Only thing I have a slight issue with was the 3 fingers drag and drop. You need to keep all 3 fingers slightly apart, if too close, you'll encounter some jumpy movement. For OC, add the kexts in the following order VoodooPS2Controller (acidanthera or Rehabman's version are fine) VoodooPS2Keyboard Plugin from VoodooPS2Controller VoodooPS2Trackpad plugin from VoodooPS2Controller (disable) VoodooPS2Mouse plugin from VoodooPS2Controller (disable) VoodooSMBus VoodooRMI RMISMBus plugin from VoodooRMI VoodooInput plugin from VoodooRMI ( if you have it elsewhere for something else, don't enable it, will cause error, just need one instance of the kext) VoodooTrackpoint plugin from VoodooRMI (this doesn't work as well, but I can't complain since touchpad work really well) Source file: https://github.com/VoodooSMBus/VoodooRMI/releases Note: You might have to check if your touchpad is an SMBUS device https://github.com/VoodooSMBus/VoodooRMI
  42. 1 point
    Using your configuration, the sleep is working... I've modified the configuration adapting it to my laptop (I have DW1560) I tried to understand why my configuration give me this problem but with no result... Now OC it's fully working thank you a lot. OC-E7270 (DW1560).zip
  43. 1 point
    Here's the files I use, no issue with sleep / wake Disable the DW1820a in the Config if you have other wifi devices E7270_OC.zip
  44. 1 point
    OPENCORE Supports Mojave to Big Sur Just replace the entire EFI folder HP840G3_OC_0.6.3.zip Update: Improved touchpad gesture functions: Zoom, left & right swipe, scrolling, etc... Big Sur ready OpenCore v6.0 HP840G3_BigSur_Beta4.zip
  45. 1 point
    Hello all! Here my configuration. Maybe someone will need it. Dell Latitude e7440 (no Fingerprint version) CPU: Haswell Intel Core i7-4600u dual core 4th gen IGPU: Intel Graphics HD 4400 Ram: 16GB DDR3 SSD M-SATA: 256GB Bios: A28 Mac Os: Catalina 10.15.4 Working: full graphics acceleration on Intel HD4400 iGPU, including brightness control (Fn+F3 Brightness up Fn+↓ Brightness up) (with Lilu v1.4.2 + Whatevergreen v1.3.7) multi-display with HDMI audio, including HDMI, (no microphone input) and headset output (with AppleALC v1.4.7 & No Inject audio) GigEthernet LAN connection (with IntelMausiEthernet 2.5.0 kext) wireless and bluetooth with any compatible card (a BCM94352HMB with Airportbrcmfixup.kext v2.0.6, BrcmBluetoothInjector.kext 2.5.1, BrcmFirmwareData.kext 2.2.10, BrcmFirmwareRepo.kext 2.5.1, BrcmPatchRAM3.kext 2.5.1, FakePCIID_Broadcom_WiFi.kext 1.3.15, FakePCIID.kext 1.3.15) All USB ports (3.0) integrated webcam sleep & wake battery management (with ACPIBatteryManager v1.90.1) keyboard and touchpad, max 2 finger multitouch(with VoodooPS2ControllerR6 v6.0.0) SD Card reader Not working: Nothing For Bios settings follow this perfect guide by Hervè (set like this all option that you can find) For create bootable usb/Installation/Post Installation follow this perfect guide by Hervè (just download latest Catalina 10.15.4 from Apple Store) Is better to use the latest clover release, for download it click here You can also follow these steps, starting from the installation of the clover in the usb stick (after the media creation tool process in terminal is done) : Run Clover r51xx.pkg and select USB (Install Mac Os Catalina) as destination Just flag in true on Clover for UEFI booting only, Install Clover in the ESP, UEFI Drivers - Racommended drivers - Install Open terminal and paste: diskutil list Choose your usb EFI partition and type (for example disk1s2): sudo diskutil mount disk1s2 Open Finder and open mounted EFI Replace the EFI folder with this: EFI 10.15.4 e7440 V2.zip Boot from USB and install Mac OS For post-installation repeat the same steps with these differences: Run Clover r51xx.pkg and select your SSD/HHD as destination Just flag in true on Clover for UEFI booting only, Install Clover in the ESP, UEFI Drivers - Recommended drivers - Install Remove all usb sticks and others disk (leave only the target Mac Os disk) and just type : sudo diskutil mount EFI Open Finder and open mounted EFI Replace the EFI folder with the USB EFI Change your serial number in clover configurator SMBIOS section Enjoy your hack! Clover Configurator.app.zip
  46. 1 point
    Last update: 06 Jan 2020 Questions around this Broadcom BCM4350 chipset (in particular the Dell DW1820A) have resurfaced again so I digged into the matter since most people reported it did not work. Outside the model fitted to Apple MacBooks (subsystem id 106b:0131, rev. 05), Wikidevi lists a few cards cards for this chipset, including: Dell DW1820A (several models with different part numbers) Foxconn T77H649.00 (Lenovo part number 00JT494) Lite-on WCBN808B (Lenovo part number 00JT493) All those cards carry PCI id 14e4:43a3 and normally offer high speed 802.11ac wireless + Bluetooth 4.1 services. Broadcom BCM4350 chipset is supported since Yosemite 10.10 and its hardware id is listed in the Info.plist file of IO80211Family's PlugIn kext AirPortBrcm4360 up to macOS Sierra 10.12, then AirPortBrcmNIC since macOS High Sierra 10.13: <key>Broadcom 802.11 PCI</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AirPort.BrcmNIC</string> <key>IOClass</key> <string>AirPort_BrcmNIC</string> <key>IOMatchCategory</key> <string>IODefaultMatchCategory</string> <key>IONameMatch</key> <array> <string>pci14e4,43ba</string> <string>pci14e4,43a3</string> <string>pci14e4,43a0</string> </array> <key>IOProbeScore</key> <integer>1241</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>TruePowerOff</key> <true/> </dict> - - - - - - - - - - Edit: 06 Jan 2020 Removed the warning about DW1820/BCM4350 cards following tests confirming that disabling ASPM does fix the stability issues previously encountered by most users.
  47. 1 point
    Last Update: 06 Jan 2020 Foxconn T77H649.00: Ok Foxconn T77H649.00 appears mostly offered with Lenovo laptops and carries Lenovo FRU (i.e. part #) 00JT494. The cards carries the usual Broadcom PCI id 14e4:43a3 and subsystem id 17aa:075a. - - - - - - - - - - Edit: 06 Jan 2019 This Foxconn T77H649 actually works perfectly with ASPM disabled through additional Clover property injection under the associated device address: Key = pci-aspm-default | Value = 0 | Type = NUMBER ASPM disabling appears mandatory with this card to avoid CPU overloading and system freeze after a few minutes.
  48. 1 point
    Last update: 28 Jan 2020 Dell DW1820A: Ok Ok Ok DW1820A is a pretty good combo card providing 2.4/5GHz 802.11ac wireless at 867Mbps + Bluetooth 4.1. As stated at Wikidevi, there appears to be a few different models of the card. Whilst they all carry the same Broadcom id 14e4:43a3, they each carry a different subsystem id/part #: 1028:0021 (part # CN-0VW3T3) -> 100% Ok with ASPM disabled (originally tested 100% Ok on my Latitude 7490 without ASPM tuning) 1028:0021 (part # CN-096JNT) -> 100% Ok with APSM disabled 1028:0022 (part # CN-096JNT) -> 100% Ok with APSM disabled 1028:0023 (part # CN-0VW3T3) -> 100% Ok with APSM disabled 1028:0023 (part # CN-08PKF4) -> 100% Ok with APSM disabled I acquired a Dell DW1820A a few months ago and was able to play with that card on a Latitude 7490 laptop (fitted with an M.2 2230 Key A+E WLAN slot) that I targeted for Mojave. The model I received was CN-0VW3T3. Before it was later established that not all DW1820A were equal, I purchased a 2nd one and, as it turned out to be, was lucky to receive another 0VW3T3 model. /!\ The 1st thing I want to report is that I encountered difficulties booting my Mojave USB installer and installing macOS with the card plugged in. I had to disable wireless in BIOS to be able to install Mojave. Once it was installed, booting Mojave with wireless enabled in BIOS would cause quite severe lag and performance degradation once at the desktop, as if the card just clogged up CPU ressources. This was because I had not applied any particular tuning for the card and, of course, this was resolved once I implemented the necessary fix detailed below. /!\ Searching through the Web for that DW1820A/BCM4350, I came accross a few forum posts/threads that mentionned: rolling back the Yosemite IO80211Family kext to get the card to work, although with instability and regular KPs removing AirPortBrcmNIC plugin kext from IO80211Family kext, patching AirPortBrcm4360 plugin kext with the id of the DW1820A and installing AirportBrcmFixup kext with a couple of parameters (Credits to Hugotai, cf. his post @Voldemort's place, 2nd Dec 2018) Whilst I did not really contemplate doing the 1st thing, I did envisage the 2nd one and started to look at the differences between Yosemite's version of IO80211Family kext and Mojave's. The main difference I had already noticed was that device id 14e4:43a3 was handled by AirPortBrcm4360 up to Sierra 10.12 and by AirPortBrcmNIC since High Sierra 10.13. Further reading and experimenting showed me that AirPortBrcmNIC kext was the root cause of the problem. Building on Hugotai's success, I seeked to work out an easier solution to bypassing AirPortBrcmNIC kext that would not require kext removal and Info.plist patching but, instead, something that could be implemented through hardware properties injection, either through DSDT patching or Clover configuration. Once Hugotai's solution was verified and confirmed, I worked out the following Clover-based solution for HighSierra/Mojave: identify the IOReg/ACPI device to which the DW1820A card is attached (use IORegistryExplorer app to that effect). Eg: [email protected],yy->[email protected] in the absence of individual ACPI device entry under the PCI bridge for the card, select "FixAirport" ACPI Fix in Clover. That'll create a device "ARPT" @0 under the bridge and that's what you'll inject properties to. This may also require to select "AddDTGP" ACPI Clover fix if your DSDT does not possess any DTGP method. Use Clover Configurator app to that effect. inject the following properties either in DSDT or through Clover (latter recommended): compatibility of the card with Broadcom chips 14e4:4353 or 14e4:4331 that are handled by IO80211Family's PlugIn kext AirPortBrcm4360 ASPM disabling (required for most cards to avoid CPU clogging and system freeze) optionally, add SysProfiler's cosmetic info such as PCIe Slot, card's make and model, etc. and that's it ! Nothing to do to IO80211Family kext or its PlugIns which all remain untouched/unmodified/full vanilla in /S/L/E. It really could not be simpler... NB: if your card's country code absolutely requires to be changed, say for full 5GHz/80MHz operations, add the following steps: install AirportBrcmFixup kext in /L/E + repair permissions + rebuild your cache or inject it through Clover's EFI/CLOVER/kexts/Other add boot argument brcmfx-country=XX (where XX is the target value, eg: US, FR, #a, etc.) to the Boot section of your Clover config but, beware, I found that using AirportBrcmFixup (v1.1.9 at time of writing) with country code other than default's US setting of the card impacted my wireless performance (fluctuating and reduced RX/TX rate). For instance, with country code set to FR (for France), I would not connect at 80MHz on my 5GHz Wireless network, only to 40MHz which resulted in a local wireless connection limited to 400Mbps (vs. 867Mbps) and reduced my overall Internet RX rate by about 60% and TX rate by about 10%: with country code set to #a (to get full 80MHz connection), I could not obtain DFS channel mode to my local router and I noticed fluctuating/unstable RX/TX rates: without AirportBrmfixup, my wireless connection runs solid at 867Mbps and SpeedTest returns a solid TX and RX rates at 300Mbps (i.e. the maximum speed of my Internet connection). Properties injection through DSDT: On my laptop, the DW1820A was found attached to device RP03.PXSX located at IO address 0x001C0002, i.e. 1C,2. The DSDT patch required to inject properties could look like this (devices names will differ from one computer to another of course!): Device (RP03) // PCIe Root Bridge { name (_ADR, 0x001C0002) [...] [...] [...] Device (PXSX) // DW1820A card attached to this device (FixAirport fix required if such device is missing) { Name (_ADR, Zero) [...] [...] [...] Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package () { "AAPL,slot-name", // Optional Buffer () { "WLAN" }, "device_type", // Optional Buffer () { "Airport Extreme" }, "name", // Optional Buffer () { "Airport" }, "model", // Optional Buffer () { "Dell DW1820A 802.11ac wireless" }, "compatible", // Mandatory Buffer () { "pci14e4,4353" // Declares compatibility with BCM43224; "pci14e4:4331" for BCM94331 may also be used }, "pci-aspm-default", // Mandatory for most cards Buffer (One) { 0x00 // Disables ASPM for PCIe device } }) } } } Properties injection through Clover config: An easier alternative is to inject those properties in Clover via Clover Configurator app. This can be done within the Devices section by injecting the desired properties in the Properties sub-section: In the left part, add the PCIe address of the targeted device in the form PciRoot(0x0)/Pci(<root device address>)/Pci(<actual device address>) In the right part, add the above properties in single lines and with the right types (String, Data, Number) For instance, in the case of my laptop, the target device will be PciRoot (0x0)/Pci(0x1C,0x02)/Pci(0x0,0x0) for [email protected]>[email protected],2->[email protected] Then, properties will be injected as lines of keys of 3 x possible types: strings, hex data blocks or numbers. For instance, to declare compatibility with 14e4:4353, the line will consist of Property Key set to compatible, Key Value set to pci14e4,4353 and Key Type set to STRING. The complete properties injection will be: Device = PciRoot(0x0)/Pci(0x1c,0x02)/Pci(0x0,0x0) Key = compatible | Value = pci14e4,4353 | Type = STRING Key = pci-aspm-default | Value = 0 | Type = NUMBER Key = AAPL,slot-name | Value = WLAN | Type = STRING (optional) Key = device_type | Value = Airport Extreme | Type = STRING (optional) Key = name | Value = Airport | Type = STRING (optional) Key = model | Value = Dell DW1820 (BCM4350) 802.11ac wireless | Type = STRING (optional) Once the device properties are injected in Clover or DSDT, there's nothing left to do but reboot the computer. The DW1820A card will then be fully active and capable to connect to 2.4/5GHz networks at full speed. Results: On the Bluetooth side, once the usual Rehabman's Broadcom firmware patching kexts are installed (BrcmFirmwareRepo + BrcmPatchRAM2), the BT4.1 module will be fully operational and capable of supporting AirDrop and Handoff! Links: Clover Configurator app Rehabman's Broadcom Firmware patching kexts Acidanthera AirportBrcmFixup kext - - - - - - - - - - Edit: 06 Jan 2020 Updated with freshly found ASPM disabling property injection that fixes all outstanding stability issues. DW1820A #096JNT and Foxconn T77H649 now tested 100% Ok. DW1820A #08PKF4 should be just the same. - - - - - - - - - - Edit: 28 Jan 2020 Finally got to test a DW1820A #08PKF4 and it's also 100% Ok with ASPM disabled.
  49. 1 point
    Hi all, Specifications Dell Vostro 5568 7th Gen i7-7500U @2.7GHz 8GB DDR4 2400 MHz Memory Intel Graphics HD620 / NVIDIA® GeForce® 940MX 4GB GDDR5 15.6" screen (1920 x 1080) OpenCore Bootpacks Mac OS Big Sur 11.0.1 (OpenCore 0.6.3) OC-11.0.1 Rev A.zip (AppleHDA.kext for audio) OC-11.0.1.zip (VoodooHDA.kext for audio) So far everything works except the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS) Headphone jack not working when fully inserted. Got some audio when halfway inserted. I am very pleased that sleep works and both hdmi and vga ports are working. Two monitors can be connected to the laptop! LOL OpenCore guide and credits mainly to here : OpenCore Install Guide for Kaby Lake Laptop Kexts & ACPI patch files credits mainly to my dear friend @Jake Lo. I migrated these from Clover bootloader. Mac OS Catalina 10.15.7 (OpenCore 0.6.3) OC-10.15.7.zip So far everything works except the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS and using USB WLAN for now) This bootpack is able to boot Mac OS Big Sur 11.0.1 but so far its stuck at "waiting for.. boot-uuid-media...". If anyone managed to resolve this do let me know! @Jake Lo correctly highlighted that Big Sur removed some ports. Using Catalina AHCIPort.kext resolved this issue. Cheers! Clover Bootpacks Credits goes to Bronx Teck, Herve & Jake Lo Mac OS Catalina 10.15.5 (Clover V5119) :- CLOVER-10.15.5.zip Graphics Platform ID injected in order to resolve screen flickering and to get hdmi to work in Mac OS Catalina 10.15.5 Everything works except for the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS and using USB WLAN for now) Sleeps does not work at the moment. Each time attempting to sleep the screen just wakes up. HDMI works. However, during boot up it does not detect the hdmi is connected. Need to manual unplug and replug the hdmi to get mac os to detect it again. Mac OS Catalina 10.15.4 (Clover V5118) :- CLOVER-10.15.4.zip Everything works except for the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS and using USB WLAN for now) This bootpack does not inject any graphics platform-id. Seems to resolve the screen flickering after wake from sleep issue. Using the usual graphics platform-id of 59160000 will cause major screen flickering issue after waking from sleep. HDMI does not work without any graphics platform-id injected. However, with platform-id injected, I have yet to resolve my screen going blank or system hang issues when I connect external monitor to hdmi. Further, injecting the usual platform-id will cause flickering issue after sleep wake. So for now I rather live with no HDMI output so that it can sleep without any screen flickering after wake LOL. Mac OS High Sierra 10.13.6 (Clover V4643) :- CLOVER V3.zip Updated Lilu.kext and all Intel graphics kexts to the latest (these are the final intel graphics specific lilu plugins as whatevergreen will integrate all these plugins for 10.14 onwards) Added 10.13.6 USB port limit patch (By Jake Lo) Disabled eDP port patch which was previously enabled as not needed (By Jake Lo) Added EDID entries (disabled by default) as potential solution to screen flicker after wake. @woaiba15 was able to solve this issue with this injection but I could not replicate it. Enable EDID injection to test it. Mac OS High Sierra 10.13.1 (Clover v4289) :- CLOVER V2.zip Mac OS Sierra 10.12.6 / High Sierra 10.13 (Clover v4241) :- CLOVER.zip Added DellSMBIOSPatch in config.plist to show correct Model Identifier. Some software uses Model Identifier to check hardware compatibility such as AutoCAD 2016 LT (P/s: Thanks Jake for highlighting this just in time when I had problem installing it!) (26 Aug 2017) Fixed distorted sound from headphones on Mac OS Sierra 10.12.6 (31 Aug 2017) Kernel Extension (Kext) in "/Library/Extensions" Folder:- KEXT-10.13.zip (Note: Your will need to repair permission and rebuild cache for /Library/Extensions) Everything works except for the following:- NVIDIA® GeForce® 940MX 4GB GDDR5 (Disabled as cannot work on Mac OS) USB 2.0 Realtek CRW SD Card Reader (Detected but not working) Built-In Intel WLAN Card (Not supported by Mac OS and using USB WLAN for now) Sleep (Screen flickers after waking from sleep for 10.12.6 and screen blanks after waking from sleep for 10.13) Disconnecting HDMI out cable causes blank screen Last Remarks Let me know if the above bootpack works for you. If you managed to get some of the remaining issues resolved, do let me know so that I can update this thread. Cheers!
  50. 1 point
    Following are the features supported by the Smart touchpad driver in Mac OSX: Mouse mode Tapping Dragging Scrolling Swipes Zoom Rotation Clicking and Fingers Press Features Toggle Accidental inputs prevention and Palm detection Apple Trackpad Prefpane support Customization of features Enhanced Keyboard support Support for Asus Keyboard backlight with Idle Auto on/off Prefpane for controlling touchpad features [coming later as its got my least prority] For full details about each feature, check out the respective posts below. Supported OS X Action values to config gestures: 0 : To disable the gesture 1 - Applications Switch 2 - App close 3 - Launchpad 4 - Mission control 5 - Dashboard 6 - Left Space/Full Screen apps switch 7 - Right Space/Full Screen apps switch 8 - Application windows 9 - Minimize app 10 - Toggle Full screen Switch 11 - Backward 12 - Forward 13 - Desktop 14 - Notification center (keyboard shortcut) 15 - Show Properties/Info 16 - Hide/Show Dock 17 - Notification center (soft mode) 18 - Zoom reset (works in Photos, Browser etc., where it supports) 19 - Finder 20 - Force Quit 21 - Right click 22 - Middle click 23 - 34 as F13 - F24 35 - Left click
This leaderboard is set to Amsterdam/GMT+01:00
  • Create New...