From: nick black <dank@suburbanjihad.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6-test11 framebuffer Matrox
Date: Fri, 19 Dec 2003 16:28:01 +0000 (UTC) [thread overview]
Message-ID: <brv8uh$but$1@sea.gmane.org> (raw)
In-Reply-To: 200312190314.13138.schwientek@web.de
In article <200312190314.13138.schwientek@web.de>, Steffen Schwientek wrote:
> My Matrox-framebuffer is not working properly. Build direct into the
> kernel, the monitor will be black with some stripes at startup, just the
> reset button works.
> Build as a modules, the same happens if I load the module.
I've managed to get my AGP G400 working in the following setups under
2.6.0 since -test7:
with Petr's patch, reverting to 2.4 interfaces:
video=matroxfb:vesa:0x1bb gives me a great fbcon. I can either use
X's fbdev driver at the same resolution, or the mga driver at any
resolution, with no problems.
without Petr's patch:
video=matroxfb:vesa:0x1bb gives me a great fbcon. I can only use
X's fbdev driver at the same resolution; the mga driver at any
resolution causes massive console corruption upon switching from X to
console and causing any screen changes. Also, I get a large white
block underneath the logo on boot.
--
nick black <dank@reflexsecurity.com>
"np: nondeterministic polynomial-time
the class of dashed hopes and idle dreams." - the complexity zoo
next prev parent reply other threads:[~2003-12-19 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 2:14 2.6-test11 framebuffer Matrox Steffen Schwientek
2003-12-19 8:30 ` Michael Hunold
2003-12-19 10:50 ` Helge Hafting
2003-12-19 21:37 ` Tomasz Torcz
2003-12-20 7:36 ` Ed Sweetman
2003-12-20 21:58 ` Helge Hafting
2003-12-21 18:22 ` Tomasz Torcz
2003-12-19 8:47 ` Michael Hunold
2003-12-19 16:29 ` nick black
2003-12-19 9:41 ` Gábor Lénárt
2003-12-19 16:28 ` nick black [this message]
2003-12-21 17:51 ` Gábor Lénárt
-- strict thread matches above, loose matches on Subject: below --
2003-12-19 8:54 rwhron
2003-12-19 18:50 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='brv8uh$but$1@sea.gmane.org' \
--to=dank@suburbanjihad.net \
--cc=dank@reflexsecurity.com \
--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