Bug 1474081 - displaylink does not work
Summary: displaylink does not work
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-fbdev
Version: 26
Hardware: armv7l
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-23 18:29 UTC by Jussi Eloranta
Modified: 2018-05-29 12:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:28:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
xorg.log (14.53 KB, text/plain)
2017-07-23 18:29 UTC, Jussi Eloranta
no flags Details

Description Jussi Eloranta 2017-07-23 18:29:15 UTC
Created attachment 1303288 [details]
xorg.log

Description of problem: If I plug usb 2.0 displaylink device into my intel laptop (Fedora 26), it works as expected. However, doing the same with raspberry pi 3 does not work correctly. Actually, it kind of does when vc4 driver is used for the console (hdmi) but this driver is very unstable and unusuable for me at the moment. So, I have to run the console as fbdev. If I now add my displaylink device, it does not activate the screen attached to it. 

I think that the kernel side is probably OK (dmesg):

[ 5070.134942] usb 1-1.4: new high-speed USB device number 7 using dwc2
[ 5070.229295] usb 1-1.4: New USB device found, idVendor=17e9, idProduct=037b
[ 5070.229328] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5070.229343] usb 1-1.4: Product: Plugable USB-VGA-165
[ 5070.229355] usb 1-1.4: Manufacturer: DisplayLink
[ 5070.229367] usb 1-1.4: SerialNumber: 170609
[ 5072.631192] [drm] vendor descriptor length:1b data:1b 5f 01 00 19 05 00 01 03 00 04
[ 5072.851415] checking generic (3e5ff000 3f4800) vs hw (0 0)
[ 5072.852969] udl 1-1.4:1.0: fb1: udldrmfb frame buffer device
[ 5072.860881] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 5072.860905] [drm] No driver support for vblank timestamp query.
[ 5072.860983] [drm] Initialized udl 0.0.1 20120220 for 1-1.4:1.0 on minor 0
[ 5072.860993] [drm] Initialized udl on minor 0
[ 5072.861224] usbcore: registered new interface driver udl

I have also checked that this device should only take 500 mA max and the total current draw from USB should be within the specs.

This is what I see in xorg.log:

[    23.055] (**) Option "config_info" "udev:/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.1/0003:1C4F:0002.0003/input/input2/event2"
[    23.056] (II) XINPUT: Adding extended input device "SIGMACHIP USB Keyboard" (type: KEYBOARD, id 9)
[  5072.824] (II) config/udev: removing GPU device /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/drm/card0 /dev/dri/card0
[  5072.827] (II) config/udev: Adding drm device (/dev/dri/card0)
[  5072.827] (II) xfree86: Adding drm device (/dev/dri/card0)
[  5072.850] (II) LoadModule: "modesetting"
[  5072.853] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  5072.977] (II) Module modesetting: vendor="X.Org Foundation"
[  5072.978] 	compiled for 1.19.3, module version = 1.19.3
[  5072.978] 	Module class: X.Org Video Driver
[  5072.978] 	ABI class: X.Org Video Driver, version 23.0
[  5072.978] (II) modeset(G0): using drv /dev/dri/card0
[  5072.979] (II) modeset(G0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[  5072.979] (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
[  5072.979] (==) modeset(G0): RGB weight 888
[  5072.979] (==) modeset(G0): Default visual is TrueColor
[  5072.979] (II) Loading sub module "glamoregl"
[  5072.979] (II) LoadModule: "glamoregl"
[  5072.980] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[  5073.090] (II) Module glamoregl: vendor="X.Org Foundation"
[  5073.090] 	compiled for 1.19.3, module version = 1.0.0
[  5073.091] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  5073.091] (II) glamor: OpenGL accelerated X.org driver based.
[  5073.344] (II) glamor: EGL version 1.4 (DRI2):
[  5073.345] EGL_MESA_drm_image required.
[  5073.346] (EE) modeset(G0): glamor initialization failed
[  5073.346] (II) modeset(G0): ShadowFB: preferred NO, enabled NO
[  5073.499] (II) modeset(G0): Output DVI-I-1-1 has no monitor section
[  5073.660] (==) modeset(G0): Using gamma correction (1.0, 1.0, 1.0)
[  5073.660] (==) modeset(G0): DPI set to (96, 96)
[  5073.660] (II) Loading sub module "fb"
[  5073.660] (II) LoadModule: "fb"
[  5073.679] (II) Loading /usr/lib/xorg/modules/libfb.so
[  5073.679] (II) Module fb: vendor="X.Org Foundation"
[  5073.679] 	compiled for 1.19.3, module version = 1.0.0
[  5073.679] 	ABI class: X.Org ANSI C Emulation, version 0.4
[  5073.696] (==) modeset(G0): Backing store enabled
[  5073.696] (==) modeset(G0): Silken mouse enabled
[  5073.696] (II) modeset(G0): RandR 1.2 enabled, ignore the following RandR disabled message.
[  5073.727] (==) modeset(G0): DPMS enabled
[  5073.735] (II) modeset(G0): Damage tracking initialized
[  5073.739] xf86: found device 1


No display (or activity on displaylink device; including the green indicator led that is on when the device is in use). xrandr does not show the second screen either. I am attaching the full xorg.log.

If I configure Xorg to use just the displaylink device, it works fine (that is the console is not included in xorg conf). So, it seems that if the console is fbdev and the displaylink comes as second fbdev, things don't work.

Version-Release number of selected component (if applicable):


How reproducible: Use console as fbdev and trying plugging in usb 2.0 displaylink. This should give display rather than black screen.

Comment 1 Jussi Eloranta 2017-07-23 18:46:16 UTC
Forgot to say... I excluded vc4 by just blacklisting it in /etc/modprobe.d rather than doing anything with xorg configuration. This leads to xorg using it as fbdev.

Comment 2 Jussi Eloranta 2017-07-23 18:50:47 UTC
And this is what my intel (f26) box says when it is plugged in:

[   985.394] (II) config/udev: removing GPU device /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/drm/card2 /dev/dri/card2
[   985.395] (II) config/udev: Adding drm device (/dev/dri/card2)
[   985.395] (II) xfree86: Adding drm device (/dev/dri/card2)

Comment 3 GroovieMan 2018-04-22 11:12:52 UTC
Dear colleagues,

the display-link adapter is working on my Fedora F27. You need to add a special driver, that can be generated with this project as a rpm package, that needs to be installed.

Simple perform:

$ git clone https://github.com/displaylink-rpm/displaylink-rpm
$ make 

and then look into x86_64 (or i386) subdir, that will contain the package you have to install.

If you are running a plasma/kde desktop, you may run into a problem, when you try to configure the new displays. So firstly configure your desktop config with cinnamon or gnome and then you re-login with your KDE/Plasma desktop.

I have tested it with a StarTech.com USB->HDMI adapter on a 4K Display and a Dell USB-Docking-Station connected with 2 Dell HD monitors. It is running!

@Redhat/Fedora: Please support these adapter in future, you find them as a replacement for ole docking station in lot of office desktops.

Comment 4 GroovieMan 2018-04-22 11:15:43 UTC
oh sorry, my solution works with i386 and x86-64 hardware. So you may contact display-link to provide for a ARM implementation

Comment 5 Fedora End Of Life 2018-05-03 08:08:40 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2018-05-29 12:28:03 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.