Re: Unresolved symbols on networking modules

[Peter Berlau <pberlau@muenster.de>]

Hi Curt,

On Thu, Nov 12, 1998 at 08:54:50PM -0600, Curt Daugaard wrote:
> I've seen posts to this list about this problem before, but I
> can't recall the solution.  I'm trying to revive an ip
> masquerading setup I had in the past, but when I try to start it
> up a get a long list of unresolved symbols on the net modules.
> The modules were made and installed after the last kernel compile.
> Can anyone give me any clues about how to fix this?
OK: You have to configure the modules out with
    (*) 
	cd /usr/src/linux
	should a link to kernel-path
You have a /usr/src like this(?)
drwxr-xr-x   3 root     root         1024 Nov  3 14:04 kernel-headers-2.0.35
-rw-r--r--   1 root     src        662122 Nov 10 04:04 kernel-image-2.0.35_custom.1.0_i386.deb
drwxr-xr-x  16 root     root         1024 Nov 11 16:33 kernel-source-2.0.35
drwxr-xr-x   3 root     root         1024 Nov  2 03:55 liblockdev-0.9
lrwxrwxrwx   1 root     src            20 Nov  3 16:25 linux -> kernel-source-2.0.35
lrwxrwxrwx   1 root     src            20 Nov  3 14:19 linux-2.0.35 -> kernel-source-2.0.35
drwxr-xr-x   7 root     root         1024 Nov  2 03:53 redhat
	make xconfig,  or make menuconfig, or make config
	<M> is the modular setting, after saving the new 
	systemmap now You have to build the kernel
The 2 Ways to build kernel after (*)
traditional:
make dep clean
make zImage (or if kernel exceeds 512 KB make bzImage)
make modules make modules_install
depmod -a
make zlilo

the up-to-date-way: e.g.
make menuconfig
make-kpgk clean
make-kpgk --rootcmd fakeroot --revision=custom1.0 kernel_image
dpkg -i ../kernel-image-2.0.35_custom.1.0_i386.deb
this is the preffered method You have installed the modules
and called depmod -a automatically.

Before You can do this You must install the kernel-package,
get it from debian via ftp search in development-package

-- 
cheers
   Peter