Fedora 24 AMD64: evdi_painter_crtc_state_notify:362 Painter does not exist!

[RobertCochran]

As it says on the title.

OS: Fedora 24 AMD64
Kernel: 4.6.4-301.fc24.x86_64
DisplayLink software: 1.1.65 (Installed from https://github.com/ssaavedra/displaylink-rpm/releases/download/v1.1.65-5/displaylink-1.1.65-5.x86_64.rpm)
Displays: ASUS MB169B+ x2

The ASUS logo is displayed then the screen turns back off when plugged in. No additional screens appear in any RandR tools.

Displays are known good: they work on this machine in Windows 10.
The RPM is known good: the driver works on another machine with Fedora 24 AMD64 and kernel 4.6.4-301.fc24.x86_64.

It doesn't seem to matter if I do one at a time or both of them at once.

The relevant portion of dmesg output:

[  119.773307] evdi: [D] add_store:195 Increasing device count to 1
[  119.775968] evdi: [D] evdi_crtc_init:304 drm_crtc_init: 0
[  119.776347] evdi: [W] evdi_painter_crtc_state_notify:362 Painter does not exist!
[  119.776359] evdi: [D] evdi_detect:72 Painter is disconnected
[  119.776373] evdi evdi.0: No connectors reported connected with modes
[  119.776381] [drm] Cannot find any crtc or sizes - going 1024x768
[  119.782981] evdi evdi.0: fb1: evdidrmfb frame buffer device
[  119.782996] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[  119.783003] [drm] No driver support for vblank timestamp query.
[  119.783009] [drm] evdi: evdi_stats_init
[  119.783034] [drm] Initialized evdi 1.1.65 20160512 on minor 1
[  119.878077] evdi: [W] evdi_painter_disconnect:462 (dev=0) An unknown connection to ffff88036f437a00 tries to close us
[  119.878086] evdi: [W] evdi_painter_disconnect:463  - ignoring

Output from the support tool:
SoraLaptop_2016-08-01T11:17:03.558863.zip

[RobertCochran]

So I've been digging around in the evdi module sources, and I've found something
that I find quite puzzling. Here's another dmesg excerpt, from a build of evdi
that I've added some debug printouts to, as well as being log level 6:

[  164.693328] evdi: [D] add_store:195 Increasing device count to 1
[  164.693646] evdi: [V] evdi_platform_probe:119 
[  164.695186] evdi: [V] evdi_driver_load:25 
[  164.695209] evdi: [V] evdi_driver_load:37 
[  164.695216] evdi: [V] evdi_modeset_init:368 
[  164.695284] evdi: [V] evdi_crtc_init:313 
[  164.695312] evdi: [D] evdi_crtc_init:319 drm_crtc_init: 0
[  164.695724] evdi: [V] evdi_flip_workqueue_init:331 
[  164.696221] evdi: [V] evdi_crtc_disable:112 
[  164.696227] evdi: [D] evdi_crtc_disable:118 No evdi->painter!
[  164.696234] evdi: [W] evdi_painter_crtc_state_notify:367 Painter does not exist!
[  164.696243] evdi: [V] evdi_detect:67 
[  164.696249] evdi: [D] evdi_painter_is_connected:170 No evdi->painter
[  164.696255] evdi: [D] evdi_detect:72 Painter is disconnected
[  164.696268] evdi evdi.0: No connectors reported connected with modes
[  164.696277] [drm] Cannot find any crtc or sizes - going 1024x768
[  164.700674] evdi evdi.0: fb1: evdidrmfb frame buffer device
[  164.700688] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[  164.700694] [drm] No driver support for vblank timestamp query.
[  164.700701] evdi: [V] evdi_painter_init:666 
[  164.700707] [drm] evdi: evdi_stats_init
[  164.700721] evdi: [W] evdi_driver_load:65 Painter present
[  164.700731] [drm] Initialized evdi 1.1.65 20160512 on minor 1
[  164.798994] evdi: [V] evdi_driver_preclose:108 
[  164.799008] evdi: [V] evdi_painter_close:502 
[  164.799016] evdi: [V] evdi_painter_disconnect:460 
[  164.799022] evdi: [V] painter_lock:153 
[  164.799033] evdi: [W] evdi_painter_disconnect:467 (dev=0) An unknown connection to ffff880340c6a200 tries to close us
[  164.799040] evdi: [W] evdi_painter_disconnect:468  - ignoring
[  164.799046] evdi: [V] painter_unlock:159 

Calls that lead back into evdi_modeset_init need to have the painter
available... before the painter is initialized in evdi_driver_load... I'm
either missing something fundamental about this, or something is fundamentally
broken...

Am I misunderstanding something here?

[RobertCochran]

More debugging indicates that for some reason, the evdi module is not receiving
the DRM_IOCTL_EVDI_CONNECT ioctl. This strongly indicates an issue in the
DisplayLinkManager executable to me.

[displaylink-mlukaszek]

I will close this issue here, and will follow up on DisplayLink forum. This problem does not look evdi-specific.