make-kpkg kernel doesn't install on other system

Hello all!

I tried to use Knoppix for the following task:

- make kernel packages running Knoppix 3.3 on my P4 for my debian router wich is a P120.

It's obvious why I got this idea, compiling a kernel on a P120 is a pain in the a**. So I downloaded the v3.3 built 22 Sep. 2003 and after that the latest kernel source which is now 2.4.22.

I used the old config file from my previous 2.4.20 kernel package and added some new features and most importantly the module for a faster NIC.

Well, I had no problems at all compiling and creating the packages but when dpkg I finally set up the kernel-image package on my server, I got loads of "unresolved symbols in... xyz" errors.

It seems as if debmod is unable to resolve symbols for my whole collection of modules. And now I wonder what and where things went wrong. Maybe there are some entries in /etc/modutils/path missing? I had some problems with missing or wrong entries in that files once in a while. But I to admit it I have no clue how to add the new 2.4.22 paths manually or automagically. Maybe the problem is totally different:

I didn't compile the kernel in /usr/src/linux, but in a directory on a mounted ext2 file I created on my W-DOS partition, so the base path ( -I e.g.) was /mnt/tmp/linux. Maybe this path is ported into the kernel-package and I have to override it with an option when make-kpkg??? I dunno. Please help. :?:

Have you tried installing a 2.4.22 kernel on the P120 previously? If that's the case you might be installing the modules in a previously used directory (/lib/modules/<uname -r>).

If you can get as far as logging in to this computer with the new kernel, try just running update-modules as root.

The build directory should have nothing to do with the resulting kernel package.

hw

Quote:

---

Originally Posted by hw-tph

Have you tried installing a 2.4.22 kernel on the P120 previously? If that's the case you might be installing the modules in a previously used directory (/lib/modules/<uname -r>).

If you can get as far as logging in to this computer with the new kernel, try just running update-modules as root.

The build directory should have nothing to do with the resulting kernel package.

hw

---

No I didn't installed any previous 2.4.22 kernels. But to be honest, after rebuilding the kernel package with a different config on the P4, I kind of forgot to remove the /lib/modules/2.4.22.2003-sep-25 directory... so if there were modules with unresolved symbols left over from my first... they might be the troublemakers then. :oops: But I have to check that first.

About just saying [no] and installing the kernel-image completely... hmmm... I avoided that, because I didn't want to reboot my server with an half-broken kernel-image set up. But it seems so that I simply have to do that. Since I only have one VGA monitor :cry: and managed the server completely via SSH, I wanted to wait with the physical procedure of switching the VGA cable between both PCs as long as possible. :P

Thanks, you helped me a lot by pointing out some the obvious mistakes I may have done. It's a long time ago since I maintained my GNU box, so I've forgotten a lot. That's why I post. ;)

If it fails, I'll come back.
Cheers.

Ok now I'm under Knoppix again... ready for some action.


The deletion of the old /lib/modules didn't make it run... because there was never any 2.4.22 directory left over since I made a dpkg --purge after each failing attempt. It cleaned the modules dir up.

So I'll include my dpkg output. Maybe someone with more experience with the new 22 kernel sees what depmod is missing:

Code:

---

root@apollon:/opt/kernel# dpkg -i kernel-image-2.4.22.2003-sep-25_10.00.Custom_i386.deb
Selecting previously deselected package kernel-image-2.4.22.2003-sep-25.
(Reading database ... 30221 files and directories currently installed.)
Unpacking kernel-image-2.4.22.2003-sep-25 (from kernel-image-2.4.22.2003-sep-25_10.00.Custom_i386.deb) ...
Setting up kernel-image-2.4.22.2003-sep-25 (10.00.Custom) ...
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/drivers/block/rd.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/drivers/char/lp.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/drivers/isdn/divert/dss1_divert.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/drivers/isdn/hisax/hisax.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/drivers/isdn/isdn.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/drivers/isdn/isdn_bsdcomp.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/drivers/isdn/isdnloop/isdnloop.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/drivers/net/dummy.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/drivers/net/slhc.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/affs/affs.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/fat/fat.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/lockd/lockd.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/minix/minix.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/msdos/msdos.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/nfs/nfs.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/nfsd/nfsd.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/nls/nls_cp437.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/nls/nls_cp850.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/nls/nls_iso8859-1.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/nls/nls_iso8859-15.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/nls/nls_utf8.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/smbfs/smbfs.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/fs/vfat/vfat.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/core/pktgen.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/ip_gre.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/ipip.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_conntrack.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_conntrack_amanda.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_conntrack_ftp.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_conntrack_irc.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_conntrack_tftp.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_nat_amanda.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_nat_ftp.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_nat_irc.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_nat_snmp_basic.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_nat_tftp.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_queue.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ip_tables.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_DSCP.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_ECN.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_LOG.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_MARK.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_MASQUERADE.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_MIRROR.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_REJECT.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_TCPMSS.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_TOS.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_ULOG.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_conntrack.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_ecn.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_helper.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_limit.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_mac.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_owner.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_recent.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_tcpmss.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_ttl.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/ipt_unclean.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/iptable_filter.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/iptable_mangle.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipv4/netfilter/iptable_nat.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/ipx/ipx.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/netlink/netlink_dev.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/cls_fw.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/cls_route.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/cls_rsvp.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/cls_rsvp6.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/cls_tcindex.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/cls_u32.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_cbq.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_csz.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_dsmark.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_gred.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_htb.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_ingress.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_prio.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_red.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_sfq.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_tbf.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sched/sch_teql.o
depmod: *** Unresolved symbols in /lib/modules/2.4.22.2003-sep-25/kernel/net/sunrpc/sunrpc.o
There was a problem running depmod.  This may be benign,
(You may have versioned symbol names, for instance).
Or this could be an error.
        depmod exited with return value 1
In any case, since depmod is run at install time,
we could just defer running depmod
Would you like to abort now? [Yes]
dpkg: error processing kernel-image-2.4.22.2003-sep-25 (--install):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 kernel-image-2.4.22.2003-sep-25
root@apollon:/opt/kernel#

---

phew long list... I hope it helps.

Are you using gcc > 3.x to compile the kernel? If so you should export CC=/usr/bin/gcc-2.95 and try compiling with that set. Also why are you not compiling the kernel in /usr/src?

Quote:

---

Originally Posted by hw-tph

If you can get as far as logging in to this computer with the new kernel, try just running update-modules as root.

---

I am logged in now, actually. :D I just tried to reboot it with the new kernel, expecting the worst. But as far as I can see everything works like before. Even beter now, because I now have a 100MBit connection between my server and this PC. Ok, I think I just was a bit too ubercautious.
But a mkrescue bootdisk with an the former kernel gave me the needed courage. Omg, what a drama.

Quote:

---

Originally Posted by hw-tph

The build directory should have nothing to do with the resulting kernel package.

hw

---

Yes, indeed. :D

Thx again, tho I don't know why these warning messages appeared at all... maybe because I installed the kernel-image package while running an older/other kernel version.

I mean, I reinstalled my custom kpkg running the custom kernel and none of these warnings appeared. Even though, I hadn't done a update-modules and no modules.dep file was there in the 2.4.22.2003-sep-25 dir.

Or was it because of the 2.4.20 System.map being loaded while dpkg was doing a modprobe -a... but I even tried to use the new System.map of my 2.4.22 custom kernel using the -F option and the same errors occured.

And I am 200% sure that dpkg invokdes the depmod cmd with "-F /boot/System.map-to_be_installed_version". So what was it that made me think it is unsafe to boot that server with broken modules?

cheers,
i_needed_help

Quote:

---

Originally Posted by Stephen

Are you using gcc > 3.x to compile the kernel? If so you should export CC=/usr/bin/gcc-2.95 and try compiling with that set.

---

The different gcc versions made no problems, since I am actually using the new gcc 3.2.3 built kernel on my server on which gcc 2.95.4 is installed. Maybe I should upgrade to 3.2.3 before I try to compile something on my P120 box?

Quote:

---

Originally Posted by Stephen

Also why are you not compiling the kernel in /usr/src?

---

:lol: that's why:

Code:

---

root@ttyp0[root]# cd /usr/src/linux
root@ttyp0[linux]# touch test
touch: kann »test« nicht berühren: Das Dateisystem ist nur lesbar
root@ttyp0[linux]#

---

which is german for the fs is read-only.

Ok I recompiled the 2.4.22 kernel with gcc 2.95.4 now... I was already running a 2.4.22 kernel when I installed the latest kernel-image package I made.

Still I get these unresolved symbols by depmod... wait. I haven't got the same version running like I installed:

Code:

---

root@apollon:~# uname -r
2.4.22.2003-sep-25
root@apollon:~# l /opt/kernel/kernel-image-2.4.22.2003-sep-27_10.00.Custom_i386.deb
-rw-r--r--    1 root    root      1806130 Sep 27 06:54 /opt/kernel/kernel-image-2.4.22.2003-sep-27_10.00.Custom_i386.deb
root@apollon:~# l -d /lib/modules/2.4.22.2003-sep-27/
drwxr-xr-x    4 root    root        1024 Sep 27 07:04 /lib/modules/2.4.22.2003-sep-27/
root@apollon:~#

---

Ahh crap. Anyways... I guess it's all about 'uname -r' and the diff kernel versions why I get these dull ksym warnings... after booting the new kernel they disappear...

OK, case closed.
Cya