Jump to content


  • Content count

  • Joined

  • Last visited

About blase

  • Rank
    InsanelyMac Protégé
  1. Any updates to this? Did touch-base ever release anything?
  2. GTX 285 only 1/2 the speed of GTX 260 in Cinebench

    If I delete AppleGraphicsPowerManagement.kext, my gtx285 is no longer throttled. Galaxies.app benchmark shoots from 85 to 307. But eventually the card overheats due to no fan control. Any solutions?
  3. I have an Agere FW3227 firewire which doesn't want to work. On boot I see: FireWire runtime power conservation disabled. FireWire (OHCI) Lucent ID 5811 PCI now active, GUID 001e8c0001ce3a31; max speed s400. ERROR: FireWire unable to determine security-mode; defaulting to full-secure. On shutdown I see: FireWire (OHCI) Lucent ID 5811 PCI: no valid selfIDs for more than 3 minutes after bus reset AppleEFIruntime.kext is loading, AppleHPET.kext is not affecting anything, and I'm on Chameleon RC3 which doesn't have the /option issue. My vanilla snow leopard install consists of an EFI boot partition with Chameleon RC3, and an smbios.plist containing my UUID. /E/E contains a UUID.kext with the same UUID (made with the mac address of my EN0). Any ideas?
  4. It seems the patcher generated dsdt.aml is disabling my firewire on my i7 system which is otherwise fully operational in vanilla 10.5.7. Removing dsdt.aml breaks the machine unless I disable hypertheading and multi-cores. Is there a way to remove it using boot flags or otherwise and still get all my cores working? Alternatively can the dsdt.aml be further modified to correct whatever is breaking firewire? Thanks!
  5. I'm on the P6T WS Pro board, and have everything up and running except for firewire (LSI Agere FW3227 chip). It seems the DSDT.aml is messing that up. But I can't remove the dsdt.aml without removing hyperthreading and all cores. Is there a way to either modify the dsdt.aml to not interfere with firewire, or remove it and still enable hyperthreading?
  6. DSDT Patcher

    Does a change in hardware require a new DSDT?
  7. Yes, I think an smbios came with chameleon, or possibly from elsewhere along the process. Geekbench, system profiler, and terminal all report bus at 600. I'm only concerned if it affects system performance.
  8. My bus and memory speed are a third of what they should be (1850 DDR3 reporting as 667 DDR2). Is this just a reporting problem, or is my system actually running at a comprimised bus speed?
  9. I solved this on the P6t by enabling both network adapters in the BIOS. It still took about 10 minutes to boot, but it got me through to the account setup screen.
  10. What would happen if I simply plugged in a clone of my current hard drive (running 10.5.6 with the 9.6.0 kernel) into a new X58 system? Assuming I pre-copied the necessary kexts in place of course. I'm guessing this wouldn't work, because people aren't talking about doing it. But I'd like to know specifically where the problem would be. Alternatively, if I built a fresh install and then did a "migrate" to copy my system over, would that work without a problem?
  11. Cannot turn AirPort on

    Solved my problem as well (the stupid toggle button on the side of the laptop), thanks!
  12. Marvell Yukon 8001 - the driver

    I have the same motherboard, and mine would kernel panic when I updated to 10.5.6 and had the skge.kext loaded. It would give me a panic report of a conflict with IONetworkingfamily.kext, etc.. After about a weeks worth of troubleshooting, I solved the problem by removing the dsdt.aml I had generated and installed pre-update, and replacing AppleHPET.kext with the 10.5.5 version. (This was solved by accident, as I was replacing the HPET to fix my firewire.) Hope this saves someone some headaches!
  13. Did you ever find a solution?
  14. Did you ever find a solution?
  15. Slow Firewire Drives

    I'm running into the same problem. I have the ADS pyro PCI fw800 card (cheap), which I'm getting similar speeds on (40 write, 24 read). I bought the Sonnet Tango 800 Express to replace it. $100, PCI-e. It only got 24 write, 24 read. I called the tech support team and they told me all the companies are using the same TI chipset, and that there's a bottleneck that happens in the PCI-e itself. That explains why I get good write speeds with the PCI card instead.