[SOLVED] Updating Xorg screwed up my screen-resolution.

After doing pacman -Syu earlier this evening, my screen-resolution was screwed up. One of the packages that was updated by pacman -Syu was X to 1.7.1-1 and all of its depencies.
I downgraded xorg (and its dependencies) to 1.6.3.901-1 and after that everything is working fine again.
I'm trying to figure out why the update failed, but to be honest I don't know where to look for clues. The only thing I can come up with is that maybe it would be better to update X without X running.
Before I try this solution I need some feedback on this. So if you could please give your comments/advise towards the following issues:
1. Is it better to update X without X running?
2. Where would I have to look for clues to find out why the update of X failed?
Thxs.
Last edited by NeoXP (2009-11-01 21:39:13)

NeoXP wrote:
After doing pacman -Syu earlier this evening, my screen-resolution was screwed up. One of the packages that was updated by pacman -Syu was X to 1.7.1-1 and all of its depencies.
I downgraded xorg (and its dependencies) to 1.6.3.901-1 and after that everything is working fine again.
I'm trying to figure out why the update failed, but to be honest I don't know where to look for clues. The only thing I can come up with is that maybe it would be better to update X without X running.
Before I try this solution I need some feedback on this. So if you could please give your comments/advise towards the following issues:
1. Is it better to update X without X running?
2. Where would I have to look for clues to find out why the update of X failed?
Thxs.
I have a similiar problem except that my X hang the whole computer. I have an Intel card and maybe thats the reason for the hang. To answer 1., I did my upgrade without X running, so that doesn't prevent bad things from happening. I downgraded to the previous version, as you did, and now everything is working again.
With respect to 2., I looked into Xorg log and found nothing relevant to this problem.

Similar Messages

Authorware Screwing up my screen resolution settings

Was having problems with my macromedia flash and the website
said download this Authorware. Now everytime I click on my web
browser FireFox or on the downloaded authorware desktop install
icon it resizes my screen. I have gone back to the properties and
reset the screen size however it continues to resize it
everytime.I've tried to locate and remove this Authorware download,
but have had no luck finding it. Please help!!!

You were at this site:
http://www.macromedia.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash&p romoid=BIOX
...and it asked you to install Authorware? Flash does not
require the
Authorware plugin. Or are you confusing the Authorware Web
Player with the
Flash player? They are not the same thing.
First, check to see if the Authorware Web Player plugin is,
in fact,
installed. In Firefox, type "about
lugins" (without the quotes) in the
Address bar. Look for Authorware Web Player. If you find it,
close Firefox,
and go to C:\Program Files\Mozilla Firefox\plugins and delete
np32asw.dll.
Then go to C:\Documents and Settings\<your login
name>\Application
Data\Macromedia and delete the "Authorware Web Player"
directory. Then
restart Firefox and see what happens.
Your symptoms are so strange, I wonder if you didn't get to a
spoofed site
and have downloaded a virus or some other malware. If I were
you, I would
update my virus signature files and run a complete system
scan.
Paul Swanson
Portland, Oregon, USA
"Wiscvol" <[email protected]> wrote in
message
news:e233aj$i3n$[email protected]..
> I was on the Macromedia Flash free download site. It
said if you are not
seeing
> the image/graphics download authorware which I did. It
installed the
authorware
> download setup file on the desktop. After it downloaded
it resized the
desktop.
> .I have removed and reinstalled firefox and that did not
help. When I
click on
> the Firefox icon to launch the web browser it resizes
the screen still. It
does
> not happen if I use IE or if I don't click on the
Authorware setup
install
> icon.
>
> Should there be a uninstall feature. I've looked in the
add/remove
programs
> but nothing.
>

Tiger update 2008-004 screwed up iMac G5 screen resolution/desktop

I have an iMac G5. Installed the Tiger 2008-004 update (and Safari update). When the iMac boots up the screen resolution/desktop gets enlarged just as the spotlight icon appears. As I move the mouse around the screen the desktop moves with it. The desktop is about 5%-10% larger than the standard size. Tried display preferences with no effect. Zapped PRAM. Re-installed updates individually,nothing works.Help!

Hi,
You probably have 'Zoom' enabled in the Universal Access preferences. Have a play around in there to find the setting to turn it off (sorry for the vague directions but I'm on a Linux machine at the moment )

Xorg 1.6, nvidia and screen resolutions

I just upgraded to xorg 1.6 from testing, including the nvidia drivers and kernel from testing. Everything is working great (and it fixed the libxi keyboard layout problems I was having), except that I can no longer select the screen resolution I want from the nvidia-settings application. The set of resolutions is very limited and I'm getting a horizontal stretch due to an incorrect aspect ratio.
I've tried manually adjusting the xorg.conf file after saving it in nvidia-settings, but it makes a mess of the file and I couldn't get it working. Does anybody know how to add screen resolutions into the nvidia-settings application?
Thank you!
Darin

Happened to me with most recent 1.5 update, I downgraded back to previous one to get working again. And now same happened with 1.6, this time I downgrade again without any further testing until someone else gets it solved

Screen resolution too large on HP Pavilion dv6608ca after Windows 7 Update

Hi, I've recently updated my HP Pavilion dv6608ca from Vista to Windows 7 64 bit, and all of a sudden the screen resolution is just too big even after I adjust it in the display. I've searched high and low here and elsewhere but can't seem to find the correct driver.
Can someone please help?
Thanks in advance.
Chris
This question was solved.
View Solution.

Newuser1227, welcome to the forum.
Have you used Windows Update and HP Update to see if this installs the appropriate driver?
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

XP update wrecks my screen resolution on Qosmio G10-133

I am running a two years old G10-133. Great and reliable machine. The reason I bought it was because it has great screen resolution/sharpness for MS Word texts and Outlook emails.
For various reasons I do not download the MS Windows updates that are frequently offered in a pop-up at start up (suspicion that they can bring more problems than they solve). Anyway I have recently (despite running Norton Security all the time) picked up some sort of nasty malware in Google that hijacks around 50% of the google links after a search and sends then off to another search engine with links.
The windows and Norton firewalls did not pick these up or clean them out so I tried the Spybot freeware to get rid of them to no affect.
Finally rang up Toshiba Europe Support and the chap there recommended that :
1) Don't use Norton. Waste of time and money and slows machine. Get the new Windows Defender freeware instead.
2) Do all the XP updates
So I started with all the windows updates (loads), including Internet Explorer 7.
Guess what, after restart computer went a bit slow cranky, but worse the screen resolution (sharpness/clarity of text) had deteriorated in both Word, Outlook and Explorer.
So I called Toshiba Support again (I am on a three years warranty contract) and they could not solve the problem or suggest anything and seemed surprised that it had happened. We checked the usual screen resolution things in Control panels to no avail.
So I gave up, set the System Restore back before all the updates.
Computer is now stable and the screen resolution back to where it was.
Questions:
1) Can I get the XP updates and EXP 7 and still get my old (best) screen resolution.
2) What about giving up Norton for Windows Defender good/safe idea?
3) Any ideas on how to stop the hijacking of Google links?
All help much appreciated
Message was edited by: holtom

Hi
1.) This is very strange and I have never heard about bad display quality after installation of Microsoft updates!
I think you should try to contact the Microsoft support and maybe they know something about such strange behaviour.
But did you try to update graphic driver and/or BIOS?
2.) This is true. I have installed the Norton System Works several months ago and my unit booted very slow with preinstalled Norton Antivirus.
I have removed it and use and freeware AntiVirus application called "Antivir".
I don't want to use the MS Windows Defender. But I don't say this application is bad.
3) I don't know what you want to do but I don't think that this has something to do with your Toshiba notebook ;)

ZBook 14 - Can't change screen resolution after update

After I installed some software updates the Laptop was suggesting me, my screen resolution went suddenly from 1900x1200 to 1200x720 after reboot, and it doesn't let me change it, not even to a smaller resolution. I am quite frustrated, because I will need the computer next week for visualization works and I really need the display working well.
It doesn't let me change the resolution. The display and graphics drivers are up to date and working properly, according to the device manager. I made a system recovery, but that just made everything worse although the resolution thing worked again, I had to run a startup repair several times before my laptop would boot propery again. This didn't solve the issue, since the display drivers weren't working properly (videos were being visualized very poorly) and even after updating them the computer wouldn't start up again, so I had to made another system recovery and now I am back to the point where I can't change the resolution and is starting to be really frustrating.
Thanks for any help anyone can offer.

Hello @hellmet,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I understand that your notebook computer is not able to change its display settings, and I would be happy to guide you towards a resolution!
I am sorry, but to get your issue more exposure, I would suggest posting it in the commercial forums, since this is a commercial product. You can do this at:
http://h30499.www3.hp.com/t5/Notebook-HP-ProBook-EliteBook/bd-p/bsc-274
I hope this helps!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

Anyone experiencing screen resolution problems after latest Mavericks Update?

Anyone got a blurred monitor after the latest Mavericks Update?
I am running Mavericks 10.9.2 on a Mini Mac with a Logic TV/Monitor. Since the latest Mavericks update I no longer have the option in settings to scale to 1600 x900. Since this gives the best picture on my monitor I now have either a blurred screen with large text or a blurred screen with very tiny text. No other options that give a 'normal' display seem available now, after allowing the 'Update'. The update claims to be addressing faults on the MacBook display, which it may well do, but it has also apparently screwed up Mac Mini screen resolution Options for some of us.
I have reverted back to 10.9.2 and turned off automatic updates, but I can't stay that way indefinitely.
I've tried to find an e-mail address or phone number to log my complaint to Apple but to no avail. (I guess they would otherwise be inundated with customer complaints so keep that kind of information under wrapps). Anyone got any ideas?

I'm not having any problems with dual DVI connected Samsung 21.5" monitors in 10.9.3
What connection (adapter, cable, etc.) are you using..?
To send Apple Feedback, go to > Apple - Mac OS X - Feedback
If your looking for better resolution options, try > Mac App Store - Display Menu

I updated to iTunes 11 on my Windows PC. Since the update, when I open iTunes its window is too large for my screen. Resizing is a pain, because I have to change my screen resolution. And when I restart iTunes,it has reverted back to being too large.Help!

I recently updated to iTunes 11 on my Windows PC. Since the update, each time I open iTunes its window is too large for my screen. Resizing it is a pain, because I have to change my screen resolution. And then when I restart iTunes, it has reverted back to being too large. Please help!

Having the same issue here....a quick fix is to just minimize the window, and immediately maximize it. It will now fit the screen. Trouble is, after you close it, you'll have to do it again when you re-start itunes. The good news is it takes all of about 2 seconds. Apple should fix this. Should.

|Solved| - Screen resolution and nVidia

I installed arch, xorg, nvidia's drives, openbox and gnome.
I can run gnome and openbox without any problem, however, my screen resolution isn't recognised. Here's my /etc/X11/xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Thu Jun 5 00:08:24 PDT 2008
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# Files section. This allows default font and rgb paths to be set
# Server flags section.
# Input devices
# Core keyboard's InputDevice section
# Core Pointer's InputDevice section
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
# Section "DRI"
# Mode 0666
# EndSection
Section "ServerLayout"
# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
Identifier "Simple Layout"
Screen "Screen 1" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# FontPath "/usr/share/fonts/TTF"
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# Load "type1"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
# Load "xtt"
Load "glx"
EndSection
Section "InputDevice"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xorg"
Option "XkbModel" "logicd"
Option "XkbLayout" "pt"
Option "XkbVariant" "pt"
EndSection
Section "InputDevice"
# Identifier and driver
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"
# Mouse-speed setting for PS/2 mouse.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection
Section "Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
Identifier "My Monitor"
HorizSync 80.0 - 80.0
VertRefresh 75.0
EndSection
Section "Device"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "Standard VGA"
Driver "nvidia"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
# unsupported card
#VideoRam 319488
# Insert Clocks lines here if appropriate
Identifier "My Video Card"
Driver "nvidia"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "My Video Card"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1440x900"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1440x900"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1440x900"
EndSubSection
EndSection
If I run "xorgconfig" and after that "nvidia-xconfig", my screen resolution is 1024x860, but after changed very mode to my native resolution ("1440x900"), is changes to "800x600".
Last edited by Nomearod (2008-07-23 09:19:07)

heleos wrote:
Widescreen resolutions are not possible with newest vista and linux drivers if the tft is connected with dvi.
Use an older driver or the vga-port instead.
There are maybe some hacks, but I tried many times in vista and linux. And it's always the same, only 1280x1024.
did some googling:
http://forums.nvidia.com/lofiversion/in … 20005.html
Thanks for the reply, but I don't believe that's the problem since that topic is from 2006 and I didn't had any problems last time I instaled arch (3 months ago).

Just updated my iPad 2 to ios7 and now my screen resolution is terrible...

I tried rebooting several times, but it didn't help. Everything else seems to be working fine. Any suggestions?

Diavonex
This helped meRe: Just updated my iPad 2 to ios7 and now my screen resolution is terrible... Jan 4, 2014 10:50 PM (in response to Batsy2000)
Try restore iPad
http://support.apple.com/kb/ht1414
Backup before you do it.
Just tried this...did not work. Resolution is still horrible. This is not an issue of it just not looking smooth or sharp. It's so much worse than that. It was actually fine right after the update. The next morning when I turned it on it was messed up.

[Solved] Set Screen Resolution in Openbox

Is there a utility to set the screen resolution in Openbox?
Last edited by Wintervenom (2008-09-26 07:43:03)

You can make an Openbox submenu with various xrandr settings.
Like so:
<menu id="res-menu" label="Resolution">
<separator label="Resolution"/>
<item label="1280x1024">
<action name="Execute">
<execute>
xrandr -s 1280x1024
</execute>
</action>
</item>
<item label="1024x768">
<action name="Execute">
<execute>
xrandr -s 1024x768
</execute>
</action>
</item>
<item label="800x600">
<action name="Execute">
<execute>
xrandr -s 800x600
</execute>
</action>
</item>
Of course, you need to have those modes defined in xorg.conf.
Last edited by moljac024 (2008-09-26 00:06:37)

How to solve screen resolution in bdc

hi experts,
please tell me how to solve screen resolution in bdc.
regards.
subhasis

Hi,
<b>Pls check other posts in SDN before posting ur thread..there is same thread related to this on this forum on same day.</b>
Screen resolution means different in the screen display depending on ur system screen resolution.
suppose ur system resolution is diff and another's system is different then like in Tcode VA01, there will be 3 lineitems and another there will be 5 lineitems ,
so while doing recording and page down that will bw diff so there will be some problem
So u have to set the screen resolution as default by using CTU parameters..
write this code then
f_option-updmode = 'S'.
f_option-defsize = 'X'.* f
_option-dismode = 'N'.
*call transaction 'VA01' using bdcdata options from f_option messages into bdcerror.
Hope it helps.
Regards,
Sonika

Screen resolution changed only in the browser after update of version 9.0.1 how do I change it back

Screen resolution changed only in the browser after update of version 9.0.1 how do I change it back?

http://kb.mozillazine.org/Screen_resolution_changes_when_launching_application ?

[SOLVED]Screen resolution began to be incorrectly detected

After installing some packages not having obvious relations to video issues (mysql and zfs related packages), the screen resolution on my 1280x1024 screen began to be set as 1024x768 without 1280x1024 in the list of possible modes. I tried to X -configure but to no avail. Reinstalling xorg-server also didn't help. I tried to manually detect and add 1280x1024 mode with xrandr, this mode began to appear in the modes list, but the resolution remains 1024x768 when it's selected.
I have an ancient SiS videocard, but it worked OK with the standard vesa driver.
What can be the cause of this issue and how it could be corrected?
Some fragments of Xorg log:
[ 769.623] (II) VESA(0): Total Memory: 512 64KB banks (32768kB)
[ 769.623] (II) VESA(0): Monitor0: Using default hsync range of 31.50-48.00 kHz
[ 769.623] (II) VESA(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz
[ 769.623] (II) VESA(0): Monitor0: Using default maximum pixel clock of 65.00 MHz
[ 769.623] (WW) VESA(0): Unable to estimate virtual size
[ 769.623] (II) VESA(0): Not using built-in mode "1600x1200" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
[ 769.623] (WW) VESA(0): No valid modes left. Trying less strict filter...
[ 769.623] (II) VESA(0): Monitor0: Using hsync range of 31.50-48.00 kHz
[ 769.623] (II) VESA(0): Monitor0: Using vrefresh range of 50.00-70.00 Hz
[ 769.623] (II) VESA(0): Monitor0: Using maximum pixel clock of 65.00 MHz
[ 769.623] (WW) VESA(0): Unable to estimate virtual size
[ 769.623] (II) VESA(0): Not using built-in mode "1600x1200" (hsync out of range)
[ 769.623] (II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range)
[ 769.623] (--) VESA(0): Virtual size is 1024x768 (pitch 1024)
[ 769.623] (**) VESA(0): *Built-in mode "1024x768"
[ 769.623] (**) VESA(0): *Built-in mode "800x600"
[ 769.623] (**) VESA(0): *Built-in mode "640x480"
[ 769.623] (==) VESA(0): DPI set to (96, 96)
[ 769.623] (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (118)
[ 769.624] (II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (115)
[ 769.624] (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (112)
// Another fragment:
[ 769.384] (II) LoadModule: "glx"
[ 769.384] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 769.392] (II) Module glx: vendor="X.Org Foundation"
[ 769.392] compiled for 1.16.0, module version = 1.0.0
[ 769.392] ABI class: X.Org Server Extension, version 8.0
[ 769.392] (==) AIGLX enabled
[ 769.392] (II) LoadModule: "vesa"
[ 769.393] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 769.395] (II) Module vesa: vendor="X.Org Foundation"
[ 769.395] compiled for 1.16.0, module version = 2.3.2
[ 769.395] Module class: X.Org Video Driver
[ 769.395] ABI class: X.Org Video Driver, version 18.0
[ 769.395] (II) VESA: driver for VESA chipsets: vesa
[ 769.395] (++) using VT number 1
[ 769.395] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 769.395] (II) Loading sub module "vbe"
[ 769.395] (II) LoadModule: "vbe"
[ 769.396] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 769.396] (II) Module vbe: vendor="X.Org Foundation"
[ 769.396] compiled for 1.16.0, module version = 1.1.0
[ 769.396] ABI class: X.Org Video Driver, version 18.0
[ 769.396] (II) Loading sub module "int10"
[ 769.396] (II) LoadModule: "int10"
[ 769.398] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 769.399] (II) Module int10: vendor="X.Org Foundation"
[ 769.399] compiled for 1.16.0, module version = 1.0.0
[ 769.399] ABI class: X.Org Video Driver, version 18.0
[ 769.399] (II) VESA(0): initializing int10
[ 769.421] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 769.424] (II) VESA(0): VESA BIOS detected
[ 769.424] (II) VESA(0): VESA VBE Version 3.0
[ 769.424] (II) VESA(0): VESA VBE Total Mem: 32768 kB
[ 769.424] (II) VESA(0): VESA VBE OEM: SiS
[ 769.424] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
[ 769.424] (II) VESA(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp.
[ 769.424] (II) VESA(0): VESA VBE OEM Product: 6330
[ 769.424] (II) VESA(0): VESA VBE OEM Product Rev: 3.72.10
[ 769.448] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[ 769.448] (==) VESA(0): RGB weight 888
[ 769.448] (==) VESA(0): Default visual is TrueColor
[ 769.448] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 769.448] (II) Loading sub module "ddc"
[ 769.448] (II) LoadModule: "ddc"
[ 769.448] (II) Module "ddc" already built-in
[ 769.533] (II) VESA(0): VESA VBE DDC supported
[ 769.533] (II) VESA(0): VESA VBE DDC Level none
[ 769.533] (II) VESA(0): VESA VBE DDC transfer in appr. 0 sec.
[ 769.576] (II) VESA(0): VESA VBE DDC read failed
[ 769.576] (II) VESA(0): Searching for matching VESA mode(s):
Last edited by nbd (2014-08-05 09:17:50)

I tried the 'xf86-video-sis' from the official repositories, but it didn't work: 'X -configure' outputs that no devices are found.
The command
# lspci | grep SiS
gives the output:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 662 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0)
00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA (rev 01)
00:1f.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (rev 04)
The command 'X -configure' with the 'xf86-video-vesa' driver produces the following xorg.conf file:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card0"
Driver "vesa"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
The X server is started via startxfce4 in the ~/.xinitrc file:
#!/bin/sh
# ~/.xinitrc
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec startxfce4
I tried to use the recommendations about using xrandr. The command
# cvt 1280 1024
produces the following:
# 1280x1024 59.89 Hz (CVT 1.31M4) hsync: 63.67 kHz; pclk: 109.00 MHz
Modeline "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync
Then I perfrom the following two commands:
# xrandr --newmode "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync
# xrandr --addmode default "1280x1024_60.00"
This adds the 1280x1024 mode to the list of available modes in the display control panel, but when
this mode is selected - nothing happens and the resolution remains the same: 1024x768.
EDIT:
I tried all three SiS drivers from the repository: sis, sisusb and sisimedia. In all three cases 'X -configure' failed with an error message: "No devices to configure". The strange thing is that the vesa driver worked OK out of the box. What could cause such a strange problem with the screen resolution?
EDIT 2:
The cause of the problem was the cable from the monitor to the computer: it was twisted and apparently was causing some aberrations to the signal. I found out it when added to the xorg.conf file the line HorizSync = 58-61. After adding that line the problem disappeared. I began to think why the things previously have been working OK without that line. And supposed that the matter is in hardware. I straighted out the cable and the problem isn't occuring anymore even without the xorg.conf editings.
Last edited by nbd (2014-08-04 17:58:13)

[SOLVED] Updating Xorg screwed up my screen-resolution.

Similar Messages

Maybe you are looking for