Bug 117079 - Does not autodetect ThinkPad T23 display
Summary: Does not autodetect ThinkPad T23 display
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-28 02:55 UTC by Mark Atwood
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-08-15 16:00:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
here is the X.log (35.59 KB, text/plain)
2004-03-01 09:50 UTC, Mark Atwood
no flags Details

Description Mark Atwood 2004-02-28 02:55:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031030

Description of problem:
The installer does not detect the "monitor type" when installing on a
IBM TP T23

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


How reproducible:
Always

Steps to Reproduce:
1. Boot install CDROM on an IBM TP T23
2. Proceed to monitor detection
3. Notice that it's an "unknown monitor" with "unknown resolution"
    

Expected Results:  It should have autodetected the builtin LCD
display, with the correct resolution. 

Additional info:

Comment 1 Bart Martens 2004-02-28 23:57:48 UTC
This may be for component=hwdata. Could you have a look at bug #107788
and provide the relevant information?


Comment 2 Jeremy Katz 2004-02-29 04:01:06 UTC
Can you attach the X.log from a running system?  Unfortunately, LCDs
aren't probably via DDC so the cases where this work are due to a
really bad hack :/

Comment 3 Mark Atwood 2004-02-29 10:55:23 UTC
how do I configure X to make an X.log?

Comment 4 Mark Atwood 2004-03-01 09:50:33 UTC
Created attachment 98154 [details]
here is the X.log

Comment 5 Jeremy Katz 2004-03-03 03:42:52 UTC
Should hopefully be fixed in CVS (which will hopefully be built for
FC2 test2)


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