Jump to content


  • Content count

  • Joined

  • Last visited

About maruchan

  • Rank
    InsanelyMac Protégé
  1. DSDT Auto-Patcher

    Awesome! Thank you so much!!
  2. For people getting lag on hi-def Flash videos, depending on your processor, this isn't really uncommon--it is well known that Adobe's OSX Flash Player is subpar in comparison to its Windows counterpart; just because it doesn't lag in Windows does not mean that it shouldn't lag in OSX either. Flash is supposedly even worse on Linux. With that being said, with an EP45-UD3L and a Core2Duo e2160 (1.8ghz stock, OC'd to 3.0 ghz) I can run hi-def flash video perfectly, as well as 1080P h264/mkv video in Leopard 10.5.8.
  3. For those who don't have working sleep, my sleep was broken at first (EP45-UD3L)... the computer would appear to sleep fine, but when I tried to start it back up, it would just reboot. Then I remembered there was an option I had to check in Leopard before sleep would work called "Restart automatically after a power failure" under the Energy Saver settings. Found it in SL and sleep worked (be sure you have sleepenabler.kext as well.)
  4. I have a GA EP45-UD3L. Here are my experiences, with those who have the motherboard... if anyone else has advice or reports, please post: I installed SL to a spare IDE drive from inside my Leopard 10.5.8 installation (on a different SATA disk.) I'm NOT using AHCI as it would make no difference, I installed to an IDE drive. Anyways, after the install finished, I dropped in all of the kexts included in the guide, made an EFI string, and installed Chameleon 2RC1. Booted with "-v -x32" On first boot, graphics worked but no sound (see below.) I tried doing the Apple account setup, and got far enough to create my username, and then after that I had an MDWorker panic. Rebooted I was getting KP related to MDWorker, as mentioned, so I did the spotlight trick (took me a couple of tries, as it panicked before I could even get to the menu at first) and then it stopped KPing over mdworker. But the panics persisted, related to other things. I tried to run DiskUtility, but it failed making the mkext and when I tried to be reboot I got the dreaded BSOD (no mouse or anything, just sat at the blue screen.) I tried clearing the kextcache from single user mode, and it didn't seem to change anything, so I booted into Leopard and used Disk Utility to repair the permissions on the SL drive. Didn't seem like it repaired anything, but a reboot proved successful. I was back into SL. This time, KextUtility worked and everything seemed fine. So what didn't work? And what's different from the guide? - Audio - I tried to insert DSDT audio code for my 888. Then I tried a few different 888 kexts to supplement. No working sound in 32-bit or 64-bit. If anyone has audio working for ALC888 on the UD3(L) series, please post how! I'd love for the audio to work. - As mentioned, the JmicronATA kext that comes in the package is NOT 64-bit compatible. You can find one at PCWiz's download site, or linked a few posts above, I believe. After that, I was able to boot into 64-bit mode. - Finally, it wasn't seeing any of the other drives Chameleon was listing (Win 7, Leopard.) I installed Netkas' AppleIntelPIIXATA.kext and voila, I could now see them. Just a few things left to iron out! Mainly the sound.
  5. I have a working dual boot with OSX and Windows 7 using only Chameleon 2. The steps are as follows: 1.) Boot the Windows 7 install disc. Create two partitions, one for W7 and one for OSX. While setting up the partitions, W7 will tell you that it may create an extra partition. 2.) Install W7. 3.) Start W7 and make sure everything is okay. It should be. From inside W7, format the blank partition to FAT32. 4.) Using a tool like GParted Boot Disc, set the FAT32 partition to be the active partition. 5.) Boot the OSX install disc, use Disk Utility to reformat the FAT32 partition to HFS+ and install. 6.) Boot into OSX and install Chameleon 2. Restart. 7.) Now you should see 3 partitions in Chameleon. One is "System Reserved", the other is W7, the other is OSX. To start W7, boot the System Reserved partition, NOT the W7 partition. W7 stores its bootmgr file on the System Reserved partition. Boot OSX as normal. If you would like to get rid of the System Reserved partition and boot the W7 partition directly, boot back into W7, give the System Reserved partition a drive letter, copy all of the files to the root W7 drive (C:\ probably) and then delete System Reserved. You should now be able to boot W7 directly. This is what I did, hope it works for you! As a final note, Chameleon 2 apparently breaks hibernate/sleep in W7. I spent a day or two trying to figure out which driver would be causing the sleep conflict, only to find a post on the voodooprojects forum that says Chameleon prevents Windows from waking back up from sleeping. If you can live with this, the setup is perfect!
  6. My partitions are set up as follows: Partition 1: Windows 7 (HFS+) Partition 2: OSX (HFS+) Partition 3: Data (HFS+) Originally, Data was formatted as NTFS and I was using NTFS-3G. That is, until NTFS-3G crashed and wiped a bunch of the files off (egh.) So, I reformatted Data as HFS+, and after a few days of use got around to rebooting it and now com.apple.Boot.plist isn't being read. Perhaps, somehow, there is a hidden Boot.plist on the new partition? I think I would've noticed it, but I'll do a search when I get home from work.
  7. Hi everyone, I've been using Chameleon 2.0RC2 happily for a few months now, but upon reboot today I realized that the com.apple.Boot.plist file in my /Extra/ folder wasn't being loaded. I don't see any errors in verbose mode, but there's no timeout, my "Graphics Mode" setting is ignored, etc. Does anyone know what would cause this? I tried chmod 755 and chown root:wheel on the file, but it didn't make a difference. Sorry if this has been answered before... I tried searching, to no avail.
  8. I have a question... I use distros because I read once that you need a SATA optical drive for the boot 123 method. Is this true? I only have an IDE DVD-RW.
  9. 10.5.8 deep sleep problem?

    Make sure you're not overlooking NullCPUPowerManagement.kext. I'd removed Disabler.kext and was frustrated by sleep still not working, then I discovered that and removed it. Sleep now works 100% at the expense of my CPU running a few degrees hotter.
  10. OSX 10.5.8 is now in software update

    Is sleep not working when OSX sleeps itself, or is it not working when you go to Apple Menu > Sleep? After updating to 10.5.8, sleep wasn't working when I went to Apple > Sleep. I read today that deleting Disabler.kext fixes it for some, but at the expense of CPU temperature. After deleting it, sleep still didn't appear to work and my temperatures were the same. I walked away from my computer and when I came back it was sleeping, but woke up fine. I also just realized I have NullCPUPowerManagement.kext in my extensions, so that may explain the temperatures staying the same. Sleep menu option still doesn't work, but this is not a huge issue since auto-sleep works. To anyone experiencing sleep trouble, check if both don't work or if one or the other does. Edit: Just removed NullCPUPowerManagement.kext and I can confirm that sleep now fully works (from Apple Menu and via auto-sleep.) As expected, the CPU seems to be running about 5-7 degrees hotter than it did before.
  11. OSX 10.5.8 is now in software update

    Updated via software update and everything went fine. First reboot it hung and second reboot I got in with everything sans audio and sleep. Audio was fixed by reloading HDAenabler. We'll have to see about sleep. Update history: 10.5.6 Vanilla > 10.5.7 iDeneb Combo Updater > 10.5.8 Software Update
  12. ASRock 4CoreDual & nVidia

    I have an ASRock 4CoreDual-SATA2 rev 2 and, from everything I've gathered (both from others and personal experience), you're outta luck with the PCI-Express graphics. I switched from AGP a few months ago and decided to give OSX a try, and while everything works perfect (sleep, shutdown, restart, etc) I cannot get QE/CI enabled with either a Gigabyte 8400GS or with an ASUS EN9400GT. Multiple people have confirmed these cards working and even went so far as to send me the exact Kexts they're using. I've also tried NVInject/NVKush/NVDarwin/Natit, EFI strings, multiple NVCAPs, generating my own NVCAP, etc. with no luck. So, as much as it sucks to admit, I'm guessing it's a matter of the 4x PCIe slot not playing nice with OSX86.
  13. Drivers for Nvidia Geforce 9400 GT - Success

    Both cables I'm using (DVI and VGA) are the ones that came with my Samsung SyncMaster 220WM. I don't know why I said I picked it up; what I meant was that I finally found where I placed it They seem to be decent quality cables, but I'm not sure... I'll take a closer look at them when I get home from work. I'm still confused as to why certain drivers result in a black screen, and other methods result in just a quick black flash and a frozen image of whatever's on screen at that moment. I initially thought that the black screen meant the OS was still loading, but couldn't detect a monitor on whatever port it's connected to, whereas the quick flash meant the OS had locked up, but I'm pretty sure it's just freezing. Hmm... will play with more EFI strings this evening... I'm beginning to think I should just spend the $50 on a new ASUS or Gigabyte mo/bo.
  14. Drivers for Nvidia Geforce 9400 GT - Success

    Thank you for all of your help Stanza-- I've tried different NVCAP settings with the EFI string--DVI/DVI, VGA-DVI-I, DVI/VGA, as well as the NVCAP I get from NVCAP Maker... frustrated about the lack of DVI output, I went out and picked up a VGA cable, only to find that the two scenarios I described persist even over VGA. This rules out my monitor's EDID, as I not only generated an override for it, but VGA doesn't even use EDID (from what I've read.) To my surprise, the VGA output on my 9400 GT is very crisp and (to my eyes) looks the same as my DVI port; my previous card was an AGP Radeon x850 PRO and the VGA output was terrible. I never ran OSX86 on it, so I can't speak about whether or not it worked, but I would be content if I even got VGA working and forgot about DVI completely (I'm only running one 22" 1680x1050 monitor and don't plan to do anything like a dual monitor setup, TV-out, etc) If I remove NVDAResman.kext, I'll get past the black screen and system profiler will show my card's 512mb and recognize it, but there will be no resolution switching and no CI/QE, so it's rather pointless. Does anyone have suggestions as to what could cause a frozen bootup or black screen on BOTH VGA and DVI? I'm going to try doing a fresh install of iPC instead of XxX and see if changing the distro elicits any different behavior. I got in contact with the user who posted the ASUS 9400 GT working in the 10.5.6 HCL list, and he says he's used them in a few machines and they all work wonderfully. That, coupled with Stanza and some others who have posted this card works fine is keeping me going... but because my 8400GS did the same thing, I'm beginning to wonder if it's an incompatibility with my motherboard's 4x PCIe slot (ASRock 4CoreDual-SATA2, it's a 16x fitting though it runs at 4x electrically), though without any drivers or without NVDAResman, the DVI/VGA works fine, so it's not as if OSX can't use it whatsoever.
  15. Drivers for Nvidia Geforce 9400 GT - Success

    Well, I have to report that Stanza's EFI string didn't work :[ I think this is because his PCIe bus is in a different position (mine was something like (2, 0) if I remember right) and CoreVidia does the same thing any of the other injectors do. I'm so, so frustrated at this point, especially because I know other people have got the same card working--in fact, I bought this card BECAUSE I saw other people getting it to work. Sigh. The only things I can think of are either: 1.) An NVCAP issue. This seems like a possibility, but others have reported VGA/DVI working with no further messing around and I've tried many, many different NVCAPs. I'm using DVI and have no way of testing the VGA port at the moment. 2.) It's a problem with my mo/bo. This is because I'm using the 4coredual-sata2, which a number of people seem to have success with, but the PCIe slot on it is only 4x. I never thought that was a big deal, but in the HCL someone mentioned that a certain nVidia card wouldn't work on my board specifically because of the 4x slot. Maybe it's not just limited to that specific card... :/ I have seen other people with the same board post that they have working PCIe cards though they tend to either be ATI or older nVidia (7300/7900). 3.) Perhaps a monitor EDID issue? I don't think so, though, as it's not as though the monitor gets no signal, and it works fine when I don't muck about with the display drivers. If ANYONE has any suggestions, I'd love to hear. Another distro perhaps? XxX supports everything my computer has, this graphics card is the last piece of the puzzle and I really wish I could get it going... :[