Jump to content
272 posts in this topic

Recommended Posts

my CPU without SS4.1 . Can it install macOS 10.12?

You have to wait until a suitable sse4.1emulator is built. then it will work ^_^

fixed scale 1 address

the test with your last kernel gave me the same as already posted here : http://www.insanelymac.com/forum/topic/322370-task-force-amd-to-missing-sse41-instruction-set-older-cpus-on-macos-sierra-1012x/page-10?p=2525212&do=findComment&comment=2525212

 

Edit:

@ydeng,

maybe we should build a vanillia kernel with your emulator and test the kernel with a pentium dual core cpu (for example) and see if it will work. what do you mean?

Added more prints.  All instructions look fine to me.

You have to wait until a suitable sse4.1emulator is built. then it will work ^_^

the test with your last kernel gave me the same as already posted here : http://www.insanelymac.com/forum/topic/322370-task-force-amd-to-missing-sse41-instruction-set-older-cpus-on-macos-sierra-1012x/page-10?p=2525212&do=findComment&comment=2525212

 

Edit:

@ydeng,

maybe we should build a vanillia kernel with your emulator and test the kernel with a pentium dual core cpu (for example) and see if it will work. what do you mean?

AMD kernel boots Intel CPU as well.

  • Like 1

Fixed some typos printing.  I cannot see anything wrong.

 

After this is blank screen and then installer quits?

I can't boot to the blank screen because it takes too much time with print delay

How about building a kernel without debug printouts?

  • Like 1

here you go.

It shows many prints like "copying 4 bytes at ..." and I wasn't able to boot to the blank screen and can't tell what happens when it's booting because of many prints of copying bytes.

  • Like 1

It shows many prints like "copying 4 bytes at ..." and I wasn't able to boot to the blank screen and can't tell what happens when it's booting because of many prints of copying bytes.

forgot to remove all of them.

  • Like 1

forgot to remove all of them.

It keeps showing these messages

post-1299088-0-94511300-1509925961_thumb.jpg

How about disabling debug prints for pmovzxbd, pmovsxbw, roundsd and pinsrb to be able to see other instructions?

  • Like 1

It keeps showing these messages

attachicon.gifIMG_0571.JPG

How about disabling debug prints for pmovzxbd, pmovsxbw, roundsd and pinsrb to be able to see other instructions?

roundsd is still printed.  Need to see different modes.

 

trustd keeps dying, understandable, lots of crypto calculations.

 

source code is here

https://opensource.apple.com/source/Security/Security-58286.1.32/OSX/trustd/trustd.c.auto.html

  • Like 1

roundsd is still printed.  Need to see different modes.

 

trustd keeps dying, understandable, lots of crypto calculations.

 

source code is here

https://opensource.apple.com/source/Security/Security-58286.1.32/OSX/trustd/trustd.c.auto.html

I took a video 

https://workupload.com/file/xDD964X

  • Like 1

pcmpeqq gone too.

is it the right kernel? it shows me prints of pmovzxbd and pmovsxbw.

 

With removed com.apple.trustd.plist from S/L/LaunchDaemons it shows these printouts before booting to the blank screen with previous kernel and there is no more prints of other instructions except pcmpeqq

post-1299088-0-84649900-1510014679_thumb.jpeg

post-1299088-0-62752500-1510014685_thumb.jpeg

  • Like 1

is it the right kernel? it shows me prints of pmovzxbd and pmovsxbw.

 

With removed com.apple.trustd.plist from S/L/LaunchDaemons it shows these printouts before booting to the blank screen with previous kernel and there is no more prints of other instructions except pcmpeqq

This one is correct.

  • Like 1
×
×
  • Create New...