|
12-27-2008, 11:59 AM
|
 |
|
|
Join Date: Jan 2008
Location: The Netherlands
Posts: 280
|
|
Quote:
Originally Posted by demigod
i used the installer which came with voodoo package.in mac drive i have two files "mach_kernel" as link and "mach_kernel.voodoo" too.. i didn't modified it. and the kernel panic with VMWare is some thing to do with the update i guess.there are lots of post regarding this in vmwarefusion forum.
fusion is important for me atleast for now.so i reverted back to 10.5.5 .. 
Thanks for the help nfoav8or |
You should rename you're mach_kernel.voodoo back to mach_kernel to get vmware working...
Place the other mach_kernel in a safe location 
Code:
VMware (OS X) does not run when running on Voodoo kernel.
VMware requires the running kernel to be named /mach_kernel. This is a known
bug in VMware. Either install your Voodoo kernel as /mach_kernel (not
recommended), or remove /mach_kernel and create a symbolink link in its place
(alias) which points to Voodoo kernel (/mach_kernel.voodoo). If you used the
automatic installer, this has been done for you. If you installed the kernel manually,
refer to the Insta$ing the Kernel section for more details.
Mac Inspiron 531 » 10.6.8 • 10.8.0 Legacy Kernel • AMD Athlon 64 X2 5000+ (2.60GHz)
Dell M2N61-AX/nForce 430/MCP61 • 4GB Dual Channel DDR2 667MHz
ALC888 • nVidia GeForce 8600 GT 256 MB
2 x WDC WD5000AAKS 500 GB SATA HDD
|