|
|
Thread Tools | Search this Thread | Display Modes |
08-18-2015, 06:17 AM | #11 |
Junior Member
Join Date: Aug 2015
Posts: 12
|
any update on this?
|
08-18-2015, 07:45 AM | #12 |
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 |
08-18-2015, 08:11 AM | #13 |
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 |
08-18-2015, 08:51 AM | #14 |
Junior Member
Join Date: Aug 2015
Posts: 12
|
dmesg log
attached find the dmesg log, it does contain several errors
|
08-25-2015, 08:03 AM | #15 |
Junior Member
Join Date: Aug 2015
Posts: 12
|
any update on this? did the last logs reveal anything?
|
09-01-2015, 02:39 PM | #16 |
Junior Member
Join Date: Aug 2015
Posts: 12
|
Ran with new version...
I ran with the new version 138. Good news its no longer crashing, but no display in xrandr, no provider. dmesg seems to indicate that the display is not found although I get the correct edid logged again.
new logs and new dmesg |
09-02-2015, 08:58 PM | #17 |
Junior Member
Join Date: Sep 2015
Posts: 7
|
So, I am own a D3100 and using Gentoo, too.
After building and loading evdi.ko and starting DisplayLinkManager I got a few lines in my system log (after a few seconds): Loading evdi.ko Code:
Sep 02 22:41:13 m3800 kernel: [ ] evdi_init Initialising logging on level 5 Code:
Sep 02 22:41:23 m3800 kernel: [D] add_store increasing device count to 1 Sep 02 22:41:23 m3800 kernel: [D] evdi_crtc_init drm_crtc_init: 0 Sep 02 22:41:23 m3800 kernel: [D] evdi_encoder_init drm_encoder_init: 0 Sep 02 22:41:23 m3800 kernel: [D] evdi_detect Painter is disconnected Sep 02 22:41:23 m3800 kernel: evdi evdi.0: No connectors reported connected with modes Sep 02 22:41:23 m3800 kernel: [drm] Cannot find any crtc or sizes - going 1024x768 Sep 02 22:41:23 m3800 kernel: evdi evdi.0: fb1: evdidrmfb frame buffer device Sep 02 22:41:23 m3800 kernel: [drm] evdi: evdi_stats_init Sep 02 22:41:23 m3800 kernel: [drm] Initialized evdi 1.0.68 19700101 on minor 1 Code:
Sep 02 22:41:35 m3800 kernel: [W] evdi_painter_disconnect (dev=0) An unknown connection to ffff880461ca2e00 tries to close us - ignoring Sep 02 22:41:36 m3800 kernel: [W] evdi_painter_disconnect (dev=0) An unknown connection to ffff88046d2cf800 tries to close us - ignoring
In the top-directory I also got a file that seems to be the EDID of my attached monitor:
So, no further success, the monitor is kept blank. Could I provide you further log stuff (files, ...)? |
09-02-2015, 09:09 PM | #18 |
Junior Member
Join Date: Sep 2015
Posts: 7
|
I would like to use strace to show what is going on.
So I stopped the running DisplayLinkManager while X is still running and started it again using "strace -f ...". Now I see an additional provider and could use xrandr to activate the monitor output. So at least it is working, but need to have a further look at the order of the commands. Log: Code:
Sep 02 23:05:00 m3800 kernel: [D] add_store increasing device count to 2 Sep 02 23:05:00 m3800 kernel: [D] evdi_crtc_init drm_crtc_init: 0 Sep 02 23:05:00 m3800 kernel: [D] evdi_encoder_init drm_encoder_init: 0 Sep 02 23:05:00 m3800 kernel: [D] evdi_detect Painter is disconnected Sep 02 23:05:00 m3800 kernel: evdi evdi.1: No connectors reported connected with modes Sep 02 23:05:00 m3800 kernel: [drm] Cannot find any crtc or sizes - going 1024x768 Sep 02 23:05:00 m3800 kernel: evdi evdi.1: fb2: evdidrmfb frame buffer device Sep 02 23:05:00 m3800 kernel: [drm] evdi: evdi_stats_init Sep 02 23:05:00 m3800 kernel: [drm] Initialized evdi 1.0.68 19700101 on minor 2 Sep 02 23:05:00 m3800 kernel: [W] evdi_painter_disconnect (dev=0) An unknown connection to ffff88042a424400 tries to close us - ignoring Sep 02 23:05:00 m3800 kernel: [W] evdi_painter_disconnect (dev=0) An unknown connection to ffff88006731ee00 tries to close us - ignoring Sep 02 23:05:00 m3800 kernel: [D] evdi_detect Painter is disconnected Sep 02 23:05:00 m3800 kernel: [D] evdi_detect Painter is disconnected Sep 02 23:05:00 m3800 kernel: [D] evdi_painter_crtc_state_notify (dev=0) Notifying crtc state: 0 Sep 02 23:05:00 m3800 kernel: [D] evdi_painter_crtc_state_notify (dev=0) Notifying crtc state: 0 Sep 02 23:05:10 m3800 kernel: [W] evdi_painter_disconnect (dev=0) An unknown connection to ffff880460654200 tries to close us - ignoring Sep 02 23:05:10 m3800 kernel: [D] evdi_painter_connect (dev=2) Connected with ffff880415c1ae00 Sep 02 23:05:10 m3800 kernel: [D] evdi_painter_connect (dev=2) Edid (3 bytes): 00 ff ff Sep 02 23:05:10 m3800 kernel: [D] evdi_detect (dev=2) Painter is connected Sep 02 23:05:10 m3800 kernel: [D] evdi_detect (dev=2) Painter is connected Sep 02 23:05:10 m3800 kernel: [D] evdi_painter_get_edid (dev=2) 00 ff ff Sep 02 23:05:50 m3800 kernel: [D] evdi_detect (dev=2) Painter is connected Sep 02 23:05:50 m3800 kernel: [D] evdi_painter_get_edid (dev=2) 00 ff ff Sep 02 23:06:08 m3800 kernel: [D] evdi_detect (dev=2) Painter is connected Sep 02 23:06:08 m3800 kernel: [D] evdi_painter_get_edid (dev=2) 00 ff ff Sep 02 23:06:08 m3800 kernel: [D] evdi_painter_mode_changed_notify (dev=2) Notifying mode changed: 1920x1200@60; bpp 32; pixel format 875713112 Sep 02 23:06:08 m3800 kernel: [D] evdi_painter_crtc_state_notify (dev=2) Notifying crtc state: 1 Sep 02 23:06:08 m3800 kernel: [D] evdi_detect (dev=2) Painter is connected Sep 02 23:06:08 m3800 kernel: [D] evdi_painter_get_edid (dev=2) 00 ff ff |
09-02-2015, 09:20 PM | #19 |
Junior Member
Join Date: Sep 2015
Posts: 7
|
I rebooted my machine to find the simple steps:
Now xrandr shows the provider (listproviders). Code:
$ xrandr --listproviders Providers: number : 2 Provider 0: id: 0x49 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 6 associated providers: 0 name:Intel Provider 1: id: 0x11c cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting Code:
xrandr --setprovideroutputsource 1 0 All fine. |
09-03-2015, 09:07 AM | #20 |
Junior Member
Join Date: Aug 2015
Posts: 12
|
ok I can confirm that after loading module prior to X and of course installing the modesetting driver it works now.
|
|
|