Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > "No kernel dependency" message. What the hell does this mean?

"No kernel dependency" message. What the hell does this mean?
Thread Tools
Mac Elite
Join Date: Feb 2001
Location: Canaduh
Status: Offline
Reply With Quote
Aug 22, 2005, 01:38 AM
 
I've posted this problem at a couple of other Mac forums and haven't gotten an answer. It seems as if nobody has a clue about the underpinnings of OS X. It'd be nice if Apple actually published a guide explaining all the alarming and cryptic error messages that appear in the console or in single user mode. Anyway, I hope someone here can explain my "kernel dependency" message.

When I boot into single-user mode, I keep seeing a series of messages about "no kernel dependency."

Extension "com.apple.driver.initioFWBridge" has no kernel dependency.
Extension "com.apple.iokit.IOFireWireSerialBusTransport" has no kernel dependency.
Extension "com.apple.driver.Oxford_Semi" has no kernel dependency.
Obviously, the messages have something to do with the two Firewire hard drives I have attached to my iMac G5. Are these error messages? And what is a kernel dependency and why is it needed or not needed.
     
Baninated
Join Date: Dec 2004
Location: Illinois might be cold and flat, but at least it's ugly.
Status: Offline
Reply With Quote
Aug 22, 2005, 01:49 AM
 
Do you have Tiger? What version of the OS are you running?

Are you getting a Kernel Panic? Is the Drive working?

http://www.thexlab.com/faqs/kernelpanics.html
(Last edited by budster101; Aug 22, 2005 at 01:59 AM. )
     
Ω
Mac Elite
Join Date: Nov 2003
Status: Offline
Reply With Quote
Aug 22, 2005, 01:51 AM
 
How old are the FW drives?

Wondering if it might have something to do with the Oxford chipset or whatever the fsck they were talking about 3 years ago (when FW drives were being toasted when you connected them to your machine)

Just guessing, could be completely wrong (and most likely am).

Has googling turned up anything?
"angels bleed from the tainted touch of my caress"
     
Spliff  (op)
Mac Elite
Join Date: Feb 2001
Location: Canaduh
Status: Offline
Reply With Quote
Aug 22, 2005, 01:59 AM
 
Originally Posted by Ω
How old are the FW drives?

Wondering if it might have something to do with the Oxford chipset or whatever the fsck they were talking about 3 years ago (when FW drives were being toasted when you connected them to your machine)

Just guessing, could be completely wrong (and most likely am).

Has googling turned up anything?
Googling hasn't turned anything up that's helpful. Another person over at the Apple discussion forums had the same problem (he posted in July) but he never got a response. One drive is an EZQuest Cobra 120 GB and the other is a MacAlly USB 2.0/FW 400 drive.

I'm running Tiger on a new iMac G5. Interestingly, I never saw these messages on my old iMac G3 which was running Panther. So I don't know if it's a Tiger issue or a G5 issue. The Firewire drives seem to be working fine, but my console is generating an excessive number of weird and alarming messages. Here's another example:

"[HCIController][Start][AppleUSBHCIController][StopIsochPipeRead] - mInnt1IsuchInPipe = 0 -numReadsPending -0 [Start]1' "

If I disconnect all my usb devices, it still appears. I called Apple and they didn't know what is was but told me not to worry about it.

I just wish these messages were documented so we knew what they meant. In the days of OS 8 and 9, MacFixit.com was a useful resource but they've become useless in these OS X days.
     
Senior User
Join Date: Nov 2000
Status: Offline
Reply With Quote
Aug 22, 2005, 04:57 AM
 
This is a minor packaging problem with the kernel extensions (kexts) mentioned. This is a warning saying that the kext has no specific kernel modules mentioned in it's dependency list, so the kernel has decided that it depends on the default value (com.apple.kernel.libkern, version 6.0 or later).

There is nothing to worry about and you can safely ignore it.

For those who care, the message is emitted by figureDependenciesForKext in xnu/libsa/kext.cpp.

- proton
(Last edited by proton; Aug 28, 2005 at 03:17 AM. (Reason:Fix silly mistake))
     
Spliff  (op)
Mac Elite
Join Date: Feb 2001
Location: Canaduh
Status: Offline
Reply With Quote
Aug 22, 2005, 12:47 PM
 
Originally Posted by proton
There is nothing to worry about and you can safely ignore it.

- proton
Thanks, proton.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 12:46 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2