Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 78114 - monitor detection inconsistent
monitor detection inconsistent
Product: Red Hat Linux
Classification: Retired
Component: kudzu (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-11-19 02:17 EST by Chris Ricker
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-23 15:49:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2002-11-19 02:17:02 EST
I've tried 3 installs on the same system (AOC Spectrum 7Glr + Matrox Millenium
G200) so far. Try one:

cold boot, graphical install, NFS -- anaconda detected monitor

Try two:

warm boot, graphical install, NFS -- anaconda unable to detect monitor type

Try three

warm boot, text install, NFS -- anaconda unable to detect monitor type
Comment 1 Bill Nottingham 2002-11-19 14:21:05 EST
Obviously, you shouldn't do warm boots.

What sort of machine do you have?
Comment 2 Chris Ricker 2002-11-19 14:32:16 EST
Heh.  I'm not sure the cold boot is what makes it work -- it might be something
less obviously different.  I'll play more tonight and see.

The machine itself is an AMD K7, probably VIA chipset.
Comment 3 Chris Ricker 2002-11-19 21:30:35 EST
Try number 4:

Cold boot, graphical install, NFS -- unable to detect

It's not a cold boot / warm boot issue
Comment 4 Chris Ricker 2002-12-09 23:54:41 EST
Try #1 on the same system with beta2. Cold boot, NFS graphical install, monitor
detection worked
Comment 5 Chris Ricker 2002-12-23 01:38:49 EST
beta3 - it fails consistently
Comment 6 Chris Ricker 2002-12-23 02:01:38 EST
VC2 during install reports:

* ddcprobe returned bogus values:
ID: None
Name: None
HorizSync: None
VertSync: None
Comment 7 Chris Ricker 2002-12-23 02:03:38 EST
Sorry -- that should, of course, have been VC3, not VC2.

If I manually run ddcprobe during install, I get:

Videocard DDC probe results
Description: Matrox MGA-G200
Memory (MB): 8

Monitor DDC probe results
Monitor DDC Probe failed.

Comment 8 Chris Ricker 2003-01-11 10:15:05 EST
new install of beta3 on this same machine worked. So, it's consistently
inconsistent in beta3 too ;-)
Comment 9 Bill Nottingham 2005-09-23 15:49:11 EDT
Apologies for the slow response. Please attempt to reproduce this problem on a
currently supported release, such as Fedora Core 4. If it does still happen,
please open a new issue.

Note You need to log in before you can comment on or make changes to this bug.