linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Zielinski <grim@undead.cc>
To: Thomas Winischhofer <thomas@winischhofer.net>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: fbcon or sisfb problem?
Date: Thu, 27 May 2004 22:32:34 -0400	[thread overview]
Message-ID: <40B6A4C2.80708@undead.cc> (raw)
In-Reply-To: <40B6874E.8070200@winischhofer.net>

Thomas Winischhofer wrote:

> 1) Upon start (be it in kernel, be it upon modprobe), I see a big 
> white rectangle. It seems that this rectangle's size matches exactly 
> the size of the previous console area. I have seen reports of similar 
> problems since late 2003. Any progress on this? (I have digged around 
> in the fbcon code but got lost at some time.)
>
I get something similar when using the radeonfb driver except that I get 
mulit-colored garbage on the screen instead of solid white.  The 
difference is probably due to the different ways that radeonfb and sisfb 
remap the VGA memory layout.  I posted a fix in a post titled "Console 
takeover screen corruption issue" a while back on this list.

Could you see if that patch fixes your problem?  If enough people test 
it we could probably get it included into the kernel.

John




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click

  reply	other threads:[~2004-05-28  2:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28  0:26 fbcon or sisfb problem? Thomas Winischhofer
2004-05-28  2:32 ` John Zielinski [this message]
2004-05-28 14:52   ` Thomas Winischhofer
2004-05-28 23:52     ` John Zielinski

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=40B6A4C2.80708@undead.cc \
    --to=grim@undead.cc \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=thomas@winischhofer.net \
    /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).