AXAXAXAXAXAX Posted October 15, 2017 Share Posted October 15, 2017 Commented out Debugger message. 1 Link to comment Share on other sites More sharing options...
ydeng Posted October 15, 2017 Share Posted October 15, 2017 IMG_1803.JPG Ok, forgot extended registers in long mode. Please try this one. Thanks for continued patience. 1 Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted October 15, 2017 Share Posted October 15, 2017 it has been a lot o time since last time I have seen a double kernel panic Link to comment Share on other sites More sharing options...
Loloflat6 Posted October 15, 2017 Share Posted October 15, 2017 Not able to boot for the moment but may be my usb installer, i will try with another one. Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 15, 2017 Share Posted October 15, 2017 Ok, forgot extended registers in long mode. Please try this one. Thanks for continued patience. Link to comment Share on other sites More sharing options...
ydeng Posted October 15, 2017 Share Posted October 15, 2017 IMG_1804.JPG This looks like something else. These people has a fix for intel cpu https://www.tonymacx86.com/threads/kernel-panic-and-reboot-while-installing-sierra-g4500-h110.207109/ . launchd gets segmentation fault... Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted October 15, 2017 Share Posted October 15, 2017 This looks like something else. These people has a fix for intel cpu https://www.tonymacx86.com/threads/kernel-panic-and-reboot-while-installing-sierra-g4500-h110.207109/ . this is not our problem, the problem of that people is that Skylake pentiums (that supports also sse4.1) needs fake cpu id to work, we are instead working with cpus that needs a lot of kernel mods to run properly, specifically an engine to emulate sse4.1 instructions that are missing in older cpus Link to comment Share on other sites More sharing options...
ydeng Posted October 16, 2017 Share Posted October 16, 2017 IMG_1804.JPG Fixed some warnings. Don't know it changes anything. 1 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 16, 2017 Share Posted October 16, 2017 Fixed some warnings. Don't know it changes anything. it gives me the same log messages as previous kernel Link to comment Share on other sites More sharing options...
ydeng Posted October 17, 2017 Share Posted October 17, 2017 it gives me the same log messages as previous kernel How about add amfi_get_out_of_my_way=1 to kernel flag? Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 17, 2017 Share Posted October 17, 2017 How about add amfi_get_out_of_my_way=1 to kernel flag?It doesn't help. I updated my sierra installer to 10.12.6 and now it shows me this(with -f flag): But if it boots with -x flag it will show this: 1 Link to comment Share on other sites More sharing options...
spakk Posted October 17, 2017 Author Share Posted October 17, 2017 Opcode is still faulty ;-/ Link to comment Share on other sites More sharing options...
ydeng Posted October 17, 2017 Share Posted October 17, 2017 It doesn't help. I updated my sierra installer to 10.12.6 and now it shows me this(with -f flag): IMG_1813.JPG But if it boots with -x flag it will show this: IMG_1814.JPG Turned on more opemu print. My test shows no problem for pinsrtb. 1 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 18, 2017 Share Posted October 18, 2017 Turned on more opemu print. My test shows no problem for pinsrtb. It doesn't show more opemu print and it stopped showing messages of pinsrtb 1 Link to comment Share on other sites More sharing options...
ydeng Posted October 18, 2017 Share Posted October 18, 2017 It doesn't show more opemu print and it stopped showing messages of pinsrtb did not turn on user mode print. How about this one? kernel binary deleted. source code posted in this thread. 2 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 18, 2017 Share Posted October 18, 2017 did not turn on user mode print. How about this one? 1 Link to comment Share on other sites More sharing options...
ydeng Posted October 18, 2017 Share Posted October 18, 2017 IMG_1817.JPG IMG_1884.JPG only pinsrd is sse4.1. Link to comment Share on other sites More sharing options...
spakk Posted October 20, 2017 Author Share Posted October 20, 2017 unfortunately no luck, at the end the system stops at this point. What changes did you make? Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 20, 2017 Share Posted October 20, 2017 unfortunately no luck, at the end the system stops at this point. What changes did you make? Did you try with Enoch r2902? Link to comment Share on other sites More sharing options...
spakk Posted October 20, 2017 Author Share Posted October 20, 2017 Did you try with Enoch r2902? I've tried to boot with Enoch r2889 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 20, 2017 Share Posted October 20, 2017 unfortunately no luck, at the end the system stops at this point. What changes did you make? I've tried to boot with Enoch r2889This issue will go away with Enoch r2902 1 Link to comment Share on other sites More sharing options...
spakk Posted October 21, 2017 Author Share Posted October 21, 2017 same problem Edit: current bootloader version is better than previous version. The image shows another panic message from my last faulty kernel 1 Link to comment Share on other sites More sharing options...
ydeng Posted October 21, 2017 Share Posted October 21, 2017 same problem Edit: current bootloader version is better than previous version. The image shows another panic message from my last faulty kernel That means something else is wrong. My change handles invalid opcode traps for all sse4.1 instructions with emulations. All the emulations are tested against compiler intrinsics. 1 Link to comment Share on other sites More sharing options...
spakk Posted October 21, 2017 Author Share Posted October 21, 2017 That means something else is wrong. My change handles invalid opcode traps for all sse4.1 instructions with emulations. All the emulations are tested against compiler intrinsics. okay, would it be possible to publish the sse4.1 emulator? edit: I've also been using the gcc compiler intrinsics (sse4.1) in my source but without success Link to comment Share on other sites More sharing options...
ydeng Posted October 21, 2017 Share Posted October 21, 2017 okay, would it be possible to publish the sse4.1 emulator? edit: I've also been using the gcc compiler intrinsics (sse4.1) in my source but without success Here you go. May the source be with you. Notice there is a bug fix for libuids86. A separate patch is needed for standalone libuids86 because that file is generated at compile time. Can not use intrinsics for this, circular logic. patch.zip 3 Link to comment Share on other sites More sharing options...
Recommended Posts