This problem is going on over six months now, and it’s been given peripheral attention, at best, when given any attention at all. If it’s being actively worked on — which would be great — we haven't heard about it.
DisplayLink team: What else can we do by way of logging, driver testing, or any other troubleshooting to help track this problem down? We’re willing to help solve this problem alongside you, but we can’t help if we aren’t hearing any communication that this is being worked on or even acknowledged.
|