public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: J Brook <jbk@postmark.net>
Cc: mythos <papadako@csd.uoc.gr>, Alan Olsen <alan@clueserver.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Matrox G400 Dualhead
Date: Fri, 30 Mar 2001 17:59:52 -0800	[thread overview]
Message-ID: <3AC53A18.C08FFC38@vc.cvut.cz> (raw)
In-Reply-To: <20010331001238.10669.qmail@venus.postmark.net>

J Brook wrote:
> 
> > Does anyone know why fualhead is not working anymore?
> > I just get a screen with rubbish on the second head.
> > Also when kernel loads and and registers fb1 I lose signal
> > on the second head.

On G400 there is no signal on second head after poweron. So you cannot
lose it ;-) On G450 there is same signal on both heads - but you are
talking about G400. Or no? They are very different (they have different
everything except PCI device ID register :-( ). You should add
'Option "UseFBDev"' into your XF86Config-4 - probably together with 
'Option "NoHWCursor"'.

> ...
> 
> >With 2.4.2 it was working just fine.
> 
> I have also noticed problems with the 2.4.3 release. I have a G450
> 32Mb, that I use in single-head mode. The console framebuffer runs
> fine at boot time, but when I load X (4.0.3 compiled with Matrox HAL
> library) and then return to the console, I get a blank screen (signal
> lost).

It is easy - do not do that. Matroxfb really does not expect that
someone
will powerdown parts of chip which matroxfb needs, but which XFree does
not use (for example clock source for secondary head) or that it will
change
some undocumented registers (for example Matrox HAL driver changes
memory
clock speed).
 
> I don't know what the problem is. I can confirm with Mythos that
> under
> 2.4.2 it was working just fine :-)

I have no idea what changed between 2.4.2 and 2.4.3 - I do not
remember that I was doing some changes into the matroxfb during
last few weeks - so maybe that source of these problems is in XFree
4.0.3 ?
					Petr Vandrovec
					vandrove@vc.cvut.cz

  reply	other threads:[~2001-03-31  2:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-31  0:12 Matrox G400 Dualhead J Brook
2001-03-31  1:59 ` Petr Vandrovec [this message]
2001-03-31  7:09 ` Rafael E. Herrera
  -- strict thread matches above, loose matches on Subject: below --
2001-05-27 22:48 mythos
2001-05-28  3:13 ` Rafael Herrera
2001-05-28  8:43   ` mythos
2001-05-28 16:16     ` Rafael Herrera
2001-04-02 22:55 Trevor Hemsley
2001-04-01 20:22 mythos
2001-04-02 17:36 ` Petr Vandrovec
2001-03-31 17:46 J Brook
2001-03-31 11:01 Trevor Hemsley
2001-04-02 17:39 ` Petr Vandrovec
2001-03-30 20:13 mythos
2001-03-30 20:45 ` Alan Olsen
2001-03-30 21:10   ` mythos

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=3AC53A18.C08FFC38@vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=alan@clueserver.org \
    --cc=jbk@postmark.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=papadako@csd.uoc.gr \
    /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