Ubuntu
linux package

DisplayLink Attached Display Adapter and Monitor Not Recognized

Bug #1376771 reported by Dennis Gesker
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059

All ports on the device are recocognized and function correctly except the display adapter.

Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10

This problem also exists under trusty. 14.04

My intention is to drive 2 external monitors with this device.
This specific device has no issues under Windows 8.1

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-20-generic 3.16.0-20.27
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: gesker 2140 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 2 08:54:53 2014
HibernationDevice: RESUME=UUID=8d719d41-d691-447b-8dd0-29bbdd631465
InstallationDate: Installed on 2014-08-24 (38 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: System76, Inc. Gazelle Professional
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-20-generic root=UUID=5dc9a0a5-84ba-495e-b644-8d11f37bece5 ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-20-generic N/A
 linux-backports-modules-3.16.0-20-generic N/A
 linux-firmware 1.134
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-09-26 (5 days ago)
dmi.bios.date: 05/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Gazelle Professional
dmi.board.vendor: System76, Inc.
dmi.board.version: gazp7
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/16/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp7:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp7:cvnNoEnclosure:ct9:cvrN/A:
dmi.product.name: Gazelle Professional
dmi.product.version: gazp7
dmi.sys.vendor: System76, Inc.

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Displaylink Attached Display Adapater and Monitor Not Recognized

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Dennis Gesker (dennis-gesker) wrote :

Just downloaded and installed:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/linux-image-3.17.0-031700rc7-generic_3.17.0-031700rc7.201409281835_amd64.deb

Same behavior. Displaylink Attached Display Adapater and Monitor Not Recognized

tags: added: kernel-bug-exists-upstream
Revision history for this message
Dennis Gesker (dennis-gesker) wrote :

I changed status to confirmed. I think this was a mistake for me to do that as I am the reporter. Apologies if I did not follow correct procedure.

But, it did not work with latest v3.17 kernel

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc7-utopic/linux-image-3.17.0-031700rc7-generic_3.17.0-031700rc7.201409281835_amd64.deb

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Dennis Gesker (dennis-gesker) wrote : Re: [Bug 1376771] Re: Displaylink Attached Display Adapater and Monitor Not Recognized

Hi Joseph:

I will do that. But, need a hint. There seem to be MANY lists on kernel.org.
Which one is the right one?

--drg

On Thu, Oct 2, 2014 at 1:01 PM, Joseph Salisbury <
<email address hidden>> wrote:

> This issue appears to be an upstream bug, since you tested the latest
> upstream kernel. Would it be possible for you to open an upstream bug
> report[0]? That will allow the upstream Developers to examine the issue,
> and may provide a quicker resolution to the bug.
>
> Please follow the instructions on the wiki page[0]. The first step is to
> email the appropriate mailing list. If no response is received, then a
> bug may be opened on bugzilla.kernel.org.
>
> Once this bug is reported upstream, please add the tag: 'kernel-bug-
> reported-upstream'.
>
> [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1376771
>
> Title:
> Displaylink Attached Display Adapater and Monitor Not Recognized
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1376771/+subscriptions
>

Revision history for this message
Dennis Gesker (dennis-gesker) wrote : Re: Displaylink Attached Display Adapater and Monitor Not Recognized
Download full text (48.1 KiB)

Sent the following message to the <email address hidden> list. I hope it was the correct list....

Apologies in advance if I'm posting to the wrong list. I began by filing this as a bug on launchpad.net. Folks on that site indicated that it should be filed at kernel.org as it is upstream but not until after asking first on the mailling lists. My issue touches many parts usb/graphics/etc so I tried to choose the most general list.

Below is my collected information. Please let me know If I should post to a different list or if this is OK to file in the bug system.

Thanks,
Dennis

[1.] One line summary of the problem:

Displaylink Attached Display Adapater and Monitor Not Recognized

[2.] Full description of the problem/report:

DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059

All ports on the device are recocognized and function correctly except
the display adapter. My intention is to drive 2 external monitors with this device.

[3.] Keywords

[4.] Kernel version

Linux version 3.17.0-031700rc7-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201409281835 SMP Sun Sep 28 22:36:30 UTC 2014

[5.] Output of Oops

N/A

[6.] A small shell script or example program which triggers the problem (if possible)

N/A

[7.] Environment

Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10

[7.1.] Software (add the output of the ver_linux script here)

linux-headers-3.17.0-031700rc7-generic_3.17.0-031700rc7.201409281835_amd64.deb failed to install. Could not override with --force. So, could not run ver_linux script.

[7.2.] Processor information (from /proc/cpuinfo):

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
stepping : 9
microcode : 0x12
cpu MHz : 1290.335
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 4589.68
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
stepping : 9
microcode : 0x12
cpu MHz : 1224.031
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nons...

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :
Download full text (35.1 KiB)

A participant on the list wanted my Xorg logs. i submitted:

On this device

DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059

I did have an hp keyboard and mouse also plugged in...

X.Org X Server 1.16.0
Release Date: 2014-07-16
[ 9.901] X Protocol Version 11, Revision 0
[ 9.901] Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
[ 9.901] Current Operating System: Linux drgnbk
3.17.0-031700rc7-generic #201409281835 SMP Sun Sep 28 22:36:30 UTC
2014 x86_64
[ 9.901] Kernel command line:
BOOT_IMAGE=/@/boot/vmlinuz-3.17.0-031700rc7-generic
root=UUID=5dc9a0a5-84ba-495e-b644-8d11f37bece5 ro rootflags=subvol=@
quiet splash vt.handoff=7
[ 9.901] Build Date: 10 September 2014 01:10:01PM
[ 9.901] xorg-server 2:1.16.0-1ubuntu1 (For technical support
please see http://www.ubuntu.com/support)
[ 9.901] Current version of pixman: 0.32.4
[ 9.901] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 9.901] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 9.901] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 2
10:42:03 2014
[ 9.901] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 9.901] (==) No Layout section. Using the first Screen section.
[ 9.901] (==) No screen section available. Using defaults.
[ 9.901] (**) |-->Screen "Default Screen Section" (0)
[ 9.901] (**) | |-->Monitor "<default monitor>"
[ 9.901] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 9.901] (==) Automatically adding devices
[ 9.901] (==) Automatically enabling devices
[ 9.901] (==) Automatically adding GPU devices
[ 9.901] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 9.901] Entry deleted from font path.
[ 9.901] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 9.901] Entry deleted from font path.
[ 9.901] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 9.901] Entry deleted from font path.
[ 9.901] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 9.901] Entry deleted from font path.
[ 9.901] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 9.901] Entry deleted from font path.
[ 9.901] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[ 9.901] (==) ModulePath set to
"/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[ 9.901] (II) The server relies on udev to provide the list of
input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 9.901] (II) Loader magic: 0x7fedb59b7d80
[ 9.902] (II) Module ABI versions:
[ 9.902] X.Org ANSI C Emulation: 0.4
[ 9.902] X.Org Video Driver: 18.0
[ 9.902] X.Org XInput driver : 21.0
[ 9.902] X.Org Server Extension : 8.0
[ 9.902] (II) xfree86: Adding drm device (/dev/dri/...

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :
Download full text (82.5 KiB)

<email address hidden> pointed me to <email address hidden>

Here is my new post to that list...Displaylink USB 3.0 Attached Display Adapater and Monitor Not Recognized
DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059

Apologies in advance if I'm posting to the wrong list.

I began by filing this as a bug on launchpad.net.
Folks on that site indicated that it should be filed at kernel.org as it is upstream but not until after asking first on the mailling lists.

My issue touches many parts usb/graphics/laptops/etc so I tried to choose what I thought was the most general list: linux-x86_64

Since the chip set in this docking station (port replicator) is a little newer it was suggested on the <email address hidden> that perhaps I should post to linux-kernel.

Below is my collected information.

Please let me know If I should post to a different list or if this is OK to file in the bug system. Or, if since this chip set might be considered newer, if should file a feature/enhancement request in the bug system.

Thanks,
Dennis

[1.] One line summary of the problem:

Displaylink Attached Display Adapater and Monitor Not Recognized

[2.] Full description of the problem/report:

DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059

All ports on the device are recocognized and function correctly except
the display adapter. My intention is to drive 2 external monitors with
this device.

[3.] Keywords

[4.] Kernel version

Linux version 3.17.0-031700rc7-generic (apw@gomeisa) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201409281835 SMP Sun Sep 28
22:36:30 UTC 2014

[5.] Output of Oops

N/A

[6.] A small shell script or example program which triggers the
problem (if possible)

N/A

[7.] Environment

Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10

[7.1.] Software (add the output of the ver_linux script here)

linux-headers-3.17.0-031700rc7-generic_3.17.0-031700rc7.201409281835_amd64.deb
failed to install. Could not override with --force. So, could not run
ver_linux script.

[7.2.] Processor information (from /proc/cpuinfo):

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
stepping : 9
microcode : 0x12
cpu MHz : 1290.335
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl
vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln
pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
xsaveopt
bugs :
bogomips : 4589.68
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family :...

penalvch (penalvch)
tags: added: trusty
summary: - Displaylink Attached Display Adapater and Monitor Not Recognized
+ DisplayLink Attached Display Adapter and Monitor Not Recognized
Revision history for this message
Dennis Gesker (dennis-gesker) wrote :
Download full text (47.3 KiB)

Upstream on the lists the flow has been:

linux-x86_64 sent me to linux-kernel
linux-kernel sent me to linux-usb

Copy of post to linux-usb is as follows....

Apologies in advance if I'm posting to the wrong list. I began by
filing this as a bug on launchpad.net. Folks on that site indicated
that it should be filed at kernel.org as it is upstream but not until
after asking first on the mailling lists.
My issue touches many parts usb/graphics/etc so I tried to choose the most general list.

linux-x86_64 sent me to linux-kernel
linux-kernel sent me to linux-usb

Below is my collected information. Please let me know If I should post
to a different list or if this is OK to file in the bug system.

Thanks,
Dennis

[1.] One line summary of the problem:

Displaylink Attached Display Adapater and Monitor Not Recognized

[2.] Full description of the problem/report:

DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059

All ports on the device are recognized and function correctly except
the display adapter. My intention is to drive 2 external monitors with
this device.

[3.] Keywords

[4.] Kernel version

Linux version 3.17.0-031700rc7-generic (apw@gomeisa) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201409281835 SMP Sun Sep 28
22:36:30 UTC 2014

[5.] Output of Oops

N/A

[6.] A small shell script or example program which triggers the
problem (if possible)

N/A

[7.] Environment

Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10

[7.1.] Software (add the output of the ver_linux script here)

linux-headers-3.17.0-
031700rc7-generic_3.17.0-031700rc7.201409281835_amd64.deb
failed to install. Could not override with --force. So, could not run
ver_linux script.

[7.2.] Processor information (from /proc/cpuinfo):

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
stepping : 9
microcode : 0x12
cpu MHz : 1290.335
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl
vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln
pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
xsaveopt
bugs :
bogomips : 4589.68
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
stepping : 9
microcode : 0x12
cpu MHz : 1224.031
cache size : 6144 KB
physical id : 0
siblings : 8
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse...

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :
Download full text (72.0 KiB)

<email address hidden> asked for outpu from lsusb -v:

Bus 002 Device 003: ID 04f2:b34c Chicony Electronics Co., Ltd
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 239 Miscellaneous Device
  bDeviceSubClass 2 ?
  bDeviceProtocol 1 Interface Association
  bMaxPacketSize0 64
  idVendor 0x04f2 Chicony Electronics Co., Ltd
  idProduct 0xb34c
  bcdDevice 91.57
  iManufacturer 1
  iProduct 2
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 903
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 500mA
    Interface Association:
      bLength 8
      bDescriptorType 11
      bFirstInterface 0
      bInterfaceCount 2
      bFunctionClass 14 Video
      bFunctionSubClass 3 Video Interface Collection
      bFunctionProtocol 0
      iFunction 4
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 14 Video
      bInterfaceSubClass 1 Video Control
      bInterfaceProtocol 0
      iInterface 4
      VideoControl Interface Descriptor:
        bLength 13
        bDescriptorType 36
        bDescriptorSubtype 1 (HEADER)
        bcdUVC 1.00
        wTotalLength 79
        dwClockFrequency 30.000000MHz
        bInCollection 1
        baInterfaceNr( 0) 1
      VideoControl Interface Descriptor:
        bLength 28
        bDescriptorType 36
        bDescriptorSubtype 6 (EXTENSION_UNIT)
        bUnitID 6
        guidExtensionCode {b0d0bb68-a461-834b-90b7-a6215f3c4f70}
        bNumControl 24
        bNrPins 1
        baSourceID( 0) 2
        bControlSize 3
        bmControls( 0) 0xff
        bmControls( 1) 0xff
        bmControls( 2) 0xff
        iExtension 0
      VideoControl Interface Descriptor:
        bLength 18
        bDescriptorType 36
        bDescriptorSubtype 2 (INPUT_TERMINAL)
        bTerminalID 1
        wTerminalType 0x0201 Camera Sensor
        bAssocTerminal 0
        iTerminal 0
        wObjectiveFocalLengthMin 0
        wObjectiveFocalLengthMax 0
        wOcularFocalLength 0
        bControlSize 3
        bmControls 0x00000004
          Auto-Exposure Priority
      VideoControl Interface Descriptor:
        bLength 11
        bDescriptorType 36
        bDescriptorSubtype 5 (PROCESSING_UNIT)
      Warning: Descriptor too short
        bUnitID ...

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :
Download full text (78.2 KiB)

Alan Stern's Response:

> By the way, Alan. Thank you for looking at that. I'd really like to
> get this working. --drg

Well, I'm not so much looking at this as trying to collect information
that will help the people who do know what to look for. The standard
information requested by the "Submitting Bugs" form is almost
completely useless for USB-related problems.

> On Wed, Oct 8, 2014 at 2:23 PM, Alan Stern <email address hidden> wrote:
> > lsusb -v

I also asked for the dmesg output. What does that show?
Okay. I don't know if Linux supports this or not. If it does, the
relevant driver is udl. Is CONFIG_DRM_UDL enabled in your kernel
configuration?

Note that Displaylink has claimed they will add Linux support at some
indefinite time in the future, but they haven't added it yet. Alan Cox
told you this back on October 6, but apparently you didn't pay
attention to what he or Oliver Neukum wrote.

Information supplied in response to Alan:

I did see that note and link but it was an to a pretty old thread. I figured something must have happend on this since then. There seem to be quite a few products with these displaylink chip sets in them.

If its really just a bad product as as far as linux goes could you recommend other USB to Dual Monitor product that is supported?

CONFIG_DRM_UDL=m

dmesg..

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.17.0-031700rc7-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201409281835 SMP Sun Sep 28 22:36:30 UTC 2014
[ 0.000000] Command line: BOOT_IMAGE=/@/boot/vmlinuz-3.17.0-031700rc7-generic root=UUID=5dc9a0a5-84ba-495e-b644-8d11f37bece5 ro rootflags=subvol=@ quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000040005000-0x00000000d9c08fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000d9c09000-0x00000000da098fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000da099000-0x00000000da099fff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000da09a000-0x00000000da1b7fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000da1b8000-0x00000000da64dfff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000da64e000-0x00000000da64efff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000da64f000-0x00000000da691fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000da692000-0x00000000dad8cfff] usable
[ 0...

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :
Download full text (150.9 KiB)

Hello <email address hidden>:

This might be charging at windmills but I'm going to try...

So far my path has been launchpad.net to linux-x86_64 to linux-kernel to linux-kernel to linux-usb

linux-usb recommend I try linux-fbdev and reach out to Bernie Thompson -- who seems to be the maintainer of udl.

I want to drive a couple of monitors off of a USB 3 port. But, I can't seem to get my device to work. My device is a

DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059

I'm not die hard dedicated to this particular product. But, it does seem to have the characteristics of most of the products I've found that would seem let me drive monitors off of a USB 3.0 port in that it is running a DisplayLink chip set.

Some options offered on the others lists (besides ask on a different list) is to send it back and referrals to threads that are a couple of years old indicating that the product line / chip set is not supported. I'm hoping that something of this kind -- after all this time -- is supported and can be made to work with Linux.

I do know that the hardware of both the notebook and the USB display adapter are OK as they operate as expected in a different environment. Under Linux all of the features of this "DisplayLink Plug and Play Universal docking Station" work properly -- except of course the display adapter.

By the way, I am very open to alternative known working product recommendations if this product is simply a "no go."

Am I running into a true bug and should file it as such? Or, is this a feature request and I should file it as such? Is there something I can try?

I've tried to include all the info I could from the standard bug report format. I've also included lsusb -v, dmesg and CONFIG_DRM_UDL=m output as requested by members of previous lists to which I have posted.

I'd be grateful for any help and or direction.

Thank you so much in advance,
Dennis

[1.] One line summary of the problem:

Displaylink Attached Display Adapater and Monitor Not Recognized

[2.] Full description of the problem/report:

DisplayLink Plug and Play Universal docking Station
DELL
Model: D3000
MFG: ACP075US
SN: 1309017059

All ports on the device are recocognized and function correctly except
the display adapter. My intention is to drive 2 external monitors with
this device.

[3.] Keywords

[4.] Kernel version

Linux version 3.17.0-031700rc7-generic (apw@gomeisa) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201409281835 SMP Sun Sep 28
22:36:30 UTC 2014

[5.] Output of Oops

N/A

[6.] A small shell script or example program which triggers the
problem (if possible)

N/A

[7.] Environment

Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10

[7.1.] Software (add the output of the ver_linux script here)

linux-headers-3.17.0-031700rc7-generic_3.17.0-031700rc7.201409281835_amd64.deb
failed to install. Could not override with --force. So, could not run
ver_linux script.

[7.2.] Processor information (from /proc/cpuinfo):

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
stepping : 9
microcode : 0x12
cpu MHz...

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :

response from linux-fbdev:

Hi Dennis,

Only drivers for DisplayLink's USB 2.0 generation chips (DL-1x5) are available and in kernel. That Dell dock is using the newer DL-3x00 chips. There's no way to get the graphics portion working for Linux on that.

Part of the reason is even for USB 2.0 graphics devices where the driver is in kernel, getting anything working is very distro and component-version dependent. You'll see a few success stories if you search around, but they're fleeting. In short, it's not for any normal user. For the longer story (if you have a USB 2.0 generation device), see http://plugable.com/2014/03/06/displaylink-usb-2-0-graphics-adapters-on-linux-2014-edition
.
By the way, programmatically you can tell the difference between the DL-1x5 chips and the newer ones by these portions of the USB descriptors:
  idVendor 0x17e9 DisplayLink [this is the vendor ID for all DisplayLink chips, regardless of brand of product they're used in]
  Configuration Descriptor:
    Interface Descriptor:
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 3 [DL-3x0 chips with in-kernel support have bInterfaceProtocol=3. Later protocols are not supported]

This is how they're distinguished in uldfb (the fbdev driver I helped with) and udl (the DRM driver David Airlie created).

Sorry for the bad news,
Bernie

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :

I very much appreciate the cordial response from Bernie. Bernie Thompson is a gentleman.

Much of the response in regards to seeking help from those who are indeed the experts "upstream" was short, curt, arrogant and condescending.

Getting help with bugs upstream is hard.

I would like to update the status of this report but S.O.L. is doesn't seem to be an option.

Again, thank you Bernie Thompson. Plugable will now be my first stop always for accessories as when I spend money with my organization I would like to spend it with folks with the sense to have a guy like Bernie Thompson on staff.

That being said I hope plugable adds more Linux support so I can spend money with that company.

https://launchpad.net/~jsalisbury Thank you and please advice on what I should do with the status of this report.

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :

Bernie:

Thank you for your response. I can't tell you how much I appreciate your good manners. Reporting bugs "upstream" is hard for regular users.

If you are doing testing on Linux for products from your company please let me know so I can buy and help you test any drivers/products you are trying to get to market.

Thank you so much,
Dennis

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :

<email address hidden> offered this link:

https://lkml.org/lkml/2013/7/23/121

Revision history for this message
Dennis Gesker (dennis-gesker) wrote :

By the way...

I wanted to apologize for the "curt, arrogant and condescending" part of my post in #16 on this bug. I know those guys on the development lists are busy and responding to many inquiries.

Still, I very much appreciate the cordial response from Bernie.

And, if anyone knows of a product that would allow Ubuntu/Linux to reliably drive a couple of monitors off a USB 3.0 port please let me know.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

FYI an update from last October regarding the technical hurdles with USB3 DisplayLink: http://airlied.livejournal.com/80307.html

Because of HDCP, the products based on USB3 DisplayLink are not of use currently.

Revision history for this message
Nish Aravamudan (nacc) wrote :

Not sure if this will really help here, but I have a D3100 and I was able to drive two monitors using http://www.displaylink.com/downloads/ubuntu on 16.04. 16.10 again breaks it since the out-of-tree driver doesn't build against the later kernels (or so it seems). I wonder if this is something worth packaging into Ubuntu proper (or contacting DisplayLink about).

Revision history for this message
Nish Aravamudan (nacc) wrote :

Re-tested in 16.10, and the displaylink driver does work, but is much much laggier than in 16.04. Not yet had a chance to debug that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.