Re: [gentoo-dev] kernel 2.4.10 Unresolved symbols

[Collins Richey]

On Sat, 29 Sep 2001 09:51:19 -0400 Joe DeRosa <derosa@×××××××××.net>
wrote:

> Try this,
> Build a new bzImage and install it in your boot partition. This
> image
> must contain all you need without modules to get the basic system up
> and
> running IE all scsi/ide drivers and filesystems. Make modules, but
> don't
> do a modules_install yet.
> Reboot using the new kernel
> Then do a modules_install
> What is happening, and I'm not sure why is the depmod is trying to
> find
> dependencies from the old kernel module tree.
>
> This worked for me.
>
> Joe
>
> -----Original Message-----
> From: gentoo-dev-admin@××××××××××.org
> [mailto:gentoo-dev-admin@××××××××××.org] On Behalf Of Dan Nelson
> Sent: Saturday, September 29, 2001 1:37 AM
> To: gentoo-dev@××××××××××.org
> Subject: [gentoo-dev] kernel 2.4.10 Unresolved symbols
>
> I am compiling kernel 2.4.10 and getting the following Unresolved
> symbol
>
> errors while doing the make modules_install:
>
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.4.10;
> fi
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.4-ac9/kernel/drivers/char/agp/agpgart.o
> depmod:         contig_page_data_R4f152932
> depmod:         pm_register_R8dbab11c
> depmod:         pm_unregister_all_R9c0ba5b2d
>
> There are more but they are all the same.  I am attempting to update
> to
> this
> kernel on a 1.0 rc5 box.
>

I don't know wheter this is your problem or not, but I've always found
this sequence of events to be necessary for a clean kernel/modules
apply

	1. Put the linux source somewhere like your home directory.  If you
untar it yourself, after it's untarred in your home directory, mv
linux linux-kernel_release (eg linux-2.4.10).

	2. su (not strictly necessary for everything below, but I do
everything from root mode).

	3. Rename your current modules directory to something else, eg mv
/lib/modules/linux-2.4.x /lib/modules/2.4.x-old.  Otherwise you will
have problems.

	4. Do the usual sequence (use a script if you have it)
	     make mrproper (I've had mixed results without this, even on
virgin kernel source)
             make whatever to edit the kernel config
	     make dep
	     make clean (maybe not necessary, but do it anyway)
	     make bzImage
	     make modules
	     make modules_install

	5.  Now reverse the rename of you old modules (3 above).  You will
already have a new modules directory corresponding to your new kernel.

	6. Copy over your bzImage to your /boot directory with a new name
(don't overlay your working kernel).

	7.  Do the ususal grub or lilo work to make the new kernel bootable.

Unless there are problems with the kernel source itself (1 out of 30
times I've done this), this procedure always works for me.
	
Good luck.  I'm waiting for the ebuilds to stabilize before I try
2.4.10.

-- 
Collins Richey
Denver Area
gentoo_rc6 xfce+sylpheed