Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 89472

Summary: Installer detects DVI port but uses VGA port
Product: [Retired] Red Hat Linux Reporter: Per Steinar Iversen <persteinar.iversen>
Component: XFree86Assignee: Mike A. Harris <mharris>
Status: CLOSED DUPLICATE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: msf
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:52:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Per Steinar Iversen 2003-04-23 08:42:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
When installing on a machine with an nVidia GeForce4 Ti 4400 graphics card with
both VGA and DVI ports the installer correctly detected that the monitor was
connected to the DVI port. The graphics install however started on the VGA port.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start install
2. See that the installer detects that the monitor is on the DVI port
3. The installer enters graphics mode, but with output on the ordinary VGA port

Actual Results:  Had to find a VGA monitor cable.

Expected Results:  Install should have used the DVI port.

Additional info:

Comment 1 Michael Fulbright 2003-04-23 18:54:05 UTC
Mike is there anything we have to do in the XF86Config to have the output come
on the alternate controller?

The probe succeeded because we use the video BIOS.

Comment 2 Mike A. Harris 2003-04-23 22:19:09 UTC
I've no DVI panel hardware and no experience configuring or using XFree86 on
LCD panels, so I'm afraid I can't really give an informed answer.  ;o/

What I can however say for sure, is that the "nv" driver DVI support is
experimental only and not something Red Hat "supports" other than that
we ship it because it is in XFree86.  The DVI support there is known to
have problems, and unfortunately for both us, and for Nvidia hardware
owners using the "nv" driver, only Nvidia can really fix the driver

All I can do is refer people to the "nv" manpage, and to
bugzilla for Nvidia to be able to investigate driver specific problems
and queries, and fix and/or recommend workarounds.

I do really need to be sent a flat panel display some time soon however
if I'm expected to even be able to remotely try to investigate LCD panel
related problems.

Comment 3 Mike A. Harris 2003-04-23 22:20:45 UTC
Don't know if this is the answer or not, but from the "nv" driver manpage:

       Option "CrtcNumber" "integer"
              nForce2, Quadro4, GeForce4 and NV30 may have two video  outputs.
              The  driver attempts to autodetect which one the monitor is con-
              nected to.  In the case that autodetection picks the wrong  one,
              this  option  may be used to force usage of a particular output.
              The options are "0" or "1".  Default: autodetected.
       Option "FlatPanel" "boolean"
              The driver usually cannot autodetect  the  presence  of  a  flat
              panel  so this option should be set when used with a flat panel.
              With this driver a flat panel will only work if it was POSTed by
              the  BIOS,  that  is, the machine must have booted to the panel.
              Default: off.

msf, does this help?

Comment 4 Mike A. Harris 2003-09-27 01:02:07 UTC

*** This bug has been marked as a duplicate of 88360 ***

Comment 5 Red Hat Bugzilla 2006-02-21 18:52:47 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.