From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Terminal Video Problem Solved (and sound too!)
Date: Mon, 02 Dec 2002 13:42:55 +0300 [thread overview]
Message-ID: <3DEB392F.4050504@yahoo.com> (raw)
Hello.
Mushroom wrote:
>> OK, try the attached patch.
> That's fixed it!!!
Great!
Hmm, that was just too easy, there
is still something fishy about that.
Do you have $_pci option disabled
or enabled?
If it is enabled, could you try to undo
the patch, set $_pci=(off) and reproduce
the problem?
Oh, please, do that carefully this time:)
The suggested way would be to just
erase and re-install the entire 1.1.3
sources with 1.1.3.7 patchset (1.1.3.7
patchset is an essential part here, as
1.1.3.0 have its own problems with some
video boards). You may also use a default
dosemu.conf as $_pci is disabled there.
That way the chances of any mistake are
minimized.
I want to be certain that it is not a
$_pci option guilty for your problems at
a first place.
> The graphic card details no longer come up when dosemu starts
Yes, it was printed by the POST routines,
which are now bypassed.
> The console is left in video mode
Could you elaborate on that?
This happens only when you terminate dosemu
while in graphics mode, right? How exactly
are you terinating it?
I've never seen such a strange behaveour
here with my Radeon unless I was playing
with VESA (which is disabled for most
dosemu users including you).
next reply other threads:[~2002-12-02 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 10:42 Stas Sergeev [this message]
2002-12-02 21:02 ` Terminal Video Problem Solved (and sound too!) Mushroom
2002-12-02 21:33 ` Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 16:12 Stas Sergeev
2002-12-02 22:24 Stas Sergeev
2002-12-03 5:27 ` Mushroom
2002-12-01 18:37 Newbie with terminal video problems Stas Sergeev
2002-12-01 23:47 ` Terminal Video Problem Solved (and sound too!) Mushroom
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=3DEB392F.4050504@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