All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Zimmermann <florian.zimmermann@gmx.net>
To: linux-8086@vger.kernel.org
Subject: Re: Booting with Elks
Date: Wed, 11 Feb 2004 20:02:33 +0100	[thread overview]
Message-ID: <1076526153.4032.13.camel@mindfsck> (raw)
In-Reply-To: <1076443760.4034.28.camel@mindfsck>

mail I accidently forgot to CC to linux-8086:

On Tue, 2004-02-10 at 21:09, Florian Zimmermann wrote:
> Hi Blaz!
> 
> On Wed, 2004-02-11 at 05:48, Blaz Antonic wrote:
> > Hello,
> > 
> > > when I try to boot the elks boot disk on my toshiba lt1200
> > > (8086 cpu, 640k ram) I am getting displayed the error 8000 in an
> > > infinite loop. I have also tried the comb disk and a self-made
> > > kernel dd'ed on a disk, with same results :(
> > > 
> > > Can anyone point me to where this error may come from?
> > > What kind of bootloader is used on the elks boot disk? (if any)
> > > Google and a grep over kernel sources gave no hint to me yet...
> > 
> > Can you post the exact error message you see ? Vague descriptions never
> > help and i don't recall any "error 8000" error message anywhere in the
> > source (grep around to provve me wrong, it's a small number of files
> > anyway so should be over quickly no matter how slow your compilation box
> > is).
> 
> After the bios screen I can see a clear screen and after that
> floppy disk led is active, loading, then only the 8000 error appears,
> like this:
> 8000
> 8000
> 8000
> 8000
> 8000
> 8000
> etc.
> 
> The floppy disk led stays active, so it seems to be like an infinite
> loop. And as already said, I have no reference to this 8000 number found
> in the kernel sources either :(
> 
> > 
> > If it is register small dump (with AX containing error value) it might
> > be that BIOS read function is returning an error, presumeably because
> > your drive/medium is defective. Are you sure that both drive and the
> > medium you use are working allright ?
> 
> I have MINIX successfully running on this machine, so I don't think it
> is hardware fault. I have only an 360k floppy drive, might that be a
> problem? (although the boot image easily fits there)
> 
> Thanks,
> Florian
> 
> > 
> > Blaz Antonic
-- 
Florian Zimmermann <florian.zimmermann@gmx.net>


  parent reply	other threads:[~2004-02-11 19:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 18:12 Booting with Elks Florian Zimmermann
2004-02-11 10:58 ` David Given
2004-02-11 11:40   ` AW: " Mario Premke
2004-02-11 11:43     ` Paul Nasrat
     [not found] ` <4029B42F.4AED@siol.net>
     [not found]   ` <1076443760.4034.28.camel@mindfsck>
2004-02-11 19:02     ` Florian Zimmermann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-11 12:44 Pat Gilliland
2004-02-11 18:52 ` Florian Zimmermann

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=1076526153.4032.13.camel@mindfsck \
    --to=florian.zimmermann@gmx.net \
    --cc=linux-8086@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 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.