From: Mark Meade <mark@lakeshoremicro.com>
To: Ilguiz Latypov <ilatypov@superbt.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [patch] doc_stage1.S : GRUB on DoC
Date: Thu, 1 Aug 2002 17:21:11 -0400 [thread overview]
Message-ID: <200208011718437.SM02488@there> (raw)
In-Reply-To: <Pine.LNX.4.44.0208011649190.21990-100000@server.superbt.com>
Ilguiz Latypov wrote:
> Could that be due to change in MTD patch I made? I added the
> informational message output "DoC found" at the time of ROM BIOS extension
> scan. I wonder if the video card's BIOS extension can render INT 10h
> unstable at that time.
I don't think so -- I temporarily removed that message, and made sure that
the initial code (what used to be in doc_stage1.S) matched the previous
version that worked. It didn't make any difference - it still locked up on
the P-133's, but not on the Athlon.
For what it's worth, on one of the PC's, the lockup occurs at line 363, in
the readbyte loop. We copy a few pages OK (%di = 0x400, 0x500, 0x600), but
lock up when %di is between 0x700 and 0x800, specifically with ES:DI equal to
0x07E0:0x0719.
The other board makes it to the "Jumping to Grub" message, but then
immediately reboots.
Mark
next prev parent reply other threads:[~2002-08-01 21:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 18:52 [patch] doc_stage1.S : GRUB on DoC Mark Meade
2002-07-17 18:35 ` Ilguiz Latypov
2002-07-30 4:11 ` Ilguiz Latypov
2002-08-01 18:43 ` Mark Meade
2002-08-01 20:53 ` Ilguiz Latypov
2002-08-01 21:21 ` Mark Meade [this message]
2002-08-01 23:44 ` Ilguiz Latypov
2002-08-02 13:37 ` Mark Meade
2002-08-02 14:02 ` Ilguiz Latypov
2002-08-02 19:18 ` Ilguiz Latypov
2002-08-02 19:49 ` Mark Meade
2002-08-02 21:27 ` Ilguiz Latypov
2002-08-02 21:57 ` Ilguiz Latypov
2002-08-06 16:26 ` Mark Meade
-- strict thread matches above, loose matches on Subject: below --
2002-08-01 14:47 Vadim Khmelnitsky
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=200208011718437.SM02488@there \
--to=mark@lakeshoremicro.com \
--cc=ilatypov@superbt.com \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.