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

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

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

  • Best screen resolution and output for CBT

    What would be the best screen resolution and output mode IYO for a CBT (Computer Based Training) program?  We would like to do either CD or online.  We are toying with either, so which do you think would be a better option for what Captivate is capable of?  Thanks!

    Nclarkats,
    While most of our employees have similar screen resolutions, a few have larger (or smaller) set ups and since we wish to avoid horizontal and vertical scroll bars; we publish with Captivate's 800 x 600 setting.  This allows us to get a bit larger imagery in place.
    Whatever you choose, try and pick something and stay consistent.  This is beneficial in the event you have to transfer slides between modules.
    Hope that helps.
    Chuck

  • 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?

  • Solaris 10  x86 console screen resolution and blank console after exiting X

    Hello,
    At some point my Solaris 10 machine stopped showing the console after leaving Xorg for the console login. I know the console is active because I can blindly pass the shutdown or other command and it will respond, or after waiting a few minutes will bring the GUI login back. I can see the console before the GUI login while booting but not after. I have a dual output Nvidia 6200 on a 22" LCD running Solaris 10 using the latest Nvidia drivers. I would also like to know if it possible to set the console screen resolution somehow either from the shell or from grub? I have been searching the internet for weeks about this and am unable to find a solution.
    TIA,
    Brett

    After doing even more searching, it looks as if this is an issue with Nvidias drivers. At least similar issues on Linux and FreeBSD that I have seen. Anyone know of a fix other than reverting to much older drivers? Still cannot find any info on setting the console screen resolution, though I can't even see it at the moment unless I refrain from ever starting X again. There has to something similar to vga= that's used in Linux. Anyone?
    Brett

  • Kde screen resolution with nvidia driver

    Hi,
    I am completely new to ArchLinux.  I really enjoyed installing it and its a hoot to play around with!
    I am having a problem getting the screen resolution to work well with the monitor and the resolution with KDE 4.3.  I found that by changing the resolution to 1024x768 and changing the refresh rate to 53 or 54hz, the fonts that otherwise display horribly with the nvidia driver and installed nvidia card will suddenly become beautiful.  I went to Kmenu, Settings, then display settings, and changed the configuration, and everything worked great.
    But on next boot up after I have shut down the computer, X doesn't remember these settings and the fonts look terrible again.  If I open the kmenu again and look at the display settings, they are still set at 1024x768 and 54 hz.  Once I have looked at them, the screen on the monitor goes dark for a second.  Then the computer knows that I want those settings without me changing anything, and adjusts to them without having to hit the apply button.  Then the fonts look great again.
    How can I get the display to start with those settings?  I have tried several configurations of the /etc/X11/xorg.conf file without success, so I need some help.
    Thanks
    Last edited by munguanaweza (2009-11-13 17:06:17)

    I know some time back using nvidia driver with my particular monitor, i had to tell it what resolution/refresh rate to use by default or else X would make a poor choice as to what it wanted the default to be (put me in 800x600 or something like that  by default).  I was able to tell X to default to what I wanted by adding in a Metamode line in my xorg.conf, i think under the screen section. I'm out right now and won't be back to my box to look up exactly what I did, but hopefully this might give a starting point if you havent tried it already.  Metamodes in xorg.conf under the Display section if i remember right.  I specified a resolution there and it now uses that as the default.

  • Windows XP Pro Desktop - Screen Resolution and Color Quality

    When synchronizing my Zire after many successful and no problems the XP Pro screen resolution reverted to the lowest profile.
    I can reset the resolution to the True color 1024 x 768 but after a minute or two it reverts again.
    1. Reinstalled driver for Intel video on Compaq D510C motherboard and get same problems as well as corrupted looking graphics on screen.
    2. Switched to a known good monitor and same problems (which I did not think was the problem but did to verify).
    3. Installed new gForce5200fx graphics card and video still reverts and is corrupted looking even when in higher reset resolution.
    4. Created new user to see if user profile was corrupted and still reverts and is corrupted looking even when in higher reset resolution.
    Any suggestions?????

    I also flashed the bios

  • Adobe Reader 9.3.4 causes poor screen resolution and unreadable pdf documents. Why?

    When I open Reader (9.3.4) the screen resolution becomes very poor - like a color monitor from the early 80's - and text in pdf documents is highlighted black or some other random color, making it unreadable.  This has been the case since I upgraded from Reader 8 recently. Any ideas on how to fix this?

    To those that tried to assist me with trying to get Reader to display
    correctly.  Thanks for your assistance.
    I resolved the problem  by doing a backup of all my files, then formatting the hard drive and reinstalling all programs, from XP to Trend Micro, to Office 2003 and finally Reader 9.
    The problem has gone and the speed and stability of my PC has been greatly improved.

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

  • Windows XP Pro Desktop - Screen Resolution and Color Quality - After Palm 6.2 Installation for Palm TX

    Recently upgraded my Palm software to 6.2. for my TX.  Now when I sync to Outlook, my windows desktop reverts to lower quality screen resolution (640 x 480 pixels) and lower color quality (8 bit).
    I then make the necessary display changes for my windows desktop back to higher quality screen resolution (1280 x 800 pixels) and highest color quality (32 bit).  Everything is fine until I sync again or shut down the computer and restart, causing the windows desktop to revert back to the lower quality screen.
    Any thoughts on possible solutions to this annoying problem.
    Thank you
    Post relates to: Palm TX

    Hello!
    First thing to do is to update the display driver for your computer.  Also make sure to use 96 DPI for the DPI setting, using another setting can cause this issue too.
    Post relates to: Treo 650 (Unlocked GSM)
    Message Edited by thetreoguy on 03-17-2009 10:29 AM

  • Current screen resolution and availability of soundcard under Mac???

    Hi
    How can I define current screen resolution under Mac OS X?
    Under Windows I use function baScreenInfo("width"),
    baScreenInfo("height")
    for this purpose or baMultiDisplayInfo("primary", "width")
    etc
    The same question concerns to availability of soundcard
    Under Windows I can define, if the soundcard is installed
    using function
    basoundCard()
    What about mac OS X ?
    Any help will be appreciated
    game_dev

    You don't need buddyAPI to find out the user's screen
    dimensions. You can just ask for the desktopRectList. This will
    give you a list of screen rects. If there is more than one rect in
    the list, then the first one is the user's primary screen. All macs
    have built in sound. You don't need to check for sound for a mac
    user.

  • [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] "mesa-libgl and nvidia-libgl-beta are in conflict"

    I just tried to install blueman (GTK+ bluetooth manager), and I was greeted with the pleasant message:
    :: mesa-libgl and nvidia-libgl-beta are in conflict (libgl). Remove nvidia-libgl-beta? [y/N]
    I've looked it up and seen many similar scenarios (with nvidia-libgl instead of nvidia-libgl-beta), but they all seemed to be resolved by uninstalling nouveau; I don't have that installed.
    Any ideas as to where I should go from here?
    Last edited by mocha_bean (2015-06-14 18:31:54)

    Ledti wrote:
    You could try downloading the tarball and building blueman with makepkg to rule out pacaur.
    # check to see if it's unrelated to blueman and just a conflict during update, force resync
    sudo pacman -Syyu
    # try building with makepkg and see if it still tries to pull mesa-libgl
    curl -L -O https://aur.archlinux.org/packages/bl/blueman/blueman.tar.gz
    tar -xvf blueman.tar.gz
    cd blueman
    makepkg -sic
    edit: er, /facepalm... I made a mistake. If those two steps don't work then I'm not sure what else you could try.
    I just built it with makepkg and it worked. ¯\_(ツ)_/¯
    Thanks!

  • [SOLVED] mesa-libgl and nvidia-libgl are in conflict

    :: Starting full system upgrade...
    resolving dependencies...
    looking for inter-conflicts...
    :: mesa-libgl and nvidia-libgl are in conflict (libgl). Remove nvidia-libgl? [y/N]
    I don't have mesa-libgl installed... but using nvidia resp. nvidia-libgl
    What's this all about? Why is it in conflict with a package not installed?
    Last edited by rtfreedman (2013-09-28 22:58:49)

    rtfreedman wrote:
    Please post full output of pacman, and use [ code ] instead of [ quote ].
    Well, I quoted the 'full output of pacman' - there was no code in it.
    When pasting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
    like this
    It makes the code more readable and - in case of longer listings - more convenient to scroll through.
    It is important you post it in full, even (or especially) when it's so short. You should include the command you used, not just the output.
    rtfreedman wrote:
    You're doing an update and something is trying to install mesa-libgl which conflicts with the already installed nvidia-libgl.
    Find out which package is it.
    Why should an already installed package trying to install another package afterwards?
    You are installing new versions of some packages. They may have different dependencies from the versions you have currently installed, so you will end up installing some new packages too.

Maybe you are looking for

  • Opening InDesign files in CS5 created in CS4 I get this message.

    I have a few files that I'm unable to open, CS4 or CS5, I created them in CS4 when trying to open I get this message "Can not open such and such file Adobe InDesign may not support the file format, a plug-in that supports the file may be missing, or

  • Why is my macbook pro running slow since ive upgraded to yosemite?

    EtreCheck version: 2.1.8 (121) Report generated March 19, 2015 at 11:45:45 PM PDT Download EtreCheck from http://etresoft.com/etrecheck Click the [Click for support] links for help with non-Apple products. Click the [Click for details] links for more

  • JApplet won't switch image??

    Hi everyone... My JApplet was supposed to display a new image when the sign up button is pressed.. But it doesn't.. Here take a look at my source code! import java.awt.*; import javax.swing.*; import java.awt.event.*; import java.applet.*; public cla

  • Upgrade iWork from v.8 to latest what do I need to do?

    Upgrade iWork from v.8 to latest what do I need to do?

  • Ajax Testing issue with e-Tester

    I'm new to using Empirix and we are using it to work with a new site that uses Ajax. I have recorded the script fine but there is an issue with the Link that needs to be clicked on that it will either always change or the index will change. I've trie