All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christian Ullrich <chris@chrullrich.de>, linux-kernel@vger.kernel.org
Subject: Re: insmod problem after modutils upgrading
Date: Wed, 13 Dec 2000 16:11:32 -0500	[thread overview]
Message-ID: <3A37E604.41D8BE77@mandrakesoft.com> (raw)
In-Reply-To: <E146JAu-0003HX-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > > 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.
> 
> It is modutils. Their behaviour changed in a non back compatible way. Do not
> use modutils 2.3.22 with Linux 2.2.* is the simple answer. Perhaps Keith can
> make this a warning in 2.3.23

That, and/or allow "insmod -f" to load the module.  '-f' has become
pretty useless lately... :)

	Jeff


-- 
Jeff Garzik         |
Building 1024       | These are not the J's you're lookin' for.
MandrakeSoft        | It's an old Jedi mind trick.
-
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:42 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
2000-12-13 21:04   ` Jeff Garzik
2000-12-13 21:10   ` Alan Cox
2000-12-13 21:11     ` Jeff Garzik [this message]
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=3A37E604.41D8BE77@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=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 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.