Category Archives: DC-125

DisplayLink Releases New Windows Driver Version 7.1 M1

Today DisplayLink released their new Windows Driver Version 7.1 M1 (7.1.45135.0). We’re excited to have this new driver out, as it fixes a number of last issues that let us recommend the latest 7.X drivers over the earlier 5.X and 6.X series drivers, on all versions of Windows. All of Plugable’s current and past USB 2.0 and USB 3.0 devices with a USB graphics function will work with this new driver.

Download the latest version of DisplayLink driver here.

This release has fixes for these issues which have affected a significant number of our users:

  • DisplayLink driver versions starting with 7.0 could cause Flash to hang up and crash when running Chrome browser. Those problems are reported fixed in 7.1 M1
  • nVidia GPUs with drivers dated Oct, 2012 or later would experience flashing screens and crashes. These problems are reported fixed in 7.1 M1 for some users, but not yet all
  • Windows 8 Metro applications running on USB displays could come up with Window unpainted (Blue or black). Reported fixed in 7.1 M1

A number of significant issues on Windows remain:

  • Windows 8 Metro apps playing protected video content will not play while the DisplayLink driver is installed (will show message in Window to upgrade graphics drivers). This is a difficult issue to solve because Microsoft has tightened DRM policies in Windows 8, and expect it may remain for some time.
  • Some driver conflicts apparently remain between nVidia drivers from October 2012 and later, and DisplayLink. The new 7.1 M1 driver solves some of these issues, but not all. We’ve also seen examples where the very latest nVidia pre-release drivers resolve this issue. We’ll keep tracking this, and appreciate your problem reports and feedback.

In detail, DisplayLink lists these issues fixed in 7.1M1

  • Microphone is shown as ‘Not plugged in’ after replugging DisplayLink device. (14345, 14431, 14463)
  • In some cases uninstallation of DisplayLink Core Software doesn’t uninstall everything properly. (14617)
  • UDP streaming using DisplayLink ethernet device is unreliable. (14678)
  • Sometimes VGA monitor attached to already connected DisplayLink device is not recognized correctly. (14699)
  • Sometimes screens remain blank after DisplayLink monitors are resumed from suspend mode. (14703, 14743, 13669)
  • Some video players showing content only on half of the screen. (14790)
  • On some systems with nVidia GPU Desktop Window Manager is crashing causing Windows to drop to Basic Mode. (14942)
  • Some Metro apps on Windows8 show a blank blue screen. (14955)
  • Sometimes Chrome web browser is responding very slowly and Flash plug-in crashes. (15014)
  • Sometimes DisplayLink monitor shows white noise instead of content when changing mode to clone while playing video. (15030)

We welcome any experiences or questions below. If you have a Plugable product and have any problems at all, just email your Amazon order # to support@plugable.com and we’ll be happy to help. Thanks!

Fedora 18 and DisplayLink USB 2.0 Graphics Adapters

With the recent release of Fedora 18, we have been testing the many changes and improvements to the DisplayLink software stack that have landed for this latest version of the popular open-source distribution. A large amount of work has gone into improving functionality and ease of use with DisplayLink USB Graphics devices. Most of these changes are not Fedora-specific, but are present in all recent versions of the Linux kernel and Xorg display server. Unfortunately, DisplayLink support is still far from perfect under Linux, but it has come a long way in recent months. What follow is an account of what we saw while testing an assortment of our USB Display Adapters and docking stations under Fedora 18.

The system we used for testing is a custom-built PC with the following specifications:
Intel Core i5-3570 Ivy Bridge
ASUS P8Z77-V LK Motherboard
8GB DDR3 RAM

Additionally, we performed tests using both the built-in Intel Ivy Bridge Graphics(using Intel’s Open Source driver) and a Nvidia GeForce GT 430(using the Nouveau Open Source graphics driver).

Note: We have yet to perform any testing using the Nvidia proprietary driver, but results for those tests will be posted as soon as they are completed.

There are 2 primary use-cases for USB Graphics on Linux. The most common one is to connect a greater number of Monitors than your computer has ports for, the other use-case is to set-up a Multi-Seat environment in which multiple users each have access to their own, separate desktop session while sharing the same computer. Fedora currently decides automatically if the device that you have connected to your PC should work as a multi-monitor or multi-seat device. What this mean is that our docking stations are automatically assigned to a separate desktop session, and there is no easy way to make them operate in multi-monitor mode(a how-to on switching a docking station to multi-monitor mode will be added to this blog post at a later time). Likewise, our USB Display Adapters will automatically work as multi-monitor devices and manual configuration is required to change this behavior. With these limitations in mind, I have split the rest of this article into 2 categories.

Multi-Monitor (UGA-125, UGA-165, UGA-2K-A, USB2-HDMI, USB-VGA-165)

The Multi-Monitor user experience has improved in many ways from previous versions of Fedora, but there are also a number of bugs that can seriously hurt a user’s enjoyment of this technology. Using the Intel Ivy Bridge graphics, we were able to connect a UGA-165 and a UGA-2K-A to our system and to a DVI display, and the display was instantly recognized in System Settings->Monitors. We were then able to enable said display, and set-up its position in our virtual desktop, and just like that, we had a working secondary display running of USB.

Unfortunately, that’s where the good news ended, there are a number of bugs that still plague this setup. For starters, we were only able to do this on the Intel Ivy Bridge graphics, when we attempted to do the same thing on the Nvidia card running Nouveau, all we saw was corrupted graphics on the USB display along with a severe performance slow down on the main display. Additionally, booting the system with a DisplayLink device connected will result in the primary monitor never reaching the login manager, so the DisplayLink device needs to be connected once you have made it into the desktop session. Finally, if you log out of your desktop session with a DisplayLink device still connected, the login manager will also fail to re-appear on your primary display. On the GUI/Ease of use side of things, we ran into problems with selecting the proper resolution for our display, no matter what display we connected to our USB Display Adapters we only had the option to set it to 800×600 or 1024×768.

As far as performance goes, a non-composite desktop will obviously render the best results. A full gnome-shell session was certainly usable on our setup, but moving windows around was choppy. Switching to fallback mode provided a much smoother experience. Scrolling websites was also very smooth, and video playback is varied. YouTube video played at an acceptable frame-rate, even when going full-screen(at 360p or 480p), but VLC gave some odd issues in which new video frames would stop rendering if we expanded the window past a certain size.

Multi-Seat (UD-160-A, UD-160-M, DC-125)

Multi-seat has not changed much functionality-wise since Fedora 17, however, many bugs have been fixed. We were able to connect a few DC-125s and UD-160s to our Fedora 18 box and login managers spawned on their respective screens with no issues. A major issue we encountered on Fedora 17 has been resolved with these release.  We were able to boot our PC with multiple docking stations connected and they all initialized properly, none of them were sent to that dreaded green screen we sometimes saw before. Unlike the Mutli-Monitor scenario, Multi-seat worked with no issues on both the Intel and Nvidia graphics chipsets.

The performance of gnome-shell still leaves a lot to be desired when running on these USB Graphics chips, but switching to fallback mode fixes these issues. As a stress-test we even ran a Youtube video(at 480p) on each of our thin-clients and the experience was fairly smooth across the board, scaling this is obviously CPU-constrained.

With all of that said, it is pretty clear that there are still quite a few issues surrounding DisplayLink graphics under Linux, mostly in the Multi-Monitor use-case. If you are an Open Source Kernel or User-Space developer that would like to help improve this situation, we’d like to point you to our Plugable Open Source Hardware Samples Program where you may sign up to receive free sample hardware to help on your development efforts.

Plugable USB 2.0 Multiseat Thin Client with DisplayLink DVI/VGA up to 1920x1080, Audio, and 4 Available High-Speed USB 2.0 Ports Plugable UD-160-M USB 2.0 Multiseat Thin Client with DVI/VGA up to 1920×1080, Audio, 4 Available High-Speed USB 2.0 Ports Product Details  $79.00
Plugable DC-125 USB 2.0 Multiseat Thin Client with VGA up to 1440×900, Audio, 2 USB ports Product Details $64.95
Plugable UGA-165 USB 2.0 to VGA/DVI/HDMI Adapter for Multiple Monitors up to 1920×1080 / 1600×1200 Each (DisplayLink DL-165 Chipset) Product Details $44.95
Plugable UGA-2K-A USB 2.0 to VGA/DVI/HDMI Adapter for Multiple Monitors up to 2048×1152 / 1920×1200 Each (DisplayLink DL-195 Chipset) Product Details $54.95

Windows Multipoint Server 2012 and Plugable USB Zero Clients

Windows Multipoint Server allows you to share a single PC among many users by connecting many USB zero clients (USB terminals). It’s a huge maintenance, power, and cost savings.

Microsoft’s newly released 2012 version has a greatly improved software interface for supporting USB clients. But this change meant that, until today, the most popular USB client technology (DisplayLink) was not supported.

Plugable Technologies is excited to announce that our full line of USB thin clients now fully supports Windows Multipoint Server 2012. We’ve partnered with OSBASE, experts in Windows driver and graphics technology, to provide a full solution for WMS 2012.

Every unit of our Plugable DC-125 low-cost thin client and Plugable UD-160-M mid-range thin client now includes a license to OSBASE’s high performance software driver for WMS 2012.

How do I get it?

Windows Multipoint Server 2012 is available for download, and the free evaluation period can be easily extended to 6 months. See Microsoft’s WMS2012 download page for details.

You’ll need one Plugable USB zero client terminal for each display, keyboard, and mouse you’re connecting to the PC. Plugable’s USB terminals are shipping in volume now, including the low-cost Plugable DC-125 ($64.95) and mid-range Plugable UD-160-M ($79).

We have a limited number of “trial kits” available for 90-day loans. They include up to four Plugable DC-125 and/or Plugable UD-160-M models, plus a powered USB hub (total around $300 value). Just email sales@plugable.com with a little detail on your organization and deployment goals.

And if you’re a non-profit, library or school, Techsoup and Microsoft have programs to donate their software for you.

How do I install drivers for it?

From the console mode of WMS 2012, download and install the new drivers for the Plugable hardware here:
WSM2012 software drivers for the Plugable DC-125 and UD-160-M.

Learn more

Read more about Windows Multipoint Server from Microsoft. And feel free to post below with any questions – we’re here to help!