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

  • Days Won


TheDub last won the day on January 10 2012

TheDub had the most liked content!

About TheDub

  • Rank
    InsanelyMac Protégé
  1. HELP, Please (Can't boot)

    /sbin/mount -uw / --- is the full and proper command and what it is doing is mounting your filesystem which is represented by the "/" as read-write because by default in single user mode it's read only. SleepEnabler.kext does exactly what it suggest. Enables Sleep Mode. It is not needed to boot up it is only needed for Sleep functionality, your Hack could live without it if you never put it to sleep. However I believe the extension version must match the kernel version. As others have mentioned, and the Kernel Panic itself mentions to a certain extent the cause for your Kernel Panic is SleepEnabler.kext - it needs to be removed from /System/Library/Extensions.
  2. Hello, I've been running Hackintosh for at least the last year, but probably closer to 2. For the most part my system has been completely stable even with an AMD chip and carefully following the vasts amount of information available online. However a few times over the weekend I got a kernel panic I've never seen before.. "Invalid kernel IP won't attempt to handle trap (double panic)" there were some additional numbers but I suspect these to be useless. I suspect the AppleAzailaAudio potentially. As it's a 32bit ancient Kext I'm using in 64bit SL but Audio works perfectly. (Used to use VoodooHDA - switched to AzailaAudio - naturally I feel this might be the cause but based on the kernel panic CAN it be the cause?) Just trying to get some feedback before making to many changes at once. I already removed what I consider unused kexts to be safe (AppleHDA, SleepEnabler - since the system won't wake up anyways). I suspect audio only because googling the kernel panic brings up multple audio topics but if anyone knows what that kernel panic means, just a gist of what happened maybe not an exact cause, that would be great. The panic didn't backtrace to anything relevant or any kind of kext..
  3. Awesome thanks for the link. So OOB meaning it should just need GraphicsEnabler=Yes?
  4. Hello everyone, I'm throwing in the towel on this whole fermi freeze issue and selling my GTX 460. I happen to be aware of a good deal on a 9800GTX, I know a step down but I only want something decently powerful I don't play the latest and greatest games, just some casual WoW. I'm currently on 10.6.8 (Lion is not an option for me yet as I'm on AMD) Will the 9800GTX work OOB with GraphicsEnabler? I feel bad asking for confirmation but I have seen so many mixed reports that I just have to double check with the experts (you guys) I don't want to buy yet another GraphicsCard that can't get along with OS X The GTX 460 performance in OS X is sub par and then you add in the freezing thing I just really want a stable semi-capable card lol. Hope you guys can fill me in Thanks in advance for your words of wisdom on the subject.
  5. The Fermi "Freeze" Discussion (Possible solutions?)

    Another note does anyone know what Exception Type = 0x26 is? I'm still digging but I'm not finding any good documentation on the driver is trying to tell us...
  6. The Fermi "Freeze" Discussion (Possible solutions?)

    I'm not so sure the Power States actually change all that much other then the performance of the card. It seems I get the best performance by choosing MacPro4,1 and then in AGPM going under MacPro4,1 (search for it) then where Device10deVendorXXXX (don't quote that) change XXXX to 0e22 (VID for GTX 460 in my case) and reboot. Suddenly UI animations are smooth and performance is up to a generally acceptable level. Fermi Freezes are identified with this error: NVDA(OpenGL): Channel exception! exception type = 0x26 = FECS Err: Watchdog Timeout After some research on what this Watchdog thing is I found a article, actually several that explain it: http://randomcontrol.../Watchdog_Timer It seems in Windows this timer can be disabled with a registry modification. If in OS X the watchdog works the same way as Windows it's killing applications that lock the display driver for "too long". Perhaps it's killing our kernel? or perhaps it's killing the display driver itself? I think... if we could disable this Watchdog Timer or increase it's timeout from 1-2 seconds to idk 4-10 maybe that would solve the problem? I'm not sure what that would require or what that would entail. I'm going to keep digging around but perhaps a dev could find out more about this... It has something to do with CUDA..
  7. The Fermi "Freeze" Discussion (Possible solutions?)

    I recently upgraded to this card on 10.6.8 / AMD. I am - after much research - so far running stable. The issue is almost certainly the power management driver on Snow Leopard not properly using the Fermi cards g-states properly. For me panics would occur after the g-state was leaving 3 to go to 0. G-state 0 doesn't exist on 4xx or 5xx series cards (to my knowledge from the research i've done!) Soooo we don't need g-state 0, g-state 1 is already full power. G-state 3 is also the unreliable state so we need to disable it, for me I disabled it by telling the driver don't switch to this state unless the graphics card has more then 98% idle time - which since the desktop is rendered by the GPU very very very rarely if ever happens. So in the end my info.plist section for 460 looks like... <key>MacPro4,1</key> <dict> <key>Vendor10deDevice0e22</key> <-- (0e22 = GTX 460) <dict> <key>Heuristic</key> <dict> <key>ID</key> <integer>0</integer> <key>IdleInterval</key> <integer>250</integer> <key>SensorOption</key> <integer>1</integer> <key>SensorSampleRate</key> <integer>4</integer> <key>TargetCount</key> <integer>5</integer> <key>Threshold_High</key> <array> <integer>0</integer> <integer>45</integer> <integer>75</integer> <integer>100</integer> </array> <key>Threshold_Low</key> <array> <integer>0</integer> <integer>0</integer> <integer>87</integer> <integer>98</integer> </array> </dict> <key>LogControl</key> <integer>1</integer> <key>control-id</key> <integer>18</integer> </dict> You need your SMIBios file to specify a MacPro4,1 so the AGPM loads. You also need to remove AppleTYMCEDriver.kext. Make sure to repair permissions on the driver. You can check if AGPM is loaded with - "kextstat | grep AGPM" If you changed LogControl to 1 like in my sample you can see your graphics card changing states with - "sudo tail -f /var/log/kernel.log" My g-state changes look like this: ###The first one is on boot when it changed from 3 to 1 for the first time, notice it never goes back to 3 and never goes to 0 - So far no freezes. 1 is when I had a game up and running, 2 is when I had the game closed and just browsed the web. 2 = lower power mode 1 = full power mode. So far no freezes, Good luck! ### Oct 29 00:15:52 - kernel[0]: AGPM: GPU = display G-state set to 1 from 3, ControlID = 18 Oct 29 00:15:59 - kernel[0]: AGPM: GPU = display G-state set to 2 from 1, ControlID = 18 Oct 29 00:18:08 - kernel[0]: AGPM: GPU = display G-state set to 1 from 2, ControlID = 18 Oct 29 00:52:15 - kernel[0]: AGPM: GPU = display G-state set to 2 from 1, ControlID = 18 Oct 29 00:52:17 - kernel[0]: AGPM: GPU = display G-state set to 1 from 2, ControlID = 18 Oct 29 00:52:26 - kernel[0]: AGPM: GPU = display G-state set to 2 from 1, ControlID = 18 Oct 29 00:52:42 - kernel[0]: AGPM: GPU = display G-state set to 1 from 2, ControlID = 18 Hope this helps... there is a ton of information on this problem out there. The solution lies in APGM and making sure that it's not addressing states that don't exist with the Fermi cards or dropping the power into State 3 to often which is the unreliable state to come out of it would appear. This works for me - so far - been running a few hours stable. Only time will tell. But good luck and give it a shot! EDIT: A.) This information is not all original so don't think that it is! Credit goes to all those who come up with this stuff to help us poor guys out. B.) After a few hours - longer then usual - I finally got a freeze. Adjusted PCIE speed to 101MHZ to see if it helps... interestingly I didn't get the normal watchdog NVDA error in the console, showed a g-state change and then just entirely locked up. I really hope a solution can be found for this other then Lion as it may be a bit before us AMD guys get to go to Lion. C.) all the freezes seem to occur immediately after a G-state change. In theory you could lock it to state 1 and maybe never freeze but would generate a lot of heat and use a lot of power for no reason. - sigh such an annoying problem
  8. AMD CPU Problem

    Use Nawcom's ModCD or ModUSB to do a retail snow leopard installation. Then you can use the combo update to install 10.6.8 (don't reboot) then install the Legacy Kernel (also available from Nawcom) for 10.6.8 which includes 64 bit support - make sure to check the AMD force64 option or add it yourself to com.apple.boot.plist. You will then have to patch some files to enable 32bit applications to run properly in a AMD 64bit userland. So. 1.)Use Nawcom ModCD or ModUSB to install a Retail Copy of Snow Leopard (don't be a pirate!) 2.)Once installed download the OS X 10.6.8 Combo Update from Apple 3.)Install the Combo Update - DO NOT REBOOT! 4.)Install the 10.6.8 Legacy Kernel which you can get here: http://blog.nawcom.com/?p=791 5.)Read this forum post and follow the instructions carefully to patch your binaries to be AMD64 friendly: http://osx86.co/f57/amd-and-legacy-t7263/ (specifically look at Post #4 by Akimoa - that is what you have to do) 6.)Enjoy Snow Leopard!
  9. Lion AMD

    No AMD (Aka Legacy Kernel) for Lion exists yet. In the world of AMD hackintosh's you may as well accept that your best experience might be staying behind one version of OS X. I used Leopard for the longest time, and just recently finally upgraded to Snow Leopard now that AMD support for it is near perfect... (I probably could've done this around 10.6.6 but was hesitant to start messing with a perfectly functional stable system until apps started complaining Leopard was to old heh heh) I expect it will be the same story with Lion. - But hey, at least OS X is relatively the same each release so you don't feel like you're missing out on something huge You never know though... Nawcom, AnV, all the others involved, have gotten very talented with the AMD stuff. Wait and see.
  10. Hello, I have been running OS X for years now and finally made the upgrade to Snow Leopard. I used ModUSB and Retail as well which so far runs a heck of a lot better then the Leopard distro I was using. Retail is always better I guess. I have a few questions though, now that the system is up and running. 64bit is working correctly with all the proper INSN patches and what not however... 1.)System doesn't sleep. With SleepEnabler.kext, the one included with Nawcom's 10.8.0 Legacy Kernel, the system will go to sleep - however when I wake it up I get the black screen of death and no system activity. 2.)VoodooHDA Sounds terrible unless I check Use SSE2 and Enhance Audio - it doesn't seem to remember these setting changes though, is there a way to set them permanently? 3.)Is hardware virtualization possible? I searched and found a few fixes that are aimed at VMWare but I still get crashes or in Virtualbox I receive (VERR_MAP_FAILED) if Hardware Virtualization is enabled. 4.)Very minor but may as well mention it. The system doesn't reboot either, it will go all the way to a halt with a black screen but never actually fully reboots. Shutdown works fine however. Tried EVOReboot and OpenHaltRestart and neither had any effect. None of these are deal breakers of course but they are the only 4 issues my box seems to be having. I would love to fix them if it's possible! My board is the GA-MA770-S3 with the SB600 chipset. I appreciate any suggestions you AMD guys might have and would appreciate any ideas. Believe me, I have been Googling the {censored} out of these problems and wouldn't ask for your time and assistance without trying everything else first. Just a little disclaimer as I'm sure the first thing some think before not responding is just google it haha. Thanks guys! TheDub
  11. Hello all! I am running a AMD system and have Snow Leopard essentially fully functional. I have upgraded to 10.6.8 and the 10.6.8 legacy kernel which included the AMD64 option. I enabled it and it modified my /Extras/com.apple.Boot.plist to contain: "-force64" and "arch=i386" in the kernel flags. (arch=i386 is supposed to be arch=i386_64 I believe) With these flags, the system boots and recognizes all of my RAM! A first for OS X on my particular system. The fun stops there though, most apps work such as Safari but within Safari flash doesn't work. Tried Google Chrome / Firefox and they both barely work at all. The system doesn't seem unstable, no panics, just lots of random hanging. Am I missing something? Any assistant is as always appreciated. Install method: Retail + Nawcom ModUSB Thanks, Dub
  12. Well - I wish you luck whatever you do. But I took the plunge and backed up my Leopard installation that has so loyally served me for the last couple years and installed Snow Leopard. Let me just say - Nawcom's ModUSB solution works BRILLIANTLY! You can use ModCD if you dont have a Mac to create the flash drive with ( I did this from Leopard ) but you use the retail installer, it auto-detects 90% of what you need to at least get you booting. Worked out of the box with ModCD/ModUSB/Nawcom autodetcted drivers settings: -SATA / AHCI / ATA (supposedly but I don't use it) -Audio via VoodooHDA (There was a odd volume control bug until I upgrade to 10.6.8 and Legacy Kernel 10.6.8) -Graphics with full acceleration (Nvidia card) -Wired Networking -All basic things seem to be functional. What didn't work? -Sleep -Computer doesn't halt properly so shutdown / restart stops at a black screen (OpenHaltRestart will likely fix) -App Store was broken ---Fixed this with the Lizard app - Had to specify what type of Mac to emulate and generate a Serial Number so the App Store thinks I'm an authentic Mac, not a Hackintosh And that's it. Overally its 100% functional with a few kinks that were worked out or need to be worked out yet - all of which are likely fixable with some research or ok to live with if they aren't. I HIGHLY recommend you try the retail method with Nawcom's utilities. They have really made this easy - I never thought I'd be using a retail install on a AMD. But I am. That's that. I hope you are somehow able to get it working in the long haul because, let's face it, nobody likes Windows. Cheers, TheDub
  13. The no root device error -> I realized you may have forgotten to select a Disk Controller driver in the install. Somewhere in the customize -> Drivers section you will see a SATA entry, if you expand the Sata entry it will show controller options, you must select AHCI. Disk Utility can you show you any Disk's ID if you select it and read the information bar at the bottom. If you take your time - Do a little research - And be patient you can probably get a working Hackintosh. I can verify the new methods of installation work with Snow Leopard, both retail and iAtkos S3V2, on an AMD System with a Gigabyte MA770-S3 SB700 motherboard/chipset. Hopefully yours is compatible to but you just need to take your time in customize and make the right selections. EFI Strings -> Your outputs - For Video Qoopz 9.7.0 (Leopard) or Qoopz 10.3.0 (iAtkos Snow) or not mach_kernel for retail - Kernel SATA Driver must be selected and it must be AHCI If you get all 3 of the above entries correct your system will boot. You might not have sound, networking, CI/CL but it will boot unless your motherboard is just simply never going to be compatible. I read the AMD800+ chipsets have some issues and won't boot.
  14. Still waiting for root device - means that OS X doesn't see your hard drive properly. Going to have to Google around the Forum, if you have SATA in AHCI mode and still get those errors something else is wrong, maybe the chipset isn't working, bad extensions, idk.
  15. iAtkos contains 4 kernels to choose from during the initial installation I believe. After installation there will be ONE kernel installed on your system and it will be located at /mach_kernel If you didn't choose ONE kernel during the installation of OS X via the iAtkos distro then the retail kernel is installed and will not work - you will have to start the installation over and choose a kernel that properly supports AMD. OR Follow either of the two guides posted word for word and you should get into SL.