From: C Sanjayan Rosenmund <gnuman0@pacbell.net>
To: linux-kernel@vger.kernel.org
Subject: Modules not being found with 2.4.0 on a 486 based box
Date: Tue, 23 Jan 2001 15:23:57 -0800 [thread overview]
Message-ID: <3A6E128D.7C436455@pacbell.net> (raw)
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>.
--
C Sanjayan Rosenmund
gnuman0@pacbell.net ICQ 95669689
It is dangerous to be right when the government is wrong. - Voltaire
-
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/
next reply other threads:[~2001-01-23 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 23:23 C Sanjayan Rosenmund [this message]
2001-01-23 23:29 ` Modules not being found with 2.4.0 on a 486 based box Mathieu Chouquet-Stringer
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=3A6E128D.7C436455@pacbell.net \
--to=gnuman0@pacbell.net \
--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