* Booting with Elks
@ 2004-02-10 18:12 Florian Zimmermann
2004-02-11 10:58 ` David Given
[not found] ` <4029B42F.4AED@siol.net>
0 siblings, 2 replies; 5+ messages in thread
From: Florian Zimmermann @ 2004-02-10 18:12 UTC (permalink / raw)
To: linux-8086
Hello list,
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...
TIA
Florian
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Booting with Elks
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
[not found] ` <4029B42F.4AED@siol.net>
1 sibling, 1 reply; 5+ messages in thread
From: David Given @ 2004-02-11 10:58 UTC (permalink / raw)
To: linux-8086
On Tuesday 10 February 2004 6:12 pm, Florian Zimmermann wrote:
> Hello list,
>
> 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 :(
At what stage? While the kernel is loading, or later (after the boot messages
start to appear)?
I've just tested the latest boot disk --- works fine on dosemu, pcemu and a
real PC. I don't know what the error code is, but it sounds like a floppy
disk problem. You're not using a 1.44MB formatted floppy disk in a 720kB
drive, are you?
(First time I've looked at ELKS for ages, actually. Wow, it's come on. It
actually looks usable! What's the network code like these days?)
> 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...
IIRC, it doesn't have a bootloader as such --- it uses a variant on big
Linux's old boot sector system. That is, you dd the kernel directly onto the
floppy disk; the first sector of the kernel becomes the floppy's boot sector,
and contains enough code to load the rest of the kernel into memory and run
it.
--
+- David Given --McQ-+
| dg@cowlark.com | UN-altered REPRODUCTION and DISSEMINATION of this
| (dg@tao-group.com) | IMPORTANT information is ENCOURAGED
+- www.cowlark.com --+
^ permalink raw reply [flat|nested] 5+ messages in thread
* AW: Booting with Elks
2004-02-11 10:58 ` David Given
@ 2004-02-11 11:40 ` Mario Premke
2004-02-11 11:43 ` Paul Nasrat
0 siblings, 1 reply; 5+ messages in thread
From: Mario Premke @ 2004-02-11 11:40 UTC (permalink / raw)
To: David Given, linux-8086
> -----Ursprüngliche Nachricht-----
> Von: linux-8086-owner@vger.kernel.org
> [mailto:linux-8086-owner@vger.kernel.org]Im Auftrag von David Given
> Gesendet: Mittwoch, 11. Februar 2004 11:59
> An: linux-8086@vger.kernel.org
> Betreff: Re: Booting with Elks
>
>
> On Tuesday 10 February 2004 6:12 pm, Florian Zimmermann wrote:
> > Hello list,
> >
> > 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 :(
>
> At what stage? While the kernel is loading, or later (after the
> boot messages
> start to appear)?
>
> I've just tested the latest boot disk --- works fine on dosemu,
> pcemu and a
> real PC. I don't know what the error code is, but it sounds like
> a floppy
> disk problem. You're not using a 1.44MB formatted floppy disk in a 720kB
> drive, are you?
>
> (First time I've looked at ELKS for ages, actually. Wow, it's
> come on. It
> actually looks usable! What's the network code like these days?)
Haven'd had time yet to look at the latest version. Is the compiler now
running on ELKS itself or is there still the bcc cross compiler?
Mario
-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Booting with Elks
2004-02-11 11:40 ` AW: " Mario Premke
@ 2004-02-11 11:43 ` Paul Nasrat
0 siblings, 0 replies; 5+ messages in thread
From: Paul Nasrat @ 2004-02-11 11:43 UTC (permalink / raw)
To: linux-8086
On Wed, Feb 11, 2004 at 12:40:15PM +0100, Mario Premke wrote:
> Haven'd had time yet to look at the latest version. Is the compiler now
> running on ELKS itself or is there still the bcc cross compiler?
ELKS is currently not self-hosting, you still need to use bcc to build
If you are feeling particularly adventurous you can also play with the turbo C
stuff for user space, although bcc is currently the prefered, recommended
compiler:
http://www.retepnet.it/alfmar/fhlvnr.html
Paul
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Booting with Elks
[not found] ` <1076443760.4034.28.camel@mindfsck>
@ 2004-02-11 19:02 ` Florian Zimmermann
0 siblings, 0 replies; 5+ messages in thread
From: Florian Zimmermann @ 2004-02-11 19:02 UTC (permalink / raw)
To: linux-8086
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>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-02-11 19:02 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox