All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Corisen" <csyap@starnet.gov.sg>
To: <linux-kernel@vger.kernel.org>
Subject: insmod problem after modutils upgrading
Date: Thu, 14 Dec 2000 01:41:28 +0800	[thread overview]
Message-ID: <001b01c0652b$ec758de0$247d9cca@mindef> (raw)

i've upgraded modutils from 2.3.14 (originally installed by RH7,kernel
2.2.16) to 2.3.22 using "rpm -Fvh modultils2.3.22-1.i386.rpm*" as required
by the kernel 2.4test12 compilation. after upgrading, the network module
refused to load anymore (was working fine with insmod 2.3.14) with kernel
2.2.16/RH7. during boot process, the following error message was shown:
insmod: /lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o insmod eth0
failed.

executing "insmod 8139too" at the command prompt shows the following error
message:
using /lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o
/lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o: symbol for
parameter debug not found.

pls kindly advise if i've done something wrong during the upgrade or are
there known compatibility issues with modutils 2.3.22?

how can i make insmod load the network module again pls?

thanks.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-13 18:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13 17:41 Corisen [this message]
2000-12-13 20:59 ` insmod problem after modutils upgrading Christian Ullrich
2000-12-13 21:04   ` Jeff Garzik
2000-12-13 21:10   ` Alan Cox
2000-12-13 21:11     ` Jeff Garzik
2000-12-13 22:05     ` Keith Owens
2000-12-13 22:13       ` Alan Cox
2000-12-14  0:02         ` Keith Owens
2000-12-14  0:43           ` Alan Cox
2000-12-14 12:32         ` Horst von Brand
2000-12-14 17:50           ` Alan Cox

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='001b01c0652b$ec758de0$247d9cca@mindef' \
    --to=csyap@starnet.gov.sg \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.