From: "Steve Kieu" <haiquy@yahoo.com>
To: Thomas Ackermann <atze-lists@ewave.at>
Cc: kernel <linux-kernel@vger.kernel.org>
Subject: Re: boot problems with older machines, kernels 2.4.x
Date: Tue, 4 Sep 2001 08:51:40 +1000 (EST) [thread overview]
Message-ID: <20010903225140.13484.qmail@web10404.mail.yahoo.com> (raw)
In-Reply-To: <3B938B06.E38D36A9@ewave.at>
--- Thomas Ackermann <atze-lists@ewave.at> wrote: >
Steve Kieu schrieb:
>
> > strange! I use a rather old 486 20M ram here and
> no
> > problem.
>
> indeed is is quite strange, if i compile that kernel
> on the 486 the machine
> works,
> only doesn`t work when i untar the system built on
> the k7 onto the 486...
> something in the system has to be wrong, maybe libs
> i think, but don't have a
> clue what it could be..
> not even a init startup message..
I once have the same problem with 2.2.19 in slackware,
thing is, even I chose to make for 486 the kernel
still refuses to run on 486 but run on the 686 (the
machine I compile. So I edit the Make file and add to
the C flags this -mcpu=i686 -march=i486 to force it
compile for the march=i486. It works.
I am not sure at this time about my glibc, may be it
was already the new compiled one for 686 ; Let me test
today. that is compile kernel for 486 but the library
all built for 686 and see if it works. Theoreticlly if
the kernel is statically linked with libc, it wont
work too. Am I right?
Regard
> -
> 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/
=====
S.KIEU
http://travel.yahoo.com.au - Yahoo! Travel
- Got Itchy feet? Get inspired!
prev parent reply other threads:[~2001-09-03 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 10:40 Thomas Ackermann
2001-08-17 23:27 ` Steve Kieu
2001-09-03 13:52 ` Thomas Ackermann
2001-09-03 22:51 ` Steve Kieu [this message]
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=20010903225140.13484.qmail@web10404.mail.yahoo.com \
--to=haiquy@yahoo.com \
--cc=atze-lists@ewave.at \
--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®