Bug 835141

Summary: Frame Buffer and X screen are bigger than my Display after kernel update
Product: [Fedora] Fedora Reporter: Ali Yazdi <platoali>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17CC: airlied, ajax, bskeggs, platoali
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-10 17:39:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ali Yazdi 2012-06-25 16:32:11 UTC
Description of problem:

I  updated my kernel few days ago from 3.3.7 to 3.4.3-1 ( both fedora package). From that time, both X and Frame buffer outputs  are bigger than my Screen monitor. I am using nouveau. KDE display setting is showing that resolution is about 2400X2000 ( Not the exact number as I am not using that kernel now). But my native display resolution is 1920x1080. 

I searched and found this: 
http://en.gentoo-wiki.com/wiki/Nouveau#Framebuffer_does_not_fill_screen_or_is_larger_than_screen

I tried to set the display resolution by adding  display=LVDS-1:1920X1080 to kernel param in Grub. It actually works and changed my resolution but still the screen is still bigger than my monitor and I am being shown only the top left part of display. When I boot with the old kernel everything is OK. Here is lspci: 

01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 330M] (rev a2)


Version-Release number of selected component (if applicable):

Fedora 17 
Linux 3.4.3-1.fc17.x86_64

How reproducible:
Very Often

Steps to Reproduce:
1.Just boot with the new kernel
  
Actual results:

output is bigger than my physical Display size

Expected results:


Additional info:

Comment 1 Ali Yazdi 2012-07-10 17:39:16 UTC
It is fix in the new kernel Version: 

3.4.4-5.fc17.x86_64

I am closing it.