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.


  • Content count

  • Joined

  • Last visited

  1. Seems like the trick for a virgin is to first get it booting Lion. By 1. using a USB boot stick, then 2. a working mac (hackintosh or not) to run the script and patch the boot loader etc. Basically just doing the first 6 steps in the guide in post 1. Once its going you are basically self-sustaining on the deflowered target machine, and can run the script there, only going back to the original helper machine if something goes badly wrong. Its been nearly 3 years since this (and ancestors) thread started and Intel brought out their 1366 i7. That original machine has been a real workhorse hasn't it. Still, I was happy to see the z68 i5 1155, and even the mATX GA-Z68MX-UD2H-B3 I'm using somewhat by accident, seem to fairly well supported. There are many detailed hardware lists and builds on tonymacx86 (apparently against the rules to link directly to them here). I didn't go so far as to use [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], but I did look at the build to decide to use Chimera and a starting subset of kexts. Lion seems to be running now using the DD script, so I could rebuild my DSDT, but yeah, I just took the DSDT for my board+BIOS from tonymac and stuffed DSDT.aml into /Extra. I do think these z68 i5 boards are going to become well supported, because in fact Apple uses them in their iMacs. Though, there oughta be a 1366 refresh in 2 - 5 months. Still, at the moment, there's nothing quite like a SATA 3 SSD on those i5 boards, say a Patriot Wildfire or an OCZ Vertex3. And the i5's seem to OC 50% without even trying. There's a gap between expert threads like this one, and script kiddie GUI tools on tonymac. Final challenge now is to try to get triple monitors working. There are some new 2012 Dells that have already appeared in Asia like the U2312HM... IPS 23" with LED and thin bezel. Thinking 3 of those rotated 90 degrees like a triptych for $200 each would be better than a single $1000 27" Apple monitor. (That would give me 3240x1920 instead of 2560x1440. There's also a U2412 16:10 for 50% more money that would add up to 3600 pixels wide). Trying to stick to known cards. Some talk on Netkas that some 5xxx and 6xxx ATI cards are OS X supported OOTB.
  2. Great idea! I removed AppleTyMCEDriver.kext from the USB boot stick, and was able to install Lion. Many thanks. Somehow the OS seemed unhappy about the i5 CPU in the GA-Z68MX-UD2H-B3. I need to find some threads about what kexts this board likes or needs. Now I'm moving the drive back to my original EX58-UD5 to install the bootloader. Going to try minimal kexts plus a DSDT. Maybe I can generate the DSDT on the target system. I'd prefer to install a DSDT while on the helper system (using one from http://www.tonymacx86.com/dsdt.php, of course not generating one on the wrong machine) but I'm not sure I see a script option for that. Maybe I can just copy it into place (er, which directory should, I guess DSDT.aml live in... do I need to tweak its permissions...)
  3. Trying to boot the Lion USB stick (from first posting) on a Gigabyte GA-Z68MX-UD2H-B3. Tried 2 different graphics cards. Then tried jamming a DSDT.aml I got from http://www.tonymacx86.com/dsdt.php into Extra on the USB stick but no change. Anyone got any ideas? I did get one successful install off this USB stick (onto rig in my sig). Other posts show the GA-Z68MX-UD2H-B3 can be made to work.
  4. Yes, hoped I might either get some help, or at least provide a detailed record that might help someone. Stay tuned for my upcoming adventures with the Gigabyte Z68MX-UD2H-B3... I had thought selecting from Chameleon was adequate, but in fact, you have to go all the way back to the origin of the boot, and use BIOS boot priority or use F12. I think in your case you had the same recent Chameleon on both or all active drives. People actively hacking would never run into this problem.
  5. After I reboot off my USB stick, I see quite a long list of kexts being loaded. It ends, and then there are maybe a dozen lines I can't read, and the system reboots itself. I've tried everything I can think of, have done it 6 times, tried adding a DSDT, tried adding an EFI string, nothing helps. Anyone got any ideas I can try? Tried booting off a different drive, tried using a HDD instead of a USB stick, same result. All I can think of is to point a movie camera at the screen to try to figure out where it is before it reboots. There's like 100's of lines of kext loading, then like a dozen more lines, then something about ACPI maybe, then blammo reboot. EDIT: Tried changing from the 9600GT to a 7300GT graphics card. Same fail. EDIT: Tried rebuilding the USB stick using a Mac Mini, fresh download, no EFI, no DSDT. Same fail. EDIT: One thing I've noticed is Apple won't let me download Lion anymore, even with holding down the option key in the App Store. It doesn't like my 10.6.8 Hackintosh and it doesn't like my 10.7.1 on a real Mac Mini. I found an InstallESD.dmg Build number 11A511. I'm really clutching at straws here. I guess the minimal Base System build doesn't have much, I'm guessing its trying to initialize the graphics. But the 7300GT is a very common card that works well with OS X. EDIT: Found this list of graphics cards http://www.apple.com/macosx/specs.html that seems like better than random. Tried an old 8800GT which was on the list. Same fail. Do the above 5 steps work for everyone else? This is an ordinary Gigabyte EX58-UD5 F12 here, and it runs 10.6.8 with no problems. EDIT: Did you know Quicktime Player now lets you record video, and doesn't even insist (as iMovie 11 still does) on you owning an iSight camera? Used it to record the dying moments. EDIT: OK fixed it. I removed all drives from the computer except the drive targeted for install, and the USB stick I was booting off. But for me, again on the stock system this thread was started about, I had to insert a step 4 1/2 "make sure only the target drive and the boot stick are installed" then a step 6 1/2 "now put your original current snow leopard boot drive back in and boot off it". EDIT: Followed along to step 12. Used the defaults. When rebooting into the patched Lion, again fail. System reboots itself. Let me point the webcam at it... EDIT: OK almost all good now. Had to again remove the old Snow Leopard drive. I realize now the problem must have been all along that it had an incompatible version of Chameleon on it. Thanks for your help everyone. EDIT: 10.7.1 from Software Update worked... after pmVersion=0
  6. You do not have to clear CMOS. You just have to remove power to the motherboard. That is sufficient to reset the built-in Ethernet.
  7. Cool. Wondering what minimum set of kexts you settled upon.
  8. My advice is, there's safety in numbers. No offense intended, and correct me if I'm wrong, but I don't see much talk about CruisAR's method lately, or many people using it. I switched from CruisAR to MAJ main method and things seem even smoother. Perhaps someone will advise you, but AFAIK the main MAJ method in post 1 is the mainstream now. MAJ states in the original post "All that's really needed to boot into OS X on this board is a disabler (i.e. Disabler.kext or NullCPUPowerManagement.kext.), a decryptor (i.e. fakesmc.kext or dsmos.kext) and graphics support. If your card is one Apple makes available, then it should work OOTB or with EFI strings. That's it. Everything else are little fixes for hardware reporting, updated device IDs, audio, network, etc. In my case, I also needed the ATY_init.kext for ATI graphics card support, as without it I just got video corruption and couldn't see the desktop." Again, no offense intended, and correct me if I'm wrong, but I think that characterizes the CruiSAR method: a disabler and a decrypter. Most people find no trouble and harm, and in fact benefits, to adding the everything else, and you'll be on a more well trodden path if you go that way.
  9. In the first post, you could edit the phrase "Note that some kexts just do not work in /Extra and must be installed into /System (or S/L/E), instead. These include the current selection of audio and networking kexts…" to add "and the graphics kext ATY_Init (if you need it)". Is my reasoning correct that, since my ATY_Init is still in /Extra, and that despite that I have the 7300GT running with QE, that actually I don't need ATY_Init anyway. But wait, I do see this in my console "ATY_Init: The 393 card already has keys set" so I must be using it. I have GraphicsEnabler set in my boot.plist if that matters. Well, I guess its better to have "it works and I don't know why" than "it don't work and I don't know why". I feel (as everyone does) that I did a completely vanilla install. But I seem to be the only one getting errors like the following... Refusing new kext com.apple.iokit.IOPCIFamily, v2.6: a loaded copy with a different executable UUID is already present. com.apple.iokit.IOPCIFamily, v2.6 com.apple.iokit.IOACPIFamily, v1.3 (these repeat over a dozen times… they do exist in /S/L/E but I don't see them in /Extra) these similar errors occur only once... com.apple.kernel.iokit, v7.9.9: com.apple.kernel.libkern, v7.9.9 com.apple.kernel.mach, v7.9.9 Above I've dumped all I know about SSD. The OCZ forums might be a place to research further. I think I now know enough to get them to work properly on the Mac situation. Its just I'm gun shy now after all the pain of the slowdown. I'd say if you go with a non-power-of-2 SSD like the latest Intels or the latest Vertex2, a 50 or 80 or 100GB unit, it will be okay on the Mac. I would avoid the 60 or 64 GB units, since OS X does not understand TRIM.
  10. MAJ, I'm using script version 4.56. From 10.6.4 hackintosh to new SATA volume. Says "1 of 9 kexts in /Extra failed to make it into cache! See logs for details." Logs say... ATY_Init.kext does not match OSBundleRequired conditions; omitting from mkext. ATY_Init.kext doesn't support architecture 'x86_64'; omitting from mkext. You mentioned you don't use ATY_Init so maybe you never saw this situation. I believe I'm doing a fairly stock install and following the guide in the first post. Now I'm trying Combo Build. The Combo Build options is not explained in this thread (at least, search didn't find it when I downloaded the entire thread). I tried Combo Build and the error went away. ----- 7300GT worked like a charm including QE. I have to say pmVersion=0 in the Chameleon boot. I think I can just add that string to the boot.plist. I get a couple dozen complaints during boot like this... "Refusing new kext com.apple.iokit.IOPCIFamily, v2.6: a loaded copy with a different executable UUID is already present." if anyone has any ideas. This started after the combo update from 10.6.0 to 10.6.4. Also did a Migration Assistant later.
  11. Sandforce controllers (probably the 1200 more than the 1500) are great, but the rest of that sentence needs clarification. The controller needs to know which sectors are available in order to perform garbage collection. The controller does not know about the different file systems that may be on the disk. The OS does need to worry about this. TRIM is how the OS to tells the SSD controller which sectors it can mess with. No TRIM, no garbage collection (unless you reformat), adds up to continually degrading performance. It seems unconscionable that Apple has been selling MacBook Air's with SSDs in them for nearly 2 years without TRIM. I expect that within 24 hours we'll see 10.6.5, but we won't see TRIM (no developer has mentioned it, and surely it requires testing). I would be happy to be proved wrong on the TRIM part. We'll soon know. --- I'm checking the press on Apple's announcement today, but I see no mention of 10.6.5 nor TRIM. Disappointing that the new MacBook Airs (and the new Mac mini, which was an aborted version of the iTV) use 2-generation-old Core 2 CPUs. I guess that's why we hackintosh. The new MacBook Airs (with the old Core 2 CPUs) have SSD on their motherboards if I'm reading it correctly. I don't understand how Apple thinks their SSD (also an option on the old Air) are immune to TRIM. Maybe their plan is, your $1000 or $2000 Air is going to have a dead non-replaceable battery and a 4-generation old CPU in about 2 years, so it won't matter that the SSD is slow, since the whole unit will be ready for the trash at that point anyway. --- OK I talked to a friend who works for Transcend. I haven't seen a real clear exposition of this, but the dirty little secret of ALL flash is that it all requires extra memory for garbage collection. They hide it from you, and some controllers do a better job than others, but its required. Again this correlates with the 80GB Intel SSDs or the 50GB OCZ (and other OEM) sandforce SSDs: they have extra hidden capacity. I believe if we pry open the new MacBook Air, or most SSD, and add up the bits on the chips, we'll also find that extra capacity, that is hidden from us, and used for garbage collection. Not sure about the old MacBook Airs with SSD, what capacity SSD did they have? The big mistake I made was to use a jMicron-controller 64GB Transcend drive. Any SSD with a power-of-2 capacity is asking for trouble, or at least, requires an expert user. This drive gives me no margin for garbage collection. What I should have done was format only 40 or 50GB - the drive does know which parts are unformatted (though I wonder if thats true for GUID!?). Instead, by foolishly formatting it to full capacity, and thinking that Apple would implement TRIM, the drive has been slowing down to the point where its like getting root canal. Even with TRIM, either the drive should ship with extra capacity baked in, or I should format it that way. Still, a question lingers: does the drive see the unformatted capacity when using GUID as opposed to MBR? Needs to be nailed down. Do 50 or 80 GB smart sized SSD actually need TRIM or extra unformatted space? What if I shrink my partition, which GUID allows... will the SSD pick up on it? Well, apparently I can't try... http://www.macworld.com/article/55274/2007...geekfactor.html diskutil resizeVolume disk0s2 limits For device disk0s2 i7b: Current size: 63.8 GB (63761768448 Bytes) Minimum size: 63.8 GB (63761768448 Bytes) Maximum size: 63.8 GB (63761768448 Bytes) OK people there it is. I don't have all the answers but I'm asking the right questions. There are pages upon pages of discussion in the OCZ forums. which is where the real beta testing for consumer-grade SSDs began. It was the highest up OCZ techs that worked with the controller manufacturers and finally figured out that the drives need more cache to make sure they last longer. Yes, I realize few people care about this, but just wanted to write this up for MAJ or anyone considering SSD.
  12. Hi MAJ, I notice you mention SSD above. SSD is a bit involved even without a Macintosh. Most SSD support TRIM now, but Apple does not support TRIM. Apple will probably refresh the MacBook Air line on 20 October 2010 and probably also release 10.6.5. Even though Apple sells the Air with an SSD option, it doesn't appear (and I wish I were wrong) from developer builds that they will ship TRIM. Windows 7 has TRIM and all I can guess is that the perfect master Steve Jobs is holding something back for 10.7, at which point he'll say he invented TRIM as well as the smart phone... I am using an SSD on my GA-EX58-UD5, and I often get unexplainable slowdowns. Nothing in the log or the activity monitor. So now I suspect my SSD. I think further research on SSD is in order. To understand the need for TRIM, and what goes astray in an OS like OS X that fails to support it. For example, consider this interesting question: why do most SSD come in 50 or 60, and not 64GB capacities? A friend tells me the full 64GB it there, but the missing space is used for TRIM. Now, my OS X SSD boot disk is formatted out to a full 64GB so I may be creating problems for myself. Or maybe just using the full capacity is all you can do if OS X fails to offer TRIM. Anyway, some food for thought.
  13. Particularly for newbies, it only makes sense to pick a well worn path. It depends a bit on how much free time and how much free money you have. Personally I end up using the more expensive board or trying a few different graphics cards, but its still a vast savings over a real Mac Pro, and faster and more flexible too.
  14. Has anyone had trouble with hot-swap hard disks? I insert a drive and it doesn't mount. Maybe, few of us use hot-swap. But if you have any tips about hot swap I am interested. Even if you use a different install (I am using CruiSAr method). OK, inserting disk, no message in the log under Console. It does NOT show up under /dev/disk*. I'm sure I've got AHCI turned on. Strange. Its hard to argue with CruiSAr's post above. And the last thing we want to do is annoy the trailblazers in this thread. I think the solution is to have a wiki. I tried setting that up here once but it didn't get much use. Anyway the fact is it takes less than 15 minutes to install with CruiSAr. You really need to 1. download the thread into a word file and search through it and 2. be willing (or get yourself a spare hard disk) to try things before begging for help. The fact that it works for everyone else means you have to figure out if you are doing anything different from the well worn path.
  15. My Windows machines can get to my hackintosh at \\ But they can't mount it at \\i7b. Windows can't see it from its network browser either. They're all in WORKGROUP. Anyone got any ideas?