From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: please explain to me why video/bios shadowing must be disabled to use graphics...
Date: Tue, 24 Sep 2002 05:20:12 +0400 [thread overview]
Message-ID: <3D8FBDCC.5050800@yahoo.com> (raw)
Hello.
Bart Oldeman wrote:
>> > c000:0003
>> Where does it do that? I have found only
>> init_vga_card(), but that doesn't seem to be
>> the place. Also I searched the +g log for
>> c000:0003 and found nothing...
> src/base/bios/bios.S, line 507, F800:4200.
> init_vga_card() pushes f800:4200 on the stack as cs:ip, so that is what
> DOSEMU gets to execute in the next vm86().
Which means that I've found the proper place not
even realising it:)
Now I also tried to nop out the hardcoded call
directly in bios.S - same effect - no graphics
modes, no even any other text modes, terminal
chars here etc. Only the progs that are setting
modes directly via ports are still working.
Doing the reset call from within DOS brings
everything back in a sane state.
Just wondering, why this reset is needed so badly?
>> > Some people reported black screens, or even machines hanging which
>> > happens when the VBIOS init routine is called.
>> Of course, that was me:) But does the problem still
>> exist after 1.1.3.1?
> Maybe, maybe not?
Hmm, my point was that having only the VGA regs
in hands, it is not possible to lock up the entire
system. Or is it? But then it would be possible
to lock also NT, isn't it?
> It wasn't clear to me whether they used terminal mode or not. Probably
> missed something :(
Well, at least the vbios init was not passed, hence
the term chars.
>> list:( That is why, I think, XFree 3.3.6 or 4.1 are not
>> able to set any VESA modes, but not the 4.2, which can!
> using VBE 3.0?
What advantages of VBE 3 are you suspecting?
Any chances to find this out without looking into an
XFree sources? Oh well, I just have to look there and
find out all the answers myself, but it is a big pain to
download the entire XFree sources...
Btw, I also played with LRMI package. There is a
program to set the VESA modes. It does iopl(3) and
then int10 in vm86(). Locks up as well...
next reply other threads:[~2002-09-24 1:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 1:20 Stas Sergeev [this message]
2002-09-24 2:18 ` please explain to me why video/bios shadowing must be disabled to use graphics Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 4:22 Stas Sergeev
2002-09-24 13:20 Stas Sergeev
2002-09-23 22:12 Stas Sergeev
2002-09-23 23:11 ` Bart Oldeman
2002-09-23 20:52 Stas Sergeev
2002-09-23 21:14 ` Bart Oldeman
2002-10-01 0:19 ` phrostie
2002-09-24 10:31 ` phrostie
2002-09-21 22:43 Stas Sergeev
2002-09-09 4:09 matt
2002-09-09 11:26 ` phrostie
2002-09-20 20:57 ` matt
2002-09-20 21:29 ` Bart Oldeman
[not found] ` <Pine.GSO.4.05.10209202215490.18306-100000@sh.enm.bris.ac.u k>
2002-09-20 23:37 ` matt
2002-09-21 5:21 ` Pat
2002-09-10 2:08 ` Pat
[not found] ` <Pine.LNX.4.44.0209091837470.20167-100000@feather.sunbird.s ys>
2002-09-20 20:52 ` matt
2002-09-21 4:53 ` Pat
[not found] ` <Pine.LNX.4.44.0209201954350.30609-100000@feather.sunbird.s ys>
2002-09-21 8:42 ` matt
2002-09-21 16:04 ` Bart Oldeman
2002-09-23 17:33 ` phrostie
2002-09-23 19:25 ` Bart Oldeman
[not found] ` <Pine.GSO.4.05.10209211648440.21069-100000@sh.enm.bris.ac.u k>
2002-09-21 20:08 ` matt
2002-09-22 20:46 ` Pat
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=3D8FBDCC.5050800@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox