Bug 178752 - Fails to detect Monitor
Summary: Fails to detect Monitor
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kudzu
Version: 5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-23 23:59 UTC by Dave Burgess
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-01-28 05:38:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Here's the output of lspci as requested (1.41 KB, text/plain)
2006-01-25 11:18 UTC, Dave Burgess
no flags Details

Description Dave Burgess 2006-01-23 23:59:35 UTC
Description of problem:

When probing the hardware during the start of Anaconda it properly detects the
video card and the mouse but fails to detect my Optiquest V-95.

System-config-display has it in the device database.

It also fails for the i386 architecture it used to work for i386 in FC2, 3, and 4. 

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


How reproducible:

Everytime.

Steps to Reproduce:
1. Start an install.
2. Fails to detect monitor when Anaconda starts.
3.
  
Actual results:


Expected results:

Should have detected the monitor (it is fully supported) and  properly populate
xorg.conf.

Additional info:

Comment 1 Wade Mealing 2006-01-24 05:05:02 UTC
To make life easier for engineering, please attach the output of the following
commands to this ticket. 

lspci &> BZ178752.lspci

dmidecode &> BZ178752.dmidecode



Comment 2 Dave Burgess 2006-01-25 11:18:23 UTC
Created attachment 123660 [details]
Here's the output of lspci as requested

A full search of my system (FC5T2) fails to find dmidecode, so I can't give you
that output.

Comment 3 Jeremy Katz 2006-01-28 05:38:40 UTC
Monitor probing isn't supported on x86_64 due to the fact that we use real-mode
BIOS calls which can't be done once you've transitioned to long mode.


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