not sure how you found that rrittste but I had the same problem (not black, but garbled, not +892 but +893). Downgrading from my pacman cache fixed it:
Search Criteria
Package Details: displaylink 6.0-0
Package Actions
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: | 104 |
Popularity: | 2.96 |
First Submitted: | 2015-08-04 23:24 (UTC) |
Last Updated: | 2024-05-06 08:33 (UTC) |
Dependencies (5)
- evdiAUR (evdi-amd-vmap-textureAUR, evdi-compat-gitAUR, evdi-gitAUR)
- libusb (libusb-gitAUR)
- gawk (gawk-gitAUR, busybox-coreutilsAUR) (make)
- grep (grep-gitAUR, busybox-coreutilsAUR, grep-compatAUR) (make)
- wget (wget-gitAUR, wurlAUR) (make)
Required by (1)
Sources (7)
Latest Comments
« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 42 Next › Last »
wjhk23 commented on 2019-10-10 23:21 (UTC)
noraj commented on 2019-10-08 08:56 (UTC)
As rrittste said with latest xf86-video-intel and displink package no errors but all dock screen are black. I'll try the xf86-video-intel downgrade.
rrittste commented on 2019-10-07 09:36 (UTC)
xf86-video-intel (1:2.99.917+892+gc6cb1b19-1 destroyed my setup. My Displays connected via DisplayLink were apeared black, but the mouse could be used. A downgrade to Version xf86-video-intel (1:2.99.917+870+g6f4972d5-1) was sccessful.
graves501 commented on 2019-09-30 19:07 (UTC)
I can confirm pogojotz's comment. Build process worked flawlessly and the available driver is the current one.
pogojotz commented on 2019-09-05 10:15 (UTC)
I believe the out-of-date flag is invalid, since this is exactly the version, that is offered on displaylinks website for the several Ubuntus. Seems like the flagger just had trouble building the package.
At those who also have trouble building the package, please report in what environment you are doing it (what shell, any AUR helper you might be using, etc), since the trouble seems to be with the included script in the original driver package.
My build process works by the way. Tried it in qterminal
with blank makepkg
and the AUR helper yay
.
radiationcowboy commented on 2019-08-12 20:08 (UTC)
Getting the same error.
==> Starting package()... Adding udev rule for DisplayLink DL-3xxx/5xxx devices Installing DLM systemd service Extracting DisplayLink Driver Package xterm: cannot load font "-Misc-Fixed-medium-R---13-120-75-75-C-120-ISO10646-1" xterm: cannot load font "-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1" /var/tmp/pamac-build-james/displaylink/PKGBUILD: line 48: cd: displaylink-5.2.14: No such file or directory ==> ERROR: A failure occurred in package(). Aborting...
madFerret commented on 2019-08-09 15:16 (UTC)
Extracting DisplayLink Driver Package
/tmp/pamac-build/displaylink/PKGBUILD: line 48: cd: displaylink-5.2.14: No such file or directory
Was solved by doing to upgrade from cli, eg. pamac build displaylink
.
josuetex commented on 2019-07-26 14:45 (UTC)
I am getting this error on upgrade:
Extracting DisplayLink Driver Package
Falha ao analisar os argumentos: Opção -title desconhecida
==> ERRO: Uma falha ocorreu em package(). Abortando...
amon-ra commented on 2019-07-25 09:13 (UTC)
I am getting this error on upgrade:
Extracting DisplayLink Driver Package
/tmp/pamac-build/displaylink/PKGBUILD: line 48: cd: displaylink-5.2.14: No such file or directory
eddie1 commented on 2019-06-03 14:30 (UTC) (edited on 2019-06-03 14:48 (UTC) by eddie1)
@JustDevZero I'm on 5.1.4-1 and I'm having no luck.
I keep getting this when I enable / try to start the service:
-- A start job for unit displaylink.service has begun execution.
--
-- The job identifier is 51317.
Jun 03 09:27:46 EB-Manjaro modprobe[29689]: modprobe: FATAL: Module evdi not found in directory /lib/modules/5.1.4>
Jun 03 09:27:46 EB-Manjaro systemd[1]: displaylink.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
I tried removing everything and using the evdi-pre-release too with no luck. I'm not really finding anything else out there in terms of how to get this thing working on my T480s so far. Dock's an overpriced USB hub at present.
Pinned Comments