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).

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

• It’s shocking to see a keyboard projected onto any table, and be able to type in thin air (that was also true of its predecessor, the Celluon LaserKey CL850)
• You can connect to any PC or mobile with either with USB or Bluetooth. It uses a battery in wireless mode. That battery charges via its included USB cable
• It now has a mouse mode with multi-touch support for Windows 7 (Doesn’t support Mac or iOS multitouch)

But the really important thing about the new Magic Cube is it’s now driverless: It uses the standard Bluetooth HID profile and standard USB HID class, so for whatever you connect it to, it just sees a standard USB keyboard or mouse (which have always used HID). No drivers, no fuss.

That makes the new Magic Cube work with nearly all devices out there that can use a standard Bluetooth or USB keyboard: iPad, iPod, iPhone, Windows, Mac, Linux, and lots of other mobiles and devices.

iOS devices, in particular, are well-matched because the built-in auto-correct is a great help for improving accuracy (which is the main remaining downside of a projection keyboard — it takes getting used to).

If you’ve never had the chance to try a laser keyboard, take a look at this video to see it in action.

Celluon Magic Cube Laser Projection Keyboard and Touchpad

Product Details

$169.99

It’s amazing how few people know about the possibilities of turning one computer into many with simple USB terminals. We’re hoping more stories like this will get the word out!

To Whom It May Concern:

I want to take a second and thank you for the support you have given me. It is not often I find such good people that take time out of their busy day to help! Thank you so much!

I voluntarily single handedly support a small non-profit K-12 school. A little IT history on that school was that as of early 2009, I started getting involved with the IT Infrastructure. In reviewing their systems, I noted that they were running a Microsoft Small Business Server 2000 to which was only used to serve IP address and keep some files in a fileshare. The server had been installed in 2000 to which had not been maintained since then except for the occasional reboot and update.

In 2009, Microsoft announced that they would discontinue the support of Microsoft Server 2000 in July. Knowing this, I began having meetings communicating to the staff of the impacts of running a server without having support for major things like updates. I helped them decide that we should upgrade the infrastructure to Microsoft Small Business Server 2008 as well as source a new server to run the software.

While the server was on order, we began updating the entire wiring infrastructure of the network cabling to consistently possess at least Cat 5 cable.

I installed the new server as well as setup the ability to use Microsoft Exchange Server, Sharepoint Server, and a file Server. Also, I made sure to install a raid system as well as a nightly backup system. For the first time, the staff had email addresses with the school name! The staff we all very excited to use the new system.

Noting that there were many old computers that were at least 7-10 yrs old, we sourced and installed Microsoft Server 2008 in a Hyper-V session in order to use Terminal Server, now called Remote Desktop Services. On that Terminal Server, I installed all of Microsoft Office 2010 as well as other pertinent programs needed for the school. This allowed a repurposing of all the older computers as well as combining the old computers with new flatscreen monitors. The speed of the Terminal Server made the staff feel like they all had brand new computers!

I had been using the Comcast Modem as a firewall and knew that the firewall needed to be upgraded. The school needed a way to track everyone on the internet as well as the capability to filter the internet. I sourced a smaller used HP DL380 server to run an all-encompassing web filter, spam filter, firewall, routing, etc., named Untangle. This also sped up the internet experience as Untangle has the ability to cache websites.

Next on the list was to revive a computer lab that had not been run in over 2 years. There were several questions to be answered in order to ascertain how the lab was going to be built with these criteria in mind:

· Cost Effective

· Ease of maintenance

· As Energy Efficient as Possible(green)

· Reliable

· Ease of use

With that in mind, we came up with a few options. The first option was to utilize the computers from the old lab with a Terminal Server session. Because the base software of the computers was Windows 2000, they would have to at least be upgraded to Windows XP for security and Microsoft support reasons. Because of the expense and support needed, we decided against doing that option. Specifically we did not meet the goals of:

· Ease of maintenance

· Reliable

· Ease of use

The next option was to utilize “nettop” computers, specifically the Foxconn NetBox-nT525 nt525-0H0W-B-A-NA-BOX that we could mount to the back of a monitor. We then sourced 10 refurbished Dell 19″ monitors. I purchase one of the mini computers for test. I installed both Linux Edubuntu as well as Windows 7. The problems with this route are that it did not meet our objectives because:

· Not as cost effective because of the need for 10 computers

· Increased maintenance need

· Having to learn Linux by the staff therefore not easy to use

· No ability to use Remote Desktop into the computers (would have had to install VNC)

The third option was to install a dumb terminal system. Two systems were looked at including Linux Userful and Microsoft Multipoint Server 2011.

I admit that I am not near as intelligent on Linux as I am Microsoft products. For Linux, I know just enough to get me into trouble I think. I can do almost anything I want with any Microsoft OS and almost all software. With Linux, I have to struggle and look up internet blogs to help me with basic functionality. This is the second main reason I chose Microsoft over Linux.

We ultimately chose Microsoft Multipoint Server 2011 and here is why: I guess I could really boil it down to be selfish. Because I need to be able to support the school, I want the capability to remotely connect to any user computer either interfaced with the user or totally without the user in order to solve issues. Also would like to remote to apply updates and normal/general server maintenance.

The server we purchased to run the environment was a Dell R210. It is a 2.93 ghz Xeon Hyperthreaded Quad Core with 16 gb 1333mhz ram. It should be able to do whatever we want in this situation, right? Wrong. I also sourced 5 DC-125 units from Plugable to test the server for the needs of the school.

I then installed Microsoft Multipoint onto the server as well as all the displaylink software required. I tried plugging in a DC-125 to which did not work as expected. I then began troubleshooting.

After 3 weeks of troubleshooting with Dell and Microsoft, I got nowhere near making the system run. I then began consulting with Plugable. They had absolutely phenomenal support. Very quickly we determined the situation was caused by the 1998 technology used by Dell for the video card.

I then sourced an ATI 2270 video card and placed it in the only open slot. It worked! Yeah! If it wasn’t for Plugable’s awesome support, I would have had a very expensive paperweight as well as the need to go out an purchase 10 computers with Operating Systems!

Let’s talk about GREEN! The lab is only running one computer instead of 11. The server is running an LED monitor which is 1/10th the power requirements of LCD. The ATI 2270 video card only uses max 17.5 watts of power. All combined, the lab requires very little power requirements than what would have been.

As for the rest of the criteria, it was all met.

So, this is where we stand in the school, an operating lab based on Microsoft Multipoint OS connected to Active Directory and the internet. Have tested the system with 2 workstations running full screen Hulu and one running full screen YouTube and the frame rates never dropped as well as sound/video never got out of sync. I am extremely happy with this setup!

About me, I am an “old” computer guy I guess. Sometimes I still prefer DOS over windows. My favorite computer language is Assembler. 95% of everything I have learned has been on my own eventhough I do have a degree in CIS. I don’t admit readily to others that I know anything but I normally get tasked to fix everyone’s computer. (I gotta stop doing that or at least charge.) In my home, I am running a full server with exchange, IIS (I can run Apache just fine), and other network technologies which is where I have learned the most and have been doing this for more than 10 yrs. My entire family, internal and extended, all syncs their phones to my exchange server for email, for free.

As you can see, I love computing platforms as well as the social aspect. I also love to be on the bleeding edge. Companies like Plugable really go the extra mile to help everyone, especially to support the needs of a non-profit school. I love Plugable and their DC-125!

Unfortunately, Apple limits compatibility to Apple brand adapters (even though they use the same ASIX chipset). And it fails on non-Apple adapters in a confusing way: it will show as “Connected” in the Network control panel, but connections out won’t work — you’ll notice it has a self-assigned IP address (169.*), no router, and no DNS server. It looks something like this:

Fortunately, ASIX has an updated driver which works on Lion (and older versions). Note that if you had done this before upgrading to Lion, your old driver may be 32-bit. Lion moves all systems to a 64-bit kernel, so in the case of a Lion upgrade, you may have to uninstall the old driver (uninstaller included in the driver package), and follow the steps below to get ASIX’s latest driver.

Download the Plugable USB2-E1000 (ASIX 88178 chipset) driver.

If you’re downlading with Safari, look for the Download folder the Lion has in your Dock by default. Click on that to bring up recent downloads, which looks like this:

Open that folder, then click on the “.dmg” to open the ASIX driver installer disk image.

The image then shows up on the left side of the window, below your other drives, called “DISK IMAGE”. Click on this to open the image, then click on the installer (the icon with the package opening).

You’re finally out of Lion’s folders and into the installer proper.

The ASIX 88178 driver isn’t big (254K)

You will be prompted to let the driver install.

A reboot is required for the newly installed driver to be active.

After the reboot, if you open the Network control panel, you should now see “Connected”, but now also with a properly assigned IP address, DNS, etc.

If that’s not the case (or something goes awry later), it’s common on Mac OS X to need a fresh interface for the adapter, which you can create via the network control panel (this creates a new, clean configuration for an adapter). See the ASIX Mac installation guide for details.

And once you have that automatically assigned IP address, you should be done – open Safari and enjoy!

And if you have a Plugable adapter and have any problems at all, we’re here to help. Visit support.plugable.com or email support@plugable.com anytime. Thanks!

Where to Buy

Plugable USB 2.0 to 10/100/1000 Gigabit Ethernet LAN Network Adapter (ASIX AX88178 Chipset)

Product Details

$26.95

The easiest way to go about installing our Plugable USB to Serial adapter is by starting with the device.

• If you want to verify that the adapter and the driver were installed properly click here

Connect the device to the Mac. Once connected click on the Apple icon and on ‘About This Mac’

Click on ‘More Info…’

Click on ‘USB’ on the left and on the ‘USB-Serial Controller D’
If all is well you should be seeing something like this:

Time to get the driver! Fire up Safari and browse to http://plugable.com/drivers/prolific/ and scroll down to Mac.
Click on the ‘PL2303 MacOSX10.6 dmg v.1.4.0.zip’, the Safari Downloads window should come up:

Double click on the md_PL23-3_MacOSX10

Now double click on the PL2303_1.4.0.dmg to mount the image

Now double click on the PL2303_1.4.0 to start the installation

Once the installer comes up click ‘Continue’ to proceed.

Then ‘Select a Destination’ click on your desired drive and click ‘Continue’ to move forward

Now just click ‘Install’ to continue.

You may be asked of your username and password – enter them and click ‘OK’

You’ll get a warning about restarting the computer after the installation is complete. This is normal, click ‘Continue Installation‘.

Installing should start (takes a couple of minutes to complete)

When it’s done you should see this:

Click on ‘Restart’ to reboot the Mac.

 After you restart, check that everything has installed OK.
On the Mac there are two methods to determine this:

Method 1:
Click on ‘Applications’

Click on ‘Utilities’

Click on ‘Terminal’

Type:
kextstat | grep prolific
and:
ioreg -c IOSerialBSDClient | grep usb
Your results should be very close to this:

Method 2:
Click on ‘System Preferences’

Click on ‘Network’

Now click on the ‘+’ sign on the bottom left, and then on the ‘Select the interface and enter a name for the new Service’ click on ‘Interface’ – you should be seeing the ‘USB-Serial Controller D’ there.

This will create a “Network” interface for a modem or serial port. Because it’s a serial port, it’ll say “Not Configured” and that’s normal:

From the “Advanced” button you can change default settings (usually not needed). And this won’t change the “Not Configured” message – that’s still ok.

Now finally, you need an application which will talk to the serial port. On Mac, the file which maps to the port is /dev/cu.usbserial. If you have a null modem cable and a terminal program on the other side, the Mac actually has a built-in terminal program called “screen” that you can use to test the connection.

Once that is up and connected (and if the serial ports are set to the same baud rate and paramters), you can type on either side and see the characters come across.

Support

USB Serial on the Mac is a real melding of the very new and very old. If you have any trouble, just visit plugable.com/products/pl2303-db9/support/ to see existing FAQs for Plugable’s USB Serial adapter.

Where to Buy

Get the driver from: http://plugable.com/drivers/prolific/

You’ll want to download the driver and unzip it anywhere on your desktop. Once you have, double click on it to start the installation.

The installation is relatively simple and no questions are asked. When it’s done you should see something like this:

Now go ahead and connect the adapter. You should get a pop-up looking like this:

Finally Windows should report that the device has been installed:

On Device Manager you should be looking at something like this:

• Now, If you want to change the COM port assignment, here’s how to change the COM port for a USB Serial adapter on Windows 7

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)

Through July 4th 2011, we’re temporarily lowering the price of our Plugable UGA-2K-A USB Graphics Adapter to $57.50 (normally $64.50).

If you know how great 2 or 3 monitors are, and have wanted to add another (up to 6 on Windows; 4 on Mac), this is a great time to do it.

More independent USB-attached displays for Independence Day. Yea!