Bare Naked Install On Phenom

just a nice simple tip always keep 2 copies of kernel on root i call 1 backup then if an update puts a new kernel on i just type backup -v -f at bootloader screen then recopy mach_kernel

@axhiya, since i rarely shut my osx down i just renamed my kernel mach_kernel2 and left it at that. after the install loaded up the old mach_kernel2 and still no load. do you think its the video kext for sure? if it loads into a blank screne? is that more times than no the problem? because if so i will def try loading the kext through…

be sure to repair permissions and boot with -v -f -x then try to install drivers from there

boot with -s then repair permissions the commands are everywhere just search

this is brief it was a response i gave to someone in a pm
personally i would do a vanilla install what you need is a retail disc. I used 10.5.4 retail then you need to restore this to a hardrive partition install chameleon to that partition copy the voodoo rc1 kernel to the root of that drive (make sure its called mach_kernel) then copy your chipset kext and dsmos.kext to extensions folder. Then boot the restored parition with -v -f -s

You now have to mount the partition as writable something like /sbin/mount -uw/

this command is on screen when you log in this way for you to copy 1 of the last lines of text you'll see on screen.
Then type

chmod -R 755 /System/Library/Extensions/
chown -R root:wheel /System/Library/Extensions/
touch /System/Library/Extensions/
this is the correct way to repair the extensions you have added as disk utility will not repair any extensions that are not meant to be there.

type exit

you should now boot into the installer.

do everything as you would do normally but you will not be asked about drivers as this is a standard mac install.

once it has finished add your chipset kext to your new vanilla install maybe your ethernet kext if its not supported in osx natively unless you have an installer you can run to get it there. Also dont forget to install chameleon and add the voodoo kernel to this drive. boot into the vanilla install with -v -f -s again
and run those permissions commands again.

This should give you a retail install on AMD this is what im running and updated to 10.5.5 no problem only thing you have to do is make sure you have an additional copy of the kernel on the root partition I call mine backup. Then when i update and apple replaces my kernel with theirs i just type backup -v -f at boot then recopy my kernel. Hope this makes sense and i havnt missed anything out. Also when doing a fresh install always update to the latest if you can before adding graphix kexts as sometimes the issues you have are caused by the fact apple has added drivers for hardware that you have and they dont like the drivers you already have.

now with the new kernel and chameleon i would use guid dont have but it has benefits

this has been answered in another thread. Plus this thread is not about any distro other than a retail.

I see you got it working
how did you fix the error you were getting

lawless, i just tried on a phenom w/ the new kernel and i got an error. you said permissions were the problem? what xactly did you do?

Just tried it on my amd system and i got a kernel panic with the appleintel kext...
Used the apple software updater...

@p-JJust tried it on my amd system and i got a kernel panic with the appleintel kext... Used the apple software updater...

me too. same thing on mine

@p-JJust tried it on my amd system and i got a kernel panic with the appleintel kext... Used the apple software updater...

or download IntelCPUPMDisabler.kext and repair permissions.

EDIT: install this before you update and it will cause the system to disregard that kext that is causing the kernel panic. Ensure correct permissions.

@nfoav8oror download IntelCPUPMDisabler.kext and repair permissions. EDIT: install this before you update and it will cause the system to disregard that kext that is causing the kernel panic. Ensure correct permissions.

will using kexthelper ensure the right permissions?

yes if you aren't comfortable with Terminal use...

if you are just copy the following:

sudo chmod -R 755 /System/Library/Extensions/ && sudo chown -R root:wheel /System/Library/Extensions/

well it installed and now it just boots into the leopard screen and just sits there and doesn't load my taskbar or anythign else. but the update went fine.

tried booting into safe moe and nothing.

@nfoav8oror download IntelCPUPMDisabler.kext and repair permissions. EDIT: install this before you update and it will cause the system to disregard that kext that is causing the kernel panic. Ensure correct permissions.

Thnx, ill try this as soon as i get home

@axhiwell it installed and now it just boots into the leopard screen and just sits there and doesn't load my taskbar or anythign else. but the update went fine. tried booting into safe moe and nothing.

Try reinstalling your gfx kexts or string.

Use your install DVD and use the Terminal to install kexts via an external drive (USB HD, Flash Drive, etc).

Do you have a other osx installation?
Try removing the kexts for youre gfx card.
If not try booting into safe mode, -x.
Hope it helps

Retail / Native Running OS X on Hacintosh

While I don't have a Phenom CPU, I thought it fitting I post here stating I am running native OS X via my Hacintosh (same one in the specs) by using the method munky proposed both here and at his original location at insanelymac.com.

http://forum.insanelymac.com/index.php?showtopic=127330 ↗

EDIT: I figure I better explain... everyone has probably read munky's post here: EFI Partition Booting - Zero Modification installs on Intel SSE2 or better → so it comes as no surprise that this method can now be used with the voodoo RC kernel on the EFI partition of a GUID partition schemed drive.

Did you use a boot 132 cd?
If so could you maybe post you're cd?
Got the same pc as you

Edit: Just did a fresh install again, updated to 10.5.5 using the apple update with the intel kext loaded.
I only had to recopy the rc1 kernel...

I did the same... I had mach_kernel and voodoo (both were the same file but one was just a rename)... that way, during an update I just used the boot flag "voodoo -f -v" and it worked… that was also back in the beta days of voodoo.

ya, since i rarely shut my osx down i just renamed my kernel mach_kernel2 and left it at that. after the install loaded up the old mach_kernel2 and still no load. do you think its the video kext for sure? if it loads into a blank screne? is that more times than no the problem? because if so i will def try loading the kext through terminal. now i just need to learn how to use terminal

@LawlessPPCbe sure to repair permissions and boot with -v -f -x then try to install drivers from there

i can't boot into safe mode. That's why I think it may be something other than my video kext

did all that and still booting into a blue screen. I mach_kernel2 (my voodoo kernel) -s
typed in this code:

sudo -s
   sudo chown -R root:wheel /System/Library/Extensions/NVinject.kext  sudo chmod -R 755 /System/Library/Extensions/NVinject.kext

and nothin

you need to include "&&" in between them... when in single user mode you don't need to include sudo

boot with "-s" and use:

/sbin/mount -uw /
cd /System/Library/
chmod -R 755 Extensions/ && chown -R root:wheel Extensions/
rm -Rf Extensions.mkext
restart

now it will load all the extensions at boot since it doesn't have a .mkext file to use (don't worry, it will recreate it).

nvoav8or -- did all that and it al went just dandy...

restarted and still just a big 'ol blue screen after my apple load screen...

any other suggestions? and again, thanks for your help all the time. you rock

are you getting any "failed" kext loads during bootup (remember to use "-v" boot flag)?

EDIT: also, do you have any conflicting graphics extensions installed?

you know what, I may have other kexts aside from nvinject, is there a way to check. and i dont see any errors except for firewire, but that always did that.

I know that this is how I do the install from Lawless

I click the first driver for nVidia which I'm not certain what it is, but I know its the one I select. Then it loads my computer fine. After that I install the nvinject kext and then my computer has QE/CI. I'm pretty certain there are other kexts in there though. That idk how to get out.

Joey

i also see an Extensions.mkext.KGrQ in my /System/Library folder, is that any good?

my nvinject says: family specific matching fails

@axhii also see an Extensions.mkext.KGrQ in my /System/Library folder, is that any good? ... i have a bunch of NVDA kexts, are those good? ... my nvinject says: family specific matching fails

NVinject family matching isn't a big deal as those NVDA... these were always a part of the problem with the GeForce kexts from early Leopard installers... (I even re-ran into this problem when I installed native to my AMD via the boot-132 method).

boot via "-s"

/sbin/mount -uw /
cd /System/Library/Extensions/
rm -Rf NVDA*
cd ..
rm -Rf Extensions.m*
reboot

The issue with the ".KGrQ" file is that it is a temporary cache file for the .mkext file when it is recreated (although named with a different extension each time).

Did that and then tried loading and it loads and then the apple splash screen wheel spins for a little then stops like its going to start loading and never loads...

side note, if i boot into safe mode, it does the same blue screen thing...as before i deleted the nvda things

Persistence, Persistence, Persitence.
nfova8or, thanks for all the advice.

Final Solution:

Clean install and didn't apply ANY nVidia drivers.
Booted up, installled RC and System 9.5.0 kext, not sure if i had to...installed nvinject. applied a PATCHED 10.5.5 w/ the great Zeph's .31 patcher.
Restarted after 10.5.5 install then I got error…

Reset my permissions and voila.

I am certain that this will work when I try again using just the RC to patch on the fly the update. But as of now, running 10.5.5 thanks for all the help again!

Although my QE is not working anymore...

don't use nvinject
remove that kext and install NVkush
or use an efi string

@bhast2don't use nvinject remove that kext and install NVkush or use an efi string

Is this a personal preference or is there some known reason now for nvinject not being usable? I use EFI now but I haven't had issues with nvinject in the past (maybe its the version type).

well if he is using the older version of Nvinject it won't work on anything above 10.5.3(if I recall) there was an issue with the code but they did release a new one to fix this
but it isn't personal preference It is just NVkush fixes this problem
But it is best to use an efi string as you don't have to worry about kexts not working with updates and what not

what is your card axhi
i know it is 8600 GT but how many MB