From: "Rafael E. Herrera" <raffo@neuronet.pitt.edu>
To: J Brook <jbk@postmark.net>
Cc: mythos <papadako@csd.uoc.gr>, Alan Olsen <alan@clueserver.org>,
Petr Vandrovec <vandrove@vc.cvut.cz>,
linux-kernel@vger.kernel.org
Subject: Re: Matrox G400 Dualhead
Date: Sat, 31 Mar 2001 02:09:04 -0500 [thread overview]
Message-ID: <3AC58290.3E8E76C8@neuronet.pitt.edu> (raw)
In-Reply-To: <20010331001238.10669.qmail@venus.postmark.net>
J Brook wrote:
>
> >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).
In my case, when lilo boots my G450 on any video mode other than
'normal', going into X and then back into console, leads to a blank
screen. I've observed this behavior in 2.2 and 2.4. Otherwise, I've no
problem using the card in single or dual head.
Since the HAL lib is a binary, we might have to wait for Matrox to fix
this problem.
--
Rafael
next prev parent reply other threads:[~2001-03-31 7:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-31 0:12 J Brook
2001-03-31 1:59 ` Petr Vandrovec
2001-03-31 7:09 ` Rafael E. Herrera [this message]
-- 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=3AC58290.3E8E76C8@neuronet.pitt.edu \
--to=raffo@neuronet.pitt.edu \
--cc=alan@clueserver.org \
--cc=jbk@postmark.net \
--cc=linux-kernel@vger.kernel.org \
--cc=papadako@csd.uoc.gr \
--cc=vandrove@vc.cvut.cz \
/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®