linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Ullrich <chris@chrullrich.de>
To: linux-kernel@vger.kernel.org
Subject: Re: insmod problem after modutils upgrading
Date: Wed, 13 Dec 2000 21:59:15 +0100	[thread overview]
Message-ID: <20001213215915.A10848@christian.chrullrich.de> (raw)
In-Reply-To: <001b01c0652b$ec758de0$247d9cca@mindef>
In-Reply-To: <001b01c0652b$ec758de0$247d9cca@mindef>; from csyap@starnet.gov.sg on Thu, Dec 14, 2000 at 01:41:28AM +0800

* Corisen schrieb am Donnerstag, 14.12.2000:

> 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.

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

I "fixed" the same problem in 2.2.18 by commenting out the line

MODULE_PARM (debug, "i");

near the end of drivers/net/8139too.c. Since I run modutils 2.3.22
as well, it can't be related to the modutils.

-- 
Christian Ullrich		     Registrierter Linux-User #125183

"Sie können nach R'ed'mond fliegen -- aber Sie werden sterben"
-
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 21:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13 17:41 insmod problem after modutils upgrading Corisen
2000-12-13 20:59 ` Christian Ullrich [this message]
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=20001213215915.A10848@christian.chrullrich.de \
    --to=chris@chrullrich.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).