Red Hat Bugzilla – Bug 78114
monitor detection inconsistent
Last modified: 2014-03-16 22:32:21 EDT
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
Obviously, you shouldn't do warm boots. What sort of machine do you have?
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.
Try number 4: Cold boot, graphical install, NFS -- unable to detect It's not a cold boot / warm boot issue
Try #1 on the same system with beta2. Cold boot, NFS graphical install, monitor detection worked
beta3 - it fails consistently
VC2 during install reports: * ddcprobe returned bogus values: ID: None Name: None HorizSync: None VertSync: None
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.
new install of beta3 on this same machine worked. So, it's consistently inconsistent in beta3 too ;-)
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.