Jump to content

Mavericks kernel testing on AMD (formerly Mountain Lion kernel testing on AMD)


theconnactic
 Share

6,414 posts in this topic

Recommended Posts

I'm currently working on the ssse3emu and the blacklister. I think the blacklist is fine now... keep you posted ;)

  • Like 1
Link to comment
Share on other sites

I'm allready attaching my modifications...

Gonna test them in a minute.

If you can't wait and you build one... -enable_ssse3emu boot argument will toggle the ssse3 emulator (in 64bit).

Keep you posted...

The blacklister should also be fixed...

Gonna check anyway ;)

xnu-2050.18.24-test3.diff.zip

Link to comment
Share on other sites

sadly cant compile at the moment

 

so ill have to wait for yours

Good news and bad news...

I was unable to test the ssse3emu (my machine has ssse3 and when I use -enable_ssse3emu it panicked after the commpage_stuff2 routine).

Further testing needed...

But the good news is that the kernel blacklister is fixed.

Have a new diff (also blacklists AppleEFIRuntime)...

Kernel building now...

xnu-2050.18.24-test4.diff.zip

Link to comment
Share on other sites

Good news and bad news...

I was unable to test the ssse3emu (my machine has ssse3 and when I use -enable_ssse3emu it panicked after the commpage_stuff2 routine).

Further testing needed...

But the good news is that the kernel blacklister is fixed.

Have a new diff (also blacklists AppleEFIRuntime)...

Kernel building now...

 

Waiting patiently. Could you tell me how to add a diff file?

 

Thanks

Link to comment
Share on other sites

from within xnu source

patch -p1 < path/to/patch.diff

This will apply the diff...

Next build with

make ARCH_CONFIGS=X86_64 KERNEL_CONFIGS=RELEASE install

Kernel is attached...

Does anybody know the 64bit variant of the pusha/popa instructions?

It's possible the panic is related to these...

If we have those, we might be able to fix the 64bit version of the ssse3emu... if it doesn't work anyway... it needs testing.

ssse3emu isn't enabled by default but can be enabled with boot argument -enable_ssse3emu.

Kernel attached...

Blacklister is fully fixed now... no more need to remove AppleEFIRuntime.kext or AppleIntelCPUPowerManagement...

EDIT: I decided to attach my dmesg output... just in case it may come in handy...

AnV_kernel.zip

Dmesg_output.zip

Link to comment
Share on other sites

Oops... I found out why the panic:

I didn't pass the PE_parse_boot_argn right... forgot the &... X)

New patch, kernel, if success later...

xnu-2050.18.24-test5.diff.zip

Link to comment
Share on other sites

Enabling SSSE3 emulator. Size 9616 should be less than 4096.

Hahaha!

I just booted the newly built kernel.

I enabled the SSSE3 emulator with -enable_ssse3emu and it looks like it works!

Posting kernel now... ;)

NOTE: This is ML in 64bit with 64bit kernel of course :D

AnV_kernel.zip

Link to comment
Share on other sites

Damn corecrypto... always panics on that sha1 SSE3 compress... makes me want to hack that corecrypto kext.

Maybe we should design our own corecrypto kext...

  • Like 1
Link to comment
Share on other sites

Damn corecrypto... always panics on that sha1 SSE3 compress... makes me want to hack that corecrypto kext.

Maybe we should design our own corecrypto kext...

 

Removing the kext doesn't help, just a big panic. How would we go about making the kext?

Link to comment
Share on other sites

Did anybody try it with an Intel CPU?

If an Intel CPU without SSSE3 with emulator works we at least know something (Pentium D or so, 64bit without SSSE3)

 

We disassemble the current one and check... I wonder if I changed the current kext... lots of hard work though... gonna check later...

Link to comment
Share on other sites

You could try compiling with Xcode 3.2.6 or use my latest posted test kernel... but so far no go due to damn corecrypto kext...

Link to comment
Share on other sites

and again if anyone would take a closer look to my screens HE would see at the line Bootargs that fips_mode=0 is used !!!

 

in my case !

 

I have no idea why it would still panic. fips_mode=0 normally sidesteps that check. The only other thing I know to tell you is to mask the SSE3 instruction on AMD cpus. It will avoid the invalid opcode error and pass the FIPS tests afterwards.

Link to comment
Share on other sites

 Share

×
×
  • Create New...