linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: Rivafb won't work with DVI connector
Date: Tue, 23 Nov 2004 18:01:14 +0000	[thread overview]
Message-ID: <200411231801.14328.andrew@walrond.org> (raw)
In-Reply-To: <200411240107.13362.adaplas@hotpop.com>

On Tuesday 23 Nov 2004 17:07, Antonino A. Daplas wrote:
>
> Okay, I think I this should fix the dvi misdetection, and I think it should
> also fix the preferred timing of 1600x1200 even if both dsub and dvi are
> attached.  Try the attached patch.
>

Not quite, but close...

With just dsub and no params, we get a perfect 1600x1200 (200x75) console

nvidiafb: nVidia device/chipset 10DE0250
nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
i2c_adapter i2c-0: registered as adapter #0
i2c_adapter i2c-1: registered as adapter #1
i2c_adapter i2c-2: registered as adapter #2
nvidiafb: CRTC0 not found
nvidiafb: CRTC1 found
i2c_adapter i2c-0: master_xfer: with 2 msgs.
i2c_adapter i2c-0: master_xfer: with 2 msgs.
i2c_adapter i2c-0: master_xfer: with 2 msgs.
i2c_adapter i2c-1: master_xfer: with 2 msgs.
nvidiafb: EDID found from BUS2
========================================
Display Information (EDID)
========================================
   EDID Version 1.3
   Manufacturer: IVM
   Model: 4800
   Serial#: 95
   Year: 2001 Week 44
   Monitor Name: iiyama
   Monitor Name: AU4831D
   Display Characteristics:
      Monitor Operating Limits: From EDID
           H: 24-80KHz V: 50-85Hz DCLK: 170MHz
      Analog Display Input: Input Voltage - 0.700V/0.000V
      Sync: Separate Composite
      Max H-size in cm: 39
      Max V-size in cm: 29
      Gamma: 2.20
      DPMS: Active yes, Suspend yes, Standby yes
      RGB Color Display
      Chroma
         RedX:     0.619 RedY:     0.340
         GreenX:   0.279 GreenY:   0.600
         BlueX:    0.140 BlueY:    0.090
         WhiteX:   0.289 WhiteY:   0.300
      First DETAILED Timing is preferred
   Supported VESA Modes
      720x400@70Hz
      640x480@60Hz
      640x480@67Hz
      640x480@72Hz
      640x480@75Hz
      800x600@56Hz
      800x600@60Hz
      800x600@72Hz
      800x600@75Hz
      832x624@75Hz
      1024x768@60Hz
      1024x768@70Hz
      1024x768@75Hz
      1280x1024@75Hz
      Manufacturer's mask: 0
   Standard Timings
      1600x1200@60Hz
      1280x1024@60Hz
      1280x1024@70Hz
      1152x864@75Hz
      1152x864@85Hz
      1024x768@66Hz
      1024x768@70Hz
      1024x768@85Hz
   Detailed Timings
      162 MHz 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync

========================================
nvidiafb: CRTC 0appears to have a CRT attached
nvidiafb: Using CRT on CRTC 0
nvidiafb: MTRR set to ON
Console: switching to colour frame buffer device 200x75
nvidiafb: PCI nVidia NV25 framebuffer (128MB @ 0xE0000000)


With both dsub and dvi, another perfect 1600x1200 console. (first EDID 
truncated due to dmesg log not big enough; I can fix this if you need)

      1024x768@60Hz
      1024x768@70Hz
      1024x768@75Hz
      1280x1024@75Hz
      1152x870@75Hz
      Manufacturer's mask: 0
   Standard Timings
      1280x1024@60Hz
      1024x819@85Hz
      800x640@85Hz
      640x512@85Hz
   Detailed Timings
      65 MHz 1024 1040 1104 1344 768 781 783 817 -HSync -VSync

      162 MHz 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync

========================================
i2c_adapter i2c-1: master_xfer: with 2 msgs.
nvidiafb: EDID found from BUS2
========================================
Display Information (EDID)
========================================
   EDID Version 1.3
   Manufacturer: IVM
   Model: 4800
   Serial#: 95
   Year: 2001 Week 44
   Monitor Name: iiyama
   Monitor Name: AU4831D
   Display Characteristics:
      Monitor Operating Limits: From EDID
           H: 24-80KHz V: 50-85Hz DCLK: 170MHz
      Analog Display Input: Input Voltage - 0.700V/0.000V
      Sync: Separate Composite
      Max H-size in cm: 39
      Max V-size in cm: 29
      Gamma: 2.20
      DPMS: Active yes, Suspend yes, Standby yes
      RGB Color Display
      Chroma
         RedX:     0.619 RedY:     0.340
         GreenX:   0.279 GreenY:   0.600
         BlueX:    0.140 BlueY:    0.090
         WhiteX:   0.289 WhiteY:   0.300
      First DETAILED Timing is preferred
   Supported VESA Modes
      720x400@70Hz
      640x480@60Hz
      640x480@67Hz
      640x480@72Hz
      640x480@75Hz
      800x600@56Hz
      800x600@60Hz
      800x600@72Hz
      800x600@75Hz
      832x624@75Hz
      1024x768@60Hz
      1024x768@70Hz
      1024x768@75Hz
      1280x1024@75Hz
      Manufacturer's mask: 0
   Standard Timings
      1600x1200@60Hz
      1280x1024@60Hz
      1280x1024@70Hz
      1152x864@75Hz
      1152x864@85Hz
      1024x768@66Hz
      1024x768@70Hz
      1024x768@85Hz
   Detailed Timings
      162 MHz 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync

========================================
nvidiafb: CRTC 0appears to have a CRT attached
nvidiafb: Using CRT on CRTC 0
nvidiafb: MTRR set to ON
Console: switching to colour frame buffer device 200x75



With dvi connection and no params, I get a fully working console, but at 
1024x768 (128x48)

nvidiafb: nVidia device/chipset 10DE0250
nvidiafb: nVidia Corporation NV25 [GeForce4 Ti 4600]
i2c_adapter i2c-0: registered as adapter #0
i2c_adapter i2c-1: registered as adapter #1
i2c_adapter i2c-2: registered as adapter #2
nvidiafb: CRTC0 not found
nvidiafb: CRTC1 not found
i2c_adapter i2c-0: master_xfer: with 2 msgs.
nvidiafb: EDID found from BUS1
========================================
Display Information (EDID)
========================================
   EDID Version 1.3
   Manufacturer: IVM
   Model: 4800
   Serial#: 1001
   Year: 2002 Week 1
   Monitor Name: iiyama
   Display Characteristics:
      Monitor Operating Limits: From EDID
           H: 30-80KHz V: 56-85Hz DCLK: 170MHz
      Digital Display Input
      Sync: Serration on
      Max H-size in cm: 39
      Max V-size in cm: 29
      Gamma: 2.20
      DPMS: Active yes, Suspend yes, Standby yes
      RGB Color Display
      Chroma
         RedX:     0.619 RedY:     0.340
         GreenX:   0.279 GreenY:   0.600
         BlueX:    0.140 BlueY:    0.090
         WhiteX:   0.289 WhiteY:   0.300
      First DETAILED Timing is preferred
   Supported VESA Modes
      720x400@70Hz
      640x480@60Hz
      640x480@67Hz
      640x480@72Hz
      640x480@75Hz
      800x600@56Hz
      800x600@60Hz
      800x600@72Hz
      800x600@75Hz
      832x624@75Hz
      1024x768@60Hz
      1024x768@70Hz
      1024x768@75Hz
      1280x1024@75Hz
      1152x870@75Hz
      Manufacturer's mask: 0
   Standard Timings
      1280x1024@60Hz
      1024x819@85Hz
      800x640@85Hz
      640x512@85Hz
   Detailed Timings
      65 MHz 1024 1040 1104 1344 768 781 783 817 -HSync -VSync

      162 MHz 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync

========================================
i2c_adapter i2c-1: master_xfer: with 2 msgs.
i2c_adapter i2c-1: master_xfer: with 2 msgs.
i2c_adapter i2c-1: master_xfer: with 2 msgs.
nvidiafb: CRTC 1 is currently programmed for DFP
nvidiafb: Using DFP on CRTC 1
Panel size is 1024 x 768
nvidiafb: MTRR set to ON
Console: switching to colour frame buffer device 128x48
nvidiafb: PCI nVidia NV25 framebuffer (128MB @ 0xE0000000)


With DVI and video=nvidiafb:1600x1200-32@60 I get a kernel hang like this 
(copied by hand and shortened in places)

Decompressing linux
Bootdata ok (command line is root=... video=nvidiafb:1600x1200-32@60)
Linux version 2.6.10-rc2 ...
BIOS-provided physical map
Scanning NUMA topology in Northbridge 24
Number of nodes 2 (10010)
Node 0 using interleaving mode 1/0
No NUMA configuration found


and thats as far as it gets.

Getting closer by the hour :)

Andrew


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-23 18:01 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
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 [this message]
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=200411231801.14328.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).