View Single Post
Old 08-27-2015, 08:13 PM   #23
guerrierk
Junior Member
 
Join Date: Jul 2015
Posts: 21
Default

Quote:
Originally Posted by stuguy909 View Post
Drum Roll.............

Had to start the displaymanager.service manually.

Code:
# systemctl start displaylink.service
# systemctl status displaylink.service
● displaylink.service - DisplayLink Manager Service
   Loaded: loaded (/lib/systemd/system/displaylink.service; static)
   Active: active (running) since Thu 2015-08-27 15:01:58 CDT; 6s ago
  Process: 1832 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS)
 Main PID: 1837 (DisplayLinkMana)
   CGroup: /system.slice/displaylink.service
           └─1837 /usr/lib/displaylink/DisplayLinkManager

$ xrandr --listproviders
Providers: number : 3
Provider 0: id: 0x46 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 4 associated providers: 0 name:Intel
Provider 1: id: 0x12d cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
Provider 2: id: 0xfa cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
Yeah! You can now use xrandr to set the new provider to your Intel (provider 0). After that, you should have your screen into screen manager.

Just a question : have you 2 displaylink connected ?

I work around a best detection method to start automatically the displaylink service. I will post when I found it.

If someone have any informations about it, it could be useful for me ;-)

Thx

Last edited by guerrierk; 08-27-2015 at 08:16 PM.
guerrierk is offline   Reply With Quote