[SOLVED] Screen resolution issue

I've had an issue with screen resolution for awhile. Basically, I have it set
correctly, but a small portion of the screen is cut off on the right-hand side
of the screen. When using just the CLI, it's about a character that gets cut
off, In X (regardless of DE) it's about half the width of a toolbar. It's not
that big a deal, but it's really starting to bother me. I know I have the
resolution set correctly (1680x1050). The monitor is a LG Flatron W2252TQ.
Any ideas?
Last edited by BugenhagenXIII (2009-05-31 21:29:22)

Wow, that was the simplest fix ever. I can't believe I didn't think of that. All it took was one button press.
Last edited by BugenhagenXIII (2009-05-31 21:31:26)

Similar Messages

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 issue - BDC Grid

Hi All,
I am facing an issue with BDC for PRMM transaction.
If we look at the PRMM transaction, the very first screen consist of GRid forAction type.
The records in the grid of PRMM transaction is changing as per the screen resolution of User desktop.
Example: In my screen, I am able to see 16 rows in Grid and in user desktop i can see 10 or 20 rows. Because of this the Pagedown option and BDC is not behaving properly.
Please suggest what should be done to resolve it.
Thanks,
Shilpa

Hi Shilpa,
during recording from SHDB, use check box for Default Size.
in call transaction syntax: use
data: wa_opt type ctu_params.
wa_opt-dismode = w_mode. [N OR A OR E]
wa_opt-defsize = c_check.[X]
wa_opt-updmode = 'A'.
CALL TRANSACTION c_me41 USING i_bdcdata
OPTIONS FROM wa_opt [INSTEAD OF HARD CODING MODE]
MESSAGES INTO i_msgcoll.
Hope this can solve your problems.
Regards,
Tutun

[SOLVED] Screen brightness issues with Acer 5372Z

The screen of my laptop goes black whenever I boot into ArchLinux, after "reading Udev events" on startup. Most of the time I have to use a flashlight to see the console on my screen and type
sudo setpci -s 00:02.0 F4.B=20
to set screen brightness manually. The `Fn` + `Brightness up` combination doesn't work on my machine, but that's not an issue with Arch, but fault to sugar in coffee.
There are a lot of similar threads in this forum, but none of the solutions described there really worked 100% or not at all, that's why I'm opening a new thread as this seems to be specific to my hardware.
Details:
Graphics controller:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
Screen resolution:
1366*766
/boot/grub/menu.lst:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/sda10 resume=/dev/sda5 ro vga=775
initrd /initramfs-linux.img
/etc/rc.conf#DAEMONS:
DAEMONS=(hwclock syslog-ng network netfs crond laptop-mode dbus gdm)
I will describe here what I have did so far on hacking:
Installed the video driver for my Intel card as described here in the wiki
Set kernel mode to `nomodeset`, without specifying vga, of course, which surprisingly solved the issue, but prevented me from using Gnome.
The supposed solution in the Arch wiki doesn't work for me. It makes it worse, in the sense of dumping screen brightness even before "reading udev events" on boot.
My current workaround (to avoid using a flashlight) is to put this line into my `/etc/rc.local`:
setpci -s 00:02.0 F4.B=20
I wonder if you can help me to solve this issue, or point me to any of the great documentation provided by the Arch community I might have missed...
Last edited by kennym (2011-09-06 16:03:58)

rg_arc wrote:I have this problem as well for my Acer Aspire 4810TZ. The only thing I can think of is to make some sort of temporary fix. But I agree with you, There should be a permanent fix. Every time I've installed Arch on this computer the same problem arises and the only way I can change the brightness is the setpci terminal method.
This is bad news for new Arch (and Linux) users. This will be probably the point where they will turn over to another distribution.
It seems to be something which has been included in newer kernels, because I can remember that in the 2.6 series this issue did not exist.
Last edited by kennym (2011-09-05 16:05:08)

ThinkPad T500 Screen Resolution Issues

Dear All,
Wonder if anybody can provide any advise on the following issue(s):
Just bought a T500 Centrino vpro, running on XP professional, 15" screen. Really happy with it, its fast and all. However, there seem to be only a few screen resolution options available. On my old Acer Travelmate, I used to have a 1024x600 which suited my myopia just fine. The closest setting to this one seems to be the 1024X768 but it is not great 'cos items appear a tad out of focus.
I understand the T500 i just bought was built to accommodate Vista (as a side note, a Vista Business tag with serial number can be found at the back of my laptop although the machine came with XP pro preinstalled..This leads me to my other question: What happened to my Vista?) and this perhaps explains the limited resolution options available and the fact that apart from the native setting all other resolutions available are not optimal.
Many thanks in advance.
FB

There are several methods to increase the font sizes on your screen:
1) right click on desktop.
2) select personalize
3) select adjust font size (DPI) under the task list on the left
4) select the larger font size that is available.
Sometimes there are fonts that are just too small to read on the web browser.
Hold down your Ctrl key and use the mouse scroll button to increase the font size.
Alternatively Press the blue Fn button on the keyboard and then press the Space bar.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

Screen Resolution Issue upon Install

Howdy,
I just installed Arch for the first time (after using Ubuntu for a few years) and I'm having a problem. For some reason, it is messing up the screen resolution after rebooting the system. It occurs every time, and the text appears to both wrap around the monitor from the middle and extend beyond the bottom of the screen. The error is reproducable; when I boot up an Ubuntu live-cd, I get the same issue when trying to set my screen resolution to 1280x800. Every mode below that works just fine.
I tried a bunch of different things with respect to the screen resolution, but no matter what I set "vga=" to, I can't get it to display properly. X will open just fine, but with the same issue. For reference, here are the specs of my computer:
http://h10025.www1.hp.com/ewfrf/wc/docu … ct=3686683
Also, I am using the x86_64 install, though it happened with the i686 one as well.
Any help is appreciated, and though I will do what I can, it will be hard for me to post anything from arch since I can't see much.
Thank you in advance

Are you using any DE? Does it happen even before you install X?
There's a similar thread https://bbs.archlinux.org/viewtopic.php?id=119606

Screen Resolution Issue, Itunes? Vista?

Hello!
Ok, so every time I open Itunes my screen resolution gets automatically switched to the lowest possible resolution. An itunes pop up keeps saying:
"For best results with itunes, use a screen resolution of at least 1024x768. You can change this setting in Display Settings".
Which doesn't make sense to me anyway because why would it be switched to low when its saying it needs to be higher?
I go into control panel and switch it back to a higher resolution only to have the same problem EVERY time I open itunes. I'm using vista but the pop ups are definitely from itunes. A second pop up message that shows up is:
"Itunes.exe has been set to run in compatibility mode for an older version of windows. For best results turn off compatibility mode for itunes before you open it."
So, I check under properties for itunes.exe and compatibility mode is NOT checked off. I can't figure out where to turn off compatibility. This issue and the pop ups only started after I ran itunes "as administrator" so vista would let me edit song information.
Can anyone help me?
Thanx

So I've answered my own question. In the properties tab of itunes.exe I went into Settings for all Users and unchecked the screen resolution option. Relatively simple, but it proved exceedingly frustrating. I guess in Vista you just have to uncheck everything twice. I still can't get rid of the compatibility mode message, but that was the least of my worries.

Macbook Pro Retina Screen Resolution Issues

I have just bought a retina display Macbook Pro (Early 2013) with OS X 10.8.3 Mountain Lion.
Before getting it, I did not realize what an effect it would have on the use of my existing programs, and had I known, I would have thought twice before switching from my non-Retina Macbook Pro. I have never had so many problems with a brand new computer. On my retina screen, programs such as Microsoft Office 2011, Adobe Creative Suite 5 and Acrobat Pro X run with an awful screen resolution and impossibile legibility. The pixelated graphics and image quality hurt my eyes, beyond the fact that I cannot see my lines, images and text properly in order to work with them.
In these programs, the "Open in Low Resolution" button is enabled permanatly and cannot be changed as it's option is ghosted out. I do not know how to make it look better or what to do. I cannot work using this low resolution and this issue has affected my productivity.
<Edited by Host>

nadia_d,
You have a new MBP you have 14 days to return/exchange, 90 days of free phone support, as well as 1 year at the store. Take advantage of this.
Phone 800-692-7753

Windows 7 screen resolution issues

Hello
I've recently had to install Windows 7 on Bootcamp on my MacBook Pro - late 2011, 4GB RAM, 1GB AMD Radeon card - and I'm having three minor issues that are slowly driving me nuts:
1) the screen resolution looks kinda fuzzy, with fonts looking readable but nowhere as clear as on the Mac side or even in normal Windows laptops;
2) the maximum screen resolution is 1152x864. I thought I'd be allowed same resolutions as on the Mac side. Also because of that 4:3 ratio...
3) ...the screen looks distorted, meaning all images I have to use in my work also look visibly out of proportion. Is there a way of fixing this, i.e using the Mac's 1.6:1 ratio?
Could that be because perhaps the system is not recognising the video card?
Many thanks to all and happy new year
R

Gabriel Valdes wrote:
Where did you get the bootcamp support files?
Step 1 in Boot Camp, Download The Windows Support Software.

[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| - 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).

IMac/Boot Camp Screen Resolution Issue on XP

Anyone here running Boot Camp on an iMac? I just loaded it on my MBPro and it works great, but on my iMac I can't get the screen resolution straight. My images are stretched when shown in XP. It's a 24" iMac.
Thanks

Post your question in the Boot Camp discussions:
http://discussions.apple.com/forum.jspa?forumID=1165

X201 screen resolution issues

My x201 has a maximum screen resolution in the settings of 1280 x 800 but states that anything under 1280 x 960 may mean that some information is not displayed on the screen. I have this problem with a program that I am running. Any suggestions please.....

you can change it.
even on a netbook you can change the resolution.
make sure you have the right drivers fot the GPU.
go to the site and grab it.
i run customs all the time but you will need full software support of the graphic chip so that means not just the display driver but it software as well.
go to intels site for that.
most pc makers dont include the software just the display driver.
same one as windows has built in.
once you have fiull surport you can change it easy even give it a boost,adjust certin things.
intel is not as complex as say AMD or nvid but it getting better.
there be a limit to what the latop own display can do dpi wise size wise so on and what you read well on it depends on options too alot have a finer pith disply.
again install the software package for that chipset.

Screen Resolution Issues

Hi,
I am working with a developer on an application in air and we are having trouble adjusting the screen resolution to meet the various computers that will be running the app.
On my computer with resolution of 1440 x 900 the app looks great but as soon as we install it on another computer with moderately weaker resolution, much of the program is cut off.
Is there a way have the applicaiton adjust to different screen resolutions automatically? Or is there something we can write into the code that would not require countless hours of labor?
Or can you make a recomendation as to the resolution we should be focusing on?
Thanks!

Design your app with the minimum screen res your audience would be using (i.e. if you plan on making your app for your gamer friends, assume theyll be on a higher resolution, your grandmother is probably a lower res). 1024x768 is the safest bet.
use
stage.displayState = StageDisplayState.FULL_SCREEN_INTERACTIVE;
instead of trying to force a specific size.

Screen Resolution issue with most third party Apps

I have noticed that the screen resolution on my new iPhone 6 is not the same across the apps. For example when I open Facebook, the fonts seems to be like a little blurred and the background appears blurred. I am sure the third party apps need to work with the new iPhone to get it fixed. But just wanted to make sure that there is no need to do anything at this point. These apps are making the new iPhone screen resolution look sub-standard which is in no way Apple's fault. These Apps need to grow up faster and release updated versions before the users start cursing them for lagging behind lol..
On the other hand the Apps designed by Apple work perfectly fine!
The new iPhone 6 is beautiful! Thank you Apple! I love you.

I can't help with the problem, since I don't have a laptop or second monitor, but if you want to report this to Apple, send a bug report (or enhancement request) via its Bug Reporter system. Join the Apple Developer Connection (ADC)—it's free and available for all Mac users and gets you a look at some development software. Since you already have an Apple username/ID, use that. Once a member, go to Apple BugReporter and file your bug report/enhancement request. You'll get a get a Bug ID number; thus, starting a dialog directly with engineering.

[SOLVED] Screen resolution issue

Similar Messages

Maybe you are looking for