From: "H.Rosmanith (Kernel Mailing List)" <kernel@wildsau.idv.uni.linz.at>
To: kasperd@daimi.au.dk (Kasper Dupont)
Cc: root@chaos.analogic.com, kernel@wildsau.idv.uni.linz.at,
linux-kernel@vger.kernel.org, herp@wildsau.idv.uni.linz.at
Subject: Re: emm386 hangs when booting from linux
Date: Sat, 1 Mar 2003 00:43:44 +0100 (MET) [thread overview]
Message-ID: <200302282343.h1SNhiQN030734@wildsau.idv.uni.linz.at> (raw)
In-Reply-To: <3E5FF026.F892B2F7@daimi.au.dk> from Kasper Dupont at "Mar 1, 3 00:26:30 am"
> Booting DOS from Linux is not as easy as booting Linux from
> DOS. DOS relies much more on the BIOS, and the state of the
> computer as it is setup by the BIOS. What needs to be right
> for DOS to work is the contents of the BIOS data areas of
> RAM, and the interrupt vector table, and state of some of
> the hardware.
as far as I know, linux does not touch the BIOS data areas,
and "machine_real_start" sets the IDT to 0,3ff again (the
contents of the real-mode IDT are not modified by linux).
the only piece of hardware neccessary to reset was the interrupt
controller, in particular, the IRQ mapping.
> It is surprising it worked that well. You can't even boot
> DOS from DOS, DOS will have changed interrupt vectors which
> would cause a second DOS to fail. If Linux is booted from
> LOADLIN there will already be messed enough with the
interesting that you mention loadlin. when I run loadlin in a
DOS which I booted from linux, (boot linux->boot dos->boot linux),
the 2nd linux boot (by loadlin) will hang with the following message:
C:\LOADLIN> loadlin
[...]
Your current DOS/CPU configuration is:
load buffer size: 0x[*HANGING*]
This looks promising. I think I gonna download loadlin source now :-)
On the other hand, when instead of loadling MBR and executing it, I
do a far jmp to 0xf000:0xfff0 from "machine_real_start", normal
boot-procedure is exected without haning anywhere. So I think that the
bios-setup is doing some kind of initialisation/modification to whatver(!?)
which the "machine_real_start" function does not.
thanks,
herbert rosmanith
next prev parent reply other threads:[~2003-02-28 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 3:18 emm386 hangs when booting from linux H.Rosmanith (Kernel Mailing List)
2003-02-28 3:30 ` H.Rosmanith (Kernel Mailing List)
2003-02-28 22:54 ` Richard B. Johnson
2003-02-28 23:26 ` H.Rosmanith (Kernel Mailing List)
2003-02-28 23:26 ` Kasper Dupont
2003-02-28 23:43 ` H.Rosmanith (Kernel Mailing List) [this message]
2003-02-28 23:59 ` Kasper Dupont
2003-03-01 0:05 ` hr
2003-03-02 10:26 ` H.Rosmanith (Kernel Mailing List)
2003-03-02 10:29 ` H.Rosmanith (Kernel Mailing List)
2003-03-06 10:25 ` Denis Vlasenko
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=200302282343.h1SNhiQN030734@wildsau.idv.uni.linz.at \
--to=kernel@wildsau.idv.uni.linz.at \
--cc=herp@wildsau.idv.uni.linz.at \
--cc=kasperd@daimi.au.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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;
as well as URLs for NNTP newsgroup(s).