Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Just Joined
  • Content count

  • Joined

  • Last visited

About narcogen

  • Rank
    InsanelyMac Protégé
  1. AVCHD iMovie 09 import crash

    I'm having an identical issue, also on 10.6.1 and iMovie '09 and an AVCHD camera (Canon HG10). SL 10.6.1 (Chameleon2 RC1 Boot) Asus P5K mobo Intel Q6600 From other threads I've read, the problem seems specific to trying to import AVCHD from a removable volume; however, I've been unable to verify this. In fact, I've archived camera footage to a folder on the boot drive, and iMovie still crashes trying to import from it. It doesn't do this when you try and Import a movie, only when you try to import AVC from a camera or camera archive. So for me at least, it doesn't matter what volume the files are on; importing AVC leads to the error no matter what. The error in console is: Error getting a reference to /options com.apple.iMovie exited with exit code: 1 Incidentally I booted into my Leopard partition (10.5.6) and now it does the same thing on the same version of iMovie (8.0.4). So perhaps this isn't just an SL issue.
  2. Mdworker Kernel Panic

    Multiple runs of kext utility, the standard suggestion for fixing kernel panics, didn't seem to help me. I did do two things, and since that, I haven't had any mdworker panics even though I've indexed several volumes more than once. I'm not sure which thing fixed the problem, or if it was both in combination. 1) Since I still had a working Leopard install, I deleted all the Spotlight information on all volumes, reset the exclusion list, and then rebuilt all the indexes in Leopard. (SL is still going to rebuild them but it seems to take less time than rebuilding from scratch in SL). 2) I boot into SL in 64 bit mode (-x64 -v). On reboot, the active mdworker process is a 64 bit process. There's also a 32 bit mdworker process, but it's idle. During indexing when booting in 64 bit mode I have yet to see another mdworker KP.. so far.
  3. Let me see if I can be in some help in clarifying this guide, as I also have a similar machine (P5K, Q6600, 8800 GT, SATA HDs). [ Essentials ] 1. A 10a432.dmg I assume a retail disc would work here as well as a432 was the GM (Golden Master), yes? 2. BIOS : SATA Mode - Enhanced After booting hold down the delete key to enter BIOS setup. Under Main > SATA Configuration set SATA Configuration to "Enhanced". If you already have a working Leopard installation on this motherboard (as I do) you probably have this set already. Under that I also have "Configure SATA as" set to IDE which I think is pretty standard for Hackintoshes, and was a requirement when I was installing Kalyway. You don't mention how you have yours set. 3. An installed Leopard ( I am using iDeneb_v1.6_1058_Lite ) I am assuming the author already had this installed, but is including the Leopard installation procedure here for those who do not. I already had a Kalyway 10.5 system running, so I use that to make preparations. Also, this guide's three partition scheme (detailed below) seems intended to allow for the use of 10.5 for preparation on the first partition, the third is the 10.6 installer, restored from the image of the 10.6 Golden Master (for booting into the Snow Leopard installer) and then the second partition is the actual 10.6 installation target. Presumably other options would be to burn a DVD to boot from, or to mirror to a USB stick. I am using the USB stick method from another guide: http://www.infinitemac.com/f57/guide-retai...for-g31m-t3672/ When I installed Leopard, I made 3 GUID Partitions as the following: Start by booting into your Leopard DVD and firing up Disk Utility. Select the disk you will use, and click on the "Partition" tab. Change the "Volume Scheme" drop down menu to "3 Partitions", and then click "Options...". Select GUID, and click ok. ( My 1st partition is iDeneb1058. My 2nd partition is 10a432. My 3rd partition is 10a432dvd. ) 4. 2 blank GUID Partitions ( 10a432 Partition & 10a432dvd Partition ) The third GUID partition being the Leopard installation. 5. DSDT Patcher GUI 1.0 6. 10a432p5k.zip ( unHideIT.v1.1.dmg + KextUtility.v2.3.2.dmg + AppleIntelPIIXATA2.kext + sk1nhd33t folder + AppleAzaliaAudio.kext ) ( In sk1nhd33t folder ) cameleon-RC1-r431 pc-efi-10.1 Extra folder apple.com.Boot.plist smbios.plist Extensions.mkext Extensions folder ( In Extensions folder ) dsmos.kext NullCPUPowermanagement.kext PlatformUUID.kext Openhaltrestart.kext LegacyAppleHDAHardwareConfigDriver.kext LegacyHDAPlatformDriver.kext SleepEnabler.kext Theme folder [ Installation ] 1. Install cameleon-RC1-r431 on Leopard, and replace the installed boot file in the root of Leopard with the boot file in pc-efi-10.1. ( Show all hidden files by using unHideIT.v1.1. ) ( From now on Leopard manages the boot infomations, so you don`t have to install chameleon-RC1-r431 & pc-efi-10.1(boot file) on 10a432 & 10a432dvd. ) Notes on above: Netkas seems to be indicating that Chameleon 2.0 RC2 should not be used as there are problems with it. There are .pkg installers both for Chameleon 2.0 RC1 and for PC EFI 10.1 (If I actually manage to get this to work I'll package up all the tools I used into a download, as many others have done. Right now my drive is littered with several different guides and tools, so much so that I've forgotten where I got them all, but I think Google can help you here. The application unHide just reveals all of MacOSX's hidden files. This is necessary if you want to place the "boot" file for PC EFI 10.1 onto the disk without using the Terminal or the .pkg installer. The installer is the most comfortable method, the Terminal is the most exact (as you must be completely aware of what file you are placing where, so you can be most confident that you have done it correctly) while unHide is a way of just using Mac OS X's usual graphical interface to drag and drop the file onto the volume. Several guides I read said this was impossible, and the task had to be performed in the Terminal. I assume they just didn't know about the .pkg installer for PC EFI 10.1 or about unHide. 2. Restore 10a432.dmg to 10a432dvd by using Disk Utililty in Leopard ( Destination: 10a432dvd, Image: 10a432.dmg ). Note: Apparently we've now skipped any instructions regarding the installation of Leopard and just assume you've already got one running. The only way to get the Snow Leopard installer running is either by having an existing Leopard install to run it from, or to be able to boot into the installer directly, either from a DVD, a flash drive, or a hard drive with a modified image of the installation disc. It is this last method being used in this guide, and perhaps the best if you have trouble getting DVDs or USB sticks to boot on your machine. So far I have not gotten a completely successful boot on the USB stick but I have not given up, so I have not yet considered using a hard drive partition in this way. As I can get the Chameleon boot manager to load, and the Snow Leopard boot process at least starts, I don't think there is any problem booting a P5K from USB, at least in principle. At any rate, the above instruction takes the disk image file of Snow Leopard's golden master, and copies it to the third partition of the hard drive. The author has named this partition 10a432dvd to indicate that it is Snow Leopard, OS 10 revision 432, with "dvd" appended to indicate that it is the installation media, and not the partition we intend to install to. ( If you look at an Icon of MAC OS X Install DVD and a Window of MAC OS X Install DVD, just close the Window of MAC OS X Install DVD, otherwise you may get an "Install Failed" message ) I am honestly not completely sure what the author is trying to say here. Are you suggesting that having the installation media disk image mounted, with a window showing its contents, while Disk Utility is trying to restore the image to partition 3, that you may get an error? Otherwise, it seems like you've skipped straight from restoring the Snow Leopard image all the way to something that could only happen after you've booted that image, which we haven't done yet. In any case, in my attempts I have not so far seen the "Install Failed" message. I've had installers fail to finish booting, I've had partitions with installation completed kernel panic on boot, and I've had the installer quit silently to the desktop before completion (apparently it takes a minimum of 15-20 minutes, and if it finishes in less than ten minutes, it means it didn't really finish). ( In this step, don`t put other things [boot, kext, dsdt.aml ...] into 10a432dvd, otherwise you may see the KP[Kernel Panic]. ) Many of the other guides put the Chameleon boot manager and the PC EFI 10.1 "boot" file onto the installation media itself (either a USB stick in my case, or onto a DVD image to burn in other cases. However, since this guide is using three partitions, one of which has a Leopard installation on it, he chose to put the boot manager and the PC EFI 10.1 file on that partition. As long as that partition is set in the BIOS as booting first, the machine will load the boot manager from that partition. Chameleon will look for other available partitions and allow you to choose among them. So it is not necessary for Chameleon or PC EFI 10.1 to be on either the partition for the installation media (10a432dvd) or the partition we intend to install Snow Leopard onto (10a432). Additional kexts and the dsdt.aml file I assume are excluded from the installation media just in order to keep things simple. If the author was able to boot his machine without them then I assume this should be possible on other P5K based machines. Author-- what is the version of your BIOS? 3. In the Desktop of Leopard, make the contents of Extra folder as the followings, and then copy the Extra folder to the root of 10a432dvd. Note: While booted into your Leopard installation on Partition 1, create a new folder called "Extra" on the desktop, and place into it each of the below items. All the necessary files are included in the download 10a432p5k.zip linked in the guide. After assembling all the items in the Extra folder, copy it to the root of the partition to which you have restored the Snow Leopard install DVD image (in this case, named 10a432dvd) - Extra folder in the Desktop of Leopard ㅇ apple.com.Boot.plist ( If you want, paste your gfx string in this plist. ) The application EFI studio can help identify your graphics card and generate the strings necessary to put into this file so that your video card can be properly identified. Depending on your card and display, this may be optional, at least for getting the installer to boot. If you skip this step, and during boot you get a completely black screen (not a grey background, but a black screen, with no pointer) then you probably shouldn't skip this step. So far, with my 8800GT, I have not encountered that, whether or not I bother to put in the graphics strings into the boot.plist. Once installation is over I assume this will be necessary. ㅇ smbios.plist ( Remove this plist. My 10a432 is likely to automatically get my system infos of the System Profiler without it. ) Author: Can leaving it in cause Kernel Panics? If not, why remove it? ( Don`t put UUID into apple.com.Boot.plist and PlatformUUID.kext. ) You haven't mentioned anything about UUID before, including what it is, what it does, and where you get it. That is in other guides, but I assume many users may go directly to a guide that specifically mentions their motherboard, and not attempt to wade through a number of different guides, all with different instructions, in order to find out what the UUID is, why it is important, and where to put it. I assume, however, that you're referring to the ID of the boot volume. It is possible to place this identifier within the boot.plist file in order to tell OS X which drive to boot from. PlatformUUID.kext is a kernel extension that performs this task as well. I presume what you mean to say is that you do not need to BOTH put the UUID into boot.plist AND have the PlatformUUID.kext file in /Volumes/10a432dvd/Extensions as this would be redundant. Or do you mean to do neither-- DO NOT put the UUID into boot.plist AND DO NOT use the PlatformUUID.kext file? ㅇ Extensions.mkext ㅇ Extensions folder ㅇ dsdt.aml ( Install DSDT Patcher GUI 1.0 on Leopard, and then put the installed dsdt.aml in the root of Leopard into the Extra folder of the Desktop. ) You've contradicted yourself. Above you said do not put this file in during this step, now you say to put it in. Which is it? ( If you have your compiled/edited DSDT.aml, drop it into the Extra folder of the Desktop. ) I've read a lot of guides, although I haven't actively been building Hackintoshes since Kalyway 10.5.4. I don't yet have a clear idea what DSDT is, or what it does. Some guides seem to indicate this actually involves patching the BIOS. Have you updated the BIOS on your P5K? What revision are you using? Are you just running the DSDT patcher and copying the file? Where exactly are you putting it? "Install DSDT Patcher" seems to indicate you are applying the patch to your first partition, the Leopard boot partition. Is this the case? If so, why are you doing it? Or are you merely running it from your working Leopard partition, and the target volume for DSDT Patcher is the installation media partition, 10a432dvd? Where are you getting the dsdt.aml file from? Are you running the Patcher onto the Leopard volume, and then moving the file it places on the root of that volume into the Extra folder on the desktop of the running Leopard installation? It occurs to me that if a mistake is made here you could cause problems for your Leopard installation, or the working Leopard installation of other users. Better to have DSDT patcher apply the patch to the 10a432dvd partition, rather than target the Leopard installation and then move the file to desktop/extra and then copy that folder to 10a432dvd, no? DSDT Patcher also puts the created dsdt.aml file into the Sessions folder in its working directory, along with a log of warnings/errors. Maybe it is better to copy the file from here, to be sure what version is being used? Once you've run this program a few times you'll have a bunch of these files floating around-- the Sessions folder is a good way of making sure you're using the best, latest, most appropriate version. ㅇ Theme folder ( Remove. ) This is Chameleon's theme folder. Is there a reason to remove it? Does it cause problems? - Extra/Extensions folder in the Desktop of Leopard Again, this means the foler "Extensions" inside the folder "Extra" on the Desktop of your running Leopard installation. ㅇ dsmos.kext ( If you use fakesmc.kext in this step, you may see the KP. But, after seeing the Desktop of 10a432, you can use fakesmc.kext. ) NOTE: Some of the other guides I've read also indicate something similar; that fakesmc.kxt seems to cause kernel panics on Asus P5K machines, and that the older dsmos.kext file should be used instead. These perform the same function, and you should make sure you don't have both in your Extensions folder, as I'm guessing that would cause serious problems. ㅇ NullCPUPowermanagement.kext ㅇ PlatformUUID.kext ㅇ Openhaltrestart.kext ㅇ LegacyAppleHDAHardwareConfigDriver.kext ㅇ LegacyHDAPlatformDriver.kext ㅇ AppleIntelPIIXATA2.kext ( iATKOS 10.5.7 ) Why this version, particularly? Did others cause kernel panics? ( After seeing the Desktop of 10a432, Use SleepEnabler.kext. ) I assume you mean here that while booting the installation media, you should not have SleepEnabler.kext in /Volumes/10a432dvd/Extra/Extensions. However, after successfully running the installer and booting to the Snow Leopard installation on the 10a432 partition, you can add SleepEnabler.kext into /Volumes/10a432/Extra/Extensions. Is this correct? ( Don`t use your kexts for /System/Library/Extensions in this step, otherwise you may see the KP. ) By this I assume you mean that all the above kext files should be in /Volumes/10a432dvd/Extra/Extensions where Chameleon will see them and add them in at boot time, instead of in Apple's standard /System/Library/Extensions folder, because it will cause kernel panics. Correct? 4. After booting to 10a432dvd partition [-v -x32 or -v -f -x32 ], erase 10a432 partition by using Disk Utility and then install 10a432 on 10a432 partition. Two things: It's easy to miss "or" in the above boot strings. Perhaps better to say to boot with [-v -x32] OR [-v -f -x32] so people don't miss the OR and type in the entire string. Two, we've partitioned this drive and presumably formatted the 10a432 partition as HFS+ Journaled, using the Disk Utility in Leopard. You're saying here that once booted into the Snow Leopard installer, we have to re-format the target volume, 10a432, using Snow Leopard's Disk Utility instead of Leopard's disk utility. Is this the part of the step that, if we skip, causes a kernel panic? Or is it the part of not installing printer drivers, rosetta (powerpc emulation), the X windowing system, and the older QuickTime 7 player application, mentioned below? ( I didn`t install printer, rosseta, x11, quicktime7 ) ( This step is very important. If you skip this step, you must almost see the KP. ) ( Thanks to this step, we don`t have to put UUID into apple.com.Boot.plist and PlatformUUID.kext. ) ( Installation Time goes and comes from 20-minute to 17-minute. If you see 15-minute, you will mostly succeed. When you see 8-minute, the installstion screen will be black. Just click it by using your mouse, and it will come back. ^^ ) Click what and what comes back? I have no idea what you're referring to at this point. Do you mean if the system's screen goes black during installation? 5. First of all, go to Leopard, and then copy the Extra folder in the Desktop of Leopard to the root of 10a432 partition by using Terminal. Again some questions: This is the same /Desktop/Extra folder we started making in Step 3 and copied to /Volumes/10a432dvd, our installer volume. Are we coping the SAME Extra folder to the target volume, 10a432? If not, how are the 10a432/Extra and 10a432dvd/Extra folders different? Step 3 does not mention using Terminal to copy the Extra folder. Is it necessary to do in Terminal? If so, why? ( In this step, you can use your kexts for /System/Library/Extensions, by the way if you use them, you will see the KP within a minute. But, don`t worry. After rebooting, you can solve this problem by using Disk Utility & Kext Utility. ) Here I'm confused again. You say that I can put kexts into the standard Extensions folder, but if I do, I'll get a kernel panic in under a minute. A minute isn't a long time. This would seem to indicate to me that it is NOT okay to do. Is the idea to put the kexts in /System/Library/Extensions, boot, and then run Disk Utility (to check permissions) and Kext Utility (to rebuild the extensions.mkext) and get those tasks done before the kernel panic? I suppose if you manage to do it, that's fine, but is there a reason not to just keep the kexts in Extra/Extensions and keep the rest of the disk as "vanilla" as possible? ( I didn`t use the permission commands [chown & chmod]. ) Didn't use them for what? I realize other guides use them for various things, but you haven't mentioned them at all up to now, so it seems strange only to mention them in order to point out you don't use them. I assume there are a lot of shell commands you don't use in this guide. ( You can put AppleAzaliaAudio.kext into /System/Library/Extensions. ) Is there a reason to put this kext into System/Library/Extensions instead of Extra/Extensions? Last login: Wed Aug 26 03:21:49 on console chivalry-whites-mac-pro:~ whitechivalry$ sudo -s Password: bash-3.2# cp -R /Users/whitechivalry/Desktop/Extra /Volumes/10a432 bash-3.2# cp -R /Users/whitechivalry/Desktop/work/10a432me/audio/org/AppleAzaliaAudio.kext /Volumes/10a432/System/Library/Extensions You're copying the Extra folder from the desktop of your running Leopard installation (whitechivalry) onto the root of your target volume, 10a432. However then you've got another line about the audio kext that refers to another work folder you hadn't mentioned. For people unfamiliar with the Terminal and how directory paths in OS X look, this might be confusing. 6. It is time to go to 10a432. [-v -x32 or -v -f -x32] 7. On going to the Desktop, use Disk Utility [ RepairPermissions ] & KextUtility.v2.3.2.dmg. And do what with KextUtility?