mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: bonganilinux@mweb.co.za
Cc: "Miguel Quirós" <mquiros@ugr.es>, KML <linux-kernel@vger.kernel.org>
Subject: Re: make modules_install fail: depmod *** Unresolved symbols (official
Date: 14 Mar 2003 16:16:45 +0200	[thread overview]
Message-ID: <1047651405.3503.103.camel@workshop.saharact.lan> (raw)
In-Reply-To: <E18tpXR-0007oI-00@rammstein.mweb.co.za>

On Fri, 2003-03-14 at 16:03, bonganilinux@mweb.co.za wrote:
> > 			Granada, 14-3-2002
> > 
> > Hello, I downloaded kernel 2.4.20 and compiled it sucessfully a month
> > ago without any aparent problem. Yesterday I tried to compile it again
> > in the same computer just changing a couple of small things in the
> > configuration (agpart and the network card changed from "module" to
> > "yes").
> > 
> > make dep, make bzImage and make modules went apparently well (expect for
> > a few apparently non-important warnings with bzImage of the type
> > Warning: indirect call without '*' when compiling pci-pc and apm).
> > 
> > But when I try make modules_install, I've got a lot of error messages.
> > For each module I've got one line like:
> > 
> > depmod:  *** Unresolved symbols in
> > /lib/modules/2.4.20/kernel/arch/i386/kernel/microcode.o
> > 
> > followed by a number of lines of the type
> > 
> > depmod:     misc_deregister
> > depmod:     __generic_copy_from_use
> > depmod:     .....
> 
> Download, compile and install Rusty's latest module-init-tools
> ftp.kernel.org/pub/linux/kernel/people/rusty/modules
> 

Errr, he got 2.4.20, not 2.5.48+ ....

Miguel:  Not a real fix, but try compiling microcode.o into the
         kernel and not as a module ...


Regards,

-- 
Martin Schlemmer
Gentoo Linux Developer, Desktop Team
Cape Town, South Africa


  reply	other threads:[~2003-03-14 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 14:03 bonganilinux
2003-03-14 14:16 ` Martin Schlemmer [this message]
2003-03-14 19:53   ` Bongani Hlope
2003-03-17 15:55   ` Miguel Quirós

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1047651405.3503.103.camel@workshop.saharact.lan \
    --to=azarah@gentoo.org \
    --cc=bonganilinux@mweb.co.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mquiros@ugr.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®