spakk Posted October 27, 2017 Author Share Posted October 27, 2017 @AXAXAXAXAXAX, here is the video video result, booting with your last kernel: https://workupload.com/file/rdphVN2 a positive change against the penultimate kernel was that no has occurred "OPEMU UD2" error loop. but no changes in the boot process against your last kernel, see the two pictures, which I've uploaded above @Yuqing Deng, I hope you can fix the problem., good job! 2 Link to comment Share on other sites More sharing options...
ydeng Posted October 27, 2017 Share Posted October 27, 2017 It is always 0 IMG_1972.JPG I cannot see any thing wrong from test register dump. How about turn off the interrupt on sse41_run entry and turn it back on when it returns? This should be better than printf. bracket stuff here https://github.com/Shaneee92/SierraAMD-XNU/blob/master/osfmk/OPEMU/opemu.c#L205 with pal_cli(); .... pal_sti(); Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted October 27, 2017 Share Posted October 27, 2017 wow! it almost works, I am trying to get it to work on my intel cpu, should it theoretically work on intel? Link to comment Share on other sites More sharing options...
ydeng Posted October 27, 2017 Share Posted October 27, 2017 wow! it almost works, I am trying to get it to work on my intel cpu, should it theoretically work on intel? All my initial tests are done on Intel. Should work. 1 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 27, 2017 Share Posted October 27, 2017 I cannot see any thing wrong from test register dump. How about turn off the interrupt on sse41_run entry and turn it back on when it returns? This should be better than printf. bracket stuff here https://github.com/Shaneee92/SierraAMD-XNU/blob/master/osfmk/OPEMU/opemu.c#L205 with pal_cli(); .... pal_sti(); It gets a kernel panic with that like before without printf. Link to comment Share on other sites More sharing options...
ydeng Posted October 28, 2017 Share Posted October 28, 2017 It gets a kernel panic with that like before without printf. How about these? disable_preemption(); enable_preemption(); Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 28, 2017 Share Posted October 28, 2017 How about these? disable_preemption(); enable_preemption(); They didn't help either. The same kernel panic Link to comment Share on other sites More sharing options...
spakk Posted October 28, 2017 Author Share Posted October 28, 2017 How about these? disable_preemption(); enable_preemption(); I get a kernel panic Link to comment Share on other sites More sharing options...
Shaneee Posted October 28, 2017 Share Posted October 28, 2017 Nice work guys you are getting really close Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 28, 2017 Share Posted October 28, 2017 I get a kernel panicI'm getting this kernel panic if I don't use the current version of Enoch.But with sse41_run between pal_cli(); pal_sti(); or disable_preemption(); enable_preemption(); in opemu.c I'm getting this kernel panic which is the same one like without printf in sse4_run above of switch statement of mnemonic: And if I put printf () above sse41_run in opemu.c, I will get the same kernel panic as well. 1 Link to comment Share on other sites More sharing options...
ITzTravelInTime Posted October 28, 2017 Share Posted October 28, 2017 i am trying to use clover, how do I rebuild kernelacache using the single user mode or the terminal from the gui of the installer? (I am preparing and testing the usb drive on a sse4.1 cpu and the just replace the cpu into the machine, I am using a socket 775 machine, so I have a lot of cpus to play with) Edit by spakk: assuming your partition is called "Sierra HD" then enter the following into terminal: sudo -s rm -f /Volumes/Sierra-HD/System/Library/PrelinkedKernels/prelinkedkernel touch /Volumes/Sierra-HD/System/Library/Extensions kextcache -u /Volumes/Sierra-HD exit Link to comment Share on other sites More sharing options...
ydeng Posted October 29, 2017 Share Posted October 29, 2017 I'm getting this kernel panic if I don't use the current version of Enoch. But with sse41_run between pal_cli(); pal_sti(); or disable_preemption(); enable_preemption(); in opemu.c I'm getting this kernel panic which is the same one like without printf in sse4_run above of switch statement of mnemonic: IMG_1985.JPG And if I put printf () above sse41_run in opemu.c, I will get the same kernel panic as well. how about this one? 2 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 29, 2017 Share Posted October 29, 2017 how about this one? 1 Link to comment Share on other sites More sharing options...
spakk Posted October 29, 2017 Author Share Posted October 29, 2017 The same here and in the end it depends on this place. Link to comment Share on other sites More sharing options...
Sinetek Posted October 29, 2017 Share Posted October 29, 2017 Howdy folks. I'm getting this kernel panic if I don't use the current version of Enoch.But with sse41_run between pal_cli(); pal_sti(); or disable_preemption(); enable_preemption(); in opemu.c I'm getting this kernel panic which is the same one like without printf in sse4_run above of switch statement of mnemonic:IMG_1985.JPGAnd if I put printf () above sse41_run in opemu.c, I will get the same kernel panic as well. This means that your pid 1 (the init process, which becomes launchd) has quit, probably because of a seg fault.I'll answer questions but I'm afraid I don't have the resources to go into a restoration of the OPEMU to modernize it..-- Sinetek 1 Link to comment Share on other sites More sharing options...
spakk Posted October 29, 2017 Author Share Posted October 29, 2017 Howdy folks. This means that your pid 1 (the init process, which becomes launchd) has quit, probably because of a seg fault. I'll answer questions but I'm afraid I don't have the resources to go into a restoration of the OPEMU to modernize it.. -- Sinetek what does that mean, can you help if you have access to the source, or not ? Link to comment Share on other sites More sharing options...
ydeng Posted October 29, 2017 Share Posted October 29, 2017 IMG_1997.JPG add more debug prints. 2 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 29, 2017 Share Posted October 29, 2017 add more debug prints. 1 Link to comment Share on other sites More sharing options...
ydeng Posted October 29, 2017 Share Posted October 29, 2017 IMG_2004.JPG Instructions have no effect! how about this one? 2 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 29, 2017 Share Posted October 29, 2017 Instructions have no effect! how about this one? It doesn't get a kernel panic anymore! 2 Link to comment Share on other sites More sharing options...
ydeng Posted October 29, 2017 Share Posted October 29, 2017 It doesn't get a kernel panic anymore! Put this line where you insert printf. You can build your own without the debug messages. sse3_obj.islegacy = 0; 2 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 29, 2017 Share Posted October 29, 2017 Put this line where you insert printf. You can build your own without the debug messages. sse3_obj.islegacy = 0; it boots to white screen with loading cursor and then the system shuts down. Here are the log of booting: 2 Link to comment Share on other sites More sharing options...
ydeng Posted October 29, 2017 Share Posted October 29, 2017 it boots to white screen with loading cursor and then the system shuts down. Here are the log of booting: IMG_2011.PNG IMG_2012.PNG IMG_2014.PNG IMG_2015.PNG IMG_2017.PNG ok go back to the one with debug prints. I want to see the instructions. Link to comment Share on other sites More sharing options...
spakk Posted October 29, 2017 Author Share Posted October 29, 2017 wow! cool you are on target 1 Link to comment Share on other sites More sharing options...
AXAXAXAXAXAX Posted October 29, 2017 Share Posted October 29, 2017 ok go back to the one with debug prints. I want to see the instructions.It seems to be impossible to catch any information because debug prints run too fast: But how about saving the debug output into a file? Is it possible at this state? Link to comment Share on other sites More sharing options...
Recommended Posts