Arch Linux User Repository

please add this patch: https://github.com/RobertCochran/evdi/commit/0d80a3b7a8017709449a9938d14a5d10caadf389.patch

/evdi/1.1.62/build/.tmp_evdi_main.o /var/lib/dkms/evdi/1.1.62/build/evdi_main.c /var/lib/dkms/evdi/1.1.62/build/evdi_main.c: In Funktion »evdi_driver_unload«: /var/lib/dkms/evdi/1.1.62/build/evdi_main.c:82:2: Fehler: Implizite Deklaration der Funktion »drm_connector_unplug_all« [-Werror=implicit-function-declaration] drm_connector_unplug_all(dev); ^~~~~~~~~~~~~~~~~~~~~~~~ cc1: Einige Warnungen werden als Fehler behandelt make[2]: *** [scripts/Makefile.build:290: /var/lib/dkms/evdi/1.1.62/build/evdi_main.o] Fehler 1 make[1]: *** [Makefile:1461: _module_/var/lib/dkms/evdi/1.1.62/build] Fehler 2

installation fails since kernel got upgraded to 4.7.0 A fix can be found here : https://github.com/DisplayLink/evdi/issues/32

Using version 1.1.62-2, building evdi against linux-4.7-1 via dkms fails. To fix this temporarily until upstream releases a new version, download evdi from [1], move everything from module/ to /usr/src/evdi-1.1.62, then run [2]. [1] https://github.com/DisplayLink/evdi [2] dkms install -m evdi -v 1.1.62 -k 4.7.0-1-ARCH

Hello, I could not get the displaylink to work. the "DisplayLinkManager" keep crashing. linux ----- linux 4.5.4-1 linux-api-headers 4.5.5-1 linux-docs 4.5.4-1 linux-firmware 20160315.deb1d83-1 linux-headers 4.5.4-1 xfce4 ----- xfce4 4.12 xorg ---- xorg-server 1.18.3-1 uname -------- Linux 4.5.4-1-ARCH systemctl status displaylink.service ------------------------------------ * displaylink.service - DisplayLink Manager Service Loaded: loaded (/usr/lib/systemd/system/displaylink.service; enabled; vendor preset: disabled) Active: inactive (dead) since Sat 2016-06-04 11:00:15 AST; 15h ago Process: 4467 ExecStart=/usr/lib/displaylink/DisplayLinkManager (code=exited, status=0/SUCCESS) Process: 4464 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS) Main PID: 4467 (code=exited, status=0/SUCCESS) Jun 04 10:30:49 GatewayPC-Office systemd[1]: Stopped DisplayLink Manager Service. Jun 04 10:30:49 GatewayPC-Office systemd[1]: Starting DisplayLink Manager Service... Jun 04 10:30:49 GatewayPC-Office systemd[1]: Started DisplayLink Manager Service. Jun 04 11:00:14 GatewayPC-Office systemd[1]: Stopping DisplayLink Manager Service... Jun 04 11:00:15 GatewayPC-Office DisplayLinkManager[4467]: [libevdi] ioctl: drop_master error=-1 Jun 04 11:00:15 GatewayPC-Office DisplayLinkManager[4467]: [libevdi] ioctl: drop_master error=-1 Jun 04 11:00:15 GatewayPC-Office DisplayLinkManager[4467]: [libevdi] ioctl: drop_master error=-1 Jun 04 11:00:15 GatewayPC-Office DisplayLinkManager[4467]: [libevdi] ioctl: drop_master error=-1 Jun 04 11:00:15 GatewayPC-Office systemd[1]: Stopped DisplayLink Manager Service. journalctl ---------- May 25 03:36:11 GatewayPC-Office systemd[1]: Starting DisplayLink Manager Service... May 25 03:36:11 GatewayPC-Office systemd[1]: Started DisplayLink Manager Service. May 25 03:36:11 GatewayPC-Office DisplayLinkManager[16089]: terminate called after throwing an instance of 'dl::sys::Failure' May 25 03:36:11 GatewayPC-Office DisplayLinkManager[16089]: what(): Hive format not recognised May 25 03:36:11 GatewayPC-Office systemd[1]: Started Process Core Dump (PID 16090/UID 0). May 25 03:36:11 GatewayPC-Office systemd-coredump[16091]: Removed old coredump core.DisplayLinkMana.0.504913432703404d9d999cf6cc4236d6.13964.1464104047000000000000.lz4. May 25 03:36:11 GatewayPC-Office systemd[1]: displaylink.service: Main process exited, code=dumped, status=6/ABRT May 25 03:36:11 GatewayPC-Office systemd[1]: displaylink.service: Unit entered failed state. May 25 03:36:11 GatewayPC-Office systemd[1]: displaylink.service: Failed with result 'core-dump'. May 25 03:36:12 GatewayPC-Office systemd-coredump[16091]: Process 16089 (DisplayLinkMana) of user 0 dumped core. Stack trace of thread 16089: #0 0x00007fa20e353295 raise (libc.so.6) #1 0x00007fa20e3546da abort (libc.so.6) #2 0x00007fa20ee893dd _ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6) #3 0x00007fa20ee87196 _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6) #4 0x00007fa20ee871e1 _ZSt9terminatev (libstdc++.so.6) #5 0x00007fa20ee873f8 __cxa_throw (libstdc++.so.6) #6 0x000000000045416d n/a (DisplayLinkManager) #7 0x0000000000454259 n/a (DisplayLinkManager) #8 0x000000000044a855 n/a (DisplayLinkManager) #9 0x000000000043bd1b n/a (DisplayLinkManager) #10 0x0000000000425222 n/a (DisplayLinkManager) #11 0x000000000042551c n/a (DisplayLinkManager) #12 0x0000000000429e05 n/a (DisplayLinkManager) #13 0x000000000042a80a n/a (DisplayLinkManager) #14 0x000000000040cfd2 n/a (DisplayLinkManager) #15 0x00007fa20e340741 __libc_start_main (libc.so.6) #16 0x000000000041969f n/a (DisplayLinkManager) May 25 03:36:17 GatewayPC-Office systemd[1]: displaylink.service: Service hold-off time over, scheduling restart. dmesg ----- [ 1007.121557] WARNING: CPU: 3 PID: 4174 at include/drm/drm_gem.h:217 evdi_dumb_create+0x10a/0x120 [evdi]() [ 1007.121559] Modules linked in: evdi(O) cmac algif_hash algif_skcipher af_alg hidp nfsv3 nfs_acl uhid bnep mousedev amd_freq_sensitivity ath3k btusb btrtl joydev btbcm crct10dif_pclmul hid_generic amdkfd btintel crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul toshiba_wmi uvcvideo glue_helper bluetooth acer_wmi sparse_keymap amd_iommu_v2 usbhid snd_hda_codec_realtek snd_hda_codec_generic ablk_helper cryptd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 evdev videobuf2_core psmouse broadcom bcm_phy_lib input_leds arc4 videodev ath9k ath9k_common ath9k_hw mac_hid pcspkr media cdc_mbim hid serio_raw cdc_wdm ath snd_usb_audio snd_usbmidi_lib mac80211 snd_rawmidi cdc_ncm usbnet edac_mce_amd mii cfg80211 snd_hda_codec_hdmi snd_seq_device tg3 snd_hda_intel rfkill radeon [ 1007.121609] edac_core ptp pps_core libphy k10temp fam15h_power snd_hda_codec snd_hda_core rtsx_pci_ms memstick sp5100_tco snd_hwdep snd_pcm snd_timer snd thermal wmi soundcore ttm ac battery video shpchp i2c_piix4 i2c_algo_bit fjes button acpi_cpufreq tpm_tis tpm processor sch_fq_codel virtio_balloon virtio_scsi virtio_blk virtio_net virtio_ring virtio nfs lockd grace sunrpc fscache kvm irqbypass fuse udl drm_kms_helper drm syscopyarea sysfillrect sysimgblt fb_sys_fops ip_tables x_tables ext4 crc16 mbcache jbd2 sr_mod sd_mod cdrom rtsx_pci_sdmmc atkbd libps2 ahci libahci sdhci_pci sdhci led_class mmc_core ohci_pci ohci_hcd xhci_pci ehci_pci libata xhci_hcd ehci_hcd usbcore scsi_mod usb_common rtsx_pci i8042 serio [ 1007.121663] CPU: 3 PID: 4174 Comm: Xorg Tainted: G W O 4.5.4-1-ARCH #1 [ 1007.121665] Hardware name: Gateway NE722/EG70_KB, BIOS V1.07 09/24/2013 [ 1007.121667] 0000000000000286 0000000053cbbfd9 ffff880083e67cf0 ffffffff812dd982 [ 1007.121672] 0000000000000000 ffffffffa0bbac0d ffff880083e67d28 ffffffff81079042 [ 1007.121675] ffff8801868f7800 ffff880083e67dd0 ffff880186931d00 0000000000000072 [ 1007.121679] Call Trace: [ 1007.121684] [<ffffffff812dd982>] dump_stack+0x63/0x81 [ 1007.121688] [<ffffffff81079042>] warn_slowpath_common+0x82/0xc0 [ 1007.121692] [<ffffffff8107918a>] warn_slowpath_null+0x1a/0x20 [ 1007.121697] [<ffffffffa0bb7a1a>] evdi_dumb_create+0x10a/0x120 [evdi] [ 1007.121708] [<ffffffffa0285996>] drm_mode_create_dumb_ioctl+0xa6/0xc0 [drm] [ 1007.121718] [<ffffffffa0275862>] drm_ioctl+0x152/0x540 [drm] [ 1007.121729] [<ffffffffa02858f0>] ? drm_mode_page_flip_ioctl+0x380/0x380 [drm] [ 1007.121756] [<ffffffffa01f2b66>] ? ext4_release_dir+0x26/0x30 [ext4] [ 1007.121764] [<ffffffff811eed7e>] ? __vfs_write+0xce/0x100 [ 1007.121774] [<ffffffff812021e3>] do_vfs_ioctl+0xa3/0x5d0 [ 1007.121782] [<ffffffff8120c5b7>] ? __fget+0x77/0xb0 [ 1007.121791] [<ffffffff81202789>] SyS_ioctl+0x79/0x90 [ 1007.121800] [<ffffffff815b56ae>] entry_SYSCALL_64_fastpath+0x12/0x6d [ 1007.121807] ---[ end trace c4c221fc6e0abe63 ]--- [ 1007.122421] evdi: [D] evdi_painter_crtc_state_notify:359 (dev=0) Notifying crtc state: 3 [ 1007.122425] evdi: [W] evdi_painter_send_crtc_state:253 Painter is not connected! [ 1007.122434] evdi: [D] evdi_painter_crtc_state_notify:359 (dev=0) Notifying crtc state: 3 [ 1007.122436] evdi: [W] evdi_painter_send_crtc_state:253 Painter is not connected! [ 1037.206630] evdi: [W] evdi_painter_disconnect:462 (dev=0) An unknown connection to ffff8801868f6800 tries to close us [ 1037.206637] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 1037.222687] evdi: [D] evdi_painter_connect:433 (dev=0) Connected with (null) [ 1037.222697] evdi: [D] evdi_detect:69 (dev=5) Painter is connected [ 1037.224842] evdi: [D] evdi_detect:69 (dev=5) Painter is connected [ 1037.224852] evdi: [D] evdi_painter_get_edid_copy:186 (dev=5) 00 ff ff [ 2720.027344] evdi: [W] evdi_painter_disconnect:462 (dev=5) An unknown connection to ffff8801868f7800 tries to close us [ 2720.027350] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.300174] evdi: [W] evdi_painter_disconnect:462 (dev=-1) An unknown connection to ffff88015b345600 tries to close us [ 2720.300180] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.300200] evdi: [W] evdi_painter_disconnect:462 (dev=-1) An unknown connection to ffff88015b345600 tries to close us [ 2720.300202] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.300218] evdi: [W] evdi_painter_disconnect:462 (dev=0) An unknown connection to ffff88015b345600 tries to close us [ 2720.300220] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.300237] evdi: [W] evdi_painter_disconnect:462 (dev=0) An unknown connection to ffff88015b345600 tries to close us [ 2720.300239] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.300255] evdi: [W] evdi_painter_disconnect:462 (dev=5) An unknown connection to ffff88015b345600 tries to close us [ 2720.300257] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.314608] evdi: [W] evdi_painter_disconnect:462 (dev=-1) An unknown connection to ffff8801868f6600 tries to close us [ 2720.314614] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.314826] evdi: [W] evdi_painter_disconnect:462 (dev=-1) An unknown connection to ffff8801868f6600 tries to close us [ 2720.314829] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.315035] evdi: [W] evdi_painter_disconnect:462 (dev=0) An unknown connection to ffff8801868f6600 tries to close us [ 2720.315037] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.315245] evdi: [W] evdi_painter_disconnect:462 (dev=0) An unknown connection to ffff8801868f6600 tries to close us [ 2720.315247] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2720.315449] evdi: [W] evdi_painter_disconnect:462 (dev=5) An unknown connection to ffff8801868f6600 tries to close us [ 2720.315452] evdi: [W] evdi_painter_disconnect:463 - ignoring [ 2741.320336] evdi: [D] evdi_painter_disconnect:483 (dev=5) Disconnected from ffff8801868f6800 [ 2741.320348] evdi: [D] evdi_detect:72 Painter is disconnected [ 2741.320413] evdi: [W] evdi_painter_disconnect:462 (dev=-1) An unknown connection to ffff8801868f6800 tries to close us [ 2741.320417] evdi: [W] evdi_painter_disconnect:463 - ignoring any help would be greatly appreciated.

Hey, I'm positive it fails. After installing the package I searched for the module, but there is no evdi.ko found anywhere. If I remove the package with pacman, dkms complains that there is no module to be removed (aka not found). I'm seriously stumped.. Cheers

@kharag are you sure it failed? Cleaning build area fails on my machine as well, but the module builds just fine.

Hey, It seems I can't build the package either manually or with AUR helpers: Building module: cleaning build area...(bad exit status: 2) make KERNELRELEASE=4.5.4-1-ARCH all INCLUDEDIR=/lib/modules/4.5.4-1-ARCH/build/include KVERSION=4.5.4-1-ARCH DKMS_BUILD=1.... cleaning build area...(bad exit status: 2) Kernel cleanup unnecessary for this kernel. Skipping... Install is running through, but the module is not built. Please let me know if I can provide anything to help you, Cheers

@chearius thanks, I had actually updated the package yesterday minus the new download link. But if you are so eager with your patches, do you want to become maintainer? Also, could you please upload your patch file next time or paste it verbatim somewhere so it doesn't get corrupted? Cheers P.S.: source files are extracted automatically. (https://wiki.archlinux.org/index.php/PKGBUILD#noextract)

I've patched the PKGBUILD to use newer version of DisplayLink - 1.1.62. This version is also compatible with linux kernel 4.6. Here is the patch: diff --git a/DisplayLink_Ubuntu_1.0.335_release-note.txt b/DisplayLink_Ubuntu_1.0.335_release-note.txt deleted file mode 100644 index 981e1c5..0000000 --- a/DisplayLink_Ubuntu_1.0.335_release-note.txt +++ /dev/null @@ -1,121 +0,0 @@ -============================================================================= -============================================================================= - -DisplayLink Ubuntu Software Release Note - -Version: 1.0.335 -Date: 11th December 2015 - -DisplayLink DL-5xxx, DL-3x00 Firmware Version: 8.12.4.73304 -DisplayLink DL-41xx Firmware Version: 8.12.4.73304 -Extensible Virtual Display Interface version included: 1.0.68 - -============================================================================= -============================================================================= - - -A. Introduction -=============== - -This is the third beta of DisplayLink Driver Software v1.0 for Ubuntu. It provides initial, beta quality support for DisplayLink USB 3.0 devices on specific variants of desktop Ubuntu Linux. - -The driver enables video support for products using DisplayLink USB 3.0 technology. Standard native Ubuntu drivers provide support for DisplayLink audio and Ethernet interfaces. - - -A1. Important notes about DL5xxx, DL-3x00 and DL-41xx Firmware -============================================================== - -This software release contains an embedded firmware image. DL-5xxx, DL-3xxx and DL-41xx devices will be automatically upgraded with this firmware upon connection if required. - -The upgrade is silent, therefore screens connected to DL-5xxx, DL-3xxx or DL-41xx devices may require a few seconds to appear when devices are connected for the first time, or after devices have been used on other platforms and OSes. - -B. Contents -=========== - -A. Introduction -A1. Important notes about DL-5xxx, DL-3xxx and DL-41xx Firmware -B. Contents -C. Issues fixed -D. Supported O/S variants -E. Release components -F. How to Install -G. Supported Features & Hardware -H. Limitations & Known issues -I. Future Development - -C. Issues fixed -========================================================================== - -Issues fixed since DisplayLink Driver Software v1.0 Beta 2 for Ubuntu (1.0.138) -------------------------------------------------------------------------------- - -The installer does not create systemd service on Ubuntu 15.10 . (21018) - -Issues fixed since DisplayLink Driver Software v1.0 Beta 1 for Ubuntu (1.0.68) ------------------------------------------------------------------------------- - -DisplayLink service component may crash on device replug (20215) - -For some dock products, the DisplayLink screens may not be available after machine resume from suspend. (20218) - -Unable to install on Ubuntu with 4.x kernels. (20367) - -DisplayLink service component may crash when no EVDI module is loaded. (20398) - -D. Supported O/S variants -========================= - -This release has been prepared to be compatible with Ubuntu 15.10. Other variants and editions may be compatible if they meet minimum O/S requirements, but are not supported by DisplayLink. - -The Software contains binaries which work on Intel x86 platform (32 bit and 64 bit). -Minimum supported Linux Kernel version is 3.16. -Minimum supported Xorg version is 1.16. - -E. Release components -===================== -The Software consists of an open-source kernel mode driver (EVDI) with an accompanying library (libevdi), and a supporting binary application compatible with Intel x86 platform. -Source code for the open-source components can be found at DisplayLink's GitHub, https://github.com/DisplayLink - -F. How to Install -================= - -To install the release, from a terminal window, with root permissions use the command: - -sudo ./displaylink-driver-XXXX.run - -Where displaylink-driver-XXXX.run is the name of the extracted DisplayLink driver. - -The dkms framework is required for installation of DisplayLink. This can be installed with the command: sudo apt-get install dkms - -More detailed information on installation can be found at http://support.displaylink.com/knowledgebase/articles/615714#ubuntu - -G. Supported Features & Hardware -================================ - -This driver will support up to 2 displays connected to DisplayLink devices. More than 2 DisplayLink displays may work, but not supported or tested by DisplayLink. - -Resolutions up to 4K are supported on the appropriate DisplayLink hardware. - -Device families supported: -- DL-5xxx -- DL-41xx -- DL-3xxx - -Support for DL-1x5 and DL-1x0 devices is provided by the open source udl driver. - -H. Limitations & Known issues -============================= - -A list of limitations and known issues can be found here: -http://support.displaylink.com/knowledgebase/articles/641668 - -I. Future Development -====================== - -DisplayLink are open to suggestions and feedback on improving the proposed architecture and will gladly review patches or proposals from the developer community. Please find a current list of areas we identify as requiring attention below. - -- In this preview release, the user mode driver service is running with root permissions. In future versions, we would like to reduce the privilege level required for this process – e.g. by using a separate low-privileged user and a separate group, to ensure the permissions needed for driving DisplayLink screens are as low as possible. - -- The communication between the EVDI kernel module and the wrapper libevdi library is not access-controlled or authenticated. This could be improved in future releases, making it harder to compromise the data EVDI is sending and receiving. - -- EVDI kernel module driver is currently a platform_driver, for multiple reasons; most importantly because virtual displays are not discoverable, i.e. cannot be enumerated at the hardware level. EVDI is also a generic device, not tied to any particular kind of device, transport layer or a bus. diff --git a/DisplayLink_Ubuntu_1.1.62_release-note.txt b/DisplayLink_Ubuntu_1.1.62_release-note.txt new file mode 100644 index 0000000..faa6a91 --- /dev/null +++ b/DisplayLink_Ubuntu_1.1.62_release-note.txt @@ -0,0 +1,118 @@ +============================================================================= +============================================================================= + +DisplayLink Ubuntu Software Release Note + +Version: 1.1.62 +Date: 12th May 2016 + +DisplayLink DL-5xxx, DL-3x00 Firmware Version: 8.13.20.75809 +DisplayLink DL-41xx Firmware Version: 8.13.20.75810 +Extensible Virtual Display Interface version included: 1.1.61 + +============================================================================= +============================================================================= + + +A. Introduction +=============== + +This is DisplayLink Driver Software v1.1 for Ubuntu. It provides initial, production quality support for DisplayLink USB 3.0 devices on specific variants of desktop Ubuntu Linux. + +The driver enables video support for products using DisplayLink USB 3.0 technology. Standard native Ubuntu drivers provide support for DisplayLink audio and Ethernet interfaces. + + +A1. Important notes about DL5xxx, DL-3x00 and DL-41xx Firmware +============================================================== + +This software release contains an embedded firmware image. DL-5xxx, DL-3xxx and DL-41xx devices will be automatically upgraded with this firmware upon connection if required. + +The upgrade is silent, therefore screens connected to DL-5xxx, DL-3xxx or DL-41xx devices may require a few seconds to appear when devices are connected for the first time, or after devices have been used on other platforms and OSes. + +B. Contents +=========== + +A. Introduction +A1. Important notes about DL-5xxx, DL-3xxx and DL-41xx Firmware +B. Contents +C. Issues fixed +D. Supported O/S variants +E. Release components +F. How to Install +G. Supported Features & Hardware +H. Limitations & Known issues +I. Future Development + +C. Issues fixed +========================================================================== + +Issues fixed since DisplayLink Driver Software v1.0 Beta 3 for Ubuntu (1.0.335) +------------------------------------------------------------------------------- + +Sometimes screen corruption can be visible on DisplayLink monitor after screen layout change. (20462) + +DisplayLink monitor can be blank after PC reboot. (21166) + +The installer does not create systemd service on Ubuntu 16.04. (22031) + +DisplayLink monitor content may freeze after a resolution change. (22060) + +DisplayLink service component may crash after resolution change. (22061) + +D. Supported O/S variants +========================= + +This release has been prepared to be compatible with Ubuntu 16.04. Other variants and editions may be compatible if they meet minimum O/S requirements, but are not supported by DisplayLink. + +The Software contains binaries which work on Intel x86 platform (32 bit and 64 bit). +Minimum supported Linux Kernel version is 3.16. +Minimum supported Xorg version is 1.16. + +E. Release components +===================== +The Software consists of an open-source kernel mode driver (EVDI) with an accompanying library (libevdi), and a supporting binary application compatible with Intel x86 platform. +Source code for the open-source components can be found at DisplayLink's GitHub, https://github.com/DisplayLink + +F. How to Install +================= + +To install the release, from a terminal window, with root permissions use the command: + +sudo ./displaylink-driver-XXXX.run + +Where displaylink-driver-XXXX.run is the name of the extracted DisplayLink driver. + +The dkms framework is required for installation of DisplayLink. This can be installed with the command: sudo apt-get install dkms + +More detailed information on installation can be found at http://support.displaylink.com/knowledgebase/articles/615714#ubuntu + +G. Supported Features & Hardware +================================ + +This driver will support up to 2 displays connected to DisplayLink devices. More than 2 DisplayLink displays may work, but not supported or tested by DisplayLink. + +Resolutions up to 4K are supported on the appropriate DisplayLink hardware. + +Device families supported: +- DL-5xxx +- DL-41xx +- DL-3xxx + +Support for DL-1x5 and DL-1x0 devices is provided by the open source udl driver. + +H. Limitations & Known issues +============================= + +A list of limitations and known issues can be found here: +http://support.displaylink.com/knowledgebase/articles/641668 + +I. Future Development +====================== + +DisplayLink are open to suggestions and feedback on improving the proposed architecture and will gladly review patches or proposals from the developer community. Please find a current list of areas we identify as requiring attention below. + +- In this release, the user mode driver service is running with root permissions. In future versions, we would like to reduce the privilege level required for this process – e.g. by using a separate low-privileged user and a separate group, to ensure the permissions needed for driving DisplayLink screens are as low as possible. + +- The communication between the EVDI kernel module and the wrapper libevdi library is not access-controlled or authenticated. This could be improved in future releases, making it harder to compromise the data EVDI is sending and receiving. + +- EVDI kernel module driver is currently a platform_driver, for multiple reasons; most importantly because virtual displays are not discoverable, i.e. cannot be enumerated at the hardware level. EVDI is also a generic device, not tied to any particular kind of device, transport layer or a bus. diff --git a/PKGBUILD b/PKGBUILD index 9ae5fd8..fec9efe 100644 --- a/PKGBUILD +++ b/PKGBUILD @@ -5,21 +5,21 @@ pkgname=displaylink -pkgver=1.0.335 -pkgrel=8 +pkgver=1.1.62 +pkgrel=1 pkgdesc="DisplayLink DL-5xxx, DL-41xx and DL-3x00 Driver for Linux" arch=('i686' 'x86_64') url="http://www.displaylink.com/downloads/ubuntu.php" license=('custom' 'GPL2' 'LGPL2.1') depends=('dkms') +makedepends=('unzip') install=${pkgname}.install -changelog="DisplayLink_Ubuntu_1.0.335_release-note.txt" -source=(http://downloads.displaylink.com/publicsoftware/DisplayLink_Ubuntu_$pkgver.zip 99-displaylink.rules displaylink.service displaylink-sleep.sh https://raw.githubusercontent.com/sinfomicien/displaylink-evdi-opensuse/f08647a2659b4e18e86aa8a32b0b17646fe0f0d8/evdi-1.0.68-linux-4.5.0.patch) -md5sums=('006cfb269af80e6fc73bcfe04b693131' +changelog="DisplayLink_Ubuntu_1.1.62_release-note.txt" +source=(displaylink-driver-$pkgver.zip::http://www.displaylink.com/downloads/file\?id\=607 99-displaylink.rules displaylink.service displaylink-sleep.sh) +md5sums=('85879b750b26c464bd0f564fb76f398f' '37e076a16be49985f1d6800f960d16b4' 'c141a15e973481c7d961f8e135627ca4' - '4185b016cd64c6069302239515afadff' - '55e5cf81f2d87a5d2cf3f0bbe2c84d75') + '4185b016cd64c6069302239515afadff') package() { echo "Adding udev rule for DisplayLink DL-3xxx/5xxx devices" @@ -29,10 +29,8 @@ package() { install -D -m644 displaylink.service "$pkgdir/usr/lib/systemd/system/displaylink.service" install -D -m755 displaylink-sleep.sh "$pkgdir/usr/lib/systemd/system-sleep/displaylink.sh" - echo "Installing DisplayLink Module Patch" - install -D -m644 evdi-1.0.68-linux-4.5.0.patch "$pkgdir/usr/lib/displaylink/patch/evdi-1.0.68-linux-4.5.0.patch" - echo "Extracting DisplayLink Driver Package" + unzip displaylink-driver-$pkgver.zip chmod +x displaylink-driver-$pkgver.run ./displaylink-driver-$pkgver.run --target $pkgname-$pkgver --noexec cd "$pkgname-$pkgver" @@ -46,11 +44,6 @@ package() { mkdir -p $SRCDIR tar xf evdi-$pkgver-src.tar.gz -C $SRCDIR - CURRENT_DIR=`pwd` - cd $SRCDIR - patch -p1 < "$pkgdir/usr/lib/displaylink/patch/evdi-1.0.68-linux-4.5.0.patch" - cd $CURRENT_DIR - if [ "$CARCH" == "i686" ]; then ARCH="x86" elif [ "$CARCH" == "x86_64" ]; then