From: Brian Gerst <bgerst@didntduck.org>
To: rob@sysgo.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Anybody got 2.4.0 running on a 386 ?
Date: Tue, 09 Jan 2001 16:59:25 -0500 [thread overview]
Message-ID: <3A5B89BD.A22F6D8D@didntduck.org> (raw)
In-Reply-To: <01010922090000.02630@rob> <3A5B7F76.ABDFED7A@didntduck.org> <01010922264400.02737@rob>
Robert Kaiser wrote:
>
> On Die, 09 Jan 2001 you wrote:
> > Robert Kaiser wrote:
> > > I can't seem to get the new 2.4.0 kernel running on a 386 CPU.
> > > The kernel was built for a 386 Processor, Math emulation has been enabled.
> > > I tried three different 386 boards. Execution seems to get as far as
> > > pagetable_init() in arch/i386/mm/init.c, then it falls back into the BIOS as
> > > if someone had pressed the reset button. The same kernel boots fine on
> > > 486 and Pentium Systems.
> > >
> > > Any ideas/suggestions ?
> >
> >
> > is "Checking if this processor honours the WP bit even in supervisor
> > mode... " the last thing you see before the reset?
> >
>
> No, I don't see _any_ messages from the kernel. The last thing I see is
> "Uncompressing Linux... Ok, booting the kernel." I have added some
> quick and dirty debug code that writes messages directly to the VGA
> screen buffer. According to that, execution seems to get as far as the
> statement
>
> *pte = mk_pte_phys(__pa(vaddr), PAGE_KERNEL);
How about this patch (untested)? max_low_pfn should be a global var...
diff -urN linux-2.4.0/arch/i386/kernel/setup.c
linux/arch/i386/kernel/setup.c
--- linux-2.4.0/arch/i386/kernel/setup.c Sun Dec 31 13:26:18 2000
+++ linux/arch/i386/kernel/setup.c Tue Jan 9 17:59:00 2001
@@ -598,7 +598,7 @@
void __init setup_arch(char **cmdline_p)
{
unsigned long bootmap_size;
- unsigned long start_pfn, max_pfn, max_low_pfn;
+ unsigned long start_pfn, max_pfn;
int i;
#ifdef CONFIG_VISWS
--
Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-09 22:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 20:53 Robert Kaiser
2001-01-09 21:15 ` Brian Gerst
2001-01-09 21:17 ` Robert Kaiser
2001-01-09 21:46 ` Brian Gerst
2001-01-09 22:17 ` Robert Kaiser
2001-01-09 22:57 ` Ingo Molnar
2001-01-09 23:44 ` Robert Kaiser
2001-01-10 0:19 ` Alex Buell
2001-01-10 0:20 ` Ingo Molnar
2001-01-10 0:24 ` Ingo Molnar
2001-01-10 16:00 ` Robert Kaiser
2001-01-10 21:29 ` Tom G. Christensen
2001-01-10 22:04 ` X performance on 2.4.0 v.s. 2.4.0-test12 Alan Olsen
2001-01-09 23:03 ` Anybody got 2.4.0 running on a 386 ? Brian Gerst
2001-01-09 23:04 ` Robert Kaiser
2001-01-09 23:28 ` Anuradha Ratnaweera
2001-01-09 23:42 ` Robert Kaiser
2001-01-10 1:48 ` Miles Lane
2001-01-10 15:25 ` Robert Kaiser
2001-01-10 21:04 ` Miles Lane
2001-01-10 16:28 ` Paul Gortmaker
2001-01-15 18:38 ` [SOLVED + PATCH] " Robert Kaiser
2001-01-15 19:11 ` Linus Torvalds
2001-01-09 22:44 ` Timur Tabi
2001-01-09 21:59 ` Brian Gerst [this message]
2001-01-10 19:51 ` mo6
2001-01-10 20:18 ` Brian Gerst
2001-01-10 21:53 ` mo6
2001-01-11 12:20 ` mo6
2001-01-10 3:53 ` Tom Leete
2001-01-10 9:25 richardj_moore
2001-01-10 14:19 ` Alan Cox
2001-01-10 15:04 ` Robert Kaiser
2001-01-10 15:49 ` Alan Cox
2001-01-10 16:02 ` Robert Kaiser
[not found] <Pine.LNX.4.04.10101101000130.27018-100000@hantana.pdn.ac.lk>
2001-01-10 15:37 ` Robert Kaiser
2001-01-10 17:16 Petr Vandrovec
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=3A5B89BD.A22F6D8D@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@sysgo.de \
/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®