From: "Jurriaan Kalkman" <jurriaan@rivierenland.xs4all.nl>
Cc: linux-fbdev-devel@lists.sourceforge.net,
jurriaan <thunder7@xs4all.nl>,
adaplas@hotpop.com, adaplas@pol.net
Subject: Re: ghosting with nvidia framebuffer (pci-e 6600), 1600x1200 and 12x22 font
Date: Fri, 22 Jul 2005 08:35:46 +0200 (CEST) [thread overview]
Message-ID: <20129.194.178.120.170.1122014146.squirrel@194.178.120.170> (raw)
In-Reply-To: <200507221203.31810.adaplas@gmail.com>
> On Thursday 07 July 2005 03:04, jurriaan wrote:
>> Kernel command line: root=/dev/hda1 video=nvidiafb:1600x1200-32@85
>> atkbd.softrepeat=1
>>
>> nvidiafb: nVidia device/chipset 10DE0141
>> nvidiafb: PCI device 10de:0141 (nVidia Corporation)
>> nvidiafb: CRTC0 found
>> nvidiafb: CRTC1 found
>> nvidiafb: CRTC 0 appears to have a CRT attached
>> nvidiafb: Using CRT on CRTC 0
>> nvidiafb: MTRR set to ON
>> Console: switching to colour frame buffer device 133x54
>> nvidiafb: PCI nVidia NV14 framebuffer (64MB @ 0xC0000000)
>>
>> I'm running at 1600x1200 resolution with the 12x22 font, and a
>> 2.6.13-rc1-mm1 kernel.
>>
>> A strange effect is noticeable: often characters from the left of the
>> screen are ghosted on the right of the screen. Not all of the pixels
>> that form a character, but enough to be visible. To my best knowledge,
>> the ghosting starts at column 85, and 85 * 12 = 1020, which may mean
>> some sort of erroneous wrap-around at pixel 1024 is taking place?
>>
> It looks like a timings problem. Are the effects still present if you try
> to change modes?
I'll try that later tonight, when I'm home again.
However, whatever corruption is on screen, when I switch virtual consoles
from tty1 to 2 and back (alt-f2 alt-f1), it disappears completely. Until I
force the screen to scroll up by pressing return at the last line, then
they reappear again.
If it was a timings problem, I wouldn't expect switching virtual consoles
to remedy it, nor scrolling the screen up to reproduce it.
>
> Based on the dmesg snippet, I don't think the driver was able to grab the
> edid. Which means that the mode 1600x1200 was taken from the default
> modedb which may not be correct for your hardware.
It's an Eizo F931 monitor, capable of running 1800x1440@85 without any
trouble in X.org (where no corruption at all is evident, BTW). The monitor
is connected through a Vista Rose KVM switch. IIRC, x.org did manage to
get EDID info, I'll also post that log.
>
> If you can, grab X's modeline using xvidtune, then convert it into a fb
> compatible modeline, enter it in /etc/fb.modes then use fbset to change
> your
> video mode.
>
I'll try that and get back to you, but I'm not convinced it's timing. I
seem to remember disabling all acceleration also fixed the corruption. I
will also test that.
Todo:
1) change modes
2) x.org log wrt. EDID
3) noaccell
4) different fontsize
Thanks,
Jurriaan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-22 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 19:04 ghosting with nvidia framebuffer (pci-e 6600), 1600x1200 and 12x22 font jurriaan
2005-07-20 18:33 ` jurriaan
2005-07-22 4:03 ` Antonino A. Daplas
2005-07-22 6:35 ` Jurriaan Kalkman [this message]
2005-07-22 13:22 ` Antonino A. Daplas
2005-07-22 13:29 ` jurriaan
2005-07-22 14:05 ` Antonino A. Daplas
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=20129.194.178.120.170.1122014146.squirrel@194.178.120.170 \
--to=jurriaan@rivierenland.xs4all.nl \
--cc=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=thunder7@xs4all.nl \
/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).