Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 178168 - Installer failed to detect monitor Hitachi CM827
Installer failed to detect monitor Hitachi CM827
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2006-01-18 02:22 EST by Claus Olesen
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-18 12:11:30 EST
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 Claus Olesen 2006-01-18 02:22:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.3 (like Gecko)

Description of problem:
I just installed FC5 Test2. The installer (anaconda) did not detect my monitor          
automatically but I was able to select it manually. My monitor is a Hitachi 

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

How reproducible:

Steps to Reproduce:
1. Do a fresh install from a DVD cut with FC5Test2   

Actual Results:  The installer reported 
Probing for monitor type: Unknown monitor 

Expected Results:  It should have detected the monitor automatically.   

Additional info:
Comment 1 Chris Lumens 2006-01-18 10:45:40 EST
What are the results of running as root:

ddcprobe --monitor --raw
Comment 2 Jeremy Katz 2006-01-18 12:11:30 EST
Unfortunately, the only generic way of doing monitor probing requires LRMI and
therefore, real mode, which can't be done on x86_64
Comment 3 Claus Olesen 2006-01-21 15:20:23 EST
For comment #2: I just installed SuSE10.1Beta1 x86_64 and it did detect the 
Hitachi CM827 monitor automatically. 

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