Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

  1. Random Lock Ups

    Thanks for the reply, I read up about webkitpluginhost and it does seem people are having problems with it, and thought that may be the cause of the lock ups (although I couldn't find anyone who had experienced lock ups related to it, they were all getting temporary freezes). Everything has been running smooth for a couple of days, but then this morning it locked up again about 5 minutes after a cold boot. I turned my hack on and left the room and came back and it had frozen. I noted the time on the system clock and when I rebooted checked through all the logs I could but there was nothing within 3 minutes of the lock up in any of them So I'm a bit stuck here, I don't know how I am going to fix this if I don't know why it's happening...can anyone recommend me a diagnostic tool that I could use? Is there a log file somewhere that I don't know about that can tell me more? Really would like to get this fixed as it seems to be at random and could cause problems if it strikes at the wrong time! Thanks
  2. I have just got my first full lock up on a fresh Snow Leopard install. I had them on my Leopard install and is one of the reasons I upgraded the OS. This one happened when viewing a Youtube clip in full screen, and this happened also with my Leopard install at least once. It's not just when viewing full screen video though, it has happened when listening to music as well. The system fully locks up, and if there is sound playing it glitches continuously. I've checked the system.log at the exact minute the lock up happened and the only entry is as follows: Aug 1 17:11:10 John-Smiths-Mac-Pro WebKitPluginHost[174]: Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz. Aug 1 17:11:10 John-Smiths-Mac-Pro com.apple.WebKit.PluginAgent[173]: 2010-08-01 17:11:10.776 WebKitPluginHost[174:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz. I don't know if this is what's causing it or not, but looks unlikely. Anyone got any idea what might be going wrong? Is there any logs I should be checking?
  3. DSDT editor and patcher

    I managed to get my SL firewire working, it appears the dsdt that i was saving from the windows version wasn't working properly. it seems saving was intermittent, it wasn't clear whether i should save my edited dsdt file using the 'AML' menu or the 'Load' menu, I tried both, but I could only save using the 'Load' menu. If i tried to save using 'AML' menu then no file would be created in my chosen output folder. I ended up realising that a dsdt.aml got created in the same directory as the DSDT Editor application when I clicked on compile, and so I took this dsdt and used it to boot my SL installation, and my firewire is now working! I don't know whether this is a bug or I just used the application wrong, but maybe a small pdf file explaining the process would help others not to make the same mistake as me. In any case, thank you for making a great little app, it made patching my dsdt very simple. Now sleep doesn't work properly, it seems to sleep the computer but when I wake with either the mouse or the power button, the computer reboots. Does anyone have an idea what i can do to fix this? I tried the patches included and also the ones uploaded specifically for gigabyte boards on page 3 but neither has seemed to work. update : sleep issue was fixed by ticking the bottom option in energy saver panel as shown in the image here http://bit.ly/d5rmkI i think i am fully operational now, woohoo!
  4. DSDT editor and patcher

    Update : This is now solved, see my next post... Hi, First of all thanks for the great work on the patcher, it's a great way for beginners like me to experiment with DSDT editing and hopefully learn a thing or two. I hope someone can help me with some post-installation issues I'm having: I installed SL using Kakewalk 2.2 (http://puru.se) with the Gigabyte EP45-DS3L settings, which worked ok in enough that it installed and I could boot to the OS. This method uses Chameleon boot loader. 2 things which didn't work were sleep which I'm not fussed about and my Texas Instruments PCI firewire card (which worked fine in Leopard out of the box). I decided to try and get this all working by editing my boards own dsdt and getting rid of the one supplied by Kakewalk. I got my dsdt using the Windows 7 version of Dsdt Editor and fixed 3 errors and 1 warning so it compiled properly. I have attached this file DSDT_errors_fixed.aml in the zip. The untouched one is DSDT_untouched.aml in the zip. My installation will not boot with my dsdt like this, I do not get a KP but after the grey Apple screen I just get a blank screen, and in verbose mode I do not get any errors that I can see, but again it goes to the blank screen. At first I thought it was the graphics but these are enabled in the com.apple.Boot.plist file (also attached in the zip). The graphics work fine using the dsdt supplied with Kakewalk, so I guess there is some difference that is stopping me from booting fully. I began to patch my dsdt using Dsdt Editor, but even after applying all the patches relevant to me (DSDT_mine_patched.aml in zip), I still cannot get to the desktop, so I am at a bit of a loss as to where to go from here. Does anyone have an idea about why I am getting this blank screen? Is there another debugging method I could use to find out? As I need to get the firewire working to use my sound card, I decided to patch the Kakewalk dsdt that boots to the desktop ok (DSDT_kakewalk_ep45_with_patches.aml), and I got sleep working (waking from sleep with mouse causes system to freeze after a couple of minutes, not sure whether it has locked up or USB stops working yet), as well as speedstep as far as I can tell, but firewire still doesn't. I've been doing a lot of reading on firewire issues and it seems people are having success by adding the device in their dsdt, see here : http://www.insanelymac.com/forum/index.php...l=firewire+dsdt. I have already tried moving the firewire card to other pci slots and also removing AppleHPET.kext (which caused KP), but neither worked. I get the following error when booting in verbose mode FireWire runtime power conservation disabled. (2) And console.log shows SPFWR ERROR: FireWire bus may be unstable. Other FireWire devices may be present. And system profiler shows unable to list firewire devices. I haven't tried any firewire dsdt fixes yet, as I would like to get my own dsdt working properly first, but some guidance on doing this would be very much appreciated. I have attached my ioreg and lspci -nn outputs in the zip as well, and also my smbios.plist file just for good measure! Once again thanks for the great tool you've made, it has really helped me get this far! x0b_dsdt_etc.zip
  5. That's what I did and it worked flawlessly. Typing this from RC2
  6. Ok I have got the card working again, not 100% sure how, but I'm sure it has something to do with Windows. It seems the problem stems from me trying to get the firebox to work on Windows 7 64-bit, as presonus are such a poor company they haven't provided a working 64-bit driver for this interface and I've been trying others' suggestions to get it up and running somehow... Anyway, through the continual un/installation of drivers in Windows 7, it seems to do something to the device, and when I reboot and load up OSX the firewire card and thus the firefox can't be detected properly. But, if I actually shut the PC down and turn everything off for a few seconds then boot into OSX, the card gets picked up and works ok. I'm still getting a very long pause while it seems OSX is trying to detect the firewire device, does anyone know if this can be reduced/removed? I seem to remember this happening on my macbook when it was plugged into the firebox at boot, although I'm not 100% on that. I also get the full secure mode warning when booting in verbose mode, although this doesn't seem to affect it working, can someone explain what this actually means please? Glad it's working again anyway!
  7. Hi there, I am having some problems with detecting my firewire card in retail vanilla Leopard 10.5.6 The annoying thing is, it was working ok up until yesterday, but now I get a red error message in system profiler (I can't remember off the top of my head exactly what it said, but it is to do with not being able to detect the card rather than detecting the card and a problem with a connected device). I bought this PCI card about 2 months ago - a Lacie FireWire 400 card designed by Sismo - http://www.lacie.com/products/product.htm?pid=11161 When it was working and if I had my Presonus Firebox audio interface connected, boot times would increase, in verbose mode I got a security mode error and wondered if this was anything to do with it taking so long to boot, but made do with it at the time. This is something I'd also like to erradicate if/when I get the card working properly again. I've tried moving the card to a different PCI slot but it still doesn't seem to detect it properly and I don't really know where to turn. I'm sure there may be a problem with one or more kexts I am running but any suggestions on where to go from here would be really appreciated. I've read a load of posts on here and elsewhere trying to decipher what might be happening, some people have mentioned trying to roll back the firewire associated kexts to tiger versions - is this a wise idea/necessary? Seems counter intuitive to me, but it if it works...I'm at work right now so will try out some stuff when I get home, but some direction from peeps here would be great The only thing I can think that may have unsettled the card or firebox is installing windows 7 the other day and trying to get the audio interfaces drivers for vista to work on windows 7. Since then I have used the firebox on my Macbook though and it worked ok, so I can rule out a hardware error with that. Any ideas? Cheers