From: whitnl73@juno.com
To: raihan@citech-bd.com
Cc: linux-newbie@vger.kernel.org
Subject: Re: Network card and kernel module problems
Date: Tue, 4 Feb 2003 16:52:57 -0500 (EST) [thread overview]
Message-ID: <20030204.180710.8.0.whitnl73@juno.com> (raw)
In-Reply-To: <000301c2cb7d$184dd620$eb6510ac@citechbd.com>
On Mon, 3 Feb 2003, Amin wrote:
> I'm beginning to think I've mixed up different kernel module dependencies.
> The short story is I need help sorting out the modules for use with my two
> kernels: 2.4.18-14 and 2.4.18-14custom. The long story is: when I
> originally installed RH8.0 and found it didn't already support my NIC, I
> recompiled the kernel with
>
> make xconfig; make dep; make modules; make modules_install; make bzImage
>
> and tried to boot the new kernel. Eventually I got it to boot, but it
> failed to detect/insert a lot of modules, which seems strange in
> retrospect because I think I actually specified only one loadable module;
> all the others were built-in. I recompiled again, with the same results.
If you didn't change EXTRAVERSION in the Makefile, you will have the
leftover modules from the modular kernel in /lib/modules/`uname -r`
but they will not be able to load with the kernel that has them builtin.
I'd use a unique EXTRAVERSION for each new custom configuration.
When you get it right you can remove all the false starts.
> A lot of error messages courtesy of depmod as it tries to find module
> dependencies --- things like input.o, soundcore.o, etc. I've recompiled
> twice after that, with a slightly different command order:
>
> make xconfig; make dep; make bzImage; make modules; make modules_install
>
> But still I get the same module dependency problems during boot. Help!
>
> Yawar Amin
>
Lawson
--
---oops---
________________________________________________________________
Sign Up for Juno Platinum Internet Access Today
Only $9.95 per month!
Visit www.juno.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next prev parent reply other threads:[~2003-02-04 21:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 15:56 Network card and kernel module problems Amin
2003-02-02 16:15 ` pa3gcu
2003-02-03 12:09 ` Amin
2003-02-03 16:55 ` pa3gcu
2003-02-04 21:52 ` whitnl73 [this message]
2003-02-03 17:24 ` Ray Olszewski
2003-02-05 4:47 ` Amin
2003-02-05 6:21 ` Ray Olszewski
2003-02-05 20:24 ` whitnl73
-- strict thread matches above, loose matches on Subject: below --
2003-02-05 15:24 Whitnl73@juno.com
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=20030204.180710.8.0.whitnl73@juno.com \
--to=whitnl73@juno.com \
--cc=linux-newbie@vger.kernel.org \
--cc=raihan@citech-bd.com \
/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