You can go to System Preferences > Displays, then option-click (press option key while left-clicking) on Scaled to expose additional resolutions that aren't exposed with a normal left-click.
Otherwise, you have a great choice of software for that, like switchResX:
Why hassling with Apple's inbuilt screen settings, when there is so
much more to get and ...
As has been mentioned, you couldn't daisy-chain multiple Thunderbolt displays on pre-2012 Airs. Two possible add-ons that'll allow you to connect an additional external display:
Matrox DualHead2Go (in action hooked up to an 11" Air)
I've used the latter and they work pretty well for non-intensive applications.
We have a brand new Late 2016 Macbook Pro and 2 Apple/LG 21.5 USB-C 4K monitors. Daisy-chaining/MST does not work. We are using the monitors and nothing else with the original cables.
Only way to get it to work is to connect each to individual USB-C ports on the MBP.
Sad but true.
Apple does not support Display Port daisy chaining.
Using Thunderbolt screens, this would work, and because the Apple screen is a Thunderbolt screen, that works. The fact that Windows supports DP daisy chaining, does not mean that Apple does this intentionally to force users to buy their monitor.
So... Never attribute to malice that which is adequately ...
More than likely, the issue is, in fact, your Mini DP to HDMI adapter.
The AmazonBasics Mini DisplayPort to HDMI Adapter adapter that you listed is a passive adapter (notice nowhere do they say "active"). Additionally, is much less expensive than an active converter like the Cable Matters Active Mini DisplayPort to HDMI Adapter
Passive vs. Active
Your Air supports the internal display as well as only one ThunderBolt external display. As commented below, the Mid 2012 Air can run two ThunderBolt displays. Physically you can daisy chain as many Thunderbolt Displays as you have money, but the first limitation you will run into is the graphics card.
The official Apple knowledge base article lists the ...
After doing a little research on Dell's daisy chaining monitors, I came across this bit of info on their support site:
Multi-Stream Transport (MST), also known as Daisy Chaining, is a new
connection specification that allows multiple monitors to be connected
in series with the video signal being passed from the computer to a
monitor, and then from ...
This may not be the only available resource on this topic, but it is a comprehensive & reliable one...
EveryMac, as the name suggests, has information on every Mac model ever made [also iPhones, iPads, iPods], including but not limited to the number of external displays supported & their maximum specification.
If you are not absolutely certain ...
I own a 2013 MacBook Air. This is equipped with a Thunderbolt 1 port :
Mini-DisplayPort -> HDMI adapter (1920x1200 max.)
Mini-DisplayPort -> DisplayPort adapter (upto 2560x1600 max.)
I've used both and am now driving daily on my MBA 13" with a monitor running at 2560x1440.
You can get full resolution with mini DisplayPort to DisplayPort or mini DisplayPort to Dual-link DVI. Dual-link DVI supports up to 2560x1600 pixels resolution. DisplayPort supports that resolution or even higher.
You will not get full resolution with mini DisplayPort to DVI. DVI is limited to 1920x1200 or something similar. You usually won't get full ...
I'm not sure if this answers the question but I'm testing this out right now with a new MacBook Pro Touchbar 13" with 4 USB-C ports.
In the testing I'm using the Minix Neo C Hub which has
2x USB3 - Type A ports
SD Card Reader
Another USB-C that you can use for your power adapter
I'm able to get two monitors working, one through HDMI ...
As @bmike, @djacobson, and @jaberg have stated in comments, that will not work. There is currently (as of March 2012) no adapter, nor do I expect there to be one to adapt mini-DisplayPort to Thunderbolt. (The standards were defined to be backward-compatible, not forward-compatible.)
According to this source, this should work. This other source confirms it. These are the troubleshooting steps I would try:
Run all software updates on both the iMac and MacBook Air. A lot of times there are firmware updates that address issues like this.
Open System Preferences > Displays and click Detect Displays.
Reset the PRAM on both the iMac and the ...
Finally I found this. Looks like the default EDID configuration for Dell displays is not quite right.
On that post there's also a ruby script that suposedly generates the right file for your display, but it ended up screwing even more my resolution.
I downloaded the file from the first post, and after copying it to /System/Library/Displays/Overrides and ...
I looked up the specs and that display supports 4K resolutions. 2011 model Macs do not support 4K displays. I understand that you're trying to run it at 2560x1440, which Apple specifically says that model MBP supports for external displays. However, here's the issue you're running into...
To get that 4K resolution, you must have either an HDMI 1.4 or ...
Unfortunately no, not at present (10.10.1).
Firstly, your MBP needs to support MST which is part of DisplayPort 1.2 - you can check your laptop's specifications as they may vary depending on which GPU option you went with when you purchased your MBP.
Secondly, even if your hardware supports it (many recent MBPs do) Apple hasn't added support to OS X for ...
The solution is about as weird as the problem. To enable 60Hz in clamshell mode, I had to Option-click the "Scaled" radio button on System preferences' Display resolution screen, then the Refresh Rate option became available and I could switch from 30 to 60Hz. For some reason it wasn't enabled by default when lid closed.
EDIT: Also found out that ...
I would go for USB-C to DisplayPort directly. That would be one relatively inexpensive ($20 to $40 US prices) cable to do the job. Since your display won't charge the MacBook and do video over a single USB-C cable and you have several ports (display side and Mac side) - a dedicated cable would be my choice.
I like the USB-C to HDMI adapter you mentioned for ...
If your other input sources are networked computers that are on the same network as your MacBook? You could use a VNC like program such as ScreenRecycler to let other computers show their screen on your Macbook.
Yes, but it's not worth it.
You would have to take the laptop apart, design and engineer a custom converter to drive the LCD interface (internally, it's going to use LVDS to handle the interface between the laptop's motherboard and the screen), and power it somehow. It also would probably render the macbook from which you removed the screen unusable as a ...
According to this source, you will not be able to use a Thunderbolt cable in this fashion.
You can, however, get a Mini DisplayPort to Mini DisplayPort cable from Monoprice for about $5 and that should work just fine.
Another option to to use a display multiplexer, like the Matrox DualHead2Go DP. This will have much better performance (frame rate / snappiness) than the USB solution, at about 4X the price. It's best with matched dual external displays - or triple; there's also a 3-monitor solution. I haven't used one personally, but have recommended it to clients with ...
No. DVI-D only carries digital signals. Most (if not all) DVI -> VGA converters use the analog signal DVI-I carries. A mini DisplayPort to DVI connector will only pass on digital signals (as you correctly identified by referring to it as a DVI-D signal), so your DVI to VGA adapter is left out in the cold. You need to get a mini DisplayPort to VGA adapter.
Here's one example of someone running two 27" displays at 2560x1440 via Thunderbolt/DisplayPort plus an HDMI display at 1920x1200:
The Thunderbolt ports officially support up to 2560x1600 so that resolution shouldn't be any problem either:
As of 10.10.3 Apple does apparently support MST* on certain hardware:
These Mac computers support multi-stream transport (MST) displays at 60 Hz:
MacBook Pro (Retina, 15-inch, Late 2013) and later,
MacBook Pro (Retina, 13-inch, Early 2015) and later,
Mac Pro (Late 2013),
iMac (Retina 5K, 27-inch, Late 2014) and later
Okay, so I managed to work out what the issue was in the end - it was OS X's handling of the EDID data from the monitor. Windows evidently could read the data just fine, which is why it worked perfectly every time. Where Apple don't develop plug-and-play drivers for monitors (I assume) and hadn't added a profile for mine, it couldn't recognise it.
In the ...