Howto: DisplayLink USB Single Monitor on Linux
Posted on 23. Dec, 2011 by jerome in Using
Unfortunately, Linux doesn’t support multiple graphics adapters the way Windows does, which means you can’t just plug in USB graphics adapters and expect them to extend your desktop (the good news is there is progress on this support).
What is possible, however, is running a single DisplayLink adapter, or several with a Xinerama or multiseat configuration — just as long as you don’t expect to use your main GPU at the same time.
The single-display case is relatively easy to set up, and we’ll cover that here.
First, make sure you’re running kernel version 2.6.35 or later (Ubuntu 10.10 or later). For older kernel versions, you’ll need to update udlfb and run a modified fbdev X server (not covered in this post). On these kernel versions, when you plug in your DisplayLink-based USB graphics device, you should get a green screen. This means that at the driver built into the Linux kernel is happy, healthy, and talking to the device.
Second, if you are running Unity Desktop in Ubuntu 11.04 or later, you’ll need to switch back to Classic Mode so you’re running straight X. Here’s how on Ubuntu:
Click on the power button in the upper right corner (mine looks like a light switch) and choose the last option, System Settings. Search for Login Screen, Double-click to display, Choose Unlock and enter your password, Select Ubuntu Classic as default session.
Third, if you’re running kernel versions between 2.6.35 to 3.1, enable the fb_defio option of udlfb. To do this, create or edit a file like
/etc/modprobe.d/50-displaylink.conf
and add the single line
options udlfb fb_defio=1
And reboot (or run “sudo depmod -a” and unplug/replug your adapter). This will turn on defio (page fault change detection) support. This option is already enabled by default in kernels 3.2+.
Lastly, create an X config file called 60-plugable.conf (or similar) with the following contents and place it in /usr/share/X11/xorg.conf.d (on recent distros; on older distros, make this your xorg.conf):
Section "Device" Identifier "uga" driver "fbdev" Option "fbdev" "/dev/fb0" EndSection Section "Monitor" Identifier "monitor" EndSection Section "Screen" Identifier "screen" Device "uga" Monitor "monitor" EndSection Section "ServerLayout" Identifier "default" Screen 0 "screen" 0 0 EndSection
Note: if your main GPU creates a /dev/fb0 even when the USB display is not attached, then your USB display is probably getting assigned to /dev/fb1. In that case, change /dev/fb0 in the “Device” section above to /dev/fb1
Now, on reboot, you should (hopefully!) see your login come up on your DisplayLink USB attached display!
This kind of simple setup is useful for:
- Testing or playing with your USB graphics adatper on Linux.
- Embedded systems with USB but no GPU.
- As a backup method when the main GPU or its driver isn’t available or working.
- Systems where a USB graphics adapter enables higher modes (up to 2048×1152) than the main GPU screen.
Please comment if you have any trouble with this single display case. See our past posts for additional information about the DisplayLink Linux kernel driver and some more involved setups.
The instructed here work on all Plugable USB 2.0 graphics adapters and Plugable USB 2.0 docking stations and thin clients (and should also generally work on all DisplayLink based products).
DisplayLink’s Latest Windows Drivers (6.1 M0)
Posted on 17. Dec, 2011 by Bernie Thompson in Windows
DisplayLink has had two major updates to their Windows driver package this fall: 6.0 M1 and the newly released 6.1 M0.
For Plugable’s USB 2.0 products with DisplayLink chips, however, we’re still recommending earlier DisplayLink Windows driver version 5.6 M1 (5.6.31870.0), because of its proven stability. For now, Windows Update will still deliver 5.6 M1 automatically when you plug a Plugable device in.
Here’s a little background on why:
DisplayLink’s newest 6.x drivers work with all DisplayLink chips (USB 2.0 and the coming USB 3.0 generation), but the primary development focus of version 6.x has been on enabling the coming USB 3.0 generation of products. Perhaps as a result, there are some minor tradeoffs for USB 2.0 generation devices.
Here are the tradeoffs we’re following:
1) On a few systems, screens may go blank after returning from a reboot or power event. The cause appears to be changes in the way display configuration information is stored with the 6.0 and 6.1 drivers – Windows and the drivers can get confused, and that confusion will persist across unplugs, reboots, etc (going back to 5.6 M1 is the solution in these cases)
2) The uninstaller on version 6.1 fails to uninstall from Windows’ Programs and Features (as a workaround, you can use the DisplayLink “cleaner” utility).
3) 5.6 M1 is the last release where DisplayLink’s logs are readable. When we hit any strange problems on a customer’s system, our ability to analyze the logs to find the underlying problems (and solutions) is one of the ways we try to provide better support for Plugable brand devices.
All that said, we run the latest drivers on nearly all of our own systems (so we can stay up to date with the latest developments), and generally they’re great. So if there are any 6.x features or fixes that are relevant to you, feel free to download and install 6.1 M0 or later to give it a try. You can always download the latest DisplayLink driver here. And we expect that with one of the coming releases, we’ll push forward our recommendation to the latest version.
For those considering the latest versions, here’s the features and fixes DisplayLink has delivered since 5.6 M1 (as of version 6.1 M0). We’ve cut down the list to just those appear to be relevant to USB 2.0 devices.
New features since 5.6 M1 (as of 6.1 M0):
- Improved video smoothness for DL-1×0, DL-1×5 and DL-3×00 series
- Improved frame rate
- Reduced CPU utilization
- DisplayLink Tray applet enhancements
(Note these are generally subtle improvements)
New fixes since 5.6 M1 (as of 6.1 M0):
Sometimes the DisplayLink screen will remain blank when the device is
re-plugged after having been disconnected during power save. (11708)
Moving a mouse over full-screen video playback causes quality to drop. (12409)
Sometimes DisplayLink screen comes on in clone mode instead of extending when
connecting the device for the very first time. (10217)
Sometimes video may freeze on DisplayLink monitor. (11333)
Other miscellaneous fixes
DisplayLink 5.6 M1 Driver on Windows Update
Posted on 24. Jun, 2011 by Bernie Thompson in Windows
Microsoft’s Windows Update system has been updated to the latest DisplayLink 5.6 M1 Driver (5.6.31854.0 dated 2011/04/18). If you used Windows Update previously to get your driver, you were getting version 5.5.
This update is compatible with and applies to all Plugable USB graphics adapters and docks.
This is great news, as this new version includes a few important fixes and features, and many small ones. Details below.
Notes
- Windows 7 makes Windows Update for hardware automatic, but it can be enabled for Vista and XP also
- The update will automatically be triggered by Windows when it sees a new device. Or for an existing device, you can trigger Windows Update manually, and look for DisplayLink’s drivers among the “Optional” updates.
Important Features/Fixes from 5.5 to 5.6 M1
- Fix for software-triggered screen freezes (which required system reboot or service restart)
- Support for Windows Server SKUs (with Aero installed and enabled)
- Better compatibility with nVidia and ATI GPUs
- Improved compatibility with newer DirectX apps
Full changelist from DisplayLink
C1. Fixed issues between R5.6 (5.6.31721.0) and R5.6 M1 (5.6.31854.0)
—————————————
If the reboot prompt after install is ignored on Windows XP, then the
DisplayLink monitor set to mirror may display corrupted data. (10953)
After installing DisplayLink software on some systems with switchable graphics
architectures, the main monitor may be dimmed and not responsive until reboot.
(10534)
Monitor details were not being updated in “Devices and Printers” folder when
changing the monitors connected to DisplayLink device. (9917)
DisplayLink monitors may flash occasionally when playing fullscreen videos on
several stations. (11173)
On Windows XP after installing DisplayLink drivers several reboot cycles may be
requested. (11079)
C1. Fixed issues between R5.5 (5.5.27797) and R5.6 (5.6.31721.0)
—————————————
DisplayLink Software upgraded through Windows Update will not work correctly
after rebooting the system (issue affecting releases R5.3 to R5.4 on Windows
update). (9658)
Blue screen on Windows 7 on some platforms when rebooting after having applied
layout changes. (9631)
The DisplayLink GUI stops functioning correctly after switching GPU on some
ATI/Intel hybrid systems. (10065, 10106)
Sometimes there are two DisplayLink icons present in the system tray. (9807)
Sometimes the DisplayLink icon is missing in the system tray. (9545, 9837)
Video in Basic Mode not working with the latest Windows updates on both Windows
Vista and Windows 7. (1609)
Video playback issues on Microsoft Windows 7 with the latest NVIDIA Drivers.
(10061)
A DisplayLink USB monitor could occasionally remain blank after a PC reboot.
(9622)
DirectX 9 games could crash when running on a primary, non DisplayLink, screen.
(10027)
DisplayLink software fails to install on NVidia Quadro FX 880M graphics card.
(9637)
On Windows 7 Windows Photo Viewer may show corruption when a DisplayLink
monitor is mirroring the main screen. (9612)
On some systems with switchable graphics architectures disconnecting
a DisplayLink monitor may cause main monitor to be switched off. (9750, 9747)
Screen corruption while performing the Aero 3D flip (Windows+tab) interface
effect. (10425)
Blue screen when restarting with a connected DisplayLink screen in Projector
Only mode. (10457)
After a series of layout changes the DisplayLink screens can sometimes freeze
while the DisplayLink GUI loses functionality. (10489)
2 DisplayLink GUIs are shown in the system tray after installation. (10504)
Blue screen when using a DisplayLink device for the first time on some Optimus
configurations. (10700)
On some Optimus configurations, rebooting with a DisplayLink device connected
causes the DisplayLink screens to remain black with a blinking mouse pointer.
(10701, 10702)
Screen corruption when using 3D GUI effects on DisplayLink screens in some
display configurations. (9611, 10425)
Screen corruption on DisplayLink screens while using some applications after a
transition from projector mode to duplicate. (9612)
Video in Basic Mode not working with the latest Windows updates on both Windows
Vista and Windows 7. (1609)
In rare scenarios a DisplayLink monitor may freeze. (10230)
DisplayLink USB monitor could occasionally remain blank after a PC reboot.
(9622)
Blue screen when playing video on multiple clients. (6309, 9442)
SRC Shell application crashed when playing video clip. (10212)
When the logon screen is displayed, occasionally the DisplayLink displays are
frozen and only updated by the mouse pointer. (10044)
On some switchable systems the main screen flashes continuously after
installing the DisplayLink driver or after connecting the DisplayLink device.
(10653)
Corruption is shown while moving the cursor near the edge of a window on top of
a Windows Media Player window. (10752)
Incorrect/missing Windows Update error reporting from the DisplayLink GUI.
(10523)
Sometimes a Windows XP computer with DisplayLink drivers installed will hang
while starting. (9607)
On some nVidia Optimus systems the DisplayLink display will remain black
immediately after installing the DisplayLink drivers. A reboot recovers from
this issue. (10785)
On some machines Windows falls into endless reboot loop after installation of
DisplayLink drivers. (10918)
Timing not compliant with the CEA861D specification. (10952)
Recent Comments