Bug 184277 – Fujitsu Lifebook P Series does not detect 'monitor'

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 184277 - Fujitsu Lifebook P Series does not detect 'monitor'

Summary:	Fujitsu Lifebook P Series does not detect 'monitor'

Status:	CLOSED CANTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kudzu (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:	Desktop

Depends On:
Blocks:	183425
	Show dependency tree / graph

Reported:	2006-03-07 14:42 EST by Suzanne Hillman
Modified:	2014-03-16 22:58 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-03-08 11:44:56 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Dmidecode results from the lifebook (11.14 KB, text/plain) 2006-03-07 15:34 EST, Suzanne Hillman	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Suzanne Hillman 2006-03-07 14:42:31 EST

Description of problem:
When installing today's rawhide on a Fujitsu Lifebook P Series laptop, firstboot
is unable to autodetect the monitor type.

I would have expected the monitor type to be autodetected.

Comment 1 Suzanne Hillman 2006-03-07 15:25:35 EST

ddcprobe results:

Videocard autoprobe results
Description:  Intel Corporation Intel(r)915GM/910ML/915MS Graphics
Controller
Memory (MB):  7

Monitor autoprobe results
Monitor autoprobe failed.

Comment 2 Suzanne Hillman 2006-03-07 15:34:23 EST

Created attachment 125774 [details]
Dmidecode results from the lifebook

Comment 3 Mike A. Harris 2006-03-08 04:17:46 EST

Except it isn't X that is responsible for installation monitor detection. ;o)

Comment 4 Bill Nottingham 2006-03-08 11:44:56 EST

If the monitor autoprobe fails, there's not much we can do; the display didn't
support the DDC probe, and it doesn't have EDIDs in ACPI we can read out of.

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