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 modding my patches for current kernel.

Lots already done.

I also noticed I can apply my code signature patch perfectly to the new kernel...

So code signing... no problem ;)

EDIT: NOTE: The kernel has totally no i386 (32-bit) code inside as Mavericks never had a 32-bit kernel.

So some patches that patched the 32-bit code are obsolete...

Yes i see ! :)

I same done . I need install Maverick 10.9 and test . Or you can test it is my kernel )))

  • Like 1
Link to comment
Share on other sites

Yes i see ! :)

I same done . I need install Maverick 10.9 and test . Or you can test it is my kernel )))

I have an Intel CPU...

Did you also leave the needed support for booting Intel inside?

Unfortunetely no AMD here...

Link to comment
Share on other sites

I have an Intel CPU...

Did you also leave the needed support for booting Intel inside?

Unfortunetely no AMD here...

 

Yes ! I adding Intel's and AMD , i don't delete Intel ! If Your processor Intel(via) , i can add for VIA . ! 

  • Like 3
Link to comment
Share on other sites

Bronya and Andy, if it's not asking too much, could you include Atom CPUs support to the mix? :P

My patch supports this.

Unfortunetely cltools 5.0.1 only is not enough to build XNU.

I also need Xcode 5.0.1 itself but I don't have enough bandwidth so I can only do the download in the weekend with a friend.

The patch, however, is fully ported.

EDIT: Oh yes, AMD TLB fix is no longer set unless boot argument is given

It can be enabled with boot argument

-amdtlbfix

As most AMD cpus don't need this...

 

@Bronya: You might want this, and if you could build it, would be cool ;)

EDIT: Oops, wrong diff... see somewhat further (a couple posts ahead)...

Removed file...

  • Like 3
Link to comment
Share on other sites

I'll build it! I'll do at once. Thank you very much!


P.S.: Same errors both in patching - lots of .s files wouldn't be found - and building the actual kernel. In fact, it behaves just like when i tried with rc_4.

 

P.P.S.: a screenshot of the errors while applying the patches: 

 

Screen Shot 2013-10-24 at 3.59.48 PM.png

  • Like 2
Link to comment
Share on other sites

I'll build it! I'll do at once. Thank you very much!

P.S.: Same errors both in patching - lots of .s files wouldn't be found - and building the actual kernel. In fact, it behaves just like when i tried with rc_4.

 

P.P.S.: a screenshot of the errors while applying the patches: 

 

attachicon.gifScreen Shot 2013-10-24 at 3.59.48 PM.png

Is 32-bit Intel patches... strange...

Diff needs cleaning...

Other than that, all ok if no patches fail (fuzz = ok)

EDIT: Can't be right patch...

I checked, see screenshot, you applied the wrong one...

It has no acpi_wakeup.s in the source diff...

Uploading again...  :o

Test the MavTest 1 diff...

It should apply cleanly...

 

EDIT2: Use test2 diff... below...

I built it with Mavericks, but i really don't know. Will Xcode 5 run with Lion? If yes, i don't see why not...

Xcode 5.0.1 will run on 10.8.X -> 10.9.X

post-100023-0-21020500-1382638911_thumb.png

Link to comment
Share on other sites

Could you post me full log in text file format?

I'll fix them...

EDIT: I fixed the errors I saw in the screenshots.

Try this one...

EDIT2: Try test3 below...

Link to comment
Share on other sites

Ok after downloading what have i to do?

Put the tools in /usr/bin.

Make sure you have Xcode 5.0.1 and command line tools for Xcode installed.

Apply patch.

Build the kernel

Link to comment
Share on other sites

attachicon.giflog.txt

 

Here!

Ok... I think all is fine with the test2 diff..

They don't mention building ctf_insert from cctools.

Included in my ctf tools package...

Check MakeInc.cmds...

It is used there...

So also install ctf_insert (you can get it from my uploaded ctf tools)

ctf_insert --help
Usage: ctf_insert input [-arch <arch> <file>]... -o output

Which is used...

Link to comment
Share on other sites

When will you start working with kernel for Phenom II ?

 

Are you think i should buy new FX if i want get better working OS X ?

 The first question isn't polite to be asked to someone who's working at no charge for your benefit. The second i can answer myself: yes, FXs work better, but if you are to buy a new (and expensive) CPU, i suggest you spend a few more bucks and go straight with a future proof Gigabyte/Intel build.

Andy, the build failed again: log2.txt

  • Like 3
Link to comment
Share on other sites

 The first question isn't polite to be asked to someone who's working at no charge for your benefit. The second i can answer myself: yes, FXs work better, but if you are to buy a new (and expensive) CPU, i suggest you spend a few more bucks and go straight with a future proof Gigabyte/Intel build.

True, but I prefer Asus + Intel (cheap i3-3320 IVY Bridge + Asus P8H77-M LE)

Link to comment
Share on other sites

Interesting !!!

I install command_line_tool_mountain_lion and xcode 5.0 .

AND 

I compiled :

1) cxxfilt-11 <-- ok !

2)dtrace-96 <-- ok !

3) build xnu 10.9  <-- ok !!!

:)

No issues with ctf_insert missing?

It's defined in MakeDefs.cmd...

Link to comment
Share on other sites

 Share

×
×
  • Create New...