From: Dirk Henning Gerdes <mail@dirk-gerdes.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: dirty artefacts on bootup
Date: Tue, 06 Dec 2005 13:25:27 +0100 [thread overview]
Message-ID: <1133871927.5595.8.camel@noti> (raw)
Hi Benjamin,
I'm using the radeon framebuffer driver on a sony-notebook with a radeon
9200 mobile.
During bootup I get dirty artefacts on the screen.
It's hard to explain. The text first is clear on the screen, but then
there come so many dirty lines on top of it, that you cannot read
anything.
When the xserver is started, the problem is away. switching to a console
with [Alt][CTRL][F1] works perfectly. And then you can read the text
normally.
I have compiled the driver with the debug-option, which brought the
following output.
I'm not quite sur, if this can help, because I got it, when the console
worked after starting X.
[ 148.839846] hStart = 1040, hEnd = 1176, hTotal = 1344
[ 148.839851] vStart = 770, vEnd = 776, vTotal = 806
[ 148.839855] h_total_disp = 0x7f00ync_strt_wid = 0x11040a
[ 148.839858] v_total_disp = 0x2ff0325noti login: [ 148.839846] hStart
= 1040, hEnd = 1176, hTotal = 1344
[ 148.839851] vStart = 770, vEnd = 776, vTotal = 806
[ 148.839855] h_total_disp = 0x7f00a7ync_strt_wid = 0x60301
[ 148.839860] pixclock = 15384
[ 148.839862] freq = 6500
Is there anything I can do to get this dirty lines away?
Thanks for your help
Dirk
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-12-06 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 12:25 Dirk Henning Gerdes [this message]
2005-12-06 21:05 ` dirty artefacts on bootup Benjamin Herrenschmidt
2005-12-08 22:12 ` Dirk Henning Gerdes
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=1133871927.5595.8.camel@noti \
--to=mail@dirk-gerdes.de \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.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).