Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/17/2020 in all areas

  1. Run this program you have ➤ release V5 here don't reboot after install then run again choose Uninstall then reboot Voila
    4 points
  2. Oh boy here we go again... right now that I expected the final release of macOS BS, one more beta... all right let's do it, then...
    3 points
  3. I saw that on your screenshots on I don't know why. A switch back to console we should do before starting a verbose boot, I guess. At least one can boot !!! Don't know why the long stop. OC says your kexts are injected fine. The problem, from here, is that I have to compile an EFI, send it, someone try, send back log. That'll probably happens not only once ! Who's up for that ?
    3 points
  4. Update installed via software update. Everything works as before. Felt some animations have been sped up. Sleep still does not work on both my systems.
    2 points
  5. @ITzTravelInTime Here you have Both original and patched dsdt, i can't really tell you what is what does not let you boot since i've been using this board for almost 1 year and i patched my dsdt on catalina where i didn't have problems to boot but when I do not use my dsdt (disabled) the crashed are related to IOPCIFamily and NVMe M.2 port (which is PCI as well) and also using a Adata S11 Gamix NVMe disk (which is recognized natively by the OS as supported and gets trim without forcing it, i've teste it on a IMac pro using an adapter) DSDT-ORIGINAL.aml DSDT.aml
    2 points
  6. This project is dedicated to the memory of Mausi, the cat I loved more than anybody else. A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports: 5 Series 82578LM 82578LC 82578DM 82578DC 6 and 7 Series 82579LM 82579V 8 and 9 Series I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0) I219LM I219V 200 Series (since V2.3.0d0) I219LM I219V 300 Series (since V2.4.0d0) I219LM I219V 400 Series (since V2.5.1d1) I219LM I219V Key Features of the Driver 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). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled due to hardware bugs). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2. Current Status The driver has been tested successfully with I217V, I218V, I219V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and newer versions of macOS. Known Issues There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer. FAQ Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5. Installation Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface. 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 "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "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. Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000. 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 2.5.0 (2019-10-15) Reworked interrupt throttling code and added new configuration parameters. Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8 Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
    1 point
  7. 1 point
  8. update went well for my hack. (ie turned on update went to the bar come back job done)
    1 point
  9. on my AMD T-RyZo in fact I still haven't been able to upgrade; When you select macOSinstaller from the GUI, it crashes immediately... tried to change booters quirks, tested new kernel patch, but so far nothing
    1 point
  10. I don't know that the kernel has changed I've had different news I've heard that so far no one has been able to install this update on AMD, but until I propose it... I don't have any answers
    1 point
  11. Si pero gracias a Maldon, mi pena es que tengo la vista cascada pero bueno siempre fui bueno con el método prueba/error ahí cuesta mucho que me quede sin ideas y le doy a todo mil vueltas antes de rendirme, lo que he averiguado y se de Open Core esta a tu disposición cuando tu quieras, ahora lo conozco bastante bien creo yo.
    1 point
  12. Yes absolutely, do a time machine backup if you like and then clean install big sur and then restore your backup and your be golden. Its also fine to just upgrade but not as clean but still perfectly fine to do
    1 point
  13. Muchas gracias!!! He estado unos años algo lejos de este mundo y aguantando con la placa P55-USB3 de la que no me puedo quejar pero hace 1 mes cambié a una Z390 con i3 de 9 generación. Y he vuelto a meterme en esto y a leer y a aprender cosas nuevas como lo reciente de clover, nvram, puertos usb, etc. Lo que todavía no he tocado es open core. Veo que tú te has actualizado más aún, con chipset H410 y micro de 10 generación. Y además big sur beta! En fin, que me alegro de verte por aquí y te deseo que disfrutes al máximo con tu equipo nuevo. Un abrazo.
    1 point
  14. Yes it works just fine with Big Sur but only OpenCore not Clover as of yet.
    1 point
  15. Hey guys and gals, do you know you can use HWMontior on your Macs. Displays **** of stuff Give it a try, its free
    1 point
  16. https://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwjHm76ApvDrAhUVcCsKHdXgArwQFjAAegQIAxAB&url=https%3A%2F%2Fhackintosher.com%2Fguides%2Fhwmonitor-hackintosh-guide%2F&usg=AOvVaw0iUnw3FX_PTHy8EnCM-hyj
    1 point
  17. Sorry, wrong EFI sent. Try this one please. CloverX64.efi.zip
    1 point
  18. Having exact same stuck screen with my attempt to use "Oc Libs" with different project. Got same result while loading Oc with bcfg cmd with no Bootstrap. Something like: - Oc failed to get SmBios table from SystemConfigurationTable because it run to early, that I already resolved. - They lost "Virtual FileHandle"? - OpenRuntime is not running / running late after boot.efi already loaded? * No idea whats going on there
    1 point
  19. Solved AR9565 Wifi thanks to a tutorial I managed to activate it, now it works perfectly with Big Sur
    1 point
  20. Stopping at that location could mean an issue with kext injection - as that's normally where OC would do it at.
    1 point
  21. These are the small difference between Gcc and Xcode. Committed. @Matgen84 The second problem you had happens to me randomly. I'd say 1 time out of 10 on a x220 and 1 time out of 4 on VMWare. Don't know yet what it can be. Either a bug in OpenCore or a setting (slide setting ?). I also have different behaviour after boot failed. Sometime even go back to Clover menu. This beginning seems normal. I have the same, then a stop for 2 seconds. If you activate debug in Clover, you should also have an OpenCore debug log. It's in EFI folder, not in EFI/CLOVER folder. Unfortunately, stopping here is something that never happens in my tests.
    1 point
  22. Wouldn’t be easier to get IOReg from real iMacPro and check/compare device-ids[(device by device) and “fix” them(either with gfxutil(config.plist>DeviceProperties>Add) or SSDT-hotpatches]? Only suggestion, ignore if it doesn’t make sense.
    1 point
  23. Yes, I used CloverX64.efi you posted as you may see from my log. I have DBG("Self...." but on the screen because it happens before bootlog inited. The error tells that static_assert must have a message. Can be resolved somehow as static_assert(sizeof(gSettings.ocBooterQuirks) == sizeof(mOpenCoreConfiguration.Booter.Quirks), "sizeof quirks wrong");
    1 point
  24. Updated for 0.6.1 Warning : I tried to put in the latest version of Lilu and plug-ins .. would hang at boot. So I left them the same as in 0.6.0.
    1 point
  25. I am attaching the original tables of my motherboard Huananzhi X99 F8 from AIDA64. You can compare. In the system, I use a custom dsdt with additional ssdt tables. Tables X99.zip
    1 point
  26. Is a pity the same result. Except 3.5 seconds before start Clover 0:100 0:000 Clover : Image base = 0x4BBF3000 3:600 3:500 3:600 0:000 Now is 16.09.2020, 19:01:50 (GMT) 3:600 0:000 Starting Clover revision: 5122 (opencore_integration, commit 346661efd) on American Megatrends EFI 3:601 0:000 Build with: [Args: --gcc53 --target=DEBUG --define=DEBUG_ON_SERIAL_PORT -n 9 | build -D DEBUG_ON_SERIAL_PORT --conf=/JiefLand/5.Devel/Clover/Clover-projects/Clover--CloverHackyColor--opencore_integration/Conf -D USE_LOW_EBDA -a X64 -b DEBUG -t GCC53 -n 9 | OS: 10.14.6] 3:601 0:000
    1 point
  27. It works, i get the FWHD device into ioregistry explorer but i still got the same kp, i will continue to look at the differences beetwenn the dsdt of my system and the working one and see if there is anything else in need of a patch
    1 point
  28. I was able to boot with this kext. Remember, kext for Big Sur has to be in folder named "11". 11.zip
    1 point
  29. the question is, why do you commit to hardware from 10 years ago and beyond to be able to start old versions of macOS, where it would be enough to chameleon-enoch-clover, and not instead recent AMD hardware? I understand that apple has never used amd, but it has never even used certain intel hardware with which so many assemble hacks.
    1 point
  30. Always the same having 3 EFI in the Z370 hack EFI --> Clover bootloader default EFI3 --> OpenCore EFI2 --> bootloader windows I inserted in EFI 2 the CLOVER folder of the EFI, and added the entries in the BIOS, so that I could be freer for experimentation.... but as written on top.. always doesn't get out of the initial memory manager do
    0 points
  31. Hey STLVNUB, What's that? A sort of spam?
    0 points
  32. Hi @Jief_Machak, just tested your last CLOVERX64.efi build, unfortunately I got same screen just like @mifjpn tested on second system from my signature Acer Aspire A315-53 removed OCQUIRKS.EFI and used your KEXT from 11.zip
    0 points
×
×
  • Create New...