From: Muthukumar <kmuthukumar@mail15.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Problem on 2.6.0-test3 kernel
Date: Wed, 10 Sep 2003 22:00:19 +0400 (MSD) [thread overview]
Message-ID: <200309101800.h8AI0JYY074734@www.mail15.com> (raw)
Hello all ..,
I have compiled the kernel-2.6.0 test3 in IA64 with Ia64 patch
as
make menuconfig
make all
make modules
But in this step i got the following messages as
make modules
make[1]: `arch/ia64/kernel/asm-offsets.s' is up to date.
Building modules, stage 2.
MODPOST
*** Warning: "per_cpu__local_per_cpu_offset"
[drivers/net/tulip/tulip.ko] has no CRC!
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/tg3.ko]
has no CRC!
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/eepro100.
ko] has no CRC!
*** Warning: "per_cpu__local_per_cpu_offset"
[drivers/net/e100/e100.ko] has no CRC!
After installing the module-init-tools-0.9.tar.bz2 to update the
module tool and in the make install i got the messges of
so many ./install-with-care for all files in /bin/sh for all files
in module-init-tools-0.9.Then i have changed
the ./install-with-care for as ./install-sh.
So is there any effect of this module or....
So what is the this effect and what is the problem on the above
messages on 2.6.0test3 on Ia64.then there is no interfaces to eth0
eth1 ,so i cannot take the testings.But the entires for the
ifcfg-eth0 and ifcfg-eth1 are there.
Is that a serious problem,pls give the info for this.
So i need the guidlines for this...
Thanks
Mvthv
-
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/
reply other threads:[~2003-09-10 18:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200309101800.h8AI0JYY074734@www.mail15.com \
--to=kmuthukumar@mail15.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
all inboxes | Powered by JetHome®