Jump to content

Josvdp

Members
  • Content count

    62
  • Joined

  • Last visited

About Josvdp

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    The Netherlands
  1. I'm running 10.6.6 with DD's script and I've just purchased an HDTV. I was hoping to get this running on my HDMI, but when I start with the TV plugged in, I get no image. Even the normal monitor doesn't give image, it simply shows a black screen. Researching this issue, I came quite quickly across problems people had with 10.6.3. But as I am working on 10.6.6 I was hoping this didn't affect me. Most solutions haven't worked for me and I don't really feel like a reinstall at the moment. Has anybody got HDMI working on this hack? I'm using a GTS 250 which is basically a rebranded 9800 GX. I have an EFI string in my boot.plist and graphicsenabler on.
  2. I hoped to not have to come back to this topic for this issue, but I'm afraid I have to. This problem is still present. After the overclock it was gone for a while, but no it's back again. It seems to happen randomly because sometimes in the morning it wakes from sleep fine, but when I come home from work it doesn't. At this point I'm even suspecting the power supply to be the cause. You see, the power in my apartment has a reputation of failing... But other than that, does anybody have a clue how to solve it? I'm not even sure this is the right topic to report this, since I can't prove it is due to this method I use... Let me just say that D_D's script is amazing nonetheless!
  3. It sucks that it died, but just for the sake of informing you, I have a 250 GTS too and I have played some Steam games on it with no problems whatsoever. I installed the Nvidia drivers (and CUDA for Premiere CS5) and I use an EFI string. I'm not sure if I had the Nvidia drivers installed already before I started playing Steam but somehow it works here. Maybe the problems you encountered were some kind of sign that your 250 GTS was about to die? Windows was just too dumb too notice it but Mac OSX did...
  4. My overclock was very quick and probably was very unstable this time. Normally I spend a bit more time getting things stable but I suppose I was just a bit too inpatient. It didn't make sense to me either, but as it turns out, going back to stock speeds solved the problem. I think that the OC affected my (simple Kingston) RAM and since this is used during sleep it caused the problem. With regards to the squealing, it is something that has been there from the start and I'm ok with it. I decided not to go through the hassle of RMA with Gigabyte, even though it is probably part of warranty. An odd thing happened yesterday when I put it to sleep: the fans spun up and the display went off like normally, but the system didn't power down. So the fans kept spun up. It might have been a once-only hickup but I'll keep an eye on it.
  5. You were right and as I myself also expected, it was the overclock. I took it off and sleep worked right away. The problem is that my motherboard squeals when it runs at stock, this seems to be a common problem.
  6. I'm experiencing a strange problem and I have difficulties searching for it, so I'd be very happy if someone could share their thoughts with me on this one. My fresh 10.6.6 installation worked fine until a few days ago. I have absolutely no idea what I changed (installed?) but when I put my setup to sleep and leave it for a while (a few minutes) it is not in sleep anymore. Pushing the power button will just boot normally. To me it feels like mij RAM is just walking away... One thing I suspect is my overclock so I will check that later, but it's a mild one and this system has survived more rigorous OC's before. Anybody?
  7. Me and Sapricot discussed the exact same problem 2 pages back, here and here. It seems to be a problem between the UD5 mobo and a version of Chameleon. An older version of Chameleon still works fine. So, put r115 on your USB key (option 2 in D_D's script) to do the installation and after installation overwrite the bootloader on your hard disk with the latest chameleon from D_D's script. Edit: Hehe, lol @ Sapricot
  8. Maybe you could try running with as little kexts as possible? Like D_D said in his first post: Questions from my end: 1. How come I see CPU temps in the iStat widget only and not in iStat menu's? I know this is more of a question for iStat makers, but since I'm running my system on D_D's script... 2. Does anybody know why the installation of CUDA drivers (I think it is this) broke my sleep? Now the monitor goes off and the fans spin up but the system never cuts power. Does anybody have any suggestion on how to fix this? Never mind, I think it was a faulty installation of Remote Desktop causing this. Also, I installed the latest stable driver build and not the developer build. After this the sleep problem was gone.
  9. Sorry for the late answer, but: no it doesn't matter if you run under 32-bit. I'm not an expert though, so I am probably wrong. Nevertheless, I haven't had any difficulties or problems with a slow running OSX under 32-bit. I run CS5 and I can see in my Activity Monitor that it is running in 64-bit. Yes, defining a boot flag when booting overrides your boot.plist once.
  10. Sounds frustrating indeed, after several tries with default setups... In case you are experiencing such random and annoying problems I would strip down to the bare minimum, then slowly build up to see where the problem introduces itself. Also, be sure to turn off the auto-sleep options (including sleeping HDD's) in the Energy settings. It's an obvious thing, but I'm just saying it to be sure. So, I'm sure you've thought about it, but you could try to trip out your PCI-e card and disconnect all but one (clean) hard drive. Then, use D_D's script/guide to create a USB memory stick Boot Disk (quickest method in my opinion). The next step would be to install OSX through that USB Boot Disk on your clean hard drive. Don't copy over any of your files, yet. I actually recommend not doing that at all, just manually copy over your files and maybe some crucial Library files such as e-mail and address book. I've stopped copying over my complete profile to new installations. It's great when you actually have a mac or time machine, but on a hackintosh it just creates an unstable situation where you don't know where to find the cause of your problems. After installation, test your new setup for a while (does everything work? Sleep?), take your time to update to 10.6.6 and maybe start installing some of the apps you use. When you feel like things are stable, start plugging in some hard drives and afterwards try to put your PCI-e card back in. Keep this setup idle overnight to see if you have the same problem. I'm sure that when you build up slowly, you will notice where things go bonkers. Good luck I have the exact same setup as you (including GPU) so in case you have problems, contact me. As for the 64-bit mode, you should question yourself whether you actually need it... Sure, 64-bit sounds/feels more awesome, but in a lot of cases you don't need it (2GB+ RAM allocation). Furthermore, it is possible for apps to run in 64-bit while OSX just runs under 32-bit. So if you still feel like going 64-bit, first make sure that all the kexts you are using are capable of doing that. The latest SleepEnabler.kext for 10.6.6 is known for NOT being 64-bit (or is there already an update out?). In case you don't know, you can always try to boot and see if it works by trial and error. But before you put the boot flag in your .plist permanently, it is good to try booting with a temporary boot flag like D_D also suggests in his guide. You do this by simply start typing the wanted boot flag when Chameleon is showing at boot. The flag for 64-bit mode is: arch=x86_64
  11. Great update D_D! Amazing work! To be clear: with the new sleepenabler your script is 'officially' updated to work on 10.6.6, right? Hehe, I had the same problem as you. I had AC97 plugged in as I would normally do when I used to build my PC's. Anyhow, good that you managed to fix it quickly and easily. And, yeah, installing the new bootloader with D_D's script is so much easier
  12. Mind you, in the time that I was using the older sound kext (I used d00d's guide before too) I had to manually switch the sound output to the front. So before you go through the hassle of reinstalling/re-hacking, check your System Settings. In some cases you need to switch to 'headphones' when you plug them in. The LegacyHDA I'm using with DD's script now switches output itself. The most obvious thing to rule out your Win7 HDD is to simply disconnect (or disable in BIOS if you can) the Win7 HDD and see if the beach ball problem still persists.
  13. The topic starter already mentioned that you have to put pmVersion=21 in your boot.plist
  14. It just seems that this motherboard (GA-EX58-UD5) is just very picky. I used r115 on my USB drive to install OSX. After the install I simply installed r642 on my HDD with DD's script and now it boots fine from the HDD using r642. The problem only seems to exist when booting r642 from USB. Anyway, I have no idea what C-States are so I'm not sure if I'll need it anyway ;-) your setup sounds very promising though. I've used d00d's method before, but it is not an easy thing to do when you're a n00b like me. Did you follow his guide or did you simply use a pre-patched DSDT for your setup? Maybe I should dive into his topic again for some more studying because I like the native powermanagement. Unfortunately, I don't have the time at the moment. 10.6.6 seems to be running smoothly using DD's script and this SleepEnabler.kext (with pmVersion=21 in boot.plist). I'm working with a GTS250 as well and I have no problems outputting through DVI. I used DD's script to generate an EFI string in my boot.plist. I'm not running a dual monitor setup but I have done that before and it worked, although somehow wake-up form sleep didn't work when using both monitors. Sometimes it doesn't work to edit the boot.plist in the extra folder, there is actually another boot.plist but I'm not sure where. I've come across that problem before and sometimes it uses the boot.plist from the other location. Just try using DD's script to put the EFI string in the boot.plist. I'm not sure if this is the same kext as the 'old 10.6.5 Sleepenabler' that you describe but it works for me under 10.6.6. Remember to put pmVersion=21 in your boot.plist. Sidenote: It seems that this SleepEnabler.kext does not yet work under 64-bit, so be sure to have arch=i386 in your boot.plist as well.
  15. I had a 10.6.4 installation working with the native powermanagement thanks to the guide from d00d. After doing some research I decided to take the plunge into 10.6.6. Unfortunately, I encountered some KP's and I started to try and fix it but my n00b-skills didn't really help. I decided to do a complete reinstall with DD's script because I had done that before. But already, after a few minutes I came across a problem with booting from my Boot Disk. I seem to have the same problem as you Sapricot! I have created a boot disk from a 10.6.3 image with the script and when I plug it in, it freezes at POST. It doesn't even pass on to the memory check, it just freezes at 'CPU: Core i7...'. When I ran the script there was no option to choose a bootloader but the updated script from DD has the newest RC5 included anyway, so it shouldn't be a problem. Of course, I formatted my drive with GUID and I have tried a second external drive to be sure but came up with the same problem. Anybody any idea what I can do to solve this hanging? ---- Update ---- I installed bootloader RC5 r115 with DD's script (option 2). With this I was able to get across POST. I chose the 'replace' option and after it finished I put back the 3 files in the Extra's folder that I had backed up, which seems to have done the trick.
×