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 14:43:00 -0400 [thread overview]
Message-ID: <20020801144115.SM02488@there> (raw)
In-Reply-To: <Pine.LNX.4.44.0207300002170.7104-100000@server.superbt.com>
Ilguiz,
I tested the 07-29 patch on a DoC Millennium, and everything seemed to be
working great. I was able to build it against cvs grub with no errors, and
the resulting grub_firmware booted fine on a 1.3Ghz Athlon.
However, I have also been experimenting with booting a variant of the Linux
Router Project (LRP) from my DoC, and this latest Grub patch locks up on two
different Pentium-133 PC's.
Additionally, the M-Sys firmware also locked up on both machines. The
earlier Grub patch (the one with the -256 and -512 options) works fine. I'm
not sure what's going on here, but I'll continue to try to figure out what is
wrong.
Mark
Ilguiz Latypov wrote:
> I added floppy disk BIOS number (0) as a last resort when looking for boot
> configuration file. Would you mind testing the aggregate patch I stored
> under
>
> patches/grub-2002-07-29-doc.patch
next prev parent reply other threads:[~2002-08-01 18:45 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 [this message]
2002-08-01 20:53 ` Ilguiz Latypov
2002-08-01 21:21 ` Mark Meade
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=20020801144115.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.