Archive for January 2012

How to update iATKOS L2 to 10.7.3 [ Easy way ]

The original installation media for Mac OS X Snow Leopard was a 10.6 DVD. The DVD was only updated once to version 10.6.3. In order to provide more frequent updates to users, Apple is now slipstreaming the latest version of Lion directly into the download. Upon fresh installation, no updating is necessary!

If you purchased Lion from the App Store prior to February 1st, 2012, you most likely have 10.7.2. To re-download Lion and update your App to 10.7.3, simply log into the Mac App Store and click Update.
When the download finishes, the app will automatically open. The updated 10.7.3 Install Mac OS X Lion App can be found in the Applications folder.

If you don't see the Update button, follow this simple procedure.

     1. Delete your existing copy of Install Mac OS X from Applications folder.
     2. Hold down the alt/option key on your keyboard, and click the App Store icon.
     3. With alt/option key held, click on Purchased
     4. With alt/option key held, click on OS X Lion
     5. With alt/option key held, click on Install

If either of the above processes don't work for you, try creating a new User account. You can delete it later.

     1. Open System Preferences
     2. Click on Accounts
     3. Click Lock Icon
     4. Click (+) to add a new User
     5. Create a new Admin User
     6. Log out, and log into new User
     7. Proceed with steps above.


Sent by Mandura

UNIX, APIC and PCI Flags [ Fix ]

Unix Flags that might work in OSX. See subcategories for details

This list is mostly AMD specific boot options & for 64bit CPU's. Might also help with Intel CPU's. This list needs extensive testing & feedback but most of these flags do work in OSX. Once more info is gathered They will be categorized into the lists above

Machine check Options Flags

= Disable machine check. For compatibility with i386. Might help boot some AMD systems. nomce does the same same as mce=off

= Enable logging of machine checks left over from booting.
Disabled by default on AMD because some BIOS leave bogus logs. If your BIOS does not do that it's a good idea to enable this log to make sure you log every machine check event that result in a reboot. On Intel systems it is enabled by default.

= Disable boot machine check logging.

tolerancelevel (number from list below)

0: always panic on uncorrected errors, log corrected errors

1: panic or SIGBUS on uncorrected errors, log corrected errors. Default is 1
2: SIGBUS or log uncorrected errors, log corrected errors
3: never panic or SIGBUS, log all errors (for testing only)

APIC Flags

= Use IO-APIC. Default

= Don't use the IO-APIC.

= Don't use the local APIC

= Don't use the local APIC (alias for i386 compatibility)

= Don't set up the APIC timer

= Don't check the IO-APIC timer. This can work around problems with incorrect timer initialization on some boards.

= Run time keeping from the local APIC timer instead of using the PIT/HPET interrupt for this. This is useful when the PIT/HPET interrupts are unreliable.

= Don't do time keeping using the APIC timer. Useful when this option was auto selected, but doesn't work.

Either set to 0 or 1. Same as apicmaintimer=1/0. Do APIC timer calibration using the pmtimer. Implies apicmaintimer. Useful when your PIT timer is totally broken. Sometimes there are timer routing problems on some Nvidia and ATI chipsets. Assuming you're using 64bit then you can try apicmaintimer or apicpmtimer. On 32bit you can try pci=noacpi noapic. Needs testing.

/ enable_8254_timer = Enable interrupt 0 timer routing over the 8254 in addition to over
the IO-APIC. The kernel tries to set a sensible default.

PCI Flags

= Don't use PCI

= Use conf1 access.

= Use conf2 access.

= Assign ROMs.

= Assign busses

= Don't use ACPI to set up PCI interrupt routing. 

Flags for hacked kernels ONLY [ Fix ]

kernel name "mach_kernel" This flag simply tells the system to boot from another kernel available in / (aka root).

= Most of the hacked kernels include the possibility at boot to chosen FSB frequency. These flags DO NOT work with any known vanilla kernel. Do testing with the below values to see what works for you. The default value is 200Mhz. If you want different value, you have a few possibilities.

Ex: kernel name "netkasSS_kernel"

Ex: fsb=800 or use one of these flags below:

= For frequency's multiplied by 100 Mhz
-y = For frequency's multiplied by 133 Mhz
-z = For frequency's multiplied by 166 Mhz

* You can easily add either the -y, -g, or -z options to your boot.plist file or use the fsb=<mhz> flag to give it an exact figure. I have not tested the fsb=<mhz> flag but the -y gave me the correct 800fsb (100mhz x 8) and boosted my performance to where it should be in OSX. This may not change the FSB in about this mac on a hack, it did not for me. You would need to test with a benchmark app to see the gain. Hopefully hardcoded front side bus speeds can be added to SMBIOS files at some point in the future by netkas or Mac.Nub.

= Force vmware support, with hacked kernels. Needs testing.

= Force 64bit mode for AMD 64 bit cpu's. Needs testing.

= Number of physical cpu's installed NOT CORES. Also needs testing


Darwin flags for and more [ Fix ]

Note: Any flag can be added to your boot.plist but these are just the common ones.

"Boot Graphics"=Yes
= Yes or No. Use graphics mode or text mode when starting. Turns off vesa mode graphics at boot.

"Quiet Boot"=Yes
= Yes or No. Use quiet boot mode (no messages or prompt). Same as adding -v option.

= Any number 1-100. Number of seconds to pause at the boot prompt.

When added as a boot flag to your will give you details about a kernel panic you have at any time when running OSX. I believe it is the same as debug=0x100, not sure.

Kernel level flags:

= The flag attempts to enable the L2 cache if not already enabled. Not sure if this works on hacks. If your having an L2 cache issue try this flag.

Tells the kernel how many cores there are in place. Ex: cpus=1 OR cpus=2

Lets you set two values ether 1 or 0 stating true or false, if set to true then at idle time the cpu will halt causing power saving and cooling of CPU, if set to 0 then the cpu will allways run even in idle time.



Lets you set two values ether 1 or 0 stating true or false. This flag is exactly the same as the one above I believe. Please correct me if I'm wrong.



= causes the system to load in 32 bit mode while running on 64 bit version of OS X

= To show information about kernel panics & other useful info from system at startup. If you are getting a auto rebooting from bad kernel or kext being loaded use this flag to see what it is. Will help when posting information on this forum for diagnoses.

= This allows you to specify maximum memory used by the system. Not sure if the rest of the memory is used for apps or not. Many people have to use this if they have 4GB of memory in a 32bit OS. Ex: maxmem=2048

Darwin boot loader level flags [ Fix ]

-v = verbose mode. Basically tells you wants happening during boot up.

= Safe mode. Basically boots your system with the bare minimum kexts.

= Single user mode. Command line only mode. Allows you to run commands as root to fix system.

= Tells the machine to reload all kext and dump the boot configuration cache, (kext cache found in: /System/Library/Extensions.mkext, you can delete it manually and the system will recreate it).

"Graphics Mode"=
Tells the system what resolution width, height, color depth & refresh rate to boot the OS with.

Ex: "Graphics Mode"="1024x768x32" WIDTHxHEIGHTxDEPTH

For VESA 3.0 graphics, you may append a refresh rate after an "@" character

Ex: "Graphics Mode"="640x480x32@60" WIDTHxHEIGHTxDEPTH@REFRESHRATE

This parameter state what is the boot disk to use (instead of using the boot menu appearing before the prompt) you state the drive and partition in here: diskXsY where X stands for the disk number (first disk, usually primary master in IDE or SATA) 0 second disk is 1 etc.) and Y stands for the partition on that disk starting with 1 as the first partition.

Ex: rd=disk0s1 If you have one disk and one partition the parameter will look like this.

You can also use rd=*<IODeviceTree path> for booting from a PCI RAID card for example. Ex: of this would be rd=*/PCI0@0/CHN0@0/@0:1

this parameter sets the platform to use at this boot time.

Examples of this flag are:

platform=ACPI (ACPI support)

platform=X86PC (non ACPI support)
platform=ACPI|86PC (try to support ACPI if fails do not support it)

= this info screen display information about the memory on the machine

= this info screen display information about the video card supported graphic modes

ACPI Flags

= Don't enable ACPI

= Use ACPI boot table parsing, but don't enable ACPI interpreter

= Force ACPI on (currently not needed)

= Disable out of spec ACPI workarounds.

{edge,level,high,low} Set up ACPI SCI interrupt. EX: acpi_sci=edge

= Don't route interrupts 

VIDEO: A little more about Kernel Panics