DisplayLink Forum - Custom RPM created for Fedora and others

Page 1 of 2

Show 40 post(s) from this thread on one page

DisplayLink Forum (https://displaylink.org/forum/index.php)

- Linux and Open Source (https://displaylink.org/forum/forumdisplay.php?f=29)

- - Custom RPM created for Fedora and others (https://displaylink.org/forum/showthread.php?t=64026)

enothen

08-15-2015 02:28 AM

Custom RPM created for Fedora and others

I modified and repackaged the Ubuntu installer in rpm format. Also added a udev rule so that the displaylink unit is started when the device is plugged in, and stopped when it's plugged out. It still uses dkms to keep it working after kernel updates.

So far I've tested it in Fedora 22, with kernels 4.1.4-200.fc22.x86_64 and 4.1.3-201.fc22.x86_64, and it works quite well. Download and step-by-step available:

http://nothen.com.ar/en/support-for-...ters-on-linux/

Eric

jkudish

08-19-2015 04:35 AM

Awesome, thanks so much for putting this together. I'll report any bugs if I find any.

jkudish

08-19-2015 05:06 AM

Hiya,

Just undid my previous installation in favor of your more future proof and more efficient RPM.

I like that it auto-detects the USB module. However, I actually own two different usb modules. The one that you own (the 4 in 1) is the one I use when mobile, but I use this more complete docking station when I'm at home and plugged into my monitor.

It seems your script doesn't detect the docking station as a displaylink device and thus doesn't start the driver when it's plugged in. As a workaround, right now, I've plugged in the 4 in 1 into the docking station, which ironically enough, works.

Can I help you provide the right info to update the script to detect the docking station properly?

Also completely unrelated to the driver, but I was wondering if you had any tips on how to get Fedora/Gnome to remember display arrangement settings after a reboot. It doesn't seem to remember that the monitor is set to the left of my laptop.

Thanks for all your help!

enothen

08-20-2015 01:16 PM

Yes, the rule works when you plug one into the other because the 4-in-1 is detected, no mather where on the usb tree. You have 2 issues then, first one is broadening the detection of DisplayLink devices, the second one issomething I haven't thought before: someone plugging two devices. Issue has to do with stopping the service only when the last device has been unplugged. I don't have two devices to test this, but I imagine my rule will stop the service when you unplug the first one, hence stopping a valid monitor from working.

Ideally, I would use "/bin/lsusb -d 17e9: 2>/dev/null || /bin/systemctl stop displaylink.service", which serves as validation of a remaining DisplayLink device plugged in, but udev does not allow for piped commands on RUN, so I would have to go with an external script, which is not what I like the most, but I understand it helps on a broader set of configurations.

For now, I've updated my rpm with a udev rule that detects devices based on vendor, which should work for you. I've also fixed an issue when upgrading the rpm, so please remove the current version, then install the new one (this version will manage upgrades ok). Try using one device, using both, then removing one, and let me know.

http://nothen.com.ar/resources/displ...8-2.x86_64.rpm

As of your other question, yes, I'm running into the same. Every time I plug a monitor I have to configure it. Don't know yet where this information is saved. I thought about leaving the DisplayLinkManager service running all the time, but that didn't work either.

Thanks,
Eric

pgn674

08-20-2015 03:17 PM

I've tried this out on my setup, but it's not working.

Laptop: Lenovo ThinkPad W520
DisplayLink adapter: Lenovo ThinkPad USB 3.0 Dock
OS: Fedora 22
Kernel: 4.1.3-201.fc22.x86_64

The module is present for my kernel:

Code:

/lib/modules/4.1.5-200.fc22.x86_64/extra/evdi.ko

The kernel identifies the USB device OK:

Code:

kernel: usb 2-1.4.1: Manufacturer: DisplayLink

And the service gets started when I plug in the "dock":

Code:

● displaylink.service - DisplayLink Manager Service

   Loaded: loaded (/etc/systemd/system/displaylink.service; static; vendor preset: disabled)

   Active: active (running) since Thu 2015-08-20 11:00:51 EDT; 14min ago

  Process: 8792 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)

 Main PID: 8795 (DisplayLinkMana)

   CGroup: /system.slice/displaylink.service

           └─8795 /usr/lib/displaylink/DisplayLinkManager



Aug 20 11:00:51 w520-pnickerson.portland.desknetinc.com systemd[1]: Starting DisplayLink Manager Service...

Aug 20 11:00:51 w520-pnickerson.portland.desknetinc.com systemd[1]: Started DisplayLink Manager Service.

This is a currently running process:

Code:

/usr/lib/displaylink/DisplayLinkManager

But no additional displays appear in the Fedora settings. And I'm not seeing any log messages about new displays being detected. Any idea where I can look for additional hints as to what's wrong?

dmesg does show some evdi entries, but I think they're normal:

Code:

[  409.913339] evdi: module verification failed: signature and/or required key missing - tainting kernel

[  409.914929] [ ] evdi_init Initialising logging on level 5

enothen

08-20-2015 07:33 PM

Did you plug a monitor on the hdmi or vga ports, or did you just plug the adapter? Asking because nothing shows up on the display configuration menu if I just plug the adapter. It only shows when I actually plug a display on the hdmi port of the adapter. Also make sure to install the rpm version (release 2) that I uploaded yesterday, as it handles a wider set of devices.

pgn674

08-20-2015 07:56 PM

I tried plugging the adapter into the USB 3.0 port on the laptop first, and then the DVI monitor cables into the adapter (and the monitors are powered and turned on). I've also tried plugging the monitors into the adapter first, and then the adapter into the laptop. And the adapter has external power and a power button, so I've tried having that on and off in various ways too.

I have been using your RPM version 1.0.68-2 from the beginning.

How much does this depend on the graphics driver being used to run the integrated display and the VGA and DisplayPort ports (not currently being used)? This laptop has NVIDIA Optimus hardware which does some kind of mixing of Intel integrated and NVIDIA card graphics, but I don't have Bumblebee installed to drive that, so it's disabled in the BIOS. I am using Nouveau as the graphics driver, as the NVIDIA binary blob has given me trouble.

pgn674

08-20-2015 08:36 PM

I am finding some other people using Ubuntu and Debian and having the same issues with the Lenovo ThinkPad USB 3.0 Dock: Everything seems to work fine, but no displays are detected.

I checked xrandr, and that doesn't show the displays either.

I have increased the DisplayLink encrypted logging level and then plugged in the dock. If anyone from DisplayLink would like to see the log files, let me know.

enothen

08-21-2015 02:17 AM

Quote:

Originally Posted by pgn674 (Post 78178)

Yeah, it seems to be related to a specific hardware combination, which I don't have. As long as the module is compiled and loaded, and the service running when the dock is plugged, means the rpm is doing things right. Hopefully someone at DisplayLink can provide more help (or someone else with the same hardware)

azothforgotten

08-24-2015 02:16 PM

I had to sign the kernel mod with a private/public key pair to get it to run on my Lenovo because I dual boot with Windows 10 and it uses secure boot. I guess you could disable secure boot if that's easier.

enothen

08-25-2015 01:05 PM

Thanks for the info, good to know. I have secure boot disabled so didn't notice that was needed.

jkudish

08-28-2015 06:07 PM

@enothen sorry for the delayed reply. your latest rpm works perfectly for me, no more need to have 2 adapters daisy-chained.

thanks so much!

enothen

09-01-2015 09:00 PM

Quote:

Originally Posted by jkudish (Post 78310)

@enothen sorry for the delayed reply. your latest rpm works perfectly for me, no more need to have 2 adapters daisy-chained.

thanks so much!

Excellent, I'm glad it works as it should.

Can I ask you (and anyone else giving a try to this rpm) please let me know the hardware and OS combination you are using (Adapter model, Laptop brand/model, OS version) so that I can have a list where this is working and not working? Might help others.

Thanks,
Eric

enothen

09-03-2015 12:05 AM

RPM updated to version 1.0.138

The rpm I created for Fedora has been updated with version 1.0.138, as released few days ago by Displaylink. Available here:

http://nothen.com.ar/resources/displ...8-1.x86_64.rpm

Driver is recompiled on the new version of evdi when the rpm is upgraded. Also note that when you plug your adapter for the first time after this upgrade, it may take some seconds to bring the display up, as a firmware upgrade has been included (or at least it looks that way for Dell's DA100 adapter).

Eric

marwir

09-06-2015 06:37 PM

Quote:

Originally Posted by enothen (Post 78354)

Can I ask you (and anyone else giving a try to this rpm) please let me know the hardware and OS combination you are using (Adapter model, Laptop brand/model, OS version) so that I can have a list where this is working and not working? Might help others.

Thanks,
Eric

Dell Inspiron 5737 (Intel & Radeon GPU)
Dell Docking Station D3000.
2 external Dell E2214H displays
Fedora 22 4.1.6-200.fc22.x86_64

At the beginning additional screens were black with no signal. Gnome settings > Displays didn't show them either. It started to work after a while. Unfortunately I don't know after what rpm's it started to work as I installed a lot of software after display link driver installation (1.0.68-2).

Now they need to be set up in Gnome Settings > Display every time I plug dock station in.

BTW: I installed your new release of 1.0.138-1 today - it works for me in the same way as previous release.

jkudish

09-19-2015 02:36 AM

My hardware combination is:

Dell XPS 13 Developer Edition, running Fedora 22
Dell UltraHD 4K USB 3.0 Docking Station (D3100)
Dell 27 Ultra HD 4K Monitor – P2715Q

I have also tested with Dell DA100 works perfectly.

xenith

10-30-2015 04:24 PM

enothen would you be willing to put this up as a project on Github or similar?

enothen

10-30-2015 11:21 PM

It already is:

https://github.com/hadess/displaylink-rpm

Eric

azothforgotten

11-06-2015 10:40 PM

Has anyone figured out how to get Fedora 22 to save the monitor arrangement?

enothen

11-07-2015 01:29 AM

Quote:

Originally Posted by azothforgotten (Post 79023)

Has anyone figured out how to get Fedora 22 to save the monitor arrangement?

Does that even work on Ubuntu? I thought the problem was on all Linux versions.

xenith

11-12-2015 04:01 PM

I have a good solid 2 minutes of wait-time for udev at boot with the dell 3100, anyone else seeing this?

Lately I can't quit X at all either, the devices aren't recognized. So no logging out - only full reboots. Every. time.

Fedora 22 to Fedora 23 upgraded

xenith

12-18-2015 09:26 PM

Enothen can you please update your RPM for F23 / 1.0.335

enothen

12-18-2015 10:05 PM

Awesome, didn't noticed the driver was updated this week. Yes, we'll do soon and post in here.

enothen

12-19-2015 03:32 PM

RPM has now been updated with driver version 1.0.335 released by DisplayLink on Dec 14th.

Altough release notes don't mention it, this release now remembers the position configured for the screen, so that it stays configured after unplugging - replugging. Other than that, there still are some minor issues with the mouse pointer flickering and with initial screen setup.

If you have an older version installed, simply issue:

sudo dnf update http://nothen.com.ar/resources/displ...5-1.x86_64.rpm

Regards,
Eric

ColdFire

12-30-2015 02:45 PM

Works like a charm and the 2min timeout at boot is gone as well -

Just wanted to say "Thank you very much" for your efforts -

Now F23 just needs to fix the Xorg-X-Server on multi-monitor setups - But with the downgraded X-Server
('' dnf --showduplicates --allowerasing --releasever=22 downgrade xorg-x11-server-Xorg '' ) it actually works like a charm on F23 for me ...

enothen

12-30-2015 09:46 PM

Awesome, thanks for letting me know. There was someone else having that 2min issue as well, so maybe the upgrade will take care of that. I didn't have that on my laptop.

Eric

philtrick

01-04-2016 04:10 PM

Quote:

Originally Posted by enothen (Post 79311)

Awesome, thanks for letting me know. There was someone else having that 2min issue as well, so maybe the upgrade will take care of that. I didn't have that on my laptop.

Eric

Hi Eric,

Your site seems to be down at the moment, I keep getting server not found.

Is there a mirror of the RPMs?

Phil

enothen

01-04-2016 08:54 PM

I don't know if it was a blip or what, I see it's all up now and have downloaded the rpm. I do not have a mirror, but eventually I'll put this on copr.fedoraproject.org (I was just introduced to it recently).

Eric

philtrick

01-05-2016 12:04 PM

Quote:

Originally Posted by enothen (Post 79328)

HI Eric,

It is working now, just trying to install on my XPS13 9350 which arrived this morning.

I'm running into an error:

[root@phillaptop phil]# modprobe evdi
modprobe: ERROR: could not insert 'evdi': Exec format error

I have the following kernel installed:

[root@phillaptop phil]# rpm -q kernel
kernel-4.4.0-0.rc6.git1.2.fc24.x86_64

This is what I get in the log:

[root@phillaptop phil]# more /var/log/displaylink/displaylink.log

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

DKMS: add completed.
Error! echo
Your kernel headers for kernel 4.2.3-300.fc23.x86_64 cannot be found at
/lib/modules/4.2.3-300.fc23.x86_64/build or /lib/modules/4.2.3-300.fc23.x86_64/source.
Error! echo
Your kernel headers for kernel 4.4.0-0.rc6.git1.2.fc24.x86_64 cannot be found at
/lib/modules/4.4.0-0.rc6.git1.2.fc24.x86_64/build or /lib/modules/4.4.0-0.rc6.git1.2.fc24.x86_64/source.

------------------------------
Deleting module version: 1.0.335
completely from the DKMS tree.
------------------------------
Done.

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

DKMS: add completed.
Error! echo
Your kernel headers for kernel 4.4.0-0.rc6.git1.2.fc24.x86_64 cannot be found at
/lib/modules/4.4.0-0.rc6.git1.2.fc24.x86_64/build or /lib/modules/4.4.0-0.rc6.git1.2.fc24.x86_64/source.

Any ideas?

Phil

enothen

01-06-2016 12:37 AM

Looks like you're missing kernel-headers. Run "rpm -q kernel kernel-core kernel-devel kernel-headers | sort" and check that you have matching versions. I'm running the lastest on F24, so it looks like this:

# rpm -q kernel kernel-core kernel-devel kernel-headers | sort
kernel-4.2.8-300.fc23.x86_64
kernel-core-4.2.8-300.fc23.x86_64
kernel-devel-4.2.8-300.fc23.x86_64
kernel-headers-4.2.8-300.fc23.x86_64

Eric

philtrick

01-06-2016 10:16 AM

Quote:

Originally Posted by enothen (Post 79334)

Hi Eric,

Thanks for the reply, I ended up uninstalling the kernel-headers and kernel devel and then re-installing, it works fine now.

All I have to do is figure out why the VGA port works but the HDMI port doesn't.

Phil

firelink4

02-23-2016 04:01 PM

Update: I followed Coldfire's suggestion earlier in this thread and downgraded xorg (dnf --showduplicates --allowerasing --releasever=22 downgrade xorg-x11-server-Xorg). Everything is now working again and the menus actually show up in the correct monitors this time.

Been using this RPM for about 3 weeks now with no issues other than the menus(right click, file, edit, etc etc) refusing to open up on the display-link monitors and having to reconfigure the monitor positions on boot.

Fedora had some upgrades earlier today and as of right now I can't seem to be able to get the ports on the dock to work. They're recognized and I can see them inside the "configure displays" section of gnome, but I only see static on either monitor. No change if I move the mouse to the displays. If I restart gnome, I get to see my background, but still no update if I move my mouse to the dock monitors. There's also artifacts on my main monitor wherever my cursor ends up.

Details:

Laptop: XPS 13 9343
Dock: D3100
OS: Fedora 23 Workstation
Kernel: 4.3.5-300.fc23.x86_64

Quote:

[~:#] rpm -q kernel kernel-core kernel-devel kernel-headers displaylink| sort
displaylink-1.0.335-1.x86_64
kernel-4.3.4-200.fc22.x86_64
kernel-4.3.5-300.fc23.x86_64
kernel-core-4.3.4-200.fc22.x86_64
kernel-core-4.3.5-300.fc23.x86_64
kernel-devel-4.3.4-200.fc22.x86_64
kernel-devel-4.3.5-300.fc23.x86_64
kernel-headers-4.3.5-300.fc23.x86_64

Contents of displaylink.log:

Quote:

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area...(bad exit status: 2)
make KERNELRELEASE=4.3.5-300.fc23.x86_64 all INCLUDEDIR=/lib/modules/4.3.5-300.fc23.x86_64/build/include KVERSION=4.3.5-300.fc23.x86_64 DKMS_BUILD=1....
cleaning build area...(bad exit status: 2)

DKMS: build completed.

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

depmod....

DKMS: install completed.

Quote:

[/var/lib/dkms:#] lsmod | grep evdi
evdi 36864 2
drm_kms_helper 122880 2 i915,evdi
drm 335872 14 i915,evdi,drm_kms_helper

Let me know if there's anything else I can provide...

jfha73

06-30-2016 12:38 PM

Is there a RPM for Fedora 24?

Hey guys,

I downloaded and installed the latest version of this driver on my Fedora 24, but from time to time the screens connected to the docking station start flickering, this did not happen when I had Fedora 23 with the same driver.

Any ideas?

Thanks.

lsarrat

07-13-2016 02:22 PM

Fedora 24 4.6.3-300.fc24.x86_64 & Displaylink-1.1.65-2.x86_64

I am able to compile, install and get the service running, but when I do plug a monitor, nothing happen.
(was working previously with f23)
Was anybody successful with f24 4.6.3 and displaylink ?

Thx for your help

Laurent

aaronjcopley

08-17-2016 03:19 PM

Quote:

Originally Posted by azothforgotten (Post 78198)

Any information on how you sign the driver? I'd like to keep SecureBoot enabled. Thank in advance.

samjam

09-01-2016 01:10 PM

See: http://www.displaylink.org/forum/sho...42&postcount=6
and
http://www.displaylink.org/forum/sho...69&postcount=4

MartinHerrman

09-04-2016 07:25 PM

I'm using fedora 24 workstation, which is currently running a 4.7 kernel. I reinstalled the package:

Code:

# dnf reinstall displaylink-1.0.335-1.x86_64.rpm 

Last metadata expiration check: 0:55:17 ago on Sun Sep  4 20:02:38 2016.

Dependencies resolved.

===================================================================================================================================================================================================================

 Package                                             Arch                                           Version                                             Repository                                            Size

===================================================================================================================================================================================================================

Reinstalling:

 displaylink                                         x86_64                                         1.0.335-1                                           @commandline                                         2.6 M



Transaction Summary

===================================================================================================================================================================================================================



Total size: 2.6 M

Is this ok [y/N]: y

Downloading Packages:

Running transaction check

Transaction check succeeded.

Running transaction test

Transaction test succeeded.

Running transaction

  Reinstalling: displaylink-1.0.335-1.x86_64                                                                                                                                                                   1/2 

warning: %post(displaylink-1.0.335-1.x86_64) scriptlet failed, exit status 10

Non-fatal POSTIN scriptlet failure in rpm package displaylink

Non-fatal POSTIN scriptlet failure in rpm package displaylink

  Erasing     : displaylink-1.0.335-1.x86_64                                                                                                                                                                   2/2 

  Verifying   : displaylink-1.0.335-1.x86_64                                                                                                                                                                   1/2 

  Verifying   : displaylink-1.0.335-1.x86_64                                                                                                                                                                   2/2 



Reinstalled:

  displaylink.x86_64 1.0.335-1                                                                                                                                                                                     



Complete!

But unfortunately it doesn' t work. The EVDI module cannot be compiled. It looks like I have an incompatible library that provides DRM functions. Anyone who has an idea how this can be fixed?

Code:

  gcc -Wp,-MD,/var/lib/dkms/evdi/1.0.335/build/.evdi_encoder.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/6.1.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 -Wno-unused-const-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_encoder"'  -DKBUILD_MODNAME='"evdi"' -c -o /var/lib/dkms/evdi/1.0.335/build/evdi_encoder.o /var/lib/dkms/evdi/1.0.335/build/evdi_encoder.c

/var/lib/dkms/evdi/1.0.335/build/evdi_modeset.c:124:16: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]

   .fb_create = evdi_fb_user_fb_create,

                ^~~~~~~~~~~~~~~~~~~~~~

/var/lib/dkms/evdi/1.0.335/build/evdi_modeset.c:124:16: note: (near initialization for ‘evdi_mode_funcs.fb_create’)

/var/lib/dkms/evdi/1.0.335/build/evdi_modeset.c: In function ‘evdi_modeset_init’:

/var/lib/dkms/evdi/1.0.335/build/evdi_modeset.c:148:3: error: too many arguments to function ‘drm_dev_set_unique’

   drm_dev_set_unique(dev, "%s", dev_name(dev->dev));

   ^~~~~~~~~~~~~~~~~~

In file included from /var/lib/dkms/evdi/1.0.335/build/evdi_modeset.c:14:0:

include/drm/drmP.h:1085:5: note: declared here

 int drm_dev_set_unique(struct drm_device *dev, const char *name);

     ^~~~~~~~~~~~~~~~~~

cc1: some warnings being treated as errors

scripts/Makefile.build:289: recipe for target '/var/lib/dkms/evdi/1.0.335/build/evdi_modeset.o' failed

make[2]: *** [/var/lib/dkms/evdi/1.0.335/build/evdi_modeset.o] Error 1

make[2]: *** Waiting for unfinished jobs....

/var/lib/dkms/evdi/1.0.335/build/evdi_encoder.c: In function ‘evdi_encoder_init’:

/var/lib/dkms/evdi/1.0.335/build/evdi_encoder.c:72:12: error: too few arguments to function ‘drm_encoder_init’

   status = drm_encoder_init(dev, encoder, &evdi_enc_funcs, DRM_MODE_ENCODER_TMDS);

            ^~~~~~~~~~~~~~~~

In file included from include/drm/drmP.h:68:0,

                 from /var/lib/dkms/evdi/1.0.335/build/evdi_encoder.c:13:

include/drm/drm_crtc.h:2283:5: note: declared here

 int drm_encoder_init(struct drm_device *dev,

     ^~~~~~~~~~~~~~~~

scripts/Makefile.build:289: recipe for target '/var/lib/dkms/evdi/1.0.335/build/evdi_encoder.o' failed

make[2]: *** [/var/lib/dkms/evdi/1.0.335/build/evdi_encoder.o] Error 1

  if [ "-pg" = "-pg" ]; then if [ /var/lib/dkms/evdi/1.0.335/build/evdi_connector.o != "scripts/mod/empty.o" ]; then ./scripts/recordmcount  "/var/lib/dkms/evdi/1.0.335/build/evdi_connector.o"; fi; fi;

  if [ "-pg" = "-pg" ]; then if [ /var/lib/dkms/evdi/1.0.335/build/evdi_drv.o != "scripts/mod/empty.o" ]; then ./scripts/recordmcount  "/var/lib/dkms/evdi/1.0.335/build/evdi_drv.o"; fi; fi;

Makefile:1461: recipe for target '_module_/var/lib/dkms/evdi/1.0.335/build' failed

make[1]: *** [_module_/var/lib/dkms/evdi/1.0.335/build] Error 2

make[1]: Leaving directory '/usr/src/kernels/4.7.2-201.fc24.x86_64'

Makefile:18: recipe for target 'all' failed

make: *** [all] Error 2

RobertCochran

09-06-2016 06:05 PM

The evdi module included in this package does not support 4.7.x or greater series kernels. You will have to build evdi and libevdi from source, or wait for an updated package.

MartinHerrman

09-11-2016 12:48 PM

Thanks! After installing libdrm-devel I could compile the latest code which I downloaded from the GIT repository. I copied the module to the /lib/modules/kernel/misc directory and ran depmod. Finally I reinstalled the displaylink rpm.

Will test the result tomorrow at work!

MartinHerrman

09-12-2016 11:21 AM

Test, disconnect and reconnect the dock:

Code:

[16893.602902] usb 2-2: USB disconnect, device number 8

[16893.602911] usb 2-2.1: USB disconnect, device number 11

[16893.605431] usb 2-2.2: USB disconnect, device number 9

[16893.607037] usb 2-2.3: USB disconnect, device number 10

[16893.608267] cdc_ncm 2-2.3:1.5 enp0s20u2u3i5: unregister 'cdc_ncm' usb-0000:00:14.0-2.3, CDC NCM

[16893.622576] evdi: [W] evdi_painter_disconnect:462 (dev=0) An unknown connection to ffff8800c30c9600 tries to close us

[16893.622579] evdi: [W] evdi_painter_disconnect:463  - ignoring

[16893.622585] evdi: [W] evdi_painter_disconnect:462 (dev=0) An unknown connection to ffff8800c30c9600 tries to close us

[16893.622587] evdi: [W] evdi_painter_disconnect:463  - ignoring

[16893.652409] usb 1-2: USB disconnect, device number 8

[16893.652414] usb 1-2.2: USB disconnect, device number 9

[16893.652417] usb 1-2.2.4: USB disconnect, device number 10

[16900.672034] usb 1-2: new high-speed USB device number 11 using xhci_hcd

[16900.839107] usb 1-2: New USB device found, idVendor=2109, idProduct=2812

[16900.839112] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[16900.839114] usb 1-2: Product: USB2.0 Hub             

[16900.839116] usb 1-2: Manufacturer: VIA Labs, Inc.         

[16900.840724] hub 1-2:1.0: USB hub found

[16900.841157] hub 1-2:1.0: 4 ports detected

[16900.939305] usb 2-2: new SuperSpeed USB device number 12 using xhci_hcd

[16901.187261] usb 2-2: New USB device found, idVendor=2109, idProduct=0812

[16901.187270] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[16901.187275] usb 2-2: Product: USB3.0 Hub             

[16901.187278] usb 2-2: Manufacturer: VIA Labs, Inc.         

[16901.191660] hub 2-2:1.0: USB hub found

[16901.191942] hub 2-2:1.0: 4 ports detected

[16901.260001] usb 1-2.2: new high-speed USB device number 12 using xhci_hcd

[16901.348305] usb 1-2.2: New USB device found, idVendor=2109, idProduct=2812

[16901.348308] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[16901.348310] usb 1-2.2: Product: USB2.0 Hub             

[16901.348311] usb 1-2.2: Manufacturer: VIA Labs, Inc.         

[16901.349660] hub 1-2.2:1.0: USB hub found

[16901.350310] hub 1-2.2:1.0: 4 ports detected

[16901.559354] usb 2-2.2: new SuperSpeed USB device number 13 using xhci_hcd

[16901.807336] usb 2-2.2: New USB device found, idVendor=2109, idProduct=0812

[16901.807339] usb 2-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[16901.807341] usb 2-2.2: Product: USB3.0 Hub             

[16901.807342] usb 2-2.2: Manufacturer: VIA Labs, Inc.         

[16901.810092] hub 2-2.2:1.0: USB hub found

[16901.810336] hub 2-2.2:1.0: 4 ports detected

[16901.924021] usb 1-2.2.4: new low-speed USB device number 13 using xhci_hcd

[16902.059458] usb 1-2.2.4: New USB device found, idVendor=413c, idProduct=2107

[16902.059462] usb 1-2.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[16902.059464] usb 1-2.2.4: Product: Dell USB Entry Keyboard

[16902.059465] usb 1-2.2.4: Manufacturer: Dell

[16902.063974] input: Dell Dell USB Entry Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2.4/1-2.2.4:1.0/0003:413C:2107.0005/input/input20

[16902.115366] hid-generic 0003:413C:2107.0005: input,hidraw1: USB HID v1.10 Keyboard [Dell Dell USB Entry Keyboard] on usb-0000:00:14.0-2.2.4/input0

[16902.184025] usb 2-2.3: new SuperSpeed USB device number 14 using xhci_hcd

[16902.195492] usb 2-2.3: New USB device found, idVendor=17e9, idProduct=436e

[16902.195496] usb 2-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[16902.195497] usb 2-2.3: Product: Dell USB3.0 Dock

[16902.195498] usb 2-2.3: Manufacturer: DisplayLink

[16902.195499] usb 2-2.3: SerialNumber: 1503302068

[16902.205827] usb 2-2.3: Warning! Unlikely big volume range (=511), cval->res is probably wrong.

[16902.205831] usb 2-2.3: [16] FU [Dell USB Audio Playback Volume] ch = 6, val = -8176/0/16

[16902.206643] usb 2-2.3: Warning! Unlikely big volume range (=767), cval->res is probably wrong.

[16902.206646] usb 2-2.3: [13] FU [Mic Capture Volume] ch = 2, val = -4592/7680/16

[16902.230323] cdc_ncm 2-2.3:1.5: MAC-Address: 9c:eb:e8:1e:6d:aa

[16902.230327] cdc_ncm 2-2.3:1.5: setting rx_max = 16384

[16902.230424] cdc_ncm 2-2.3:1.5: setting tx_max = 16384

[16902.230645] cdc_ncm 2-2.3:1.5 usb0: register 'cdc_ncm' at usb-0000:00:14.0-2.3, CDC NCM, 9c:eb:e8:1e:6d:aa

[16902.407171] usb 2-2.1: new SuperSpeed USB device number 15 using xhci_hcd

[16902.418772] usb 2-2.1: New USB device found, idVendor=17e9, idProduct=436e

[16902.418775] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[16902.418777] usb 2-2.1: Product: Dell USB3.0 Dock

[16902.418778] usb 2-2.1: Manufacturer: DisplayLink

[16902.418779] usb 2-2.1: SerialNumber: 1503302068B

[16902.468716] cdc_ncm 2-2.3:1.5 enp0s20u2u3i5: renamed from usb0

[16902.488895] IPv6: ADDRCONF(NETDEV_UP): enp0s20u2u3i5: link is not ready

[16902.488991] IPv6: ADDRCONF(NETDEV_UP): enp0s20u2u3i5: link is not ready

[16902.511469] evdi: [W] evdi_painter_disconnect:462 (dev=0) An unknown connection to ffff8800c2e09200 tries to close us

[16902.511471] evdi: [W] evdi_painter_disconnect:463  - ignoring

[16904.244808] evdi: [E] evdi_painter_connect:405 Edid length too large

[16904.976758] cdc_ncm 2-2.3:1.5 enp0s20u2u3i5: 1000 mbit/s downlink 1000 mbit/s uplink

[16904.992781] cdc_ncm 2-2.3:1.5 enp0s20u2u3i5: network connection: connected

[16904.992810] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20u2u3i5: link becomes ready

Module is loaded:

Code:

lsmod | grep evdi

evdi                   40960  2

drm_kms_helper        143360  2 i915,evdi

drm                   344064  13 i915,evdi,drm_kms_helper

Kernel:

Code:

uname -r

4.7.2-201.fc24.x86_64

Installed RPM: displaylink-1.0.335-1.x86_64.rpm

Any ideas?

All times are GMT. The time now is 08:57 PM.

Page 1 of 2

Show 40 post(s) from this thread on one page