From: "Daniel I. Applebaum" <kernel@danapple.com>
To: linux-kernel@vger.kernel.org
Cc: "Daniel I. Applebaum" <kernel@danapple.com>
Subject: 2.5.31 build failure & booting problems
Date: Sat, 24 Aug 2002 13:25:10 -0500 [thread overview]
Message-ID: <20020824182515.3FE3F10B7A@wotke.danapple.com> (raw)
OK, I changed to gcc 2.95.3, and that tradcpp0 error disappeared.
However, when building the ATA stuff as modules, I got some unresolved
symbols during depmod -a. Compiling the ATA stuff integral to the
kernel eliminating those issues. Sorry I didn't record the error
messages. This is all relevant to 2.5.31.
Neither 2.5.31 nor 2.4.19 will boot on my machine. So I seem to be
stalled at 2.4.13. Do I need a new version of LILO? I'm currently at
LILO version 21.4-4
(For those new to this thread, my LILO will show Loading
linux-2.4.19.................. and then the machine will immediately
reboot. Same for linux-2.5.31.)
My kernels ls -l as:
-rw-rw-r-- 1 root root 886157 Aug 24 10:36 vmlinuz-2.4.19
-rw-rw-r-- 1 root root 897454 Aug 24 11:40 vmlinuz-2.5.31
Are they too big?
This is how I build the kernel:
make clean
make menuconfig
make clean dep bzImage
make modules
make modules_install
cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.19
cd /boot
mkinitrd -f initrd-2.4.19.img 2.4.19
lilo
reboot
Any suggestions? I'm totally baffled.
Which is the very first routine in the kernel to be run? I'd like to
insert some kind of print statement, if possible, to see if it is even
getting called by LILO.
Dan.
reply other threads:[~2002-08-24 18:21 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=20020824182515.3FE3F10B7A@wotke.danapple.com \
--to=kernel@danapple.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®