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

Similar Messages

How to solve screen resolution in bdc

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

Hi,
Pls check other posts in SDN before posting ur thread..there is same thread related to this on this forum on same day.
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

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

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

[SOLVED] Screen resolution selector for non-standard Window managers

Hi.
I just replaced the propietary Nvidia drivers with Nouveau. I usually use the console, and when in GUI, i used nvidia-tools to change screen resolution and dual monitors, which now is not possible, Gnome and KDE have its own tools to do that, but i am using fvwm, and dont know any X program that allows me to do this. I tought of using console and script, bit i'd rather prefer to have a name of some program that allows me to do that, and i could install in other computers.
So, anyone knows any program that would allow me to change screen resolution, and maybe dual monitors in X, witout any Gnome or KDE dependencies?
Thank you very much in advance
Last edited by vladimir_1922 (2011-06-01 13:31:20)

-auto answer-
i did a yaourt -Ss xrandr, and found arandr, the graphical api of xrandr, which is exactly what i wanted. Anyway i would love if anyone knows more programs.

[SOLVED] Screen/Resolution problem in Gnome/Xfce

Hello,
My default resolution on starting gnome or xfce is 1024x768. It looks fine and the fonts are definitely pleasant.
One problem: The screen is cut off from the left and right (two black bands on the sides), because of which I'm losing, say, 1/5th of the width (moreover, its irritating).
I'm able to change the resolution from within gnome/xfce to 1280x800 in which case the black bands on the sides disappear and gnome/xfce is using the full width. But now the fonts are not that good; not as smooth.
Is this some basic hardware recognition problem?
Faraz.
Last edited by fh (2009-07-13 17:31:38)

This is now solved. I changed xorg.conf to include 1280x768 along with other resolutions. And then xfce/Appearance lets me set LCD, GRB, aliasing options.

Screen resolution on second monitor incorrect

Hi, I just got a new 2015 MacBook Air 13".
I use a 20" VGA second monitor at work with my 17" MacBook Pro with no problems. I also use three different projectors in the building with my 17" MBP with no problem.
My new MBAir, however, will not use all the pixels available on any of these displays.
For example, on the second VGA monitor I've used for years with my 17", the MBAir displays only in a small box in the center with a few inches of black border around the display. Of course, if I set the monitor to "scale up", the screen is filled but with a pretty blurry pixelated display. Pretty unpleasant to use.
All of the projectors display at low resolution, too.
It's important to note that the 2015 MBAir should be able to handle the 20" VGA monitor with no problem. This MBAir has been shown to be able to drive a 4k display.
I can't increase the resolution under display settings. It just isn't an option. There are only two options and the one I described above (with the huge black border) is the maximum.
I've tried detecting displays repeatedly but it does absolutely nothing.
What could the problem be? I may have to return this machine if it can't be fixed.

As far as I know, that resolution isn't available through VGA. I thought you said your machine has dual DVI out... Does your second monitor not have a DVI input? If it does, why aren't you using it?

[solve] Screen resolution changed after upgrading xorg please help?

Ive been using arch for almost a year now and have grown to like it a lot. I recently updated my system with pacman -Syu. during this process my xorg was updated and now im having issues.
I usually run my monitor at 1152 x 864 running at 85 for a refresh rate. Id like to continue doing that.
Since updating i now run at 1280x720.
Everything looks retarded as a result.. and id really like to get things back to normal. Ive pasted my xorg.conf here.. the modeline for the correct resolution is still there but it would seem xorg isnt respecting it.
I will admit to using a REALLY old radeon graphics card (radeon 7000) but it has never been an issue in the past with arch or any other distro.
Please help me restore my usual openbox display settings.
Thanks.
thewayofzen
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/artwiz-fonts"
EndSection
Section "Module"
Load "bitmap"
Load "ddc"
Load "extmod"
Load "int10"
Load "vbe"
Load "record"
Load "GLcore"
Load "dbe"
Load "xtrap"
Load "dri"
Load "glx"
Load "extmod"
Load "type1"
Load "freetype"
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"
#DisplaySize 330 240 # mm
Identifier "Monitor0"
VendorName "DEL"
ModelName "DELL D1025TM"
### Comment all HorizSync and VertRefresh values to use DDC:
HorizSync 30.0 - 85.0
VertRefresh 50.0 - 120.0
Modeline "1152x864_85.00" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
Gamma 1.71
Option "DPMS"
EndSection
Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "Dac6Bit" # [<bool>]
#Option "Dac8Bit" # [<bool>]
#Option "BusType" # [<str>]
#Option "CPPIOMode" # [<bool>]
#Option "CPusecTimeout" # 
#Option "AGPMode" # 
#Option "AGPFastWrite" # [<bool>]
#Option "AGPSize" # 
#Option "GARTSize" # 
#Option "RingSize" # 
#Option "BufferSize" # 
#Option "EnableDepthMoves" # [<bool>]
#Option "EnablePageFlip" # [<bool>]
#Option "NoBackBuffer" # [<bool>]
#Option "DMAForXv" # [<bool>]
#Option "FBTexPercent" # 
#Option "DepthBits" # 
#Option "AccelDFS" # [<bool>]
#Option "PanelOff" # [<bool>]
#Option "DDCMode" # [<bool>]
#Option "MonitorLayout" # [<str>]
#Option "IgnoreEDID" # [<bool>]
#Option "UseFBDev" # [<bool>]
#Option "MergedFB" # [<bool>]
#Option "CRT2HSync" # [<str>]
#Option "CRT2VRefresh" # [<str>]
#Option "CRT2Position" # [<str>]
#Option "MetaModes" # [<str>]
#Option "MergedDPI" # [<str>]
#Option "MergedXinerama" # [<bool>]
#Option "MergedXineramaCRT2IsScreen0" # [<bool>]
#Option "MergedNonRectangular" # [<bool>]
#Option "MergedMouseRestriction" # [<bool>]
#Option "DisplayPriority" # [<str>]
#Option "PanelSize" # [<str>]
#Option "ForceMinDotClock" # <freq>
#Option "ColorTiling" # [<bool>]
#Option "VideoKey" # 
#Option "RageTheatreCrystal" # 
#Option "RageTheatreTunerPort" # 
#Option "RageTheatreCompositePort" # 
#Option "RageTheatreSVideoPort" # 
#Option "TunerType" # 
#Option "RageTheatreMicrocPath" # <str>
#Option "RageTheatreMicrocType" # <str>
#Option "RenderAccel" # [<bool>]
#Option "SubPixelOrder" # [<str>]
#Option "ShowCache" # [<bool>]
#Option "DynamicClocks" # [<bool>]
#Option "BIOSHotkeys" # [<bool>]
#Option "VGAAccess" # [<bool>]
#Option "ReverseDDC" # [<bool>]
#Option "LVDSProbePLL" # [<bool>]
#Option "AccelMethod" # <str>
#Option "ConstantDPI" # [<bool>]
Option "AGPMode" "4"
Option "AGPFastWrite" "True"
Option "EnablePageFlip" "True"
Identifier "Card0"
Driver "ati"
VendorName "ATI Technologies Inc"
BoardName "Radeon RV100 QY [Radeon 7000/VE]"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
# SubSection "Display"
#DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1200x720" "1152x864" "1024x768" "800x600" "720x400" "720x350" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1200x720" "1152x864" "1024x768" "800x600" "720x400" "720x350" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1200x720" "1152x864" "1024x768" "800x600" "720x400" "720x350" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1200x720" "1152x864" "1024x768" "800x600" "720x400" "720x350" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1200x720" "1152x864" "1024x768" "800x600" "720x400" "720x350" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1200x720" "1152x864" "1024x768" "800x600" "720x400" "720x350" "640x480"
EndSubSection
EndSection
# 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
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
Last edited by thewayofzen (2007-11-16 12:22:55)

Is there anything insteresting in /var/log/Xorg.0.log? Have you tried switching the driver to vesa?
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/artwiz-fonts"
EndSection
Section "Module"
Load "bitmap"
Load "ddc"
Load "int10"
Load "vbe"
Load "record"
Load "GLcore"
Load "dbe"
Load "xtrap"
Load "glx"
Load "extmod"
Load "type1"
Load "freetype"
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 "DEL"
ModelName "DELL D1025TM"
Option "DPMS"
EndSection
Section "Device"
Identifier "Card0"
Driver "ati"
VendorName "ATI Technologies Inc"
BoardName "Radeon RV100 QY [Radeon 7000/VE]"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1152x864"
EndSubSection
EndSection
Try using the above as your xorg.conf file - I've cleaned it up a bit and removed everything that's not essential. If it works you can always add all the that you need from your old xorg.conf file and if it doesn't - well, I guess it won't hurt to try...
Last edited by fwojciec (2007-11-14 07:09:02)

[Solved] Screen resolution problem in a qemu guest

Hi, I have a problem with my arch os on qemu : there is a black line (near 100 pixels high) on the bottom of the virtual screen, and when i put the cursor on the bottom the screen slide (I don't see the top part of the virtual screen). I use "-vga qxl" option, and I use dwm on both the guest and the host.
Have you any ideas from where this problem could come from?
Thanks for reading, and sorry for my English, I hope you understood what I said...
Last edited by c4ffein (2014-07-26 15:08:08)

Well, you can set the resolution yourself, check 'xrandr'.
Did you set the mouse to -usbdevice tablet or -usbdevice mouse?, otherwise try the latter former. There is some kind of solution https://wiki.archlinux.org/index.php/QE … or_erratic, which don't work good enough for me, but might work for you.
Btw. nothing wrong with your English
edit;it was late
Last edited by qinohe (2014-07-26 13:36:57)

Screen resolution when PXE boot from WDS vs Install Windows 8.1 from USB

Hi all
I own a Lenovo ThinkPad T430s, X230 Tablet, and now have my hands on a T440. All three machines have UEFI Secure Boot enabled properly, i.e. Windows boot screen shows Lenovo logo instead of Windows logo.
However, if I do a PXE boot (using Windows Deployment Services from Windows Server 2012, not R2) and boot to the same boot.wim provided on a Windows 8.1 ISO image, the boot screen resolution turns crap, and the WinPE environment runs in 640x480. Also, as opposed
to the Lenovo logo showing on the boot screen, the Windows logo shows up instead, indicating it's not doing a secure boot?
When booting from a USB stick however, using the same Windows 8.1 boot.wim (copied from ISO), the screen resolution in Windows Setup is detected correctly, and the Lenovo logo shows up.
This occurs on all three machines since MDT was upgraded to MDT 2013 or when I replaced Windows 8 boot.wim with Windows 8.1 boot.wim (as the Windows ADK 8 --> ADK 8.1).
Is there a fix for this? Do others have the same problem elsewhere?
Many thanks

Hi,
When boot UEFI-based computer from PXE you should take more into consideration.
For some computers, you might have to perform additional steps to make sure that Windows is installed in UEFI mode, and not in legacy BIOS-compatibility mode.
Some computers might support UEFI. However, they do not support a PXE-initiated boot when in UEFI mode.
How to Create a PXE-Initiated Windows 8 Deployment for UEFI-Based or BIOS-Based Computers in Configuration Manager
http://technet.microsoft.com/en-us/library/jj938037.aspx
Especially for “Pre-Deployment Considerations”
If you still cannot find a way to make it boot from UEFI mode, you should contact with manufacture to confirm if PXE-initiated boot is supported.
Hope this helps.

BDC screen resolution

How to do screen resolution in BDC table control ?

so there so many threads for screen resolution check it
how to solve screen resolution in bdc
Screen Resolution in Bdc
How to make screen resolution independent in BDC
Re: Screen Resolution problem in BDC
screen resolution problem in table control
whats the screen resolution problem with bdc's how to solve it?
Screen Resolution Problem in Session Method

I'm getting kernel panics each day as I shut down, the message of restarting by holding down the power button appears on the screen - it began about a month ago and. Do you have any ideas of how to solve the problem?

I'm getting kernel panics each day as I shut down, the message of restarting by holding down the power button appears on the screen - it began about a month ago and. Do you have any ideas of how to solve the problem? I've copied the logs that I found for each kernel panic that still have the message logged. Please help if you can, I have read some of the other comments and perhaps it has something to do with my anti-virus software being on at start up. I have copied the log here. Any advice will be welcome.
Interval Since Last Panic Report: 665204 sec
Panics Since Last Report:          8
Anonymous UUID: D6DCC90D-A5CA-4BBE-A435-3E64A512A51B
Sat May 26 07:23:05 2012
panic(cpu 3 caller 0xffffff80002b4f36): trying to interlock destroyed mutex (0xffffff801a489be0)
Backtrace (CPU 3), Frame : Return Address
0xffffff8160313b00 : 0xffffff8000220792
0xffffff8160313b80 : 0xffffff80002b4f36
0xffffff8160313b90 : 0xffffff8000227e68
0xffffff8160313bd0 : 0xffffff7f80d14250
0xffffff8160313c20 : 0xffffff7f80d14f73
0xffffff8160313cc0 : 0xffffff800059a237
0xffffff8160313d00 : 0xffffff8000586cbf
0xffffff8160313d20 : 0xffffff800057e6e3
0xffffff8160313df0 : 0xffffff800057ed06
0xffffff8160313e20 : 0xffffff8000583c52
0xffffff8160313e70 : 0xffffff8000583d05
0xffffff8160313e90 : 0xffffff80005358b4
0xffffff8160313ef0 : 0xffffff80005367c3
0xffffff8160313f30 : 0xffffff8000536897
0xffffff8160313f60 : 0xffffff80005ccfe8
0xffffff8160313fb0 : 0xffffff80002da5e9
      Kernel Extensions in backtrace:
com.intego.iokit.VBX6NKE(1.0)[211D5E46-3E43-C5DC-9C6A-8C3FFF0F4493]@0xffffff7f8 0d11000->0xffffff7f80d1bfff
dependency: com.apple.iokit.IONetworkingFamily(2.1)[2FCC16E1-34AB-3908-98BD-CCBFA56FFDCE]@0 xffffff7f809b7000
BSD process name corresponding to current thread: iStatLocalDaemon
Mac OS version:
11E53
Kernel version:
Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64
Kernel UUID: A8ED611D-FB0F-3729-8392-E7A32C5E7D74
System model name: iMac11,2 (Mac-F2238AC8)
System uptime in nanoseconds: 69777074610
last loaded kext at 58265763561: com.intego.iokit.VBX6NKE            1 (addr 0xffffff7f80d11000, size 45056)
loaded kexts:
com.intego.iokit.VBX6NKE            1
com.intego.iokit.BehavioralKext            1
com.intego.kext.VirusBarrier.AppBarrierKPI            10.6.8
com.intego.kext.VirusBarrierKPI            10.6.8
com.globaldelight.driver.BoomDevice            1.1
com.huawei.driver.HuaweiDataCardACMData            4.2
Model: iMac11,2, BootROM IM112.0057.B01, 2 processors, Intel Core i3, 3.2 GHz, 12 GB, SMC 1.64f5
Graphics: ATI Radeon HD 5670, ATI Radeon HD 5670, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x802C, 0x31364A53463531323634485A2D3147344431
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x802C, 0x31364A53463531323634485A2D3147344431
Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353637334648302D4348392020
Memory Module: BANK 1/DIMM1, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353637334648302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 4.0.64.8-P2P
Bluetooth: Version 4.0.5f11, 2 service, 18 devices, 1 incoming serial ports
Serial ATA Device: ST31000528AS, 1 TB
Serial ATA Device: OPTIARC DVD RW AD-5680H
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0606, 0xfa140000 / 5
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0606, 0xfa141000 / 9
USB Device: Apple Optical USB Mouse, apple_vendor_id, 0x0304, 0xfa141100 / 8
USB Device: CanoScan, 0x04a9 (Canon Inc.), 0x1904, 0xfa141200 / 6
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 7
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa120000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: HUAWEI Mobile, 0x12d1 (Huawei Technologies Co., Ltd.), 0x1001, 0xfd130000 / 5
USB Device: My Passport 070A, 0x1058 (Western Digital Technologies, Inc.), 0x070a, 0xfd140000 / 6
USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd110000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3

Immediate suspects are the additions you added to you rsystem that installed kexts (drivers). From above,
com.intego.iokit.VBX6NKE            1
com.intego.iokit.BehavioralKext            1
com.intego.kext.VirusBarrier.AppBarrierKPI            10.6.8
com.intego.kext.VirusBarrierKPI            10.6.8
com.globaldelight.driver.BoomDevice            1.1
com.huawei.driver.HuaweiDataCardACMData            4.2
Two experiments you can try.
1. Boot in safe mode and see if you can shut down normally. All thise additions won't be running in safe mode so this test would indicate it is one of them causing the problem.
2. Uninstall all the intego VirusBarrier stuff. That's my first guess and the troublemaker.

Auto-Detect Screen Resolution Does Not Work Across Multiple Monitors With Different Resolutions

Hi,
The Acrobat Pro DC (15.007.20033.2203) auto-detect screen resolution feature does not work with multiple monitors at different resolutions. Acrobat looks fine on my hidpi primary laptop display (Razr 14" 2014) but is completely unusable if I drag or extend the application to a standard HD resolution secondary monitor. Dragging Acrobat from my primary desktop display to the secondary display causes the UI elements to become 2x as large as they should be and makes Acrobat unusable.
Is there a way to make Acrobat auto-detect the display that it is currently on?
Thanks!
-Donald

To prevent it from happing again, you can
1. go to the Mouse preference and turn off the scroll zoom feature.
2. go to the Universal Access preference and disable the zoom features.

I was trying to fix my screen resolution and now it's stuck on auto detect cannot display this video mode. I tried another monitor and it still won't show anything. I'm locked out

I was trying to fix my screen resolution and now it's stuck on auto detect cannot display this video mode. I tried another monitor and it still won't show anything. I'm locked out

Reset the SMC and PRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
About NVRAM and PRAM
Next try Safe Mode boot and and then normal boot
OS X: What is Safe Boot, Safe Mode?

Detect Screen Resolution

Hello, I am a newbie and would appreciate help from all the
helpful people on this forum.
I am creating a site with Dreamweaver but having problems
with screen resolution. I need help with a script that would detect
the screen resolution and load an alternative CSS that would also
change the font. I found several scripts on the internet but none
would work. Can someone help me with this? I found this script but
I am sure I am missing something why it is not working for me. I
spent 2 days trying to make it work and now I feel like I am
loosing my mind. Here is the script
function styleSwitcher(){
var theStyleLink = document.getElementById('styleSwitch');
if (window.innerWidth < 810){
theStyleLink.setAttribute("href","CSS/LowResAdjust.css");
else {
theStyleLink.setAttribute("href","styles_main.css");
What am I **** wrong?
Thanks in advance.
Tinaval

> What am I **** wrong?
Worrying about screen resolution. It's meaningless. What
matters is the
browser's viewport dimensions and that is unpredictable. Best
to design for
a set width (I usually use 780px) or create a fluid layout
(generally I hate
them).
Walt
"Tinaval" <[email protected]> wrote in
message
news:ff1dtn$sdc$[email protected]..
> Hello, I am a newbie and would appreciate help from all
the helpful
> people on
> this forum.
>
> I am creating a site with Dreamweaver but having
problems with screen
> resolution. I need help with a script that would detect
the screen
> resolution
> and load an alternative CSS that would also change the
font. I found
> several
> scripts on the internet but none would work. Can someone
help me with
> this?
> I found this script but I am sure I am missing something
why it is not
> working
> for me. I spent 2 days trying to make it work and now I
feel like I am
> loosing
> my mind. Here is the script
>
> function styleSwitcher(){
> var theStyleLink =
document.getElementById('styleSwitch');
>
> if (window.innerWidth < 810){
>
theStyleLink.setAttribute("href","CSS/LowResAdjust.css");
>
> }
> else {
> theStyleLink.setAttribute("href","styles_main.css");
>
> }
> }
>
> What am I **** wrong?
>
> Thanks in advance.
> Tinaval
>

[SOLVED]Screen resolution began to be incorrectly detected

Similar Messages

Maybe you are looking for