From: Andrew Walrond <andrew@walrond.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Rivafb won't work with DVI connector
Date: Sat, 20 Nov 2004 15:52:53 +0000 [thread overview]
Message-ID: <200411201552.53919.andrew@walrond.org> (raw)
In-Reply-To: <200411200608.30821.adaplas@hotpop.com>
[-- Attachment #1: Type: text/plain, Size: 3686 bytes --]
On Friday 19 Nov 2004 22:08, Antonino A. Daplas wrote:
> On Friday 19 November 2004 19:37, Andrew Walrond wrote:
> > 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.
>
> You can try the following:
>
> 1. turn on verbose debug output in drivers/video/fbmon.c
Done; but nothing gets displayed when checksum fails. Displays lots of nice
stuff with dsub connection though :)
>
> 2. Try just grabbing the EDID from BUS2, since the EDID checksum failed
> from BUS3.
Ok - I modified riva_get_EDID_i2c to probe only BUS 2, but the checksum still
fails unless the dsub is (also) connected. Infact, I hard coded each bus, 1-3
in turn. With just DVI connected, the returned EDID failed the checksum for
all three buses. With the Dsub connected, I got valid EDID's on BUS 1 and 2,
and a message saying none was available on BUS 3.
I cannot get a DVI display, whatever I try. I have also tried various
combinations of video:rivafb:forceCRTC=0/1 and video:rivafb:flatpanel, all to
no effect (flatpanel gives me a corrupt dsub display)
>
> 3. if you can, send me your EDID block. You can use the utility
> 'read-edid'.
EDID attached. Parsed output:
./read-edid-1.4.1/parse-edid: parse-edid version 1.4.1
./read-edid-1.4.1/parse-edid: EDID checksum passed.
# EDID version 1 revision 3
Section "Monitor"
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
Identifier "iiyama "
VendorName "IVM"
ModelName "iiyama "
# Block type: 2:0 3:fd
HorizSync 30-80
VertRefresh 56-85
# Max dot clock (video bandwidth) 170 MHz
# Block type: 2:0 3:fc
# DPMS capabilities: Active off:yes Suspend:yes Standby:yes
Mode "1024x768" # vfreq 59.196Hz, hfreq 48.363kHz
DotClock 65.000000
HTimings 1024 1040 1104 1344
VTimings 768 781 783 817
Flags "-HSync" "-VSync"
EndMode
Mode "1600x1200" # vfreq 60.000Hz, hfreq 75.000kHz
DotClock 162.000000
HTimings 1600 1664 1856 2160
VTimings 1200 1201 1204 1250
Flags "+HSync" "+VSync"
EndMode
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
EndSection
[-- Attachment #2: edid.dsub.32 --]
[-- Type: application/octet-stream, Size: 128 bytes --]
next prev parent reply other threads:[~2004-11-20 15:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 11:37 Rivafb won't work with DVI connector Andrew Walrond
2004-11-19 22:08 ` Antonino A. Daplas
2004-11-20 15:52 ` Andrew Walrond [this message]
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=200411201552.53919.andrew@walrond.org \
--to=andrew@walrond.org \
--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 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.