![]() |
|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
|
|
#1 |
|
Junior Member
Join Date: Aug 2015
Posts: 12
|
any update on this? did the last logs reveal anything?
|
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Aug 2015
Posts: 12
|
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 |
|
|
|
|
|
#3 |
|
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, ...)? |
|
|
|
|
|
#4 |
|
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 |
|
|
|
|
|
#5 |
|
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. |
|
|
|
|
|
#6 |
|
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.
|
|
|
|
|
|
#7 |
|
Junior Member
Join Date: Jul 2015
Posts: 3
|
Just elaborating in case anyone needs easier steps for systemd like me as I didn't know xrandr really well. This post got me on the right track however. I'm happy the displaylink made the effort and released a driver for the D3x because I can't work with Windows efficiently. I tried for 2 months...
If the driver is installed (in my case using a gentoo overlay from maggu2810) you can start the displaylink service with systemctl and add the "evdi" to /etc/modules-load/evdi.conf. By guessing that you now loaded evdi and started the displaylink service automatically, you may not be able to guess what the display device is called using xrandr. The output and steps for my 3 monitor setup, both connected via HDMI on the D3100 is here: Code:
% xrandr --listproviders Providers: number : 3 Provider 0: id: 0x94 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 4 associated providers: 2 name:Intel Provider 1: id: 0x6c cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 1 name:modesetting Provider 2: id: 0x41 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 1 name:modesetting Code:
% xrandr -q Screen 0: minimum 8 x 8, current 5760 x 1080, maximum 32767 x 32767 eDP1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 409mm x 230mm 1920x1080 60.00*+ 1400x1050 59.98 1280x1024 60.02 1280x960 60.00 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Code:
xrandr --setprovideroutputsource 1 0 xrandr --setprovideroutputsource 2 0 Code:
% xrandr -q
Screen 0: minimum 8 x 8, current 5760 x 1080, maximum 32767 x 32767
eDP1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 409mm x 230mm
1920x1080 60.00*+
1400x1050 59.98
1280x1024 60.02
1280x960 60.00
1024x768 60.00
800x600 60.32 56.25
640x480 59.94
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
DVI-2-1 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 575mm x 323mm
1920x1080 60.00*+
1024x768 75.08 70.07 60.00
800x600 75.00 60.32
640x480 75.00 60.00
720x400 70.08
DVI-1-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 575mm x 323mm
1920x1080 60.00*+
1024x768 75.08 70.07 60.00
800x600 75.00 60.32
640x480 75.00 60.00
720x400 70.08
1024x768 (0x45) 65.000MHz
h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz
v: height 768 start 771 end 777 total 806 clock 60.00Hz
800x600 (0x47) 40.000MHz
h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz
v: height 600 start 601 end 605 total 628 clock 60.32Hz
1920x1080 (0x42) 148.500MHz
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz
v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz
1024x768 (0x43) 78.800MHz
h: width 1024 start 1040 end 1136 total 1312 skew 0 clock 60.06KHz
v: height 768 start 769 end 772 total 800 clock 75.08Hz
1024x768 (0x44) 75.000MHz
h: width 1024 start 1048 end 1184 total 1328 skew 0 clock 56.48KHz
v: height 768 start 771 end 777 total 806 clock 70.07Hz
1024x768 (0x45) 65.000MHz
h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz
v: height 768 start 771 end 777 total 806 clock 60.00Hz
800x600 (0x46) 49.500MHz
h: width 800 start 816 end 896 total 1056 skew 0 clock 46.88KHz
v: height 600 start 601 end 604 total 625 clock 75.00Hz
800x600 (0x47) 40.000MHz
h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz
v: height 600 start 601 end 605 total 628 clock 60.32Hz
640x480 (0x48) 31.500MHz
h: width 640 start 656 end 720 total 840 skew 0 clock 37.50KHz
v: height 480 start 481 end 484 total 500 clock 75.00Hz
640x480 (0x49) 25.200MHz
h: width 640 start 656 end 752 total 800 skew 0 clock 31.50KHz
v: height 480 start 490 end 492 total 525 clock 60.00Hz
720x400 (0x4a) 28.320MHz
h: width 720 start 738 end 846 total 900 skew 0 clock 31.47KHz
v: height 400 start 412 end 414 total 449 clock 70.08Hz
Code:
xrandr --output DVI-1-0 --auto --right-of eDP1 xrandr --output DVI-2-1 --auto --left-of eDP1 |
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|