Jump to content
spakk

TASK FORCE - [AMD] to missing SSE4.1 Instruction set - older CPUs on macOS Sierra (10.12.x)

270 posts in this topic

Recommended Posts

@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! :)

Share this post


Link to post
Share on other sites
Advertisement

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.

Share this post


Link to post
Share on other sites

How about these?

 

disable_preemption();

enable_preemption();

I get a kernel panic

Kernel-panic_20171028_222400.jpg

Share this post


Link to post
Share on other sites

I get a kernel panic

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:

post-1299088-0-00631000-1509224819_thumb.jpg

And if I put printf () above sse41_run in opemu.c, I will get the same kernel panic as well.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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:

attachicon.gifIMG_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?

Share this post


Link to post
Share on other sites

The same here and in the end it depends on this place.

End_20171029_111654.jpg

Share this post


Link to post
Share on other sites

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:
attachicon.gifIMG_1985.JPG
And 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

Share this post


Link to post
Share on other sites

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 ?

Share this post


Link to post
Share on other sites

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:

post-1299088-0-36844500-1509312582_thumb.png

post-1299088-0-74980100-1509312596_thumb.png

post-1299088-0-46728700-1509312617_thumb.png

post-1299088-0-77279000-1509312637_thumb.png

post-1299088-0-28502800-1509312700_thumb.png

Share this post


Link to post
Share on other sites

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:

post-1299088-0-14633900-1509315252_thumb.jpg

 

But how about saving the debug output into a file? Is it possible at this state?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Sinn
      Hi
       
      After months again i want to install 10.10. I don't have old pendrive so i need to create new one. After created usb installation stick,change kernel and change some files in Extra folder i started to boot it up. Im stucked on "invalid kernel opcode (64 bit): 44 0f b6 1f 4c 8d 7f 01 41 83" What i shoud to do ? 
       
      AMD FX 8350
      Gigabyte Motherboard
      16 Gb of ram
      gtx 650ti
       
      Thanks in advance
×