From: Pawel Golaszewski <blues@ds.pg.gda.pl>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [2.5.63 and prior] Voodoo3 framebuffer bug
Date: Sat, 01 Mar 2003 00:19:44 +0100 [thread overview]
Message-ID: <3E5FEE90.8040404@ds.pg.gda.pl> (raw)
Kernel is compiled with gcc version 2.95.4 20010319 (prerelease)
That bug was in previous versions too.
I've got Voodoo3:
01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev
01) (prog-if 00 [VGA])
Subsystem: 3Dfx Interactive, Inc. Voodoo3 AGP
Flags: 66Mhz, fast devsel, IRQ 11
Memory at e4000000 (32-bit, non-prefetchable) [size=32M]
Memory at e8000000 (32-bit, prefetchable) [size=32M]
I/O ports at c000 [size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [54] AGP version 1.0
Capabilities: [60] Power Management version 1
Framebuffer works really strange.
- when I start it in 1024x768-16@75 I have strange colours: background
is brown-red, other colors are not good too (techno-like style). See
dump from 1024x768 16bit: http://piorun.ds.pg.gda.pl/~blues/dump.bz2
I don't know how to make screenshot on console better, sorry...
- I can't set other refresh rates than 60Hz - from lilo I've passed
append="video=tdfx:1024x768-16@75", but I've became 60Hz set.
- when I set resolution with fbset to i.e. 1280x1024 I have resolution
changed but avaible area is in old size.
- when I set resolution to other than passed from lilo: when I switch
from X, my screen is completely not usable. Manual setting resolution
(without visibility) makes it usable again - until next switch.
P.S.: sorry for my english - I hope you understand what I mean...
--
pozdr. Paweł Gołaszewski
blues<at>ds.pg.gda.pl
reply other threads:[~2003-02-28 23:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E5FEE90.8040404@ds.pg.gda.pl \
--to=blues@ds.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.