Jump to content


  • Content count

  • Joined

  • Last visited

About svsmurf

  • Rank
    InsanelyMac Protégé
  1. The drivers have changed with 10.9.5 again. I had been using a binary patched version for quite some time which now started refusing to load with kxld[com.apple.iokit.AppleBCM5701Ethernet]: The following symbols are unresolved for this kext: kxld[com.apple.iokit.AppleBCM5701Ethernet]: __ZN11IOPCIDevice17setTunnelL1EnableEP9IOServiceb kxld[com.apple.iokit.AppleBCM5701Ethernet]: __ZN14IOPMrootDomain20claimSystemWakeEventEP9IOServicejPKcP8OSObject I found a Clover patch here http://www.hackintoshosx.com/files/file/4215-kextstopatch-clover-broadcom-bcm57781-for-mavericks-1095/ that I have applied to the 10.9.5 kext. The kext is attached here, if anyone else needs it. IONetworkingFamily.kext 10.9.5.zip
  2. BadAxe2/Q6600?

    Works great for me too, easy to OC, even with the standard heatsink.
  3. Widescreen resolution on atix1300

    There may well be another solution to this, but an easy way to add your desired resolution is installing SwitchResX.
  4. One of the changes I've noticed can be seen in Activity Monitor, if Leopard is running 64 bit the total size of virtual memory is well above 4 GB, something that's only possible with a 64 bit CPU. I've yet to find one of the bundled apps that's actually running 64 bit code though. So far it looks like the apps are compiled for 32 bit and just get a larger address space, although I'm not sure what the benefit of that would be. XCode 3 will easily generate 64 bit code and it executes just fine. Something you can play with if you're a bit technical. The "arch" command can also be used to make sure it's actually selecting the 64 bit code path when executing an app.
  5. BrazilMac Leopard Installation

    Yeah BrazilMac's patch works great here too :-D As for booting Leopard after having installed you need to put the bootloader on the partition manually, see http://forum.insanelymac.com/index.php?sho...rt=#entry486027
  6. Can't boot Leopard

    -Sandro-'s suggestion is probably the easiest, although I've just tried running dd and startupfiletool in the DVD Terminal without problems. I'm not sure why you guys can't. Maybe you're not cd'ing to the files/i386 dir?
  7. Neither Leopard or Tiger will run

    I see you're using an X1600 series card. These usually only work if you connect the screen using a DVI2VGA adapter instead of connecting the screen directly to DVI. Same thing you're describing happens with my system if I connect my monitor directly to DVI.
  8. Can't boot Leopard

    Really? You can't run the startupfiletool from the DVD terminal? I don't see why not, it's included in the patch package you have, so it should be on your USB key. Remember to write ./startupfiletool if you've cd'ed to the files/i386 directory. Right, that should actually work (at least if by upgrading you mean upgrading without formatting the partition, but I think you do.) Yep I have the tiniest spare OSX installation that I use for testing upgrades, kext's etc before applying them to my main installation. If anything goes wrong I have a cloned copy of this test installation I can reapply in minutes and then play with again. And it was rather handy when installing Leo
  9. Can't boot Leopard

    I don't think upgrading from Tiger is likely to work either, you will still need to run the post patch, which you can't without access to a working OSX. You mentioned you have BrazilMac's patch on a USB key, can't you access this from the DVD Terminal and run the patch/install the bootloader that way? That should be fine as a "working OSX" I guess. The guide are the two RTF's included with the patch, you should have all you need already.
  10. Can't boot Leopard

    The BrazilMac guide assumes you're post patching from your old Tiger installation. I meant the Tiger terminal, but I suppose you'll have to do it from the Leopard DVD terminal if you don't have Tiger anymore. The startupfiletool command is included with the BrazilMac patch in 9a581-patch/files/i386/
  11. No your problem seems to be different, if you get that firewire error I guess your boot loader is OK. Besides the bootloader fix, I changed the two lines in 9a581-PostPatch.sh that read PATCH="/files-post/" # path to the patched extensions LEO="/Volumes/Leopard" to PATCH="/Users/USERNAME/Desktop/9a581-patch/files-post" # path to the patched extensions LEO="/Volumes/Hackintosh" so that it matched my system and the patch would run properly. Note lack of trailing slashes.
  12. Can't boot Leopard

    Assuming you're using BrazilMac's patch and following the instructions to the letter, you'll have to run them using Terminal after post-patching. The i386 folder is in /Users/yourname/Desktop/9a581-patch/files/i386 If you do it right, it won't replace Grub. Make sure you are writing to the right partition, check partition names using "mount" for instance. If you write to the wrong partition you might indeed lose Grub or any other of your OS'es.
  13. Yes, that's exactly what I had to do too. No Tiger here anymore either.
  14. ATI X1600 PRO AGP Support for Leopard

    Ah. True
  15. Apple USB keyboards?

    They do, volume controls and disk eject too - at least the one I have (the generation before the ones you get now with the laptop keys). Using it right now to reply to your message on my OSx86 box It also works fine with Ubuntu and Vista in case you're wondering, although you might miss PrintScr etc.