Bug 68926 - limbo install did not recognize monitor in kickstart
Summary: limbo install did not recognize monitor in kickstart
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda
Version: limbo
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks: 67218
TreeView+ depends on / blocked
 
Reported: 2002-07-16 00:38 UTC by Need Real Name
Modified: 2007-04-18 16:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-08-23 15:31:54 UTC
Embargoed:

Attachments (Terms of Use)

Description Need Real Name 2002-07-16 00:38:02 UTC 
Description of Problem:limbo install did not recognize monitor (Optiquest V655).
 Later, Xconfigurator was able to recognize it.


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


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:
Comment 1 Jeremy Katz 2002-07-16 17:06:51 UTC 
kudzu wasn't properly recognizing some monitors due to not looking in the
MonitorsDB properly.  Fixed in CVS
Comment 2 Tim Waugh 2002-07-17 16:41:08 UTC 
My IBM P72 monitor still isn't detected with anaconda-7.3.93-0.200207170147
(worked in 7.3).
Comment 3 Jay Turner 2002-07-29 17:19:21 UTC 
Tim, will you test again with the latest Limbo code.  I'm not seeing any
problems here in the test lab, but just wanted to check with you.
Comment 4 Tim Waugh 2002-07-30 22:35:13 UTC 
Problem still happens with anaconda-7.3.93-5 (from 0729.nightly).
Comment 5 Tim Waugh 2002-07-30 22:36:40 UTC 
Oh, the problem only happens with kickstart installations by the way; 
installing interactively is fine.
Comment 6 Michael Fulbright 2002-08-23 15:21:49 UTC 
I fixed some problems related to this recently.
Comment 7 Tim Waugh 2002-08-23 15:31:47 UTC 
Yes, it works for me now.
Comment 8 Ben Levenson 2002-09-05 22:57:49 UTC 
closing -> RESOLVED
Note You need to log in before you can comment on or make changes to this bug.