From: jurriaan <thunder7@xs4all.nl>
To: adaplas@hotpop.com, adaplas@pol.net,
linux-fbdev-devel@lists.sourceforge.net
Subject: ghosting with nvidia framebuffer (pci-e 6600), 1600x1200 and 12x22 font
Date: Wed, 6 Jul 2005 21:04:56 +0200 [thread overview]
Message-ID: <20050706190456.GA20251@amd64.of.nowhere> (raw)
I've bought myself a fine new s939 motherboard, which meant another
videocard as well. Since I couldn't get an Ati X600 running reliably
under X.org (#@#$*$ FIFO timed out errors are very frustrating, and the
only solution I found was to shut down all acceleration, which didn't
make me happy), I'm now running an Nvidia 6600.
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?
I can reproduce this almost immediately by pressing <RETURN> on the last
line of the screen, thus scrolling the screen up.
It also happens in other situations, but not often enough to be able to
say what is necessary to reproduce it.
0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0141 (rev a2) (prog-if 00 [VGA])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 217
Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=64M]
Region 1: Memory at c0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at d4000000 (64-bit, non-prefetchable) [size=16M]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] #10 [0001]
Can you think of anything I can do to resolve this? Where do I start to
look?
Thanks,
Jurriaan
--
We have engaged the Borg. The wedding will be Friday.
Debian (Unstable) GNU/Linux 2.6.13-rc1-mm1 4427 bogomips load 0.06
-------------------------------------------------------
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 reply other threads:[~2005-07-06 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 19:04 jurriaan [this message]
2005-07-20 18:33 ` ghosting with nvidia framebuffer (pci-e 6600), 1600x1200 and 12x22 font jurriaan
2005-07-22 4:03 ` Antonino A. Daplas
2005-07-22 6:35 ` Jurriaan Kalkman
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=20050706190456.GA20251@amd64.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--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).