Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Linux and Open Source

Reply
 
Thread Tools Search this Thread Display Modes
Old 08-20-2015, 07:56 PM   #1
pgn674
Junior Member
 
Join Date: Aug 2015
Posts: 4
Default

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 is offline   Reply With Quote
Old 08-20-2015, 08:36 PM   #2
pgn674
Junior Member
 
Join Date: Aug 2015
Posts: 4
Default

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.
pgn674 is offline   Reply With Quote
Old 08-21-2015, 02:17 AM   #3
enothen
Junior Member
 
Join Date: Aug 2015
Posts: 15
Default

Quote:
Originally Posted by pgn674 View Post
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.
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)
enothen is offline   Reply With Quote
Old 08-24-2015, 02:16 PM   #4
azothforgotten
Junior Member
 
Join Date: Aug 2015
Posts: 3
Default

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.
azothforgotten is offline   Reply With Quote
Old 08-25-2015, 01:05 PM   #5
enothen
Junior Member
 
Join Date: Aug 2015
Posts: 15
Default

Thanks for the info, good to know. I have secure boot disabled so didn't notice that was needed.
enothen is offline   Reply With Quote
Old 12-18-2015, 10:26 PM   #6
xenith
Junior Member
 
Join Date: Oct 2015
Posts: 6
Default

Enothen can you please update your RPM for F23 / 1.0.335
xenith is offline   Reply With Quote
Old 12-18-2015, 11:05 PM   #7
enothen
Junior Member
 
Join Date: Aug 2015
Posts: 15
Default

Awesome, didn't noticed the driver was updated this week. Yes, we'll do soon and post in here.
enothen is offline   Reply With Quote
Old 08-17-2016, 03:19 PM   #8
aaronjcopley
Junior Member
 
Join Date: Aug 2016
Posts: 1
Default

Quote:
Originally Posted by azothforgotten View Post
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.
Any information on how you sign the driver? I'd like to keep SecureBoot enabled. Thank in advance.

Last edited by aaronjcopley; 08-17-2016 at 03:22 PM.
aaronjcopley is offline   Reply With Quote
Old 09-01-2016, 01:10 PM   #9
samjam
Junior Member
 
Join Date: May 2016
Posts: 22
Default

See: http://www.displaylink.org/forum/sho...42&postcount=6
and
http://www.displaylink.org/forum/sho...69&postcount=4
samjam is offline   Reply With Quote
Old 09-04-2016, 07:25 PM   #10
MartinHerrman
Junior Member
 
Join Date: Aug 2015
Posts: 7
Default

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
MartinHerrman is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 03:05 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.