DisplayLink drivers on Ubuntu 17.10

Update: Driver version 1.4 works on 17.10 without hacks mentioned below. 

(there is whole journey of me and DisplayLink, NVidia, Intel and Dell troublemakers - see here and here and here)

After last updates I ended up with unbelievably annoying flickering, and sometimes completely missing, cursor on main display.

Desperate people do desperate actions. So I have tried to upgrade to Ubuntu 17.10 with kernel 4.13. Attempt to install “DisplayLink USB Graphics Software for Ubuntu 1.3.54” failed with following issue:

/var/lib/dkms/evdi/1.3.54/build/evdi_gem.c: In function ‘evdi_prime_create’:
/var/lib/dkms/evdi/1.3.54/build/evdi_gem.c:276:15: error: implicit declaration of function ‘drm_malloc_ab’; did you mean ‘dma_alloc_wc’? [-Werror=implicit-function-declaration]
 obj->pages = drm_malloc_ab(npages, sizeof(struct page *));
 ^~~~~~~~~~~~~
 dma_alloc_wc

I have asked on forum when 17.10 will be supported. Meanwhile there is workaround:

1. Download 1.3.54 driver from http://www.displaylink.com/downloads/ubuntu
2. Run installer with parameter keep ./displaylink-driver-1.3.54.run –keep
3. It fails, but in current directory there is folder displaylink-driver-1.3.54
4. There is file evdi-1.3.54-src.tar.gz, move it somewhere into temp directory
5. Unpack using tar -zxvf evdi-1.3.54-src.tar.gz
6. Replace evdi_gem.c by this file from this commit
7. Pack it again using tar cvzf evdi-1.3.54-src.tar.gz *
8. Replace original file in folder displaylink-driver-1.3.54
9. Install driver using ./displaylink-driver-1.3.54/displaylink-installer.sh install
10. Reboot computer, device should be recognized
11. But Gnome with Wayland will switch off because recognizes unsupported device. (when will be supported Wayland is a big question)
12. So first other shell is selected - Plasma in my case. Unfortunatelly most of packages is missing so nasty error appears.
13. Log out, and on login screen below credentials select cog and there Unity
14. Then it works except screen connected on DisplayLink shows only cursor
15. Apply workaround 2 from here, reboot computer
16. Voila!