Apogee Ensemble (Firewire) crackles after update to 10.5.8: Firewire Full-Secure Mode!

[sirdemonbrown]

hey!

 

i just did a major jump from Leo4All v3 - 10.5.2

to iDeneb Combo 10.5.7 upgrade.

 

i have a P4 530 3 ghz chip in an ASUS P5WD2 Premium board.

i've experimented with both AnV's 9.7 kernel and Qoopz Voodoo based 9.7.

both seem to work fine. i have not experienced any kernel panics, etc.

 

the one thing i have noticed is that i am getting pretty terrible digital crackles

from my Apogee Ensemble pro audio device. It is connected via firewire.

it worked flawlessly before.

 

any ideas?

 

thanx!

sir demon

[sirdemonbrown]

updated to 10.5.8 with the iDeneb Combo 10.5.8 updater.

using Qoopz 9.8 kernel. my system feels very zippy now!

 

but i still have the crackles!

[sirdemonbrown]

after snooping around the last couple of days, i have figured out that the problem lies with this error:

 

"ERROR: FireWire unable to determine security-mode; defaulting to full-secure"

 

i have tried the following:

 

installed Chameleon 2.0 RC2

installed AnV's AppleSMBIOS.kext

installed AnV's 9.8 kernel

bought a PCIe firewire card with a Lucent 5091 chipset.

found out my motherboard firewire chip is a TI 8023.

 

still no progress!

[mentorek]

after snooping around the last couple of days, i have figured out that the problem lies with this error:

 

"ERROR: FireWire unable to determine security-mode; defaulting to full-secure"

 

i have tried the following:

 

installed Chameleon 2.0 RC2

installed AnV's AppleSMBIOS.kext

installed AnV's 9.8 kernel

bought a PCIe firewire card with a Lucent 5091 chipset.

found out my motherboard firewire chip is a TI 8023.

 

still no progress!

 

 

 

 

You have to be able to use all EFI/NVRAM kexts (watch out for Disabler.kext).

 

I got rid of this error message but still had firewire issues using TI chipset, and kernel_task process was using much more CPU time when using firewire equipment.

 

cheers,

 

mentorek