2468 replies to this topic

[gils83]

)-

[gils83]

spakk, on 18 November 2012 - 11:07 PM, said:

We urgently need to look for the cause of the error Launched 86 , Request for feedback please

[IiTz ShAnE]

I am getting the launchd errno 86 now aswell. The install starts loading as lion does then KP's. From what I found its something to do with drivers not being mounted. I have tried the launchd file from 10.8 DP1 and my 10.7.4 installation.

EDIT:
System froze instead of kp.
Booted using,

-legacy arch=i386 -force64 -v npci=0x2000

It freezes at BSD root: disk2s2, major 14, minor 11

On Lion right after that line is launchd loading...

Is this classed as progress or another brick wall?

[theconnactic]

Watching closely this thread, at least twice a day. I didn't abandon the boat, my friends.

Very interested to see if you guys can succeed in booting ML DP1. That would be an enormous step!

Gilles, glad to see you here at last!

[spakk]

IiTz ShAnE, on 19 November 2012 - 01:25 AM, said:

I am getting the launchd errno 86 now aswell. The install starts loading as lion does then KP's. From what I found its something to do with drivers not being mounted. I have tried the launchd file from 10.8 DP1 and my 10.7.4 installation.

EDIT:
System froze instead of kp.
Booted using,

-legacy arch=i386 -force64 -v npci=0x2000

It freezes at BSD root: disk2s2, major 14, minor 11

On Lion right after that line is launchd loading...

Is this classed as progress or another brick wall?

Please boot with boot flag:
-v busratio=20 arch=i386 -force64 maxmem=4096 npci=0x2000

[Deltac0]

Hi!

I'm a little busy at this moment, but when I'm back home (about 6½h), I'll look the launchd source and find out the error 86!

Lion 10.7.4: http://www.opensourc...launchd-392.38/
Mountain Lion 10.8.0: http://www.opensourc...launchd-442.21/

EDIT: I FOUND IT!

/usr/lib/sys/errno.h says this:

#define EBADARCH 86 /* Bad CPU type in executable */

Have fun investigating more, I gotta go now...

[IiTz ShAnE]

spakk, on 19 November 2012 - 06:17 AM, said:

Please boot with boot flag:
-v busratio=20 arch=i386 -force64 maxmem=4096 npci=0x2000

Didn't help. Still pauses before launchd loads.
Will take a look at the launchd source and see if there is anything I can do.

[spakk]

IiTz ShAnE, on 19 November 2012 - 01:25 AM, said:

I am getting the launchd errno 86 now aswell. The install starts loading as lion does then KP's. From what I found its something to do with drivers not being mounted. I have tried the launchd file from 10.8 DP1 and my 10.7.4 installation.

EDIT:
System froze instead of kp.
Booted using,

-legacy arch=i386 -force64 -v npci=0x2000

It freezes at BSD root: disk2s2, major 14, minor 11

On Lion right after that line is launchd loading...

Is this classed as progress or another brick wall?

nice to see you,

Deltac0, on 19 November 2012 - 06:29 AM, said:

Hi!

I'm a little busy at this moment, but when I'm back home (about 6½h), I'll look the launchd source and find out the error 86!

Lion 10.7.4: http://www.opensourc...launchd-392.38/
Mountain Lion 10.8.0: http://www.opensourc...launchd-442.21/

EDIT: I FOUND IT!

/usr/lib/sys/errno.h says this:

#define EBADARCH 86 /* Bad CPU type in executable */

Have fun investigating more, I gotta go now...

Great work, Deltac0

[Deltac0]

spakk, on 19 November 2012 - 11:53 AM, said:

Great work, Deltac0

Thanks! I'm back @ home now, time to start experimenting with some AMD patching

EDIT: Don't know what is the problem with launchd... The error 86 is Bad CPU type, but the launchd runs fine when ran from SL.
The problem means that the launchd is x86_64... Don't understand, when I do "file launchd" it says that it IS universal PPC / i386 / x86_64...


I will now install Lion on my Phenom II machine (32-bit), then I will modify the XCode 4.2 for SL to run on Lion 32-bit.
Then I'll compile a new launchd with ARCHS="i386" option, it should work... But I just don't understand why it doesn't work with the universal binary.

[spakk]

Deltac0, on 19 November 2012 - 12:58 PM, said:

Thanks! I'm back @ home now, time to start experimenting with some AMD patching

EDIT: Don't know what is the problem with launchd... The error 86 is Bad CPU type, but the launchd runs fine when ran from SL.
The problem means that the launchd is x86_64... Don't understand, when I do "file launchd" it says that it IS universal PPC / i386 / x86_64...


I will now install Lion on my Phenom II machine (32-bit), then I will modify the XCode 4.2 for SL to run on Lion 32-bit.
Then I'll compile a new launchd with ARCHS="i386" option, it should work... But I just don't understand why it doesn't work with the universal binary.

Hello my friend,
On Windows I have in the Xnu-2050.7.9 (Mountain Lion 10.8)
after "Bad CPU type in executable" sought and found
15 files with this entry.
in the first file "nfs-vnops" on line 6931 "DUMPANDLOG, / * 86 EBADARCH Bad CPU type in executable * /"
Please look at the pictures.

>>>


Edit:

Info about various errors including "86 EBADARCH Bad CPU type in executable"

Network error codes

In the case of network errors (e.g. a connection to a proxy server fails) Proxifier outputs error code numbers. These are the standard error codes. This section contains the codes of network errors and their description.

see here:
http://www.proxifier...n/v2/errors.htm


Edit: search for: cputypes.h
result:
kern_exec
mkmakefile
thread
ast
kern_xxx

[Deltac0]

spakk, on 19 November 2012 - 03:41 PM, said:

Hello my friend,
On Windows I have in the Xnu-2050.7.9 (Mountain Lion 10.8)
after "Bad CPU type in executable" sought and found
15 files with this entry.
in the first file "nfs-vnops" on line 6931 "DUMPANDLOG, / * 86 EBADARCH Bad CPU type in executable * /"
Please look at the pictures.

>>>


Edit:

Info about various errors including "86 EBADARCH Bad CPU type in executable"

Network error codes

In the case of network errors (e.g. a connection to a proxy server fails) Proxifier outputs error code numbers. These are the standard error codes. This section contains the codes of network errors and their description.

see here:
http://www.proxifier...n/v2/errors.htm

Thanks for information! I just found a a book about some OS X things by searching the load_init_program().

And there was this explanation how the launchd is launched:


I underlined the main parts of it. This is exactly why the kernel panics!

Link: http://books.google....epage&q&f=false

[spakk]

Deltac0, on 19 November 2012 - 04:10 PM, said:

Thanks for information! I just found a a book about some OS X things by searching the load_init_program().

And there was this explanation how the launchd is launched:


I underlined the main parts of it. This is exactly why the kernel panics!

Link: http://books.google....epage&q&f=false

Thanks for information!

[spakk]

Deltac0


   and what are we doing now?

has anyone an idea?

[spakk]

a very interesting website if it should interest anyone:
http://osxbook.com/software/xbinary/

[gils83]

theconnactic, on 19 November 2012 - 01:29 AM, said:

Watching closely this thread, at least twice a day. I didn't abandon the boat, my friends.

Very interested to see if you guys can succeed in booting ML DP1. That would be an enormous step!

Gilles, glad to see you here at last!

Merci , je fais ce que je peux au milieu de grosse tête !



Hi,

Did someone try it you virtualize ML DP1 10.8 on AMD PC?

[Deltac0]

Anyone with Lion or Mountain Lion could try to compile 32-bit launchd?

Here is some instructions:

1. Download this and extract to your desktop
2. Open terminal and navigate to the folder with "cd" command: "cd Desktop" should go to your desktop folder, then "cd launchd*" and it takes you to the launchd folder.
3. Type in terminal: sudo xcodebuild ARCHS="i386" <- WITH THE QUOTES ON "i386".
4. If it doesn't give any errors and says something like "Build succeeded", go to the build folder (usually named "BUILD"), there might be folder named "obj" (or not). Try to find the launchd there.
5. Upload the launchd somewhere, I'll try to boot with it and my custom kernel
6. ???
7. Profit. Pure profit.

[gils83]

Deltac0, on 19 November 2012 - 09:01 PM, said:

Anyone with Lion or Mountain Lion could try to compile 32-bit launchd?

Here is some instructions:

1. Download this and extract to your desktop
2. Open terminal and navigate to the folder with "cd" command: "cd Desktop" should go to your desktop folder, then "cd launchd*" and it takes you to the launchd folder.
3. Type in terminal: sudo xcodebuild ARCHS="i386" <- WITH THE QUOTES ON "i386".
4. If it doesn't give any errors and says something like "Build succeeded", go to the build folder (usually named "BUILD"), there might be folder named "obj" (or not). Try to find the launchd there.
5. Upload the launchd somewhere, I'll try to boot with it and my custom kernel
6. ???
7. Profit. Pure profit.

Deltac0, on 19 November 2012 - 09:01 PM, said:

Anyone with Lion or Mountain Lion could try to compile 32-bit launchd?

Here is some instructions:

1. Download this and extract to your desktop
2. Open terminal and navigate to the folder with "cd" command: "cd Desktop" should go to your desktop folder, then "cd launchd*" and it takes you to the launchd folder.
3. Type in terminal: sudo xcodebuild ARCHS="i386" <- WITH THE QUOTES ON "i386".
4. If it doesn't give any errors and says something like "Build succeeded", go to the build folder (usually named "BUILD"), there might be folder named "obj" (or not). Try to find the launchd there.
5. Upload the launchd somewhere, I'll try to boot with it and my custom kernel
6. ???
7. Profit. Pure profit.

Give more details on the exact commands to write please?

[spakk]

Deltac0, on 19 November 2012 - 09:01 PM, said:

Anyone with Lion or Mountain Lion could try to compile 32-bit launchd?

Here is some instructions:

1. Download this and extract to your desktop
2. Open terminal and navigate to the folder with "cd" command: "cd Desktop" should go to your desktop folder, then "cd launchd*" and it takes you to the launchd folder.
3. Type in terminal: sudo xcodebuild ARCHS="i386" <- WITH THE QUOTES ON "i386".
4. If it doesn't give any errors and says something like "Build succeeded", go to the build folder (usually named "BUILD"), there might be folder named "obj" (or not). Try to find the launchd there.
5. Upload the launchd somewhere, I'll try to boot with it and my custom kernel
6. ???
7. Profit. Pure profit.

Hi Deltac0
I lie now in my bed and read all what you do.
I can today and tomorrow do not test because I have exams, unfortunately.
But I will read here in the forum and wishes to good succeed.

[IiTz ShAnE]

Deltac0, on 19 November 2012 - 09:01 PM, said:

Anyone with Lion or Mountain Lion could try to compile 32-bit launchd?

Here is some instructions:

1. Download this and extract to your desktop
2. Open terminal and navigate to the folder with "cd" command: "cd Desktop" should go to your desktop folder, then "cd launchd*" and it takes you to the launchd folder.
3. Type in terminal: sudo xcodebuild ARCHS="i386" <- WITH THE QUOTES ON "i386".
4. If it doesn't give any errors and says something like "Build succeeded", go to the build folder (usually named "BUILD"), there might be folder named "obj" (or not). Try to find the launchd there.
5. Upload the launchd somewhere, I'll try to boot with it and my custom kernel
6. ???
7. Profit. Pure profit.

Here you go. The whole build folder,

 build.zip   267.21K   13 downloads

[gils83]

IiTz ShAnE, on 19 November 2012 - 10:05 PM, said:

Here you go. The whole build folder,

build.zip

thank you!

it might be necessary that I install xcode !