Bug 91179 - System is not running display at correct resolution
Summary: System is not running display at correct resolution
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-02 00:54 UTC by Jim Haynes
Modified: 2015-07-02 15:41 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Xorg.0.log (58.05 KB, text/plain)
2015-07-02 01:00 UTC, Jim Haynes 		no flags Details
View All

Description Jim Haynes 2015-07-02 00:54:24 UTC 

    


    


      



        
          Comment 1
        

        
          Jim Haynes

        

        
        

        
          2015-07-02 01:00:11 UTC
        

      






Created attachment 116859 [details]
Xorg.0.log

lspci says Intel 82865G Integrated graphics controller
Monitor is AOC Model 2051
Monitor normal resolution is 1600x900.  Windows XP gets it right, and
grub uses the full width of the screen, but Fedora 22 Linux running X
sets the screen resolution to 1024x768 and won't change it to anything greater.

driver is xorg-x11-drv-intel-2.99.917-12.20150615.fc22.i686

I don't claim to know much, so if this is not really a bug then please tell me
how to fix things.

    


    


      



        
          Comment 2
        

        
          Chris Wilson

        

        
        

        
          2015-07-02 06:32:08 UTC
        

      






Remove "nomodeset" form your kernel command line - it's not even loading the intel driver.

    


    


      



        
          Comment 3
        

        
          Jim Haynes

        

        
        

        
          2015-07-02 15:38:16 UTC
        

      






Thanks.  Removing "nomodeset" eliminated the problem.

As for the driver, I'm just using them as Fedora releases them.

    


    


      



        
          Comment 4
        

        
          Chris Wilson

        

        
        

        
          2015-07-02 15:41:58 UTC
        

      






It's weird that it ended up with nomodeset in the first place. But probably the installer encountered an error so added that as a failsafe? *shrug*

    



  






  














    


  Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.