DisplayLink Forum - View Single Post - AOC e1649wu does not work with Ubuntu 16.04 with ALIENWARE R13

chirag712 · 04-20-2017, 02:06 AM

Hello,

I am not able to use AOC e1649wu with Ubuntu 16.04 with Alienware R13 laptop. I have a dual boot system, the device works perfectly fine in Windows 10. Moreover, I have checked with my friend's laptop - the device works fine in HP Envy with Ubuntu 16.04. I am using DisplayLink USB Graphics Software for Ubuntu 1.3.52 driver.

Attached are the log files generated using DisplaLink Linux tool.

I have disabled secure boot option as mentioned in some thread in the forum.

This is my uname -a output:

Code:

Linux thunderbolt 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Libusb output:

Code:

Bus 001 Device 002: ID 8087:8001 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 17e9:ff0c DisplayLink 
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0
Bus 002 Device 004: ID 187c:0527 Alienware Corporation 
Bus 002 Device 003: ID 0c45:6708 Microdia 
Bus 002 Device 002: ID 04f3:0441 Elan Microelectronics Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

From the thread: systemctl status dlm.service - shows following output

Code:

systemctl status dlm.service
● dlm.service - DisplayLink Manager Service
   Loaded: loaded (/lib/systemd/system/dlm.service; static; vendor preset: enabl
   Active: active (running) since Wed 2017-04-19 21:14:13 EDT; 21min ago
  Process: 2227 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install evdi/1.3.
 Main PID: 2231 (DisplayLinkMana)
   CGroup: /system.slice/dlm.service
           └─2231 /opt/displaylink/DisplayLinkManager

Apr 19 21:14:13 thunderbolt systemd[1]: Starting DisplayLink Manager Service...
Apr 19 21:14:13 thunderbolt systemd[1]: Started DisplayLink Manager Service.

Here, there was similar problem - and I get following output to http://www.displaylink.org/forum/sho...t=64438&page=2
modinfo drm

Code:

   filename:       /lib/modules/4.8.0-46-generic/kernel/drivers/gpu/drm/drm.ko
license:        GPL and additional rights
description:    DRM shared core routines
author:         Gareth Hughes, Leif Delgass, José Fonseca, Jon Smirl
license:        GPL and additional rights
description:    DRM bridge infrastructure
author:         Ajay Kumar <ajaykumar.rs@samsung.com>
license:        GPL and additional rights
description:    DRM panel infrastructure
author:         Thierry Reding <treding@nvidia.com>
srcversion:     2C719D2DB13DC5043515411
depends:        
intree:         Y
vermagic:       4.8.0-46-generic SMP mod_unload modversions 
parm:           edid_fixup:Minimum number of valid EDID header bytes (0-8, default 6) (int)
parm:           debug:Enable debug output, where each bit enables a debug category.
		Bit 0 (0x01) will enable CORE messages (drm core code)
		Bit 1 (0x02) will enable DRIVER messages (drm controller code)
		Bit 2 (0x04) will enable KMS messages (modesetting code)
		Bit 3 (0x08) will enable PRIME messages (prime code)
		Bit 4 (0x10) will enable ATOMIC messages (atomic code)
		Bit 5 (0x20) will enable VBL messages (vblank code) (int)
parm:           vblankoffdelay:Delay until vblank irq auto-disable [msecs] (0: never disable, <0: disable immediately) (int)
parm:           timestamp_precision_usec:Max. error on timestamps [usecs] (int)
parm:           timestamp_monotonic:Use monotonic timestamps (int)

Thank you for help,
Chirag