Two monitor issues.

Hi yes, when I try and plug my MacBook pro to display a second screen using a thunderbolt to hdmi converter the second monitor has this weird shade of green is there a way to fix that or is my converter broken.

your converter may not be plugged in properly make sure it's pushed in all the way. If that doesn't work check to see if the pins on the inside of the converter are bent/missing. if they are it may be a problem with the converter.

Similar Messages

Two monitor issue

I work with two monitors. All of a sudden the size of the image on the screens has enlarged and when I move my mouse the whole screen moves with it????? The image of the 27" screen is now overlapping on the 20" screen.

On Thu, 27 Jul 2006 23:19:15 +0000 (UTC), "Nikkinames"
<[email protected]> wrote:
>I used to have two monitors and I put dreamweaver on the
right one but now I
>have one monitor hooked up, The problem is that
dreamweaver stayed on the
>second screen thats not there anymore and I cant get it
back to the main (left
>screen) When I maximize it goes to the right.
Windows or Mac? If Windows, right-click on an empty spot on
the task bar
and choose one of the Tile Windows options from the context
menu.
Gary

How to connect two monitors using macbook pro?

Hi,
I have a Macbook Pro through which I want to extend the displays to two individual monitors.
The two monitors should show two different windows which is opened through my macbook.
I have observed that macbook has only one mini display port through which I connect to HDMI or to DVI ports in monitor.
So how do I connect another monitor source to my macbook, which ports can help in this situation?
The monitors I have which can supports HDMI,DVI,VGA and DP ports.
Could anyone help me on this issue.
Thanks.

You can use a USB 2.0/3.0 to HDMI/DVI interface. You might also consder Thundebolt to HDMI/DVI.
The MBP 13" will support three screens (two external) and the MBP 15" will support four screen (three external).

Multi-monitor issue with CS4?

Hi; I'm running a Mac with the following specs:
3 x 30" ACD
MacPro 2,8 Ghz Quad
2x ATI Radon 2600 XT graphics cards (2 screens attached to 1 card; 1 screen to the other card)
I've encountered after the switch from CS3 to CS4 the following issue:
Whenever I try to use the new Bridge Review function using one of the the screens sharing one graphics card I just get a grey screen.
If I move the bridge window to the solely attached screen it works.
Is that an issue of CS4 or is just the throughput of the second graCard providing 2 monitors not sufficient.
Thanks t.

T,
There are known issues with using more than one graphics card which Apple has not truly resolved. You may want to browse some of the threads in the Adobe Photoshop Macintosh forum.
In addition, you should know that Photoshop and Bridge cannot really take advantage of more than one graphic card.
http://forums.adobe.com/message/1540485#1540485
This bit of information in relation to GPU and OpenGL features and
limitations in Photoshop CS4 had totally escaped me until now. Though
it doesn't affect my setup, it might be of interest to others who may
have missed it too.
Excerpt from
http://www.adobe.com/go/kb404898
Q. Does Photoshop take advantage of dual-GPU display cards?
A. Not at this time.
Q. Why can't Photoshop take advantage of more than one display card?
A. When you move an image window between two monitors that are
each on a separate display card, the GPU attached to the second monitor
does not have access to the data necessary to accelerate drawing. The
SLI and Crossfire technologies that use more than one GPU to speed up
full-screen games will not work with Photoshop, because their use is
limited by design to accelerate only full-screen games.

Three Monitor Save, Two Monitor Hang- CS6

I have three monitors running from my Dell M6600 at work. I save a Premiere Project with any panel open on the third monitor. Then take my computer home where I only have two monitors and open the project file, Premiere hangs. It will never launch the application fully. It opens to the point where it would normally load project data, and then hangs.
As a workarround I have begun making sure I save the project with all panels on two screens. However, if I forget then the only solution I have is to go to work to open the project. (Or get a third monitor at home...)
I would love to be able to edit the project XML and remove or reset the panel layout. Anyone else experiencing this issue? or know how to "hack/workaround" the project file?

Jim Simon wrote:
I don't think that's correct. Each project loads with the last saved window arrangement, named or not. So he'll need to rearrange the windows before saving at work (or get that third monitor at home).
I'm just going by the help file:
http://helpx.adobe.com/premiere-pro/using/workspaces.html
"If a project saved with a custom workspace is opened on another system, the application looks for a workspace with a matching name. If it can’t find a match (or the monitor configuration doesn’t match), it uses the current local workspace."
But like I said, I haven't tested it out myself.

Connect two monitors to a Pavilion dv6t-2300 laptop (Windows 7 64)?

What type of connector do I use to use two monitors with my Pavilion DV6t-2300?

Hi,
Read this..
http://www.tech-faq.com/how-to-connect-multiple-monitors-to-your-laptop.html
Dv6-7000 /Full HD/Core i5-3360M/GF 650M/Corsair 8GB/Intel 7260AC/Samsung Pro 256GB
Testing - HP 15-p000
HP Touchpad provided by HP
Currently on Debian Wheeze
*Please, help other users with the same issue by marking your solved topics as "Accept as Solution"*

How can one use Mission Control with two monitors? Please bring Spaces back

How can one use Mission Control with two monitors. With Spaces I could treat each space as a single desktop.
SyBB

I use two monitors at work and have no issue. I have my mail set to use Desktop 1 and iTunes set to the second monitor of Desktop 1. I have browsers set to Desktop 2 and Fusion and RDC set to Desktop 3.
Two things that may help you. In System Preferences > Mission Control, disable the setting "Automatically rearrange spaces...". This screwed with assigning applications to certain spaces. And the other thing is don't use full screen on apps that support it. This just makes your second monitor superfluous.

3d Acceleration on two monitors with nvidia?

Is there any way to get two monitors that are running on the same pc and kernel BOTH be 3d accelerated in X?
Like two instances of X or two instances of the WM...or...something? I have an nvidia card for both of my monitors and would like both accelerated...
Is this possible? Can I use the "nvidia" (as opposed to "nv") driver for both?
I'm unclear on this issue, any help would be appreciated.

I finally had a chance to do some more exploration.
Currently, I've got two fluxboxes running across my monitors (no xinerama right now). The only thing I don't like is that I still can't get the "nvidia" driver to work for both displays.
Strangely enough, when I try to use the "nvidia" module for both, upon "startx" both monitors go black and ctl + alt + backspace won't kill X, I have to hit the reset button.
Here is the log generated after both monitors going blank. Any help would be very appreciated:
<----------I editted a few lines out here and there in the log, due to the forums truncating the message. I editted in particular the long series of line starting with NV or NVIDIA and then a bunch of resolutionm combos. let me know if there is something particular you want me to post. ---------->
(II) LoadModule: "dbe"
(II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a
(II) Module dbe: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a
(II) Module extmod: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.2
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "type1"
(II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a
(II) Module type1: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Type1
(II) Loading font CID
(II) LoadModule: "speedo"
(WW) Warning, couldn't open module speedo
(II) UnloadModule: "speedo"
(EE) Failed to load module "speedo" (module does not exist, 0)
(II) LoadModule: "freetype"
(II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 6.8.1, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font FreeType
(II) LoadModule: "nvidia"
(II) Loading /usr/X11R6/lib/modules/drivers/nvidia_drv.o
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.6106
Module class: XFree86 Video Driver
(II) LoadModule: "nv"
(II) Loading /usr/X11R6/lib/modules/drivers/nv_drv.o
(II) Module nv: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 0.7
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.4
(II) LoadModule: "keyboard"
(II) Loading /usr/X11R6/lib/modules/input/keyboard_drv.o
(II) Module keyboard: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.4
(II) NVIDIA X Driver 1.0-6106 Wed Jun 23 08:14:45 PDT 2004
(II) NVIDIA Unified Driver for all NVIDIA GPUs
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
GeForce4 420 Go 32M, GeForce4 460 Go, GeForce4 440 Go 64M,
GeForce4 410 Go 16M, Quadro4 500 GoGL, Quadro4 550 XGL, Quadro4 NVS,
GeForce4 MX 440 with AGP8X, GeForce4 MX 440SE with AGP8X,
GeForce4 MX 420 with AGP8X, GeForce4 448 Go, GeForce4 488 Go,
Quadro4 580 XGL, Quadro4 280 NVS, Quadro4 380 XGL,
GeForce4 MX Integrated GPU, GeForce3, GeForce3 Ti 200,
GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600, GeForce4 Ti 4400,
0x0252, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
GeForce FX 5600 Ultra, GeForce FX 5600, 0x0313, GeForce FX 5600SE,
0x0316, 0x0317, GeForce FX Go5600, GeForce FX Go5650,
Quadro FX Go700, 0x031D, 0x031E, 0x031F, GeForce FX 5200,
GeForce FX 5200 Ultra, GeForce FX 5200, GeForce FX 5200SE,
GeForce FX Go5200, GeForce FX Go5250, GeForce FX Go5200 32M/64M,
0x0329, Quadro NVS 280 PCI, Quadro FX 500, GeForce FX Go5300,
GeForce FX Go5100, 0x032F, GeForce FX 5900 Ultra, GeForce FX 5900,
GeForce FX 5900XT, GeForce FX 5950 Ultra, 0x0334, Quadro FX 3000,
GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
GeForce FX 5700VE, 0x0345, GeForce FX Go5700, GeForce FX Go5700,
0x0349, 0x034B, Quadro FX Go1000, Quadro FX 1100, 0x034F
(II) Primary Device is: PCI 01:00:0
(WW) NVIDIA: No matching Device section for instance (BusID PCI:2:4:0) found
(--) Chipset NVIDIA GPU found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xfeaffc00 - 0xfeaffcff (0x100) MX[B]
[6] -1 0 0xea7ff000 - 0xea7fffff (0x1000) MX[B]
[7] -1 0 0x40000000 - 0x400003ff (0x400) MX[B]
[8] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[9] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[10] -1 0 0x48000000 - 0x4fffffff (0x8000000) MX[B](B)
[11] -1 0 0xea7fe000 - 0xea7fefff (0x1000) MX[B](B)
[12] -1 0 0xfc9e0000 - 0xfc9fffff (0x20000) MX[B](B)
[13] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B)
[14] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[B](B)
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[17] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[18] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[19] -1 0 0x0000bc00 - 0x0000bc07 (0x8) IX[B]
[20] -1 0 0x0000b800 - 0x0000b81f (0x20) IX[B]
[21] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B]
[22] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[23] -1 0 0x0000e000 - 0x0000e003 (0x4) IX[B]
[24] -1 0 0x0000e400 - 0x0000e407 (0x8) IX[B]
[25] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[B]
[26] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[27] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[28] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[29] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[30] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[31] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B]
(--) Chipset GeForce2 MX/MX 400 found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xfeaffc00 - 0xfeaffcff (0x100) MX[B]
[6] -1 0 0xea7ff000 - 0xea7fffff (0x1000) MX[B]
[7] -1 0 0x40000000 - 0x400003ff (0x400) MX[B]
[8] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[9] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[10] -1 0 0x48000000 - 0x4fffffff (0x8000000) MX[B](B)
[11] -1 0 0xea7fe000 - 0xea7fefff (0x1000) MX[B](B)
[12] -1 0 0xfc9e0000 - 0xfc9fffff (0x20000) MX[B](B)
[13] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B)
[14] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[B](B)
[15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[17] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[18] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[19] -1 0 0x0000bc00 - 0x0000bc07 (0x8) IX[B]
[20] -1 0 0x0000b800 - 0x0000b81f (0x20) IX[B]
[21] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B]
[22] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[23] -1 0 0x0000e000 - 0x0000e003 (0x4) IX[B]
[24] -1 0 0x0000e400 - 0x0000e407 (0x8) IX[B]
[25] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[B]
[26] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[27] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[28] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[29] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[30] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[31] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B]
(WW) ****INVALID MEM ALLOCATION**** b: 0xff000000 e: 0xffffffff correcting
(II) NonSys
[0] -1 0 0xfeaffc00 - 0xfeaffcff (0x100) MX[B]
[1] -1 0 0xea7ff000 - 0xea7fffff (0x1000) MX[B]
[2] -1 0 0x40000000 - 0x400003ff (0x400) MX[B]
[3] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[4] -1 0 0xf0000000 - 0xf0000000 (0x1) MX[B]
[5] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[6] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[7] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[8] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[9] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[10] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[11] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[12] -1 0 0x0000bc00 - 0x0000bc07 (0x8) IX[B]
[13] -1 0 0x0000b800 - 0x0000b81f (0x20) IX[B]
[14] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B]
[15] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[16] -1 0 0x0000e000 - 0x0000e003 (0x4) IX[B]
[17] -1 0 0x0000e400 - 0x0000e407 (0x8) IX[B]
[18] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[B]
[19] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[20] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[21] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[22] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[23] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[24] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[25] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[26] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[27] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[28] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B]
[29] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[30] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(WW) ****INVALID MEM ALLOCATION**** b: 0x48000000 e: 0x4fffffff correcting
<----------EDIT---------->
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Reloading /usr/X11R6/lib/modules/libfb.a
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/X11R6/lib/modules/libxaa.a
(II) Module xaa: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.2.0
ABI class: X.Org Video Driver, version 0.7
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Reloading /usr/X11R6/lib/modules/libramdac.a
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? Yes, I do.
(II) LoadModule: "rac"
(II) Loading /usr/X11R6/lib/modules/librac.a
(II) Module rac: vendor="X.Org Foundation"
compiled for 6.8.1, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) resource ranges after preInit:
[0] 1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B]
[1] 1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B]
[2] 0 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B]
[3] 0 0 0xfb000000 - 0xfbffffff (0x1000000) MX[B]
[4] -1 0 0xe0000000 - 0xe7ffffff (0x8000000) MX[B](B)
[5] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[B](B)
[6] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[7] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[8] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[9] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[10] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[11] -1 0 0xfeaffc00 - 0xfeaffcff (0x100) MX[B]
[12] -1 0 0xea7ff000 - 0xea7fffff (0x1000) MX[B]
[13] -1 0 0x40000000 - 0x400003ff (0x400) MX[B]
[14] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]
[15] -1 0 0xf0000000 - 0xefffffff (0x0) MX[B]O
[16] -1 0 0xea7fe000 - 0xea7fefff (0x1000) MX[B](B)
[17] -1 0 0xfc9e0000 - 0xfc9fffff (0x20000) MX[B](B)
[18] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B)
[19] -1 0 0xfb000000 - 0xfbffffff (0x1000000) MX[B](B)
[20] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[21] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[22] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[23] 1 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
[24] 1 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
[25] 1 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
[26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[27] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[28] -1 0 0x0000b000 - 0x0000b007 (0x8) IX[B]
[29] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[B]
[30] -1 0 0x0000bc00 - 0x0000bc07 (0x8) IX[B]
[31] -1 0 0x0000b800 - 0x0000b81f (0x20) IX[B]
[32] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B]
[33] -1 0 0x0000dc00 - 0x0000dc0f (0x10) IX[B]
[34] -1 0 0x0000e000 - 0x0000e003 (0x4) IX[B]
[35] -1 0 0x0000e400 - 0x0000e407 (0x8) IX[B]
[36] -1 0 0x0000e800 - 0x0000e803 (0x4) IX[B]
[37] -1 0 0x0000ec00 - 0x0000ec07 (0x8) IX[B]
[38] -1 0 0x0000ffa0 - 0x0000ffaf (0x10) IX[B]
[39] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[B]
[40] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[B]
[41] -1 0 0x0000d000 - 0x0000d01f (0x20) IX[B]
[42] -1 0 0x0000cc00 - 0x0000cc1f (0x20) IX[B]
[43] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[44] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
[45] 1 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
[46] 1 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(II) NVIDIA(0): Setting mode "1280x960"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) Loading extension NV-CONTROL
(EE) NVIDIA(0): Failed to load GLX
(==) RandR enabled
(==) NV(1): Write-combining range (0xe0000000,0x4000000)
(II) NV(1): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Scanline Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(==) NV(1): Backing store disabled
(==) NV(1): Silken mouse enabled
(WW) NV(1): Option "RenderAccel" is not used
(==) RandR enabled
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Option "Protocol" "IMPS/2"
(**) Mouse1: Device: "/dev/psaux"
(**) Mouse1: Protocol: "IMPS/2"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons"
(**) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Mouse1: Buttons: 5
(**) Option "CoreKeyboard"
(**) Keyboard1: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard1: Protocol: standard
(**) Option "XkbRules" "xorg"
(**) Keyboard1: XkbRules: "xorg"
(**) Option "XkbModel" "pc101"
(**) Keyboard1: XkbModel: "pc101"
(**) Option "XkbLayout" "us"
(**) Keyboard1: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard1: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(II) Mouse1: ps2EnableDataReporting: succeeded
Could not init font path element /usr/X11R6/lib/X11/fonts/local/, removing from list!
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
GetModeLine - scrn: 0 clock: 148500
GetModeLine - hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
SwitchToMode - scrn: 0 clock: 74250
hdsp: 640 hbeg: 672 hend: 752 httl: 864
vdsp: 480 vbeg: 480 vend: 482 vttl: 505 flags: 37
Checking against clock: 148500 (148500)
hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
Checking against clock: 94500 (94500)
hdsp: 1024 hbeg: 1072 hend: 1168 httl: 1376
vdsp: 768 vbeg: 769 vend: 772 vttl: 808 flags: 5
Checking against clock: 56300 (56300)
hdsp: 800 hbeg: 832 hend: 896 httl: 1048
vdsp: 600 vbeg: 601 vend: 604 vttl: 631 flags: 5
Checking against clock: 74250 (74250)
hdsp: 640 hbeg: 672 hend: 752 httl: 864
vdsp: 480 vbeg: 480 vend: 482 vttl: 505 flags: 37
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(II) NVIDIA(0): Setting mode "640x480"
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
SwitchToMode - Succeeded
GetModeLine - scrn: 0 clock: 74250
GetModeLine - hdsp: 640 hbeg: 672 hend: 752 httl: 864
vdsp: 480 vbeg: 480 vend: 482 vttl: 505 flags: 37
GetModeLine - scrn: 0 clock: 74250
GetModeLine - hdsp: 640 hbeg: 672 hend: 752 httl: 864
vdsp: 480 vbeg: 480 vend: 482 vttl: 505 flags: 37
SwitchToMode - scrn: 0 clock: 148500
hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
Checking against clock: 148500 (148500)
hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
vdsp: 960 vbeg: 961 vend: 964 vttl: 1011 flags: 5
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(II) NVIDIA(0): Setting mode "1280x960"
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
SwitchToMode - Succeeded
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing.

Can any one share with me any two critical issues in DP support project

Hello friends,
I am new to DP support project in SCM5.0 version,can any one share with me my queries
1.what is my support rolles and responsiblities .in DP
2.can any one share with me any two critical issues in DP and how can you resole it

Hi Sivaram,
1. As a DP functional consultant you need to resolve all the incidents raised in APO DP module( Forecasting, lifecycle planning, master data in APO DP, Planning books, macros , release to APO SNP or R/3 or other systems, CVC maintenance etc) which will also include BW part of SCM -APO related to DP, like data extraction and back up into and from infocubes. You will also support all the interfaces realted to APO DP , for the APO related part of the interface.
You need to reoslve these incidents in the time frames defined by SLAs for the support project.
You will have to also carry out problem management of some of the critical incidents so that incidents do not re-occur.
Further you will have to support Release /Change managment support( if it is part of your contract of Support project).
This willl involve testing changes in quality system, before these are moved to production system.
2 I found 2 crtical issues in APO DP support as below:
2.1 Sales history extraction data interafces from BW system used to have problems : technical problems of interface / jobs in BW running late, functional problems: sales history extract in BW not correct because various reasons
This used to lead to delayed job runs in APO and finally delayed forecasting and ptehr DP processes .
By proactive monitoring by BW team and taking appropriate actions for master data issues, this issue occurance frequency was reduced , but not completely eliminated.
2.2 Another major issue was related to back up process of APO DP planning data into infocubes. Finally by splitting the jobs as per daily, weekly and monthly bakc up procedure , we were able to resolve the issue.
I hope I have answered your queries.
Pleasse check and confirm.
Regards
Datta

Two Monitors cause crashes in 10.4.7?

I remember reading a Macintouch article a couple months ago stating that two monitor systems crash in 10.4.7 and that this was a "known issue."
Whether my recollection is correct or not, I had three or more mysterious crashes after updating to 10.4.7. This resulted in my going back to 10.4.6, which has solved the problem.
I have two questions: 1) Is this indeed a known issue, and 2) is there a way for me to run 10.4.7 with two monitors with no monitor-related crashes?
Thanks a lot.
Trevor Monroe
PowerMac G4 AGP Mac OS X (10.4.6) 2 GB RAM, ATI 9800 Video Card, FASTMAC 1.5 GHz CPU Upgrade

I don't recall the article but I can say that I've been running my dualie G5 with two displays and I'm updated to 10.4.7. I also often run my MacBook with an external display or projector. I've not seen a kernel panic on my MacBook ever and I can't remember the last time I've seen a kernel panic on my G5. In fact, I'm not sure if I ever have...I've owned it about 18 months now.

Multi monitor issues with resolution(?)

At a customer I have got a really strange and annoying problem. The customer has got a Hyper-V VM with 2012 R2 Server as a RDS server aka Terminal Server.
One user has got issues with his multi monitor setup. The connection settings seems to be OK. It is set to full screen and the checkbox for the multi monitor configuration is enabled. Theoretically this works because the user sees a correct setup with one
primary display and one secondary display. The settings itself are correct.
1. Primary display: 1680*1050
2. Secondary display: 27" 1920*1080
The display settings on the client are nearly the same except that the numbers of the two monitors are different (those numbers you get when you click identify at the resolution change window). On the Windows 7 client the primary display
number 2 and the 27" has got the number 1. On the Terminal Server the primary display has got the number 1 and the 27" display has got the number 2. But the corresponding resolution at the display number is correct.
Now the problem. Everything seems fine, the desktop is expended. But when the user is "touching" the top or bottom edge of the screen the display is scrolling (in full screen) - like in a 3D game scrolling over a map. The user told me that
both screens are scrolling equally at the same time. I am not sure but the user told me that if he is going to the bottom the CLIENT task bar appears. Changing the task bar of the client to fixed the user told me that the task bar will always show up. - Strange
that CTRL + ALT + BREAK does not work.
I tried to press CTRL + ALT + BREAK twice, changing the resolution to a fixed value and back to full screen again, changing the primary display to the new 27" monitor, adding smart sizing:i:1 to rdp file and upgrading the Intel HD
4600 laptop graphic drivers (must be downloaded from Lenovo :/). NOTHING helped :(.
But this strange behavior does not exist on the client. Opening two programs (simple notepad e.g.) on each display and maximize them and moving the mouse the screen borders won't show this problem. It only exist on the remote session.
Now the "funny" part. If I connect with Team Viewer to the client the problem disappears as long as I am connected. If I disconnect the problem shows up again.

Hi,
This is most likely a problem with the local machine's graphics driver and monitor configuration. I would suggest trying different things like removing and re-installing the display adapter and its drivers, removing the second monitor/restarting/adding
the second monitor back, adjusting the multi-monitor settings in display properties (changing between extending the desktop to the second monitor and not), undocking/restarting/docking, changing between different modes using Fn key on laptop (if laptop), etc.
The behavior under Team Viewer is likely because the graphics configuration is different when the driver is active.
I wish I could give you more precise instructions on how to resolve the issue. I have seen this behavior (panning desktop, multi-monitor config not exactly right) probably 3 times over the last 5 years, always with a laptop, and I had to "play"
with the settings before it finally went back to normal. The instances I have seen it occur did not involve Remote Desktop specifically.
-TP

Problem Connecting Two Monitors

Just set up a new HP Mini 300-30 with two monitors. Monitor connection is through a device I bought that has HDMI cable connecting to back of HP Mini and two outlets on device to connect two monitors using VGA cables that came with each monitor. Monitors work but are set up with mirror image and I have not been able to find a way to make each monitor run indpendently. If I use keyboard and press Windows key + P it brings up a screen where I can select monitor options. I select the option to run separate monitors but nothing happens. I believe I have tried everything but the correct way.

Hello @RedWingFan,
Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
I have read your post on how your desktop computer is not able to display two independent images, and I would be happy to assist you in this matter!
To ensure your displays are configured correctly, I recommend following the steps in this document on Using Two or More Monitors with One Computer (Windows 8).
Please re-post with the results of your troubleshooting, and I look forward to your reply!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

M92p HELP!!! About to return 6 new M92p due to Problems with two monitors.

Hope someone can help. Just unpacked last week six (6) brand new M92p with dual 24" monitors. Unfortunatelly the monitors are NOT from Lenovo since Lenovo does not sell color calibrated monitors.
The problem we are having is that we have tried connecting the two monitors using different conbinations of the 3 or 4 available video connectors on the back of the machine.
only ONE monitor works at 1920x1200, the other defaults to 640x480.
All the machines have a video card with 2GB. The video card has a DVI and a VGA port. The motherboard has VGA and DisplayPort. We tried one cable to DVI on video card the other on VGAon video card. Then we tried One cable on video card another on motherboard.
I also disable the motherboard video in BIOS; that did not work either.
NOTHING works!!! I am about to repack all these equipment and send them back.
If anyone has any solution to this issue, please let me know.
Thanks!

Possible driver issue. Have you run Windows Update and Lenovo System Update?
Also, beware of the BIOS settings for multi-monitor: http://support.lenovo.com/en_NL/downloads/detail.page?DocID=HT062228

How do i fix this dual monitor issue?

I'm trying to use two monitors in Premiere Pro: my main monitor for my timeline and editing, and the second for putting bin windows on. The issue is when I simply try to click to play a clip, full screen playback comes up on both monitors and basically freezes. I have to unplug the second monitor to get the monitor to respond.
I am up to date, I have tried checking and unchecking the second monitor playback button in Prefrences > Playback menu, I've restarted the program, and tried restarted my computer.
please help

this seems to be a new bug, seen a few posts but no solutions. you can try updating video driver. try changing the renderer to software only, thats in the menu "project settings". along with the unchecking of the second monitor in playback preferences, make sure the wrench tool icon menu on the program panel has enable transmit unchecked. do you have any third party plugins or hardware premiere uses? does this happen instantly or just every so often? computer specs, win/mac, hardware etc.

Upgraded to 10.8.5 and now have multiple monitor issues

hi all,
i recently updated my macpro (4,1) to 10.8.5 from 10.6.8.   i have two monitors hooked up to the gt120, one through dvi-->hdmi cable and one displayport-->hdmi cable. both monitors have worked fine for a year or two before update.
my desktop extends across both screens just fine. however, when i open up system preferences to adjust the color of the second monitor (using the display window on the second desktop) any changes i make affect the main monitor, not the second.   so i try changing color settings on the main monitor and it affects the main monitor, too. so i have no control over the second monitor's color.
i have reset PRAM, disconnected power, etc. i downloaded nvidia's latest driver. not sure where to go from here. btw - i am having other minor issues since upgrade such as my moure (wacom intuos) won't move onto second monitor; it's stuck on main monitor.   my apple wireless mouse will span both desktops. i guess it's probably unrelated but since it is affected by the monitors, too, maybe it's related.
any thoughts? thanks.
macpro (2x2.26 quad)
12 GB RAM
gt 120
gtx 285
internal RAID

If you have them in iCloud, open System Preferences > iCloud and activate Contacts

Two monitor issues.

Similar Messages

Maybe you are looking for