Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 474739

Summary:	Refresh-rate problems in Plymouth when display connected via VGA
Product:	[Fedora] Fedora	Reporter:	John <jdelisle>
Component:	plymouth	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	10	CC:	fedora, krh, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-12-05 04:26:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John 2008-12-05 04:14:24 UTC

Description of problem:
Hardware: ATI 9700 pro, Samsung 226CW LCD, via VGA port.
On boot, my system enters a graphical boot loader and my LCD goes nuts. It immediately complains re resolution/refresh, and suggests changing to 1680x1050@60hz. This happens with both the installer CD, and also my upgraded system (done via DVI port as a work-around).

When I display the current display info, it shows refresh rates of not 60hz, sometimes it's 59.5, other times it's other values. In all cases, the display is unusable and seems to lock after a short time at this res/ref rate.

Regardless of my xorg.conf I can't get the monitor into the correct refresh rates. I've tried custom modelines etc, but it doesn't seem to be related to X.

This only happens with the display via VGA, and only started after F9-F10 upgrade.

A workaround is to add "nomodeset" to the boot prompt - it boots text mode, and when X starts everything works as expected now.

Version-Release number of selected component (if applicable):
plymouth-libs-0.6.0-0.2008.11.17.3.fc10.i386
plymouth-scripts-0.6.0-0.2008.11.17.3.fc10.i386
plymouth-utils-0.6.0-0.2008.11.17.3.fc10.i386
plymouth-system-plugin-0.6.0-0.2008.11.17.3.fc10.i386
plymouth-gdm-hooks-0.6.0-0.2008.11.17.3.fc10.i386
plymouth-0.6.0-0.2008.11.17.3.fc10.i386
plymouth-plugin-solar-0.6.0-0.2008.11.17.3.fc10.i386
plymouth-plugin-label-0.6.0-0.2008.11.17.3.fc10.i386

How reproducible:
Unsure. Happens to me 100% of the time, with my HW config. I've seen multiple posts about similar issues on the forums so it seems to be happening to others too.

Steps to Reproduce:
Boot with a similar HW config.

Actual results:
Crazy monitor - goes all nuts due to incorrect refresh rate I suspect.

Expected results:
Working monitor.

Additional info:
Adding "nomodeset" to the boot prompt worked as a temp work-around.

Comment 1 John 2008-12-05 04:26:43 UTC


*** This bug has been marked as a duplicate of bug 464896 ***