Technical FAQ

From OSx86
Revision as of 00:53, 5 April 2007 by (Talk)

Jump to: navigation, search

Use this FAQ page to answer all the technical questions that are usually asked! This is not a place to ask for help. Use the forum instead.


Want Access to a whole community of os x x86 users who know it all?" go to They have all the answers!

Commonly Asked Questions

Q: Why do I get a kernel panic on boot from GeForce.kext and how do I fix it?

(commonly asked in #OSx86 on
A: Boot to command prompt with -s and type:

mkdir /GeForce
mv /System/Library/Extensions/GeForce* /GeForce

That should fix it.

Q: Why do I get an Ebios error when booting and how do I fix it?

A probable cause is a defect dvd. Try burning it again. DVD-RW seems to work well.

Q: How can I install the MacVidia Beta 2 Driver?

Please note that the following guide is no longer relevant for later builds of the BETA driver. For comprehensive instructions of how to install newer releases, reference Joost's guide here A2: There is now an installer!

A: The following guide was created using info from Omni and Domino's posts:

( Warning, this procedure is not guaranteed to work for everybody. This MacVidia release is still a BETA, and the 1st one at that... Proceed with caution Also, please read the thread about this driver. There have already been many issues reported, and np_ is already working on a beta 1 build 1 to address them. In particular, many people with nForce chipsets on their motherboards have issues. I have tested the following method with my Intel 865P chipset mobo, Asus nVidia FX 5700 card with excellent results. As always your mileage may vary, so please read the thread ahead of time, and make sure to make the suggested backups, in case of failure.)

  • 1. Download the attachment from the original post, here

       [If you choose to install the newer version,, you can find it here,
        however these instructions may need some modifications for build 1. Check the forum posts for that.]
  *****Update: There is now a 2nd update, which can be downloaded here (NB: i don't think the directions below work with this!! without build1 first??)
              np_ has also added a bonus file, See his post for more info.

  • 2. Unzip the file on your desktop

         *****I highly recommend performing all the remaining steps from terminal*****
         *****In terminal: type "sudo su" and enter root password, to become root*****
         *****After doing so, you won't have to type sudo at each line. BE CAREFUL*****

  • 3. The only file from the archive you will edit is the NVidiaHAL.kext

         3.a Open the content of NVidiaHAL.kext (for build2: right click> show package contents) and browse to the Info.plist
         3.b Edit the following line of the Info.plist (right click> open with> other> applications> textEdit) with your Device ID:


               Using your Graphics Card Device ID in place of ####
               (visible in System Profiler>>Graphics/Displays) for example, 0281, or 0342.
         3.c Save the file and close all the windows

  • 4. Create a new folder on your desktop and name it Original nV kexts
  • 5. Copy the following 7 files from your /System/Library/Extensions folder to Original nV kexts (as a backup)
           NVDANV10Hal.kext    NVDAResman.kext
           NVDANV20Hal.kext    GeForce.kext
           NVDANV30Hal.kext    GeForceGA.plugin
  • 6. Delete the above 7 files from the /System/Library/Extensions directory
  • 7. Copy the 4 new files from Step 2 to the /System/Library/Extensions directory
  • 8. Do all the following commands:
           chown -R root:wheel /System/Library/Extensions/NVidiaHAL.kext
           chown -R root:wheel /System/Library/Extensions/NVidia.kext
           chown -R root:wheel /System/Library/Extensions/NVDriver.kext
           chown -R root:wheel /System/Library/Extensions/GeForceGA.plugin
           chmod -R 755 /System/Library/Extensions/NVidiaHAL.kext
           chmod -R 755 /System/Library/Extensions/NVidia.kext
           chmod -R 755 /System/Library/Extensions/NVDriver.kext
           chmod -R 755 /System/Library/Extensions/GeForceGA.plugin
  • 9. Use Disk Utility and repair permissions on your system drive
  • 10. Delete Extensions.kextcache and Extensions.mkext from your /System/Library directory
  • 11.Delete any files named or from the following 3 directories:

                           *****make sure to substitute your actual username in place of "yourusernamehere"*****  ;-)

  • 12. Edit  in /Library/Preferences/SystemConfiguration/ and remove the "Graphics Mode" key and string
  • 13. reboot with -v flag

Poochie's experience:
If they work, but only in safe mode, edit Info.plist of the following kexts:
IOGraphicsFamily.kext, NVidiaHAL.kext, NVidia.kext, NVDriver.kext replacing the string "Safe Boot" with "Root".
This worked for me on a DFI SLI DR S939 and a PCI-X Asus 6600 GT 128 MB (DevID 0x0140)

phor2zero's experience:
In addition to Poochie's instructions, in order to boot up in normal mode I had to edit /etc/rc and add the following 3 lines at the very top:
kextload /System/Library/Extensions/NVDriver.kext
kextload /System/Library/Extensions/NVidiaHAL.kext
kextload /System/Library/Extensions/Nvidia.kext
This worked for me on an Asus A8N-SLI Deluxe with a PCIe EN7800GTX 256MB (DevID 0x0091)
I now have perfect 1440x900 rez on my Westinghouse 19" Widescreen LCD at normal bootup.
(I used NVDriverBeta1Build1 which is now available.)

A special thread devoted to the installation of the NVDriverBeta1 can be found here:

Q: Is there an easier way of installing np_'s nVidia driver (aka I-fear-the-Terminal)?

A: Fortunately yes! User tomaik has kindly made an easy-to-use installer for installing np_'s nVidia driver. Find it here:

Or you can go to , register, and get the latest installer-package (the red link).

Q: What are the solutions to the "Still waiting for root device" message?

A: The most common solution is making your OSX drive the primary IDE. Try disconnecting all the other hard drives, make the OSX drive IDE0, using either cable-select or Master jumper settings. In my particular case, Darwin only sees the "root device" if it's in the primary IDE slot.

A2: Try many boot option:

   platform=X86PC -v
   -x -v
   rd=disk0s* -v (replace the * with your OS X partition number)
   -f -v

A3: Try other bootloaders:

  • Windows 2000/XP/2003 BOOT.INI is one of the easiest and best options. Many people use this method.
  • GRUB WARNING: GRUB can cause some serious damage in the MBR of your HDD.

It may cause the same problem.

  • LILO
  • boot0: The FreeBSD bootloader.

A4:Use IDE drives, or patch for SATA

How do I get a PS/2 keyboard to work?

A: There are a few tips regarding this subject on the forums. PS/2 apparently is not recognized by OS X if there is a USB mouse attached. The easiest solution is to use USB keyboard and mouse, or some mice include an adapter to allow them to operate off the PS/2 mouse port. Basically, you need to be all one way or the other for the OS to function correctly.

One thing that might work for you is to boot the system up with a PS/2 keyboard connected and then once you get the blue Mac OS background screen, plug in the USB mouse. This has worked with the Dell Mice as well as the Logitech Cordless Optical Trackman.

Alternatively, people have found that sometimes going into BIOS and disabling the USB (legacy) keyboard and mouse settings work. Note, you leave the USB ports enabled and strictly disable the keyboard and mouse USB functions in BIOS, if available.
Lastly, people patch the /etc/rc file thusly:
if [ "${VerboseFlag}" != "-v" ]; then
kextunload /System/Library/Extensions/ApplePS2Controller.kext/Contents/PlugIns/ApplePS2Keyboard.kext
kextload /System/Library/Extensions/ApplePS2Controller.kext/Contents/PlugIns/ApplePS2Keyboard.kext
exit 0

If your PS/2 keyboard works the first time after installing but then doesn't work on subsequent reboots, it's probably a permissions error on the /System/Library/Extensions/ApplePS2Controller.kext directory. Unfortunately, repairing permissions via Disk Utility doesn't fix it, you have to do it yourself:

cd /System/Library/Extensions/ApplePS2Controller.kext
sudo find . -type d -exec chmod 755 {} \;
sudo find . -type f -exec chmod 644 {} \;

I've successfully used a PS/2 keyboard with a USB mouse with these permissions set correctly.

On a Dell 270, a ps2 keyboard has been succesfully recognized AFTER the instlallation using an usb keyboard. Nothing has been touched in the bios It's a compaq french keyboard, bad part is that the mapping is the one from an apple USB keyboard (keyboard utility doesn't work with this one, the touch are recognized as an internal keyboard)

On an eMachines T3120, I have no way to try this, since neither PS/2 mouse or keyboard works. On an eMachines T5026 I can use a PS/2 or USB keyboard, but can only use a USB mouse.

Q: How do I enable sound with an AC 97 codec or SB Live! ?

Apple system profiler nor dmesg show that a sound card has been detected. A: But it works, doesn't it? In the TipsnTricks there is stuff about getting AC97 sound to work. For me AC97-Sound worked without any changes when i deleted the ATI-Drivers and so was able to boot up without safe-mode enabled. Try

In some cases, people have found that their card is recognized, the driver is loaded, you can adjust the volume, etc.. but there is no sound. Try tweaking the settings in Audio MIDI in the Utilities folder. For example, try setting your output to 4 or 6 channels and set the active speaker configuration to channels 3 and 4 or 3 and 6. [This is especially work with HP dx2000MT Desktops]

Q: I have an SSE3 CPU. I am using the Deadmoo image, but I can't get PowerPC applications to run.

A: Excellent question, one that has been causing big headaches for a lot of users. You see, the Deadmoo image has patched out support for CoreGraphics, which is what iTunes and alot of other apps (this is why an install of Photoshop or other programs might be failing) need to run. All you have to do is replace the patched file with an unpatched version, then activate it using Terminal. The file needed can be found at:;4050152;;/fileinfo.html

Instructions: Go to terminal and type this stuff cd /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A chmod 755 CoreGraphics.sse3 sudo chown root:wheel CoreGraphics.sse3 sudo mv CoreGraphics CoreGraphics.original sudo mv CoreGraphics.sse3 CoreGraphics

Q: I'm using the Deadmoo image. How can I resize my partition without erasing the Mac OS X installation?

A: Don't use iPartition or VolumeWorks to resize a partition, you'll mess up your install because they don't support pc style partition tables! You can, however, copy the installed system to a bigger partition on the same or on a different HD. There are several ways of doing that:

1. There is a program called Carbon Copy Cloner that is free. I installed a second HDD partitioned it the way I wanted and then copied over my original 6GB with this app. You need a special app like this one to make the drive bootable when your done. You can get the program here.

You also need to install the boot loader on the target partition, this isn't done by Carbon Copy Cloner because it was designed for PPC Macs. This can be done by installing Darwin on the partition beforehand, or apparently using fdisk in Mac OS X - see 2. below.

2. The easiest method to accomplish this is to install Darwin on the drive/partition you want, then use Disk to restore your working OSX to the new drive. To do this, in disk utility, select any drive, the click restore. For the Source and Destination you simply drag and drop the partitions from the pane on the left. After the restore is done, click the newly restored partition, then on First Aid, then Repair Disk Permissions. After this is accomplished, you can now boot from the newly created drive. (If you check erase button in restore pane, then you can not get bootable partition. Rather delete all files by using "rm -rf *" and "rm -rf .*" at the root directory of the new partition.)

EDIT: This can be done without first installing Darwin. The only thing Darwin is doing for you here is setting the partition as active or bootable. You can simply use Disk Utility 'Restore' to copy to a fresh hfs+ partition and then set this new partition as 'active' or 'bootable' using fdisk: sudo fdisk -e /dev/rdisk1 - You must substitue the correct device name for the new disk. At the prompt type: print - You should see a table with one row for every partition. Figure out which is the partition you intend to make bootable, note the number, n, of the partition (likely 1), and type: flag n. Then type: write, then: exit. Now you should be able to boot from the disk with the new partition.

  EDIT: Doesn't work for me! Installing Darwin (5.0.122) first and restoring the original partition
  to the disk (with erasing or not, Carbon Copy Cloner or Disk Util, it doesn't matter) loads Darwin
  and Darwin kext, but that's it Os X doesn't continue booting after Darwin! And making the partition
  active or bootable usinf fdisk isn't installing you an PC Bios compatible Bootloader the boot your
  partition! Works under Open or Extended Firmware, doesn't in a PC! Sorry, I tried all this guides
  to enlarge my partition and not one of them worked! And "parted" under Ubuntu Install crashes my
  filesystem twice! So don't do this!!!! USE VMware TO INSTALL IT NATIVE!!! LOOK IN FORUM

3. Another possibility is using Apple Software Restore to write the deadmoo image to a bigger partition. You need a functional Mac OS X install (x86 or PPC) and some disk space for that. Use the man pages to familiarize yourself with the tools used: man hdiutil and man asr. I don't remember all the details since it's been some time since I did it, but it went somewhere along the following lines:

  1. copy the HFS partition out of the image: dd if=tiger-x86-flat.img of=tiger-x86-hfs.img iseek=63 or tar xjOvf tiger-x86.tar.bz2 tiger-x86/tiger-x86-flat.img | dd of=tiger-x86-hfs.img iseek=63
  2. convert it to an UDRW disk image: hdiutil convert tiger-x86-hfs.img -format UDRW -o tiger-x86.dmg
  3. scan it with asr to enable restoring: asr -imagescan tiger-x86.dmg
  4. write it to the partition: asr -source tiger-x86.dmg -target /dev/diskxsy -erase ASR should then perform a block copy ("Restoring..."), even if the destination partition is bigger than the original image.

4. Use a linux boot disk with parted included. I tried this with the gentoo x86 install disk. I'm not going to go into step-by-step cause you should know what you're doing before you start messing with your disk partitions. Tips:

  • parted can't move the beginning of the partition for hfs+, only the end.
  • parted sets the filesystem type to Linux. Open cfdisk and reset it to af.

Q: Which SATA controllers work?

A: Working extensions for SATA are:

ICH5 Serial ATA Controller
ICH6 Serial ATA Controller
ICH6-M Serial ATA Controller
VIA SATA Controller
8237 SATA
nForce3/4 (need to edit above kext with device ID's)
nForce 3/4 ata and sata supported. Should work on mcp chipset too.
See this thread on the forum: link

Q: Why does my PowerPC-based application not load when I click on it?

A : This usually means that you do not have Rosetta functioning properly. Rosetta is how Intel-based OSX runs applications that were written for the PowerPC version. From what I gather, in order to use Rosetta, you will need either a SSE3-enabled CPU, or a patch that lets you emulate SSE3 instructions on a non-SSE3 processor. If you are running the deadmoo image and have an SSE3-compatible CPU, you must replace CoreGraphics with a non-patched version; reboot after replacing it, and Rosetta should work.

If you have a non-SSE3 processor and use the Patches made by Maxxus (currently v5), you may notice that some applications do still crash, e.g. Safari, you can get around this by doing the following: Right-click on Safari-Icon in dock. Choose open in finder. Right-click and chosse Get Info. There you can set: Run with Rosetta. This should solve the problems.

To obtain this patch, try SSE2 patches, the forums, or Tips and Tricks

Q: What is AppleACPIDisplay.kext and how can I get it to load correctly?

A: it allows OSX to control power management. On some systems it does not function correctly. If it does not load corectly just use


in the bootloader, or add it in the boot file (that way you dont need to write it every time after). A -v is also usefull for faster osx.

Q: I get a blue background with mouse and boot screen (only with -F) but nothing load?

A: The partition table is not edit when you install darwin or osx, there is no real reason for darwin but the parititon stay NTFS FAT32 or EXT3 (it depend of what os you was using). For fix this problem, you need to use AF partition format and use UBUNTU live-cd for edit the parition table. It is not in the list but dont worry. After, the windows bootloader and GRUB will be able to work. For the first time, reboot FROM WINDOWS and when the bootloader will apear, choose tiger-x86 (OS X) and in the advenced part, write: platform=X86PC -v
Good luck!
NB: See also Technical FAQ#Why do I see only a blue screen when booting?

Q: How can I prep a partition for OS X under Windows XP?

A: Start > Run > diskpart
Then once the command (black) window opens, type in these commands (return after each):
list disk (should show at least 1 drive listed)
select disk 1 (change this number to correspond to the drive listing number for the hard disk you're going to install OS X upon)
list part (You may or may not have partitions established on the disk you selected)
The next two steps are only needed if you are going to remove an existing partition for OS X use:
select part 2 (whatever partition in the list you intend for OS X)
delete partition
In either case, continue below:
create part primary id=AF (the drive selected now has free space for an OS X partition)

Then shutdown/reboot your install DVD. If you get past the language selection, choose Disk Utility from the Utilities menu, then click the new partition listed (usually a name like s0d2), and erase it. Request the OS X Journaled format. Then when that's done, quit the Disk Utility and continue installing.

Q: What are patched kernels?

A: mach_kernel is a special binary file that exists on the root (base) directory of a Mac OS X install DVD. Most patches released currently involve patching the ISO image of this DVD with the various bit-and-byte changes between the original and a more PC compatible version, which in many cases can be then burned, booted, and installed.

Previously, and in certain customization procedures, patches (PPF) are applied to the original PC compatible mach_kernel, usually known as mach_kernel.orig. The result is known as a patched kernel.

Q: How are patched kernels used?

A: The patched kernel must replace the existing mach_kernel normally included in an original boot DVD. There are many methods to achieve this. On a PC, a utility known as TransMac can import .dmg and .iso files, access the macintosh file system inside, and perform file functions (copy, rename, delete) on the contents. The result can then be saved to disk, or burned directly by the utility.

The Disk Utility included with Mac OS X 10.4 can save disk images in "CD/DVD Master" format. Although the extension by default is .cdr, it is an ISO image. ISO images can be mounted by using the command "hdiutil attach MY_ISO.iso -readwrite" from a terminal (console) window. Then you may use the mounted volume as you would any other re-writable media, and upon eject, the changes would be saved and then you can proceed to burn the image with Disk Utility or Toast.

NB: A working OS X system can use a number of different kernels. The file contains an entry indicating what name the desired boot kernel goes by. Originally, it is mach_kernel. These kernel files are assumed to be at the "root" (base directory) of the volume. The file is found in /Library/Preferences/SystemConfiguration/ directory. It is an XML file, so be sure to follow the format you see when editing it using an ordinary text editor.

Q: What are PPF files?

A: PPF files are Playstation Patch Format files. The utility that operates with them is so generic, it is a good binary-level editing program with the ability to validate and undo patches to binary images. When patching a kernel, usually the mach_kernel.orig file is used as the "binary" input to a PPF utility, and developers come up with various PPF files that address issues like SSE3 emulation, various kernel panics during boot or installation, and so forth.

As of this writing, the Paradogs PPF-o-Matic is not fully stable or functional except as a PC executable. Use the Mac and Java versions with caution. General use is to select as input your kernel image, select the patch file you want, and either apply or undo the patch. Undoing can be done repeatedly without error. NB: Some patch files assume the binary is the ISO of a bootable DVD, so make sure you know what you're doing. If the PPF patcher complains, chances are you selected the wrong patch file and/or are trying to apply it to the wrong binary data.

Why do I see only a blue screen when booting?

A: One of the first things done by Mac OS when booting (after the initial loading and initialization) is to ask the user for a preferred language to use for the installation. If you have problems with Rosetta, you will see the blue background and a "beachball cursor" but no list of languages.
NB: Laptop users experiencing blue screen may need an external monitor attached, or a dongle. See Forum Entry.

What do I do if I suspect Rosetta isn't working?

A: Make sure you have a compatible CPU. There are patches to make Rosetta work if your CPU supports the SSE2 instruction set. SSE3 is the assumed instruction set Rosetta originally was coded for. The JaS 4.2b patch creates a bootable DVD that has SSE2 support. It also should be harmless on SSE3 machines.

Rosetta is required during the installation process, and afterward, it is intertwined to certain rarely-used OS functions. The easiest way to check to see if Rosetta is working is to run an application you know is NOT in Universal Binary format, only PPC or regular Mac OS X format. Rosetta is the mechanism by which this PPC legacy software is made to work.

Less Frequently Asked Questions

Q: When I boot, I get a "HFS+ partition error." I have booted many times before.

A: You did something under "Startup Disk" in System Preferences. To fix this, boot into the ubuntu live cd and write cfdisk in Terminal, which should list every partition on the hard disk. OSX will have a boot tag. Remove it by pressing enter, then press enter on your grub\boot.ini partition.

  • Never play under Startup disk. While OSx86 is made to be a primary os, this feature doesn't correctly work.

Q: Why don't Chess and the DVD Player work? I only see a grey screen.

A:Both Chess & Preview (& Grapher 3d) rely on OpenGL to draw their views. This can be modified for Preview by editing in your preferences folder. If you have an intel extreme graphics board and got OpenGL / Quartz Extreme to work, all these apps work right.

Q: I have a compatible system (well, my AMD64 3000+ is SSE3-less). Why doesn't booting from USB-HDD work?

A: It does not work because of 2 possible things.

  1. Your motherboard is emulating the HD as something. Check your bios settings.
  2. Osx86 does not support your USB controller fully and that is causing issues.

My understanding was USB only fully works on motherboards with an Intel ICH6 southbridge.

One way to work around the first problem if your BIOS doesn't allow booting from the USB Hard Disk, you can use the linux bootloader GRUB to boot off of a USB-HDD.

Q: Where is the rest of iLife in the Deadmoo image?

A: iLife is not bundled in the devkit dvd, only iPhoto is provided. To use iLife you need to install a PowerPC version, it will run fine with Rosetta.

Q: Is there a way to install the Classic MacOS environment on the Deadmoo image?

A: The "Classic" environment in OSX won't work on your PC. Classic works by letting your Mac fall back to OS9 to run older programs, it won't work on an x86 PC at all, as OS9.2.2 (the version of OS9 used to run Classic) is pure PowerPC code. Rosetta doesn't come into play. Getting Classic to run within OSX x86 is impossible. Unless perhaps, someone were to create a full featured PowerPC emulator/translator.

Possibly PearPC would do the trick??? (I can't recall if it will run OS9 or not, but it can emulate PPC, albeit quite slowly) Give it a try

SheepShaver will run on an Intel Mac. I'm currently emulating OS 8.6.

Q: Is there any way to network OSX in VMware?

A: Yes, you can network VMWare to your Windows XP, allowing Internet access.

Method 1 (virtual serial port)

VMWare works with a serial port / PPP connection. I used a demo of Virtual Serial Port Driver XP v5 to create a pair of serial ports. I bound one of them to Incoming Connections, no flow control, 115200. Allow directly connected users to connect without a password, give it a pair of IP addresses under TCP/IP config.

The other serial port I bound to the Virtual Machine. Within OSX select the Null Modem at 115200 as your modem, unselect compression and wait for dial tone. Under PPP Options, select use terminal window. Click Connect. When the terminal window appears, type in CLIENTCLIENT and hit enter (you won't see anything in the window as you type). The XP side should respond with CLIENTSERVER. Click connect. If all goes well you'll be connected via PPP.

Method 2 (dual virtual machines)

Here's something else to try... Basically what you need to do is create a Windows/Linux/BSD VM to run alongside the OSX VM. Then enable "Named Pipe" COM port redirection on both VM's and set up a PPP-Over-Serial link between the two VM's COM ports.

Remark This method doesn't seem to work with deadmoo's image. Seems to work fine (but slow) with a new image(not the one from TPB !).
Remark Correction this method actually works with deadmoo's image. However, if you ever get into a situation where the system preferences network app no longer functions, you may have to start from a clean deadmoo image. The trick is to make sure the builtin-serial device is detected.

Method 3

Install Maxxus' patch to make network work in VMware.

Method 4

If you are using VMWare 5.5.x, just open .vmx (VMWare configuration) file, add/change two lines:

guestOS = "darwin"
ethernet0.virtualDev = e1000

see vmware forum thread [1]

Q: Could Linux or BSD drivers work under OSX86? If not, would it be difficult to tweak them?

Short Answer: no and yes.

Long Answer:

1) Drivers are very different in Darwin/OSX. While Darwin looks like just another BSD variant to normal applications, it has little in common with BSD (or Linux) regarding drivers.

2) Due to (1), it's not possible to use an open source driver and just tweak a bit. Open source drivers are useful, but mostly as guidelines for writing a new driver from scratch. Actually, Darwin contains quite a few drivers that were originally written for Linux, but porting them is a lot of work. Often it's easier to just write a new driver from scratch.

Rarely Asked Questions

Q: I get an error resembling "vram=[0000000000]x[0000000]" before reaching the login screen.

  • Note: Without the "-v", the mouse appears on the frozen spinning Apple logo.

A: try removing whatever kernel modules are in /System/Library/Extensions that correspond to your video card. Like if it's an ATI card, get rid of all the ATI modules. The only video chipset with a functional driver in OS X 86 is for the Intel Media Accelerator 900. Everything else is used through framebuffer.

  • note: i have an intel chips, supose to be suported for accel

Working answer:Reboot from windows using the boot.ini bootloader, be sure you formated "AF" before installing osx.

  • thanks, it worked!

Q: I want Wi-Fi, OpenGL, and Quartz Extreme with my ATI video card and a nice widescreen resolution.

A: Apple didn't intend on OS X Tiger x86 being installed on varying hardware configurations. Because of this, a significant amount of hardware is not supported (doesn't have a fully working driver). There are a few supported WiFi Cards by AirPort2.kext (mostly Broadcom). Here is a forum topic that helped me get my WiFi working. And there are efforts to get NVIDIA and ATIdriver kexts to load.

A: There now the omni callisto driver, with it, you can change resolution (1280x800 too)

Q: How do I edit ""

A: Go to your user folder. Open Library/Preferences . Scroll down to "", right-click on it. Go to "open with". If you have the developer tools, "Property List Editor" will show up and that's the one you should choose. Otherwise select "Other..." and search for "" in the file selector. In your editor search for "PVDebugImageForceCPUMode" and "PVDebugImageUseQuartzCore" and play around with both values (they are 0 / 1) by default and should probably be (1 / 0) on a non-accelerated machine. If you can't find "" in the user folder, run Preview and change some Preferences inside the app to make OSX write that file into your user folder.

  • This section is unclear please provide further instructions on how to change the 0/1 values*

Q: Why does my Xeon cause a kernel panic?

A : The "Xeon" versions of Intel's CPUs aren't the same as their non-Xeon counterparts. There isn't much you can do to get it working.

Remark Why do other Xeons work?

Response They're enough like their non-Xeon brothers to be stand-ins in most cases, but there are several minor differences that make them unsuitable in certain situations. You should consider the Xeon line of CPUs to be "x86, sorta". If it works, that's great. You're lucky. If it doesn't, oh well. It was never really meant to.

  • Somebody needs to edit this answer appropriately to note that it's most likely a chipset issue as Xeons are the same as P4s minus the varying cache sizes.*

Q: My CPU is listed as incompatible. It boots, but it keeps freezing on startup.

A: Well, booting doesn't mean it "works". Maybe that's why your specific processor is incompatible.

Comment: It's possible that the Darwin x86 kernel and bootloader you're using is compiled without SSE2 or SSE3 optimizations. Hence, the VM seems to boot. However, since the many or all of the executables and libraries probably are compiled with SSE2 and SSE3 optimizations, nothing will actually run. In theory, if you patch/replace all SSE, SSE2, SSE3 instructions from all binaries in the deadmoo image, it should boot and work. The success rate of accomplishing this task is unlikely.

Q: When I try to install OSx86, I get the message "Still waiting for root device."

A: OSx86 is not seeing your optical drive. If the drive is IDE, make SURE it is on the IDE port that goes to your southbridge (usually the blue one, but it varies), NOT on any supplementary IDE controllers. If it is SATA, set your bios settings to emulate or compatibility or something like that, NOT native or RAID or AHCI. Note: After changing the sata mode, if you also run windows off of the same/another HD on this controller, you may notice degraded performance and/or faliure to boot windows IF you change the sata settings.

If you mean boot instead of install, just replace the phrase "optical drive" with hard drive, the rest still applies. It is a detection issue with your IDE/SATA controller. Also you have to check that The Hard Disk is on the same ATA cable as the optical drive (in my case a DL DVD recorder).

Spanish Si a pesar de controlar todas las particiones una y otra vez y de checkear el teclado y el mouse usb sigue saliendo este mensaje deben chequear si tienen el disco rigido y la unidad lectora de dvd en el mismo cable ATA (siempre poniendo como master el disco rigido y como slave o secundario la lectora de dvd).

Edit: Try to use a different DVD drive when installing. I kept getting "Still waiting for root device" then I swapped in a different dvd drive and it booted like normal!

Edit: Try deleting the ApplePS2controller.kext - I get rid of that and it boots up for me no problem then!

EDIT: If you have an Ati Xpress200m Chipset, you must use scousi's Ati ATA kext..HERE

Edit: After installing OSX86 and this error appears, try typing rd=disk0s1 at the Darwin bootloader (or whichever disk partition you used when setting up OSX86 - for example rd=disk0s3 if partition 3 on disk 0 (IDE Primary Master) was used) - the kernel is otherwise trying to find a boot partition by UUID - see

In my case its intel ggc101 Mb with ati southbridge and ati 200 vga initially hdd(pata) on primary channel as a master and sony dvdrw on secondary master gave the error msg "still waiting for root drive". i changed hdd to secondary master and dvdrw to primary master and it solved the problem. it finally installed installation took more than eight hours on 2.8 ghz dual core with one gb Ram.but it installed.performance is ok but not is like xp on p3 mechine. (os x 10.4.8 jas)

Q: I read that Java does not work in OSX86 - is this true?

A: This is not true, tiger comes with 1.4.2 and you can download and install 1.5.0

Remark: The 1.4.2_07 JDK/JRE may not be 100% functional. Certain large Java apps will crash. e.g. NetBeans. Also, applications that use SWT do not work, even with a functioning rosetta. e.g. Eclipse, Azureus. You usually get a linkage type error. i.e. The lib's included with the PPC/Carbon MacOSX SWT bundle doesn't seem to work on x86 via rosetta. ZZ

Update: I got eclipse 3.1 up and running. I had to recompile swt 3.1 carbon jni libs using Xcode and the native x86 libs. Then I had to hack up a startup script and relink some jars. Note: I didn't have any luck with eclipse 3.0.2/swt 3.0.2. After it was compiled, the UI would not react to mouse clicks. ZZ

Question: Could you please zip it up and put the working eclipse 3.1 on the web somewhere ? Thank you!

Update: Check this.

Q: What is the FireWire chip version on the Apple Reference Platform?

FireWire works fine with the Intel 82801FR I/O Controller Hub (ICH6-R) on my 915P-based motherboard. This I/O bridge is featured on many newer Intel motherboards, and is probably similar (if not the same as) the chips used in the Dev Kits.

How to Multi-Boot

Q: How do I dual-boot Mac OS X with other OSes without messing with bootloaders?

A: Quick and easy, copy chain0 to the root directory of your bootable Windows drive, then add the following the bottom of your "boot.ini" file:

C:\Chain0="Mac OS X86"

this however renders the Quiet Boot option useless, so if the Darwin loader annoys you as much as it does me then add this to the bottom of your "boot.ini" instead:

C:\Chain0="Mac OS X86" "Quiet Boot"="Yes"

I do not mess about with boot loaders. I run XP and OSX. I boot from pc BIOS F11, which enables boot from any available disk. A lot of PCs are similar. I have dual boot XP and Tiger, on seperate disks. The dd must have the bs=32256 skip=1 or equivalent, to put the boot sector on sector 64, which is where the PC expects it to be. I believe any reasonable MBR will boot as long as disk type is (hex)AF. The byte at offset 1C2 can be changed to AF with a small sector editor, I use Hex Workshop. It is also possible to adjust the boot sector, at offset 17 in the boot sector is byte AF followed by 75 03. overwrite the 75 03 with 90 90 (NOP's) and the code will jump to the load routine. Either should work.

Unanswered Questions

Q: What is AppleACPIDisplay.kext and how can I get it to load correctly?

A: It helps for using less power to your computer, if it doesn't load correctly, you can use


in bootloader, or add it in boot file (you dont need to write it every time after).

Q: After reboot, Mac OS X refuses to start by saying chain0 error, or HFS+ partition error. What do I do?

A: This seems to be an incompatibility on some computers between Mac OS X (10.4.7 JaS) and Windows Vista (final release). Install Mac OS X before Windows Vista


  • After rebooting and getting the "HFS+ partition error" is most likely because the partition not being set as active . A way to fix this is to restart and boot the dvd. At the boot screen press F8 to give yourself boot options.
  • type -s press enter
  • now type fdisk -e /dev/rdisk0 >> 0 would be the disk you installed it too.
  • flag 2 >> 2 would be the partition of the harddrive you installed OSX86 on.
  • update
  • write
  • exit
  • reboot
  • That should fix the problem

Q: After rebooting a Mac OS X install, I get this following message: Error Loading Operating System, how to fix?

Q: What are all the different options I can specify on the BOOT: prompt? The "?" help doesn't seems to work

A: Incomplete list:

  • -f - This forces rebuilding of extensions cache
  • -s - Boots into a single user command line mode
  • -v - Verbose, boots in text mode showing all debug info and errors
  • -x - Boots into safe mode
  • "Graphics Mode"="1024x768x32" - Tells VESA to boot with this resolution, the x32 is bit depth and is only compatible with VESA 3.0 and up
  • "Quiet Boot"="Yes" is the opposite of -v, forcing the graphic boot
  • rd=disk0s1 - Tells Darwin to boot from a certain partition specified in BSD format. Disk 0 specifies first HDD and s1 specifies first partition as 0 is the MBR.
  • cpus=1 - Tells the system how many CPUs or cores to use, useful for Core Duo users.
  • platform=X86PC - Can be used if problems with normal booting, ACPI is another option here
  • -legacy - Boots OS X in 32bit mode rather than 64bit if 64bit is used due to a 64bit processor
  • idehalt=0 - May stop stuttering
  • -vmware ?
Powered by MediaWiki © 2015 OSx86 Project  |   InsanelyMac  |   Forum  |   OSx86 Wiki  |   PHP hosting by CatN  |   Designed by Ed Gain   |   Privacy policy   |   About OSx86   |   Disclaimers