Re: dyld returns 2 when loading AppleHDAHALPlugIn
Re: dyld returns 2 when loading AppleHDAHALPlugIn
- Subject: Re: dyld returns 2 when loading AppleHDAHALPlugIn
- From: Jeff Moore <email@hidden>
- Date: Thu, 13 Jul 2006 14:43:02 -0700
The log message means that, for whatever reason, the plug-in that the
built-in hardware uses with the HAL isn't getting loaded. It could be
because it isn't fat (end users have a myriad of ways to thin what
gets installed, usually in a vain attempt to save disk space), but it
could just as easily be because of disk corruption.
At any rate, my guess is that the log message has nothing to do with
anything this user is experiencing. The failure to load the plug-in
is not fatal. Further, failure to load the plug-in for the built-in
hardware has no impact on the MotU hardware.
So presuming your user has a uncorrupted system installed, I think
you are chasing a red herring with this log message. What you need to
do is look at the "crashes and buggy audio behavior" and try to
explain what each of them is about. From there, you can start to see
if they are all the same crash, or a cluster of related crashes, or
just random. That should help you determine the commonality and lead
you to the source.
On Jul 13, 2006, at 1:21 PM, Christopher Ashworth wrote:
I have a user on an Intel machine that is connected to a MOTU
828kii. He is on OS 10.4.7 and is using the most recent Universal
drivers, v1.4.1.
He is experiencing some crashes and buggy audio behavior that
appear to be related to the being connected to the MOTU device
(they have so far always disappeared when disconnecting from the
MOTU).
In his console log, during startup, he gets:
2006-07-13 14:16:42.446 QLab[341] CFLog (21): dyld returns 2 when
trying to load /System/Library/Extensions/AppleHDA.kext/Contents/
PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn
repeated several times.
What does this mean? (I haven't been able to find a definitive
description of this error code anywhere, just vague discussions of
it possibly meaning that the code is not Universal--which seems
weird, coming from an Apple bundle....)
FWIW, later there are some errors logged to the console from my
code concerning a kAudioUnitErr_InvalidPropertyValue error
occurring in the following call:
// Set the output device of _outDeviceUnit.
err = AudioUnitSetProperty( _outDeviceUnit,
kAudioOutputUnitProperty_CurrentDevice,
kAudioUnitScope_Global,
0,
&deviceID,
sizeof(deviceID));
Which I assume is connected, although my assumptions have bitten me
on this list before.
Any insight on this?
--
Jeff Moore
Core Audio
Apple
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden