From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Armin <Zoup@zoup.org>
Cc: linux-kernel@vger.kernel.org, unki@netshadow.at
Subject: Re: FrameBuffer Problem With 2.6.0
Date: Fri, 19 Dec 2003 14:29:36 +0200 [thread overview]
Message-ID: <2CA1166592F@vcnet.vc.cvut.cz> (raw)
On 18 Dec 03 at 23:29, Armin wrote:
> On Thursday 18 December 2003 00:35, Andreas Unterkircher wrote:
> > I had similar the same Problem... i fixed it when i also put the
>
> i have compile kernel with vga fonts , Still are not working ...
And did you enable framebuffer console support in Device Drivers ->
Graphics Support -> Console display driver support -> Framebuffer Console
Support ? It looks to me like that you did not enabled this, and so you
get hardware in graphics mode (when fbdev loads), but no text there (as
there is no fbcon in your kernel). 2.6.x kernel has strange idea
that non-embedded users need fbdev without fbcon by default...
I'm not aware about any problems with matroxfb driver in Linus kernel
except that you should use 'video=matroxfb:nopan' to avoid problems
with default resolution XXXx65536 (or clip vyres yourself to reasonable
value). Of course all 2.6.x fbdev limits apply also to matroxfb driver.
If you want interface compatible with 2.4.x, you'll have to get patch
from ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/matroxfb-2.6.0.gz
(only vgacon, matroxfb and vesafb are tested).
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2003-12-19 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 12:29 Petr Vandrovec [this message]
2003-12-20 21:41 ` FrameBuffer Problem With 2.6.0 Zwane Mwaikambo
2003-12-20 22:54 ` Armin
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 21:54 Armin
2003-12-18 9:35 ` Andreas Unterkircher
2003-12-19 8:29 ` Armin
2003-12-18 23:22 ` Davidlohr Bueso A.
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=2CA1166592F@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=Zoup@zoup.org \
--cc=linux-kernel@vger.kernel.org \
--cc=unki@netshadow.at \
/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