Photoshop, multi-monitor setup has wobbly lines at left of monitors

Hi All
I'm having a problem with jagged, wobbly lines in Photoshop CS5.1.  This has nothing to do with Smoothing or anything (the wobble is more pronounched with smoothing off however).
I believe it has something to do with my 3 monitor setup in Windows 7 64bit, Nvidia GTX 460, and some sort of positioning error PS can't get it's head around (this affects NO other programs I have like Painter or Artrage).   See below for my setup.  I have the Cintiq 24HD and Intuos 4 and the problem occurs on both tablets.  Any monitor that is set in Windows Display at '0' will have a wobbly line in Photoshop if I draw if the doc is at the left of the monitor and I then draw in that area.
If I place a doc from Photoshop in the centre of the Cintiq - no wobbles.  As soon as I move it near the top left of the Cintiq (when it's monitor position in Windows is aligned directly under Monitor 1 as they are the same size), the wobble starts.  Once it's started on a doc, it continues no matter where you try drawing on the screen after that until I close and reopen Photoshop.
This definitely has NOTHING to do with electromechanical interference to the tablets as I never physically move anything but can change it's occurance by moving the Display layout in Windows.
Any monitor For me it starts from the '0' position up to about the '474' position. If I aligned all my monitors one underneath the other so they were all started at '0', then they'd all do the wobble thing on the lefthand side (using either the Inutos4 or Cintiq).  Windows makes you have your main monitor at '0', so I alway have a problem on that monitor.  The other person I know of who has this problem (posted on the Wacom forum), has said they get around it on their Cintiq (which is the main monitor), by pushing on of their other monitors into a negative setting to the left.
It's a real pain.  Anytime I want to use my Cintiq in Photoshop I have to go into Display setting and move it to the right.  Once you get the wobbles they don't stop.  ie they are then not restricted to the left of the doc, but all over.  You have to close and reopen PS and start again.
Below is an example of the wobble.  First I drew on the right... no wobble.  Then I drew on the left.  Lines are no longer smooth, but jiggly.  Note smoothing is ON.  Wiggling is worse with it off.
I haven't a clue if it's an Adobe problem or a Wacom one.  Note that my graphic drivers etc are all up-to-date and I've uninstalled, reinstalled, cleaned reg, unplugged/replugged, tried just one tablet or other , stood on my head, for Wacom drivers (old versions and newest versions) till I'm blue in the face.  No difference.
Anybody have an idea?  PS Wacom (europe at least) do seem to know of the problem, but are not saying anything else at the moment.

No, it's got nothing to do with electromagnetic interference, or I couldn't change what happened by just altering the monitor position within Windows multimonitor display setup and not moving the tablets physically at all.  And as you say, interference would happen on every program - not just Photoshop.  There is no actual 'cursor' wobble. I've had interferance on older Intuos 3 tablets and at the edges of the old Cintiq 21UX, so know what that is like. 
I think it's either the Windows OS or Wacom Driver, not telling PS something about the Monitor position Or PS not reading the info correctly.

Similar Messages

  • Monitor setup has changed - KDE Daemon after sleep

    After the monitor goes into powersave mode and is restored I keep gettung the Monitor setup has changed - KDE Daemon  box, anyone know how to get rid of this? everything seams to work but the box is getting annoying.  Logs dont show anything wrong and I have tried lots of things to fix it with no solution.

    Ok still cant work this out. manually set monitor settings etc the box still pops up when waking monotor from sleep. logs still show nothing.  Can anyone help?
    Log below
    [ 11.918]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 11.918]
    X.Org X Server 1.13.2.901 (1.13.3 RC 1)
    Release Date: 2013-02-15
    [ 11.918] X Protocol Version 11, Revision 0
    [ 11.918] Build Operating System: Linux 3.7.5-1-ARCH x86_64
    [ 11.918] Current Operating System: Linux ThunderBolt.LoadBalancer.Org 3.7.9-2-ARCH #1 SMP PREEMPT Mon Feb 25 12:04:25 CET 2013 x86_64
    [ 11.918] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=bc60faad-b008-4f1f-8682-88d4c6f235cc ro quiet
    [ 11.918] Build Date: 18 February 2013 03:52:56PM
    [ 11.918]
    [ 11.918] Current version of pixman: 0.28.2
    [ 11.918] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 11.918] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 11.918] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 17:45:33 2013
    [ 12.161] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 12.326] (==) ServerLayout "ServerLayout0"
    [ 12.326] (==) No screen section available. Using defaults.
    [ 12.326] (**) |-->Screen "Default Screen Section" (0)
    [ 12.326] (**) | |-->Monitor "<default monitor>"
    [ 12.326] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 12.326] (**) | |-->Device "Intel Graphics"
    [ 12.326] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 12.326] (**) Option "BlankTime" "0"
    [ 12.326] (**) Option "StandbyTime" "0"
    [ 12.326] (**) Option "SuspendTime" "0"
    [ 12.326] (**) Option "OffTime" "0"
    [ 12.326] (==) Automatically adding devices
    [ 12.326] (==) Automatically enabling devices
    [ 12.326] (==) Automatically adding GPU devices
    [ 12.513] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 12.513] Entry deleted from font path.
    [ 12.561] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 12.561] Entry deleted from font path.
    [ 12.561] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 12.561] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 12.561] Entry deleted from font path.
    [ 12.561] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 12.561] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 12.561] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 12.561] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 12.562] (II) Loader magic: 0x7fcc20
    [ 12.562] (II) Module ABI versions:
    [ 12.562] X.Org ANSI C Emulation: 0.4
    [ 12.562] X.Org Video Driver: 13.1
    [ 12.562] X.Org XInput driver : 18.0
    [ 12.562] X.Org Server Extension : 7.0
    [ 12.562] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 12.563] (--) PCI:*(0:0:2:0) 8086:2e22:1025:0251 rev 3, Mem @ 0xfe400000/4194304, 0xd0000000/268435456, I/O @ 0x0000dc00/8
    [ 12.563] (--) PCI: (0:0:2:1) 8086:2e23:1025:0251 rev 3, Mem @ 0xfe900000/1048576
    [ 12.762] Initializing built-in extension Generic Event Extension
    [ 12.763] Initializing built-in extension SHAPE
    [ 12.763] Initializing built-in extension MIT-SHM
    [ 12.763] Initializing built-in extension XInputExtension
    [ 12.763] Initializing built-in extension XTEST
    [ 12.763] Initializing built-in extension BIG-REQUESTS
    [ 12.763] Initializing built-in extension SYNC
    [ 12.763] Initializing built-in extension XKEYBOARD
    [ 12.763] Initializing built-in extension XC-MISC
    [ 12.763] Initializing built-in extension SECURITY
    [ 12.763] Initializing built-in extension XINERAMA
    [ 12.763] Initializing built-in extension XFIXES
    [ 12.763] Initializing built-in extension RENDER
    [ 12.763] Initializing built-in extension RANDR
    [ 12.763] Initializing built-in extension COMPOSITE
    [ 12.763] Initializing built-in extension DAMAGE
    [ 12.763] Initializing built-in extension MIT-SCREEN-SAVER
    [ 12.763] Initializing built-in extension DOUBLE-BUFFER
    [ 12.763] Initializing built-in extension RECORD
    [ 12.763] Initializing built-in extension DPMS
    [ 12.763] Initializing built-in extension X-Resource
    [ 12.763] Initializing built-in extension XVideo
    [ 12.763] Initializing built-in extension XVideo-MotionCompensation
    [ 12.763] Initializing built-in extension XFree86-VidModeExtension
    [ 12.763] Initializing built-in extension XFree86-DGA
    [ 12.763] Initializing built-in extension XFree86-DRI
    [ 12.763] Initializing built-in extension DRI2
    [ 12.763] (II) LoadModule: "glx"
    [ 12.816] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 12.828] (II) Module glx: vendor="X.Org Foundation"
    [ 12.829] compiled for 1.13.2.901, module version = 1.0.0
    [ 12.829] ABI class: X.Org Server Extension, version 7.0
    [ 12.829] (==) AIGLX enabled
    [ 12.829] Loading extension GLX
    [ 12.829] (II) LoadModule: "intel"
    [ 12.853] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 13.078] (II) Module intel: vendor="X.Org Foundation"
    [ 13.078] compiled for 1.13.2.901, module version = 2.21.3
    [ 13.079] Module class: X.Org Video Driver
    [ 13.079] ABI class: X.Org Video Driver, version 13.1
    [ 13.079] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
    Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
    Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
    Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
    Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
    Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
    Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
    Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
    Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
    Haswell Server (GT2+), Haswell SDV Desktop (GT1),
    Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
    Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
    Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
    Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
    Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
    Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
    Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
    Haswell ULT Server (GT1), Haswell ULT Server (GT2),
    Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
    Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
    Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
    Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
    Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
    ValleyView PO board
    [ 13.079] (++) using VT number 7
    [ 13.213] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 13.213] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 13.213] (==) intel(0): RGB weight 888
    [ 13.213] (==) intel(0): Default visual is TrueColor
    [ 13.213] (**) intel(0): Option "AccelMethod" "sna"
    [ 13.213] (--) intel(0): Integrated Graphics Chipset: Intel(R) G45/G43
    [ 13.213] (**) intel(0): Framebuffer tiled
    [ 13.213] (**) intel(0): Pixmaps tiled
    [ 13.213] (**) intel(0): "Tear free" disabled
    [ 13.213] (**) intel(0): Forcing per-crtc-pixmaps? no
    [ 13.253] (II) intel(0): Output VGA1 has no monitor section
    [ 13.362] (II) intel(0): Output HDMI1 using monitor section HDMI1
    [ 13.403] (II) intel(0): Output DP1 has no monitor section
    [ 13.443] (II) intel(0): EDID for output VGA1
    [ 13.552] (II) intel(0): EDID for output HDMI1
    [ 13.552] (II) intel(0): Manufacturer: GSM Model: 56cc Serial#: 258443
    [ 13.552] (II) intel(0): Year: 2011 Week: 4
    [ 13.552] (II) intel(0): EDID Version: 1.3
    [ 13.552] (II) intel(0): Digital Display Input
    [ 13.552] (II) intel(0): Max Image Size [cm]: horiz.: 53 vert.: 30
    [ 13.552] (II) intel(0): Gamma: 2.20
    [ 13.552] (II) intel(0): No DPMS capabilities specified
    [ 13.552] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 13.552] (II) intel(0): First detailed timing is preferred mode
    [ 13.552] (II) intel(0): redX: 0.635 redY: 0.342 greenX: 0.292 greenY: 0.611
    [ 13.552] (II) intel(0): blueX: 0.147 blueY: 0.070 whiteX: 0.313 whiteY: 0.329
    [ 13.552] (II) intel(0): Supported established timings:
    [ 13.552] (II) intel(0): 640x480@60Hz
    [ 13.552] (II) intel(0): 800x600@60Hz
    [ 13.552] (II) intel(0): 1024x768@60Hz
    [ 13.552] (II) intel(0): Manufacturer's mask: 0
    [ 13.552] (II) intel(0): Supported standard timings:
    [ 13.552] (II) intel(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 13.552] (II) intel(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 13.552] (II) intel(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 138.5 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
    [ 13.552] (II) intel(0): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1111 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 148.5 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 13.552] (II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 13.552] (II) intel(0): Ranges: V min: 56 V max: 61 Hz, H min: 30 H max: 83 kHz, PixClock max 155 MHz
    [ 13.552] (II) intel(0): Monitor name: W2442
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 148.5 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 13.552] (II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 74.2 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 13.552] (II) intel(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 74.2 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 13.552] (II) intel(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 27.0 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 13.552] (II) intel(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 13.552] (II) intel(0): Number of EDID sections to follow: 1
    [ 13.552] (II) intel(0): EDID (in hex):
    [ 13.552] (II) intel(0): 00ffffffffffff001e6dcc568bf10300
    [ 13.552] (II) intel(0): 0415010380351e780aaec5a2574a9c25
    [ 13.552] (II) intel(0): 125054210800b3008180814001010101
    [ 13.552] (II) intel(0): 0101010101011a3680a070381f403020
    [ 13.552] (II) intel(0): 3500132b2100001a023a801871382d40
    [ 13.552] (II) intel(0): 582c4500132b2100001e000000fd0038
    [ 13.552] (II) intel(0): 3d1e530f000a202020202020000000fc
    [ 13.552] (II) intel(0): 0057323434320a202020202020200128
    [ 13.552] (II) intel(0): 020321f14e900403011412051f101300
    [ 13.552] (II) intel(0): 000000230907078301000065030c0010
    [ 13.552] (II) intel(0): 00023a801871382d40582c4500132b21
    [ 13.552] (II) intel(0): 00001e011d8018711c1620582c250013
    [ 13.552] (II) intel(0): 2b2100009e011d007251d01e206e2855
    [ 13.552] (II) intel(0): 00132b2100001e8c0ad08a20e02d1010
    [ 13.552] (II) intel(0): 3e9600132b2100001800000000000000
    [ 13.552] (II) intel(0): 00000000000000000000000000000026
    [ 13.552] (II) intel(0): Printing probed modes for output HDMI1
    [ 13.552] (II) intel(0): Modeline "1920x1080"x59.9 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 13.552] (II) intel(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
    [ 13.552] (II) intel(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 13.552] (II) intel(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 13.552] (II) intel(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 13.552] (II) intel(0): Modeline "1680x945"x60.0 131.48 1680 1784 1960 2240 945 946 949 978 -hsync +vsync (58.7 kHz)
    [ 13.552] (II) intel(0): Modeline "1400x1050"x59.9 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e)
    [ 13.552] (II) intel(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
    [ 13.552] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "1366x768"x60.0 85.89 1366 1439 1583 1800 768 769 772 795 -hsync +vsync (47.7 kHz)
    [ 13.552] (II) intel(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x768"x60.0 68.25 1280 1328 1360 1440 768 771 778 790 +hsync -vsync (47.4 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 13.552] (II) intel(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
    [ 13.552] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 13.552] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 13.552] (II) intel(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 13.552] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 13.593] (II) intel(0): EDID for output DP1
    [ 13.593] (II) intel(0): Output VGA1 disconnected
    [ 13.593] (II) intel(0): Output HDMI1 connected
    [ 13.593] (II) intel(0): Output DP1 disconnected
    [ 13.593] (II) intel(0): Using exact sizes for initial modes
    [ 13.593] (II) intel(0): Output HDMI1 using initial mode 1920x1080
    [ 13.593] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 13.593] (==) intel(0): DPI set to (96, 96)
    [ 13.593] (II) Loading sub module "dri2"
    [ 13.593] (II) LoadModule: "dri2"
    [ 13.593] (II) Module "dri2" already built-in
    [ 13.593] (==) Depth 24 pixmap format is 32 bpp
    [ 13.793] (II) intel(0): SNA initialized with Broadwater/Crestline backend
    [ 13.793] (==) intel(0): Backing store disabled
    [ 13.793] (==) intel(0): Silken mouse enabled
    [ 13.793] (II) intel(0): HW Cursor enabled
    [ 13.793] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 13.794] (==) intel(0): DPMS enabled
    [ 13.794] (II) intel(0): Overlay video not supported on this hardware
    [ 13.794] (II) intel(0): [XvMC] xvmc_vld driver initialized.
    [ 13.794] (II) intel(0): [DRI2] Setup complete
    [ 13.794] (II) intel(0): [DRI2] DRI driver: i965
    [ 13.794] (II) intel(0): direct rendering: DRI2 Enabled
    [ 13.794] (==) intel(0): hotplug detection: "enabled"
    [ 13.794] (--) RandR disabled
    [ 14.124] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 14.124] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 14.124] (II) AIGLX: enabled GLX_ARB_create_context
    [ 14.124] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 14.124] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 14.124] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 14.124] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 14.124] (II) AIGLX: Loaded and initialized i965
    [ 14.124] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 14.125] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
    [ 14.210] (II) intel(0): Setting screen physical size to 508 x 285
    [ 14.922] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 14.922] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 14.922] (II) LoadModule: "evdev"
    [ 14.922] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 14.957] (II) Module evdev: vendor="X.Org Foundation"
    [ 14.957] compiled for 1.13.0, module version = 2.7.3
    [ 14.957] Module class: X.Org XInput Driver
    [ 14.957] ABI class: X.Org XInput driver, version 18.0
    [ 14.957] (II) Using input driver 'evdev' for 'Power Button'
    [ 14.957] (**) Power Button: always reports core events
    [ 14.957] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 14.957] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 14.957] (--) evdev: Power Button: Found keys
    [ 14.957] (II) evdev: Power Button: Configuring as keyboard
    [ 14.957] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 14.957] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 14.957] (**) Option "xkb_rules" "evdev"
    [ 14.957] (**) Option "xkb_model" "evdev"
    [ 14.957] (**) Option "xkb_layout" "us"
    [ 14.988] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 14.988] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 14.988] (II) Using input driver 'evdev' for 'Power Button'
    [ 14.988] (**) Power Button: always reports core events
    [ 14.988] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 14.988] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 14.988] (--) evdev: Power Button: Found keys
    [ 14.989] (II) evdev: Power Button: Configuring as keyboard
    [ 14.989] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
    [ 14.989] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 14.989] (**) Option "xkb_rules" "evdev"
    [ 14.989] (**) Option "xkb_model" "evdev"
    [ 14.989] (**) Option "xkb_layout" "us"
    [ 14.989] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 14.989] (II) config/udev: Adding input device UVC Camera (046d:0825) (/dev/input/event14)
    [ 14.989] (**) UVC Camera (046d:0825): Applying InputClass "evdev keyboard catchall"
    [ 14.989] (II) Using input driver 'evdev' for 'UVC Camera (046d:0825)'
    [ 14.989] (**) UVC Camera (046d:0825): always reports core events
    [ 14.989] (**) evdev: UVC Camera (046d:0825): Device: "/dev/input/event14"
    [ 14.989] (--) evdev: UVC Camera (046d:0825): Vendor 0x46d Product 0x825
    [ 14.989] (--) evdev: UVC Camera (046d:0825): Found keys
    [ 14.989] (II) evdev: UVC Camera (046d:0825): Configuring as keyboard
    [ 14.989] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-6/1-6:1.0/input/input14/event14"
    [ 14.989] (II) XINPUT: Adding extended input device "UVC Camera (046d:0825)" (type: KEYBOARD, id 8)
    [ 14.989] (**) Option "xkb_rules" "evdev"
    [ 14.989] (**) Option "xkb_model" "evdev"
    [ 14.989] (**) Option "xkb_layout" "us"
    [ 14.990] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event4)
    [ 14.990] (II) No input driver specified, ignoring this device.
    [ 14.990] (II) This device may have been added with another device file.
    [ 14.990] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event10)
    [ 14.990] (II) No input driver specified, ignoring this device.
    [ 14.990] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event11)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event12)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event13)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel HDMI/DP,pcm=3 (/dev/input/event6)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.992] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event7)
    [ 14.992] (II) No input driver specified, ignoring this device.
    [ 14.992] (II) This device may have been added with another device file.
    [ 14.992] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event8)
    [ 14.992] (II) No input driver specified, ignoring this device.
    [ 14.992] (II) This device may have been added with another device file.
    [ 14.992] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event9)
    [ 14.992] (II) No input driver specified, ignoring this device.
    [ 14.992] (II) This device may have been added with another device file.
    [ 14.993] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 14.993] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 14.993] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 14.993] (**) AT Translated Set 2 keyboard: always reports core events
    [ 14.993] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 14.993] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 14.993] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 14.993] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 14.993] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 14.993] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 14.993] (**) Option "xkb_rules" "evdev"
    [ 14.993] (**) Option "xkb_model" "evdev"
    [ 14.993] (**) Option "xkb_layout" "us"
    [ 14.993] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/event5)
    [ 14.993] (**) ImPS/2 Generic Wheel Mouse: Applying InputClass "evdev pointer catchall"
    [ 14.993] (II) Using input driver 'evdev' for 'ImPS/2 Generic Wheel Mouse'
    [ 14.993] (**) ImPS/2 Generic Wheel Mouse: always reports core events
    [ 14.993] (**) evdev: ImPS/2 Generic Wheel Mouse: Device: "/dev/input/event5"
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Vendor 0x2 Product 0x5
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found 3 mouse buttons
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found scroll wheel(s)
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found relative axes
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found x and y relative axes
    [ 14.993] (II) evdev: ImPS/2 Generic Wheel Mouse: Configuring as mouse
    [ 14.993] (II) evdev: ImPS/2 Generic Wheel Mouse: Adding scrollwheel support
    [ 14.994] (**) evdev: ImPS/2 Generic Wheel Mouse: YAxisMapping: buttons 4 and 5
    [ 14.994] (**) evdev: ImPS/2 Generic Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 14.994] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input5/event5"
    [ 14.994] (II) XINPUT: Adding extended input device "ImPS/2 Generic Wheel Mouse" (type: MOUSE, id 10)
    [ 14.994] (II) evdev: ImPS/2 Generic Wheel Mouse: initialized for relative axes.
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) keeping acceleration scheme 1
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration profile 0
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration factor: 2.000
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration threshold: 4
    [ 14.994] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/mouse0)
    [ 14.994] (II) No input driver specified, ignoring this device.
    [ 14.994] (II) This device may have been added with another device file.
    [ 14.994] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 14.994] (II) No input driver specified, ignoring this device.
    [ 14.994] (II) This device may have been added with another device file.
    [ 23.841] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 23.841] (II) intel(0): Using EDID range info for horizontal sync
    [ 23.841] (II) intel(0): Using EDID range info for vertical refresh
    [ 23.841] (II) intel(0): Printing DDC gathered Modelines:
    [ 23.841] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 23.841] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 23.842] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 23.842] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 23.842] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 23.842] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 23.884] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
    [ 24.108] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 24.108] (II) intel(0): Using hsync ranges from config file
    [ 24.108] (II) intel(0): Using vrefresh ranges from config file
    [ 24.108] (II) intel(0): Printing DDC gathered Modelines:
    [ 24.108] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 24.108] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 24.108] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 24.108] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 24.108] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 24.108] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 33.191] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 33.191] (II) intel(0): Using hsync ranges from config file
    [ 33.191] (II) intel(0): Using vrefresh ranges from config file
    [ 33.191] (II) intel(0): Printing DDC gathered Modelines:
    [ 33.191] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 33.191] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 33.191] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 33.191] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 33.191] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 33.191] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 33.191] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 33.191] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 33.191] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 33.191] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 33.192] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 33.192] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 33.192] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 33.192] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 33.192] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 33.192] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 33.192] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 40.998] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 40.998] (II) intel(0): Using hsync ranges from config file
    [ 40.998] (II) intel(0): Using vrefresh ranges from config file
    [ 40.998] (II) intel(0): Printing DDC gathered Modelines:
    [ 40.998] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 40.998] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 40.998] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 40.998] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 40.998] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 40.998] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 936.094] (II) evdev: ImPS/2 Generic Wheel Mouse: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: AT Translated Set 2 keyboard: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: UVC Camera (046d:0825): Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: Power Button: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: Power Button: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.194] Server terminated successfully (0). Closing log file.
    kde log
    Note that your system uses syslog. All of kdm's internally generated messages
    (i.e., not from libraries and external programs/scripts it uses) go to the
    daemon.* syslog facility; check your syslog configuration to find out to which
    file(s) it is logged. PAM logs messages related to authentication to authpriv.*.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(7126) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(7120)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(7120)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    klauncher(7543) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(7537)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(7537)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    kdmgreet: Fatal IO error: client killed
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(326) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(285)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(285)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(341) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(294)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(294)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(273) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(264)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(264)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    klauncher(857) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(847)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(847)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    klauncher(1223) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(1215)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(1215)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(269) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(263)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(263)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(706) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(700)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(700)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(2630) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(2624)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(2624)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(3118) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(3112)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(3112)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(4638) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(4632)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(4632)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(5014) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(5008)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(5008)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extensio

  • Dual monitor setup - need laptop on the left

    Hi All
    I'm running a dual monitor setup - specifically a HP G72 laptop and a widescreen monitor. I use the monitor as the default and sometimes I want to use the Laptop as a secondary screen for watching TV etc. My desktop is Enlightenment, I just changed to it from Gnome. My issue is that I want the laptop to be on the left of the monitor - that's how it is physically positioned - but when I switch the Laptop screen on all my applications shift over to the laptop screen. I've written 2 scripts, attached to hotkeys, one to turn the laptop off and the other to turn the laptop on. The script to turn the laptop on is as follows:
    xrandr --output LVDS1 --mode 1600x900 --pos 1600x0 --rotate normal
    --output VGA1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --left-of LVDS1
    This works fine, applications stay where they should be, except that the physical position is incorrect; VGA1 should be to the right of LVDS1 like this:
    xrandr --output LVDS1 --mode 1600x900 --pos 1600x0 --rotate normal
    --output VGA1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --right-of LVDS1
    However, when I use the second script all of the applications shift to the laptop but at least the physical position is correct. The issue appears to be something to do with laptops, almost as though when it's a laptop the default monitor is forced to be on the left. Has anybody got any suggestions how to get around this issue?
    Thanks
    Richard

    This is due to your window manager treating the two monitors as a larger 'desktop' area - that combined with your specification of the pos=0x0 you are telling it to do this.
    If you have only the VGA output on, the top left corner of the VGA monitor is 0x0.  If you open a window, and it is placed 10 pixels in and down from the top left, it is at coordinates 10x10 in the x session.  Then you turn on the laptop monitor and specify that the top left corner of the laptop monitor should now bo considered 0x0 - but nothing is done to move the windows, so the window with coordinates 10x10 is now near the top left of the laptop monitor.
    I see 3 possible ways of acheiving what you want:
    1) swap the "pos" parameters in your xrandr commands so that the monitor on the left is always at 0x0 and the one on the right is always at 1920x0 (or whatever).  This will leave a large area of available X desktop that is not visible - I don't know how your window manager will treat this.  It might try to map windows on the laptop screen space even though that screen is not on.  I know openbox is easy to configure where it tries to place windows.
    2) Keep the VGA monitor always at 0x0, but place the laptop monitor at a negative offset when you want it on.  I don't actually know if X allows negative coordinates like that, but it's worth a shot.
    3) Configure your window manager, or use a different window manager, so that it is aware of the two screens and treats them reasonably (e.g. moves windows when the desktop area is changed).
    Last edited by Trilby (2014-07-12 12:15:42)

  • My MBPro Screen Has White Line Running Left To Right & Up & Down

    Early 2011 MacBook Pro Has Line Running Across Screen & Up & Down - Help Or Advise Please??

    Hello Folks, I Need Some Help & Advise Please?? My MacBook Pro ( Early 2011 ) Model, Purchased June 17, 2011 (NEW). Purchased Extended Apple Care Protection Plan. The Screen Has A White Line Running Left To Right Or (Vise Versa) & A White Line Up & Down. Very Noticeable @ Start-Up And Visable At All Times When Screen Is On. The Unit Has Never Been Dropped Or Mishandled! The Laptop Sits On A Logitech Stand Along Side My Recliner Or On My Lap On The Logitech Stand. Only Moved Back & Forth By Myself! Noone Else Has Ever Used The MacBook Pro. Would Anyone Please Respond, If They Have Had This Problem Or Knows If There Is A Setting Or Anything I Can Do To Remedy This?? Your Help Is Greatly Appreciated!!! Jan

  • I have 12 core with Quatro 4000 and 5770, I want to use dual monitor setup, monitors are NEC with Spectraview-II.  How do I connect?  4000 only has 1 Display Port and 1 DVI.  5770 has 2 of each, if I use both 5770 Display Ports, does the 4000 contribute?

    I just bought a 12 core with Quatro 4000 and 5770, I want to use dual monitor setup, monitors are NEC with Spectraview-II.  How do I connect?  4000 only has 1 Display Port and 1 DVI.  5770 has 2 of each, if I use both 5770 Display Ports, does the 4000 contribute any work at all?  I read where on a PC they would work together, but on a MAC they do not.
    I read that Display Port has higher band width than DVI, NEC monitors for best performance they recommend using DIsplay Port.
    When I was setting this up I looked at a Nvidia Quadro 4000, unfortunately it was for PC, it had 2 Display Ports, in the Mac version they reduce it to one.  I did not think there could be a difference.
    Mainly want to use it for CS6 and LR4.
    How to proceed??? 
    I do not want to use the Quadro 4000 for both, that would not optimize both monitors, one DP and 1 DVI.  Using just the 5770 would work but I do not think the 4000 would be doing anything, and the 5770 has been replaced by the 5870.more bandwidth.
    Any ideas, I am a Mac newbie, have not ever tried a Mac Pro, just bought off ebay and now I have these problems.
    As a last resort I could sell both and get a 5870.  That would work, I'm sure of that, it's just that I wanted the better graphics card.
    Thanks,
    Bill

    The Hatter,
    I am a novice at Mac so I read all I can.  From what I understand the NEC monitors I bought require Display Port for their maximum performance.  The GTX 680 only has DVI outputs.  Difference from what I understand is larger bandwidth with the DP.
    You said I have the 4000 for CUDA.  I am not all that familiar with CUDA and when I do read about it I do not understand it. 
    A concern I have is, that if I connect the 2 high end NEC monitors via the 5770, using it's 2 Display Ports I would have nothing connected to the 4000.  Is the 4000 doing anything with nothing connected?  I read where in a PC system the 2 cards would interact but in a Mac system they do not.
    Bottom line, as I see it, the 4000 will not be useful at all to me, since I want a dual monitor set-up.
    So far the 5870 seems the best choice, higher band width than the 5770, and it has 2 Display Ports to optimize the NEC monitors.
    I'm not sure how fine I am splitting hairs, nor do I know how important those hairs are.  I am just trying to set up a really fast reliable system that will mainly be used for CS6 and LR4.  Those NEC monitors are supposed to be top notch.

  • How do I avoid errors on a Multi - monitor setup?

    Hi.
    I want to use Photoshop CS6 on a Multi - monitor setup, using iGPU multi-monitor + GPU system for 4 monitors.
    Preiously, I used Photoshop on a Multi - monitor setup without useing iGPU multi-monitor.
    And, Photoshop worked well.
    However, when I wanted to use 1 more monitor, my GPU supports only 3 monitors.
    Then, I enabled iGPU multi-monitor function. It supports 2 more monitors.
    At first, It worked. But, after I use "Free transform", "Transform"  or something like these tools, Photoshop hang up!
    I couldn't figure out the reason why these errors happened.
    I need ways to avoid these errors.
    Thanks.

    Thanks for viewing this discussion.
    Finally, I brok through this problem.
    I show you how to do, in case of when you face to this problem.
    The way to solve this problem is, simple, "buy a new GPU."
    But, there is 1 important point, you should buy a same bland's GPU.
    In my case, I have SAPPHIRE'S RADEON HD5670, and I bought SAPPHIRE'S RADEON HD 6450.
    I think that Photoshop GPUsniffer was confused about GPU driver.
    Because there were 2 drivers -- Radeon and Intel Graphics -- exist.
    That's why Photoshop hang up.
    For your reference,
    Best regards.

  • Multiple chrome windows on a multiple monitor, multi-desktop setup?

    Dear all,
    I'm having this huge headache because I have a dual monitor setup (imac 27" + second 24" monitor) and I have configured 6 different desktops in it (mountain lion here) where each desktop dual monitor scene has a chrome window (with several tabs each) on each monitor. I do this because i work 90% on SaaS's and as such I need this multi-desktop setup with chrome spread all over it.
    Problem: Everytime i reboot the system, all those crhome windows get back to desktop 1 (on both monitors) and I have to painstakingly put each chrome window one by one back into each desktop again. Its really a PITA.
    Solution: Anyone can tell me a workaround for this or if I am missing some OSX or chorme trick or tweak that will make the system "remember" where each chrome windows was in each desktop + monitor?
    Thanks in advance!
    //Ricardo

    Peggy,
    We have been running 3 separate Forte environments on one server (dev,
    test, prod) for over a year now. The environments have been at
    different Forte release levels at various times. Darrell is right on
    target with the UNIX links and separate fortedef.sh files for each
    environment. The links will help reduce disk space. Follow his
    instructions and you should be good to go. We have each Forte
    environment point to its own database instance also. You can set the
    environment variables in each fortedef.sh file to do this. If you keep
    multiple versions of Forte on a windows client machine, you will have to
    switch the Forte.ini file before starting Forte.
    As for security and auditing, I not sure what you are looking for here.
    Our application has security and auditing but that it.
    Keep in mind, that each Forte environment will be competiting for system
    resources on the same server. When we have 3 environments running, we
    notice a performance hit. Try to use as few resources as you can. For
    example, our test and production environments do not require a
    repository server, since we test deployed. So do not start these
    processes.
    Good luck.
    Robert Crisafulli
    AMISYS
    301-838-7540
    Long live Forte...

  • When installing Adobe Photoshop CS3 on Windows Vista I get this error "Setup has encountered an erro

    When installing Adobe Photoshop CS3 on Windows Vista I get this error "Setup has encountered an error and cannot continue. Contact Adobe Customer Support for assistance. Internal Error 2739" I have used the cleanup script included in Adobe Photoshop CS3 installer, and have removed all traces of Adobe apps including the beta versions and Acrobat 8 pro, and I still get the same error, how can I install this application? is there any way or do I have to reformat and reinstall windows?

    Hello everyone,
    I was having the same issue:
    "Setup Error. Setup has encountered an error and cannot continue. Contact Adobe Customer Support for assistance. Quit."
    If you receive this error also, press Quit and follow these steps:
    1. Start
    2. Control Panel
    3. Administrative tools (in classical view)
    4. Event Viewer
    5. Application
    You will see something like this:
    Double-Click for error (emphasized by red color). I have an error like this:
    "Error 1327.Invalid Drive: E:\" if you have the same or e.g. Drive F:\ ir whatever letter, you should solve this problem extremely easy - just insert USB-flash into computer (it will launch as E\ or whatever disk) and than run installation again. It will work than.
    Setup doesnt start if disk is offline.

  • Mouse pointer is unchangeable at 100% scaling in multi monitor setup with different resolutions

    Hi there, I have been asked by one of the moderators of the Windows 8.1 forums to post this topic here.  You can see the thread relating to this post here
    http://answers.microsoft.com/en-us/windows/forum/windows8_1-tms/cant-change-the-cursor-pointer/ae8ad8a0-3ded-4810-a3be-794f6c4830a4?msgId=2bd7082f-f5d1-4b01-8c70-e0d2a754d66f&page=1<o:p></o:p>
    The problem:  The mouse pointer becomes unchangeable in size, type, trails etc when 100% scaling is used.  As in it reverts to the standard small white non-inverted, no trails,
    no shadow 'pointer', no matter what options you select in the 'Mouse' control panel settings.<o:p></o:p>
    This appears to be a scaling problem with the Windows 8/8.1 display, not an actual mouse problem.  Judging by my own and other peoples experience it seems to happen mainly with multi
    monitor setups where different screen resolutions are used.  The issue occurs typically when 100% scaling for all monitors is used or this option is un-ticked and the 'change the size of all items' is on smallest (equivalent to 100%).  <o:p></o:p>
    If the scaling is set to 150% or greater the issue disappears and the mouse pointer becomes fully functional.  Also bizarrely when the scaling is set to 100% if the screen is recorded
    using a screen capture program, the recording of the screen shows the mouse pointer selected in the mouse options and not the default small white cursor that is present when recording it.  Here is a link to a video where I explain and show the problem
    happening on my system.  http://youtu.be/xs2cxoeaq-A<o:p></o:p>
    I have every update installed without exception, latest drivers etc.  I use a 55" 4k screen with 2x1080p monitors in portrait on either side.  All are connected through 1 Nvidia
    GTX 780 6GB graphics card<o:p></o:p>
    Hope you can help us<o:p></o:p>
    thanks<o:p></o:p>
    Jon M<o:p></o:p>

    Hi Jon,
    I'm looking into this issue but it will take me some time to provide a reply. 
    In the meantime I noticed that you have 3 monitors with 1x 55' and 2x27' - please have a try to only connect 1x27' monitor and see if issue persists.
    Also please try to change the screen resolution to a lower size and see if issue persists. 
    Both suggestions are not solution, I just would like to know if it is related to multiple monitor or screen resolution. 
    If you have any feedback on our support, please send to [email protected]

  • IMac 17" has vertical lines of multi colors

    Just bought a iMac 17" and it has vertical lines of multi colors. What are the causes, how can I troubleshoot the source and what is the most cost effective way to fix?

    Since the last 17" iMac was discontinued in 2007, it's unlikely that it's still under warranty, unless you managed to get Applecare with it.
    I had the same problem. The local Mac repair place, Dino computers in Pasadena, said that what it needs is a replacement display, but that alone costs $500, plus installation, so it isn't really worth it to fix.
    But I found a website call realmacmods.com, which offers a kit just for this purpose. Not for the layperson however. You can get a kit for about $50 and supply your own 17inch display, or you can buy a display plus adapter board for $150. I talked to Dino and they said they could install it for me for about $120. I decided to get some Mac tools and try it myself. The vendor recommends you have some laptop repair experience, which I don't have, but I have opened up desktop computers before, and that helped. Anyway, it worked. And, you get a higher resolution display: 1900 x 1200, formerly 1440 x 900. It looks great. But again, not for the layperson.

  • Accessibility zoom unusable on multi-monitor setup

    The accessibility zoom feature (ctrl-scoll when enabled) that always worked so well and fluidily in previous versions of OSX is now broken in Yosemite.
    It works fine on my macbook pro retina's main display when there are no monitor connected, but on my usual dual external monitor setup the frame rate is so slow it makes is useless.
    Does anyone have the same issue?

    I just found a great workaround for the zoom and it works better than before.
    The zoom defaults to fullscreen zoom and when you have multiple monitors it zooms all of them. Normally I don't need to zoom all just the one monitor that I'm working on.
    Go to  "system preferences " ,"accessibility ", set zoom style to "picture in picture" and then click   "more options"  and then click "adjust size and location"  then you can set the zoom window to the size of a monitor. then when you zoom only the monitor you are on gets zoomed and is fast.
    Works for me. Hopefully helps others as well.

  • Windows 10 hiding taskbar in multi-monitors setup bug.

    This bug persists since windows 8.1 and is already discussed
    here, but it wasn't fixed in approx. half a year :( So, I'm gonna give it a try here.
    Here's the screenshot of it in Windows 10.
    Well, the bug is with incorrectly disappearing taskbar - taskbar "hides" not in the bottom of the screen, but "taskbar height pixels" higher (see the images in onedrive folder below). It hides in such a way only when you go to start screen
    with visible taskbar, wait until it disappears and return to desktop in any way (by pressing the win key, by selecting desktop on startscreen or by clicking the windows logo in the lower left corner);  this bug only appears with two monitors setup and
    heavily depends on monitors position - the secondary monitor bottom should be below primary monitor bottom (I mean not physical location, of course, but monitors' relative location in "Screen resolution" menu). The bug didn't appear before Update
    1; I can't confirm whether it is reproduceable only on my PC at the moment.
    I have reproduced the bug on windows 8.1 U1 across several computers with 100% success rate: two macbooks pro retina, lenovo laptop, two desktops (on one of them I reproduced the bug via teamviewer). I've reproduced it today in VMWare with windows 10 Technical
    Preview.
    This bug is really annoying - when it happens, you need "to cast some magic" - move the mouse to the bottom of the screen, activate/deactivate several applications, etc. in order for taskbar to reappear properly, let alone the fact that it looks
    unaesthetic.
    Skydrive folder with bug screenshot
    Screen recording of the bug
    Step-by-step guide with screenshots

    Yeah, I already did it. I just wanted to open it here, because I've been trying to contact MS about this bug for almost half a year with no success, so I'm just trying to bring their attention to this thing in all ways possible. I could reproduce this bug
    on all the systems I've tried so far, and I've managed to reproduce it even on VMWare in newly-installed windows 10 TP in a single try.
    @rgggg
    I can't understand what do you mean by weakness in graphics. It's a 100% functionality bug. Also, of course, I have nothing to do except reporting some non-existent bugs, making fake screenshots etc. I can't understand what do you mean about "intermediate
    servers", and it's almost impossible to change every Windows iso distributive I've downloaded in such a way that this bug will appear there :D
    C:\Users\Sfairat>fciv -both D:\Downloads\WindowsTechnicalPreview-x64-EN-US.iso
    // File Checksum Integrity Verifier version 2.05.
    MD5 SHA-1
    9005dce26734bcde7f912c2c51ab1127 eb75a3d3c0f621f175b75dc65db036d0e00eac43 d:\dow
    nloads\windowstechnicalpreview-x64-en-us.iso

  • [AwesomeWM] Applications locked to one screen in a dual monitor setup

    Perhaps the title should be "Multiple Screens with multiple video cards." I imagine  my confusion here is the reason I am unable to move clients from one screen to the other in awesome. Though the cursor moves fluidly between Screen1 and 2,  MOD4+drag traps the cursor and the client on the current screen. MOD4+o brings the cursor to the upper left corner of the current screen. Openbox and fluxbox are similarly limited.
    With my Xorg.conf I have $DISPLAY as :0.0 or :0.1 depending on which screen the terminal is open.
    The closest I've come to a solution is xpra from the parti-all aur package. But, I haven't found a way to make it useful. I'm hoping there is an alternative configuration. Maybe something like xinerama or Zaphod?
    I'd like to use xrandr but it seems thats a no go for multiple boards as of the the previous version. I cannot find documentation for 1.3.
    http://wiki.debian.org/XStrikeForce/HowToRandR12 wrote:VI.5. Multi-board support broken - RandR 1.2 does not support multiple boards yet (it's planned for RandR 1.3). It means that any RandR 1.2 aware driver will crash the server if you have 2 boards. Even one board with a RandR 1.2 driver and another board with a classic driver does not work. It just crashes the X server.
    Any ideas?
    > grep -v "^\s*#" /etc/X11/xorg.conf|grep -v ^$ |xclip wrote:Section "ServerLayout"
        Identifier     "X.org Configured"
        Screen      0  "Screen0" 0 0
        Screen      1  "Screen1" RightOf "Screen0"
        InputDevice    "Mouse0" "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
        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"
    EndSection
    Section "Module"
        Load  "glx"
        Load  "dri2"
        Load  "extmod"
        Load  "dbe"
        Load  "dri"
        Load  "record"
    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 "Monitor"
        Identifier   "Monitor1"
        VendorName   "Monitor Vendor"
        ModelName    "Monitor Model"
    EndSection
    Section "Device"
        Identifier  "Card0"
        Driver      "nv"
        VendorName  "nVidia Corporation"
        BoardName   "NV25 [GeForce4 Ti 4200]"
        BusID       "PCI:3:0:0"
    EndSection
    Section "Device"
        Identifier  "Card1"
        Driver      "radeon"
        VendorName  "ATI Technologies Inc"
        BoardName   "Radeon RV100 QY [Radeon 7000/VE]"
        BusID       "PCI:1:7: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
    Section "Screen"
        Identifier "Screen1"
        Device     "Card1"
        Monitor    "Monitor1"
        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

    Err. My confusion is indeed the culprit. For anyone who might find themselves in a similar situation the nomenclature is as follows.
    "Zaphod mode" on wikipedia is listed as a multi-seat configuration, however, I think it more often describes the set up in my posted xorg.conf. That is, the server has two independent screens associated with their respective device. Titling window managers seem to present multiple screens a la Zaphod. At least in awesome, each screen has its own set of tags.  Xinerama is a soon to be deprecated extension merging multiple physical displays into a singular virtual one. It will be replaced with RandR. But, as of the current version of RandR, multi-board setups are not supported.
    ATI and nVidia have proprietary implementations for multi-head configurations (Big Desktop and Twinview respectively). I assumed both cards would have to be same brand and either ATI or nv. So, I didn't look into this.
    By the nature of Zaphod mode, applications exist only on one screen. They cannot easily be moved. Because the Xinerama extension implements one large virtual display, X clients can be displayed anywhere. This is apparently at the cost of direct rendering on both screens. Xinerama is also limited in that all screens have to have the same depth.
    Having the Zaphod mode xorg config, enabling Xinerama just requires one line in the ServerLayout section:
    Section "ServerLayout"
    Option "Xinerama" "on"
    However, if the resolution differs on the screens, screens with lower resolutions will have "dead space" where the rectangle of the virtual resolution is not displayed by the physical resolution of a screen.  Moving the cursor into this area will pan the screen to show the previously hidden area and hiding what was previously visible. This means an application fullscreened on the screen with the lower resolution will never be completely visible.
    To enforce physical resolutions in the virtual screen also only requires one line. In the display subsection of the lower resolution screen section, setting the virtual display to the same as the mode will remove the dead area.
    Section "Screen"
    Identifier "Screen1"
    SubSection "Display"
    Modes "1280x1024"
    Virtual 1280 1024
    EndSubSection
    Please reply if I've gotten anything wrong!
    Last edited by _will (2009-10-07 22:08:19)

  • Setup has stopped working

    I recently upgraded to Windows 7 and had not problems with Photoshop after doing so.  Last week I installed a new monitor and discovered the
    tools were so small I had a hard time seeing them.  I also noticed the cursor had 3 little things on it.  I decided to uninstall and reinstall Photoshop CS4 Extended.  When doing so, I get a message, Setup Has Stopped Working.  I am installing from the DVD and when that didn't work I downloaded from the Adobe site.  Still have the same problem.  I have even tried installing as administrator.
    Can someone please help..
    I have been on hold with Adobe for almost an hour trying to get help.
    Thank you in advance
    Judy

    If you have adobe reader installed remove it. For some reason it sometimes does not play well while PS CS4 is installing.
    Look in Task manager and if you have other adobe products installed make sure they are not running.
    Look in msconfig and turn off any items that do not need to be running during computer start up.
    Run this CS4 cleaner utility. you will have a choice of level 1 or 2. Type in 3 and run it.
    http://www.adobe.com/support/contact/cs4clean.html
    Run the windows installer clean up
    http://support.microsoft.com/kb/290301
    Run defrag before and after install.
    Turn off windwos defender, any anti-virus running and ensure your connected to the internet before install starts.
    When you put the disk in the drive and it wants to run, don't run it. Close out and go to computer and right click on the DVD drive and explore. There is a CS4 folder so open that and find the .exe folder. Right click on that folder and chose run as admin.
    The set up will start and will take a few to run its course. During the install the bar will look like it is hanging around 90 percent. This is normal so let it finish. May hang for 5 to 10 mins.
    After install is finished remove disk and reboot.
    Now the first time you run PS CS4 you need to run as Admin. Right click on the icon in the start area. Choose properties, Compatibility and check run as Admin and close out. Then click on PS to start and then update.

  • [Solved]Dual Monitor Setup

    So, I inherited a new monitor from my friend just a couple days ago and had a go at setting it up. Here's my current setup, to illustrate:
    -- MOD EDIT -- Please follow image posting rules
    The one on the right is mirroring the left at the moment, which happened via default when I booted up. I have the monitor to the left plugged via a dvi cable, and the one to the right that is rotated (for the purpose of better viewing webpages) with plain old vga. Both are running off my only graphics card, a Radeon X300:
    $ lspci | grep VGA
    01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]
    Here is the compatible resolutions and refresh rates and such for each:
    $ xrandr
    Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
    VGA-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
    1280x1024 60.0*+ 75.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 450mm x 280mm
    1680x1050 60.0 +
    1280x1024 75.0 60.0*
    1440x900 75.0 59.9
    1152x864 75.0 70.0 60.0
    1024x768 75.1 70.1 60.0
    832x624 74.6
    800x600 72.2 75.0 60.3 56.2
    640x480 72.8 75.0 66.7 60.0
    720x400 70.1
    S-video disconnected (normal left inverted right x axis y axis)
    So, this information aside, I went and tried to add my second screen and make everything happy, I used the dual screen section in the X.Org Wiki page, which I believe was for the nVidia users, but I couldn't find any direction otherwise, so I figured with a few changes it could work with my radeon just fine. I am on xorg-server 1.9.4.901-1 with openbox as my window manager, no complete DE.
    This is my current /etc/X11/xorg.conf.d/10-monitor.conf written for two monitors, which at the moment does not work, saying no screens found when I run startx:
    Section "ServerLayout"
    Identifier "DualScreen"
    Screen 0 "Screen0"
    Scren 1 "Screen1" RightOf "Screen0" #Screen1 is to the right of Screen0
    Option "Xinerama" "1" #To move windows between screens, set to 1
    EndScetion
    Section "Monitor"
    Identifier "Monitor0"
    Option "Enable" "true"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    Option "Enable" "true"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "radeon"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "radeon"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "0" #Set to 1 to make both monitors act as one big screen, with no distinction between the two
    SubSection "Display"
    Depth 24
    Modes "1680x1050_60.00"
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor" "Monitor1"
    DefaultDepth 24
    Option "TwinView" "0"
    SubSection "Display"
    Depth 24
    Modes 1280x1024_75.00
    EndSubSection
    EndSection
    And here is the same file, in a working configuration:
    Section "Monitor"
    Identifier "Monitor0"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "radeon" #Driver used for this monitor
    EndSection
    Section "Screen"
    Identifier "Screen0" #Collapse Monitor and Device section to Screen section
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24 #Choose the Depth (16 || 24) (24 for true colour)
    Subsection "Display"
    Depth 24
    Modes "1680x1050_75.00" #Choose the resolution
    EndSubSection
    EndSection
    This leaves me with 3 questions I cannot seem to figure out:
    1) What did I do wrong with the non-working xorg config file, giving the error "no screens found"?
    2) Another extra twist of difficulty comes from the rotated monitor on the right.  How should I adopt for that, with resolutions and such?
    3) Xinerama/Twinview  - I am confused which one of these I should choose, what they offer over the other, or should I just not bother at all?
    I would like, in a "perfectly good configuration", windows to be able to move from each monitor to the other, the monitors to be two distinct monitors (ie. they don't mirror each other), a maximized window to only fill up just the one monitor (and not both), and finally, fullscreen programs (like games and such) only fullscreen to the monitor they are on. Is such a configuration possible with all of these parameters?
    -Scott
    Last edited by Inxsible (2011-06-05 18:33:38)

    BurntSushi wrote:
    Your desired configuration is quite common, and indeed, is the default setup provided by Openbox---once the monitors are properly configured, of course :-)
    Anywho, modifying xorg.conf files for something like this is a thing of the past, man. (Incidentally, you have made the lethal mistake of assuming an nvidia config will work with an ATI card. For example, "TwinView" is only available when you are using the nvidia proprietary driver.)
    Judging by your use of "radeon" as your video driver, it looks like you're using xf86-video-ati. Therefore, congratulations, xrandr will rescue you :-) (This should also be the case if you you're using the Catalyst driver.)
    thinkwiki should be enough to get your feet wet. Note: This guide is a bit dated, but 90% of it is still relevant and useful. For example, it claims that you need to modify your xorg.conf to add a Virtual screen size---this is only true if kernel modesetting is disabled. If it's enabled (and it should be if you're using xf86-video-ati), then you're good to go. If you're using Catalyst, you will have had to disable KMS. So you'd either have to add a Virtual screen to use xrandr, or configure your monitor setup with amdcccle.
    Finally, you asked about rotation. I don't think this is anything that `man xrandr` can't answer, and you should be okay as far as support goes---rotation was added in RandR 1.2, which any civilized video driver should support. (Except nvidia blob.)
    Anywho, feel free to come back with more questions if you have any!
    (For terminology sake, this means you will be using neither Xinerama nor TwinView to configure your multi-monitors. You will be using RandR if you use xrandr. Interestingly, your screen setup will still be reported to Openbox via the Xinerama extension. You may be interested in a utility like `lxrandr` if the command line frightens you.)
    Xrandr does the job elegantly, thanks! It's a simple matter of putting the commands I needed in openbox's autostart.sh. Thanks for pointing me in the right direction.
    #xrandr --output DVI-0 1680x1050 --output VGA-0 1280x1024 --right-of DVI-0
    # xrandr --output VGA-0 --rotate left
    Scott

Maybe you are looking for

  • How to upload local photos to icloud photo library

    with the new icloud photo library(beta) that was introduced in iOS 8.1, I tried to turn it on to upload my photos on my iphone 6 to icloud drive, but it warned me those photos I uploaded from my mac to my iphone will be removed..... So does it only u

  • Windows 2008 Server boot loop and unable to log on in Safe mode

    The Situation: I used msconfig to reboot Windows 2008 Server r2 into safe mode. On rebooting, boot progresses ok and the log in screen appears very quickly, then disappears and the machine reboots. I've tried typing the password very quickly and whet

  • ORA-22160: element at index name does not exist

    hi i have a procedure which insert values from a VARRAY type in a table. My question is how can i verify the existence of nth element before inserting to avoid ORA-22160: element at index name does not exist Here is my code: CREATE OR REPLACE PACKAGE

  • 9850 White Screen during OS upgrade

    After losing power during a security wipe (long story) i've tried several methods to either reload the OS to my BlackBerry 9850 or just wipe it to start from scratch. In each instance, the device can boot to 3/4 of the white bar and then will go to a

  • Need to reinstall Adobe Audition CS6 that I purchased

    I need to reinstall my Adobe Audition CS6 that I purchased.  How do I do that?