From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Benjamin Gilbert <bgilbert@backtick.net>
Cc: Ghozlane Toumi <gtoumi@messel.emse.fr>, linux-kernel@vger.kernel.org
Subject: Re: matroxfb problems with dualhead G400
Date: Tue, 4 Sep 2001 13:14:16 MET-1 [thread overview]
Message-ID: <27DB1B1012B@vcnet.vc.cvut.cz> (raw)
On 3 Sep 01 at 22:31, Benjamin Gilbert wrote:
> On Mon, Sep 03, 2001 at 02:51:44PM +0000, Petr Vandrovec (VANDROVE@vc.cvut.cz) wrote:
> > You must boot your kernel with 'video=scrollback:0'. Otherwise your
> > kernel die sooner or later... JJ's scrollback code does not cope with
> > more than one visible console, so you must disable it if you have more
> > than one display in the box.
>
> That doesn't fix it. Shift-PgUp no longer works (of course), and
> it's not immediately oopsing on me, but I still have the same type of
> intrusion onto the secondary display.
And did you run 'fbset <anymode>' on first head after secondary head
was registered? You have to... After bootup first head uses all 16MB
for picture. When you load secondary head module, videoram is split
8MB for first head/8MB for second. And because of for correct
checking driver have to scan all your VCs for picture size, and refuse
to load if any resolution is over 8MB, I just decided to put this
task on user - run 'fbset -a -depth 8' after you load secondary head
module. It will shrink '-vyres' values for primary head displays
from their current value to maximum value possible for new memory
configuration.
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2001-09-04 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 13:14 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-03 14:51 matroxfb problems with dualhead G400 Petr Vandrovec
2001-09-04 2:31 ` Benjamin Gilbert
2001-09-03 4:25 Benjamin Gilbert
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=27DB1B1012B@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=bgilbert@backtick.net \
--cc=gtoumi@messel.emse.fr \
--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