On 10/01/14 05:39, jd1008 wrote: > My physical screenis 1280x800. It is the screen of a Dell Latitude E6500 laptop. > > Now, all gui app windows are being displayed as if my physical screen is 1280x760, > and the app's window is 1280x800, thus I can pan the window up and down by > moving the mouse to top of screen or bottom of screen. > > This resizing happened AFTER I uninstalled the rpmfusion nvidia packages: > > xorg-x11-drv-nvidia.x86_64 > xorg-x11-drv-nvidia-304xx.x86_64 > xorg-x11-drv-nvidia-304xx-devel.x86_64 > xorg-x11-drv-nvidia-304xx-libs.x86_64 > xorg-x11-drv-nvidia-libs.x86_64 > > xrandr reports: > > # xrandr --verbose > xrandr: Failed to get size of gamma for output default > Screen 0: minimum 640 x 480, current 1280 x 768, maximum 1280 x 768 > default connected 1280x768+0+0 (0x186) normal (normal) 0mm x 0mm > Identifier: 0x181 > Timestamp: 55232 > Subpixel: unknown > Clones: > CRTC: 0 > CRTCs: 0 > Transform: 1.000000 0.000000 0.000000 > 0.000000 1.000000 0.000000 > 0.000000 0.000000 1.000000 > filter: > 1280x720 (0x182) 0.000MHz > h: width 1280 start 0 end 0 total 1280 skew 0 clock 0.00KHz > v: height 720 start 0 end 0 total 720 clock 0.00Hz > 1024x768 (0x183) 47.972MHz > h: width 1024 start 0 end 0 total 1024 skew 0 clock 46.85KHz > v: height 768 start 0 end 0 total 768 clock 61.00Hz > 800x600 (0x184) 29.280MHz > h: width 800 start 0 end 0 total 800 skew 0 clock 36.60KHz > v: height 600 start 0 end 0 total 600 clock 61.00Hz > 640x480 (0x185) 18.432MHz > h: width 640 start 0 end 0 total 640 skew 0 clock 28.80KHz > v: height 480 start 0 end 0 total 480 clock 60.00Hz > 1280x768 (0x186) 0.000MHz *current > h: width 1280 start 0 end 0 total 1280 skew 0 clock 0.00KHz > v: height 768 start 0 end 0 total 768 clock 0.00Hz > > Is there a way to restore it back to physical resolution of 1280x800? > Now the you have connectivity and have taken this to the list.... I should tell the list what has been found so far... As I said, I'm fairly certain you're having problems due to this in your Xorg.log [ 29.862] (EE) [drm] KMS not enabled [ 29.862] (EE) open /dev/dri/card0: No such file or directory [ 29.862] (WW) Falling back to old probe method for modesetting Looking down further you see it is falling back and using the VESA driver and not nouveau. [ 29.863] (II) Module int10: vendor="X.Org Foundation" [ 29.863] compiled for 1.14.4, module version = 1.0.0 [ 29.863] ABI class: X.Org Video Driver, version 14.1 [ 29.863] (II) VESA(0): initializing int10 [ 29.864] (II) VESA(0): Primary V_BIOS segment is: 0xc000 [ 29.919] (II) VESA(0): VESA BIOS detected [ 29.919] (II) VESA(0): VESA VBE Version 3.0 [ 29.919] (II) VESA(0): VESA VBE Total Mem: 14336 kB So, that is the problem.... That, I believe, is often caused by another driver being loaded and interfering in things. It can also be caused by having a parameter set in the boot line....but I see that is not the case as you have... [ 29.631] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.3-200.fc20.x86_64 root=UUID=691db345-e126-4dc7-8846-95545a9422f7 ro vconsole.font=latarcyrheb-sun16 rhgb quiet quiet splash acpi=off Sooo.... What is the output of "lsmod"? -- If you can't laugh at yourself, others will gladly oblige. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
