Jump to content

IM's AMD MAVERICKS TASK FORCE


Sinetek
 Share

40 posts in this topic

Recommended Posts

bootloader chameleon .

 

1) system 10.9 on amd . 

2) kernel 10.9 patched for amd .

3) if start and running system 10.9 with flag -s , stop at "launchd" . 

4) if copy files *.dylib from 10.8.3 to 10.9 - it is working and continue running to single user !

5) if without flag -s ---- no GUI , stop at MACH_SUCCESS...

 

no files log.

Link to comment
Share on other sites

bootloader chameleon .

 

1) system 10.9 on amd . 

2) kernel 10.9 patched for amd .

3) if start and running system 10.9 with flag -s , stop at "launchd" . 

4) if copy files *.dylib from 10.8.3 to 10.9 - it is working and continue running to single user !

5) if without flag -s ---- no GUI , stop at MACH_SUCCESS...

 

no files log.

 

Using your 10.9 kernel this is where it gets stuck for me, http://www.insanelymac.com/forum/topic/281450-mountain-lion-kernel-testing-on-amd-dont-ask-help-here-use-the-help-topic/?p=1938486

 

All 10.9 vanilla so far.

Link to comment
Share on other sites

:)

 

Avec le noyau Bronya 12.3 fix et Extension 12.3 avec Sandbox et corecrypto 13.0 , je vais jusque "kernel LP 64" suivi de USB.....xxxx  et le système se fixe sans KP , corecrypto à l'air de passer mais Sanbox is failled . :(  AppleFSCompression passe (normal)

 

la tentative était bonne à faire malgrès les résultats perdu d'avance .

 

With the kernel fix and Extension Bronya 12.3 12.3 13.0 corecrypto with Sandbox and I'll even "kernel LP 64" monitor ..... xxxx USB and the system fixed without KP corecrypto air to pass but is Sanbox failled. (AppleFSCompression password (normal)

the attempt was good to malgrès results already lost.

  • Like 1
Link to comment
Share on other sites

Perhaps!

 

The commpage.c of every kernel i saw has a case/switch function that checks the CPU capabilities. My preliminary attempts in the early ML kernel development were by bypassing this function (obviously it wasn't enough, since those days there was not the opcode emulator, so it would crash further ahead in the userland). Perhaps there's also a function for effectively check the CPU ID?

 

Where exactly this check is located, Bronzovka? I suppose you're disassembling the binaries and scrutinizing the hex files for it, right?

 

In C, it used to be like this:

 

 

switch (cpu_info.vector_unit) {
case x:
bits |= instruction;
/* fall thru */
case x-1:
bits |= instruction 1;
/* fall thru */
.
.
.
case x-n:
bits |= instruction n;
 
Can you bypass it, if it's the case here?

 

 

 

All the best!

Link to comment
Share on other sites

:)

 

hello Bronya  :)

 

cette tentative , je l'ai fait sur AMD , tu penses que Sandbox 10.9 bloque le CPU AMD ? avec le noyau 10.9 vanille , c'est reboot direct , je pensais mettre les Frameworks 10.8.3 pour aller plus loin .

 

this attempt, I made it on AMD, you think Sandbox 10.9 blocks AMD CPU? with vanilla kernel 10.9 is live reboot, I thought put 10.8.3 Frameworks to go further.

Link to comment
Share on other sites

Perhaps!

 

The commpage.c of every kernel i saw has a case/switch function that checks the CPU capabilities. My preliminary attempts in the early ML kernel development were by bypassing this function (obviously it wasn't enough, since those days there was not the opcode emulator, so it would crash further ahead in the userland). Perhaps there's also a function for effectively check the CPU ID?

 

Where exactly this check is located, Bronzovka? I suppose you're disassembling the binaries and scrutinizing the hex files for it, right?

 

In C, it used to be like this:

 

 

switch (cpu_info.vector_unit) {
case x:
bits |= instruction;
/* fall thru */
case x-1:
bits |= instruction 1;
/* fall thru */
.
.
.
case x-n:
bits |= instruction n;
 
Can you bypass it, if it's the case here?

 

 

 

All the best!

Hi ! It is instructions if in processor's have use , example ssse3 ... :)

If delete  "bits |= instruction 1" - kernel 100 % no working ! 

 

You see . Maybe it is check platform , maybe it stop at "launchd" :

post-31928-0-15118800-1376411671_thumb.png

:)

 

hello Bronya  :)

 

cette tentative , je l'ai fait sur AMD , tu penses que Sandbox 10.9 bloque le CPU AMD ? avec le noyau 10.9 vanille , c'est reboot direct , je pensais mettre les Frameworks 10.8.3 pour aller plus loin .

 

this attempt, I made it on AMD, you think Sandbox 10.9 blocks AMD CPU? with vanilla kernel 10.9 is live reboot, I thought put 10.8.3 Frameworks to go further.

hello ! in 10.9 special symbol's , in 10.8 no symbol's . and it don't working sandbox from 10.8.3 .

  • Like 2
Link to comment
Share on other sites

@Bronya    Они сняли SSSE3 bcopy, ваш AMD не имеет SSE4_2 так она не запускается. Необходимо пропатчить ядро немного.

libplatform не имеет значения
Edited by theconnactic
Please, folks, from now on i'll ask you guys to either post in english or translate your posts for others to follow the conversation. :) All the best!
  • Like 1
Link to comment
Share on other sites

 

@Bronya    Они сняли SSSE3 bcopy, ваш AMD не имеет SSE4_2 так она не запускается. Необходимо пропатчить ядро немного.

libplatform не имеет значения

 

Sinetek !  Да я посмотрел что libplatform не имеет значения . Но мой процессор FX имеет поддержку " hw.optional.sse4_2: 1 " . :)

Между прочим всё это зависит от библиотек *.dylib . 

Я вышлю рисунок :) .

post-31928-0-59295000-1376590961_thumb.jpg

 

It is i copy lib 10.8.3 to 10.9 and working . If original lib 10.9 , no working - stop at "launchd".

Edited by theconnactic
Please, folks, from now on i'll ask you guys to either post in english or translate your posts for others to follow the conversation. :) All the best!
  • Like 1
Link to comment
Share on other sites

@Bronya  Попробуйте с 32bit /sbin/launchd    

или launchd из МЛ, не 64-bit

Edited by theconnactic
Please, folks, from now on i'll ask you guys to either post in english or translate your posts for others to follow the conversation. :) All the best!
  • Like 2
Link to comment
Share on other sites

@Bronya  Попробуйте с 32bit /sbin/launchd    

или launchd из МЛ, не 64-bit

Ок , попробую .

Launchd 32 битный не будет работать .

post-31928-0-87620600-1376595930_thumb.png

Edited by theconnactic
Please, folks, from now on i'll ask you guys to either post in english or translate your posts for others to follow the conversation. :) All the best!
  • Like 2
Link to comment
Share on other sites

  • 2 weeks later...

Получилось пройти дальше синглоюзверь мода? Вообще на сколько это возможно запустить последующую версию мака с ядром от предыдущего? Может проверить на интелах? Я могу воткнуть в макбук старый mach_kernel, у меня сейчас 10.9, ну, если есть смысл.

Have you managed to pass through singleuser mode? Is it even possible to startup a new macosx with a kernel of an old one? Maybe we should check this on intel? I can replace a mach_kernel on my macbook, I have 10.9 set up and running.

Link to comment
Share on other sites

Получилось пройти дальше синглоюзверь мода? Вообще на сколько это возможно запустить последующую версию мака с ядром от предыдущего? Может проверить на интелах? Я могу воткнуть в макбук старый mach_kernel, у меня сейчас 10.9, ну, если есть смысл.

 

Have you managed to pass through singleuser mode? Is it even possible to startup a new macosx with a kernel of an old one? Maybe we should check this on intel? I can replace a mach_kernel on my macbook, I have 10.9 set up and running.

Hi ! on intel normal working . On amd don't working . If copy lib*files.dylib , working , but no guy ... 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...