displaylink-rpm / displaylink-rpm Goto Github PK

RPM sources for the DisplayLink USB display adapters

License: MIT License

Makefile 59.05% Shell 40.95%

displaylink-rpm's Introduction

DisplayLink RPM

This is the recipe for building the DisplayLink driver in a RPM package for Fedora, CentOS 7 and Rocky Linux. This driver supports the following device families:

DL-7xxx
DL-6xxx
DL-5xxx
DL-41xx
DL-3xxx

The package includes the Open Source evdi library.

Packages get automatically built by GitHub Actions and get uploaded to GitHub releases.

Usage

NOTE: Now buildable cleanly via .spec file (in mock f.e.). Download files via make srpm.

In order to create the driver rpm package you can run the command make from within the checked out directory. The Makefile should download the files needed for you and create an RPM.

A default make will use the evdi driver that is bundled with the Displaylink driver package. If you need to use a newer released version from the evdi Github repo and it is not currently present in the Displaylink driver package, you can do so by running:

make github-release

Secure boot on Fedora

To use displaylink-rpm and the evdi kernel module with secure boot enabled on Fedora you need to sign the module with an enrolled Machine Owner Key (MOK).

First create a self signed MOK:

openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out \
MOK.der -nodes -days 36500 -subj "/CN=Displaylink/"

Then register the MOK with secure boot:

sudo mokutil --import MOK.der

Then reboot your Fedora host and follow the instructions to enroll the key.

Now you can sign the evdi module. This must be done for every kernel upgrade:

sudo modinfo -n evdi /lib/modules/5.10.19-200.fc33.x86_64/extra/evdi.ko.xz

sudo unxz $(modinfo -n evdi)

sudo /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./MOK.priv \
  ./MOK.der /lib/modules/$(uname -r)/extra/evdi.ko

sudo xz -f /lib/modules/$(uname -r)/extra/evdi.ko

Now any display, hdmi and/or dvi ports on your docking station should work, and the displaylink-driver.service should run.

Hardware-specific behavior

Dell D6000

When used with the Dell D6000 docking station, DisplayLink 5.1.26 regularly loses communication with attached monitors, causing them to go blank and enter power-saving mode. At the time the monitors blank, the kernel logs two error messages:

kernel: usb <xxx>: Disable of device-initiated U1 failed.
kernel: usb <xxx>: Disable of device-initiated U2 failed.

To work around this issue, disable power management for the audio device by commenting out a line in /etc/pulse/default.pa:

### Automatically suspend sinks/sources that become idle for too long
# load-module module-suspend-on-idle

Development Builds

Generally we want to track the current stable release of the evdi library. However, Fedora kernels are often much newer than those officially supported by that release and it is not uncommon for a new kernel to completely break the build. This can leave you in a situation where you cannot upgrade your kernel without sacrificing your displaylink devices. This is not great if the new kernel has important security or performance fixes.

The evdi developers use the main branch as their main branch for all changes.

To pull the latest code from the main branch and use it to build, do the following:

make main

make github-release

Of course this main branch will also include some experimental and less tested changes that may break things in other unexpected ways. So you should prefer the mainline build if it works, but if it breaks, you have the option of making a main build.

If you are using Fedora Rawhide, you can create a build which will automatically download from the main branch and build by running:

make rawhide

In the past, code in the main branch would be tagged and that version is what would be included in the Displaylink driver package.

Recently, we are seeing newer changes appear in the Displaylink driver package without the evdi library version being changed. This has created some confusion and difficulty when it comes to maintenance updates.

The evdi folks have acknowledged this issue and are working on making the process more transparent.

Contributing

The easiest way to contribute with the package is to fork it and send a pull request in GitHub.

There are two main kind of contributions: either a new upstream version is released or a modification in the packaging is proposed.

There is a variable called RELEASE for packaging purposes. That variable should be set to 1 when contributing a new upstream version release, and incremented in one when adding any other functionality to the specfile for the same upstream version.

New Upstream release

From time to time, DisplayLink will update their driver. We try to do so, but for that we usually rely on pull requests.

We manage three different upstream numbers for versioning:

evdi kernel driver version
DisplayLinkManager daemon and libraries version
Download ID number from DisplayLink (for automatic zip retrieval)

These variables need to be changed in the following places:

Makefile
- DAEMON_VERSION is the DisplayLinkManager version
- VERSION is currently the evdi driver version
- DOWNLOAD_ID is the ?download_id= query parameter in DisplayLink website to download the zip

Also, please update the changelog at the bottom of the displaylink.spec file.

Packaging change

When changing a packaging rule, please increment the RELEASE variable by one in displaylink.spec

displaylink-rpm's People

Contributors

Stargazers

Watchers

displaylink-rpm's Issues

Any interest in adding support for Secure Boot via dkms module signing?

Its pretty easy to get your system to support Secure Boot with dkms modules and the MOK keyring. All you need to do is:

Ensure Secure boot is turned on
Create an appropriate key pair
Add the new key to the MOK keyring
Reboot to install the key
Set up dkms to resign the evdi modules whenever they are rebuilt

The first 4 steps can be easily covered by a bit of documentation (with official references).

The last step requires a configuration file, module signing script, and a bit of advice on how to do this all without defeating the whole purpose of Secure Boot.

I've sketch out a proposed implementation of the last step at

https://github.com/tartansandal/displaylink-rpm/tree/support-for-module-signing

If there is any genuine interest in this, I can do some work on documenting the first 4 steps :-)

And, yes, there is a project to get evdi mainlined into the kernel, so it can be signed by official keys, but I think that may take a fair while. It may require someone to code an open source reference implementation of the DisplayLink userspace service for this to get enough traction.

systemctl enable displaylink.service

Hi,

thanks to this community I got displaylink to work on 4.14.11-300.fc27.x86_64.

Now the following gets an interesting reaction...

sudo systemctl enable displaylink.service
[sudo] password for : 
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.

Any ideas?

Fedora 25 on 4.11.3-200.fc25.x86_64 fails to install or build

When I try to install the source RPM, I get:

  0 root@pulsar:~# rpm -Uvh fedora-25-displaylink-1.3.43-2.src.rpm 
Updating / installing...
   1:displaylink-1.3.43-2             ################################# [100%]
  0 root@pulsar:~/rpmbuild/SPECS# rpmbuild -ba displaylink.spec 
error: File /root/rpmbuild/SOURCES/v%{_version}.tar.gz: No such file or directory

When I try to install the precompiled RPM;

  0 root@pulsar:~# rpm -Uvh fedora-25-displaylink-1.3.43-2.x86_64.rpm 
Preparing...                          ################################# [100%]
Updating / installing...
   1:displaylink-1.3.43-2             ################################# [100%]
warning: %post(displaylink-1.3.43-2.x86_64) scriptlet failed, exit status 10

This was on a freshly rebooted fedora 25 to make sure I was running the latest kernel.

Fedora 28 - RPM fails install

Hi all ,
I have a D1000 Dell adaptor but struggling to get it working running Fedora 28

# lsb_release -a
LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	Fedora
Description:	Fedora release 28 (Twenty Eight)
Release:	28
Codename:	TwentyEight

# uname -a
Linux localhost.localdomain 4.16.3-301.fc28.x86_64 #1 SMP Mon Apr 23 21:59:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I've tried using the latest RPM fedora-28-displaylink-1.5.0.2-2.x86_64.rpm
But it's not installing for me.

# sudo rpm -ivh fedora-28-displaylink-1.5.0.2-2.x86_64.rpm 
Verifying...                          ################################# [100%]
Preparing...                          ################################# [100%]
Updating / installing...
   1:displaylink-1.5.0.2-2            ################################# [100%]
Job for displaylink.service failed because the control process exited with error code.
See "systemctl status displaylink.service" and "journalctl -xe" for details.
warning: %post(displaylink-1.5.0.2-2.x86_64) scriptlet failed, exit status 1


# /sbin/modprobe evdi 
modprobe: FATAL: Module evdi not found in directory /lib/modules/4.16.3-301.fc28.x86_64

Is there any other files which I could give that may help debug ?
Any help would be appreciated

( As a side note I thought it might have something to do with me not having the nvdia drivers installed so I followed the instructions at https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/ -- but it seemingly failed since whenever I boot into that kernel i just get a black screen.... So hopefully I don't need to go into that kernel )

build error drm_mode_object_find missing parameter

to reproduce, try to build evdi on for example fedora 27 (4.15.4-300.fc27.x86_64):

/usr/src/evdi-1.5.0/evdi_connector.c:90:6: error: too few arguments to function ‘drm_mode_object_find’

fix/workaround:

	  drm_mode_object_find(connector->dev, NULL, enc_id,
				 DRM_MODE_OBJECT_ENCODER);

Screen flickering when Displaylink device connected

I'm having an issue in both Fedora 28/29 and Centos 7 where the screen flickers and stutters while the display link is connected. The exact behavior is the cursor will flicker when moving it, or in the case of Centos, cause an artifact to appear as a black square/a square section from another part of the overall display, or the cursor will multiple about 20 times and "re-play" the last .1 second movement for a few seconds.

I have the libva drivers for my intel iris display adapter and am running kernel 4.4 in Centos and 4.19 in Centos 29 even with this issue being a problem since F28 at least.

Functionally, the device is working well with the driver. The artifacts are just annoying.

Fedora 27 (beta) 4.13.5-300.fc27.x86_64

Hello, better early than never -
anyone tried Fedora 27 beta? just upgraded to kernel 4.13.5-300.fc27.x86_64 and experience the usual big black...

libebvdi.so cannot be found

I compiled and installed the latest displaylink driver using this package (I built the RPM myself using the provided sources), but the driver didn't work. My external monitory wasn't found. I then asked about this problem on the displaylink forum and got a very helpful reply. See [1].
Per the reply I modified the spec file and added a line to the %install section:
cp evdi-%{version}/library/libevdi.so $RPM_BUILD_ROOT/usr/libexec/displaylink
With this change, the driver works and finds my external monitor.
(For a complete change, the comment about not copying libevdi.so should also be removed.)

[1] http://www.displaylink.org/forum/showthread.php?p=80215

after install displaylink.service complain that modprobe evdi status=1/FAILURE)

Used the "displaylink-rpm" - zip download - unpack - cd displaylink-rpm-master - run ./ci/fedora.sh no error - excep for the:
Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2017-11-21 14:48:59 CET; 3s ago
Process: 24912 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILURE)

if looking at the "https://github.com/displaylink-rpm/displaylink-rpm" it say:
The package includes the Open Source evdi library.

any suggestions

thanks in advance

John

DisplayLink Display doesn't refresh

I'm having an issue with the Disaplylink devices not updating the screen when things change. For instance, on the laptop screen I am typing this message now, however on the screens connected to the DisplayLink device, it shows the original image of the screen the last time I restarted the DisplaylinkManager.

Device Info:
Dell XPS 13 (9360)
Dell D3100 DisplayLink Docking Station
Fedora 25

$ uname -r 4.10.6-200.fc25.x86_64

$ sudo modprobe evdi $

`$ sudo systemctl status displaylink
● displaylink.service - DisplayLink Manager Service
Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled)
Active: active (running) since Mon 2017-04-03 12:03:10 CDT; 6min ago
Process: 12753 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)
Main PID: 12755 (DisplayLinkMana)
Tasks: 43 (limit: 4915)
CGroup: /system.slice/displaylink.service
└─12755 /usr/libexec/displaylink/DisplayLinkManager

Apr 03 12:03:10 systemd[1]: Starting DisplayLink Manager Service...
Apr 03 12:03:10 systemd[1]: Started DisplayLink Manager Service.`

Everything was installed using the git source and running make inside the directory. I did have to perform the following steps before I could get the displaylink manager to run:

$ cd /usr/src/evdi-1.3.43/ && sudo make
$ sudo insmod ./evdi.ko
$ sudo dkms install evdi/1.3.43

I can see the mouse movement on the DL attached screens, however the browser and workspace switcher does not update to match what is currently on the laptop screen.

An example is attached showing the disparity between laptop screen and DL attached screen.

I'm guessing this is a conflict or something with the laptop's display driver and the DL driver? I'm not really sure whats going on here to cause this issue.

displaylink.service cant enable

[root@fedora-x1]# systemctl enable displaylink.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:

A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
In case of template units, the unit is meant to be enabled with some
instance name specified.

Can anyone help me with this?

Missing BuildRequires

It seems a line
BuildRequires: libdrm-devel
is needed in the spec file. Without it, I can't build the RPM using mock, with it, I can.

Building and Installing displaylink in RHEL7.3 fails with dependecy-issue Kernel > 4.7

Hi, I was trying to install the generated RPM from source on RHEL-7.3. But it is failing due to missing dependecies. Is there anything I can

# cat /etc/redhat-release
Red Hat Enterprise Linux Workstation release 7.3 (Maipo)

# uname -a
Linux rhel73.example.com 3.10.0-514.21.2.el7.x86_64 #1 SMP Sun May 28 17:08:21 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux

# sudo yum localinstall x86_64/displaylink-1.4.1-5.x86_64.rpm                                                                                                                                                                                                                                                                                                                                                                                                                 
Loaded plugins: changelog, fs-snapshot, priorities, product-id, refresh-packagekit, rhnplugin, rpm-warm-cache, search-disabled-repos, subscription-manager, verify, versionlock
There was an error communicating with RHN.
RHN channel support will be disabled.
Error communicating with server. The message was:
Unable to connect to the host and port specified
Repository google-chrome is listed more than once in the configuration
Repository google-talkplugin is listed more than once in the configuration
Examining x86_64/displaylink-1.4.1-5.x86_64.rpm: displaylink-1.4.1-5.x86_64
Marking x86_64/displaylink-1.4.1-5.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package displaylink.x86_64 0:1.4.1-5 will be installed
--> Processing Dependency: kernel > 4.7 for package: displaylink-1.4.1-5.x86_64
--> Processing Dependency: kernel-devel > 4.7 for package: displaylink-1.4.1-5.x86_64
--> Processing Dependency: dkms for package: displaylink-1.4.1-5.x86_64
--> Processing Dependency: libstdc++.so.6(CXXABI_1.3.8)(64bit) for package: displaylink-1.4.1-5.x86_64
--> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.20)(64bit) for package: displaylink-1.4.1-5.x86_64
--> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.21)(64bit) for package: displaylink-1.4.1-5.x86_64
--> Finished Dependency Resolution
Error: Package: displaylink-1.4.1-5.x86_64 (/displaylink-1.4.1-5.x86_64)
           Requires: libstdc++.so.6(GLIBCXX_3.4.20)(64bit)
Error: Package: displaylink-1.4.1-5.x86_64 (/displaylink-1.4.1-5.x86_64)
           Requires: dkms
Error: Package: displaylink-1.4.1-5.x86_64 (/displaylink-1.4.1-5.x86_64)
           Requires: libstdc++.so.6(GLIBCXX_3.4.21)(64bit)
Error: Package: displaylink-1.4.1-5.x86_64 (/displaylink-1.4.1-5.x86_64)
           Requires: libstdc++.so.6(CXXABI_1.3.8)(64bit)
Error: Package: displaylink-1.4.1-5.x86_64 (/displaylink-1.4.1-5.x86_64)
           Requires: kernel-devel > 4.7
           Installed: kernel-devel-3.10.0-514.16.1.el7.x86_64 (@production-rhel-x86_64-workstation-7.2)
               kernel-devel = 3.10.0-514.16.1.el7
           Installed: kernel-devel-3.10.0-514.21.1.el7.x86_64 (@production-rhel-x86_64-workstation-7.2)
               kernel-devel = 3.10.0-514.21.1.el7
           Installed: kernel-devel-3.10.0-514.21.2.el7.x86_64 (@production-rhel-x86_64-workstation-7.2)
               kernel-devel = 3.10.0-514.21.2.el7
Error: Package: displaylink-1.4.1-5.x86_64 (/displaylink-1.4.1-5.x86_64)
           Requires: kernel > 4.7
           Installed: kernel-3.10.0-514.16.1.el7.x86_64 (@production-rhel-x86_64-workstation-7.2)
               kernel = 3.10.0-514.16.1.el7
           Installed: kernel-3.10.0-514.21.1.el7.x86_64 (@production-rhel-x86_64-workstation-7.2)
               kernel = 3.10.0-514.21.1.el7
           Installed: kernel-3.10.0-514.21.2.el7.x86_64 (@production-rhel-x86_64-workstation-7.2)
               kernel = 3.10.0-514.21.2.el7
 You could try using --skip-broken to work around the problem

Pre-release a non-official RPM based on mintel's fixes for Kernel 4.15.3

Do you think it would be interesting to "pre-release" a version against mintel/evdi @ aefc9ef while we don't hear from anybody at evdi?

If somebody can prepare a tag against mintel/evdi as a PR it would be great, as I'd rather have it built by Travis transparently than having to trust a binary uploaded by any of us.

This would "unblock" the state of #55 for the time being.

Xorg crash on Rawhide with v1.5.0.2

I have a ThinkPad USB 3.0 Pro dock. When I connect a Dell U3011 monitor (DVI) I can configure it in the GNOME Displays panel but when I switch it to ON in the panel, I get an Xorg crash.

I get a similar crash when I power on the dock with a Samsung S27F350 connected (VGA->DVI or HDMI->DisplayPort), or if I plug the Samsung in to an already-powered dock.

I'm not sure what's good diagnostic information, but journalctl shows these:
Jul 27 14:24:57 himon systemd-coredump[2940]: Process 30576 (Xorg) of user 1000 dumped core.
Jul 27 14:24:59 himon audit[3007]: ANOM_ABEND auid=4294967295 uid=42 gid=42 ses=4294967295 subj=system_u:system_r:xserver_t:s0-s0:c0.c1023 pid=3007 comm="Xorg" exe="/usr/libexec/Xorg" sig=11 res=1
...and...
Jul 27 14:25:03 himon /usr/libexec/gdm-x-session[3125]: gbm: Last dlopen error: /usr/lib64/dri/evdi_dri.so: cannot open shared object file: No such file or directory

why I installed it successfully? but my virtualbox fedora26 can't boot to screen?

before I install it,
I install kernel-headers-${uname -r} kernel-devel-${uname -r}
the I installed it successfully and without any mistake
type systemctl status displaylink
it show Running
but the virtual machine can't boot to screnn to login ,Is it normal ? should I ingore this?
I'm try to install to my pc, I'm afraid of this happen to my real pc

env is fedora26 kernel 4.11.8-300.fc26.x86_64 26

issue with display ports on docking

hi running the following kernel and distro - 4.14.16-300.fc27.x86_64
have a dell xps 13,dell d6000 docking
installed the following rpm
fedora-26-displaylink-1.5.0-1.x86_64.rpm

for some reason the driver only works with hdmi ports on the docking but not the display ports

kindly assist

Asus Dock Outputs Mirrored Only

I've been using an Asus USB 3.0 HZ-1 Docking Station for some time. The dock has DVI, VGA, and HDMI outputs, of which you can use two at a time. I have the dock connected to two external monitors on the VGA and DVI outputs.

Currently, the external displays show the same image. Previously, I was able to use them as independent displays, in the same configuration.

I'm not sure when this stopped working, as I've had to travel for work, and I've been through several kernel upgrades since. The oldest kernel currently installed is 4.13.4-200.fc26.x86_64, which exhibited the same behaviour.

Xrandr shows only one modesetting interface; it used to see two.

$ xrandr --listproviders 
Providers: number : 3
Provider 0: id: 0x8f cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 5 associated providers: 2 name:Intel
Provider 1: id: 0x17e cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 1 name:modesetting
Provider 2: id: 0x62 cap: 0x7, Source Output, Sink Output, Source Offload crtcs: 2 outputs: 1 associated providers: 1 name:nouveau

I used to get two outputs starting with DVI-I-; now there is only one.

$ xrandr | awk '/connect/'
LVDS1 connected primary 1366x768+0+282 (normal left inverted right x axis y axis) 340mm x 190mm
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
DVI-I-2-1 connected 1680x1050+1366+0 (normal left inverted right x axis y axis) 474mm x 296mm
VGA-1-2 connected (normal left inverted right x axis y axis)

displaylink.service starts up on boot

$ systemctl status displaylink
● displaylink.service - DisplayLink Manager Service
   Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled)
   Active: active (running) since Sun 2017-10-29 07:27:33 EDT; 4min 28s ago
  Process: 1338 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)
 Main PID: 1345 (DisplayLinkMana)
    Tasks: 26 (limit: 4915)
   CGroup: /system.slice/displaylink.service
           └─1345 /usr/libexec/displaylink/DisplayLinkManager

I don't see any displaylink or evdi errors in journalctl -xe.

fedora 29, kernel 4.19.13 - screen stays black

Hi,

I just jumped from f28 to f29 (4.19.13-300.fc29.x86_64) and now, my screen stays black. (Was working fine with f28)

I both installed "rpm -ivh fedora-29-displaylink-1.5.1-1.src.rpm fedora-29-displaylink-1.5.1-1.x86_64.rpm".

$ systemctl status displaylink.service
● displaylink.service - DisplayLink Manager Service
   Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled)
   Active: active (running) since Wed 2019-01-16 11:12:09 CET; 25s ago
 Main PID: 19679 (DisplayLinkMana)
    Tasks: 33 (limit: 4915)
   Memory: 12.7M
   CGroup: /system.slice/displaylink.service
           └─19679 /usr/libexec/displaylink/DisplayLinkManager

Jan 16 11:12:09 stefan.dalibo.local systemd[1]: Starting DisplayLink Manager Service...
Jan 16 11:12:09 stefan.dalibo.local systemd[1]: Started DisplayLink Manager Service.

From journalctl :

kernel: evdi: [D] evdi_painter_connect:574 (dev=1) Connected with 00000000aa539aae
kernel: evdi: [D] evdi_detect:85 (dev=1) Painter is connected
kernel: evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 3
kernel: evdi: [D] evdi_detect:85 (dev=1) Painter is connected
kernel: evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
kernel: evdi: [D] evdi_detect:85 (dev=1) Painter is connected
kernel: evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
kernel: evdi: [D] evdi_painter_mode_changed_notify:507 (dev=1) Notifying mode changed: 1920x1080@60; bpp 32; 
kernel: evdi: [D] evdi_painter_mode_changed_notify:508 pixel format 875713112
kernel: evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 0
kernel: evdi: [D] evdi_painter_dpms_notify:470 (dev=1) Notifying dpms mode: 0

What can I check now?

Many thanks in advance,
Kind regards

Fedora 26 support is currently broken

First, with the latest F26 4.12 kernel, the module does not build anymore.

A fix was already added in the upstream DisplayLink/evdi repo: DisplayLink/evdi@6c689d6

But even when applying this patch, I have other errors with evdi that prevent it from working (it was fine yesterday but is broken with latest package upgrades).

Here is a log:

Aug 16 09:57:53 CH900635.keymile.net kernel: evdi: [D] add_store:195 Increasing device count to 1
Aug 16 09:57:53 CH900635.keymile.net kernel: evdi: [D] evdi_crtc_init:310 drm_crtc_init: 0
Aug 16 09:57:53 CH900635.keymile.net kernel: evdi: [W] evdi_painter_crtc_state_notify:362 Painter does not exist!
Aug 16 09:57:53 CH900635.keymile.net kernel: evdi: [D] evdi_detect:78 Painter is disconnected
Aug 16 09:57:53 CH900635.keymile.net kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Aug 16 09:57:53 CH900635.keymile.net kernel: evdi evdi.0: fb1: evdidrmfb frame buffer device
Aug 16 09:57:53 CH900635.keymile.net kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
Aug 16 09:57:53 CH900635.keymile.net kernel: [drm] No driver support for vblank timestamp query.
Aug 16 09:57:53 CH900635.keymile.net kernel: [drm] evdi: evdi_stats_init
Aug 16 09:57:53 CH900635.keymile.net kernel: [drm] Initialized evdi 1.4.1 20170417 for evdi.0 on minor 1
Aug 16 09:57:53 CH900635.keymile.net kernel: evdi: [D] evdi_detect:78 Painter is disconnected
Aug 16 09:57:53 CH900635.keymile.net kernel: evdi: [W] evdi_painter_disconnect:471 (dev=0) An unknown connection to ffff9d8ac4105200 tries to close us
Aug 16 09:57:53 CH900635.keymile.net kernel: evdi: [W] evdi_painter_disconnect:472 - ignoring

Cannot Insert evdi: Operation not permitted

Good Morning, I tried to install from the Travis build on to Fedora 28_64.
This feels related to #63 , but I'm not smart enough to know how.

EDIT2: Using X11 rather than Wayland, while having Secure boot disabled did the trick. This should probably be added to the docs? Is there an easier way and I got lucky here?

Any thoughts or more info I can provide?

Result of journalctl -f -n 0 is:

Aug 11 12:27:55 magritte systemd[1]: dlm.service: Service hold-off time over, scheduling restart.
Aug 11 12:27:55 magritte systemd[1]: dlm.service: Scheduled restart job, restart counter is at 310.
Aug 11 12:27:55 magritte systemd[1]: Stopped DisplayLink Manager Service.
Aug 11 12:27:55 magritte audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dlm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 11 12:27:55 magritte audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dlm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 11 12:27:55 magritte systemd[1]: Starting DisplayLink Manager Service...
Aug 11 12:27:55 magritte sh[25641]: modprobe: ERROR: could not insert 'evdi': Operation not permitted
Aug 11 12:27:55 magritte sh[25641]: Module evdi/4.2.29 already installed on kernel 4.17.12-200.fc28.x86_64/x86_64
Aug 11 12:27:55 magritte sh[25641]: modprobe: ERROR: could not insert 'evdi': Operation not permitted
Aug 11 12:27:55 magritte systemd[1]: dlm.service: Control process exited, code=exited status=1
Aug 11 12:27:55 magritte systemd[1]: dlm.service: Failed with result 'exit-code'.
Aug 11 12:27:55 magritte systemd[1]: Failed to start DisplayLink Manager Service.

output of cat /var/log/displaylink/displaylink.log is

Creating symlink /var/lib/dkms/evdi/1.5.0.2/source ->
                 /usr/src/evdi-1.5.0.2

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area....(bad exit status: 2)
make -j4 KERNELRELEASE=4.17.12-200.fc28.x86_64 all INCLUDEDIR=/lib/modules/4.17.12-200.fc28.x86_64/build/include KVERSION=4.17.12-200.fc28.x86_64 DKMS_BUILD=1.....
cleaning build area....(bad exit status: 2)

DKMS: build completed.

evdi.ko.xz:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.17.12-200.fc28.x86_64/extra/
Adding any weak-modules

depmod.....

DKMS: install completed.

evdi.ko.xz:
Running module version sanity check.
 - Original module
   - This kernel never originally had a module by this name
 - Installation
   - Installing to /lib/modules/4.17.12-200.fc28.x86_64/extra/
Adding any weak-modules

depmod.....

DKMS: install completed.

EDIT:: I disabled Secureboot, and now when I check journalctl, I get this:

Aug 11 12:41:49 magritte kernel: usb 1-1: New USB device found, idVendor=0bda, idProduct=5412, bcdDevice= 0.00
Aug 11 12:41:49 magritte kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 11 12:41:49 magritte kernel: usb 1-1: Product: 4-Port USB 2.0 Hub
Aug 11 12:41:49 magritte kernel: usb 1-1: Manufacturer: Generic
Aug 11 12:41:49 magritte kernel: hub 1-1:1.0: USB hub found
Aug 11 12:41:49 magritte kernel: hub 1-1:1.0: 2 ports detected
Aug 11 12:41:49 magritte upowerd[1886]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0
Aug 11 12:41:49 magritte upowerd[1886]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
Aug 11 12:41:50 magritte kernel: usb 1-1.1: new full-speed USB device number 17 using xhci_hcd
Aug 11 12:41:50 magritte kernel: usb 1-1.1: not running at top speed; connect to a high speed hub
Aug 11 12:41:50 magritte kernel: usb 1-1.1: New USB device found, idVendor=0bda, idProduct=5400, bcdDevice= 1.00
Aug 11 12:41:50 magritte kernel: usb 1-1.1: New USB device strings: Mfr=17, Product=18, SerialNumber=19
Aug 11 12:41:50 magritte kernel: usb 1-1.1: Product: BillBoard Device
Aug 11 12:41:50 magritte kernel: usb 1-1.1: Manufacturer: Realtek
Aug 11 12:41:50 magritte kernel: usb 1-1.1: SerialNumber: 123456789ABCDEFGH
Aug 11 12:41:50 magritte upowerd[1886]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1
Aug 11 12:41:55 magritte kernel: usb 1-1.2: new high-speed USB device number 18 using xhci_hcd
Aug 11 12:41:55 magritte kernel: usb 1-1.2: New USB device found, idVendor=17e9, idProduct=4300, bcdDevice=72.51
Aug 11 12:41:55 magritte kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 11 12:41:55 magritte kernel: usb 1-1.2: Product: MB16AC
Aug 11 12:41:55 magritte kernel: usb 1-1.2: Manufacturer: DisplayLink
Aug 11 12:41:55 magritte kernel: usb 1-1.2: SerialNumber: 82173224058292M0628
Aug 11 12:41:55 magritte mtp-probe[4578]: checking bus 1, device 18: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.2"
Aug 11 12:41:55 magritte mtp-probe[4578]: bus: 1, device: 18 was not an MTP device
Aug 11 12:41:55 magritte fwupd[3104]: failed to parse interface data for 17e9:4300: interface found, but not the correct length for functional data: 25 bytes: 09 21 01 c8 00 00 40 01 01 10 40 09 05 12 08 08 0f 45 6c 6c 61 44 6f 63 6b
Aug 11 12:41:55 magritte upowerd[1886]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.2
Aug 11 12:41:55 magritte upowerd[1886]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.2/1-1.2:1.0
Aug 11 12:41:55 magritte kernel: evdi: [D] evdi_painter_connect:573 (dev=2) Connected with 00000000ac088fea
Aug 11 12:41:55 magritte kernel: evdi: [D] evdi_detect:75 (dev=2) Painter is connected
Aug 11 12:41:55 magritte kernel: evdi: [D] evdi_painter_crtc_state_notify:482 (dev=2) Notifying crtc state: 3

"kernel-mt" in displaylink.spec

Shouldn't this be "kernel-ml" or better "kernel-lt" in %global in displaylink.spec?

fedora 25 wayland - Failed to start DisplayLink Manager Service.

$ uname -a
Linux 4.9.3-200.fc25.x86_64 #1 GNU/Linux

RPM "fedora-25-displaylink-1.2.64-1.x86_64.rpm" and "fedora-25-displaylink-1.2.64-1.src.rpm" downloaded from
https://github.com/displaylink-rpm/displaylink-rpm/releases

"fedora-25-displaylink-1.2.64-1.x86_64.rpm" cant be installed becauseof "10" return code, without any extra info
"fedora-25-displaylink-1.2.64-1.src.rpm" installed successfully

$ systemctl status displaylink.service 
● displaylink.service - DisplayLink Manager Service
   Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since czw 2017-01-19 20:49:10 CET; 1s ago
  Process: 5409 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILURE)

sty 19 20:49:10 kastin-laptop systemd[1]: Failed to start DisplayLink Manager Service.
sty 19 20:49:10 kastin-laptop systemd[1]: displaylink.service: Unit entered failed state.
sty 19 20:49:10 kastin-laptop systemd[1]: displaylink.service: Failed with result 'exit-code'.

$ systemctl restart displaylink.service 
Job for displaylink.service failed because the control process exited with error code.
See "systemctl status displaylink.service" and "journalctl -xe" for details.

$ journalctl -xe
sty 19 20:51:01 kastin-laptop modprobe[5574]: modprobe: FATAL: Module evdi not found in directory /lib/modules/4.9.3-200.fc25.x86_64
sty 19 20:51:01 kastin-laptop systemd[1]: displaylink.service: Control process exited, code=exited status=1
sty 19 20:51:01 kastin-laptop systemd[1]: Failed to start DisplayLink Manager Service.

general fix for "Module evdi not found in directory" error is

$ sudo /sbin/dkms install evdi/1.2.64

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...(bad exit status: 2)
make -j4 KERNELRELEASE=4.9.3-200.fc25.x86_64 all INCLUDEDIR=/lib/modules/4.9.3-200.fc25.x86_64/build/include KVERSION=4.9.3-200.fc25.x86_64 DKMS_BUILD=1...(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.9.3-200.fc25.x86_64 (x86_64)
Consult /var/lib/dkms/evdi/1.2.64/build/make.log for more information.

after dig a bit deeper (cat /var/lib/dkms/evdi/1.2.64/build/make.log)

echo >&2;                                                       \
echo >&2 "  ERROR: Kernel configuration is invalid.";           \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";      \
echo >&2 ;

not sure if "displaylink-rpm" issue, but just to notice..

What are the steps after install?

I am running Fedora 25 and I've found this, I have installed the latest package by running sudo dnf install <package>.rpm my device is a TU3-DS2 and I have connected one monitor to the dock but I can't see anything on the monitor, do I need anything else rather than install the driver? A friend of mine has the same device working properly in Ubuntu so I don't know what's happening here

RHEL7/Centos 7 support

Running on a Lenovo X1 Carbon (gen 1) with Lenovo Thinkpad USB 3 dock

$ sudo rpm -i centos-7-displaylink-1.2.64-1.x86_64.rpm
[sudo] password for xxx:
error: Failed dependencies:
libstdc++.so.6(CXXABI_1.3.8)(64bit) is needed by displaylink-1.2.64-1.x86_64
libstdc++.so.6(GLIBCXX_3.4.20)(64bit) is needed by displaylink-1.2.64-1.x86_64
libstdc++.so.6(GLIBCXX_3.4.21)(64bit) is needed by displaylink-1.2.64-1.x86_64

I am running CentOS 7.3 with kernel updated to 4.9
$ cat /etc/centos-release
CentOS Linux release 7.3.1611 (Core)
$ uname -r
4.9.0-1.el7.elrepo.x86_64

$ yum list | grep libstdc++
compat-libstdc++-33.i686 3.2.3-72.el7 @base
libstdc++.i686 4.8.5-11.el7 @base
libstdc++.x86_64 4.8.5-11.el7 @anaconda
libstdc++-devel.x86_64 4.8.5-11.el7 @base
libstdc++-static.x86_64 4.8.5-11.el7 @base
compat-libstdc++-33.x86_64 3.2.3-72.el7 base
libstdc++-devel.i686 4.8.5-11.el7 base
libstdc++-docs.x86_64 4.8.5-11.el7 base
libstdc++-static.i686 4.8.5-11.el7 base

Package evdi separately

Since EVDI is supposed to be a reusable kernel module it seems like it would make sense to package it separately. Would you accept a pull request to do this?

Fedora 27 RPM

Now that Fedora 27 is released it would be nice to have a RPM for it.
I am too scared to update my machine as displaylink in general is touchy.

External monitor on DisplayLink (DVI) not working

Hi,

I have a MacBook Pro with Fedora 27 (4.15.14-300.fc27.x86_64). I tried installing the latest release RPM and tried building the rawhide one. Both result in the same situation where the laptop screen briefly turns black when plugging in the USB cable but the external monitor doesn't turn on.

It's a Fujitsu DisplayLink 3.0 Hub. To add: USB and Ethernet does work on the device, it's just the DVI monitor that isn't recognized.

Please send help.

Issue connecting USB screen Lenovo LT1421

Hello,
many thanks for making the RPMs available. I managed to compile this from source but unfortunately have the same result as with the release RPMs:
as soon as I connect the USB screen, it shows an image, freezes, turns black and keeps re-connecting

I'm running on a Dell XPS 13 with kernel 4.8.4-200.fc24.x86_64

dmesg | grep "usb 1-1" returns

[18493.675392] evdi: [D] evdi_detect:72 Painter is disconnected
[18493.675403] evdi: [D] evdi_detect:72 Painter is disconnected
[18494.019604] usb 1-2: USB disconnect, device number 11
[18494.310695] usb 1-2: new high-speed USB device number 12 using xhci_hcd
[18494.466722] usb 1-2: Device not responding to setup address.
[18494.672663] usb 1-2: Device not responding to setup address.
[18494.880645] usb 1-2: device not accepting address 12, error -71
[18532.614273] usb 1-2: new high-speed USB device number 14 using xhci_hcd
[18532.770295] usb 1-2: device descriptor read/64, error -32
[18533.045073] usb 1-2: New USB device found, idVendor=17e9, idProduct=03e0
[18533.045075] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18533.045077] usb 1-2: Product: Lenovo LT1421 wide
[18533.045078] usb 1-2: Manufacturer: DisplayLink
[18533.045078] usb 1-2: SerialNumber: 6V9CATN2
[18533.126862] evdi: [W] evdi_painter_disconnect:478 (dev=-1) An unknown connection to ffff8a9116073000 tries to close us
[18533.126863] evdi: [W] evdi_painter_disconnect:479  - ignoring
[18533.150553] evdi: [W] evdi_painter_disconnect:478 (dev=0) An unknown connection to ffff8a9116073000 tries to close us
[18533.150555] evdi: [W] evdi_painter_disconnect:479  - ignoring
[18533.418368] evdi: [D] evdi_painter_connect:448 (dev=-1) Connected with           (null)
[18533.418370] evdi: [D] evdi_detect:69 (dev=1) Painter is connected
[18533.418399] evdi: [D] evdi_painter_crtc_state_notify:374 (dev=1) Notifying crtc state: 3
[18533.420757] evdi: [D] evdi_detect:72 Painter is disconnected
[18533.420805] evdi: [D] evdi_detect:69 (dev=1) Painter is connected
[18533.420808] evdi: [D] evdi_painter_get_edid_copy:192 (dev=1) 00 ff ff
[18533.525273] evdi: [D] evdi_painter_mode_changed_notify:391 (dev=1) Notifying mode changed: 1366x768@60; bpp 32; 
[18533.525274] evdi: [D] evdi_painter_mode_changed_notify:392 pixel format 875713112
[18533.525281] evdi: [D] evdi_painter_crtc_state_notify:374 (dev=1) Notifying crtc state: 0
[18533.525283] evdi: [D] evdi_painter_dpms_notify:361 (dev=1) Notifying dpms mode: 0
[18533.726488] evdi: [D] evdi_detect:72 Painter is disconnected
[18533.726501] evdi: [D] evdi_detect:69 (dev=1) Painter is connected
[18533.726503] evdi: [D] evdi_painter_get_edid_copy:192 (dev=1) 00 ff ff
[18534.103659] traps: SourceEngine_00[26798] general protection ip:4d57f4 sp:7f15c57fa5b0 error:0 in DisplayLinkManager[400000+66d000]
[18534.302793] evdi: [D] evdi_painter_disconnect:499 (dev=1) Disconnected from ffff8a9172f92200
[18534.302795] evdi: [D] evdi_detect:72 Painter is disconnected
[18534.305741] evdi: [D] evdi_detect:72 Painter is disconnected
[18534.305798] evdi: [D] evdi_detect:72 Painter is disconnected
[18534.329847] evdi: [D] evdi_painter_crtc_state_notify:374 (dev=-1) Notifying crtc state: 3
[18534.329849] evdi: [W] evdi_painter_send_crtc_state:266 Painter is not connected!
[18534.424560] evdi: [D] evdi_detect:72 Painter is disconnected
[18534.424574] evdi: [D] evdi_detect:72 Painter is disconnected

No providers in Fedora 28 after apparent successful install.

Hello,
I have been trying to get this working for a while now but I am stuck.
Here is my process. I downloaded the source and extracted it. I ran make and after I installed all the dependencies, It completed successfully. I have .rpm files in i386 and the x86_64 directories. I ran dnf install ./displaylink-1.5.0.2-2.x86_64.rpm. Then after it said it installed correctly but actually didn't due to
more dependencies that weren't required for rpm-build and libdrm that were not required by the rpm, it said it installed correctly and appears to be so.

`$ systemctl status displaylink
● displaylink.service - DisplayLink Manager Service
Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor >
Active: active (running) since Fri 2018-06-29 09:46:43 MDT; 40min ago
Process: 1008 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)
Main PID: 1020 (DisplayLinkMana)
Tasks: 11 (limit: 4620)
Memory: 12.2M
CGroup: /system.slice/displaylink.service
└─1020 /usr/libexec/displaylink/DisplayLinkManager

Jun 29 09:46:43 localhost systemd[1]: Starting DisplayLink Manager Service...
Jun 29 09:46:43 localhost systemd[1]: Started DisplayLink Manager Service.
lsmod | grep evdi
evdi 61440 0
drm_kms_helper 196608 2 evdi,i915
drm 458752 6 drm_kms_helper,evdi,i915
[shane@localhost x86_64]$
`

But when I have my device plugged in, there is only the original modesetting device.

[shane@localhost x86_64]$ xrandr --listproviders Providers: number : 1 Provider 0: id: 0x42 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 1 associated providers: 0 name:modesetting [shane@localhost x86_64]$
The device is present but has no drivers associated with it. (usb-devices output)

T: Bus=07 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0 D: Ver= 3.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs= 1 P: Vendor=17e9 ProdID=6000 Rev=30.00 S: Manufacturer=DisplayLink S: Product=USB 3.0 Dual 4K HDMI adapter S: SerialNumber=GWCD00160902353 C: #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=504mA I: If#=0x0 Alt= 0 #EPs= 6 Cls=ff(vend.) Sub=00 Prot=03 Driver=(none) I: If#=0x1 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none) I: If#=0x2 Alt= 0 #EPs= 1 Cls=01(audio) Sub=01 Prot=20 Driver=snd-usb-audio I: If#=0x3 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=20 Driver=snd-usb-audio I: If#=0x4 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=20 Driver=snd-usb-audio [shane@localhost x86_64]$
Here is my /etc/X11/xorg.conf.d/20-displaylink.conf. The settings are per the recommendations I found on the displaylink site.
`[shane@localhost x86_64]$ cat /etc/X11/xorg.conf.d/20-displaylink.conf
Section "Device"
Identifier "intel"
Driver "modesetting"
Option "kmsdev" "/dev/dri/card0"
Option "PageFlip" "off"
Option "SWCursor" "on"
Option "ShadowFB" "true"
EndSection

Section "Device"
Identifier "DisplayLink"
Driver "modesetting"
Option "PageFlip" "false"
EndSection

Section "Device"
Identifier "USB3"
BusID "USB"
Driver "modesetting"
Option "kmsdev" "/dev/dri/card1"
Option "PageFlip" "off"
Option "SWCursor" "on"
Option "ShadowFB" "true"
EndSection

Section "Device"
Identifier "USB3"
BusID "USB"
Driver "modesetting"
Option "kmsdev" "/dev/dri/card2"
Option "PageFlip" "off"
Option "SWCursor" "on"
Option "ShadowFB" "true"
EndSection

Section "Device"
Identifier "USB3"
BusID "USB"
Driver "modesetting"
Option "kmsdev" "/dev/dri/card3"
Option "PageFlip" "off"
Option "SWCursor" "on"
Option "ShadowFB" "true"
EndSection
`
Please let me know what I am missing on this. I would really like to get this working.

Thank you in advance for your help.

Shane

Current evdi fails to build on kernel >= 4.7

The currently released evdi version fails on kernels >=4.7 due to the drm interface having changed.

Updating to master evdi should solve the issue (see DisplayLink/evdi#32) while DisplayLink does not release a packaged update.

Steps to reproduce:

Update to kernel >=4.7 (in my case, 4.7.2-101.fc23)
dkms install evdi/1.1.65

[EDIT: If the package is not yet installed, its installation will fail with non-fatal POSTIN due to the very dkms install operation as present in the spec file]

Expected result:
evdi gets installed

Observed output:
dkms fails with:

DKMS make.log for evdi-1.1.65 for kernel 4.7.2-101.fc23.x86_64 (x86_64)
lun sep  5 15:42:51 CEST 2016
make KBUILD_VERBOSE=1 SUBDIRS=/var/lib/dkms/evdi/1.1.65/build SRCROOT=/var/lib/dkms/evdi/1.1.65/build CONFIG_MODULE_SIG= -C /lib/modules/4.7.2-101.fc23.x86_64/build modules
make[1]: Entering directory '/usr/src/kernels/4.7.2-101.fc23.x86_64'
[...]
[unimportant lines]
[...]
  gcc -Wp,-MD,/var/lib/dkms/evdi/1.1.65/build/.evdi_stats.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/5.3.1/include -I./arch/x86/include -Iarch/x86/include/generated/uapi -Iarch/x86/include/generated  -Iinclude -I./arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fvar-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -DCC_HAVE_ASM_GOTO -Iinclude/drm  -DMODULE  -DKBUILD_BASENAME='"evdi_stats"'  -DKBUILD_MODNAME='"evdi"' -c -o /var/lib/dkms/evdi/1.1.65/build/evdi_stats.o /var/lib/dkms/evdi/1.1.65/build/evdi_stats.c
/var/lib/dkms/evdi/1.1.65/build/evdi_main.c: In function ‘evdi_driver_unload’:
/var/lib/dkms/evdi/1.1.65/build/evdi_main.c:82:2: error: implicit declaration of function ‘drm_connector_unplug_all’ [-Werror=implicit-function-declaration]
  drm_connector_unplug_all(dev);
  ^
/var/lib/dkms/evdi/1.1.65/build/evdi_fb.c: In function ‘evdi_fb_user_fb_create’:
/var/lib/dkms/evdi/1.1.65/build/evdi_fb.c:503:30: error: passing argument 1 of ‘drm_gem_object_lookup’ from incompatible pointer type [-Werror=incompatible-pointer-types]
  obj = drm_gem_object_lookup(dev, file, mode_cmd->handles[0]);
                              ^
In file included from /var/lib/dkms/evdi/1.1.65/build/evdi_drv.h:23:0,
                 from /var/lib/dkms/evdi/1.1.65/build/evdi_fb.c:22:
include/drm/drm_gem.h:241:24: note: expected ‘struct drm_file *’ but argument is of type ‘struct drm_device *’
 struct drm_gem_object *drm_gem_object_lookup(struct drm_file *filp, u32 handle);
                        ^
/var/lib/dkms/evdi/1.1.65/build/evdi_fb.c:503:35: warning: passing argument 2 of ‘drm_gem_object_lookup’ makes integer from pointer without a cast [-Wint-conversion]
  obj = drm_gem_object_lookup(dev, file, mode_cmd->handles[0]);
                                   ^
In file included from /var/lib/dkms/evdi/1.1.65/build/evdi_drv.h:23:0,
                 from /var/lib/dkms/evdi/1.1.65/build/evdi_fb.c:22:
include/drm/drm_gem.h:241:24: note: expected ‘u32 {aka unsigned int}’ but argument is of type ‘struct drm_file *’
 struct drm_gem_object *drm_gem_object_lookup(struct drm_file *filp, u32 handle);
                        ^
/var/lib/dkms/evdi/1.1.65/build/evdi_fb.c:503:8: error: too many arguments to function ‘drm_gem_object_lookup’
  obj = drm_gem_object_lookup(dev, file, mode_cmd->handles[0]);
        ^
In file included from /var/lib/dkms/evdi/1.1.65/build/evdi_drv.h:23:0,
                 from /var/lib/dkms/evdi/1.1.65/build/evdi_fb.c:22:
include/drm/drm_gem.h:241:24: note: declared here
 struct drm_gem_object *drm_gem_object_lookup(struct drm_file *filp, u32 handle);
                        ^
cc1: some warnings being treated as errors
scripts/Makefile.build:289: recipe for target '/var/lib/dkms/evdi/1.1.65/build/evdi_fb.o' failed
make[2]: *** [/var/lib/dkms/evdi/1.1.65/build/evdi_fb.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/var/lib/dkms/evdi/1.1.65/build/evdi_gem.c: In function ‘evdi_gem_mmap’:
/var/lib/dkms/evdi/1.1.65/build/evdi_gem.c:211:30: error: passing argument 1 of ‘drm_gem_object_lookup’ from incompatible pointer type [-Werror=incompatible-pointer-types]
  obj = drm_gem_object_lookup(dev, file, handle);
                              ^
In file included from /var/lib/dkms/evdi/1.1.65/build/evdi_drv.h:23:0,
                 from /var/lib/dkms/evdi/1.1.65/build/evdi_gem.c:11:
include/drm/drm_gem.h:241:24: note: expected ‘struct drm_file *’ but argument is of type ‘struct drm_device *’
 struct drm_gem_object *drm_gem_object_lookup(struct drm_file *filp, u32 handle);
                        ^
/var/lib/dkms/evdi/1.1.65/build/evdi_gem.c:211:35: warning: passing argument 2 of ‘drm_gem_object_lookup’ makes integer from pointer without a cast [-Wint-conversion]
  obj = drm_gem_object_lookup(dev, file, handle);
                                   ^
In file included from /var/lib/dkms/evdi/1.1.65/build/evdi_drv.h:23:0,
                 from /var/lib/dkms/evdi/1.1.65/build/evdi_gem.c:11:
include/drm/drm_gem.h:241:24: note: expected ‘u32 {aka unsigned int}’ but argument is of type ‘struct drm_file *’
 struct drm_gem_object *drm_gem_object_lookup(struct drm_file *filp, u32 handle);
                        ^
/var/lib/dkms/evdi/1.1.65/build/evdi_gem.c:211:8: error: too many arguments to function ‘drm_gem_object_lookup’
  obj = drm_gem_object_lookup(dev, file, handle);
        ^
In file included from /var/lib/dkms/evdi/1.1.65/build/evdi_drv.h:23:0,
                 from /var/lib/dkms/evdi/1.1.65/build/evdi_gem.c:11:
include/drm/drm_gem.h:241:24: note: declared here
 struct drm_gem_object *drm_gem_object_lookup(struct drm_file *filp, u32 handle);
                        ^
cc1: some warnings being treated as errors
scripts/Makefile.build:289: recipe for target '/var/lib/dkms/evdi/1.1.65/build/evdi_gem.o' failed
make[2]: *** [/var/lib/dkms/evdi/1.1.65/build/evdi_gem.o] Error 1
cc1: some warnings being treated as errors
scripts/Makefile.build:289: recipe for target '/var/lib/dkms/evdi/1.1.65/build/evdi_main.o' failed
make[2]: *** [/var/lib/dkms/evdi/1.1.65/build/evdi_main.o] Error 1
  if [ "-pg" = "-pg" ]; then if [ /var/lib/dkms/evdi/1.1.65/build/evdi_stats.o != "scripts/mod/empty.o" ]; then ./scripts/recordmcount  "/var/lib/dkms/evdi/1.1.65/build/evdi_stats.o"; fi; fi;
Makefile:1461: recipe for target '_module_/var/lib/dkms/evdi/1.1.65/build' failed
make[1]: *** [_module_/var/lib/dkms/evdi/1.1.65/build] Error 2
make[1]: Leaving directory '/usr/src/kernels/4.7.2-101.fc23.x86_64'
Makefile:21: recipe for target 'all' failed
make: *** [all] Error 2

Error out early when can't sign kernel modules

Running the installer on a fresh F25 install returns:

[bhart@SysAdmin-02 displaylink]$ sudo ./displaylink-driver-1.2.58.run
[sudo] password for bhart: 
Verifying archive integrity... All good.
Uncompressing DisplayLink Linux Driver 1.2.58  100%  
DisplayLink Linux Software 1.2.58 install script called: install
Distribution discovered: "Fedora release 25 (Twenty Five)"
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64-ubuntu-1404/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing license file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.
ln: failed to create symbolic link '/lib/systemd/system-sleep/displaylink.sh': File exists
Job for dlm.service failed because the control process exited with error code.
See "systemctl status dlm.service" and "journalctl -xe" for details.
[bhart@SysAdmin-02 displaylink]$

I know theres no release for 25 currently.. but I wanted to ask about the section mentioning the Unit files have no install config. Is that intended? Is there anything I can do to resolve this?

CentOS7 with DisplayLink

I'm hoping that this will help someone out. I spent way too much time on figuring this out this yesterday.

Here's how I got my DisplayLink dock going with CentOS 7 : #13 (comment)

RPM builds and Installs on Fedora 28 but does not install evdi module nor displaylink manager ?

I have two machines where I m trying to make this work under Fedora 28
lenovo Thinkpad Ultra USB 3 dock with HDMI and Displayport out ( trying to use HDMI Out)

Both machines are running Nvidia propietary drivers.

RPM Builds and installs without error message on both but evdi module and displaylink manager service does not seem to be installed

$modprobe evdi
modprobe: FATAL: Module evdi not found in directory /lib/modules/4.17.2-200.fc28.x86_64

systemctl does not recognize a service as displaylink.service

Viktor

F26 Dell XPS 13 square monitor resolutions

Hi there,
Not entirely sure if this is something I should be raising here or with EVDI.
I have just upgraded from Fedora 24 -> 26 and have all monitors "working"/ displaying something.
However the builtin laptop monitor will not allow me to select any rectangular resolutions to make use of the whole real estate (16:9), so at the moment that is stuck on 4:3 resolution.
If I choose the top resolution of 3200x1800 I am unable to use all monitors (because the total resolution area is too large)

It would be great to continue using the 3 external monitors and to set the laptop to 1920x1080 (or something similar)

(I was able to use the full laptop resolution, and monitor setup back on Fedora 24 and kernel 4.7.9-200)

System Information
Manufacturer: Dell Inc.
Product Name: XPS 13 9343
Version: Not Specified
Serial Number: 683TL32
UUID: 4C4C4544-0038-3310-8054-B6C04F4C3332
Wake-up Type: Power Switch
SKU Number: 0665
Family: Not Specified

Using a Dell D3100
Kernel: 4.11.11-300.fc26.x86_64
Package: displaylink-1.4.1-4.x86_64
SELinux: enforcing

I have also attached my xrandr output
xrandr-output.txt

Thanks

kernel 4.19

After the update to kernel 4.19 displaylink stop working. When trying to load the module I get this error

/sbin/modprobe evdi modprobe: FATAL: Module evdi not found in directory /lib/modules/4.19.2-300.fc29.x86_64
Modul is available up to kernel 4.18.7-200

Maybe it is the same issue as descriped in DisplayLink/evdi#139

Fedora 27 - displaylink.service: Failed with result 'exit-code'.

I'm getting the error below, any suggestions?

systemctl status displaylink.service
● displaylink.service - DisplayLink Manager Service
Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2017-11-30 12:14:22 CET; 1s ago
Process: 18447 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILURE)

Nov 30 12:14:22 localhost.localdomain systemd[1]: displaylink.service: Failed with result 'exit-code'.

Fedora 26 - Failed to enable unit: Unit file displaylink.service does not exist.

Hello,

When attempting to install and configure the displaylink RPM I am hitting an issue while trying to enable the displaylink service. After reading through several posts I am a bit lost but may also be missing something very simple.

I have done the following:

Downloaded the zip from the main github page
Unzipped to a folder on my Desktop
"Make" from konsole (KDE)
RPM - Uvh on displaylink-1.5.0-1.src.rpm

All processes appear successful, after running the last command I then attempt to start the service using

systemctl enable displaylink.service

I receive an error: Failed to enable unit: Unit file displaylink.service does not exist.

I assume this file should appear in, "/lib/systemd/systemd" but do not see it

Note: I also tried
make clean
make rawhide

I now have two RPM's in the target directory, one rawhide and one not.

Please bump version to DisplayLink 1.3.52 16 Feb 2017

Please bump to recently released DisplayLink 1.3.52 16 Feb 2017

Host RPMs/SRPMs

It would be nice if the RPMs or SRPMs could be downloaded from somewhere without having to build the RPM oneself.

(I mean, I have no problem with that, but it can be a hassle for a greater user base)

We can use GitHub's releases (you can see it also in my own fork of the repo), or we can just host here the SRPM and build the different RPMs using copr for each Fedora release. Although it seems we do not depend on anything else than libdrm-devel for building, so a single RPM might suffice, but not sure about that. libdrm-devel versions are scattered between 2.4.59 and 2.4.66 for most recent Fedora/CentOS-based releases.

evdi_modeset.c:375:2: error: implicit declaration of function ‘drm_mode_create_dirty_info_property’

Getting this error when installing fedora-25-displaylink-1.2.64-1.x86_64.rpm
on fedora 25 - 4.9.3-200.fc25.x86_64

    Manufacturer: Dell Inc.
    Product Name: XPS 13 9343
    00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)

/var/lib/dkms/evdi/1.2.64/build/evdi_modeset.c: In function ‘evdi_modeset_init’:
/var/lib/dkms/evdi/1.2.64/build/evdi_modeset.c:375:2: error: implicit declaration of function ‘drm_mode_create_dirty_info_property’ [-Werror=implicit-function-declaration]
  drm_mode_create_dirty_info_property(dev);
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/evdi/1.2.64/build/evdi_connector.c: In function ‘evdi_connector_init’:
/var/lib/dkms/evdi/1.2.64/build/evdi_connector.c:148:24: error: ‘struct drm_mode_config’ has no member named ‘dirty_info_property’; did you mean ‘tile_property’?
        dev->mode_config.dirty_info_property, 1);
                        ^
scripts/Makefile.build:293: recipe for target '/var/lib/dkms/evdi/1.2.64/build/evdi_connector.o' failed
make[2]: *** [/var/lib/dkms/evdi/1.2.64/build/evdi_connector.o] Error 1
make[2]: *** Waiting for unfinished jobs....
  if [ "-pg" = "-pg" ]; then if [ /var/lib/dkms/evdi/1.2.64/build/evdi_encoder.o != "scripts/mod/empty.o" ]; then ./scripts/recordmcount  "/var/lib/dkms/evdi/1.2.64/build/evdi_encoder.o"; fi; fi;
cc1: some warnings being treated as errors
scripts/Makefile.build:293: recipe for target '/var/lib/dkms/evdi/1.2.64/build/evdi_modeset.o' failed
make[2]: *** [/var/lib/dkms/evdi/1.2.64/build/evdi_modeset.o] Error 1
  if [ "-pg" = "-pg" ]; then if [ /var/lib/dkms/evdi/1.2.64/build/evdi_drv.o != "scripts/mod/empty.o" ]; then ./scripts/recordmcount  "/var/lib/dkms/evdi/1.2.64/build/evdi_drv.o"; fi; fi;
Makefile:1494: recipe for target '_module_/var/lib/dkms/evdi/1.2.64/build' failed
make[1]: *** [_module_/var/lib/dkms/evdi/1.2.64/build] Error 2
make[1]: Leaving directory '/usr/src/kernels/4.9.3-200.fc25.x86_64'
Makefile:21: recipe for target 'all' failed
make: *** [all] Error 2

possibly related to this:
DisplayLink/evdi@b7606bc

May need to go to this version of EVDI:
https://github.com/DisplayLink/evdi/releases/tag/v1.3.43

RHEL7 with 3.10 kernel steps

I am working on doing the "hand compile" method for a RHEL7 laptop (work related system) which has a 3.10 kernel (yes, I know...dated). Here is what I have done so far for steps:

wget displaylink-rpm-1.3.52.tar.gz
tar -zxvf displaylink-rpm-1.3.52.tar.gz
cd displaylink-rpm-1.3.52
sudo yum install -y gcc rpm-build make wget yum-utils libdrm-devel
sudo make
sudo rpm -ivh displaylink-1.3.43-2.src.rpm

However, when I do a "lsmod|grep evdi" (sans quotes) I am not noticing the "evdi" module noted as I see on my Ubuntu 16.04 laptop (personal system). Did I miss a step or two here?

For reference, I am seeing the DisplayLink device via "lsusb".

Thanks in advance.

On Fedora 29, module loads but I get no providers

On a Fedora 29 system (a Dell Latitude 7490 with a Dell D6000 dock), the rpm installs, and the service starts successfully:

[root@localhost Downloads]# systemctl status displaylink.service 
● displaylink.service - DisplayLink Manager Service
   Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled)
   Active: active (running) since Tue 2018-11-06 16:12:44 PST; 4s ago
  Process: 8428 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)
 Main PID: 8429 (DisplayLinkMana)
    Tasks: 65 (limit: 4915)
   Memory: 16.1M
   CGroup: /system.slice/displaylink.service
           └─8429 /usr/libexec/displaylink/DisplayLinkManager

Nov 06 16:12:44 localhost.localdomain systemd[1]: Starting DisplayLink Manager Service...
Nov 06 16:12:44 localhost.localdomain systemd[1]: Started DisplayLink Manager Service.

But I get no providers... like literally 0, not even a builtin:


xrandr --listproviders
Providers: number : 0

What am I doing wrong?

LICENSE?

The code on this repo lacks a LICENSE, which should be an important thing to have.

I am not sure this is even copyright-able, and for what is worth, I send all my contributions to the Public Domain through CC0.

This is not about DisplayLink's license, but about the packaging scripts and metadata license.

trouble following installation procedure on Fedora 26

sorry guys if this is a noob issue rather than a real one but I am unable to install the displaylink driver for Fedora 26 I currently run. I don't seem to be able to understand how this driver should be installed. I am trying to make an Asus MB169B+ display run with my Lenovo i510

I first downloaded the fedora-26-displaylink-1.4.1-4.x86_64.rpm and installed it using the Software Install and checked with sudo systemctl status displaylink.services and it didn't work, When checked with journal -xe I saw there was an error modprobe: FATAL: Module evdi not found in directory /lib/modules/4.11.11-300.fc26.x86_64
I then uninstalled the rpm, made a git repository in my file system and executed the following commands:

git init
git remote add github https://github.com/displaylink-rpm/displaylink-rpm
git pull github master
sudo make

It downloaded and compiled stuff but not service was installed, configured etc. I found the same rpm package inside the x86_64 folder which if I install it gives the same result as in the first case.

Please help me understand where I'm doing things wrong. Thank you for your patience

Should the %post script only install evdi for the running kernel?

Currently displaylink.spec runs dkms install against all installed kernel versions.

Among other things, the user may not have the kernel-headers for all the installed kernel versions. As dkms will try to build the module anyway for a missing kernel on system boot, should we just build it on install against the current kernel?

That should use less time on installation (and avoid problems with missing kernel-headers versions), and the user should see the changes in less time.

Is there any caveat apart from increased load time if a user chooses to use an earlier kernel?

Fedora 27 kernel update is breaking my displaylink service

I was able to get my displaylink monitor working again recently and that's great. I have been noticing it stops working each time I have a kernel update though. The logs show:

-- Unit displaylink.service has begun starting up.
Apr 11 13:14:52 fedora27.example.com modprobe[3869]: modprobe: FATAL: Module evdi not found in directory /lib/modules/4.15.15-300.fc27.x86_64
Apr 11 13:14:52 fedora27.example.com systemd[1]: displaylink.service: Control process exited, code=exited status=1
Apr 11 13:14:52 fedora27.example.com systemd[1]: Failed to start DisplayLink Manager Service.

Removing and reinstalling the displaylink rpm fixes the issue. I'm using fedora-27-displaylink-1.5.0.2-2.x86_64.rpm.

Do I have something wrong or is this happening to others?

Thanks,
-Jeff

External monitors are not working.

I am running Fedora 27 on a Dell Latitude 7490. I also have a Dell D6000 dock connected to the laptop using a USB Type-C cable.

My peripherals, networking and power work fine when connected to the dock but my two 1080p monitors are blank. The monitors are connected via the displayports out from the dock.

I used this release - fedora-27-displaylink-1.5.0.2-2.x86_64.rpm to install the displaylink drivers.

Kernel version -

$ uname -r
4.16.4-200.fc27.x86_64

Displaylink service status -

$ systemctl status displaylink.service 
● displaylink.service - DisplayLink Manager Service
   Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled)
   Active: active (running) since Wed 2018-05-02 12:13:30 EDT; 5min ago
  Process: 1177 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)
 Main PID: 1183 (DisplayLinkMana)
    Tasks: 11 (limit: 4915)
   CGroup: /system.slice/displaylink.service
           └─1183 /usr/libexec/displaylink/DisplayLinkManager

May 02 12:13:30  systemd[1]: Starting DisplayLink Manager Service...
May 02 12:13:30  systemd[1]: Started DisplayLink Manager Service.

lsusb output -

$ lsusb
Bus 002 Device 004: ID 05e3:0620 Genesys Logic, Inc. 
Bus 002 Device 003: ID 17e9:6006 DisplayLink 
Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:6715 Microdia 
Bus 001 Device 008: ID 0a5c:5832 Broadcom Corp. 
Bus 001 Device 009: ID 0461:4d22 Primax Electronics, Ltd 
Bus 001 Device 010: ID 06c4:c411 Bizlink International Corp. 
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 011: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 007: ID 413c:2107 Dell Computer Corp. 
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

evdi module has loaded -

$ lsmod | grep evdi
evdi                   61440  0
drm_kms_helper        196608  2 evdi,i915
drm                   454656  17 evdi,i915,drm_kms_helper

My display settings only show the laptop's built-in display -

Can anyone please help?

Driver no longer works in Fedora with Kernel 4.15.3

Dear everyone,

I am having trouble with the displaylink driver, since the last kernel update (Linux fedora 4.15.3-300.fc27.x86_64 #1 SMP Tue Feb 13 17:02:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux).
Basically, I can no longer start the displaylink service, therefore my second screen does not work.

The version of the driver that I am using is fedora-27-displaylink-1.5.0-2.x86_64.rpm and since kernel 4.13 I have had to follow the instructions of @LanceKroepke in issue #48 on installing the latest evdi module.

Please let me know if I can provide you with more information or if you think this should submitted to DisplayLink/evdi instead.

Many thanks!

Monitors Not working on D3100 Dock DisplayLink

Hi Guys,
Hope you can help me I just bought a D3100 dock and two 27'' monitors, but I cant make them to work on my Fedora 26, Can you help me with this.

I have Fedora 4.13.6-200.fc26.x86_64

And displaylink

#dnf info displaylink*
++++++++++++++++++++++++++++
Last metadata expiration check: 8 days, 2:46:58 ago on Wed 11 Oct 2017 09:11:02 AM BST.
Installed Packages
Name         : displaylink
Version      : 1.5.0
Release      : 1
Arch         : x86_64
Size         : 8.7 M
Source       : displaylink-1.5.0-1.src.rpm
Repo         : @System
From repo    : @commandline
Summary      : DisplayLink VGA/HDMI driver for DL-6xxx, DL-5xxx, DL-41xx and DL-3xxx adapters
License      : GPL v2.0, LGPL v2.1 and Proprietary
Description  : This adds support for HDMI/VGA adapters built upon the DisplayLink DL-6xxx,
             : DL-5xxx, DL-41xx and DL-3xxx series of chipsets. This includes numerous
             : docking stations, USB monitors, and USB adapters.

+++++++++++++++++++++

This is what I get when querying the status of displaylink

$ systemctl status displaylink.service
● displaylink.service - DisplayLink Manager Service
   Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static; vendor preset: disabled)
   Active: active (running) since Thu 2017-10-19 11:47:25 BST; 15min ago
  Process: 9601 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)
 Main PID: 9602 (DisplayLinkMana)
    Tasks: 34 (limit: 4915)
   CGroup: /system.slice/displaylink.service
           └─9602 /usr/libexec/displaylink/DisplayLinkManager

Oct 19 11:47:25 macos.mask systemd[1]: Starting DisplayLink Manager Service...
Oct 19 11:47:25 macos.mask systemd[1]: Started DisplayLink Manager Service.

$ loginctl show-session 2 -p Type
Type=wayland


$ sudo dnf install -y edora-26-displaylink-1.5.0-1.x86_64.rpm
[sudo] password for mask: 
Last metadata expiration check: 1:28:29 ago on Thu 19 Oct 2017 10:13:22 AM BST.
Can not load RPM file: edora-26-displaylink-1.5.0-1.x86_64.rpm.
Could not open: edora-26-displaylink-1.5.0-1.x86_64.rpm
[mask@macos Mapas]$ sudo dnf install -y fedora-26-displaylink-1.5.0-1.x86_64.rpm
Last metadata expiration check: 1:28:43 ago on Thu 19 Oct 2017 10:13:22 AM BST.
Dependencies resolved.
======================================================================================================================
 Package                Arch              Version                                    Repository                  Size
======================================================================================================================
Installing:
 displaylink            x86_64            1.5.0-1                                    @commandline               3.1 M
Installing dependencies:
 dkms                   noarch            2.4.0-1.20170926git959bd74.fc26            updates-testing             81 k

Transaction Summary
======================================================================================================================
Install  2 Packages

Total size: 3.2 M
Total download size: 81 k
Installed size: 8.9 M
Downloading Packages:
dkms-2.4.0-1.20170926git959bd74.fc26.noarch.rpm                                        72 kB/s |  81 kB     00:01    
----------------------------------------------------------------------------------------------------------------------
Total                                                                                  35 kB/s |  81 kB     00:02     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                              1/1 
  Installing       : dkms-2.4.0-1.20170926git959bd74.fc26.noarch                                                  1/2 
  Running scriptlet: dkms-2.4.0-1.20170926git959bd74.fc26.noarch                                                  1/2 
  Installing       : displaylink-1.5.0-1.x86_64                                                                   2/2 
  Running scriptlet: displaylink-1.5.0-1.x86_64                                                                   2/2 
  Running scriptlet: displaylink-1.5.0-1.x86_6   2/2 
  Verifying        : displaylink-1.5.0-1.x86_6   1/2 
  Verifying        : dkms-2.4.0-1.20170926git9   2/2 

Installed:
  displaylink.x86_64 1.5.0-1                         
  dkms.noarch 2.4.0-1.20170926git959bd74.fc26 




$ sudo  make
make -C /lib/modules/4.13.6-200.fc26.x86_64/build M=$PWD
make[1]: Entering directory '/usr/src/kernels/4.13.6-200.fc26.x86_64'
  AR      /usr/src/evdi-1.5.0/built-in.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_drv.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_modeset.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_connector.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_encoder.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_main.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_fb.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_gem.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_stats.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_painter.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_debug.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_cursor.o
  CC [M]  /usr/src/evdi-1.5.0/evdi_ioc32.o
  LD [M]  /usr/src/evdi-1.5.0/evdi.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /usr/src/evdi-1.5.0/evdi.mod.o
  LD [M]  /usr/src/evdi-1.5.0/evdi.ko
make[1]: Leaving directory '/usr/src/kernels/4.13.6-200.fc26.x86_64'