Bug 512602 - Kernel modesetting doesn't honour xorg.conf screen modes
Summary: Kernel modesetting doesn't honour xorg.conf screen modes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 11
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-19 19:04 UTC by James Wilkinson
Modified: 2018-04-11 17:30 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-28 13:43:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
xorg.conf (818 bytes, text/plain)
2009-07-19 19:04 UTC, James Wilkinson
no flags Details
Xorg.0.log without KMS (51.99 KB, text/plain)
2009-07-19 19:06 UTC, James Wilkinson
no flags Details
Xorg.0.log *with* KMS (32.00 KB, text/plain)
2009-07-19 19:08 UTC, James Wilkinson
no flags Details

Description James Wilkinson 2009-07-19 19:04:32 UTC
Created attachment 354279 [details]
xorg.conf

Description of problem:

Hi there.

I have an AOC CRT that is capable of 1600x1200 at 75 Hz. X has never auto-detected that it is capable of this resolution, but if I tell it so (through xorg.conf) it has worked fine with nv, nouveau, ati, and intel drivers (on suitable video cards), and under Windows.

With kernel mode-setting, obviously X configures the screen before it gets a chance to look at Xorg.conf. So the kernel modesets to only 1024x768, and system-config-display won't let me set the display to 1600x1200.

Is there any way to configure KMS's modes through the command line? Is there any documentation available? And is it possible to get X to auto-configure my monitor correctly?

Thanks,

James.

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.7.0-7.fc11.x86_64
kernel 2.6.29.5-191.fc11.x86_64

Comment 1 James Wilkinson 2009-07-19 19:06:12 UTC
Created attachment 354280 [details]
Xorg.0.log without KMS

Comment 2 James Wilkinson 2009-07-19 19:08:14 UTC
Created attachment 354281 [details]
Xorg.0.log *with* KMS

Comment 3 Dan Thurman 2009-08-24 21:18:06 UTC
This is a problem for me as well.  Seems to
affect Intel 945 chipsets.

This was posted over a month ago with no response?

We can add the 'nomodeset' kernel argument and
get around this issue, but it would be nice to
get this fix in for F11 & future releases and at
least a comment?

Comment 5 Matěj Cepl 2009-11-05 18:35:15 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 6 Dan Thurman 2009-11-07 17:48:17 UTC
I have waited for this fix for F11 since the very beginning
and it still does not work.  I am still forced to use 
nomodeset. I will be glad to check out the updates-testing,
but I am unable to get access to the repo.

I tried: yum upgrade --enablerepo='*-updates-testing'
but the problem is, only rpmfusion appears for updates-testing
and none from Fedora.

I also tried: I tried: yum upgrade --enablerepo='fedora-updates-testing'
but I get no repository found:

# yum upgrade --enablerepo='fedora-updates-testing'
Loaded plugins: fastestmirror, presto, protect-packages, refresh-packagekit


Error getting repository data for fedora-updates-testing, repository not found




Here is my /etc/yum.repo.d/fedora-updates-testing.repo:
===================
[updates-testing]
name=Fedora $releasever - $basearch - Test Updates
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/testing/$releasever/$basearch/
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f$releasever&arch=$basearch
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch

[updates-testing-debuginfo]
name=Fedora $releasever - $basearch - Test Updates Debug
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/testing/$releasever/$basearch/debug/
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=updates-testing-debug-f$releasever&arch=$basearch
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch

[updates-testing-source]
name=Fedora $releasever - Test Updates Source
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/testing/$releasever/SRPMS/
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=updates-testing-source-f$releasever&arch=$basearch
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
===================


Please advise,
Dan

Comment 7 James Wilkinson 2010-02-25 11:55:12 UTC
(Still a problem, on F11 and F12. When I can get F13 media that isn't too buggy, I'll try it there.)

Comment 8 Dan Thurman 2010-02-25 15:42:38 UTC
I find that I no longer need to set nomodeset on F12.
MUCH better than F11/10, which is broken.  Since there
are many problems besides this issue w/ 10-11, probably
best to move on to either 12 or 13.

Comment 9 Bug Zapper 2010-04-27 15:47:28 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Bug Zapper 2010-06-28 13:43:14 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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