Jump to content
459 posts in this topic

Recommended Posts

Ok, nevermind, I think I've done it from Windows, as I said. I've used the files that are in the folder of the Patch Solution of the install DVD. Hope I did right. Later I will boot MAC OS and see what happens! :) THANKS!

 

Good luck. You did back up the old one, right? Just in case... ;)

 

@myzar:

 

Ok then, maybe it was just me... :guitar:

i've played with maxxuss_sse the tool for controlling the sse emu and it shows in the diagnostic output 0 illegal instructions trapped, i've also run its microbench with b2 & b3 on a kernel showing sse3 and one without and it didn't show any difference outside the nominal diff you get at every run.

 

The coder of the emu aka maxxuss also said it would be impossible for his emu to be called on a sse3 cpu because there wouldn't be anything to trap.

 

If you have time to waste try base patch + amd + cpuid and it will not show sse3 , so if you guys are right the system would just crash without sse3 and without the sse3 emulator

 

 

So then There IS NO speed difference with the SSE3 patch on an SSE3 Processor vs an SSE3 Processor without the patch. Right? Emulator dosn't emulate if it is available on the CPU. :)

Good luck. You did back up the old one, right? Just in case... ;)

 

@myzar:

 

Ok then, maybe it was just me... :)

 

 

these are the benches and the info from the sse3 emu

 

Diagnostic Tool for MAXXUSS SSE3 Emulator v5.0 (10.4.4/8g1165)

 

* Version:

MAXXUSS SSE3-Emulator v5.0-8G1165

* Features:

FISTTP, LDDQU, MOVDDUP;

HT/Multi-Core supported

 

* Diagnostic Infos:

 

In-use Codeslots = 0

Full Diagnostic Info = Not Available

Slots Cleared Counter = 0

Last Invalid Instr = 0 , 0

Last Invalid Instr EIP = 0

Invalid Instr Counter = 0

Query INTR Counter = 1

InvOp INTR Counter = 0

 

Diagnostic Tool for MAXXUSS SSE3 Emulator v5.0 (10.4.4/8g1165)

 

SSE2 Pendant Microbenchmark Mix in progress ... Please wait

 

 

real 0m0.055s

user 0m0.015s

sys 0m0.002s

myzars-computer:/ myzar$ time /maxxuss_sse b3

Diagnostic Tool for MAXXUSS SSE3 Emulator v5.0 (10.4.4/8g1165)

 

SSE3 Emulation Microbenchmark Mix in progress ... Please wait

 

 

real 0m0.054s

user 0m0.015s

sys 0m0.002s

 

 

no diffs but it's better to run a kernel without the cpuid hack i agree on that, it messes with ht and dualcore but on the iso the best solution was the most generic one so you can get it running on the biggest number of boxes and you can tweak it later :)

Um, {censored}........SABR, what to do when the kernel patch didn't work and now it won't boot?

Tried these steps:

 

sudo cp /mach_kernel /kernel-backup/mach_kernel.backup

 

sudo rm /mach_kernel

 

sudo cp /kernel-backup/**NAME OF PATCHED MACH_KERNEL HERE** /mach_kernel

 

 

I could have messed up patching, or copying the kernel......

 

Now it's hosed! Is their a way to boot offa an Install disc to get the old kernel back in terminal?

 

 

I FIXED THIS: Maybe this is a no brainer for some, but I was able to use: /kernel-backup/mach_kernel.backup

 

I typed that while starting up and it worked, thank god!!!

Um, {censored}........SABR, what to do when the kernel patch didn't work and now it won't boot?

Tried these steps:

 

sudo cp /mach_kernel /kernel-backup/mach_kernel.backup

 

sudo rm /mach_kernel

 

sudo cp /kernel-backup/**NAME OF PATCHED MACH_KERNEL HERE** /mach_kernel

I could have messed up patching, or copying the kernel......

 

Now it's hosed! Is their a way to boot offa an Install disc to get the old kernel back in terminal?

I FIXED THIS: Maybe this is a no brainer for some, but I was able to use: /kernel-backup/mach_kernel.backup

 

I typed that while starting up and it worked, thank god!!!

 

Did you literally type:

 

sudo cp /kernel-backup/**NAME OF PATCHED MACH_KERNEL HERE** /mach_kernel

 

?

Did you literally type:

 

sudo cp /kernel-backup/**NAME OF PATCHED MACH_KERNEL HERE** /mach_kernel

 

?

 

No......of course not. I got it to at least boot back up. But still have the sse2 kernel from the patched DVD. It seems to be running fast, I think I patched the file wrong.

Hmm, one thing I noticed during my install though (well I think I saw it), AMD Enabled or something like that was ticked by default... but I haven't noticed any odd behaviour of the OS.

Can anyone confirm this please? is there any way of being able to check myself? :D

 

The extra choices added for a custom install, are enabled by default. I believe this was done to cover as many generic combinations as possible. I have installed with and without the AMD option with an intel 3.2 ghz chip, and noticed no differences. imo

 

Perhaps someone more qualified can give a more technical explanation.

 

In this thread about patching to get the correct information to show up in system profiler, as an indicator of sse3 support, I have experienced this successful combination of patches:

 

Within the Kernel_Patchfiles folder, using the patch file "patch-base.ppf" and "patch-amd_enabler.ppf" to patch "mach_kernel.orig" is correct.

 

If I just use "patch-base.ppf" I get to the blue screen and that's it.

If I use the combination of "patch-base.ppf" and "patch-cpuid_panic.ppf", I get a automatic reboot.

 

anyone else with similar experiences

 

kaos

To Myzar:

 

I have used the installation disk and everything went ok. Everything working. Then I've changed the installed kernel with one only base patched because I have Intel CPU, SS3 and NX. It shows SS3 at boot but when it swirches to graphic mode I have only a blue screen with the mouse arrow.

I also tried to install it.. Two problems:

 

- I can only use the dvd when I boot using the '-v' option. Without I get the 'com.apple.bootlist not found' error.

 

- After I installed the dvd there is a blinking minus forever.. I tried to fix the permission booting back to the dvd again but without luck...

 

Anyone?

I had this last post problem, but I´ve done this:

 

1) Booted up 10.4.4/5 Myzar Patched DVD and ERASED the HD I choose to install OS X. Quited Disc Utility and restarted the PC

2) Installed the OSX without .5 atualization - All fine and working, no more blinking cursors. Darwin boot fine!

3) Rebooted and performed an upgrade to 10.4.5. Everything fine at all.

 

Will try again to install directly to 10.4.5 later today.

Hello everybody,

 

I am currently in the process of downloading this file, but have a pre-installation question for you all. I have a Compaq V2402AU laptop with a ATI Radeon Xpress 200M IXP card. My question is this, will Quartz Extreme and Core Image be supported for this card under OSx86? If so, will it work 'out of the box' or will I have to tweak some stuff in order to get it working? I'd appreciate some answers, as I am absolutely new to this whole thing.

 

Regards,

Dhruv

To Myzar:

 

I have used the installation disk and everything went ok. Everything working. Then I've changed the installed kernel with one only base patched because I have Intel CPU, SS3 and NX. It shows SS3 at boot but when it swirches to graphic mode I have only a blue screen with the mouse arrow.

 

 

you need to add the amd enabler to the kernel too , a bunch of files like loginwindow and the ui server are patched for amd on the dvd and since osx installation is the worst abomination ever coded by man, it's a {censored} inbred, some files are copied from the packages some directly from the dvd, that's the reason why is needed.

 

So the min patch reqs are base + amd enabler

The extra choices added for a custom install, are enabled by default. I believe this was done to cover as many generic combinations as possible. I have installed with and without the AMD option with an intel 3.2 ghz chip, and noticed no differences. imo

 

Perhaps someone more qualified can give a more technical explanation.

 

In this thread about patching to get the correct information to show up in system profiler, as an indicator of sse3 support, I have experienced this successful combination of patches:

 

Within the Kernel_Patchfiles folder, using the patch file "patch-base.ppf" and "patch-amd_enabler.ppf" to patch "mach_kernel.orig" is correct.

 

If I just use "patch-base.ppf" I get to the blue screen and that's it.

If I use the combination of "patch-base.ppf" and "patch-cpuid_panic.ppf", I get a automatic reboot.

 

anyone else with similar experiences

 

kaos

 

Cheerz for the reply kaos :)

Anybody tried to apply what jrrjrr said?

 

http://forum.osx86project.org/index.php?showtopic=10601

 

 

Need to Undo Maxxuss AMD-Enabler Patch.. How?

 

These were the instructions I used. They are from Maxxuss' site and changed a little for my installation, so double check the file and folder names mentioned...

 

Open the "cpuid_patches.txt" file in a text editor and swap out the second and third lines, so it looks like this:

 

2

cd fb

0f a2

 

Save it to a new name like "cpuid_patches_1045_UNDO.txt".

 

Then, place the AMD_Enabler folder (with a desired new kernel added inside it) at the root of the volume.

 

 

Reboot, with the "-s" option. You have to enter single-user mode to replace the files.

 

* Mount the volume writable by executing

fsck -fy

mount -uw /

 

* Execute the patcher command from within the AMD_Enabler folder. Pipe the command through "less" and browse the output:

 

cd /AMD_Enabler

chmod 755 patcher

./patcher cpuid_patches_1045_UNDO.txt | tee result.txt | less

 

It's OK if not all files can be found and patched. Some files might be missing due to your customized installation.

 

* Replace the existing kernel with the desired kernel:

mv /mach_kernel /mach_kernel_old

mv mach_kernel.all /mach_kernel

chmod 755 /mach_kernel

chown root:wheel /mach_kernel

 

Then type:

 

reboot

 

and it should boot up and run fine, with the new kernel and unpatched files.

The extra choices added for a custom install, are enabled by default. I believe this was done to cover as many generic combinations as possible. I have installed with and without the AMD option with an intel 3.2 ghz chip, and noticed no differences. imo

 

Perhaps someone more qualified can give a more technical explanation.

 

In this thread about patching to get the correct information to show up in system profiler, as an indicator of sse3 support, I have experienced this successful combination of patches:

 

Within the Kernel_Patchfiles folder, using the patch file "patch-base.ppf" and "patch-amd_enabler.ppf" to patch "mach_kernel.orig" is correct.

 

If I just use "patch-base.ppf" I get to the blue screen and that's it.

If I use the combination of "patch-base.ppf" and "patch-cpuid_panic.ppf", I get a automatic reboot.

 

anyone else with similar experiences

 

kaos

 

I get pretty much the same thing. I think the problem is that the DVD automatically installs the AMD patches (which touch much more than just the kernel). When you try to use a non-AMD patched kernel, it breaks compatibility with other parts of the system. I was looking at modifying the Owned.pkg to not install the AMD stuff for those of us with Intel processors. Fixing the DVD would then be a matter of making an image from the DVD, mounting it read-write, replacing the Owned.pkg in the image, then burning the image back to disc. I think this should work, but would of course require re-installing the system. I don't see an easy way of un-patching all of the files that the AMD patch touched.

 

edit: First I guess I'll try the un-AMD script above. maybe that will fix things for me. The worst that could happen is that I'd have to re-apply the AMD patches

 

edit 2: FreeSoftwareMan, you are brilliant! It worked perfectly.

×
×
  • Create New...