From: Andrew Walrond <andrew@walrond.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Rivafb won't work with DVI connector
Date: Fri, 19 Nov 2004 11:37:14 +0000 [thread overview]
Message-ID: <200411191137.14649.andrew@walrond.org> (raw)
I have a TFT LCD screen (1600x1200) with both D-Sub and DVI inputs, and a NV25
[GeForce4 Ti 4600] with same outputs.
Using the old D-Sub cable works fine:
rivafb: nVidia device/chipset 10DE0250
rivafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
rivafb: Detected CRTC controller 0 being used
rivafb: RIVA MTRR set to ON
rivafb: Found EDID Block from BUS 2
rivafb: setting virtual Y resolution to 83886
Console: switching to colour frame buffer device 200x75
rivafb: PCI nVidia NV25 framebuffer ver 0.9.5b (128MB @ 0xE0000000)
but with the DVI cable (dsub disconnected) I get a blank screen as soon as
rivafb takes over:
rivafb: nVidia device/chipset 10DE0250
rivafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
rivafb: Detected CRTC controller 0 being used
rivafb: RIVA MTRR set to ON
rivafb: Found EDID Block from BUS 3
EDID checksum failed, aborting
rivafb: setting virtual Y resolution to 209715
Console: switching to colour frame buffer device 80x30
rivafb: PCI nVidia NV25 framebuffer ver 0.9.5b (128MB @ 0xE0000000)
I then have to plug the d-sub back in to see the output.
[side note: 2.6.8.1 shows only garbage on reconnecting dsub, so rc2 is an
improvement.]
No I don't understand the lingo here, but I assume EDID/BUS2/BUS3 and the
checksum failure are the bits I'm interested in here.
I'm willing to do the grunt work to get this fixed, but can you guys give me a
heads up on how this stuff works, and what might be involved in a fix?
Thanks
Andrew Walrond
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next reply other threads:[~2004-11-19 11:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 11:37 Andrew Walrond [this message]
2004-11-19 22:08 ` Rivafb won't work with DVI connector Antonino A. Daplas
2004-11-20 15:52 ` Andrew Walrond
2004-11-22 0:11 ` Antonino A. Daplas
2004-11-22 9:23 ` Andrew Walrond
2004-11-22 9:43 ` Andrew Walrond
2004-11-22 22:13 ` Antonino A. Daplas
2004-11-22 23:47 ` Andrew Walrond
2004-11-22 23:54 ` Andrew Walrond
2004-11-23 1:50 ` Antonino A. Daplas
2004-11-23 12:32 ` Andrew Walrond
2004-11-23 14:28 ` Antonino A. Daplas
2004-11-23 15:09 ` Andrew Walrond
2004-11-23 15:18 ` Antonino A. Daplas
2004-11-23 16:08 ` Andrew Walrond
2004-11-23 17:07 ` Antonino A. Daplas
2004-11-23 18:01 ` Andrew Walrond
2004-11-23 18:26 ` Antonino A. Daplas
2004-11-23 19:00 ` Andrew Walrond
2004-11-23 19:07 ` Andrew Walrond
2004-11-23 19:23 ` Andrew Walrond
2004-11-23 19:59 ` Geert Uytterhoeven
2004-11-23 20:53 ` Andrew Walrond
2004-11-23 22:44 ` Antonino A. Daplas
2004-11-23 23:59 ` Andrew Walrond
2004-11-24 22:38 ` Andrew Walrond
2004-11-23 20:21 ` Chad Daelhousen
2004-11-24 23:01 ` Andrew Walrond
-- strict thread matches above, loose matches on Subject: below --
2004-11-25 0:07 Antonino A. Daplas
2004-11-25 15:27 ` Andrew Walrond
2004-11-25 21:16 ` Antonino A. Daplas
2004-11-26 14:09 ` Antonino A. Daplas
2004-11-27 12:40 ` Andrew Walrond
2004-11-27 18:29 ` Michel Dänzer
2004-11-27 22:35 ` Andrew Walrond
2004-11-27 22:43 ` 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=200411191137.14649.andrew@walrond.org \
--to=andrew@walrond.org \
--cc=adaplas@hotpop.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).