Display Port via USB-c

displayportusb

I cannot get display port via usb-c working. I've tried 2 cables but no success. Xrandr simply can't see the external screen. I'm sure I'm missing any configuration or installed package but I have no idea where to start.

~ » uname -a 
Linux box 4.16.0-1-amd64 #1 SMP Debian 4.16.5-1 (2018-04-29) x86_64 GNU/Linux

When I plug in the screen (which has also built-in USB hub) I get this.

Jun 27 21:54:23 box kernel: [  208.841807] ACPI BIOS Error (bug): Failure creating [\_GPE.XTBT.SPRT], AE_ALREADY_EXISTS (20180105/dswload2-350)
Jun 27 21:54:23 box kernel: [  208.841826] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180105/psobject-252)
Jun 27 21:54:23 box kernel: [  208.841834] ACPI Error: Method parse/execution failed \_GPE.XTBT, AE_ALREADY_EXISTS (20180105/psparse-550)
Jun 27 21:54:23 box kernel: [  208.841847] ACPI Error: Method parse/execution failed \_GPE.XTBT, AE_ALREADY_EXISTS (20180105/psparse-550)
Jun 27 21:54:23 box kernel: [  208.841861] ACPI Error: Method parse/execution failed \_GPE._E42, AE_ALREADY_EXISTS (20180105/psparse-550)
Jun 27 21:54:23 box kernel: [  208.841873] ACPI Error: AE_ALREADY_EXISTS, while evaluating GPE method [_E42] (20180105/evgpe-646)
Jun 27 21:54:28 box kernel: [  213.956323] pci 0000:01:00.0: [8086:1576] type 01 class 0x060400
Jun 27 21:54:28 box kernel: [  213.956413] pci 0000:01:00.0: enabling Extended Tags
Jun 27 21:54:28 box kernel: [  213.956540] pci 0000:01:00.0: supports D1 D2
Jun 27 21:54:28 box kernel: [  213.956544] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 27 21:54:28 box kernel: [  213.957134] pci 0000:02:00.0: [8086:1576] type 01 class 0x060400
Jun 27 21:54:28 box kernel: [  213.957232] pci 0000:02:00.0: enabling Extended Tags
Jun 27 21:54:28 box kernel: [  213.957371] pci 0000:02:00.0: supports D1 D2
Jun 27 21:54:28 box kernel: [  213.957376] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 27 21:54:28 box kernel: [  213.957604] pci 0000:02:01.0: [8086:1576] type 01 class 0x060400
Jun 27 21:54:28 box kernel: [  213.957701] pci 0000:02:01.0: enabling Extended Tags
Jun 27 21:54:28 box kernel: [  213.957840] pci 0000:02:01.0: supports D1 D2
Jun 27 21:54:28 box kernel: [  213.957844] pci 0000:02:01.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 27 21:54:28 box kernel: [  213.958060] pci 0000:02:02.0: [8086:1576] type 01 class 0x060400
Jun 27 21:54:28 box kernel: [  213.958157] pci 0000:02:02.0: enabling Extended Tags
Jun 27 21:54:28 box kernel: [  213.958323] pci 0000:02:02.0: supports D1 D2
Jun 27 21:54:28 box kernel: [  213.958328] pci 0000:02:02.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 27 21:54:28 box kernel: [  213.958606] pci 0000:01:00.0: PCI bridge to [bus 02-39]
Jun 27 21:54:28 box kernel: [  213.958627] pci 0000:01:00.0:   bridge window [mem 0xc4000000-0xda0fffff]
Jun 27 21:54:28 box kernel: [  213.958642] pci 0000:01:00.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
Jun 27 21:54:28 box kernel: [  213.958769] pci 0000:02:00.0: PCI bridge to [bus 03]
Jun 27 21:54:28 box kernel: [  213.958789] pci 0000:02:00.0:   bridge window [mem 0xda000000-0xda0fffff]
Jun 27 21:54:28 box kernel: [  213.958919] pci 0000:02:01.0: PCI bridge to [bus 04-38]
Jun 27 21:54:28 box kernel: [  213.958938] pci 0000:02:01.0:   bridge window [mem 0xc4000000-0xd9efffff]
Jun 27 21:54:28 box kernel: [  213.958952] pci 0000:02:01.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
Jun 27 21:54:28 box kernel: [  213.959144] pci 0000:39:00.0: [8086:15b5] type 00 class 0x0c0330
Jun 27 21:54:28 box kernel: [  213.959205] pci 0000:39:00.0: reg 0x10: [mem 0xd9f00000-0xd9f0ffff]
Jun 27 21:54:28 box kernel: [  213.959332] pci 0000:39:00.0: enabling Extended Tags
Jun 27 21:54:28 box kernel: [  213.959504] pci 0000:39:00.0: supports D1 D2
Jun 27 21:54:28 box kernel: [  213.959510] pci 0000:39:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Jun 27 21:54:28 box kernel: [  213.959876] pci 0000:02:02.0: PCI bridge to [bus 39]
Jun 27 21:54:28 box kernel: [  213.959896] pci 0000:02:02.0:   bridge window [mem 0xd9f00000-0xd9ffffff]
Jun 27 21:54:28 box kernel: [  213.959956] pci_bus 0000:02: Allocating resources
Jun 27 21:54:28 box kernel: [  213.960021] pci 0000:02:01.0: bridge window [io  0x1000-0x0fff] to [bus 04-38] add_size 1000
Jun 27 21:54:28 box kernel: [  213.960043] pci 0000:02:02.0: bridge window [io  0x1000-0x0fff] to [bus 39] add_size 1000
Jun 27 21:54:28 box kernel: [  213.960052] pci 0000:02:02.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 39] add_size 200000 add_align 100000
Jun 27 21:54:28 box kernel: [  213.960074] pci 0000:01:00.0: bridge window [io  0x1000-0x0fff] to [bus 02-39] add_size 2000
Jun 27 21:54:28 box kernel: [  213.960085] pci 0000:01:00.0: BAR 13: no space for [io  size 0x2000]
Jun 27 21:54:28 box kernel: [  213.960091] pci 0000:01:00.0: BAR 13: failed to assign [io  size 0x2000]
Jun 27 21:54:28 box kernel: [  213.960096] pci 0000:01:00.0: BAR 13: no space for [io  size 0x2000]
Jun 27 21:54:28 box kernel: [  213.960100] pci 0000:01:00.0: BAR 13: failed to assign [io  size 0x2000]
Jun 27 21:54:28 box kernel: [  213.960111] pci 0000:02:02.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Jun 27 21:54:28 box kernel: [  213.960115] pci 0000:02:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Jun 27 21:54:28 box kernel: [  213.960118] pci 0000:02:01.0: BAR 13: no space for [io  size 0x1000]
Jun 27 21:54:28 box kernel: [  213.960123] pci 0000:02:01.0: BAR 13: failed to assign [io  size 0x1000]
Jun 27 21:54:28 box kernel: [  213.960135] pci 0000:02:02.0: BAR 13: no space for [io  size 0x1000]
Jun 27 21:54:28 box kernel: [  213.960142] pci 0000:02:02.0: BAR 13: failed to assign [io  size 0x1000]
Jun 27 21:54:28 box kernel: [  213.960155] pci 0000:02:02.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Jun 27 21:54:28 box kernel: [  213.960161] pci 0000:02:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Jun 27 21:54:28 box kernel: [  213.960168] pci 0000:02:02.0: BAR 13: no space for [io  size 0x1000]
Jun 27 21:54:28 box kernel: [  213.960173] pci 0000:02:02.0: BAR 13: failed to assign [io  size 0x1000]
Jun 27 21:54:28 box kernel: [  213.960180] pci 0000:02:01.0: BAR 13: no space for [io  size 0x1000]
Jun 27 21:54:28 box kernel: [  213.960186] pci 0000:02:01.0: BAR 13: failed to assign [io  size 0x1000]
Jun 27 21:54:28 box kernel: [  213.960194] pci 0000:02:00.0: PCI bridge to [bus 03]
Jun 27 21:54:28 box kernel: [  213.960208] pci 0000:02:00.0:   bridge window [mem 0xda000000-0xda0fffff]
Jun 27 21:54:28 box kernel: [  213.960228] pci 0000:02:01.0: PCI bridge to [bus 04-38]
Jun 27 21:54:28 box kernel: [  213.960241] pci 0000:02:01.0:   bridge window [mem 0xc4000000-0xd9efffff]
Jun 27 21:54:28 box kernel: [  213.960252] pci 0000:02:01.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
Jun 27 21:54:28 box kernel: [  213.960267] pci 0000:02:02.0: PCI bridge to [bus 39]
Jun 27 21:54:28 box kernel: [  213.960279] pci 0000:02:02.0:   bridge window [mem 0xd9f00000-0xd9ffffff]
Jun 27 21:54:28 box kernel: [  213.960298] pci 0000:01:00.0: PCI bridge to [bus 02-39]
Jun 27 21:54:28 box kernel: [  213.960311] pci 0000:01:00.0:   bridge window [mem 0xc4000000-0xda0fffff]
Jun 27 21:54:28 box kernel: [  213.960321] pci 0000:01:00.0:   bridge window [mem 0xa0000000-0xc1ffffff 64bit pref]
Jun 27 21:54:28 box kernel: [  213.963686] xhci_hcd 0000:39:00.0: xHCI Host Controller
Jun 27 21:54:28 box kernel: [  213.963714] xhci_hcd 0000:39:00.0: new USB bus registered, assigned bus number 3
Jun 27 21:54:28 box kernel: [  213.964938] xhci_hcd 0000:39:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x00009810
Jun 27 21:54:28 box kernel: [  213.965345] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
Jun 27 21:54:28 box kernel: [  213.965352] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jun 27 21:54:28 box kernel: [  213.965357] usb usb3: Product: xHCI Host Controller
Jun 27 21:54:28 box kernel: [  213.965363] usb usb3: Manufacturer: Linux 4.16.0-1-amd64 xhci-hcd
Jun 27 21:54:28 box kernel: [  213.965368] usb usb3: SerialNumber: 0000:39:00.0
Jun 27 21:54:28 box kernel: [  213.965779] hub 3-0:1.0: USB hub found
Jun 27 21:54:28 box kernel: [  213.965805] hub 3-0:1.0: 2 ports detected
Jun 27 21:54:28 box kernel: [  213.966925] xhci_hcd 0000:39:00.0: xHCI Host Controller
Jun 27 21:54:28 box kernel: [  213.966939] xhci_hcd 0000:39:00.0: new USB bus registered, assigned bus number 4
Jun 27 21:54:28 box kernel: [  213.966949] xhci_hcd 0000:39:00.0: Host supports USB 3.1 Enhanced SuperSpeed
Jun 27 21:54:28 box kernel: [  213.967049] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
Jun 27 21:54:28 box kernel: [  213.967055] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jun 27 21:54:28 box kernel: [  213.967060] usb usb4: Product: xHCI Host Controller
Jun 27 21:54:28 box kernel: [  213.967065] usb usb4: Manufacturer: Linux 4.16.0-1-amd64 xhci-hcd
Jun 27 21:54:28 box kernel: [  213.967070] usb usb4: SerialNumber: 0000:39:00.0
Jun 27 21:54:28 box kernel: [  213.967478] hub 4-0:1.0: USB hub found
Jun 27 21:54:28 box kernel: [  213.967502] hub 4-0:1.0: 2 ports detected
Jun 27 21:54:28 box kernel: [  214.299702] usb 3-1: new high-speed USB device number 2 using xhci_hcd
Jun 27 21:54:28 box kernel: [  214.459749] usb 3-1: New USB device found, idVendor=0800, idProduct=0800
Jun 27 21:54:28 box kernel: [  214.459755] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 27 21:54:28 box kernel: [  214.459759] usb 3-1: Product: USB 2.0 BILLBOARD             
Jun 27 21:54:28 box kernel: [  214.459763] usb 3-1: Manufacturer: VIA Technologies Inc.         
Jun 27 21:54:28 box kernel: [  214.459766] usb 3-1: SerialNumber: 0000000000000001

I've also updated bios to the latest – no luck.
Any help appreciated.

Best Answer

DisplayPort over USB-C "Alternate Mode" is coming to Linux in version 4.19.

Sources:

First News: https://www.phoronix.com/scan.php?page=news_item&px=Linux-USB-Type-C-Port-DP-Driver
Confirmation for release 4.19: https://www.phoronix.com/scan.php?page=news_item&px=Type-C-DP-Alt-Mode-Linux-4.19
Article Source: http://lkml.iu.edu/hypermail/linux/kernel/1806.3/03118.html

Related Solutions

Disconnect and reconnect USB port via cli

Save the following to usbreset.c

/* usbreset -- send a USB port reset to a USB device */

#include <stdio.h>
#include <unistd.h>
#include <fcntl.h>
#include <errno.h>
#include <sys/ioctl.h>

#include <linux/usbdevice_fs.h>


int main(int argc, char **argv)
{
    const char *filename;
    int fd;
    int rc;

    if (argc != 2) {
        fprintf(stderr, "Usage: usbreset device-filename\n");
        return 1;
    }
    filename = argv[1];

    fd = open(filename, O_WRONLY);
    if (fd < 0) {
        perror("Error opening output file");
        return 1;
    }

    printf("Resetting USB device %s\n", filename);
    rc = ioctl(fd, USBDEVFS_RESET, 0);
    if (rc < 0) {
        perror("Error in ioctl");
        return 1;
    }
    printf("Reset successful\n");

    close(fd);
    return 0;
}

The run the following commands in terminal:

Compile the program:
```
cc usbreset.c -o usbreset
```

Get the Bus and Device ID of the USB device you want to reset:

lsusb -t 

Bus#  4  
-Dev#   1 Vendor 0x1d6b Product 0x0001    
-Dev#   3 Vendor 0x046b Product 0xff10

Make our compiled program executable:
```
chmod +x usbreset
```
Execute the program with sudo privilege; make necessary substitution for <Bus> and <Device> ids as found by running the lsusb command:
```
sudo ./usbreset /dev/bus/usb/004/003

Resetting USB device /dev/bus/usb/004/003

Reset successful
```

Source of above program: http://marc.info/?l=linux-usb&m=121459435621262&w=2

USB C → DisplayPort Adapter support

[EDIT: I append at the end of this answer a very brief update, one year after i gave the answer here. If this update should be a second, separate answer, please lmk. Apart from this update at the end, the answer is unchanged]

Your questions are very timely, even though you asked them 7 months ago. And you asked two questions, so you get two answers:

Is it worth trying to get this to work or should I just send it back directly?

A set of kernel patches to support DisplayPort over USB-C have just been published to the Linux-kernel archive here. So for the moment, you need to apply patches and roll your own kernel for it to be possibly worthwhile. (This is less scary than it might seem at first, so I hope you'll consider this encouragement and not the opposite).

A second constraint is that according to the that post in the Linux-Kernel archive, the patches are good for hardware platforms that use FUSB controllers. He will soon also publish support for UCSI controllers -- and I think (but am not positive) that both Intel and ASMedia controllers are of this type. To quote him:

I've tested these with a platform that has fusb302, and also with UCSI platforms. The UCSI driver will need separate support for alternate modes >that I'm not including to this series. I'm still working on it.

In other words, "soon."

What is the status of DP via USB–C in Linux?

I learned about the above in an article in Phoronix, and the article states that the hope is to merge these patches into the 4.19 kernel.

Finally, it's worth noting that for the particular case of DisplayPort over USB-C, the cable is entirely passive and there is a rather mature standard, so you can be close to certain that your cable WILL work once there is OS support for it. This is also true of Thunderbolt over USB-C, but not true of HMDI, for example: A USB-C to HDMI cable is likely to be a DP-to-HDMI adapter on the inside, with the DP side simply using the standard USB-C connector.

If you are not going to deal with kernel patches, I would guess that your cable will 'just work' sometime between 3 months to one year from now.

EDIT/UPDATE: My day-to-day machine is a Dell 7577 Inspiron laptop, running stock Arch Linux. It has a USB-C port and an HDMI port, and I run X/openbox on it with THREE side-by-side monitors: one of them is connected with a stock/standard HDMI cable, and the other with a stock/standard USB-C-to-DisplayPort cable. "Three Monitors with Arch Linux and this particular Dell laptop: It just works". It seems that the prediction I made in the last sentence of the original answer has proved to be accurate.

That being said, there are two important little caveats/nits that I would certainly consider if I were buying a machine today, and wanted this configuration of monitors:

I find the whole "hybrid/mixed/dual discrete and integrated GPU" architecture to be a pain to understand and manage. It's a pain, but it is possible (barely). On Dell systems this architecture is called "Optimus", and how you set things up will have an enormous impact on the kind of video function and performance you get. I realize that I'm being very generic, but there isn't any one thing that's true for all set ups. Basically: if you are looking a machine that has BOTH an integrated GPU AND a discrete GPU, do some research to make sure that OS you intend to install can support the configuration you wish to use.
In particular, it seems that many (most? all?) modern laptops seem to hard-wire each monitor output port to exactly ONE of the two GPUs. So, for example, if the laptop built-in LCD display is hard-wired to the integrated GPU, then any time you use the discrete NVIDIA or Radeon GPU with an application, each frame will be copied at the end over to the integrated GPU in order to actually get displayed on the screen. It may well be that the performance gain from the discrete GPU is so enormous that this extra copy is a negligible price to pay. But it might not be; and even if it is, intensive users of discrete GPU-power often are the type of person who don't like to pay even the most negligible of prices.

I am no true expert, but i think that that's where linux support for three monitors is today. (If by "three monitors" one means "using simultaneously the built-in LCD screen and the two external monitor ports on the laptop."

Best Answer

Related Solutions

Disconnect and reconnect USB port via cli

USB C → DisplayPort Adapter support

Related Question