Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Linux and Open Source

Reply
 
Thread Tools Search this Thread Display Modes
Old 02-25-2017, 06:14 AM   #1
rup
Junior Member
 
Join Date: Sep 2016
Posts: 11
Default v1.3.52 is not working with AOC e1649wu - Ubuntu 16.04

The new version is not working. Support tool output is attached.

I uninstalled the old driver, rebooted, and installed the new version. Using a brand-new high quality USB cable and a powered USB hub. The AOC monitor shows alternating magenta/cyan bands. If I move the mouse across the screen it leaves traces of the pointer.

Ubuntu 16.04 on an HP G72 laptop with an AOC e1649wu USB monitor as a secondary monitor. The older 1.1.68 driver release, works on this display except that the USB display will not come back on after suspend or after unplugging the USB display.

Please advise.
Attached Files
File Type: zip jr-HP_2017-02-24T23:00:04.406093.zip (32.4 KB, 1 views)
rup is offline   Reply With Quote
Old 02-27-2017, 08:01 AM   #2
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

I don't see evdi or DisplayLinkManager running. I do see udl trying to access the device instead though - which is not right for this device (and you should probably blacklist udl in modprobe.conf). How did the installation end?

Cheers,
Michal
mlukaszek is offline   Reply With Quote
Old 02-27-2017, 10:35 AM   #3
pev
Junior Member
 
Join Date: Jan 2017
Posts: 11
Default

I had a problem with the e1659 not working on my HP laptop running 16.04 where the installation would fail, not building evdi and it wasn't immediately obvious. If you check evdi.ko, does it exist with a non-zero size?
$ ls -l /lib/modules/$(uname -r)/updates/dkms/evdi.ko
pev is offline   Reply With Quote
Old 02-27-2017, 07:24 PM   #4
rup
Junior Member
 
Join Date: Sep 2016
Posts: 11
Default

I tried
Code:
ls -l /lib/modules/$(uname -r)/updates/dkms/evdi.ko
and the file did not exist. So I did
Code:
sudo displaylink-installer uninstall
and rebooted the computer.

after rebooting, I reinstalled with the following results:

Code:
jr@jr-HP:~/Downloads/DisplayLink$ sudo ./displaylink-driver-1.3.52.run
[sudo] password for jr: 
Verifying archive integrity... All good.
Uncompressing DisplayLink Linux Driver 1.3.52  100%  
DisplayLink Linux Software 1.3.52 install script called: install
Distribution discovered: Ubuntu 16.04.1 LTS
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64-ubuntu-1604/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing license file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices
jr@jr-HP:~/Downloads/DisplayLink$ ls -l /lib/modules/$(uname -r)/updates/dkms/evdi.ko
-rw-r--r-- 1 root root 95760 Feb 27 12:02 /lib/modules/4.4.0-64-generic/updates/dkms/evdi.ko
The displaylink monitor behavior is the same.
The new DLSupportTool output is attached.

I read pev's post about editing the makefile. My evdi makefile is also attached if it helps.

Thank you
Attached Files
File Type: zip jr-HP_2017-02-27T12:17:46.360350.zip (36.1 KB, 1 views)
File Type: zip Makefile.zip (860 Bytes, 1 views)
rup is offline   Reply With Quote
Old 02-28-2017, 08:15 AM   #5
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

Installation log look fine, but again, no signs of evdi but udl is loaded. As I suggested - do blacklist udl so it never attempts to open the device. Then reboot and connect the device - evdi should load and DLM should then start as well. What does `systemctl status dlm.service` show?

Cheers,
Michal
mlukaszek is offline   Reply With Quote
Old 02-28-2017, 09:04 AM   #6
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

Sorry - ignore my previous comments; I just realized this monitor is indeed a DL-1xx device and is driven by udl - 100% open-source module that your kernel contains. You don't need evdi nor DisplayLinkManager.

Cheers,
Michal
mlukaszek is offline   Reply With Quote
Old 02-28-2017, 05:31 PM   #7
rup
Junior Member
 
Join Date: Sep 2016
Posts: 11
Default

Please clarify on
Code:
You don't need evdi nor DisplayLinkManager.
The monitor does not light up at all unless I install the Displaylink software. If evdi and DisplayLinkManager are not required, how do I get the monitor to work?

As I mentioned in my initial post, The older 1.1.68 release intermittently works with this display except that the USB display will not come back on after suspend or after unplugging the USB display unless I reboot.

Can you please clarify for me the proper way to blacklist udl in modprobe.conf so that I do it properly.
Also:
Code:
jr@jr-HP:~$ systemctl status dlm.service
● dlm.service - DisplayLink Manager Service
   Loaded: loaded (/lib/systemd/system/dlm.service; static; vendor preset: enabl
   Active: inactive (dead)

Last edited by rup; 02-28-2017 at 05:40 PM.
rup is offline   Reply With Quote
Old 03-02-2017, 12:01 AM   #8
rup
Junior Member
 
Join Date: Sep 2016
Posts: 11
Default

So I did the following:

1) Added
Code:
blacklist udl
to etc/modprobe.d/blacklist.conf and rebooted. No change
2) Added
Code:
blacklist udlfb
to etc/modprobe.d/blacklist.conf and rebooted. No change

3) Ran the DLSupportTool. Output attached as jr-HP_2017-03-01T16:08:13.071021.zip

4) Removed the two blacklist entries and rebooted.

5) Removed evdi
Code:
sudo dkms remove evdi/1.3.52 --all
and rebooted. No change.

6) Removed displaylink
Code:
sudo displaylink-installer uninstall
and rebooted. Monitor does not work.

7) Ran the DLSupportTool. Output attached as jr-HP_2017-03-01T16:28:51.725975_uninstalled.zip

Please advise. This device does not function properly with or without the latest Displaylink software on Ubuntu 16.04. It works with no problems whatsoever without drivers on a windows machine. It is operational using the 1.1.62/68 software as long as I don't unplug it or suspend the computer. (which is a big handicap) I am very frustrated and about ready to abandon my efforts and give it to my toddler to use as a snow sled.
Attached Files
File Type: zip jr-HP_2017-03-01T16:08:13.071021.zip (33.6 KB, 0 views)
File Type: zip jr-HP_2017-03-01T16:28:51.725975_uninstalled.zip (34.5 KB, 0 views)

Last edited by rup; 03-02-2017 at 01:17 AM. Reason: added zips and clarification
rup is offline   Reply With Quote
Old 03-02-2017, 03:39 PM   #9
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

Well, the device is definitely DL-1xx based device. These should be supported by udl driver - and if they don't work the source is there to poke around.

Since 1.2 driver for newer devices, we've changed the udev rules so they would only match DL-3xxx/5xxx-based products, not to interfere with udl kernel module that should be driving the older chips. This is also why DisplayLinkManager would not even start.

Bottom line is, DL-1xx devices working with the new Ubuntu driver is not something we support. I will PM you later with some hints you might try though.

Cheers,
Michal
mlukaszek is offline   Reply With Quote
Old 02-08-2018, 03:25 PM   #10
Stevie White
Junior Member
 
Join Date: Feb 2018
Posts: 1
Default E1659Fwu Black Screen on host P50

Didn't read install instructions and plugged the E1659Fwu into my Lenovo Thinkpad P50.

Fix:


CD is included with product, if you don't have a CD drive on your machine, find one that does and copy the CD files to USB drive.

- Boot to Safe Mode
- Control Panel
- Display Adapter
- Disable Nvidia Quadro
- Boot to normal mode and install the drivers.

Everything is working for me.
Stevie White is offline   Reply With Quote
Reply

Tags
aoc, dl-125, e1649fwu, udl

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 06:36 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2021, vBulletin Solutions, Inc.