public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Dan Brown <dan_brown@ieee.org>
To: Brian O'Dell <brian@clarionsensing.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: DOCBoot doesn't compile
Date: Tue, 28 Jun 2005 15:12:26 -0400	[thread overview]
Message-ID: <42C1A11A.2020108@ieee.org> (raw)
In-Reply-To: <42C180D4.1010607@clarionsensing.com>

Brian O'Dell wrote:

> Thank you for the quick response Dan.  DOCBoot does compile now, but 
> it freezes prior to any indication that it is trying to load the 
> kernel.  Here is what I get with DEBUG_BUILD defined:
> Installing DOCBoot.
> doc_seg = 0xE000           setup_seg = 0x2400
> int15/e801 returns 0x0F00    initrd_start = 0x0FFF0000
> top of low mem = 0x0279k    handler seg = 0x9E00
> -- Press any key --
>
> Prior to pressing any key, numlock and capslock respond normally.  I 
> can also reboot via ctrl-alt-del.  I press enter, then the system 
> freezes hard.  No numlock or capslock response, ctrl-alt-del does not 
> work.  Any thoughts or ideas are much appreciated.


Hmm.  Well, nothing appears odd in the debug messages.  Your DOC is at 
E000, you have 256Mbytes of RAM, you have 633k free low memory, etc.  
Let me get some more info from you:

- what type/size of DOC you're using
- size of your kernel and initrd
- what options you use when building DOCBoot (which interrupt, for 
instance).
- what other devices are in the system (video, harddrives, etc)

Hopefully you're able to boot your system normally (DOCBoot install will 
be skipped if you hold down shift, alt, or control at the appropriate 
phase of BIOS boot).

    -Dan

  reply	other threads:[~2005-06-28 19:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 18:05 DOCBoot doesn't compile Brian O'Dell
2005-06-27 18:50 ` Dan Brown
2005-06-28 16:54   ` Brian O'Dell
2005-06-28 19:12     ` Dan Brown [this message]
2005-06-28 21:39       ` Brian O'Dell
2005-06-29 18:39         ` Brian O'Dell
2005-06-29 18:47           ` Dan Brown
2005-06-29 20:12             ` Dan Brown
2005-06-29 21:50               ` Brian O'Dell

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=42C1A11A.2020108@ieee.org \
    --to=dan_brown@ieee.org \
    --cc=brian@clarionsensing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox