Leaderboard

@Mieze@arsradu Hi, thanks for helping me find the solution to my problem. I want to tell you that I actually followed the steps that mieze indicated in post number 1 of this thread, install version 2.3.0d10 of the kext, which is the last version that has mieze of the driver, this was installed correctly and when connecting the ethernet cable still did not recognize the network. I continued investigating in the post that mieze had published and I noticed the incompatibility and the variants that the ethernet interface may have (connectors, cables). the only solution was to change my old network cable for a newer and ready one, it immediately recognized the network and the sleep / wake up behavior worked without problems. I wonder a little the question of the cable, since I have been using it for a long time but they are typical of the apple environment anyway. everything working correctly, thanks to you for answering for being aware of my inconvenience and really that mieze's work is very valuable and I appreciate it very much! They are the best !!!! Thank you !!!!!!!

Supported 0.5.8 on dortania: FixShutdown

Was something local there, had other issues too, ended up reinstalling the OS, and after that it worked fine.

We wish that @n.d.k. is just busy by real life things and wishing him good health

You're most welcome. Glad to hear you've sorted it out. And yes, all the credit goes to Mieze, for an amazing work.

OK, accepted.

@arsradu just clear FV2 ui caches. It is a macOS bug that happens sometimes.

Now made the move to Mojave, all well. (sleep, speedstep, turbo etc), have also overclocked the CPU to 3.8 GHZ. May now experiment with catalina. I know i will have to change the SMBIOS away form the old faithfull macpro5,1 i guess i'll need to be careful to not break the cpu power management.

@hardcorehenry The driver load well in both cases but never establishes a link. Looks more like a hardware problem because the driver is known to work well with chipset 20 and I haven't changed anything which is specific to that device.

You need to carefully read the installation notes and requirements to enable a trouble free install. To change the language, download 'PlistEdit Pro' and open your config.plist with it, go to the NVRAM section (As shown) and change to this value. Good luck.

@Slice the xcpm patch stop working again here (i5 3210m) with this commit. In 10.15.4 + there is an additional check that prevent unsupported cpus to activate it and goto xcpm_mode = 0x00 in the _xcpm_bootstrap: function _xcpm_bootstrap { r14 = *qword_ffffff8000e55100; if (r14 == 0x0) { loc_ffffff8000a9e720("-cpuid", dword_ffffff8000e55108, 0x4, 0x0); _cpuid_set_info(); r14 = dword_ffffff8000e55110; *qword_ffffff8000e55100 = r14; } loc_ffffff8000a9e720("xcpm_pcps", _xcpm_boot_pcps_mode, 0x4, 0x0); rax = *qword_ffffff8000e55100; if (rax == 0x0) { loc_ffffff8000a9e720("-cpuid", dword_ffffff8000e55108, 0x4, 0x0); _cpuid_set_info(); rax = dword_ffffff8000e55110; *qword_ffffff8000e55100 = rax; } rbx = *(int8_t *)(rax + 0x4d); r15 = *(int8_t *)(rax + 0x50); *(int32_t *)_xcpm_cpufamily = *(int32_t *)(rax + 0x1a0); rax = _cpuid_features(); if (rax < 0x0) goto loc_ffffff80004667b5; loc_ffffff80004666ae: if (rbx <= 0x3b) goto loc_ffffff80004666e1; <--- this one needs to be ignored after that (see last line) if the cpu is unsupported it will goes to: *(int32_t *)_xcpm_mode = 0x0; ..and a fake cpu id will be needed. This patch surpass it: for (UINTN i = 10; i < 20; ++i) { if (KernelData[place + i] == 0xC4) { KernelData[place + i] = 0xC6; + if (KernelData[(place + i) - 5] == 0x3B) { + KernelData[(place + i) - 5] = 0x00; + } break; } } Attached modified kernel_patcher.cpp and the entire _xcpm_bootstrap function. kernel_patcher.cpp.zip _xcpm_bootstrap.h.zip

Could be a crash. Please navigate at Clover.app/Contents/MacOS/Clover and run it in Terminal, it should show something.

@haroldju Most likely that's a link error. Clean system caches as described in post #1 of the thread. After that, recreate the kernel cache and your issue should be resolved. @ThExSenatoR First of all make sure to select a medium without flow control and EEE. Second, try another cable and another switch in order to rule out incompatibilities. Another possible reason would be a firmware issue but as there is no documentation, that would be a problem I couldn't resolve. Also ASPM turned out to be a root of much evil. I tried my best to disable it, but some platforms don't let the OS handle it and due to the lack of documentation, I'm at a loss too. If there are ASPM related settings in your UEFI setup, select a setting which allows the OS to control it. Mieze

Sorry I don't. It was one of those situations, it was 2 am, and I thought "let me just update this confirm it still boots, and go to sleep." At 4 am I was still trying to see what I could change in the Bios that might be causing the KP. Luckily, the ASUS flashback button and USB flash drive allowed me to go back to 2002, which I did after a semi sleepless night/morning. Are you getting any UNSYNCRONIZEDTSC errors with your setup? Everything works, except for those errors, which is affecting overall performance, again on 10.13, 10.14, and 10.15. 10.15 is the only OS that recognizes the CPU, but I get the errors on all. It's aggravating that my i7-3820 X79 Rampage IV Gene is still more efficient overall than my current setup.

Please do not reply to UNRELATED topic and start your own new topic. You keep on doing this constantly. You replied to a topic about hot keys BUT started discussing your personal issue that is totally unrelated (regarding bootmgfw.efi) . If you are trying to direct attention for your topic to a particular forum member then use for example @ameenjuz. As soon as you start typing @.... a list of members names will appear and you then click on the correct person's name like I did above for your name.

Dude your shocking me if you don’t understand why that’s not a good idea. noo nothing will break but it’s a fake overclock and it’s that simple. you might as well get a bit of A4 paper and write your number on that and then claim that’s what your Oc is, just as fake.....lol

Thanks. Yes, I know only the small icon should appear, but it wasn't appearing, and I thought the problem is because it wasn't installed. But actually the problem was something else with the OS on that system.

Nothing happen except a small clover icon in menu after some delay.

Is it possible to run Clover.app after compiling without installing to the system? I thought to try that on some other computer, and after compiling, I tried to run CloverApp/build/Clover.app, but nothing happens. It doesn't start or display anything (note: it was never installed before on that system)

You have the kernel debugging turned on. Check nvram arguments (or ones in the config.plist?) and clean anything related to debugging like "debug=0x44 kcsuffix=development” if any, in short: sudo nvram -d boot-args and readd any needed bootArgs (but I guess you already have them in the config.plist?) then try with: sudo rm -f /System/Library/PrelinkedKernels/prelinkedkernel.de* then sudo kextcache -invalidate / then sudo touch /System/Library/Extensions && sudo kextcache -u / reboot and see if something changed.

@TalkingHead There is no bug, the driver is working as specified. The root of the problem is located in your DHCPv6 configuration. The option kIONetworkLinkNoNetworkChange tells the network stack to skip renewal of the DHCP leases after wakeup because the has been no change. This speeds up wakeup and has been designed to work that way. It's only used when WoL is enabled, a valid link was established while the machine went to sleep and the link is still up when it wakes up. I tested this option intensively years ago when I implemented this feature and I use it in my network without any problems since then. In case you are experiencing problems, best option would be to fix DHCPv6, in case you can't do that, disable WoL on your machine and everything will be fine. Mieze

Take Clover release and install it official way. Drag CloverConfigurator to trash before.

using clover works for up to yosemite(works in el capitan too but sleep and shutdown don't seem to be working) use smbios macbookpro6,2 don't generate c-states don't generate p-states don't drop oemssdt should only have DSDT in the patched folder(if patched)

hi did you consider putting -v in your boot to see what exactly succeed and what did and for how much