Amotz

My feedback

  1. 264 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  DisplayLink Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Gathering Feedback  ·  Wim responded

    This is on the backlog of Linux work, but is possible to be addressed by the community.

    It is possible the issue could be fixed with changes to the EVDI driver, which is an open source component available on github here:

    https://github.com/DisplayLink/evdi

    Amotz supported this idea  · 
    An error occurred while saving the comment
    Amotz commented  · 

    On my machine it seems related to not detecting nvidia on /dev/fb0 and try to use it instead of /dev/fb1.
    Though the relevant code might be in https://github.com/DisplayLink/evdi/blob/devel/module/evdi_fb.c, it is hard to understand how it is used and debug without the rest of the driver.
    Do you already know more on this issue? Is there an opened ticket with more information, or a tester to recreate the issue without the proprietary driver?

    (I'm with Linux-4.4.0-57-generic-x86_64-with-Ubuntu-16.04-xenial, EVDI 1.2.64, Plugable UGA-4KDP, and Nvidia GT216GLM nvidia-340.98)

Feedback and Knowledge Base