Package Details: displaylink 6.0-0

Git Clone URL: https://aur.archlinux.org/displaylink.git (read-only, click to copy)
Package Base: displaylink
Description: Linux driver for DisplayLink devices
Upstream URL: https://www.synaptics.com/products/displaylink-graphics
Keywords: dock gpu graphics usb
Licenses: GPL2, custom, LGPL2.1
Submitter: Hideaki
Maintainer: endorfina
Last Packager: endorfina
Votes: 99
Popularity: 0.100736
First Submitted: 2015-08-04 23:24 (UTC)
Last Updated: 2024-05-06 08:33 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 31 32 33 34 35 36 37 38 39 40 41 Next › Last »

PlusMinus commented on 2016-09-20 07:14 (UTC)

According to the release notes, the UD devices aren't supported. As for you other device, have you tried another cable or another monitor? If nothing else works, try debugging the application with the help of the forums. And if you find a solution I can try to patch it in.

solo9300 commented on 2016-09-19 15:38 (UTC)

@PlusMinus I have to tow. 1) Plugable USB 3.0 to HDMI (DL-3500). 2) Plugable USB Docking Station (UD-3900).

PlusMinus commented on 2016-09-19 08:51 (UTC)

@solo9300 could you be more specific please? Which device do you mean?

solo9300 commented on 2016-09-18 19:04 (UTC)

did anyone get this USB3 to HDMI adapter to work? Nothing seem to be working for me, I keep updating the driver but the driver would not work. dmesg: [ 1790.594982] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd [ 1790.626596] usb 4-1: Warning! Unlikely big volume range (=511), cval->res is probably wrong. [ 1790.626609] usb 4-1: [14] FU [USB3-HDMI-DVI Audio Playback Volume] ch = 6, val = -8176/0/16

rhabbachi commented on 2016-09-15 14:22 (UTC)

Updated https://github.com/rhabbachi/displaylink-pkgbuild with @PlusMinus suggestions.

rhabbachi commented on 2016-09-15 14:17 (UTC)

The thing is AFAIK This module is not functional using the latest 4.7 kernel that is the current kernel in Arch.

rhabbachi commented on 2016-09-15 14:14 (UTC) (edited on 2016-09-15 14:15 (UTC) by rhabbachi)

> Maybe it makes more sense to put evdi into another package. In a more generic case I would 100% agree. But for this package I'm not really sure. Will the eventual evdi package be installed without this package? And what will this package (displaylink) depend on? should all the evdi packages `provides= "evdi"`? I think to mitigate the confusion that might arise we can keep this package using the default evdi module provided by the displaylink site and create another package (displaylink-latest-evdi or something similar) that uses the latest evdi module.

PlusMinus commented on 2016-09-15 13:41 (UTC)

Maybe it makes more sense to put evdi into another package.

PlusMinus commented on 2016-09-15 13:21 (UTC)

Thanks for the effort @rhabbachi I added some inline comments on your git.

rhabbachi commented on 2016-09-15 13:04 (UTC)

updated the PKGBUILD to use the latest evdi module from https://github.com/DisplayLink/evdi. Feedback welcome https://github.com/rhabbachi/displaylink-pkgbuild