Hello,
I have a problem with BenQ E2200HDA monitor connected to MacBook Pro 13" (early 2011). As this monitor have only D-Sub connector (no Thunderbold, DisplayPort, HDMI nor DVI), I've bought Mini DisplayPort <-> D-Sub adapter.
This looks to be compatible at least on hardware level - I have Windows 7 on bootcamp, and there, I am able to use FullHD (1080p) resolution without any problem. Anyway, on OS X, highest resolution I am able to work on is 1680x1050. If I switch to 1920x1080, monitors goes black (anyway, it does *not* show "no signal" message; only goes black, but I am unable to open OSD menu).
I have tried SwitchResX software to check more resolutions, and the biggest one which works is 1920x1060 (does not work perfectly, part of image seems to "go out" of bottom of the screen, but at least, the image is visible).
I don't have so much idea about the reason. As it works on Windows on the same hardware, I suppose the problem may be somewhere in OS X. Maybe any setting I don't know about? System is of course up-to-date, but I hope this is not a problem with OS X itself.
Any idea?
Thanks in advance.
I have a problem with BenQ E2200HDA monitor connected to MacBook Pro 13" (early 2011). As this monitor have only D-Sub connector (no Thunderbold, DisplayPort, HDMI nor DVI), I've bought Mini DisplayPort <-> D-Sub adapter.
This looks to be compatible at least on hardware level - I have Windows 7 on bootcamp, and there, I am able to use FullHD (1080p) resolution without any problem. Anyway, on OS X, highest resolution I am able to work on is 1680x1050. If I switch to 1920x1080, monitors goes black (anyway, it does *not* show "no signal" message; only goes black, but I am unable to open OSD menu).
I have tried SwitchResX software to check more resolutions, and the biggest one which works is 1920x1060 (does not work perfectly, part of image seems to "go out" of bottom of the screen, but at least, the image is visible).
I don't have so much idea about the reason. As it works on Windows on the same hardware, I suppose the problem may be somewhere in OS X. Maybe any setting I don't know about? System is of course up-to-date, but I hope this is not a problem with OS X itself.
Any idea?
Thanks in advance.