From: Marcus Ramos <marcus@ansp.br>
To: linux-kernel <linux-kernel@vger.kernel.org>, juan@ansp.br
Subject: Re: Can't find modules after moving to 2.4.2
Date: Thu, 29 Mar 2001 11:13:36 -0300 [thread overview]
Message-ID: <3AC3430F.B2A87DB8@ansp.br> (raw)
In-Reply-To: <3AC24E42.7CAB822A@ansp.br>
Hello,
Thanks for those who replied telling me to upgrade modutils to 2.4.5.
I downloaded modutils-2.4.5.tar.gz and placed it in my /root directory. After
tar -xzvf, I got a new directory /root/modutils-2.4.5. Then I followed the
instructions in INSTALL:
cd modutils-2.4.5
./configure
But, from this point on, I wasn't able to finish the installation. What is
meant by "/paht/to/master/modutils/configure" ? Anyway, doing "make install"
doesn't cause any effect, as my modules still aren't loaded when I reboot
with kernel 2.4.2. Thanks in advance for your comments.
Best Regards,
Marcus.
Marcus Ramos wrote:
> Hello,
>
> I've moved from kernel 2.2.16 to 2.4.2 (RH7) and its boots OK, except
> for the fact that none of the modules in "/etc/modules.conf" are loaded
> anymore (although modules were enabled in kernel config). In
> "/lib/modules" I see two directories: 2.2.16 and 2.4.2 (which I assume
> is the default for modules.conf). However, the "/lib/modules/2.4.2"
> contains almost no files, differently from 2.2.16. I guess I've missed
> some important step during the installation of 2.4.2, but now I am
> confused and can't recover. Can anyboy point me what the missing step is
> ? I will be most grateful.
>
> Thanks in advance,
> Marcus.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
parent reply other threads:[~2001-03-29 14:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3AC24E42.7CAB822A@ansp.br>]
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=3AC3430F.B2A87DB8@ansp.br \
--to=marcus@ansp.br \
--cc=juan@ansp.br \
--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