![]() |
|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
|
|
#1 |
|
Senior Member
Join Date: Feb 2010
Posts: 386
|
Thanks for these. I raised it internally to have a deeper look.
|
|
|
|
|
|
#2 |
|
Senior Member
Join Date: Feb 2010
Posts: 386
|
Are you sure you are running DisplayLink Manager application as a root? It looks like it cannot communicate with evdi kernel driver through the libevdi library.
Thanks, Michal |
|
|
|
|
|
#3 |
|
Junior Member
Join Date: Aug 2015
Posts: 12
|
I did both, user and root, but I'll try again.
|
|
|
|
|
|
#4 |
|
Junior Member
Join Date: Aug 2015
Posts: 12
|
# loaded module and verified
evdi 23854 0 drm_kms_helper 61022 2 i915,evdi drm 233198 8 i915,evdi,drm_kms_helper # ran ran DisplayManager as root, but the xsession was of course already running when I did that. # connected displaylink via USB, lsusb shows its there # connected the screen via displayport on the dock, roughly 10-20 seconds later crash. This time I also see an edid file which represents the screen that I plugged in. part of log.zip |
|
|
|
|
|
#5 |
|
Junior Member
Join Date: Aug 2015
Posts: 12
|
any update on this?
|
|
|
|
|
|
#6 |
|
Senior Member
Join Date: Feb 2010
Posts: 386
|
The application is crashing as it would when evdi kernel module is not loaded. We have already fixed the crash for next release, but this does not explain why you experience this if the evdi is indeed loaded.
Can you check if you can access /sys/devices/evdi folder? The application will try to write to files which are exposed there. Any problems with sysfs would be fatal - maybe it is a read-only filesystem? Also, could you attach your dmesg log - preferably with maximum logging level set for evdi following instructions in http://displaylink.org/forum/showpos...30&postcount=5 . Thanks, Michal |
|
|
|
|
|
#7 |
|
Junior Member
Join Date: Aug 2015
Posts: 12
|
directory is readable by users. Writable by root
Code:
ls -la /sys/devices/evdi total 0 drwxr-xr-x 3 root root 0 18. Aug 10:07 . drwxr-xr-x 13 root root 0 10. Aug 12:35 .. --w------- 1 root root 4096 10. Aug 14:27 add -r--r--r-- 1 root root 4096 18. Aug 10:07 count -rw-r--r-- 1 root root 4096 18. Aug 10:07 loglevel lrwxrwxrwx 1 root root 0 18. Aug 10:07 module -> ../../module/evdi drwxr-xr-x 2 root root 0 11. Aug 12:21 power --w------- 1 root root 4096 18. Aug 10:07 remove_all -rw-r--r-- 1 root root 4096 11. Aug 12:21 uevent -r--r--r-- 1 root root 4096 18. Aug 10:07 version I'll do another try of evdi in a bit with increased log level and dmesg log |
|
|
|
|
|
#8 |
|
Junior Member
Join Date: Aug 2015
Posts: 12
|
attached find the dmesg log, it does contain several errors
|
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|