From: Miles Lane <miles@megapathdsl.net>
To: James Simmons <jsimmons@transvirtual.com>,
Fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: rivafb problems with 2.5.24 + latest fbdev.diff patch
Date: Fri, 21 Jun 2002 00:53:11 -0700 [thread overview]
Message-ID: <3D12DB67.4010007@megapathdsl.net> (raw)
Problems:
1) When I boot, when the rivafb is activated, I don't see Tux.
Instead, where Tux should be, there are about four or five text
rows that are completely white. The scrolling boot information
does appear below the white rectangle.
2) After booting, running the command "fbset -a 1600x1200-76"
causes the machine to lock up. This same command worked fine
with 2.5.22.
3) After starting up XFree86, when I switch to one of the
VTs, all characters are reversed! The lines are not reversed,
but each character is displayed flipped on its vertical axis.
4) Lastly, I have not yet figured out how to get rivafb
in the 2.5 series to boot directly into 1600x1200x16 @ 76Hz.
Thus far, running "fbset -a 1600x1200-76" has worked.
I tried using video=riva:1600x1200-76 and that partly worked.
It got me the resolution I wanted, but the colors were wrong
and the frequency was off:
mode "1600x1200-60"
# D: 162.022 MHz, H: 75.010 kHz, V: 60.008 Hz
geometry 1600 1200 1600 1200 16
timings 6172 304 64 46 1 192 3
hsync high
vsync high
accel true
rgba 5/11,6/5,5/0,0/0
endmode
Running "fbset -a 1600x1200-76" has been giving me:
mode "1600x1200-76"
# D: 197.981 MHz, H: 95.183 kHz, V: 76.146 Hz
geometry 1600 1200 1600 1200 8
timings 5051 304 40 42 3 136 5
accel true
rgba 8/0,8/0,8/0,0/0
endmode
I was then informed that I should use "video=riva:1600x1200@75-16",
since there is no 76Hz entry in linux/drivers/video/modedb.c.
Here's the modedb.c entry I am trying to use:
/* 1600x1200 @ 75 Hz, 93.75 kHz hsync */
NULL, 75, 1600, 1200, 4938, 304, 64, 46, 1, 192, 3,
FB_SYNC_HOR_HIGH_ACT|FB_SYNC_VERT_HIGH_ACT, FB_VMODE_NONINTERLACED
Boot command:
kernel /vmlinuz ro root=/dev/hda6 hdd=ide-scsi console=ttyS0,38400 console=tty0 pci=noacpi video=riva:1600x1200@75-16
Kernel log section showing console setup:
Jun 21 00:03:48 turbulence kernel: rivafb: RIVA MTRR set to ON
Jun 21 00:03:48 turbulence kernel: Console: switching to colour frame buffer device 80x25
Jun 21 00:03:48 turbulence kernel: rivafb: PCI nVidia NV10 framebuffer ver 0.9.3 (nVidiaGeForce-DD, 32MB @ 0xE8000000)
Portions of lspci output that may pertain:
01:05.0 VGA compatible controller: nVidia Corporation GeForce 256 DDR (rev 10) (prog-if 00 [VGA])
Subsystem: VISIONTEK: Unknown device 000b
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e8000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at feaf0000 [disabled] [size=64K]
Capabilities: [60] Power Management version 1
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 2.0
Status: RQ=31 SBA- 64bit- FW+ Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] System Controller (rev 25)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 64
Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
Region 1: Memory at fc9ff000 (32-bit, prefetchable) [size=4K]
Region 2: I/O ports at ffe4 [disabled] [size=4]
Capabilities: [a0] AGP version 1.0
Status: RQ=15 SBA+ 64bit- FW- Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP Bridge (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fca00000-feafffff
Prefetchable memory behind bridge: e4800000-f48fffff
BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-756 [Viper] ACPI (rev 03)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
.config info:
CONFIG_MK7=y
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_RIVA=y
CONFIG_FBCON_ACCEL=y
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
next reply other threads:[~2002-06-21 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 7:53 Miles Lane [this message]
2002-06-27 20:24 ` rivafb problems with 2.5.24 + latest fbdev.diff patch James Simmons
2002-06-28 0:28 ` Miles Lane
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=3D12DB67.4010007@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=jsimmons@transvirtual.com \
--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).