The DisplayLink provider will not be automatically connected to the main provider in most cases, therefore the DVI output device will not be available. For automating the configuration process, see displaylink.sh. Once the screen is available, refer to Xrandr for info on setting it up. If the above does not list the DisplayLink screen, then you will need to offload DisplayLink to the main GPU: V: height 768 start 769 end 772 total 795 clock 59.9Hz H: width 1368 start 14 total 1800 skew 0 clock 47.6KHz VGA1 disconnected (normal left inverted right x axis y axis)ĭVI-1-0 connected (normal left inverted right x axis y axis) LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm Running xrandr -current gives a list of available screens: In the above example, provider 1 is the DisplayLink device, and provider 0 is the default display. Provider 1: id: 0xcb cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 1 name:modesetting Provider 0: id: 0x43 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 2 outputs: 2 associated providers: 1 name:Intel Once the driver is loaded, the DisplayLink monitor is listed as an output provider: Use xrandr or your Desktop Environment's display setup UI to configure your USB monitors running either the udl or displaylink driver. Instead of loading udl manually, you can load the module at boot. Initialized udl 0.0.1 20120220 on minor 1įurthermore, /dev should contain a new fb device, likely /dev/fb1 if you already had a framebuffer for your primary display. Udl 2-1.1:1.0: fb1: udldrmfb frame buffer device Usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Usb 2-1.1: New USB device found, idVendor=17e9, idProduct=03e0 Usb 2-1.1: new high-speed USB device number 7 using ehci-pci Most importantly, the output of dmesg should show something like the following, indicating a new DisplayLink device was found: Although a green screen is the standard indicator of this, other variations have been spotted and are perfectly normal. If your DisplayLink device is connected, it should show some visual indication of this. These instructions assume that you already have an up and running X server and are simply adding a monitor to your existing setup.īefore your system will recognize your DisplayLink device, the udl kernel module must be loaded. If it works then everything below is unnecessary. This is still experimental but supports hotplugging and when works, it is by far the simplest setup. To use the DisplayLink device, connect provider 1 to provider 0:Īnd xrandr will add a DVI output you can use as normal with xrandr. In the above output, we can see that provider 0 is the system's regular graphics provider (Intel), and provider 1 (modesetting) is the DisplayLink provider. Provider 1: id: 0x13c cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting Provider 0: id: 0x49 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 2 outputs: 8 associated providers: 0 name:Intel $ xrandr -listproviders Providers: number : 2 etc/X11//nf Section "OutputClass"Ī reboot may be required for the setting to be effective.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |