From: Helge Hafting <helgehaf@aitel.hist.no>
To: Michael Hunold <hunold@convergence.de>
Cc: Steffen Schwientek <schwientek@web.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6-test11 framebuffer Matrox
Date: Fri, 19 Dec 2003 11:50:54 +0100 [thread overview]
Message-ID: <3FE2D80E.4070107@aitel.hist.no> (raw)
In-Reply-To: <3FE2B717.7020502@convergence.de>
Michael Hunold wrote:
> Hello Steffen,
>
>> 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.
>
>
> All I can say is "me, too". 8-(
>
>> Steffen
>
>
> Can somebody definately say if "matroxfb" is working for 2.6? I haven't
> tested it for a while, but I was surprised to find it non-working in 2.6...
The matrox framebuffer works with 2.6.0-test11 and a matrox G550.
This is statically compiled, with smp and preempt.
It dies if I use fbcon + the ruby patch (for multiple keyboard support) though.
So something is wrong - this patch changes the console but not the fb driver
so it isn't supposed to crash. I guess there's some problem with the driver
that gets triggered only in some circumstances.
Helge Hafting
next prev parent reply other threads:[~2003-12-19 10:39 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 [this message]
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
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=3FE2D80E.4070107@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=hunold@convergence.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwientek@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.