Jump to content

[Solution] "does printf work?" freeze with osxaptiov2


Krim404
 Share

24 posts in this topic

Recommended Posts

I had this issue after upgrading to 10.13.2 - Clover stops with the cryptic error message "does printf work??" and completly freezes the system.

i googled the issue, only found error reports - sadly no solution (except removing aptiov2).

 

The issue is triggered whenever the prelinked kernel is defunc. osxaptiov2 triggers this message, while the older osxaptiov1 (and hence the free2000 version) works fine.

This happens for ex. after a timemachine recovery.

 

EDIT: It seems like this is the "Error - requested memory exceeds our allocated relocation block" error. In a newer clover test build it seems to be corrected.

 

Easiest solution (in case it worked before):

boot in recovery mode, remove old kext cache and prelinked kernel, force kext cache rebuild and reboot - twice.

sudo -s
rm -f /Volumes/VOLUME/System/Library/PrelinkedKernels/prelinkedkernel
rm -R /Volumes/VOLUME/System/Library/Caches/com.apple.kext.caches
touch /Volumes/VOLUME/System/Library/Extensions
kextcache -u /Volumes/VOLUME

obviously change VOLUME to your descriptor.

 

EDIT: If this doesnt work, then you have to fiddle with the slide parameter. See "solved" post.

post-19619-0-69839500-1513121171_thumb.png

Link to comment
Share on other sites

 

I had this issue after upgrading to 10.13.2 - Clover stops with the cryptic error message "does printf work??" and completly freezes the system.

i googled the issue, only found error reports - sadly no solution (except removing aptiov2).

 

The issue is triggered whenever the prelinked kernel is defunc. osxaptiov2 triggers this message, while the older osxaptiov1 (and hence the free2000 version) works fine.

This happens for ex. after a timemachine recovery.

 

Solution:

boot in recovery mode, remove old kext cache and prelinked kernel, force kext cache rebuild and reboot - twice.

sudo -s
rm -f /Volumes/VOLUME/System/Library/PrelinkedKernels/prelinkedkernel
rm -R /System/Library/Caches/com.apple.kext.caches
touch /Volumes/VOLUME/System/Library/Extensions
kextcache -u /Volumes/VOLUME

Why would you "touch" /Volumes/VOLUME/System/Library/Extensions ?

Link to comment
Share on other sites

Ok, this works until you actually make a system change. The only way i can get around this is by constantly rebooting w/ -f....

 

EDIT: Ok, now this is becoming a P.I.T.A. Now it's just doing it randomly. Does anyone have another solution to this issue? I've tried removing OsxAptioFixDrv and using the free2000 version. Still randomly gives me the "Does printf work??" message and halts.

Link to comment
Share on other sites

I've never had slide=0

It is really frustrating!

For me, if I boot off my backup SSD instead of my NVME drive, it works fine. They're completely identical.

I think it is a cache thing because it happens more after I've made changes, even if I boot into windows will kick it off.

At the moment every 3rd boot is successful.

Link to comment
Share on other sites

the problem occurs whenever its unable to load the (cached) kernel. It's also possible that the slide value is calculated the wrong way or your memory is too fragmented. Best would be a more relateable error message with some debug information - but this has to be done by clover.

 

So other possible "fixes": add slide=0 to your boot parameters, remove the slide value at all or calculate the slide using

https://github.com/wmchris/DellXPS15-9550-OSX/blob/10.13/Additional/slide_calc.md

you can also try the attached EFI extensions built from a newer clover version, some people reported to get it to work with them or at least got the correct error message. Just replace them in CLOVER/drivers64uefi.

osxaptio-printf.zip

  • Like 2
Link to comment
Share on other sites

the problem occurs whenever its unable to load the (cached) kernel. It's also possible that the slide value is calculated the wrong way or your memory is too fragmented. Best would be a more relateable error message with some debug information - but this has to be done by clover.

 

So other possible "fixes": add slide=0 to your boot parameters, remove the slide value at all or calculate the slide using

https://github.com/wmchris/DellXPS15-9550-OSX/blob/10.13/Additional/slide_calc.md

you can also try the attached EFI extensions built from a newer clover version, some people reported to get it to work with them or at least got the correct error message. Just replace them in CLOVER/drivers64uefi.

 

Hmm....3 successful boots in a row.....replacing those extensions seems to work ok for now. I do notice that it automatically appends slide=0 to the boot arguments for some reason....but hey, it works and I ain't complainin'.

Link to comment
Share on other sites

  • 1 month later...

Hi there, I like the look of the github link, but when I try and Boot into the UEFI Shell from Clover, I don't see any option for the UEFI Shell and so cant run the memory command... All i see in clover are my boot options, options, about clover, restart computer and exit clover.  I know it used to be a option in the older clover, but I cant see it with the latest one, which is where my boot is stuck on at "does printf work??"
My machine simply hangs on the .............. line of osxaptio version 1 and the free 2000 version does something funny as well. So I'm figuring that version 2 (or clovers new 'version 3') is probably my best bet of moving forward at the moment.
I also have a slightly older clover installed on a nother HDD in my hackintosh's system with version 4243 but that also seems to lack the UEFI Shell option in clover. Any ideas how to bring up the UEFI  shell?? I cant find anything online about bringing it up only that it is accessible in Clover.

I'm running on a freshly updated 10.13.3 OSX on my X99 Xeon hack. Clover 4243 worked ok in 10.13.1 but seems to have issues with 10.13.2 & now  .3 hence me wanting to update my clover (but am stuck on not being able to get into OSX). I tried Slide=0   nothing happened. So if I can calculate my rigs slide value, that would be amazing.

Link to comment
Share on other sites

Hi there, I like the look of the github link, but when I try and Boot into the UEFI Shell from Clover, I don't see any option for the UEFI Shell and so cant run the memory command... All i see in clover are my boot options, options, about clover, restart computer and exit clover.  I know it used to be a option in the older clover, but I cant see it with the latest one, which is where my boot is stuck on at "does printf work??"

My machine simply hangs on the .............. line of osxaptio version 1 and the free 2000 version does something funny as well. So I'm figuring that version 2 (or clovers new 'version 3') is probably my best bet of moving forward at the moment.

I also have a slightly older clover installed on a nother HDD in my hackintosh's system with version 4243 but that also seems to lack the UEFI Shell option in clover. Any ideas how to bring up the UEFI  shell?? I cant find anything online about bringing it up only that it is accessible in Clover.

 

I'm running on a freshly updated 10.13.3 OSX on my X99 Xeon hack. Clover 4243 worked ok in 10.13.1 but seems to have issues with 10.13.2 & now  .3 hence me wanting to update my clover (but am stuck on not being able to get into OSX). I tried Slide=0   nothing happened. So if I can calculate my rigs slide value, that would be amazing.

u tested a new driver?

AptioMemoryFix.efi.zip

credits vit6969

Link to comment
Share on other sites

It runs through a ton of slide values up to 127 all 'cannot be used!' then says 'only 128/256 slide values are available for usage! Booting may fail!'

 

Now its just sitting on the  +++++++ line..

Does that mean something useful?

looks like a..u need a fakecpuid, try with KernelCpu in config.plist or inject fakecpuid 0x40674, check if solve ur problem

 

check treads about x99

http://www.insanelymac.com/forum/topic/313296-guide-mac-osx-1012-and-1013-with-x99-broadwell-e-family-and-haswell-e-family/

 

http://www.insanelymac.com/forum/topic/316516-macos-sierrahigh-sierra-on-broadwell-eep-not-a-guide-but-maybe-a-working-in-progress/

 

Enjoy!

Link to comment
Share on other sites

  • 2 months later...

Got same error randomly on my new hack :

GA Z370 gaming 7

i7 8700K

64go Ballistix 2400 MHz

It can pop 3 times in a row and after wait the 7th boot before appears again. Don't understand why and how fix it. I'm trying the AptioMemoryFix driver include in Clover Configurator right now. 

Link to comment
Share on other sites

15 minutes ago, Delecta said:

Got same error randomly on my new hack :

GA Z370 gaming 7

i7 8700K

64go Ballistix 2400 MHz

It can pop 3 times in a row and after wait the 7th boot before appears again. Don't understand why and how fix it. I'm trying the AptioMemoryFix driver include in Clover Configurator right now. 

u use last version? is stable

AptioMemoryFix.efi.zip

Link to comment
Share on other sites

43 minutes ago, MaLd0n said:

use only AptioMemoryFix and clear nvram, press F11 in clover boot screen

Thanks. This problem has been bugging me for a while a while with recent Clover builds on my Z77X-up5 motherboard.

Just replaced the aptiofix3 driver with aptiomemoryfix and done 5 restarts without issues. So far so good.

I think issues arise when there's a system change like installing or moving kexts.

PS. I get the message 119/256 slide values. What does that mean ?

Link to comment
Share on other sites

15 minutes ago, MacNB said:

Thanks. This problem has been bugging me for a while a while with recent Clover builds on my Z77X-up5 motherboard.

Just replaced the aptiofix3 driver with aptiomemoryfix and done 5 restarts without issues. So far so good.

I think issues arise when there's a system change like installing or moving kexts.

PS. I get the message 119/256 slide values. What does that mean ?

common, auto calculate

Features (compared to the original)
Automatically finds the available memory region for boot.efi to use
Implements KASLR support for systems where certain slides cannot be used
Adds Safe Mode support on systems with used lower addresses
Ensures no slide argument leak to the operating system
Attempts to more properly handle the memory mappings
Implements new mapping code when waking from hibernation (still not stable enough)

https://github.com/vit9696/AptioFixPkg 

  • Thanks 1
Link to comment
Share on other sites

Thank you all ! The AptioMemory Fix solve my issue ! But now my computer crash when I edit some 360 video on Premier Pro and I think it's my Vega 64 FE the problem becasue the LED are only flashing.

Thank you again

Link to comment
Share on other sites

 Share

×
×
  • Create New...