Jump to content

Templeton Peck

Members
  • Content count

    213
  • Joined

  • Last visited

About Templeton Peck

  • Rank
    InsanelyMac Geek
  1. Hi dd, I've been using your script since Snow Leo. Great job! Have a bit of a roadblock issue, and I'm hoping you/others can help. I'm running Mountain Lion now, and I'm attempting to make a bootable USB installer for Mavericks. However, my MBR-formatted USB drive does not appear in the list of available targets in your script. For argument's sake, I tried installing to a GUID-formatted drive, the script succeeded. However, the resulting USB drive hangs at the BIOS screen on my mobo (GA-EX58-UD5). Not sure how to proceed from here. Tried [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] with my MBR disk, and the USB disk was created successfully, but I get the famous reboot loop when trying to start from that. I'm confident I'd have better luck with your script, if only I can get it to recognize my disk.
  2. It works fine for me. I used the dsdt.aml from the boot image in RAS' post (this is essential). Then I put ALC889a.kext directly into S/L/E. I also used the two Legacy HDA kexts from the "more kexts" link in RAS' post, though I don't think these were factors in getting it working. Then, I added the "-x32" flag to my boot.plist (I don't know if it works with the 64-Bit kernel, but even the Mac Pro uses 32-Bit, so who cares!). Finally, I ran Kext Utility and rebooted. The result: I have s/pdif out and in working perfectly (I have the gigabyte spdif-in bracket). FYI, it's supposed to say "The selected device has no output controls." That's how digital audio works on the Mac. It just sends the bits straight from your application to the target device. You can still control the volume from your applications and your target devices. One more thing: These kexts are safe to install in S/L/E. These don't replace Apple's kexts, so you won't have any trouble with software update.
  3. I'm thinking this is a issue with the JMicron controller, the infamous >4GB KP bug. But, I would think that the Kalyway system would have that fix installed. I don't have experience with dealing with this bug, but we could try several things: 1. Try "maxmem=2048" without the quotes at the bootloader prompt or include it as a kernel flag in your boot.plist 2. You could pull a stick of your RAM. 3. Use a SATA drive. 4. Install the later Kalyway distro, as you are doing. MAJ Cool, thanks! CONFIRMED: I pulled out a stick, and it installed fine. Since I'm only using the PATA drive for rescue/installation to a SATA drive, I'm comfortable with simply adding maxmem to my boot.plist So there you have it. You can't install from a PATA drive with >4GB RAM. Either use maxmem on your PATA installation, or pull out a stick when installing. Try to search the entire thread next time, before posting. It's tedious, it's boring, but it keep the thread length down, making it that much easier to find information.
  4. Geekbench is just reporting the same bad info as About This Mac. Neither app is getting the speed directly --they're both using the same intermediate library (part of the OS). Even if that library knows how to calculate the speed for our i7's, it could still get bad parameters from other sources, such as SMBIOS. If you look at CPU-X, you can see for yourself how screwed up the information is. For me, it's reporting 3200MHz core, with a 9.5 multiplier and a 333MHz FSB. Absolutely impossible. Firstly, 9.5x333 = 3163.5; not 3200. Secondly, in order to reach 3200 with a 9.5 multiplier, you'd need a base clock of 336.84... but fractional divisions are not permissible. Thirdly, the X58 base clock tops out at around 200MHz, when HEAVILY overclocked -- 336MHz would literally melt your northbridge. Above all, Mac OS X is completely incapable of overclocking your CPU. It would require third party software that doesn't exist for the Mac.
  5. No probs. It could be. I used to have this PS/2 to USB adapter that would behave like that. If you bought your mouse+keyboard new, then I would blame the adapter. Yeah, that's right. "About This Mac" miscalculates the speed. The issue is purely cosmetic, and has no bearing on the actual speed. If you're the OCD type, there's an option in DD's script for pasting the correct information directly into loginwindow.app. It doesn't really solve the problem, as it's just reporting what you tell it to, but whatever. Sounds about right. I think I had about 12-something, but that was with a hefty overclock.
  6. I have the same card (well, before they changed the name). Try plugging your monitor into the other port --It sounds weird, but it worked for me. VoodooHDA.kext should work for you (but only for stereo). You probably need to install it directly in /System/Library/Extensions for it to work (not the extra folder provided by the script). You can do this using kext helper. You should also remove the old audio kexts. For that, you'll need to remove the kext files from the audio folder in DD's script package. Then, run the script again, and select option 5 to install the kexts (This will reinstall all of your kexts to /extra minus the old audio kexts). Restart, and you should be good to go. I don't think this is a hackintosh issue. Most wireless mice/keyboards (mice, especially) exhibit some degree of input lag, which is usually only noticeable when playing games. If your lag is pausing/hitching, it's probably a weak/bad battery. In any case, I don't think it's hackintosh related. Look on real Mac forums.
  7. I've been using hackintoshes almost exclusively since 2005. It came at just the right time, too, as I was on the verge of completely abandoning the platform. In the early 00's, Apple started to phase out the mid/high-end desktop; the iMac was elevated in status (but not performance), and the towers became workstations. I loved the Mac, but I wasn't willing to get forcibly penetrated, just for the ability to use OS X. To answer your question, in the very beginning, each update required special attention, but that's not really the case any more --provided you have the right hardware. These days, we have EFI boot loaders, which makes most of the old hacking unnecessary. The few hacks we do still need (DSDT, gfx strings, special kexts) only need to be done once. While I can't make any promises for the future, software updates have been working for a while now on (supported hardware).
  8. That looks like a pretty capable machine, except for one weak point: Graphics. The 8400GS is pretty anemic by today's standards. For example, most games released over the past 4 years will run like a slide show, even on the lowest settings. It's not just games, either. 3D animation programs, Photoshop CS4, Final Cut Pro, Motion, iMovie/iDVD, or any other application that uses Core Image, won't run quite as well as it could. When Snow Leopard ships in the coming months, it will have a feature called OpenCL. This is basically an API that makes it easier for developers to utilize the graphics card for non-graphics (general purpose) tasks. When dealing with highly parallel general purpose tasks, a decent graphics card will run circles around our shiny new i7's. I would recommend a card that's powerful enough to require a cooling fan I'm kidding, but I'm not. Something like a 250 at the absolute minimum. For now, OS X can only use one GPU. So, cards with multiple GPUs (GTX 295 and Radeon X2 cards) will only work at half-capacity in OS X --The same goes for multiple *cards* in SLI or Crossfire. Personally, I'm running a pair of 8800GT's in SLI. In windows, this combination is faster than a single GTX 280, and roughly on par with a 285. But as mentioned, OS X only recognizes one of those cards. The reason for going SLI is that I already had one 8800GT and wanted to save some cash. If I were buying new, I'd have gotten a 280 or 285. In case you're curious, the GTS 250 is essentially a die shrunk 8800GT, which, for some reason, NVIDIA renamed a half-dozen times. Where was I?? Oh yeah... Great machine you've got, but I recommend a better card. I'm pretty sure that's how it's supposed to be. If you go to "Window" --> "Floating CPU Window," you'll see 8 threads in all their magnificent glory. Apple must've figured that having histories for 8 threads would be too cluttered; so they give one "average" history instead.
  9. I installed a 285 in my Dad's machine. First, follow DD's scripted install of the OS, followed by 10.5.7. Next, install the latest Mac 285 drivers from EVGA's website, and then Netkas' injector. When I first tried this, I mistakenly assumed that the 285 drivers were part of 10.5.7, and installed netkas without the drivers (until now, graphics updates have been available exclusively through software update). If you do this, you'll get garbled graphics, so make sure you have both in place before restarting. NOTE: The package installers referenced above will install to /S/L/E instead of /Extra. This is totally acceptable, since these are third-party kexts (as opposed to modified first-party kexts) and will never interfere with software update.
  10. Sounds wonderful. Thanks for your hard work! One thing I forgot to mention earlier is that when I first tried to run your script without a password, it didn't accept <no password> as a password. While bad practice in general, I figured it would make troubleshooting easier (Of course I used a password on my target install). Anyway, I ended up setting a password and running the script again, and all went well. But I just thought I'd let you know... Again, thanks for your hard work. Mine looks like that too, whether at stock speeds or overclocked. It didn't bother me, so I left it alone. One thing I did notice, though, is that DD's CPU-X info looks a lot more accurate than mine (and presumably yours). I think this could have something to do with the different chip steppings. I think "2.66 GHz Intel® Core™ i7 920 CPU" is the name that's hard-coded into the chip, whereas "About This Mac" actually tries to calculate the speed (incorrectly, in our case).
  11. Thanks, I updated to F7, and I got the same thing. Then I removed all my peripherals except for my Leopard drive, one video card, and a USB mouse and keyboard. Reset CMOS, and entered the settings you posted -- again, same issue. OpenHaltRestart is installed. Sleep works, restart works, but shut down behaves like restart (effectively). Weird, right? UPDATE: I tried removing OpenHaltRestart (just for the hell of it), but then the system didn't shut down fully (fans remained on). Then I tried booting from an iPC disc I had downloaded prior. Since that was an installation disc, the shut down option was greyed out, so I opened up the Terimal and typed "shutdown -h now" That worked properly! So at least I know that shut down is possible. But is this command equivalent to clicking shut down from the Apple menu? To find out I booted back into my Vanilla install, and typed it into the terminal. I got the exact same problem as before. The machine shut down, and after a brief delay, started back up again! So now I need to figure out why shut down works for my iPC disc, but not my vanilla install. I know that iPC uses the Voodoo kernel, so I hope that's not the answer, but I'll keep digging... UPDATE 2: I've solved the shut down issue. I changed PME Event Wakeup to [Disabled] in the BIOS. Now when I turn off the machine, it STAYS OFF! The bad news is that now sleep no longer works -- more specifically, the system doesn't wake up. Enabling PME Event Wakeup makes no difference, so the problem must lie elsewhere. I'll give it another half hour --if I can't figure it out by then, I'm just going to disable sleep altogether with Insomnia.kext. I've had sleep issues on some of my REAL MACS, so for all I know, it might not even be hackintosh-related.
  12. I think I've got a new one... When I shut down, my computer just restarts! The machine appears to go through the full shut down process; the case fans and drives all turn off. Then about two seconds later, the machine starts back up again. Shutting down from Windows works properly. Any ideas? I'm on F6 BIOS.
  13. Cool, thanks! I'll give it a shot. At one point, I actually suspected bad RAM, but your suggestion makes perfect sense. CONFIRMED: I pulled out a stick, and it installed fine. Since I'm only using the PATA drive for rescue/installation to a SATA drive, I'm comfortable with simply adding maxmem to my boot.plist
  14. I have a little problem myself: I keep getting kernel panics 85% of the way through the installation. Here's what I've done: I have AHCI enabled in both places in the BIOS. I installed Kalyway 10.5.2 to an old PATA drive, and made an image of my retail 10.5.6 dvd, and downloaded the 10.5.7 update. I also downloaded the files from this guide, and ran the patch script. I formatted the target drive in Disk Utility using GUID, and then ran the script. I chose Chameleon RC1 for my boot loader. For the installation itself, I've tried un-checking everyghing but the base system, but even this does not work -- still panics. I'm at my wit's end! Could my retail disc be too new? Could my Kalyway disc be too old? Is it the fact that I'm trying to install from a PATA drive to a SATA drive? What could possibly be causing this!? I'm in the process of downloading a newer kalyway disc (10.5.6) as we speak, so I'll report back then. Also, I admit I skipped the disk verification that occurs during installation (because the mounting verification turned out ok). So I'm going to sit through both verifications this time, and see if it helps. If anyone has any other ideas, be sure to let me know! Thanks.
×