Jump to content


  • Content count

  • Joined

  • Last visited

About septicdeath

  • Rank
    InsanelyMac Protégé
  1. Z68X-UD3H-B3 Sleep NOT working

    Anyone ever get this working? tried with bios f8 and f9 dsdt's from tonymac library. As well as Kakewalk; alll tries with NO added kext's (besides what [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] installs with a user dsdt). Machine sleeps, and powers down. Hitting keyboard or power button wakes machine, spins fans up to full speed, starts drive access, and then locks up before video is displayed. The usb bus stays powered down and non responsive, and machine requires a hard power off and a reset. CMOS overflow happens and bios is wiped. ga-z68x-ud3h-3b f8/f9 bios, ik 2500k (no over clocking), bios set with minimal necessary edits, gtx 280, 10.7.1 Lion Thanks for any help. I have even tried with the sleepenabler kext that was needed with my ex58-ud5 and it makes no difference at all. If you got it working, let me know, I'll try what you have tried. Oh ya, the motherboard has a rev 1.0 and a rev 1.3, my mb is rev 1.0 -SD
  2. Kakewalk 4: Makes installing Lion a breeze

    What selection would you suggest be taken for the z68a-d3h-b3, I actually missed when ordering the z68x-ud3h-b3, which is too funny. I have been using kakewalk on my x58-ud5 since the first release, just always enjoyed the success that its given me. I've tried to compare the z68 chipset against each other, and they seem to be pretty simular, in all actuality it seems that the amount of rear port usb ports and the addition or deletion of a onboard 1394a seem to be about it, they all use the same z68 sata controller, same usb3 controller, etc. I suppose I could just start guessing, but thought I might ask since someone might have already done the work. I actually installed the ssd while externally mounted to my x58-ud5 and transfered it to my new z68a-d2h-b3 and it booted just fine, ethernet and sound didn't work, and it wouldnt wake from Sleep properly. so I grabbed [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] and installed the sound and ethernet that way and it all works, except when resuming from sleep when pressing the keyboard/mouse, the keystoke registers cause it awakens, but you have to disconnect and reconnect the usb keyboard/mouse to get it to work once it wake. all powered usb external hard drives also warn that they were disconnected improperly, so I know this isnt the correct solution, before playing around, I thought I would come ask which kakewalk board to choose, since its always all worked out of the box.
  3. I've been running a hack with the x58 series gigabyte for quite some time. Im in the process of building a new rig. I have access to a GA-Z68A-D3H-B3 motherboard, which I am aware that with mutibeast as well as kakewalk there should be no issues. My question is about the sata 3gb and sata 6gb ports, back with the x58, only one set of sata ports could be used (I believe it was the white ports [the ones with no onboard raid functions]). Has this changed with the z68 series chipsets? I cant find any glaring info (I admit my search skills suck). The 68 series seem to have a very varied amount of ports, but just in the number, they all seem to have the same 6gb ports and just more or less of the 3gb ports. Can someone confirm that all the sata ports now work (even if with a modded ddst) or is it the same layout where only specific sata ports can be used. I only intend to boot osx on this system but would like to use all 6 internal sata ports on the GA-Z68A-D3H-B3 motherboard? Thanks in advance. I will continue to search, like I said, I can read all kinds of posts about success with the MB, just no one is talking about using all the sata ports, I have quite a few older 1tb drives that I would like to use internally on the onboard sata ports. -SD
  4. I figured I would visit back and see if anyone else has experienced the same thing. I have a EX58-ud5, with a default clocked i7 920 in it. I have run kakewalk (as well as just about every flavor of install on this gigabyte board). I even posted a couple of months ago as I flirted with my issue. Keep in mind, that I had the system just as the first release of kakewalk came out, and it ran from 10.6.0 to 10.6.3 without a crash at all, no matter what I pushed it just chugged along. The system has OZ 12800 memory in it (12 gigs) along with a 240 gig SSD and a few other sata drives. As soon as I updated to 10.6.4, the system became unstable and I played around with it, rebuilding it via kakewalk, [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], digital dreamers scripts) and after about 2 weeks and tweaking everything and all, I got it to stay stable for a couple of days, but If I ran a couple of virtual machines and say a resource hog like photoshop, 100% of the time it would crash. Fast forward 6 months and I finally lost some work due to a kernel panic, so I got frustrated and thought, why dont I pull 6 gigs of memory. That was a month ago, with uptime over 720 hours now. I've tried pulling dimms and rotating them through trying to find a bad dimm, none are bad, windows 7 on the box doesn't crash and memtest tests clean, its just running osx and the 6 dimms, and it crashes, take 3 out and it works. If I had larger dimms, I would try to see if its actually the # of dimms or the amount of memory. Although up intel 10.6.4 I ran 12 with no issues, I wonder if its a faulty dimm slot? as its not the memory. Im running just fine on 6gb, but I cant fire up two virtual machines and use osx at the same time anymore, just thought I would ask if anyone else experienced this? Thanks in advance.
  5. DD did a better job of describing it for you, obviously he has more experience explaning how:to's. Just so you know, the pmVersion= is specific for the update you are at, ie: pmVersion=0 disables it. pmVersion=20 was for 10.6.4 pmVersion=19 was for 10.6.3 21 happens to be for both 10.6.5 and 10.6.6 however.. you can use DD's script to edit your boot plist, or a text editor, or ever easier, go and download the property list editor from apple, I know the text editor is faster, but I use the gui from apples dev site. -SD
  6. You'll need to change the pmVersion=X in boot plist to pmVersion=21; also from the hackintosh script folder, you need to replace the sneepenabler.kext in the "Kexts_10.6/Misc_Patches" with the 10.6.5/10.6.6 version, then rerun the script and re-do the kext install/cache steps. Check the first page for the link to the new SleepEnabler.kext, pretty simply actually.
  7. I spent the last 2 days trying to iron out this guid 00000000 message, lots of people guessing, lots of people thinking its DSDT entries (but no one hearing that the fw was working, hot plug-able, EVERY feature working) so it wasn't the same as the power issue, or any of those, I noticed that my mac pro has a ti2213 chipset in it, the same as this card. but I noticed that we also have a namebrand SIIG fw800 card in my office, It also has a ti2213 chipset, so I swapped them, the SIIG card has a GUID 00000008b000002 or something like that, and it loads just like the other card, except it says a valid guid and reports it to console, and then stops talking about it, where as the other card worked 100% but reported every 5 secs about the invalid 000000000000000 guid to console. So I guess the no-name cheap card just enough different that it complains, but the $50.00 SIIG works great, maybe its something that has to be done to each card as they come off the line, and to cut money, the cheap company (it was in a orange box, called "Best Connectivity") just doesn't do it because its cheap? i dont know, anyways, problem solved.
  8. Why are you using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]? You should be able to get your system running using the script that this topic is associated with? I finally have up trying to use this DDST and that DDST, and from a skelton system created a USB boot install (step 15 in the script) and then re-installed using said installer. Ran through the steps like the first page talks about, and ended up with a stable 10.6.6 system (something 10 or 11 attempts upgrading a working 10.6.4 continued to fail). I would suggest that you try that. The audio option is linked to the DDST and using the script will take care of that, as will the monitor sleep/system sleep (with sleepenabler.kext). The only thing you might need to tweak with in the video card, but you should be able to get your system up, and then polish the video card into the setup, but you can even use the script to edit your plists (boot plist), add efi string, choose nvidia, and you'll find your card listed right in it, it will generate the efi injection all by the script. Dont see a single reason to be messing with [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] (Im sure it has its place, but with what you have for hardware, your just adding to the mess from using different procedures mixed together). Thats my advice at least, and Im no expert, but everything works on mine, and except for the issue of 10.6.4 to 10.6.6 (probally something I did anyway), my system's been up for over 2 years now with no random kernel panics or random crashes at all. Its as reliable as the iMac it replaced....btw, my magic mouse worked without adding any kexts. right out of the box (as soon as 10.6.x update that enabled it, using dlink dbt-120 BT dongle). give it a try at least I suggest. my extra kexts: fakesmc HDAEnabler IONetowrkingFamily LegacyHDA NullCPUPowerManagement SleepEnabler DDST created from scripts option #7. Everything works.... Chameleon 2.0 RC5 - Mozo bootloader -SD
  9. Your having the same issues that the 3 other of us have had with the USB/Gigabyte system. For whatever reason, the boot-loader that is created on step 15 on the USB drive doesn't work with the setups we have. What you need to do, is a few simple steps. Use the script option #2 to choose r115 release of chameleon, allow script to erase and recreate /Extra, then take files from original /Extra and merge them into the new /Extra overwriting any files that are the same. steps: #1. boot back into your working OSX, or startup environment, make sure your install drive made with step 15 isnt plugged in until your old/startup osx has booted. Once it is booted, access the hackintosh installer script, re-run it. Choose the drive made in step 15, copy the /Extra from your system mad with step 15, then with the script use step 2 and re-install a different boot-loader, cham2 r115 works great, and when it asks if you want to overwrite the existing /Extra choose YES (you want to overwrite /Extra.). Once the new boot-loader is installed to your step #15 disk, then "combine" the contents of the saved Extra with the new one step 2 created. YOU have to take the original step 15 /Extra and file by file "replace" and add to the new /Extra (I say it this way, because if you just drag and drop /Extra, unlike windows which will combine them just overwriting existing files, OSX will find the conflict, erase the ENTIRE /Extra and copy the old one, you need to merge the two with priority going to the original step #15 Extra, I always just drop to terminal and do a mv ~/Desktop/Extra /Volumes/OS X Install DVD/ and this way it will merge rather than clobber, o'well, I might have tried to make it too simple and made a mess out of it, but if you have questions, just read back on pages 150-155 or so, 2 other users plus myself will describe the issue (although ours is with a Memory stick) but a USB HDD is the same thing. SD
  10. I re-ran the DSDT dump (saving my old DSDT), ran a diff against them and they are different, so obviously it makes sense to re-run it as you add or subtract software? yes? Anyways, I did some searching for the GUID 00000000 definition on the gigabyte dsdt thread, but my dsdt contains nothing like they have you looking for, not sure if thats the issue, (that its not mentioned) and thus why it gets the 000000000 guid, here is it getting recognized in dmesg if anyone can help with stopping this, it adds to my console ever 5 seconds, and makes it a huge file.. <from my dmesg> IOBlockStorageDriver/INTEL SSDSA2M080G2GC Media/IOGUIDPartitionScheme/SSD-osX@2 BSD root: disk0s2, major 14, minor 3 FireWire (OHCI) TI ID 823f PCI now active, GUID 0000000000000000; max speed s800. RealtekRTL81xxx.kext: NIC identified as RTL8168D/8111D (mcfg=18)RealtekRTL81xxx.kext: NIC identified as RTL8168D/8111D (mcfg=18) when I pull the add-on Firewire board and turn on the motherboards fw 400, the OHCI line above reads -> FireWire (OHCI) TI ID 8024 PCI now active, GUID 007bbc070000241d; max speed s400 Im sure I need to add a GUID to it somehow, thanks in advance. SD
  11. I've been following the post's reply's for the last couple of weeks, and even started reading from where I left off back when I installed 10.6. So I apologize if its been asked and my search choice/combo of words isn't flagging it. But here is my question, as I start to add my pulled hardware back into the machine to test each piece, should I be re-running the scripts DDST routines? I would assume that a card being added, or memory being added I should be re-running it? I also noticed during a verbose boot (and remembered that It was doing it before but I gave up on worrying about it because it didn't affect anything), but with the pci/e firewire card I get LOTS of these in my log files 2/1/11 1:09:33 PM kernel FireWire GUID 0000000000000000 is invalid! Also, one guy back was asking how I put this card into my machine because on his pcie/1 slot it hit the cooler die, I just realized that even though its a pcie/1 lane card, I have it in the pcie/4 lane slot. Hope that helps.
  12. Probally should have done less at one time, might make it easier to identify the issue(s), but I assume putting stuff back in one at a time will make more sense, as long as stability is reached at each step. Anyways, I finally installed from a DDScript created USB source. I also removed 6GB of memory. (BIOS post only said I had 8GB of memory, but once in OSX it showed I had 12gb like it should, not sure if that right there was the issue or not, will only be able to tell after putting it back in) I also removed the PCIex1 FW800x2 FW400x1 card from the system. Connected fw devices through onboard fw at the present time. I also removed all JMicron kexts from the system as I dont use those ports at all. Added the sleepenabler.kext for 10.6.6 with pmversion=21. (Even though I DONT put my system to sleep, just didnt like that putting it to sleep it never woke up, which it does now.) Anyways. been stable for 4-5 hours of no use, of course, the real test is leaving the office, I've yet to return to a 10.6.6 system the next morning not KP'd, but using DD's script via usb install, I had no issues at 10.6.4 over the weekend, put thats nothing new, my Kakewalk 2.2 install of 10.6.4 has been stable and up since 10.6.4 combo, so we shall see. oh ya, running the RC5 mozo bootloader Thanks for the pointers and suggestions.
  13. Thanks guys, I would have never thought to try that, r115 allowed it to boot, where I was greeted with a cannot continue memory error. So I am re-making the stick and following what you said exact, copy the extra, update with r115, allow to recreate extra, and then erasing extra and restoring the original from step 15's creation. Between then and now, I have been using my stable 10.6.4 (kakewalk) install to try running the script and install to another harddrive in the system. No matter what I try or who I use (tonymac's [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] method, DD's script with chameleon as well as pci-efi 10.5/6, Kakewalk 3.1) they all do the same thing, although most of them actually KP randomly and at least once a hour, I had one attempt at DD that lasted all day, but froze/kp'd at night just like my original 10.6.4 that I upgraded to 10.6.5 10.6.6 via combo updates. I now leave my 10.6.4 on my ssd as a fall back that works no matter what and stays up and doesn't kp at all (In all honesty, I can make it KP if I run parrallels and try to run win7 and xp or 2 virts, or pound the virt) but with no parallels 6 running its rock solid with everything working. I've taken the Firewire card out, I was also running 12 megs of OCZ pc3 12800 memory (that post always said was 1066 (even though its faster memory) and said I had 8 gigs of memory), until osx booted and told me I had the correct 12gigs, so this time I am removing half of the memory. other than that, nothing except the GT8800 video card is in the machine and Im using only light blue ports (so Im going to remove ALL jmicron.kexts) and try that. I've had my firewire drives turned off as well as on and connected dasiy chain to the onboard firewire (rather than the fw800 pcie/1 card I have used forever with my 10.6.4 install). I ran (optimize defaults load) on bios and changed the minimum (native ide/etc/etc) and I've loaded a minimal amount of apps to still be able to do my job (adium, office, chrome, firefox) and still cant find anything that is stable. I thought maybe it was iStat, so I uninstalled that. we shall see I have one question, why is it that people are using the sleepenabler kext? Sleep has always worked for me and I thought we all had the same Motherboard, so Im wondering why some people do and others dont? we'll see... at least I know I can fall back to a very stable 10.6.4 but that sure would suck not being able to update anymore. What really changed in 10.6.5 anyway? I think I read a kernel change from 4 to 5 or something like that, so I know its a more major one (as compared to 10.6.1, .2, .3, .4 which didn't change the kernel, I dont know, just glad that I can boot back when I get frustrated. we shall see.
  14. Not sure why this worked for me, I had the same issue, booted from USB, then attempted to choose fresh install and just get cannot locate kernel. So I booted, choose my new disk, got error, and then went back to usb which then booted my new drive continuing the install just like a real mac would. go figure, but the kakewalkl stuff hasn't been run on the new install yet, so maybe this has to do with it. Anyways, good luck, all I get is a kernel panic a couple minutes into the boot into the new system. Like my post says, I have been using kw since the very first release, and my machine has been stable the entire time, applying all updates and never touching anything, like a real mac. UNTIL 10.6.5, where updating, my machine now runs most of the day, but locks up every night. I work all day on my machine to Im pretty sure its just that after I leave it can go idle and then KP. my kw 2.2 10.6.4 is on a different drive and I can boot that and continue to work for the last week without any issues, start testing on a new drive with 3.1 and 10.6.3 -> 10.6.5 combo and KP all day long. Just weird that a system that was as stable as a real mac for 16 months now wont allow ANY of the 10.6.5 installs to work on it (digital dreamers script, kakewalk 3.0, 3.1, tonymac).. just weird.... gonna go try the digital dreamer version, because the author monitors that thread and responds to the emails (not that that doesnt happen here, just not as often I guess). Good luck, hope the boot from usb, attempt to boot new install (watch it fail) and then back to usb works for you too, did for me every time, I suspect if I can ever get my 10.6.3 to update with a KP, the drive will work once KW 3.1 is run on it..
  15. I finally have some time to try working on this again. I have been running the DD script from within my working 10.6.4 install onto a fresh disk. But I thought maybe I would try doing it by the USB method. I've tried twice to re-create the USB install, hoever, after creation. when I reboot, my machine hangs at bios with the usb connected. Booting without the usb in (works, then at the cham boot loader, plugging in the usb stick locks the system up again.) weird, same stick I've used for other install methods from USB? any ideas? I'll try booting into 10.6.4 and then plugging it in and see if it locks up the 10.6.4