View Single Post
Old 08-18-2016, 12:00 AM   #5
RobertCochran
Junior Member
 
Join Date: Aug 2016
Posts: 12
Default

Quote:
Originally Posted by mlukaszek View Post
It is hard to tell exactly what's happening, but DisplayLinkManager clearly has some problems with connecting to EVDI nodes on your machine - as in, I am certain that a call to evdi_connect fails, but it may even not get to this - our logging is not too verbose by default so can't tell for sure without a repro.
I have debug printout patches in both evdi and libevdi. In my tests with these versions, the call never happens.

Quote:
Originally Posted by mlukazek View Post
Is it possible that this started since an update of the package? Has it ever worked for you, using a previous version for example?
No, I've only ever used this package. I haven't had my displays long enough to use any prior version.

Quote:
Originally Posted by mlukazek View Post
Edit: I managed to upgrade my FC23 installation to FC24 (running 4.6.6) and tried the RPM you linked with two identical ASUS monitors. As you see they worked for me. Obviously my host is different.

Attachment 2823
Unsurprising, given my relative lack of luck compared to other people I've had try. :P

Quote:
Originally Posted by mlukazek View Post
Could you try with Ubuntu on your setup for comparison?
I'm willing to try it, but I'm not sure how to go about this. I'm certainly not going to install Ubuntu over top my existing Fedora system. Would booting from a USB image be alright?

Quote:
Originally Posted by mlukazek View Post
If possible I recommend trying with a shorter/better quality USB cable, and/or a connection through a powered hub.
The cables I'm using are the ASUS OEM ones, and they are also the only 3.0 USB Micro cables I own.

I'll try with a powered hub, but I'm not sure what that will do me. Even if it did work, needing a second power socket would kinda suck; I was not anticipating needing a powered hub for this, especially considering I can plug in directly in Windows.

EDIT: Powered hub did not make a difference.

Quote:
Originally Posted by mlukazek View Post
You also mention that the monitors work with Windows. If you use another O/S, it's possible that a firmware package for the monitors is being changed upon connecting - and with these monitors it can take quite long (can be about 30 secs I think), and Linux driver does not show any notifications that this is happening.
Can you connect one of them and keep it connected for longer to be sure that the firmware image is fully flashed to it? The logo should appear for a moment, then the screen turns black during the update, then the logo should reappear for a moment and soon after this the driver should start displaying pixels. If this succeeds, try with the second screen.
I ensured that the flashing had completed (the monitor did exactly as described). No change.

Quote:
Originally Posted by mlukazek View Post
PS: Sorry for a delay, it's a holiday season and things are a bit slower than usual
Eh, slightly unhappy that things have been going slow, but all will be forgiven if we can get things to work.

Thanks for your assistance.

~RobertCochran

Last edited by RobertCochran; 08-18-2016 at 12:10 AM. Reason: Powered HUB made no difference
RobertCochran is offline   Reply With Quote