Monitor Setup Help

OK I have a decent budget for a Mac Pro setup and need help with the displays. The system will be used for video and photo editing. I'm torn between 3 23" displays and 2 30" displays. I really like the look and feel of that central display with flanking monitors. One of the things I will be doing is taking simultaneous video from 3 sources and pulling it together into one video. The final product will alternate between all three clips onscreen at once and transitions between the clips. If you had your druthers what would you choose?
Thanks.
PS I'm looking to buy after the next rev of the MP processors and am looking at the NEC line or Cinema Display (if they upgrade with the new MP line as I don't like the refresh rates).

Similar Messages

External Monitor Setup Help

I was wondering if anyone knew a way that I could connect my laptop to another monitor, and then connect the laptop to my Macbook Pro, and use both the laptop's monitor, and the monitor it's connected to, as external monitors. I was also thinking I could possibly throw in my 2nd Gen iPod Touch and my iPad as even more visual space. This would be an amazing setup and a huge accomplishment for me, and I could amaze everyone I know when they come over. Just in case it's useful, the Macbook Pro is a (I think it's refurbished) 2007 version. If anyone needs more info about ANYTHING, I will gladly provide it.

Never mind. I posted this on another website and got a little bit of help from there, but I did most of it on my own. I'm using ScreenRecycler trial version (NEVER BUY IT, THERES NO POINT) to connect to my Macbook Pro to my laptop, iPad, or iPod touch, whichever I choose. I can only do one at a time and I didn't have to spend any money at all! I can also connect my laptop to my monitor or TV and add another screen into the play! The only downside is that the TV stays as Windows while the laptop is connected with my Mac, unless I drag the window to the TV and then the laptop stays as windows. It's almost like having 2 Macs and 1 PC! Thanks to anyone who even considered helping me.
arecusrulz

Multipule Monitor setup Help

I have a hp laptop with windows 7, and i want to set up 2 monitors to it and still have my laptop screen on. I do not know how to set it up and i want to have 3 monitors for gaming. help please.

Dylan, welcome to the forum.
When requesting help you should always include the make/model (i.e. p6-xxxx) of the computer and/or monitor. This information is necessary for us to review the specifications of them.
If you have enough video ports on the laptop, here is how you can connect two monitors to it:
How to Connect Two Monitors to a Laptop
Step 1
Plug in the first monitor into the power outlet. Connect the VGA cable from the monitor to the VGA input on the laptop.
Step 2Power on the VGA monitor. Enter the system configuration preferences. On a PC, enter the system preferences by clicking the Start button, then "Control Panel" and "Display." On a Mac, enter by clicking the apple icon. Once in the display settings screen, click "Detect" to have the laptop find the first external monitor.
Step 3Power off the second monitor. Connect the monitor to the computer through an available HDMI port. Power on the monitor. Enter the display preferences panel and detect the second external monitor.
Step 4Connect the second monitor to a USB slot, if no HDMI slot is available. Repeat the process of entering the display preferences screen to detect the monitor.
Step 5Install an extra monitor PCMCIA (Personal Computer Memory Card International Association) card into a free PCMCIA slot on your computer. Power off the monitor, connect to the card and turn the computer on again. Detect the external monitor through the display program.
Step 6Connect a dual monitor expansion box to a USB port on your laptop. Install any additional software as required by the manufacturer. Connect the two external monitors to the expansion box and turn on the power. Run through the device detection, if needed, to have your laptop locate the external displays.
Please click the "Thumbs Up+ button" if I have helped you and click "Accept as Solution" if your problem is solved.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

Dual monitor setup and intel help

Hello
I am trying to set up and dual monitor setup here, with a monitor and a tv, the monitors resolution is 1680x1050, the tv's resolution is 1360x720, which results in that the desktop will have an resolution on 3040x1050.
When I try to do this with GNOME's xrandr gui, I get this:
required virtual size does not fit available size: requested=(3040, 1050), minimum=(320, 200), maximum=(1920, 1920)
When looking in the motherboards manual, it states that each out of my graphics card can do a resolution of 1980x1080. Is the intel driver missunderstanding something? Since both the dvi and hdmi output only delivers 1360x720 and 1680x1050, 3040x1050 is only an virtual resolution.
Any suggestions?

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "record"
Load "dbe"
Load "extmod"
Load "glx"
Load "dri"
Load "dri2"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "no"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
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 "intel"
VendorName "Intel Corporation"
BoardName "4 Series Chipset Integrated Graphics Controller"
BusID "PCI:0:2:0"
Option "AccelMethod" "exa"
Option "MigrationHeuristic" "greedy"
EndSection
Section "Device"
Identifier "Card1"
Driver "intel"
VendorName "Intel Corporation"
BoardName "4 Series Chipset Integrated Graphics Controller"
BusID "PCI:0:2:1"
Option "AccelMethod" "exa"
Option "MigrationHeuristic" "greedy"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
Option "LeftOf" "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
Uhm do I only need one Screen section?

Dual monitor setup with seperate resolutions

hey guys!
i currentley run thye latest version of archlinux with the cinnamon desktop environment and an nvidia geforce 7300SE graphics card.
im running a dual monitor setup with one 27" 1920x1080 monitor and one 27" 1024X768 monitor
because they have the same physical size they line up perfectley but because the resolution is different programs/mouse cursor movement doesnt, is there any way (without changing the resolutions) to compensate this effect so that in the eyes of linux/cinnamon the monitors line up so that for example dragging a window goes seamlessley between the 2 monitors.
i HAVE found out the panning option in the nvidia x server settings, but that really isnt what i am looking for...
Last edited by RikSolo (2014-08-04 11:25:02)

A magnifier following the window down to the pixel, zooming to the exact size of 540 pixels the 384 pixels window could create an illusion of just that. It would be highly impractical however, not mention all the hacking time. Even if you would manage to get two screen with different sized icons, so that they match visually, the windows and fonts resizing on the fly, wmctrl might help with windows alone, no their themes (buttons, borders thickness etc.), you would still be left with a visually differently sized mouse cursor. Technically such a feat should be possible, but who is going to code it? Nvidia?
Last edited by emeres (2014-08-04 18:48:59)

Regading PI monitoring setup in solution manager

Hi Folks,
I am new to solution manager and I need to setup PI monitoring setup in solution manager...
I read some blogs and docs but not getting clear idea. all the remaning setup has been done in solution manager and only need to configure the technical monitoring thing in solution manager...
Please help me on this step by step guide...
Thanks,
Sreenivas

Hi Hareesh,
Thanks for your reply.
In Solution manager if I opend the technical monitoring I am getting below screen..
Can you please tell me what are the steps I need to do... For first i want to test this with one file communication channel later I will do remaining channels.
I am new to this setup.. help me on this..
Thanks,
Sreenivas

System Monitoring Setup in Solution Manager

Hello Experts,
We are going to implement and configure Solution Manager - System monitoring setup for pre testing purpose
Currenly we have installed below SAP Systems
1.Solution Manager Server
2.ECC server (Without Ides) - Abap
3.CRM Server (Without Ides) -Abap + Java
We need to setup below tasks in Solution Manager
1.Early watch alert
2.System Monitoring
3.Central System Administration
4.Business Process Monitoring
5.Service Level reporting
1.Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
Could you please someone give input reg this.
Thanks
Thirumal
Edited by: Thiru Thirumal on Aug 6, 2008 4:56 AM
Edited by: Thiru Thirumal on Aug 6, 2008 4:57 AM

Hi,
Q. Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
A. Yes.
Check with links for
1.Early watch alert
This process helps you to identify potential problems early, avoid bottlenecks, and monitor the performance of your ABAP and JAVA systems and your most important business processes, regularly, automatically and effectively. The data collection infrastructure comprises the ABAP Service Data Control Center and the JAVA function module Data Provider. The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.
To be able to use it, you have:
maintained the non-ABAP systems correctly in the system landscape maintenance (transaction SMSY)
RFC u2013 Connections between: and an RFC u2013 Connections established.
your satellite systems and the SAP Solution Manager system
SAP Solution Manager and the SAP Service Marketplace
Solution Manager system and Solution Manager Diagnostics
Cf: Solution Manager IMG (transaction SPRO).
checked the availability of the tools required for the SAP Service sessions (add-on ST-A/PI), with the report RTCCTOOL.
activated Alert Monitoring and set-up the Automatic Session Manager (ASM) in the Service Data Control Center (SDCCN) of your satellite systems, for all SAP satellite systems and the central SAP Solution Manager of your solution
set-up your systems in a solution landscape in the SAP Solution Manager
configured Solution Manager Diagnostics
2.System Monitoring
The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.
The graphical display in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.
The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwriting the values in the local CCMS.
3.Central System Administration
You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, u201EBPMu201C of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.
The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:
● The system collects performance (dialog transactions), posting cancellations (V1 and V2) and u201EOther CCMSu201C and interface data, in the local CCMS of the satellite systems.
● The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.
The SAP Solution Manager system copies the data from the local CCMS.
The graphical display in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.
The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.
4.Business Process Monitoring
The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.
You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system
5.Service Level reporting
http://service.sap.com/solutionmanager for all solman tasks as given below.
http://www.asap.net.cn/homepage_en/Solution%20Manager%20EN.pdf
http://help.sap.com/saphelp_sm32/helpdata/en/1b/f02c41ab78f66fe10000000a1550b0/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/9f/1f46570f8a4a268b3154e0e0f07280/content.htm
Regards,
Srini Nookala

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

MacPro3,1 triple monitor setup

Hi there!
I'm looking to expand my Apple 30" monitor setup with two (very cheap but highly acclaimed) Dell UltraSharp™ U2311H monitors. However, I'm unsure if I do or do not need an additional video card and if so, which one. I have an NVIDIA GeForce 8800 GT with (I think) two DVI-I Dual Link ports. I've read that there are DVI-splitters, but I have been unable to find any conclusive information.
Does anyone know how I can do this?
Friendly greetings, D, Amsterdam.

Hi Grant!
Thanks for your help earlier ;-)
I hope you might be able to shed some light on a little problem I have with my triple monitor setup. I bought the following items:
Two Dell Professional P2411H 61cm (24") LED monitors.
Two MiniDisplayPort to DVI adapters.
I've took your advice on the card and also got one ATI RADEON HD 5770 1GB-ZML card.
The monitors, in combination with the adapters and the card ... it all works, but there's one limitation I believe shouldn't be there.
The problem is this: either the hardware or software is only allowing me to connect two displays in total. If I connect all three displays, only the Dell monitors are able to connect. If I disconnect one Dell monitor, the Apple 30" display goes live. So, whatever in whatever combination or order I try to connect the displays, only two screens are connecting simultaneously.
Do you, or does someone else know how to fix this? Would be great to fix this soon and become the pixonaut of my own digitale cockpit!

HP Pavilion dv7-2250ed and dual monitor setup

Good evening,
Currently I own a HP Pavilion dv7-2250ed notebook using a dual monitor setup (notebook display + extra monitor)
I wondered if it would be possible to hook 2 monitors to this laptop? (notebook display + extra monitor + extra monitor)
If this causes the problem, the notebook display isn't requered.
Also, if not, is there a dockingstation for this brand which supports the above?
Kind Regards,
Cor van Noorloos
Edit: a note to the devs of these forums, using multiple tags is done by comma's, not by spaces. You might wish to rephrase this phrase.

wgarn wrote:
I have attempted to connect one monitor via HDMI and the other one via the VGA interface.
Using Windows 7 OS and "default configurations" (Control Panel\Appearance and Personalization\Display\Screen Resolution) it is possible to use both external monitors as desktop. However the laptop screen will go blank. So at any time it appears to be possible to have an extended desktop with only two screens.
- Does HP have any drivers/solutions that make it possible to extend the desktop from "Mobile PC" display to two additional desktops?
- Has anyone tried third party software (e.g.. UltraMon)?
- Is there a technical restriction (e.g.. Videocard capability)?
- How about using a Linux OS (e.g.. Ubuntu)?
- What external Hardware exists that would enable me to extend my desktop to three or more monitors simultaneously?
Many thanks in advance.
It's the graphics card and the number of physical connections available. You might have 3 connections (notebook display being one) but the graphics card likely does not support more than 2 monitors. Intel graphics only support 2, however you may be able to find some AMD chips that will support more however that would be a major upgrade.
________________________________________________________________________________________________________ I Love Kudos! If you feel my post has helped you please click the White Kudos! Star just below my name
If you feel my answer has fixed your problem please click 'Mark As Solution' and make it easier for others to find help quickly

Preview app opens "split screen" on dual monitor setup

This is a minor issue, I rarely use the utilility "Preview" app. but I'd still like to understand this issue....I use a two monitor setup (MBP & StudioDisplay)..
The following happens if the window was last closed in "expanded" mode (you can see options for Drawer, rotate, etc)
When "Preview" launches and opens a window, it places the top portion of the window on the secondary display and bottom part of the window on the primary display.
This Does Not happen if the window was last closed in "non-exanded" (collasped) mode (sorry, I don't know the proper term).
In other words, in respect to it's position on the screen, when the window opens it always assumes it's in "collasped" mode.
Weird... any comments?

There's something wrong with the way Preview handles dual monitors. In my case if I open a smallish item, for instance a small png, instead of opening in the upper left corner of my main monitor it opens so that about half an inch of the Preview window is sticking over onto the second monitor (which is to the left of my main monitor). I had never "collapsed" the tool bar before, so I just now tried that on a small png, then closed it and re-opened. Sure enough, without the toolbar it opens properly. Display the toolbar, close, reopen, and it sticks onto the second monitor. Weird indeed. Larger size files open normally.
This started with the Tiger version of Preview. If you wish you can send feedback:
http://www.apple.com/macosx/feedback/
Maybe it will help get this odd bug squashed in a future version of Preview.
Francine
Francine
Schwieder

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.

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]

Problem in System Monitoring Setup

Hi
I need to configure System Monitoring Setup in Solution Manager. But I cannot able to open the Page SOLUTION_MANAGER -> Operations -> Solution Monitoring -> System Monitoring/Administration. I am getting the error :Network Access Message: The page cannot be displayed ". We use proxy for Insternet here. Please suggest
Regards
Soumya Dasgupta

Hi ,
Please check the PDF attached below for the Stellite System configuratiom.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0d0de5a-3436-2c10-faa1-b860db5a57b9
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0f35bf3-14a3-2910-abb8-89a7a294cedb
http://help.sap.com/saphelp_nw04/helpdata/en/5a/b27f17edb04a6882c59f6619a267b9/frameset.htm
Thanks Rishi Abrol

PI monitoring setup in Solman 7.1

Hi Experts
I have to setup PI monitoring in solman 7.1 I have followed following document for this:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/408e1501-fb8c-2e10-edba-f51f13cde64e?overridelayout=true&51556787604320
"Setup GuideCentral Monitoring of SAP NetWeaver Process Integration 7.3 with SAP Solution Manager 7.1"
As per this guide following are the prerequisites for this setup:
–Landscape Setup (once/per PI SLD)---Done
–Managed System Configuration (per Technical System)---Done
–System Monitoring Setup (per Technical System)----Done
–PI Monitoring Setup (per PI Domain)--- Not able to see the PI domains in step 4 (define scope)
The solman SLD version is 7.0212.20120528123254.0000
Can you please suggest some solution so that I can get the PI domains listed in PI monitoring
Thanks in advance

Hello Vineet,
Please also see the following Central PI Monitoring Documentation and Help Area Wiki page which includes How to/Installation/Setup and Troubleshooting guides:
PiMon_Home - Technical Operations - SCN Wiki
Regards,
Ruth

Monitor Setup Help

Similar Messages

Maybe you are looking for