TITULARES :
Mostrando entradas con la etiqueta fix. Mostrar todas las entradas
Mostrando entradas con la etiqueta fix. Mostrar todas las entradas
iATKOS L3 10.7.3 Update [ Hackintosh Support ]
Publicado por Tony el jueves, 2 de febrero de 2012 | 13:51
What we know about 10.7.3 so far...
- 11.3.0 Darwin kernel
- Improved AMD, Intel, and NVIDIA graphics drivers.
- If you use customized or edited graphics kexts, it will be necessary to make the edits again using the new drivers as a base.
- The update will replace your AppleHDA.kext.
- If you use ALC8xxHDA for onboard audio, you will have to reinstall AppleHDA Rollback using MultiBeast before rebooting.
- If you use toleda's new AppleHDA for onboard audio, you will need to reinstall it before rebooting.
- If you use VoodooHDA, you will not need to make any modifications.
- If you use Sleepenabler.kext, remove before updating.
source
CLICK THE IMAGE TO FIND LINKS
UNIX, APIC and PCI Flags [ Fix ]
Publicado por Tony el lunes, 30 de enero de 2012 | 6:30
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
mce=off = Disable machine check. For compatibility with i386. Might help boot some AMD systems. nomce does the same same as mce=off
mce=bootlog = 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.
mce=nobootlog = Disable boot machine check logging.
mce= 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
apic = Use IO-APIC. Default
noapic = Don't use the IO-APIC.
disableapic = Don't use the local APIC
nolapic = Don't use the local APIC (alias for i386 compatibility)
noapictimer = Don't set up the APIC timer
no_timer_check = Don't check the IO-APIC timer. This can work around problems with incorrect timer initialization on some boards.
apicmaintimer = 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.
noapicmaintimer = Don't do time keeping using the APIC timer. Useful when this option was auto selected, but doesn't work.
apicpmtimer=1 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.
disable_8254_timer / 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
pci=off = Don't use PCI
pci=conf1 = Use conf1 access.
pci=conf2 = Use conf2 access.
pci=rom = Assign ROMs.
pci=assign-busses = Assign busses
pci=noacpi = Don't use ACPI to set up PCI interrupt routing.
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
mce=off = Disable machine check. For compatibility with i386. Might help boot some AMD systems. nomce does the same same as mce=off
mce=bootlog = 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.
mce=nobootlog = Disable boot machine check logging.
mce= 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
apic = Use IO-APIC. Default
noapic = Don't use the IO-APIC.
disableapic = Don't use the local APIC
nolapic = Don't use the local APIC (alias for i386 compatibility)
noapictimer = Don't set up the APIC timer
no_timer_check = Don't check the IO-APIC timer. This can work around problems with incorrect timer initialization on some boards.
apicmaintimer = 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.
noapicmaintimer = Don't do time keeping using the APIC timer. Useful when this option was auto selected, but doesn't work.
apicpmtimer=1 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.
disable_8254_timer / 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
pci=off = Don't use PCI
pci=conf1 = Use conf1 access.
pci=conf2 = Use conf2 access.
pci=rom = Assign ROMs.
pci=assign-busses = Assign busses
pci=noacpi = 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).
fsb=<mhz> = 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:
-g = 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.
-vmware = Force vmware support, with hacked kernels. Needs testing.
-force64 = Force 64bit mode for AMD 64 bit cpu's. Needs testing.
cpu=x = Number of physical cpu's installed NOT CORES. Also needs testing
fsb=<mhz> = 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:
-g = 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.
-vmware = Force vmware support, with hacked kernels. Needs testing.
-force64 = Force 64bit mode for AMD 64 bit cpu's. Needs testing.
cpu=x = Number of physical cpu's installed NOT CORES. Also needs testing
Darwin flags for com.apple.Boot.plist 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.
Timeout=3 = Any number 1-100. Number of seconds to pause at the boot prompt.
debug=0x144 When added as a boot flag to your com.apple.Boot.plist 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:
-l = 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.
cpus= Tells the kernel how many cores there are in place. Ex: cpus=1 OR cpus=2
idlehalt= 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.
idlehalt=0
idlehalt=1
cpuidle= 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.
cpuidle=0
cpuidle=1
-legacy = causes the system to load in 32 bit mode while running on 64 bit version of OS X
debug=0x100 = 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.
maxmem=xxxx = 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
"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.
Timeout=3 = Any number 1-100. Number of seconds to pause at the boot prompt.
debug=0x144 When added as a boot flag to your com.apple.Boot.plist 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:
-l = 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.
cpus= Tells the kernel how many cores there are in place. Ex: cpus=1 OR cpus=2
idlehalt= 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.
idlehalt=0
idlehalt=1
cpuidle= 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.
cpuidle=0
cpuidle=1
-legacy = causes the system to load in 32 bit mode while running on 64 bit version of OS X
debug=0x100 = 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.
maxmem=xxxx = 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.
-x = Safe mode. Basically boots your system with the bare minimum kexts.
-s = Single user mode. Command line only mode. Allows you to run commands as root to fix system.
-f = 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
rd= 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
Platform= 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)
?memory = this info screen display information about the memory on the machine
?video = this info screen display information about the video card supported graphic modes
ACPI Flags
acpi=off = Don't enable ACPI
acpi=ht = Use ACPI boot table parsing, but don't enable ACPI interpreter
acpi=force = Force ACPI on (currently not needed)
acpi=strict = Disable out of spec ACPI workarounds.
acpi_sci= {edge,level,high,low} Set up ACPI SCI interrupt. EX: acpi_sci=edge
acpi=noirq = Don't route interrupts
-x = Safe mode. Basically boots your system with the bare minimum kexts.
-s = Single user mode. Command line only mode. Allows you to run commands as root to fix system.
-f = 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
rd= 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
Platform= 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)
?memory = this info screen display information about the memory on the machine
?video = this info screen display information about the video card supported graphic modes
ACPI Flags
acpi=off = Don't enable ACPI
acpi=ht = Use ACPI boot table parsing, but don't enable ACPI interpreter
acpi=force = Force ACPI on (currently not needed)
acpi=strict = Disable out of spec ACPI workarounds.
acpi_sci= {edge,level,high,low} Set up ACPI SCI interrupt. EX: acpi_sci=edge
acpi=noirq = Don't route interrupts
CAN'T FIND MACH_KERNEL [ Fix ]
Publicado por Tony el lunes, 23 de enero de 2012 | 7:27

The true is this happen for a lot of things, but this guide will help a lot of users.
1. Boot from the rBoot CD
2. While hovering over the OSX partition, type in mach_kernel rd=disk0s2
3. OSX started up fine, and then to avoid the need of keeping the rBoot disc in 24/7 to get into OSX, simply reinstall Chameleon.
:)
PCI CONFIGURATION BEGIN [ Fix ]

You only need to add:
npci=0x2000 to Kernel Flags in /Extra/org.chameleon.Boot.plist
:)
Setup your Trackpad with iATKOS [L1, L2 Compatible]
Publicado por Tony el martes, 17 de enero de 2012 | 5:28

For the Trackpad - I suggest you try the Kext from the following link:
http://www.osx86.net/downloads.php?do=file&id=1448
http://www.osx86.net/downloads.php?do=file&id=1448
Its from the GM of Lion, but for us - it actually worked, where as the 10.7.2 kext did not. Don't bother with the prefspane install if you simply just want the trackpad working.
Replace the two kexts with the one from the zip, then use kext utility to repair permissions (inlcuded in L2. Use finder to goto Utilities/Tools.
Replace the two kexts with the one from the zip, then use kext utility to repair permissions (inlcuded in L2. Use finder to goto Utilities/Tools.
Thanks to mrotacon
Audio Drivers for Onboard Realtek ALC 889 and ALC 892 [ L1, L2 Compatible]
Publicado por Tony el jueves, 12 de enero de 2012 | 6:47

Toleda has released two new patched AppleHDA audio drivers designed to optimize any motherboard with the Realtek ALC 889 or Realtek ALC 892 audio codecs. This is the best and most complete support that we've ever seen. The new one-kext solution supports most Mac OS X Lion analog and digital audio capabilities. It is designed to be an alternate or replacement for the combination of both AppleHDA Rollback and ALC8xxHDA. Proper DSDT edits are still required.
One unique feature of the driver is the ability to alternate between 2 different layout-ids, enabling either most onboard devices, or HDMI audio with slightly limited onboard devices. For example, in order to get HD 3000 HDMI audio, you will need to change your layout id in your DSDT's HDEF section to 389. The default 889, used in the DSDT Database, will enable the optimal onboard analog and digital options.
How to solve Still Waiting For Root Device Error
Publicado por Tony el martes, 10 de enero de 2012 | 5:31

Still waiting for root device error occured because the appropriate Sata/Pata driver isn’t being loaded. This error usually appears before OSX86 DVD can boot and in some cases it occurs after installation. Actually this error means that the OS is set to boot from a drive and partition that does not exist or your bootloader is not able to discover the partition.
Step 1 Jumper Settings : If your system contains IDE hard disk or DVD RW then you need to play with your jumper settings. If the following settings are not working for you try vice versa. if you have Sata Hard Disk and DVD RW skip to step 2.
Your rom/writer must be set as Primary Master.
Your hard-disk must be set as Primary Slave .
Step 2 Tweaking the BIOS : If you satisfies step 1 then time is to play with BIOS settings. Open your BIOS settings by pressing DEL or F2 key continuosly as you starts your PC. Once the BIOS screen appears try to find and change following options if they are available.
ATA/IDE Mode : Native
Configure SATA as : AHCI
S.M.A.R.T. : Enabled
Step 3 The Guide:
If you know the number of your Hard Drive then at the Darwin prompt (after boot press F8) write: rd=DiskX where X is the number of your OSX hard drive.
For instance if your hard drive is 0 (zero is the first hard drive) then write:
rd=disk0
if you do not know your hard drive then there is a try and error method of trying all the disk possibilities on your computer starting with: rd=disk0 then rd=disk1 then rd=disk2 then rd=disk3 etc. another good option is to disconnect other HD and leave the OSX HD as first and write disk0.
How to set the RD for every boot :
once you succeed and don’t want to write the rd parameter every boot, then write it in your boot plist file.this is a file that configure the system boot parameters. The file can be found at:/Library/Preferences/SystemConfiguration
once you succeed and don’t want to write the rd parameter every boot, then write it in your boot plist file.this is a file that configure the system boot parameters. The file can be found at:/Library/Preferences/SystemConfiguration
The file name is: com.apple.Boot.plist and you edit it as root and change the Kernel Flags value and add to it the rd parameter like this:
- Open terminal
- Write: sudo -s and press enter
- Enter your password when asked and press enter
- Write: vi /Library/Preferences/SystemConfiguration/com.apple.Boot.plist and press enter
- In the vi editor use the arrow keys on the keyboard and navigate the cursor to the tag: after the <key>Kernel Flags< /key > line.
- The string tag might be empty or not, if it is not empty then add space and then write: rd=diskX where X is your hard drive number.
- Press keyboard button Esc (in order to exit insert mode)
- Write: :wq and press enter (notice the : sign)
- Then reboot and thats it
source
iATKOS L2 Lion 10.7.2: Fix for most common issues ;)
Publicado por Tony el martes, 27 de diciembre de 2011 | 18:28
Simple Troubleshooting guide:
At times after installation, your system may not work properly as in - it may restart, not boot at all or hang at a certain point. This is quite normal and there are many ways for it to be fixed. It varies from one case to another case. However this basic troubleshooting guide would help you to fix most of the common problems.
- If you're facing hangs, freezes or kernel panics (which is present as a shutdown symbol on the screen just after boot) type in "-v" (without quotes) in the boot command of the bootloader. This would give you verbose output which is useful for the solution.
- "Waiting for root device" - It means that OS X doesn't see your hard disk or boot device. You can face with this during dvd boot or after system install during hdd boot.
Change your SATA mode from IDE/RAID to ACHI by your BIOS setup and also you need to check other BIOS settings that might be the usual problem, read the "mickey mouse guide" on our forum for BIOS settings. This usually does fixes the problem. If not, then you can try to install using a USB media. You need to restore the L2 image to USB media and install chameleon to it. You can do it on both OS X and Windows systems, search our forum or google for instructions. If still no light, then you may have an incompatible hardware for this OS.
- White or black screen during HDD boot - This means that OS X doesn't see your monitor properly or your graphics card isn't working correctly. Firstly boot with "-x -v" to reach up to GUI, then you can search the internet for the solution for your graphics hardware. Secondly reinstall the OS again, but this time make sure you don't select any graphic drivers. If you can login to GUI, you know what to do so.
- Keep in mind that sometimes certain kext patches may not work for your system even though they are the same chipset but a slight variation may cause it not to work on your PC. The result may be a kernel panic again, reinstall back but this time don't select any funny patches/drivers. This would resolve your problem.
By Ufuk Durgun
Surround 5.1 audio [ Fix #1 ]
Publicado por Tony el lunes, 26 de diciembre de 2011 | 5:08

You should definitely read through it, but here’s the gist for movies that contain AC3 audio files:
Install a copy of the free Perian QuickTime plug-in on your Mac. String an optical cable between your Mac and a compatible receiver. Launch Audio Midi Setup (found in the Utilities folder) and in the audio output area select Digital Out from the Source pop-up menu and 48000.0Hz and 2ch–16-bit in the Format area.
Launch the Terminal app and enter
defaults write com.cod3r.a52codec attemptPassthrough 1
Press Return.
If iTunes is running, quit and relaunch it.
Locate the movie you want to view, and play it with iTunes’ Volume slider set to its highest level. Also be sure that the equalizer is off. Place your cursor over the movie so that the on-screen controls appear, click on the small bubble icon, and choose the surround sound track. With a little luck, iTunes should now play the movie with surround-sound audio.
source:
source:
iATKOS L2: GT 240 and OS X 10.7.2 [ SOLUTION ]
Publicado por Tony el lunes, 19 de diciembre de 2011 | 5:41

iATKOS L2 has no native support for the GT 240, but here we share with you an easy solution:
For common booting issue, try:
1. FIRST:
-v arch=i386 npci=0x2000 PCIRoot=Yes DSDT=No
2. THEN:
Download from TonyMacx86 the amazing tool called MultiBeast 4.2
3. FINALLY:
If you could, donate a cup of coffe to UPHUCK and/or TonyMac
Enjoy ;)
MacMan released Chimera 1.7.0 [iATKOS L2 Compatible]
Publicado por Tony el jueves, 15 de diciembre de 2011 | 6:24
iATKOS LION AND "Kernel Cache" [ SOLUTION ]
Publicado por Tony el viernes, 9 de diciembre de 2011 | 4:42
Add the following code to your org.chameleon.boot.plist file to use:
<key>UseKernelCache</key>
<string>Yes</string>
You can also use MultiBeast 4.x to do this easy!
By TonyMac :)
Configure the BIOS before install Hackintosh :)
Publicado por Tony el miércoles, 7 de diciembre de 2011 | 13:46
- Disable Quick Boot
. You may have to look around for this, but we've often found this in a section titled Advanced BIOS Settings. Just look for a Quick Boot or Fast Boot option and ensure it is set to disabled.
- Configure SATA as AHCI
. By default, your motherboard will configure SATA as IDE and you'll need to change this to AHCI. In some cases you'll be asked if you want to do this when you boot up for the first time. If so, choose yes. If not, go into your BIOS and look for this setting as you'll need to make the change for everything to work smoothly.
- Change the Boot Device Order
. Your BIOS will default to a specific boot order, which means it'll look for a startup volume (where the operating system lives) in various places until it finds one. The boot order is the order in which it checks each location. In general, you want to set your optical drive to first boot device so you can easily boot to a disc by simply putting it in the drive and turning on your machine. The second item in the order should be the hard drive or SSD where you're going to install OS X. The order beyond that isn't terribly important and entirely up to you.
- Adjust the Hard Disk Boot Priority
. Some BIOS settings pages will also have a setting called Hard Disk Boot Priority, which is used to identify which hard drive to try and boot from first if there are multiple drives in the machine. If you install more than one drive in your hackintosh, be sure to set the Hard Disk Boot Priority to the drive where OS X will be installed.
iATKOS L2: Easy fix for bluetooth Keyboard and Mouse
Publicado por Tony el martes, 6 de diciembre de 2011 | 13:15
2- Power off keyboard & mouse
3- Power on computer
4- Allow computer to come up and say there is no keyboard & mouse connected.
5- Power ON the keyboard at the same time.
6- Above step will put it into pairing mode. re-pair it when prompted, and yes hit the enter key.
7- Then do the same for the mouse.

Enjoy :)
iATKOS Lion: DSDT Auto-Patcher
Download: DSDT_Auto-Patcher.tar.bz2
It runs on Mac OS (iATKOS Lion), Windows and Linux.

by El Coniglio
Suscribirse a:
Entradas (Atom)
FOTOS


