Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Linux and Open Source

Reply
 
Thread Tools Search this Thread Display Modes
Old 11-25-2016, 08:10 AM   #11
jepster
Junior Member
 
Join Date: Oct 2016
Posts: 28
Default

Quote:
/etc/modprobe.d/evdi.conf
There is no such file on my system.

I have tried to edit it via

Quote:
sudo vim /etc/modprobe.d/evdi.conf
I am using Ubuntu 16.10. What shall I need to do then, to extend the logging information for you?

Which log-file will you need then? I suppose you want me to switch the log-setting, reboot and afterwards post you the log file in this forum-thread.
jepster is offline   Reply With Quote
Old 11-25-2016, 08:39 AM   #12
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

Yes, you need to create file and pass an option you'd like to use while loading evdi - see https://wiki.archlinux.org/index.php...Fmodprobe.d.2F

The contents of the file should be: options evdi initial_loglevel=6

After rebooting, evdi should be much more chatty in your dmesg log. Providing dmesg log and X logs would hopefully show something interesting.

Regards,
Michal
mlukaszek is offline   Reply With Quote
Old 11-25-2016, 08:50 AM   #13
jepster
Junior Member
 
Join Date: Oct 2016
Posts: 28
Default

I have created the file and added the desired content. After the reboot, I have created an archive with log files by the "DisplayLink Linux Support Tool (1.2.17)" (http://www.displaylink.com/downloads/file?d=68). This zip-archive is attached to my post. Please be so kind and take a look, if my system provides any useful information.
Attached Files
File Type: zip computer_2016-11-25T09:46:21.247744.zip (50.1 KB, 1 views)
jepster is offline   Reply With Quote
Old 11-25-2016, 01:50 PM   #14
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

I don't see evdi being loaded or even attempts to load it, also DisplayLink Manager is not running. Is the driver installed at all?

Cheers,
Michal
mlukaszek is offline   Reply With Quote
Old 11-25-2016, 02:27 PM   #15
jepster
Junior Member
 
Join Date: Oct 2016
Posts: 28
Default

It seems that the driver was somehow not installed. But it "was" definitely installed. May I have uninstalled it accidently. So I have re-installed it.

By typing

Quote:
xrandr --auto
xrandr --setprovideroutputsource 2 0
I can manage to see 1 screen, which is plugged via the docking station, in the Ubuntu GUI display settings. I had also tried

Quote:
xrandr --setprovideroutputsource 1 0
with no visible result for me.

But now I can see at least 1 screen from 2 screens plugged in the docking station there. If I plug the other screen directly on the laptop, I can manage to get my two screens getting a signal.

The screen, which is plugged on the docking station, is switched off by default Ubuntu's display settings (the GUI). I can switch it on in the display settings and then it "kind of" works.

What means "kind of"? The mouse-cursor on this screen is slow and sometimes it takes a few seconds until I get feedback. The mouse coursor "hangs" then. So the functionality is not working properly.

After I reboot the system, I need to execute the console commands again and switch on the screen in ubuntu's GUI display settings again.

Well, something works not properly. I have created the logs-archive again and attached it. What is this KMU? Is there a chance to get the screens working properly or must the driver be modified?

P.S: If I plug the screen off, which is plugged in on my laptop, the screen which is plugged in into the docking station reacts quicker. This hangs and slowness disappears then. It seems the system cannot handle one screen directly in the laptop's HDMI port and one screen plugged into the docking station in a "quick reacting" way.

I have also tried to plug in the 1 screen on the docking station into the other port of it. But only 1 specific HDMI port from the docking station works. I have tried all xrandr options which I have mentioned in this post.
Attached Files
File Type: zip computer_2016-11-25T15:24:03.242253.zip (255.7 KB, 1 views)

Last edited by jepster; 11-25-2016 at 02:41 PM. Reason: More findings.
jepster is offline   Reply With Quote
Old 11-29-2016, 08:48 AM   #16
jepster
Junior Member
 
Join Date: Oct 2016
Posts: 28
Question

@mlukaszek: Could you please be so kind and reply?
jepster is offline   Reply With Quote
Old 12-02-2016, 12:34 PM   #17
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

Looking at the output from xrandr I am not optimistic this can work. On machines we tried so far internally even the NVIDIA driver alone doesn't work when set to modeset-compatible mode (without our driver installed at all).

Cheers,
Michal
mlukaszek is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 01:56 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.