Unresolved (module) symbols at boot time

Subject: Unresolved (module) symbols at boot time
From: Edward Lewis (lewis@tislabs.com)
Date: Wed Feb 14 2001 - 12:33:49 MST

I built a new kernel (details below), and when I boot it, I get a bunch of
messages like this (from /var/log/messages):

>depmod: depmod:
>depmod: *** Unresolved symbols in /lib/modules/2.2.17-0.6.1/net/8390.o
>depmod: depmod: *** Unresolved symbols in
>depmod: depmod: *** Unresolved symbols in

What can I do to resolve the symbols? The full list of files involved
(written this way to avoid line wrapping):

/misc/ip_gre.o, ip_masq_autofw.o, ip_masq_mfw.o , ip_masq_portfw.o, ipip.o
/pcmcia/3c574_cs.o, 3c575_cb.o, 3c589_cs.o, epic_cb.o, fmvj18x_cs.o , ftl_cs.o
/pcmcia/memory_cs.o, netwave_cs.o, nmclan_cs.o, pcnet_cs.o, smc91c92_cs.o
/pcmcia/tulip_cb.o, wavelan_cs.o, xirc2ps_cs.o

The details:
Platform is a 1999 Powerbook (Wall Street), dual booting MacOS8.6 and
Linux. (I had LinuxPPC 2000 on it, but couldn't get IPv6 to work.)

The new kernel was built cheifly to add IPv6, I did add a bunch of other
networking features. I don't recall adding any pcmcia support. The kernel
boots, IPv6 seems to work inspite of the messages.

I updated the vmlinux and system.map in / and the vmlinux is in the right
MacOS folder.

Edward Lewis NAI Labs
Phone: +1 443-259-2352 Email: lewis@tislabs.com

Dilbert is an optimist.

Opinions expressed are property of my evil twin, not my employer.

This archive was generated by hypermail 2a24 : Wed Feb 14 2001 - 12:35:24 MST