Fedora 24 AMD64: evdi_painter_crtc_state_notify:362 Painter does not exist! - Page 2

RobertCochran · 09-25-2016, 10:46 PM

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.

mlukaszek · 09-27-2016, 07:18 AM

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

RobertCochran · 10-22-2016, 04:56 AM

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

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

09-25-2016, 10:46 PM	#11
RobertCochran Junior Member Join Date: Aug 2016 Posts: 12	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.

09-27-2016, 07:18 AM	#12
mlukaszek Senior Member Join Date: Feb 2010 Posts: 386	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

10-22-2016, 04:56 AM	#13
RobertCochran Junior Member Join Date: Aug 2016 Posts: 12	I tried the new 10/11 release a few days ago. Exact same thing still.