From: "Michel Eyckmans (MCE)" <mce@pi.be>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: nick black <dank@suburbanjihad.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 + matroxfb = unuusable VC
Date: Thu, 24 Jul 2003 01:05:38 +0200 [thread overview]
Message-ID: <200307232305.h6NN5cKH027682@jebril.pi.be> (raw)
In-Reply-To: Your message of "Mon, 21 Jul 2003 16:02:27 EDT." <20030721200227.GA789@suburbanjihad.net>
Greetz,
> > In this case, does it happen if you exit X, or only if you are switching
> > to the console while X are active? If it happens only in second case, then
> > it is bug (I believe fixed long ago) in XFree mga driver: it was sometime
>
> it is the latter case, thanks for the info! regardless, the 2.6.0-test1
> problems continue; i'll update my x this evening if my version doesn't
> contain the fix.
After reading this, I enthousiastically upgraded from Xfree 4.2.0 to
4.3.0, but nothing changed. :-( The problem is indeed X-related, but
refuses to go away after the upgrade.
Also, I've had 4.2.0 and several earlier X versions working just fine
with the "old" matroxfb in the same setup that I'm using now. Was there
a bug workaround for this issue in the old driver? If so, is there any
hope of it returning?
MCE
next prev parent reply other threads:[~2003-07-23 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 18:44 2.6.0-test1 + matroxfb = unuusable VC Petr Vandrovec
2003-07-21 20:02 ` nick black
2003-07-23 23:05 ` Michel Eyckmans (MCE) [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-24 23:23 Petr Vandrovec
2003-07-23 23:50 Petr Vandrovec
2003-07-24 22:17 ` Michel Eyckmans (MCE)
2003-07-25 0:07 ` James Simmons
2003-07-26 10:33 ` Michel Eyckmans (MCE)
2003-07-25 12:20 ` nick black
2003-07-21 18:10 Petr Vandrovec
2003-07-21 18:33 ` nick black
2003-07-18 22:39 Michel Eyckmans (MCE)
2003-07-19 6:02 ` Jurriaan
2003-07-21 17:45 ` nick black
2003-07-24 23:39 ` James Simmons
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=200307232305.h6NN5cKH027682@jebril.pi.be \
--to=mce@pi.be \
--cc=VANDROVE@vc.cvut.cz \
--cc=dank@suburbanjihad.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;
as well as URLs for NNTP newsgroup(s).