From: Benjamin Gilbert <bgilbert@backtick.net>
To: linux-kernel@vger.kernel.org
Subject: matroxfb problems with dualhead G400
Date: Mon, 3 Sep 2001 00:25:18 -0400 [thread overview]
Message-ID: <20010903002518.A12008@ostrich.andrew.cmu.edu> (raw)
I've been trying to set up dualhead text console with matroxfb and a
16MB G400, with mixed success. What I think I'm seeing is that the
scrollback from the primary head, when it gets long enough (i.e., cat
/boot/System.map), intrudes on the secondary head. If the secondary
head is set to the same resolution and bit depth as the primary, I
can (sometimes) actually see the scrollback text go by on the
secondary. The rest of the time, I just get garbage on the
secondary. Scrolling text on the second head, OTOH, does not affect
the primary head. Occasionally, scrolling text on the primary head
will cause a kernel oops, although this isn't consistent; it happens
less than 25% of the time.
I've tried various combinations of video resolutions and matroxfb
boot-time options, but haven't really determined anything conclusive.
The problem lasts from boot until the first time that the fbdev
resolution is changed on the primary monitor; then the problem goes
away. This seems to be true regardless of the initial resolution of
the primary monitor. Setting "video=matroxfb:nopan" makes the
problem rarer, but it still seems to pop up occasionally -- I oopsed
once while testing this.
All of this is before starting XFree86, so X isn't a factor here.
Kernel is vanilla 2.4.9. Let me know what other information you need
from me.
Thanks in advance
--Benjamin Gilbert
next reply other threads:[~2001-09-03 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 4:25 Benjamin Gilbert [this message]
2001-09-03 14:51 Petr Vandrovec
2001-09-04 2:31 ` Benjamin Gilbert
2001-09-04 13:14 Petr Vandrovec
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=20010903002518.A12008@ostrich.andrew.cmu.edu \
--to=bgilbert@backtick.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®