USB Displaylink

[ragnarjensen]

You have to rebuild the Linux kernel, or at least build a kernel module to enable DisplayLink frame buffer support.

make menuconfig DisplayLink support

make_menuconfig_dl.jpg (59.19 KiB) Viewed 12918 times

I had to build a custom kernel in both 3.6 and 3.10.

--
Ragnar

[ragnarjensen]

Triple play

Code: Select all

Section "Device"
# RPi builtin video, framebuffer 0
        Identifier      "RPi"
        #Driver         "fbdev"
        Driver          "fbturbo"
        Option          "fbdev"                 "/dev/fb0"
        Option          "SwapbuffersWait"       "true"
        Option          "ShadowFB"              "off"
EndSection

Section "Device"
# USB DisplayLink video, framebuffer 1
        Identifier      "uga"
        #Driver         "fbdev"
        Driver          "fbturbo"
        Option          "fbdev"                 "/dev/fb1"
        Option          "SwapbuffersWait"       "true"
        Option          "ShadowFB"              "off"
EndSection

Section "Device"
# USB DisplayLink video, framebuffer 2
        Identifier      "uga2"
        #Driver         "fbdev"
        Driver          "fbturbo"
        Option          "fbdev"                 "/dev/fb2"
        Option          "SwapbuffersWait"       "true"
        Option          "ShadowFB"              "off"
EndSection

Section "Monitor"
# Center monitor. HP 1680x1050
        Identifier      "HP"
EndSection

Section "Monitor"
# Right monitor. Dell 1280x1024
        Identifier      "Dell"
EndSection

Section "Monitor"
# Left monitor. LG 1280x1024
        Identifier      "LG"
EndSection

Section "Screen"
        Identifier      "Secondary"
        Device          "RPi"
        Monitor         "HP"
EndSection

Section "Screen"
        Identifier      "Tertiary"
        Device          "uga"
        Monitor         "Dell"
EndSection

Section "Screen"
        Identifier      "Primary"
        Device          "uga2"
        Monitor         "LG"
        #DefaultDepth    24
EndSection

Section "ServerLayout"
        Identifier      "Default"
# The LG and Dell monitors are 1024 pixels high, 26 pixels less than the HP. Place their top-left corners
# 26 pixels below HP monitor's, in order to align monitors along the bottom edge.
        Screen 0        "Primary"               0 26
        Screen 1        "Secondary"             1280 0
        Screen 2        "Tertiary"              2960 26
        Option          "Xinerama"              "true"  # Enable XINERAMA extension to get one desktop over all monitors.
EndSection

One Pi, three screens.

TripleScreenPi3.jpg (61.76 KiB) Viewed 12864 times

--
Ragnar

[Shovelhead]

I am having having a hard time following your instructions. Is the only requirement is to change the xorg.conf file? Can you simplify? Thanks

[ragnarjensen]

No, first you have to get a kernel with drivers for UDL. The stock kernel from the Foundation doesn't have the drivers.
So, you'll have to compile a new kernel from source and there's no simple way to explain how to do that. http://elinux.org/RPi_Kernel_Compilation

If you don't feel up to compiling a kernel, you can try one of these:
I have made an image of Raspbian (for another purpose) that has the UDL drivers.
http://www.element14.com/community/mess ... oad#106822
That is a complete Raspbian distribution that you flash to the SD card.

As an alternative, I have made an archive of just the kernel, that is meant to go on top of an existing Raspbian installation:
http://www.element14.com/community/mess ... oad#107186

When you have a working kernel, it's time to change the xorg.conf file.
--
Ragnar

[Shovelhead]

Thank you for the help Ragnar! I will try to reflash the sd card later today. Then work on the xorg.conf file.

[Shovelhead]

Ragnar,
I was able to download your file and flash the card.
I will have to work on the config on Wednesday afternoon.
Thanks Ken

[Shovelhead]

Ragnar,
I want to make sure I am doing this correctly.
Is this how the xconfig should look? (This is what you posted)

Section "Device"
Identifier "uga0"
driver "fbdev"
Screen 0 <---
Option "fbdev" "/dev/fb0"
Option "ShadowFB" "off"
EndSection

Section "Device"
Identifier "uga1"
driver "fbdev"
Screen 1 <--- This one says "I have two monitors on the DisplayLink. Use the second."
Option "fbdev" "/dev/fb1"
Option "ShadowFB" "off"
EndSection

[ragnarjensen]

No, that one is wrong. In that post I'm pointing out where the errors are in his config.
Try this one out:

Code: Select all

Section "Device" 
# RPi builtin video, framebuffer 0
  Identifier "rpi" 
  driver "fbdev" 
  Option "fbdev" "/dev/fb0" 
  Option "ShadowFB" "off"
EndSection 

Section "Device" 
# USB DisplayLink video, framebuffer 1
  Identifier "uga" 
  driver "fbdev" 
  Option "fbdev" "/dev/fb1" 
  Option "ShadowFB" "off"
EndSection 

Section "Monitor" 
# Primary monitor.
  Identifier "PrimaryMonitor" 
EndSection 

Section "Monitor" 
# Secondary monitor.
  Identifier "SecondaryMonitor" 
EndSection 

Section "Screen" 
  Identifier "primary" 
  Device "rpi" 
  Monitor "PrimaryMonitor" 
EndSection 

Section "Screen" 
  Identifier "secondary" 
  Device "uga" 
  Monitor "SecondaryMonitor" 
EndSection 

Section "ServerLayout" 
  Identifier "default" 
  Screen 0 "primary" 0 0
  Screen 1 "secondary" RightOf "primary"
  Option   "Xinerama" "1"  # enable XINERAMA extension.  Default is disabled.
EndSection

It's a generic config with no bells and whistles. The secondary monitor to the right of the primary.
--
Ragnar

[Henry_Jones]

Even the thread is quiet old and maybe a lot of things changed in the meantime, I'd like to ask if (there is / you can make one up) a how-to for dual Monitor Setup on the raspberry.

I already have the tbtft Driver running together with an Adafruit TFT, From the post in http://www.raspberrypi.org/forums/viewt ... dc035a554a I've copied the xorg-conf contents.

But I always get the X Server start on fb0 regardless of the Option "OneDesk" or "TwoDesk" I use. If I start X with FRAMEBUFFER=/dev/fbx it goes to the correct one.

I guess I'm missing important here, maybe you can point me in the right direction. I also downloaded the image mentioned in this thread, but did not try it yet, fearing that I'll loose the tbtft driver, as they also mention to be working only with a kernel different from the original Rasperian one.

[ragnarjensen]

Several things can go wrong if you take my xorg.conf and don't adapt it for your setup.
It's hardcoded for a resolution of 1680x1050 on the HDMI monitor. If yours is different the placement of the physical screens on the virtual desktop will go awry.

A simple

Code: Select all

startx

without arguments should start X on /dev/fb1.

Code: Select all

startx -- -layout HDMI 

should start X on /dev/fb0. Note the double dashes, they're important.
Both "OneDesk" and "TwoDesk" drive both monitors simultaneously. Furthermore, "TwoDesk" requires the ~/.config/autostart/10-desktopmgr-autostart.desktop and ~/bin/desktopmgr.sh scripts I show in the post you refer to.

You could try the very simple xorg.conf I show two posts above just to test that both monitors are alive.
If you need more help, please post the entire /var/log/Xorg.0.log file.

EDIT: Don't use my image or kernel linked to earlier in this thread. They don't have the fbtft drivers .
--
Ragnar

[Henry_Jones]

Ok, I'll try to adapt (and understand) your xorg.conf script better next week

without arguments it always starts on fb0. But the script from this thread works perfect. Both Monitors share one Desktop. That's more than I'd hoped for after two days trying.

Both Monitors (TFT and HDMI) have their own touch inputs which both cover the whole screen instead of only their own range.

So there is still something left to learn, when I'm back in the office next week. If it's more than the common Windows developer can understand, I'll ask again

Thanks for your help.

[vedranius]

I know this is an old thread.
But, did anyone ever got working Samsung UbiSync7 display and how?
Thank you!

[zigzag930]

Would love to see this working, but I've tried it with newest Rabsbian, etc on Rpi3 and when turning on the Xinerama I lose my HDMI.

Without Xinerma, I get HDMI + USB (DisplayLink) monitors both working as independent workstations. Trying to get extended desktop, but no luck.

Have tried the fbdev driver as well as the fbturbo driver. All s/w updated to latest available.

Does anyone have this working on Pi3 with new version of Raspbian (or any other flavor of ARM O/S)?

[lordaker]

Hello,

I have two monitors (Philips Brilliance 220SW), an usb DisplayLink Certified Kensingston K33907 and a raspberry pi 3 model B V1.2
with the OS Ubuntu Mate installed. I install the last kernel 4.9.60-v7+ with the displaylink drivers for ubuntu. But only the monitor who is connected at the adapter work. The monitor connected by HDMI display anything, just the command prompt after the raspberry have
finish to boot.

For my xorg.conf file, I used this process: https://www.novaspirit.com/2015/12/31/l ... pberry-pi/

Do you know how can I do for have my two monitor who work ?

And extended the display from the hdmi ouput to the usb adapter displaylink ?

Which config for my xorg.conf ?


Thank a lot...

[lordaker]

I follow this proceed:

https://www.novaspirit.com/2015/12/31/l ... pberry-pi/

After I download the driver from DisplayLink:

http://www.displaylink.com/downloads/ubuntu

I install it and update the Xorg packages too.

This is what I have in my file xorg.conf (/etc/X11/xorg.conf)

Code: Select all

Section "Device"
# RPI HDMI Monitor, framebuffer 0
	Identifier "rpi"
	Driver "fbdev"
	Option "fbdev" "/dev/fb1"
	Option "ShadowFB" "off"
EndSection

Section "Device"
# USB DisplayLink Adapter Video, framebuffer 1
	Identifier "uga"
	Driver "fbdev"
	Option "fbdev" "/dev/fb0"
	Option "ShadowFB" "off"
EndSection

Section "Monitor"
	Identifier "Philips"
EndSection

Section "Monitor"
	Identifier "Philips"
EndSection

Section "Screen"
	Identifier "primary"
	Device "rpi"
	Monitor "Philips"
EndSection

Section "Screen"
Identifier "secondary"
Device "uga"
Monitor "Philips"
EndSection

Section "ServerLayout"
Identifier "default"
Screen 0 "primary" 0 0
Screen 1 "secondary" LeftOf "primary"
EndSection

The two monitors (Philips) are power on, but my keyboard and my mouse don't work. How can I do to resolve that ?

[lordaker]

Hello everyone,

I try to connect a second monitor at my Raspberry Pi 3 Model B V1.2 by the usb adapter DisplayLink Kensington. I connect the first monitor to the hdmi port. I update the kernel, configurate the xorg.conf by following this procceed (https://www.novaspirit.com/2015/12/31/l ... pberry-pi/). My two monitors are Philips Brilliance 220SW.

This is what I have when the adapter is not connected.

#01_Dual_Monitor_Step_1.jpg (90.21 KiB) Viewed 7919 times

This is what I have when I connect the adapter to the Rasberry.

#02_Dual_Monitor_Step_2.jpg (81.97 KiB) Viewed 7919 times

Do you known what I could do to resolve that ?

OS: Raspbian Stretch 9.2

[ragnarjensen]

I think the USB Displaylink driver is included in Raspbian nowadays. You shouldn't have to build it yourself.
As far as I know, the driver only supports USB2 devices. There exists an USB3 driver for Ubuntu, but it's partly closed source and only runs on x86.

--
Ragnar

[hippy]

DisplayLink support for USB2 is built into the kernel now. I have found it's best to boot with DisplayLink plugged in as I have had issues with hot-swapping. When plugged in, even if not enabled and being used, I believe the DisplayLink monitor should show a green background.

[lordaker]

Hello @ragnarjensen,

Now it's work, I add in the /boot/config.txt file the line bellow:

framebuffer_depth=16

with the code foward:

Code: Select all

Section "Device"
    Identifier "displaylink"
    Driver "fbturbo"
    Option "fbdev" "/dev/fb1"
    Option "ShadowFB" "off"
EndSection

Section "Device"
    Identifier "Raspberry Pi FBDEV"
    Driver "fbturbo"
    Option "fbdev" "/dev/fb0"
    Option "ShadowFB" "off"
EndSection

Section "Monitor"
    Identifier "PHILIPS 221E"
EndSection

Section "Monitor"
    Identifier "PHILIPS Brilliance 220SW"
EndSection

Section "Screen"
    Identifier "screen"
    Device "displaylink"
    Monitor "PHILIPS Brilliance 220SW"
    SubSection	"Display"
    		Mode	"1680x1050"
    EndSubSection
EndSection

Section "Screen"
    Identifier "screen1"
    Device "Raspberry Pi FBDEV"
    Monitor "PHILIPS 221E"
EndSection

Section "ServerLayout"
    Identifier "default"
    Screen 0 "screen1" 0 0
    Screen 1 "screen" RightOf "screen1"
    Option "Xinerama" "true"
EndSection

But on my second screen I have little resolution all my icons are big. How can I resolve that ?
I use a DisplayLink USB 2.0 to VGA (U2-165-VGA). I try to install xorg-xrandr but when I put the command
xrandr in my terminal emulator I have the message below:
RandR extension missing

[ragnarjensen]

The keyword to set screen resolutions is "Modes"
The "Mode" keyword is something very different.

Have you tried without the Subsection Display?

--
Ragnar

[lordaker]

The keyword to set screen resolutions is "Modes"
The "Mode" keyword is something very different.

Have you tried without the Subsection Display?

--
Ragnar

Hello @ragnar

I try without the SubSection but it's always the same thing.



But the command xrandr doesn't work...

[ragnarjensen]

And if you have a subsection with Modes in there?

Code: Select all

SubSection	"Display"
    		Modes	"1680x1050"
EndSubSection

I have never had to use the Randr extension myself.

--
Ragnar

[lordaker]

And if you have a subsection with Modes in there?

Code: Select all

SubSection	"Display"
    		Modes	"1680x1050"
EndSubSection

--
Ragnar

Yes, it's the same thing. I have the same result...

What's the matter ? Is it the os ? If you have a solution, please tell me, thank a lot...

[ragnarjensen]

I have googled a little on your Kensington K33907 DisplayLink adapter.
Apparently it only supports resolutions up to 1440 x 1050.

--
Ragnar

[lordaker]

I have googled a little on your Kensington K33907 DisplayLink adapter.
Apparently it only supports resolutions up to 1440 x 1050.

--
Ragnar

Hi @ragnarjensen,

Now I use a adapter USB 2.0 to VGA (U2-165-VGA) with a supported resolution bellow:

Widescreen (16/32 bit)
- 1920x1080, 1680x1050, 1600x900, 1440x900, 1360x768, 1280x768, 1280x720

Standard (16/32 bit)
- 1600x1200, 1400x1050, 1280x1024, 1280x960, 1152x864, 1024x768, 800x600