Jump to content


  • Content count

  • Joined

  • Last visited

About man_bites_dog

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  1. DSDT Auto-Patcher

    I don't get it? Do you mean I should replace PCIB with that Hex above? I'll take a pic of the KP when I get a chance. Thanks
  2. DSDT Auto-Patcher

    Hi Maldon My quest for sorting out my Sabertooth X58 continues... I have attached my DSDT for you to have a look at as I'm having issues and I really don't know how to edit / modify the DSDT. I don't understand the layout of DSDT's and the syntax of how one declares methods and devices. I wish there was a noob's guide to DSDT (can someone please write one up?) Issue 1 is Firewire: I've worked out that is must be a power management issue that's causing it not to work correctly. If I put the computer to sleep, then awaken it, then my firewire drive comes to life. I've tried editing my DSDT with DSDTSE and using this code: Firewire power conservation Hack. It´s a nice idea to change all your firewire names on DSDT to apple´s ones, for example from FIWI to FRWR. Locate Scope (_GPE), add this on the end. Method (_L1A, 0, NotSerialized) /* <-- Added for firewire */ { Notify (\_SB.PCI0.PCIB.FRWR, 0x00) Notify (\_SB.PWRB, 0x02) } Locate your Firewire device (or create it with this code if it doesn´t exist) Device (FRWR) /*Add all this code if you don´t have firewire device on DSDT*/ { Name (_ADR, 0x00070000) Name (_GPE, 0x1A) Method (_DSM, 4, NotSerialized) /* Add from here if you already have a firewire device on dsdt*/ { Store (Package (0x02) { "fwhub", Buffer (0x04) { 0x00, 0x00, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } /* End of code if you just add to a existing firewire device */ } I couldn't find Scope(GPE), only Scope (\_GPE). I modified that and added the Device and got a compile error: 4518: Notify (\_SB.PCI0.PCIB.FRWR, 0x00) Error 4064 - Object does not exist ^ (\_SB.PCI0.PCIB.FRWR) Secondly I have an issue with NullCPUPowerManagement.kext. If I delete it from /Extra/Extensions, then I get a kernel panic. Is there an issue in my DSDT causing this? Is it better to use NullCPUPowermanagement or DSDT? dsdt.aml.zip Thanks in advance for all the help. Cheers ManB
  3. Firewire issues

    Hi all I'm a DSDt newb and have been trying unsuccessfully to install the firewire hack code into my DSDT. Is there a good place to learn DSDT editing? Any help appreciated. Thanks
  4. DSDT Auto-Patcher

    Maldon, I have read the post you linked before and was how I fixed firewire on my old q6600 setup. However, I thought your DSDT edits fixed IRQ conflicts. I'll try it out and let you know. Regarding the eSATA, well, it seems the Marvell chip is just not sorted currently. Hopefully someone will find a way around it.
  5. DSDT Auto-Patcher

    Hi Maldon Thanks for all the great work, really appreciate it. I'm trying to solve a problem with my Asus Sabertooth install that's driving me nuts. Here's my config: Board: Asus Sabertooth x58 Ram: Corsair 3 x 2gb GPU: Nvidia GTX 280 CPU: i7 950 Custom DSDT with HDEF Audio edits /Extra/Extensions= ALC8xxHDA, FakeSMC, IOAHCIblockStorage, Jmicron36xATA, Jmicron36xeSATA, NullCPUPowermanagement, Sleepenabler I used your tool to generate my DSDT and apply patches. I've got it 90% perfect, but firewire and and esata just won't seem to work. I've tried searching everywhere for a fix and the only thing I found was a conversation you had with someone else in Portuguese I had to google translate - he also had the same problem with eSata. For the eSata problem I have tried the following: 1: Installed the Jmicron36xxx kexts 2: Played with every BIOS setting that has to do with AHCPI Could this be because the eSata port on this drive is part of the Marvell bus? For firewire, I have tried the following: 1: I tried to add the Firewire power scheme hack to my DSDT, but couldn't get it to compile. I don't know enough about DSDT editing to do this properly. The system profiler sees there is firewire, but when I connect a firewire drive, nothing happens. I know from a previous Hackintosh install that sometimes there are IRQ conflicts with the SATA, USB etc that can cause the firewire BUS not to get an IRQ and therefore it doesn't work. Could this be the case here? Also, if I try to delete NullCPUPowermanagement, I get a crash on startup and it won't boot. I'm sure I've read that I shouldn't need that kext. Thanks in advance. ManB
  6. I'd follow MaleorderBride's advice, especially with your voltages. I'd also like to add the following though as I had a similar problem with fluctuating benchmarks. Make sure you're using the correct DSDT. Use the one Maleorderbride posted a while back. Also make sure your power management settings in your BIOS are all on. When I initially set up my overclock, I disabled all the power saving features and this I found to be the cause of different geekbench scores. Also set your RAM voltages manually. This is a snapshot of my Geekbench score now, which is 99% consistent (variance is negligible). I'm using Maleorderbrides EXTRA folder, and I installed via the [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] Method which worked flawlessly. My specs are: CPU: i7 950 RAM: 6 gigs Triple Channel Corsair XMS 3 GPU: Nvidia GTX 280 If anyone wants to follow the guide I followed to install, here is a link to the readme: guide.txt This has both an [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] method (I used this method) as well as a Kakewalk method (which I hear is good too) Let me know how you all get on. Later
  7. Hi Maleorderbride (always weird typing that!) I can report success regarding getting all 4 of the CPU temps working. I've even got Northbridge and Heatsink temps! Here's how. Check this post here: http://www.insanelymac.com/forum/index.php?showtopic=234452# It's the Hardware Sensors Project which uses a modified version of FakeSMC (based on Slice's hard work). I tried this before with no luck and only last night worked out why it wasn't working. I've attached the compiled kexts in case anyone gets confused. They need to be installed in either E/E or S/L/E. I have them in E/E - better management I think. The trick to getting it working was ditching the Nvidia GPU temperature kext - it caused all kinds of problems and I don't really care about GPU temps: maybe someone else in here will get it working with their card - my BFG GTX 280 didn't like it. There are also reports that putting the kexts in S/L/E can yield better results, but since we've all got the same motherboard and (hopefully DSDT's) you shouldn't need to install them there. If it works for me I don't see why it shouldn't work for everyone else. WARNING: DO NOT INSTALL "NVCLOCK.KEXT" first time around - it may cause issues. You can mess around with it once you know everything's working. If you get kernel panics, it's because of this Kext. Install and go to iStat preferences. Check out the Sensors section and you'll access to a whole lot more! Let me know how it goes. later HWSensors_latest.zip
  8. Maleorderbride Thanks for the speedy response. I've installed your kexts and now get an "Ambient" temp. reading in iStat. I've got this far before but thought it wasn't quiet right as it seemed a little low compared to my Windows7 Coretemp readings. Also, there's only 1 core. I've been reading in other posts of people managing to get all cores showing as well as the GPU temp. However, as soon as I go down this route I KP. What are you getting in iStat? Same? Re my overclock. I'm running 1.38 Volts to the CPU and it's rock solid in Win7 running Orthos and Prime95 (a little hot, but hey, these i7 suckers are not like the Q6600's!). RAM is running at close to 1600 and QPI is 2x RAM. Benchmarking in Win7 seems fine - it's only a problem in OSX - particularly when turning off all CPU power saving. I don't like using power saving when OC'ing as it can cause stability issues. However, I won't be running my rig at 4.01 all the time, more likely 3.6 as I like the lower coretemps better. I'll experiment some more and try with all power management enabled. I'll let you know. Cheers, and thanks again for all your help.
  9. Hi Maleorderbride (and everyone else that's contributed to this very helpfull thread) I'd like to find out a few things that have been troubling me with my install. Here we go. My Specs: CPU: i7 950 RAM: 6 gigs in triple channel mode GPU: Nvidia GTX 250 1gb Motherboard: EX58-UD3R REV 2.0 with FB Firmware My system is rock solid and I get a Geekbench score of 10318 running your (Maleorderbride's) DSDT and com.Apple.Boot.plist. I also have the exact same E/E folder structure. However, not wanting to be too greedy, I've noticed that if I tinker in my BIOS, my Geekbench scores drop dramatically. If I overclock my CPU to 4.01 GHZ, my geekbench actualy drops! To 7338. In fact, if I turn off some of the CPU specific power saving features in the BIOS such as EIST etc, it also dramatically drops geekbench results. The question is, how does the DSDT effect the CPU power saving modes encoded in the BIOS? Do we need to change the DSDT so that modified BIOS settings don't effect CPU performance? I'm lost here. Second question has to do with Temperature readouts using iStatMonitor. Using your packaged FakeSMC.kext, I get no joy with CPU temps displaying in iStat. I've tried using the latest FakeSMC builds by Netkas - but they give me kernel panics at boot. I think I've tried about 5 different FakeSMC's with no luck. Has anyone here managed to get iStat working properly, showing GPU and CPU temps? I find it really useful having a temp monitor in OSX especially since I'm experimenting with overclocks all the time. If anyone has, please could they point me to the correct FakeSMC.kext. Thanks
  10. Hi All Does anyone have an alternative DSDT for an FB Bios than the one found on TonyMac? I tried his DSDT but my geekbench scores halved. Very strange. Anyone else had the same issues? Everything works perfectly, but I want to see if I can get a near prefect DSDT and have no idea where to begin. My set up: GA-X58A-UD3R **rev 2.0** with FB Bios 6 gigs Ram i7 950 CPU NVIDIA BFG GTX280 GPU
  11. Avid Machine ID

    For all those still struggling to get their machine ID, I was a bit vague on how to fix this problem, but I thought you might have been brave enough to figure it out yourselves. This .plist fix: <key>EthernetBuiltIn</key> <string>Yes</string> DIDN'T WORK for me either. I had to do it the long way around. Like I said in my first post, you're going to have to USE EfiStudio or OSX86Tools to fix this properly. You may also need to find the right Kext for your Network card so it's recognised. I used EfiStudio. Open it and choose "Select Device". Choose Ethernet. Click, "add device". On the window that pops up, choose "Save as XML". Save it somewhere like ethernet.plist. Open the new ethernet.plist file you've just made (I use Plist edit pro or you can use Textedit). You should have something that looks like this: <key>PciRoot(0x0)/Pci(0x1e,0x0)/Pci(0x4,0x0)</key> <dict> <key>built-in</key> <string>0x01</string> <b>DON'T USE THIS ONE, THIS IS MINE AS AN EXAMPLE AND YOURS MIGHT/SHOULD BE DIFFERENT!</b> Copy this into your com.apple.BOOT.plist file located in the /Extra folder in the root of your drive and NOT in the other one found in /Library/yadyada.... Reboot. Check "About this mac, More info". If you see in the "Ethernet" section of the system profiler your ethernet card, then you'll be fine. If not, you're in trouble and it won't work. Also make sure you have the correct kext for your card. Check Kexts.com. Hope this was more informative. later
  12. Avid Machine ID

    Had the same problem and fixed it. You'll need to add your Ethernet card to your com.apple.Boot.plist in your Extra's folder. Use OSX86tools or EFItools to create the string neccessary and copy it into your .plist file. Later
  13. How do I install new EFI eg. Chameleon.

    When you say you updated the Kernel, what exactly are you referring to?
  14. How do I install new EFI eg. Chameleon.

    Searay, thanks for your response and help, it's really appreciated. I've succesfully installed the new Chameleon EFI and patched my DSDT! Now I'm thinking about taking the leap and installing 10.5.6. What do you think? Is it safe? Thanks again MBD
  15. Hi all I have a Kalyway 10.5.5 install perfectly set up. I know I shouldn't mess with it, but I'd like to use the boot options that the new Chameleon EFI offers and also try to update to 10.5.6. How do I go about "updating" my EFI to the Chameleon one. I'm too cautious to just install it and see what happens - I really don't have the time or energy to re-install a perfect setup. I've scouredt his forum and other sites trying to find info on how to go about this but to no avail. Please help. Thanks