The new driver release does not fix my issue.

I'm not going to change OSes for a stupid monitor. I shouldn't *have* to.

As far as I can see, you appear to be the only DisplayLink guy helping out in the
Linux subforum. It sucks, so I understand to a point. Still though:

1) I bought these monitors close to 2 months ago and haven't been able to use them.
2) I have done everything I can reasonably do to fix the problem from my end WRT code.
I looked through and worked out as much as I can of EVDI.
3) But the problem is in the proprietary part. So I can't fix it.
4) This could have been done and over with nearly 2 months ago if I could have fixed it
myself.
5) Now I have to wait on DisplayLink to fix the issue.
6) Support has been abysmal because they only have one freaking developer on the
Linux subforum.

None of that is necessarily /your/ fault; rather, DisplayLink as a whole. I'm not
attempting to single out and flame you in particular. I'm just done dealing with this issue.

This whole experience has been so bad that even *if* I'm able to get my monitors to
work, I'm never buying anything with DisplayLink inside again.

http://displaylink.org/forum/showthr...t=64026&page=5

Some folks are successful on Fedora. Did you try the RPM they prepared based on the latest release?

I still can't see what specific difference you have in your setup making it not compatible. You said that it works with Ubuntu - and we don't officially support any other distro, despite trying to assist in porting where we can. Sorry.

Cheers,
Michal

I tried the new 10/11 release a few days ago. Exact same thing still.