Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/16/2020 in all areas

  1. @Slice, what if the Wiki run inside Clover.app, or even better the wiki can also edit the config.plist so that explanations will always be visible?
    4 points
  2. I reworked chip identification in version 1.0.0d6 to fix the issue. Attached you'll find debug and release builds for Mojave and Catalina. Mieze LucyRTL8125Ethernet-V1.0.0d6.zip
    2 points
  3. Glad to see something new here.
    2 points
  4. This project is dedicated to Lucy, my lovely little Tyrannofelis Rex. LucyRTL8125Ethernet is an open source driver for the Realtek RTL8125 family of 2.5GBit Ethernet controllers. Key Features of the Driver Supports all versions of Realtek's RTL8125 2.5GBit Ethernet Controllers found on recent boards. Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). TCP segmentation offload over IPv4 and IPv6. Support for TCP/IPv4, UDP/IPv4, TCP/IPv6 and UDP/IPv6 checksum offload. Supports jumbo frames up to 9000 bytes (strongly recommended for 2.5GBit operation). Fully optimized for Mojave and above. Note that older versions of macOS might not support 2.5GB Ethernet. Supports Wake on LAN (untested). Supports VLAN (untested). Support for Energy Efficient Ethernet (EEE) which can be disabled by setting enableEEE to NO in the drivers Info.plist without rebuild. The default is YES. The driver is published under GPLv2. Current Status The driver has been tested successfully under Catalina (10.15.4 and above) and, according to first tests, is working stable. I haven't experienced any Kernel Panics during my tests and is working stable on my primary work machine. The driver has been designed to work with Catalina but might also work with Mojave, provided you build from source with Xcode 10.. Please keep in mind that support for 2.5GBit Ethernet was introduced in Mojave (or maybe High Sierra?) so that there is no way to make it work with Sierra or below. Known Issues Using autoselect medium it seems to prefer negotiating a connection speed of 1Gbit with my switch so that I had to select 2.5GBit/s manually in order to achieve this speed but it might be different with other switches. This problem has been resolved in version 1.1.0. Installation You might want to install the driver to /L/E as usual but it's also ok to use Clover's or OC's injection function (installation in the EFI folder). Use your favorite kext installation tool for installation or perform the installation manually (for Clover or OC injection). It's your call! Help - I'm getting kernel panics! Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches. As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches: Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again. Troubleshooting Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog Version 1.1.0 (2021-04-29) Changed version number to 1.1.0 to make it an official release. Version 1.1.0d12 (2021-04-25) Updated Linux sources to 9.005.01. Fixed auto-negotiation for all speeds (including 2.5 Gigabit). Added support for adaptive poll interval in 2.5 Gigabit mode. Version 1.0.0 (2020-08-14) Changed version number to make this the first official release. Version 1.0.0d6 (2020-06-14) Fixed chip recognition. Version 1.0.0d3 (2020-04-20) First working development release. Getting the driver Source code can be found on GitHub: https://github.com/Mieze/LucyRTL8125Ethernet You'll find the lastest prebuilt binary in the download section: https://www.insanelymac.com/forum/files/file/1004-lucyrtl8125ethernet/
    1 point
  5. Some boards do not have a visible option for CFG Lock. For those cases the Bootloaders offer options to not write to the MSR. An other way is to disable CFG Lock in the BIOS despite the fact that there is no option available in the user interface. One way to do so is to use UEFITool, ifrextract and a patched Grub. Which is not only cumbersome, also it will work only, if the storage used for CFG Lock is in a certain varstore. Generally speaking CFGLock.efi does what those tools do, but the only user interaction needed is to confirm that you want to toggle the CFG Lock value (on to off/off to on) and it works regardless where the CFG Lock option resides, as long as the BIOS has a CFG Lock option - hidden or not - in their HiiDatabase. It is an EFI Application. Install it in the Tools folder of your OpenCore EFI and enter it under Misc->Tools in the config.plist. The EFI must not be able to boot MacOS, it must just be able to show the picker. It should also run as an application from the UEFI shell, but I haven't tested this. CFGLock.efi.zip
    1 point
  6. Hi, I've created a new GUI agent application to assist Clover bootloader. Its name is "Clover.app". Made to run in 10.9 and newer. What it does (or should do)? Give prominent info about the current revision in use, the Boot Device (disk where Clover is) and the the config.plist used. Install Clover in UEFI and legacy mode with a new way to store preferences and with out a pain searching for the correct ESP. Prevent target like Catalina-Dati from another OS (and ruin it) or read-only volumes, as this is not allowed. Provide essential NVRAM management for most used things such Theme and sound used. Ability to search any (correctly formatted) ESP in the system and mount/open them. As well the ability to umount. Auto mount for the chosen ESP. Get rid of RC Scripts... Yes, no more, just a new daemon (CloverDaemonNew) written in Swift and controllable by the NVRAM. Dump the nvram in the ESP, boot device takes precedence, otherwise the first available Internal) EFI System Partition. Root partition as last resource. Easily read the boot log (and the daemon log.. w/o mess the System log). Checking for updates whithout installing preferences panes here and there: just one app. Themes Manager embedded which doesn't require git to be installed. About installing drivers Unlike the package you have more control about what you are installing: Selected drivers are just the mirror of what is it really present in your EFI/CLOVER/drivers folders, and in fact, checkboxes get activated only if the driver is really present. Unknown drivers, i.e. ones not included in the current installer, are listed as well. Of course the app will not be able to update drivers that doesn't own. Be aware that deselecting a driver means (unlike the pkg) to delete the driver! A back up is always made to ~/Desktop/CloverBackUp/ .. so you can handle the back up immediately by your self. Warning: old drivers64 and drivers64UEFI directories aren't taken into account, only new ones (drivers/UEFI and drivers/BIOS). For some time the package was updated to migrate old directory structure to a new one with also the renaming of drivers with the old -64 suffix (as Clover is 64-bit only for some time.. so no need to specify again and again). Clover bootloader Updates Updates are online, but will show up only if the online version is greater then installed one. Based on the update intervall you set in the GUI, otherwise monthly as default. Clover.app Updates When a new release will be published it will appear a window that will inform you about it. Based on the update intervall you set in the GUI, monthly as default otherwise. Testing Clover.app is in a Beta stage, and is going to be promoted as "stable". Update: installation of legacy Clover looks really good. (thanks to @Rodion2010 for testing the installation) Update: since v1.11 is now compatible with 10.9 Mavericks and newer. Tested in 10.9, 10.10, 10.11, 10.12, 10.14 and 10.15. As soon someone will test successfuly it in 10.13 the Beta stage will ends. But why waiting for a test in 10.13.. there are problems otherwise? No, no problems. The code is written in swift 5 (whith stable ABI) and I did not expect something different for the code I wrote, but the difference can reside in the Cocoa.framework shipped with the OS: starting in 10.10 Apple introduced some new stuff for the interfaces like dark mode, Visual effect views (with vibrancy appearance) and problems can reside because many Apple-bugs where introduced and only fixed later. For this some graphical issues can show up (like a dark background with a dark text where you are able to see nothing). In the mentioned OSes all is fine (or at least perfectable), so just High Sierra is missing .... FAQs How to find the correct partition to update/install Clover? When you select a disk, the one with the Clover image... is the partition where Clover started. Easy no? Why you can't see other disks under "Mount (ESP)"? Because there, the app show only ESPs (EFI System Partition) and if a disk did not show up here... it's because the partition you are looking for is not an EFI System Partition. Why you can't see all the partition you have in the Installer? Because to install Clover it's required a filesystem to be FAT16, FAT32, EXFAT or HFS. Other ones are simply not taken into account. Example: if your ESP is formmated with FAT16 filesystem, BIOS options will not get activate because Clover doesn't have boot secotors for the ol fat filesystem! Warning, FAT16 can be good for UEFI loading, but for example my firmware simply ignore it. FAT32 is higly recommended for ESP, you're warned. What Make filesystem read-write" does? It is irreversible? This function add an nvram key that the daemon can read when the system starts so that can made the filesystem writable, if isn't, by invoking "mount -uw /". As you know starting from 10.15 the root filesystem is read-only and this functionality can help if you want to write to the System partition, like the case if you want to disable the Bonjour Sleep proxy Client, or to dump the nvram in / using EmuVariableUefi.efi, or using kexts like HibernationFixUp. It is a permanent change? No, mount -u means update an already mounted file system, so disabling the functionality the filesystem will stay as per default. The change is applied at next start up. What does "Disable Sleep Proxy Client? If your computer wake itself from sleep each n hours it's probably due to the Bonjour service called "Sleep Proxy Client". If you don't want this to happen you may want to disable it. In 10.15+ this functionality require the filesystem to be writable to add a special argument to the mDNSResponder launch daemon. By disabling the checkbox the service get re-enabled as per default, but then will require a read-write filesystem, at least for the next reboot. Note: if the filesystem is not writable the daemon will try to make it read-write to do the modification even if "Make filesystem read-write" is turned off. CloverDaemonNew is a complete replacement for the RC Scripts? Yes. It does every things done by rc scripts but without installing additional scripts into the System directories. Warning: the CloverDaemonNew is not compatible with old rc scripts and for this reason, since v1.07, Clover.app remove them. For the same reason the package remove CloverDaemonNew if you install back the rc scripts (since commit d447228 of november 29 2019). Big thanks to @Sherlocks for helping me to make it work. Themes Since v1.15 Clover.app has a Theme Manager. Unlike CloverThemeManager.app git is not mandatory, and in fact it doesn't use it. The requirement it is a Github repository instead. The main repo for Clover.app is https://github.com/CloverHackyColor/CloverThemes but the app allow you to chose a fork by specifying the GitHub user name and the GitHub repository name: A requirement for users repository is that your will contains themes in the root of it, and not in a sub directory. After themes are indexed (if you ever run the Theme Manager) a list of all themes is listed below: (You can type anything you want, and auto completion is available) ..so you can switch the theme to use by set its name in NVRAM. This way Clover override what is set in the config.plist. Sound Since v1.13 (with Clover r5102+) Clover.app is able to handle the volume level and the device for the the start up sound: No sound? Ensure the volume is audible (100%) and the device it is really connected to speakers. Of course your theme must contains the sound file. How to install Clover in UEFI only? Simply by not selecting "CloverEFI" (which means legacy Clover) and without play with MBR/PBR (Master Boot Record/Partition Boot Record). "CloverEFI" it's replaced by "BIOS". How can you install Clover in legacy mode? Simply by selecting "CloverEFI" (which means legacy Clover). MBR/PBR (Master Boot Record/Partition Boot Record) must be enabled the first time to make your disk bootable, and when this happened once there is no need to install boot sectors again. "CloverEFI" it's replaced by "BIOS". "Alternative boot" means that the installer will installs more then one boot loader you can chose by pressing the relative number (boot3, boot5, boot6, boot7, boot9) while booting. To do that the installer use a special boot 1 sector that wait 2 seconds to wait you for a key to be pressed. kernel panic installing bootsectors to a hfs partition (Clover legacy) During my tests with Clover.app I run in to a kernel panic installing boot sectors in a hfs formatted pen drive (and I realize some users had already run into this problem with the pkg) . After studying the problem, the conclusion is that the hfs driver panics when the journaling is enabled, so Clover.app take the step to disable the journal just before the installation. Of course the app re enable it as soon sectors are installed. Will the package installer no longer be supported? No. The package is still supported, also because Clover.app doesn't support old OSes like 10.8, 10.7 etc. and older. However the pkg has reached some limits by installing on Catalina. Can the Clover updater coexist? Yes, but why? With the package you have to install Clover to update them (in all partitions you have) to get access to it. With Clover.app you need only one app for all, ok, unless you have really old OSes. The Clover preferences panel? The idea is that you have every things you need by make Clover.app run at login. In how many languages it is translated? Actually in English (me) Italian (me) Russian (Slice) Portoguese (artur_pt) Korean (Sherlocks) German (Mork vom Ork) Simplified Chinese (Steve Zheng) Indonesian (Badruzeus) Serbian (crusher) French (Ellybz) But it can be translated in any language supported by macOS, so just start translating the en.strings and post the file here. Or make a pull request at github. Is it open source? Of course yes! Changes committed at github. How to compile? Xcode 11+ and swift 5+ both required. buildme do it for you. Last Release here
    1 point
  7. Please sell this site to someone who will fix it. Hell, I'll buy it. Just don't let this place continue to wither and die like it's doing right now.
    1 point
  8. Yes it works perfectly. i have the WiFi version and am using Mojave, and the latest OC works. Just be sure to edit relevant parts (serial number, etc.) I also had to add some things in order for my particular WiFi/Bluetooth card to work.
    1 point
  9. Sorry to ask the obvious, although your pics shows the card, I dare say it came with compatible aerials for attachment and boosting the signal because the last but one pic shows the card is recognised and functioning correct - Examples: Bluetooth Low Energy Supported: Yes, Handoff Supported: Yes, Instant Hot Spot Supported: Yes. So as far as I can surmise the possible fault could be inadequate aerials or none at all.
    1 point
  10. Thank you very much @hardcodehenry, that worked!! Now would be nice to figure out how can we implement that into an SSDT! But that's business for another day, I think everyone will be happy with the improvement!
    1 point
  11. 1 point
  12. Renaming _STA to XSTA is tricky, you have to rename it only in H_EC device by adding in patch count 1 and skip value(you have to count yourself). Post your untouched DSDT.aml(dumped via OC debug or acpidump.efi or clover(F4)) up to you.
    1 point
  13. It's possible you need to disable original _STA in Device (H_EC) via rename _STA to XSTA and add this modified SSDT-EC-USBX.aml SSDT-EC-USBX.aml
    1 point
  14. Yes, this is VMware Workstation Pro on Windows 10 Pro x64. Each time a new version of Workstation was released I simply accepted the automatic prompt to upgrade, then re-ran the MK Unlocker afterwards. Didn't do anything fancy other than that. As for macOS installation media, from Lion through to Catalina, I've been making my own ISO images for several years now by downloading the associated .dmg direct from the Apple Store and using the command line to create a bootable ISO.
    1 point
  15. Still only in my mind yet, but I'll start working on it
    1 point
  16. Hi yes there is and old npci=0x2000 trick fixed it, everything now seems to be working perfectly except kernel panic on AppleACPIPlatform on wake, working on it now.
    1 point
  17. hi weg I think should have renamed your H_EC to EC or you have to doit but once oc did it you can't have ssd looking for H_EC because it is already renamed so you have rename ssd by hand by replacing H_EC to EC so that that SSDT should do it what ever it supposed to do now I am sure there are more knowledgeable people who will tell you what to do this is just my 2 cents worth by the way AAPPLE doesn't understand H_EC but only EC hence all of the renaming goes on
    1 point
  18. Hello @vit9696 I have been recently setting up the new NUC10i7FHN with latest OC 0.5.9 (which works) everything is working but there is no way to disable device AppleACPIEC via SSDT, the original BIOS contains PNP0C09 under device H_EC, everytime I try to disable it with the following code DefinitionBlock ("", "SSDT", 2, "ACDT", "SsdtEC", 0x00001000) { External (_SB_.PCI0.LPCB.H_EC, DeviceObj) Scope (\_SB.PCI0.LPCB.H_EC) { Method (_STA, 0, NotSerialized) // _STA: Status { If (_OSI ("Darwin")) { Return (0) } Else { Return (0x0F) } } } } It throws a KP at boot, I still haven't had this issue with any other build, so I'm a bit lost... To me it seems that H_EC on original DSDT is not loading, see code: Scope (_SB.PCI0.LPCB) { Name (ONEW, Zero) Device (H_EC) { Name (_HID, EisaId ("PNP0C09") /* Embedded Controller Device */) // _HID: Hardware ID Name (_UID, One) // _UID: Unique ID Method (_CRS, 0, Serialized) // _CRS: Current Resource Settings { Name (BFFR, ResourceTemplate () { IO (Decode16, 0x0062, // Range Minimum 0x0062, // Range Maximum 0x00, // Alignment 0x01, // Length ) IO (Decode16, 0x0066, // Range Minimum 0x0066, // Range Maximum 0x00, // Alignment 0x01, // Length ) }) Return (BFFR) /* \_SB_.PCI0.LPCB.H_EC._CRS.BFFR */ } Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) ^^^GFX0.CLID = 0x03 Return (Zero) } Here is where I'm a little confused, there is a Return (0x0B) and then a Return (Zero) under STA, system boots as is without trying to disable H_EC but loads Kernel Extension ACPIEC.. Here is a pic of the KP, which seems to me like the one I had on my X299X designare till RTC0 SSDT was made, I have tried with it and AWAC too, but nothing happens.. Could you shed some light here? Many thanks in advanced!
    1 point
  19. I still have to refresh every page 3 times before i can access it, using latest firefox... Certificate issues
    1 point
  20. @Brumbaer Thanks for tracking down this bug to it's origin. I'm going to rewrite chip recognition from scratch next week because Realtek's solution is not only confusing but also extremely ugly.
    1 point
  21. Version 2.0.8

    732,694 downloads

    Mac OS X Unlocker for VMware V2.0 Please ask questions in this thread http://www.insanelymac.com/forum/topic/303311-workstation-1112-player-712-fusion-78-and-esxi-6-mac-os-x-unlocker-2/ 1. Introduction Unlocker 2 is designed for Workstation 11, Player 7, ESXi 6 and Fusion 7. If you are using an earlier product please continue using Unlocker 1 Version 2 has been tested against: Workstation 11/12 on Windows and Linux Player 7 & Workstation Player 12 on Windows and Linux Fusion 7/8 on Mavericks and Yosemite ESXi 6.0 The patch code carries out the following modifications dependent on the product being patched: Fix vmware-vmx and derivatives to allow Mac OS X to boot Fix vmwarebase .dll or .so to allow Apple to be selected during VM creation Fix libvmkctl.so on ESXi 6 to allow use with vCenter Download a copy of the latest VMware Tools for OS X Note that not all products recognise the darwin.iso via install tools menu item. You will have to manually mount the darwin.iso for example on Workstation 11 and Player 7. The vmwarebase code does not need to be patched on OS X or ESXi so you will see a message on those systems telling you that it will not be patched. In all cases make sure VMware is not running, and any background guests have been shutdown. The code is now Python as it makes the Unlocker easier to run and maintain on ESXi. There are some challenges to write the code as ESXi has a subset of Python 2.7 which constrains some modules that can be used. 2. Prerequisites The code requires Python 2.7 to work. Most Linux distros, ESXi and OS X ship with a compatible Python interpreter and should work without requiring any additional software. Windows has a packaged version of the Python script using PyInstaller, and so does not require Python to be installed. 3. Limitations If you are using VMware Player or Workstation on Windows you may get a core dump. Latest Linux and ESXi products are OK and do not show this problem. IMPORTANT: If you create a new VM using version 11 hardware VMware will stop and create a core dump.There are two options to work around this issue: 1. Change the VM to be HW 10 - this does not affect performance. 2. Edit the VMX file and add: smc.version = "0" | 4. Windows On Windows you will need to either run cmd.exe as Administrator or using Explorer right click on the command file and select "Run as administrator". win-install.cmd - patches VMware win-uninstall.cmd - restores VMware win-update-tools.cmd - retrieves latest OS X guest tools 5. Linux On Linux you will need to be either root or use sudo to run the scripts. You may need to ensure the Linux scripts have execute permissions by running chmod +x against the 2 files. lnx-install.sh - patches VMware lnx-uninstall.sh - restores VMware lnx-update-tools.cmd - retrieves latest OS X guest tools 6. Mac OS X On Mac OS X you will need to be either root or use sudo to run the scripts. This is really only needed if you want to use client versions of Mac OS X. You may need to ensure the OS X scripts have execute permissions by running chmod +x against the 2 files. osx-install.sh - patches VMware osx-uninstall.sh - restores VMware 7. ESXi You will need to transfer the zip file to the ESXi host either using vSphere client or SCP. Once uploaded you will need to either use the ESXi support console or use SSH to run the commands. Use the unzip command to extract the files. <<< WARNING: use a datastore volume to run the scripts >>> Please note that you will need to reboot the host for the patches to become active. The patcher is embbedded in a shell script local.sh which is run at boot from /etc/rc.local.d. You may need to ensure the ESXi scripts have execute permissions by running chmod +x against the 2 files. esxi-install.sh - patches VMware esxi-uninstall.sh - restores VMware Note: 1. Any changes you have made to local.sh will be lost. If you have made changes to that file, you will need to merge them into the supplied local.sh file. 2. The unlocker runs at boot time to patch the relevant files and it now survives an upgrade or patch to ESXi as local.sh is part of the persisted local state. 8. Thanks Thanks to Zenith432 for originally building the C++ unlocker and Mac Son of Knife (MSoK) for all the testing and support. Thanks also to Sam B for finding the solution for ESXi 6 and helping me with debugging expertise. Sam also wrote the code for patching ESXi ELF files. History 12/12/14 2.0.0 First release 13/13/14 2.0.1 Removed need for Python for Windows 13/13/14 2.0.2 darwin.iso was missing from zip file 02/01/15 2.0.3 Added EFI firmware files to remove Server check Refactored Python code 07/01/15 2.0.4 Added View USB Service to Windows batch files Fixed broken GOS Table patching on Linux 18/06/15 2.0.5 ESXi 6 working Latest tools from Fusion 7.1.2 20/06/15 2.0.6 ESXi 6 patch for smcPresent vCenter compatibility 16/09/15 2.0.7 Workstation 12 on Linux fixes 14/11/15 2.0.8 Player 12 on Linux fixes Get latest VMware tools command Removed firmware files Moved to PyInstaller 3.0 © 2011-2015 Dave Parsons
    1 point
  22. this is not working as it is a 32bit app. "..needs to be updated by the developer" message of Catalina fame
    0 points
×
×
  • Create New...