From: Mathieu Chouquet-Stringer <mchouque@e-steel.com>
To: linux-kernel@vger.kernel.org
To: gnuman0@pacbell.net
Subject: Re: Modules not being found with 2.4.0 on a 486 based box
Date: 23 Jan 2001 18:29:51 -0500 [thread overview]
Message-ID: <m3wvbl6e4w.fsf@shookay.e-steel.com> (raw)
In-Reply-To: <3A6E128D.7C436455@pacbell.net>
You need to install a recent version of modutils (at least 2.4.0) because
the directory structure changed as you noticed it and the new modutils are
able to deal with that.
gnuman0@pacbell.net (C Sanjayan Rosenmund) writes:
> Please cc: me as well, as I'm on to many lists as is. . .
>
> Irecently built 2.4.0 on two diferent x486 PCs and neither of them
> recognised the new module directory structure found in the 2.4.x
> kernels. I did not have this problem on the Pentium and better
> machines that I built this same kernel on. I got around the problem
> by making a symlink from where the module actually was
> (/lib/modules/2.4.0/kernel/drivers/net/) to where the system was
> looking for it (/lib/modules/2.4.0/net/) and all is well. . .for now.
> I was wondering if there was any light that could be shed on why this
> might happen? I have only found this to be a problem on 486s,
> everything bigger has worked fine. Details below:
> Feature Working Not Wotking
> Processor Pentium + 486 (486DX2-66, 486DX-50)
> Distrobution Debian unstable Debian stable (unstable caused other
> problems)
> RAM 16Mb + 16Mb +
> Hdd size 1Gb + 540Mb +
> Modules involved Any network cards (that is all I was using)
>
> More info can be provided if needed. This is low priority, I was
> wondering if you had any ideas why (or how to get around it, other
> than my solution).
>
> Thank you all for your time, and for producing a kernel that is worth
> all this work <grin>.
--
Mathieu CHOUQUET-STRINGER E-Mail : mchouque@e-steel.com
Learning French is trivial: the word for horse is cheval, and
everything else follows in the same way.
-- Alan J. Perlis
-
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/
prev parent reply other threads:[~2001-01-23 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 23:23 Modules not being found with 2.4.0 on a 486 based box C Sanjayan Rosenmund
2001-01-23 23:29 ` Mathieu Chouquet-Stringer [this message]
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=m3wvbl6e4w.fsf@shookay.e-steel.com \
--to=mchouque@e-steel.com \
--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