| Previous | Next |
| kIOUSBUnknownPipeErr | kIOFireWirePending |
kIOConfigNoEntry
A valid lookup can still have no matching entry
kIOConfigNoEntry is the FireWire-family status for a Configuration ROM lookup that found no requested entry. This differs from kIOFireWireConfigROMInvalid: here the operation can reach the lookup stage, but the key, directory, unit, or other requested item is absent from the ROM data visible for the node.
Configuration ROM content identifies device and unit information on an IEEE 1394 bus. A bus reset can change node identity and causes clients to reconsider the current bus generation, so stale ROM pointers or cached directory positions should not be reused as proof that an item must still exist.
Capture the lookup context
- Keep the node GUID, bus generation, raw ROM image or its digest, and the exact key/directory/entry requested.
- Distinguish a missing entry from an invalid ROM parse before changing cable or power hardware.
- Refresh device information after reset or reconnect rather than relying on a prior node ID or unit directory offset.
- Do not substitute a guessed ROM entry; device-class or unit binding must be based on the descriptors actually present.
References
- Apple: IOFireWireFamilyCommon.h
- Apple: IOFireWireDeviceInterface
- Linux kernel: FireWire driver interface guide
Looking for a different code? Search another status or error code.