Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Providers: number : 1 in Debian Testing - XPS13 - kernel 4.18.0-2-amd64 #173

Closed
nllz opened this issue Nov 20, 2018 · 20 comments
Closed

Providers: number : 1 in Debian Testing - XPS13 - kernel 4.18.0-2-amd64 #173

nllz opened this issue Nov 20, 2018 · 20 comments

Comments

@nllz
Copy link

nllz commented Nov 20, 2018

Thanks a lot for this great work. Unfortunately I have some issues getting this to work.

My setup:

Dell XPS13 - HP 3005pr

$ cat /proc/version
Linux version 4.18.0-2-amd64 ([email protected]) (gcc version 7.3.0 (Debian 7.3.0-30)) #1 SMP Debian 4.18.10-2 (2018-11-02)

Installation went fine, and process is running:

$ systemctl status dlm.service
● dlm.service - DisplayLink Manager Service
   Loaded: loaded (/lib/systemd/system/dlm.service; enabled; vendor preset: enab
   Active: active (running) since Tue 2018-11-20 13:49:22 CET; 1h 15min ago
  Process: 712 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install evdi/4.4.2
 Main PID: 716 (DisplayLinkMana)
    Tasks: 35 (limit: 4915)
   Memory: 36.4M
   CGroup: /system.slice/dlm.service
           └─716 /opt/displaylink/DisplayLinkManager

but unfortunately I get:

$ xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x47 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 4 associated providers: 0 name:Intel

Any pointers on how I can get my two external screens to work?

@nllz nllz changed the title Debian Testing - XPS13 - kernel 4.18.0-2-amd64 Providers: number : 0 in Debian Testing - XPS13 - kernel 4.18.0-2-amd64 Nov 20, 2018
@nllz nllz changed the title Providers: number : 0 in Debian Testing - XPS13 - kernel 4.18.0-2-amd64 Providers: number : 1 in Debian Testing - XPS13 - kernel 4.18.0-2-amd64 Nov 20, 2018
@kopax
Copy link

kopax commented Nov 20, 2018

Could you try another USB port / reboot ? I got the same results and after doing that I was able to see 2 providers.

@nllz
Copy link
Author

nllz commented Nov 20, 2018

Switched port and rebooted by to no avail. I think some answers might be found in this part of my log:

$ sudo dmesg | grep evdi
[   13.076935] evdi: loading out-of-tree module taints kernel.
[   13.078939] evdi: [I] Initialising logging on level 5
[   13.078940] evdi: [I] Atomic driver:no
[   13.647703] evdi: [D] evdi_add_devices:134 Increasing device count to 1
[   13.647820] evdi: [D] evdi_crtc_init:353 drm_crtc_init: 0
[   13.647979] evdi: [W] evdi_painter_crtc_state_notify:486 Painter does not exist!
[   13.647982] evdi: [D] evdi_detect:79 Painter is disconnected
[   13.647988] evdi: [W] evdi_painter_crtc_state_notify:486 Painter does not exist!
[   13.648785] [drm] Initialized evdi 1.5.1 20180731 for evdi.0 on minor 1
[   13.648786] [drm] evdi: evdi_stats_init
[   13.696180] evdi: [D] evdi_painter_connect:574 (dev=1) Connected with 000000008ee51dc6
[   13.696183] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[   13.696204] evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 3
[   13.696645] evdi: [D] evdi_add_devices:134 Increasing device count to 2
[   13.696756] evdi: [D] evdi_crtc_init:353 drm_crtc_init: 0
[   13.697832] evdi: [W] evdi_painter_crtc_state_notify:486 Painter does not exist!
[   13.697836] evdi: [D] evdi_detect:79 Painter is disconnected
[   13.697841] evdi: [W] evdi_painter_crtc_state_notify:486 Painter does not exist!
[   13.697926] [drm] Initialized evdi 1.5.1 20180731 for evdi.1 on minor 2
[   13.697927] [drm] evdi: evdi_stats_init
[   13.710356] evdi: [D] evdi_painter_connect:574 (dev=2) Connected with 0000000042c8b383
[   13.710359] evdi: [D] evdi_detect:76 (dev=2) Painter is connected
[   13.710485] evdi: [D] evdi_painter_crtc_state_notify:483 (dev=2) Notifying crtc state: 3

@nllz
Copy link
Author

nllz commented Nov 20, 2018

I also tried re-plugging and running
$ sudo systemctl restart dlm.service

@kopax
Copy link

kopax commented Nov 20, 2018

@AdnanHodzic recommended here to try with : #172 (comment) and to post your debian version uname -a

@nllz
Copy link
Author

nllz commented Nov 20, 2018

working! thanks for all the fish!

@nllz nllz closed this as completed Nov 20, 2018
@kopax
Copy link

kopax commented Nov 20, 2018

Hey, do you mind to give some details for others ? Mine isn't working. What do you mean it work ?

@nllz
Copy link
Author

nllz commented Nov 20, 2018

Heya,

This is what I am on:

$ cat /proc/version
Linux version 4.18.0-2-amd64 ([email protected]) (gcc version 7.3.0 (Debian 7.3.0-30)) #1 SMP Debian 4.18.10-2 (2018-11-02)

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux testing (buster)
Release:	testing
Codename:	buster

As you suggested I did this:

$ sudo mv /etc/X11/xorg.conf.d/20-displaylink.conf ~/20-displaylink.conf

and when I then logged back into my xsession (rebooting or loggin out and in again) I got the following output:

$ xrandr --listproviders
Providers: number : 3
Provider 0: id: 0xa9 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 3 associated providers: 0 name:modesetting
Provider 1: id: 0x7a cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
Provider 2: id: 0x41 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting

Hope this helps!

@nllz
Copy link
Author

nllz commented Nov 20, 2018

Make sure that when you login, you are selecting from X11, not Gnome.

Click on the cogwheel drop-down menu next to the login form and select X11.

@kopax
Copy link

kopax commented Nov 20, 2018

I don't have such kind of form on cinnamon when I login, but still, thanks a lot for the clarification.
I am confident that this will help others. @AdnanHodzic I am curious why did you recommend to move that file.

Can we know more about that fix?

What is it supposed to fix exactly? What's expected?

@nllz seems to have a different behaviour than mine, when is it appropriate to do that?

Also, it may be because of cinnamon that I can't display using my screen don't you think?

@nllz
Copy link
Author

nllz commented Nov 20, 2018

@kopax Are you sure you are on Debian and not on Linux Mint?

If you use Cinnamon I think you are using Wayland as display server, and DisplayLink currently only works on X11 afaik.

@AdnanHodzic
Copy link
Owner

@kopax reason I recommended to remove that file is after last pull request by @NoNeedForNames. I realized that adding this won't work for everybody, but I merged it with master anyways, as I wanted to see how it plays out.

In meantime I also wanted to add a new implementation which would add this file only if it's needed, but didn't have time to work on it yet.

Can you both (@nllz @kopax) please tell me what paste back the outputs of both:

lspci | grep -i vga
lspci -nnk | grep -i vga -A3 | grep 'in use'|cut -d":" -f2|sed 's/ //g'

@nllz
Copy link
Author

nllz commented Nov 21, 2018

$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
$ lspci -nnk | grep -i vga -A3 | grep 'in use'|cut -d":" -f2|sed 's/ //g'
i915

@kopax
Copy link

kopax commented Nov 22, 2018

$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Device 5912 (rev 04)
$ lspci -nnk | grep -i vga -A3 | grep 'in use'|cut -d":" -f2|sed 's/ //g'
i915

@AdnanHodzic
Copy link
Owner

@nllz and everybody else with this problem, could you please pull the latest changes and run "reinstall".

@kopax
Copy link

kopax commented Nov 24, 2018

@AdnanHodzic thanks, I've reinstalled and again, the screen is displaying, the mouse can move but can't add window to that screen. It is still "frozen" but working.

How can I help troubleshoot?

@AdnanHodzic
Copy link
Owner

You could try by Monitoring for errors

You could also look into these, as they are Debian related problems, which sound a lot like yours, maybe you can find some useful information:
#68
#130

@NoNeedForNames
Copy link
Contributor

@kopax, your behavior is exactly the reason why I have built in the driver-statement in the first place. It was exactly the same behavior on my setup. What's the content of your etc/X11/xorg.conf.d/20-displaylink.conf ?

@NoNeedForNames
Copy link
Contributor

@nllz which one of the driver-versions in 20-displaylink.conf is working for you ?

@AdnanHodzic
Copy link
Owner

@nllz ok problem has been fixed as part of different issue.

Please pull the latest changes and run "reinstall".

@nllz
Copy link
Author

nllz commented Nov 25, 2018

Everything is working for me*, which is why I closed the thread :)

see: #173 (comment)

Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants