Bug 491417 - xorg-x11-drv-openchrome-0.2.903-5.fc10.i386 no valid modes
Summary: xorg-x11-drv-openchrome-0.2.903-5.fc10.i386 no valid modes
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-openchrome
Version: 10
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Xavier Bachelot
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-20 21:02 UTC by Kuehner Joseph
Modified: 2009-04-27 21:26 UTC (History)
1 user (show)

Fixed In Version: 0.2.903-6.fc10
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-27 21:26:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.0.log of failing driver (30.87 KB, text/plain)
2009-03-20 21:02 UTC, Kuehner Joseph
no flags Details
xorg.conf file (3.17 KB, text/plain)
2009-03-20 21:04 UTC, Kuehner Joseph
no flags Details
Xorg.0.log.openchrome1 (42.35 KB, text/plain)
2009-03-21 19:30 UTC, Kuehner Joseph
no flags Details
X works fine with updated driver. Attached Xorg.0.log (45.24 KB, text/plain)
2009-03-22 08:36 UTC, Kuehner Joseph
no flags Details

Description Kuehner Joseph 2009-03-20 21:02:02 UTC
Created attachment 336119 [details]
Xorg.0.log of failing driver

Description of problem:
after update to xorg-x11-drv-openchrome-0.2.903-5.fc10.i386 X does not start.
Error message: no valid modes found

with previous versions of this driver X worked fine.

Version-Release number of selected component (if applicable):
xorg-x11-drv-openchrome-0.2.903-5.fc10.i386

How reproducible:
every time X is started

Steps to Reproduce:
1. from console start X
2. X does not start
3. Error message: no valid modes found
   screens found but no valid configuration
Actual results:

X does not start. I erased last version of driver, installed version 
xorg-x11-drv-openchrome-1. X starts fine.
Expected results:

X should start
Additional info:

Comment 1 Kuehner Joseph 2009-03-20 21:04:47 UTC
Created attachment 336120 [details]
xorg.conf file

this xorg.conf worked for all previous versions, not for the latest

Comment 2 Xavier Bachelot 2009-03-21 16:00:12 UTC
Could you please post the xorg log from the working attempt ? It would help me to be able to compare it with the non-working attempt.

Comment 3 Kuehner Joseph 2009-03-21 19:30:03 UTC
Created attachment 336174 [details]
Xorg.0.log.openchrome1

This is the Xorg.0.log file from driver xorg-x11-drv-openchrome-0.2.903-1.fc10.i386. This driver worked fine with my xorg.conf.
Note that even then the conf file generated by X -configure did not work.
I had to add options HorizSync and VertRefresh manually.

Comment 4 Fedora Update System 2009-03-21 22:00:16 UTC
xorg-x11-drv-openchrome-0.2.903-6.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.903-6.fc10

Comment 5 Xavier Bachelot 2009-03-21 22:03:51 UTC
New package on its way to updates-testing. 
You can grab it from koji before it hits the repo :
http://koji.fedoraproject.org/koji/taskinfo?taskID=1252587

Comment 6 Kuehner Joseph 2009-03-22 08:36:26 UTC
Created attachment 336192 [details]
X works fine with updated driver. Attached Xorg.0.log

I updated driver to xorg-x11-drv-openchrome-0.2.903-6.fc10.i386.
X works fine. Thank you very much
Regards J. Kuehner

Comment 7 Fedora Update System 2009-03-23 16:00:27 UTC
xorg-x11-drv-openchrome-0.2.903-6.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-openchrome'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-2973

Comment 8 Fedora Update System 2009-04-27 21:26:18 UTC
xorg-x11-drv-openchrome-0.2.903-6.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.


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