Mac OS X on x86 Hardware 2008–2024 Technical Archive
InfiniteMac OSx86 › OSx86 Core & 10.X › Apogee Ensemble (Firewire audio) crackles after update to 10…
3,231 reads · 2009-08-16 – 2009-08-18
Note 10.X Core

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

i am getting pretty terrible digital crackles from my Apogee Ensemble pro audio device. It is connected via firewire. it worked flawlessly before. i just did a major jump from Leo4All v3 - 10.5.2 to iDeneb Combo 10.5.7 upgrade. after…

Primary Author
@sirdemon Published 2009-08-16
Collection
OSx86 Core & 10.X
Archival Footprint
3,231 historical reads · 0 curated field notes (from 2 dispatches) · 2009-08-16 – 2009-08-18
Credited Voices (1)
@sirdemon (2)

i am getting pretty terrible digital crackles from my Apogee Ensemble pro audio device.
It is connected via firewire. it worked flawlessly before.

i just did a major jump from Leo4All v3 - 10.5.2
to iDeneb Combo 10.5.7 upgrade. after experiencing audio problems,
i decided to update to 10.5.8 using iDeneb's 10.5.8 updater.
i am now using Qoopz 9.8 kernel which i have to say has made my
system very zippy! but alas, my problem still exists.

i should note that during the boot process i get this message:
"FireWire unable to determine security-mode; defaulting to to full-secure"

i have a P4 530 3 ghz chip in an ASUS P5WD2 Premium board. Intel 955X chipset. TI 1394a firewire chip.

do i need to do some .kext fiddling? i haven't changed any kexts
since updating from 10.5.2 > 10.5.7 > 10.5.8

thanx!
sir demon

Author Updates & Technical Revisions

Follow-up dispatches by @sirdemon

Author Update #1 @sirdemon 2009-08-18

update:

i tried using AnV's AppleSMBIOS.kext, but to no avail.

my motherboard's firewire chip is a TI 8023.
today, i bought a Lucent 5091 PCIe board to see if that would work.
same result.

i also tried AnV's new 9.8 kernel.
and i've installed Chameleon 2.0 RC2.

i can't seem to change my macmodel info.
i've set it to MacPro3,1 in com.boot.Apple.plist
it still boots saying my system is MacBookPro5,1
using AnV's -nomacmodeloverride switch,
it comes up as MacBook2,1. dunno, if that makes a difference anyways.

thanx for reading!
becoming despondent...
sir demon brown

Sources & Contributor Provenance (1 credited usernames · Thread #3669)
UsernameDossier ContributionDispatchesActive Window
@sirdemonPrimary Author22009-08-16 → 2009-08-18