Setup Process on AMD and NVIDIA, Dual HDMI Testing

Unfortunately for ASUS, setup and use of the PQ321Q isn't quite as simple as plug and play quite yet.  In our initial testing video you saw some of our problems and conflicts getting the monitor up and running on both AMD and NVIDIA test beds – it was kind of annoying and embarrassing enough for NVIDIA to get them to push out a new driver to address SOME of the problems in under a week.  But let's talk about the better experience first with AMD.


Setup with AMD Radeon HD 7000-series

Connecting the ASUS PQ321Q to our AMD Radeon HD 7970 GHz Edition card via the included DisplayPort cable was by far the easier of our two experiences.  With the monitor turned on and MST mode enabled in the DisplayPort STREAM options, we booted into Windows right away but the OS and driver was seeing either head of the display as a unique monitor.  As a result, we had the start menu of Windows 8 on the left hand side and your standard desktop wallpaper on the right hand side.  But, right away, the screen was usable as AMD has identified each panel and set it up as a spaned display configuration, each at 1920×2160.

Great, but how do you set it up as a single display with a single resolution?  Eyefinity.  I entered into the AMD Catalyst Control Center and ran the standard Eyefinity configuration utility and created a two-panel option.  Boom – we were up and running.

As with any other Eyefinty result, the operating system sees a single panel, but we just happen to be running it at 3840×2160 with a refresh rate of 60 Hz. 


Setup with NVIDIA GeForce GTX 700-series

Things weren't quite as simple with NVIDIA as it turned out.  There are some bugs and issues that were addressed with some driver fixes they shared with me this week but there are other problems that won't be addressed until a new firmware is pushed out by ASUS and STMicro later in the month.  The first problem was an occasional ability to fail a cold boot – the motherboard would sit and stare at me with a "62" on the POST code and do nothing else until I hit the reset button.  Afterwards, it would start over and make its way into Windows nearly 100% of the time.  Annoying, but workable.

Another potential problem was the lack of ability to see the POST screen and BIOS during boot – most of the time our PQ321Q only showed something on the panel when we had entered Windows 8 and gotten to the login screen.  That can be pretty annoying and would require a user to have another monitor handy if any troubleshooting ever needed to happen with their rig.

In my experience it was also very hard to get anything on the screen if you don't at first boot into Windows with your NVIDIA graphics card with the monitor in SST mode rather than MST mode.  Once you are in Windows, you can switch the panel to MST mode and the system will recover, and you can reboot back into Windows each time after that without switching modes.

After talking with NVIDIA and ASUS about these problems, both companies seemed very confident that most of if not all would be addressed with a forth coming firmware updated provided by STMicro and pushed out by ASUS to its customers.  The current estimate for that release is the end of July so I'll be sure to test out the changes once we have the FW installed on our test unit.  (A recent driver release by NVIDIA helps with some other compatibility issues.)

After finally getting MST mode working over the DisplayPort cable with our NVIDIA GeForce GTX Titan graphics card, the rest of the setup is actually easier than you have with AMD.  NVIDIA has never supported 2×1 Surround configurations on GeForce graphics cards and that doesn't really change with these driver releases.  Instead, NVIDIA is looking for these panels as a matter of special case and configuring the setup automatically for you.  There is no need to go into the driver and setup a grouping or tell it which side is right or left, etc.

In truth, that is the promise of the upcoming VESA 1.3 standard that includes new requirements to make tiled displays a better supported category.  Once THAT firmware is released by ASUS (they are claiming later in the year) and with further tiled monitors, the display and graphics card will communicate without user intervention about how many heads are included, their orientation and refresh rates and set it up automatically.  NVIDIA is basically attempting to emulate this with updated drivers but it will be an industry wide feature once VESA 1.3 becomes the norm.


Dual HDMI Testing

I had several readers asking about the support for Dual HDMI mode with the ASUS PQ321Q and I have had mixed results.  Because none of the graphics cards on the market (or at least that I have here) include dual HDMI 1.4 outputs, I was forced to use one native HDMI connection and then adapt either a DVI or DP connection to HDMI for the second input.  With AMD, no collection of adapters would allow me to run 3840×2160 at 60 Hz and after a talk with AMD it seems that we need an ACTIVE DisplayPort to HDMI 1.4 adapter (which I have ordered but are still not yet available) to get it to work correctly.  You are able to run at 4K resolution with a 30 Hz refresh rate but that kind of defeats a primary selling point of this $3500 monitor.  So currently dual HDMI mode appears to be out for AMD cards.

The same was true for NVIDIA last week but over the last few days they were able to provide a brand new driver (not the one posted publicly this week) that was able to enable 3840×2160 @ 60 Hz using the native HDMI port and a passive DVI to HDMI adapter for the second input.

With this driver and configuration the system acted identically to when it was connected via DisplayPort with MST enabled.  Yes, that does include the POST and cold boot issues, but once in Windows it was seamless.


Obviously there is a lot left to be desired still for the ease of setup and configuration of the ASUS PQ321Q monitor.  The AMD setup experience was by far the easier of the two but NVIDIA made a lot of strides with a couple of driver revisions in the last seven days.  Most of the other problems with NVIDIA will likely persist until a firmware update or two filter their way out.

« PreviousNext »