Displaylink not working in F20
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 14 of 14
  1. #1
    Join Date
    Jan 2014
    Location
    GDR
    Posts
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Displaylink not working in F20

    Hello everybody,

    I have already filed a bug report, because displaylink is not working anymore in F20:
    https://bugzilla.redhat.com/show_bug.cgi?id=1047834

    Can anyone help?

    Thx,
    mokkin

  2. #2
    Join Date
    Oct 2007
    Location
    New Zealand. Godzone country! Heaven on earth.
    Posts
    97
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question Re: Displaylink not working in F20

    That bites.
    I ordered one of those over Christmas for my replacement laptop.


    What did you do to get it running in F19?

    TIA,
    Bert
    Main computer - Ex-lease Dell Latitude E6510, Intel Core i5, 8GB RAM, 250 GB SSD, Fedora 26 64 bit

    "Thus, or perhaps better!"

  3. #3
    Join Date
    Sep 2008
    Posts
    176
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Displaylink not working in F20

    I have one of these SIIG displaylink adapters ( http://www.bhphotovideo.com/bnh/cont...G&A=details&Q= ) normally attached to my Thinkpad T420 running F19. After reading your post, I booted the F20 XFCE live CD and only had the integrated VGA and HDMI working. xrandr didn't detect the displaylink card. I moved the USB cable over to my Lenovo desktop running F20 with all current maintenance. My primary video card on this box is a Radeon 7750. xrandr (alone, no options) showed the dispalylink card and xrandr --output DVI-1-2 --auto --right-of DVI-1 brought it up just fine as a 4th display on this system.

    My guess, the displaylink kernel module isn't included in the live CD... at least on the XFCE spin.

    I'm currently working on cloning my T420 drive and will do fedup update to F20. I expect everything will work. The clone copy will complete a bit later tonight and I might be able to complete the fedup upgrade thru the day tomorrow amongst my other work... lacking any other posts I'll update this thread after I get thru the fedup upgrade.

    jw.

  4. #4
    Join Date
    Sep 2008
    Posts
    176
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Displaylink not working in F20

    to Bert, I don't recall doing anything other than xrandr commands to get it working on F19. Plug it in, "xrandr" to see what your system calls it, then use the xrandr command with options to set it on with desired geography and placement amongst your other monitors. At one point I came across doc that said it only works as the left-most system on linux (position 0x0). The test I documented just above on F20 makes it look like that restriction is no longer present.

    jw

  5. #5
    Join Date
    Oct 2007
    Location
    New Zealand. Godzone country! Heaven on earth.
    Posts
    97
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Talking Re: Displaylink not working in F20

    Thanks jw,

    This is a fresh install of F20 64bit on a Dell Latitude E6410.

    I've been searching the forums and web trying to get more info on how to get it working. What I have seen so far suggests it should just run, except for this thread.

    What kernel modules do I need?

    Right now I'm using my older Latitude D830, which has it's own docking station. I decided to go for one of the DisplayLink docking stations so that I would have to keep getting new ones all the time.

    I look forward to your findings.
    Thanks for your reply,
    Bert
    Main computer - Ex-lease Dell Latitude E6510, Intel Core i5, 8GB RAM, 250 GB SSD, Fedora 26 64 bit

    "Thus, or perhaps better!"

  6. #6
    Join Date
    Sep 2008
    Posts
    176
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Displaylink not working in F20

    Bert, in reviewing google and some linux forums, it appears that fedora package xorg-x11-drv-fbdev may be required, if it wasn't automatically included on your system. Also, "lsmod" shows module "udl", which is part of the kernel package. I have no specific customization for the kernel, just standard packages installed from the fedora/rpmfusion repositories. Display setup is done via xrandr commands (see below). I don't use xorg.conf. As I remember, when you first plug in your displaylink adapter and the monitor, you may see a colored outline around the edge of the screen. As mentioned before, using xrandr (no options to display the known monitors) should give the indication that it's present and recognized, showing many supported display resolutions. The output from my system is below. My T420 only supports 2 integrated displays even tho 3 are availlable (lvds, vga, displayport). Here, LVDS1 (laptop display) shows connected but has been turned off in xrandr (xrandr --output LVDS1 --off). HDMI1 is a displayport-to-hdmi cable. VGA1 is the native VGA port. The monitor layout is: displaylink-HDMI1-VGA1 , all 3 with 1920x1080 resolution. I have a startup script with:

    xrandr --output LVDS1 --off
    xrandr --output DVI-1-0 --auto --output HDMI1 --auto --right-of DVI-1-0 --output VGA1 --auto --right-of HDMI1


    $ xrandr
    Screen 0: minimum 320 x 200, current 5760 x 1080, maximum 8192 x 8192
    LVDS1 connected (normal left inverted right x axis y axis)
    1600x900 60.0 +
    1024x768 60.0
    800x600 60.3 56.2
    640x480 59.9
    VGA1 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 477mm x 268mm
    1920x1080 60.0*+
    1280x1024 60.0
    1440x900 59.9
    1280x800 59.8
    1152x864 75.0
    1024x768 70.1 60.0
    800x600 60.3 56.2
    640x480 66.7 60.0
    720x400 70.1
    HDMI1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 477mm x 268mm
    1920x1080 60.0*+
    1680x1050 59.9
    1400x1050 59.9
    1600x900 60.0
    1280x1024 75.0 60.0
    1440x900 59.9
    1280x800 59.9
    1152x864 75.0
    1280x720 60.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    DP1 disconnected (normal left inverted right x axis y axis)
    HDMI2 disconnected (normal left inverted right x axis y axis)
    HDMI3 disconnected (normal left inverted right x axis y axis)
    DP2 disconnected (normal left inverted right x axis y axis)
    DP3 disconnected (normal left inverted right x axis y axis)
    DVI-1-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 476mm x 268mm
    1920x1080 60.0*+
    1680x1050 60.0
    1280x1024 75.0 60.0
    1440x900 59.9
    1280x960 60.0
    1280x800 59.8
    1152x864 75.0
    1280x720 60.0
    1024x768 75.1 70.1 60.0
    832x624 74.6
    800x600 72.2 75.0 60.3 56.2
    640x480 75.0 66.7 60.0
    720x400 70.1
    1920x1080 (0x42) 148.5MHz
    h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.5KHz
    v: height 1080 start 1084 end 1089 total 1125 clock 60.0Hz
    1280x1024 (0x44) 135.0MHz
    h: width 1280 start 1296 end 1440 total 1688 skew 0 clock 80.0KHz
    v: height 1024 start 1025 end 1028 total 1066 clock 75.0Hz
    1280x1024 (0x45) 108.0MHz
    h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 64.0KHz
    v: height 1024 start 1025 end 1028 total 1066 clock 60.0Hz
    1440x900 (0x46) 106.5MHz
    h: width 1440 start 1520 end 1672 total 1904 skew 0 clock 55.9KHz
    v: height 900 start 903 end 909 total 934 clock 59.9Hz
    1280x800 (0x48) 83.5MHz
    h: width 1280 start 1352 end 1480 total 1680 skew 0 clock 49.7KHz
    v: height 800 start 803 end 809 total 831 clock 59.8Hz
    1152x864 (0x49) 108.0MHz
    h: width 1152 start 1216 end 1344 total 1600 skew 0 clock 67.5KHz
    v: height 864 start 865 end 868 total 900 clock 75.0Hz
    1280x720 (0x4a) 74.4MHz
    h: width 1280 start 1336 end 1472 total 1664 skew 0 clock 44.7KHz
    v: height 720 start 721 end 724 total 746 clock 60.0Hz
    1024x768 (0x4b) 78.8MHz
    h: width 1024 start 1040 end 1136 total 1312 skew 0 clock 60.1KHz
    v: height 768 start 769 end 772 total 800 clock 75.1Hz
    1024x768 (0x4c) 75.0MHz
    h: width 1024 start 1048 end 1184 total 1328 skew 0 clock 56.5KHz
    v: height 768 start 771 end 777 total 806 clock 70.1Hz
    1024x768 (0x4d) 65.0MHz
    h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
    v: height 768 start 771 end 777 total 806 clock 60.0Hz
    800x600 (0x50) 49.5MHz
    h: width 800 start 816 end 896 total 1056 skew 0 clock 46.9KHz
    v: height 600 start 601 end 604 total 625 clock 75.0Hz
    800x600 (0x51) 40.0MHz
    h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
    v: height 600 start 601 end 605 total 628 clock 60.3Hz
    800x600 (0x52) 36.0MHz
    h: width 800 start 824 end 896 total 1024 skew 0 clock 35.2KHz
    v: height 600 start 601 end 603 total 625 clock 56.2Hz
    640x480 (0x53) 31.5MHz
    h: width 640 start 656 end 720 total 840 skew 0 clock 37.5KHz
    v: height 480 start 481 end 484 total 500 clock 75.0Hz
    640x480 (0x54) 30.2MHz
    h: width 640 start 704 end 768 total 864 skew 0 clock 35.0KHz
    v: height 480 start 483 end 486 total 525 clock 66.7Hz
    640x480 (0x55) 25.2MHz
    h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
    v: height 480 start 490 end 492 total 525 clock 60.0Hz
    720x400 (0x56) 28.3MHz
    h: width 720 start 738 end 846 total 900 skew 0 clock 31.5KHz
    v: height 400 start 412 end 414 total 449 clock 70.1Hz

    (and my drive copy completed so I'm on target to try the fedup update to F20 on Tuesday)
    jw

  7. #7
    Join Date
    Oct 2007
    Location
    New Zealand. Godzone country! Heaven on earth.
    Posts
    97
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Lightbulb Re: Displaylink not working in F20

    Thanks jw,

    Your previous post has got me thinking. I've used Xrandr to get my s-video working on an earlier laptop, and associated two button type icons to some very basic bash scripts. That way I could activate s-video as needed.

    I use this laptop in the office and for field work, so I could use the same method.

    I do have several programs that automatically run at login.
    It would be good to run the script automatically a login, and check if the DisplayLink is attached. If so it could disable the laptop LCD and enable the DisplayLink.
    I'm not much of a programmer / script writer, I prefer GUI tools if possible (The Atari STe was great for this )

    Anyway, I can find out if the modules / xorg packages are installed and install xrandr to get more info on the DisplayLink.

    Thanks for jogging my fairly fried (from fixing too many Windows computers) memory.

    Cheers,
    Bert
    Main computer - Ex-lease Dell Latitude E6510, Intel Core i5, 8GB RAM, 250 GB SSD, Fedora 26 64 bit

    "Thus, or perhaps better!"

  8. #8
    Join Date
    Sep 2008
    Posts
    176
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Displaylink not working in F20

    and... I completed the fedup to F20 on my cloned drive using a secondary T420 I have. I plugged in the displaylink adapter and it worked without issue. Going back to the original post, the issue may only be with the live media, not F20 on an installed system.

    jw.

  9. #9
    Join Date
    Oct 2007
    Location
    New Zealand. Godzone country! Heaven on earth.
    Posts
    97
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Displaylink not working in F20

    Hi jw,

    Quote Originally Posted by jwmueller
    and... I completed the fedup to F20 on my cloned drive using a secondary T420 I have. I plugged in the displaylink adapter and it worked without issue. Going back to the original post, the issue may only be with the live media, not F20 on an installed system.

    jw.
    As mentioned earlier, I am experiencing this on a clean install of F20 from the DVD ISO, not live media, and the DisplayLink isn't working.

    I've been doing some tesing and found some stuff

    Check for xorg-x11-drv-fbdev
    Code:
    rpm -q xorg-x11-drv-fbdev
    xorg-x11-drv-fbdev-0.4.3-10.fc20.x86_64
    looking good so far


    Here's the result of lsusb
    Code:
    # lsusb
    Bus 002 Device 005: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
    Bus 002 Device 004: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
    Bus 002 Device 007: ID 1a40:0101 Terminus Technology Inc. Hub
    Bus 002 Device 006: ID 17e9:4307 DisplayLink 
    Bus 002 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
    Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 003: ID 05ca:1814 Ricoh Co., Ltd HD Webcam
    Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    So the DisplayLink is detected at that level.

    XRANDR
    Without DisplayLink attached
    Code:
    Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
    eDP-1 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 303mm x 189mm
       1440x900       60.0*+   40.0  
       1152x864       60.0  
       1024x768       59.9  
       800x600        59.9  
       640x480        59.4  
       720x400        59.6  
       640x400        60.0  
       640x350        59.8  
    VGA-1 disconnected (normal left inverted right x axis y axis)
    DP-1 disconnected (normal left inverted right x axis y axis)
    DP-2 disconnected (normal left inverted right x axis y axis)
    With DisplayLink and LCD, after reboot
    Code:
    xrandr
    Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
    eDP-1 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 303mm x 189mm
       1440x900       60.0*+   40.0  
       1152x864       60.0  
       1024x768       59.9  
       800x600        59.9  
       640x480        59.4  
       720x400        59.6  
       640x400        60.0  
       640x350        59.8  
    VGA-1 disconnected (normal left inverted right x axis y axis)
    DP-1 disconnected (normal left inverted right x axis y axis)
    DP-2 disconnected (normal left inverted right x axis y axis)
    No change?

    Something is missing. Not sure where to go from here so I gave lsmod a go.
    Code:
    Module                  Size  Used by
    rfcomm                 69078  12 
    fuse                   82701  3 
    nf_conntrack_netbios_ns    12665  0 
    nf_conntrack_broadcast    12527  1 nf_conntrack_netbios_ns
    ipt_MASQUERADE         12880  1 
    ip6t_REJECT            12939  2 
    xt_conntrack           12760  42 
    ebtable_nat            12807  0 
    ebtable_broute         12731  0 
    bridge                110618  1 ebtable_broute
    stp                    12868  1 bridge
    llc                    14045  2 stp,bridge
    ebtable_filter         12827  0 
    ebtables               30758  3 ebtable_broute,ebtable_nat,ebtable_filter
    ip6table_nat           13015  1 
    nf_conntrack_ipv6      18738  24 
    nf_defrag_ipv6         34595  1 nf_conntrack_ipv6
    nf_nat_ipv6            13213  1 ip6table_nat
    ip6table_mangle        12700  1 
    ip6table_security      12710  1 
    ip6table_raw           12683  1 
    ip6table_filter        12815  1 
    ip6_tables             26808  5 ip6table_filter,ip6table_mangle,ip6table_security,ip6table_nat,ip6table_raw
    iptable_nat            13011  1 
    nf_conntrack_ipv4      14808  20 
    nf_defrag_ipv4         12702  1 nf_conntrack_ipv4
    nf_nat_ipv4            13199  1 iptable_nat
    nf_nat                 20712  5 ipt_MASQUERADE,nf_nat_ipv4,nf_nat_ipv6,ip6table_nat,iptable_nat
    nf_conntrack           91283  11 nf_conntrack_netbios_ns,ipt_MASQUERADE,nf_nat,nf_nat_ipv4,nf_nat_ipv6,xt_conntrack,ip6table_nat,nf_conntrack_broadcast,iptable_nat,nf_conntrack_ipv4,nf_conntrack_ipv6
    iptable_mangle         12695  1 
    iptable_security       12705  1 
    iptable_raw            12678  1 
    bnep                   19704  2 
    cdc_mbim               13176  0 
    cdc_wdm                18864  1 cdc_mbim
    coretemp               13435  0 
    arc4                   12608  2 
    brcmsmac              534974  0 
    snd_usb_audio         149112  3 
    snd_usbmidi_lib        24845  1 snd_usb_audio
    snd_rawmidi            29394  1 snd_usbmidi_lib
    ppdev                  17635  0 
    e1000e                254311  0 
    i2c_i801               18135  0 
    cordic                 12525  1 brcmsmac
    cdc_ncm                19689  1 cdc_mbim
    brcmutil               14880  1 brcmsmac
    kvm_intel             142832  0 
    kvm                   430555  1 kvm_intel
    crct10dif_pclmul       14289  0 
    crc32_pclmul           13113  0 
    crc32c_intel           22079  0 
    ghash_clmulni_intel    13259  0 
    snd_hda_codec_hdmi     41070  4 
    uvcvideo               80968  0 
    videobuf2_vmalloc      13163  1 uvcvideo
    videobuf2_memops       13161  1 videobuf2_vmalloc
    videobuf2_core         38899  1 uvcvideo
    videodev              132922  2 uvcvideo,videobuf2_core
    b43                   387900  0 
    mac80211              579060  2 b43,brcmsmac
    cfg80211              478020  3 b43,brcmsmac,mac80211
    ssb                    65906  1 b43
    bcma                   45511  2 b43,brcmsmac
    snd_hda_codec_idt      50386  1 
    iTCO_wdt               13480  0 
    iTCO_vendor_support    13419  1 iTCO_wdt
    snd_hda_intel          48171  7 
    snd_hda_codec         183375  3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
    dell_laptop            18168  0 
    dcdbas                 14885  1 dell_laptop
    tpm_tis                18984  0 
    dell_wmi               12681  0 
    sparse_keymap          13584  1 dell_wmi
    joydev                 17332  0 
    snd_hwdep              13554  2 snd_usb_audio,snd_hda_codec
    snd_seq                60752  0 
    snd_seq_device         14136  2 snd_seq,snd_rawmidi
    snd_pcm                98141  4 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
    snd_page_alloc         18268  2 snd_pcm,snd_hda_intel
    snd_timer              28698  2 snd_pcm,snd_seq
    snd                    75313  32 snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_idt,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,snd_seq_device
    soundcore              14491  1 snd
    usbnet                 41932  2 cdc_mbim,cdc_ncm
    mii                    13527  1 usbnet
    media                  20840  2 uvcvideo,videodev
    tpm                    25869  1 tpm_tis
    microcode              44087  0 
    sdhci_pci              18927  0 
    sdhci                  38255  1 sdhci_pci
    intel_ips              18412  0 
    ptp                    18725  1 e1000e
    parport_pc             28048  0 
    mmc_core              116378  3 b43,ssb,sdhci
    serio_raw              13413  0 
    btusb                  28170  0 
    bluetooth             366020  32 bnep,btusb,rfcomm
    pps_core               19130  1 ptp
    rfkill                 21979  7 cfg80211,bluetooth,dell_laptop
    lpc_ich                21080  0 
    mfd_core               13182  1 lpc_ich
    shpchp                 37032  0 
    parport                40425  2 ppdev,parport_pc
    tpm_bios               18688  1 tpm
    acpi_cpufreq           19790  1 
    nfsd                  279962  1 
    binfmt_misc            17431  1 
    auth_rpcgss            58797  1 nfsd
    nfs_acl                12741  1 nfsd
    lockd                  93436  1 nfsd
    sunrpc                269560  5 nfsd,auth_rpcgss,lockd,nfs_acl
    nouveau               952573  3 
    mxm_wmi                12865  1 nouveau
    i2c_algo_bit           13257  1 nouveau
    drm_kms_helper         50287  1 nouveau
    ttm                    79787  1 nouveau
    drm                   283349  5 ttm,drm_kms_helper,nouveau
    firewire_ohci          40360  0 
    firewire_core          62518  1 firewire_ohci
    i2c_core               38302  6 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau,videodev
    crc_itu_t              12613  1 firewire_core
    wmi                    18804  3 dell_wmi,mxm_wmi,nouveau
    video                  19104  1 nouveau

    So where too?

    I could fix the immediate problem, I need a docking station, simply by ordering one from my supplier. Then when I replace the hardware I'll have to get another one.

    The long term solution is to get this DisplayLink to work then I don't have to dispose of old docking stations each time I upgrade.

    Thanks for the time you have spent on this.

    Regards,
    Bert
    Main computer - Ex-lease Dell Latitude E6510, Intel Core i5, 8GB RAM, 250 GB SSD, Fedora 26 64 bit

    "Thus, or perhaps better!"

  10. #10
    Join Date
    Oct 2007
    Location
    New Zealand. Godzone country! Heaven on earth.
    Posts
    97
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Displaylink not working in F20

    Direct from the donkey's mouth, so to speak.

    I checked on the DisplayLink Linux forum and guess what I found -

    Code:
    	  #102
    kwutchak
    Junior Member
     
    Join Date: Nov 2013
    Posts: 1
    	
    Talking Insecure data path for Linux will be more than sufficient...
    Quote:
    Originally Posted by Wim View Post
    ... One issue is that the DL-3000 supports content protection and we need to ensure this remains secure under an open source environment.
    Wim
    I'd hazard a guess that not many Linux enthusiasts would be overly concerned at losing a data path that secures the interests of companies that didn't pay for your hardware (in contrast to the Linux user who did buy it).
    
    Is it possible to provide open source drivers that allow us to display X (as I do on your USB 2 chipset). I know that I don't care at all that the data path for my X display is secure from, well, me.
    Last edited by kwutchak; 11-12-2013 at 03:49 PM.
    kwutchak is offline   	Reply With Quote
    So it looks like I am stuck with an overpriced usb hub.

    Thanks for your time jw.

    Regards,
    Bert
    Main computer - Ex-lease Dell Latitude E6510, Intel Core i5, 8GB RAM, 250 GB SSD, Fedora 26 64 bit

    "Thus, or perhaps better!"

  11. #11
    Join Date
    Sep 2008
    Posts
    176
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Displaylink not working in F20

    We might be on to some other variances here... you're mentioning DL-3000. The link I posted earlier for my SIIG device indicates it uses a DL-165 chipset. Might also be relevant in the lsusb output, mine showing a different product id:
    Bus 002 Device 003: ID 17e9:02ee DisplayLink

    This link shows the several different chip versions and their capabilities. http://www.display-solution.com/en/p...play_link.html

    jw.

  12. #12
    Join Date
    Oct 2007
    Location
    New Zealand. Godzone country! Heaven on earth.
    Posts
    97
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Thumbs down Re: Displaylink not working in F20

    I've registered my disappointment with DisplayLink.

    Looks like I'll have to sell this to a Window user.

    Thanks for everyone's time.
    Bert
    Main computer - Ex-lease Dell Latitude E6510, Intel Core i5, 8GB RAM, 250 GB SSD, Fedora 26 64 bit

    "Thus, or perhaps better!"

  13. #13
    Join Date
    Oct 2007
    Location
    New Zealand. Godzone country! Heaven on earth.
    Posts
    97
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Displaylink not working in F20

    Hi jw,

    Quote Originally Posted by jwmueller
    We might be on to some other variances here... you're mentioning DL-3000. The link I posted earlier for my SIIG device indicates it uses a DL-165 chipset. Might also be relevant in the lsusb output, mine showing a different product id:
    Bus 002 Device 003: ID 17e9:02ee DisplayLink

    This link shows the several different chip versions and their capabilities. http://www.display-solution.com/en/p...play_link.html

    jw.
    Yeah, unfortunately I couldn't ID the device initially as it doesn't mention a manufacturer. The only ID is LAPDOCK and DisplayLink certified. So it is a Chinese copy of something or other.

    It is a USB 3.0 laptop docking station, with 1 x USB 3.0 input, 2 x USB 3.0 out, 4x USB 2 out, 1 x HDMI & 1 x DVI out, and Gig ethernet.

    From your link it looks like a 3500.

    Anyway it looks like content protection has stymied me.

    Thanks for your time.

    Bert
    Last edited by Bert Rolston; 8th January 2014 at 12:44 AM. Reason: change Winders DRM to content protection
    Main computer - Ex-lease Dell Latitude E6510, Intel Core i5, 8GB RAM, 250 GB SSD, Fedora 26 64 bit

    "Thus, or perhaps better!"

  14. #14
    Join Date
    Feb 2013
    Location
    Westfield, IN
    Posts
    2
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Displaylink not working in F20

    For me a (failing to display) Sabent USB-DH88 on Fedora 22 gives:
    lsusb | grep Display
    Bus 001 Device 012: ID 17e9:0360 DisplayLink

    I can display using the latest libdlo 'make check' from:
    https://wiki.freedesktop.org/libdlo/
    (Note you have to run autoupdate first to fix/upgrade the configure.ac, next add AM_PROG_AR:
    ...
    # Checks for programs.
    AM_PROG_AR
    AC_PROG_CC
    LT_INIT
    ...)
    Note that Firefox, GNOME Terminal, and a few other things might die during the test or when/if you unplug the USB to it. The display attached to the USB-DH88 does display the tests.

    From journalctl:
    kernel: usb 1-1.2: new high-speed USB device number 14 using ehci-pci
    kernel: usb 1-1.2: device descriptor read/64, error -32
    kernel: usb 1-1.2: New USB device found, idVendor=17e9, idProduct=0360
    kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    kernel: usb 1-1.2: Product: Sabrent USB-DH88
    kernel: usb 1-1.2: Manufacturer: DisplayLink
    kernel: usb 1-1.2: SerialNumber: 715833
    kernel: [drm] vendor descriptor length:22 data:22 5f 01 00 20 05 00 01 03 00 04
    kernel: udl 1-1.2:1.0: fb6: udldrmfb frame buffer device
    kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    kernel: [drm] No driver support for vblank timestamp query.
    kernel: [drm] Initialized udl on minor 6
    mtp-probe[18281]: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
    mtp-probe[18281]: bus: 1, device: 14 was not an MTP device
    /usr/libexec/gdm-x-session[7077]: (II) config/udev: removing GPU device /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/drm/card6 /dev/dri/card6
    /usr/libexec/gdm-x-session[7077]: (II) config/udev: Adding drm device (/dev/dri/card6)
    /usr/libexec/gdm-x-session[7077]: (II) xfree86: Adding drm device (/dev/dri/card6)
    /usr/libexec/gdm-x-session[7077]: (II) systemd-logind: got fd for /dev/dri/card6 226:6 fd 50 paused 0
    /usr/libexec/gdm-x-session[7077]: (II) LoadModule: "modesetting"
    /usr/libexec/gdm-x-session[7077]: (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    /usr/libexec/gdm-x-session[7077]: (II) Module modesetting: vendor="X.Org Foundation"
    /usr/libexec/gdm-x-session[7077]: compiled for 1.17.2, module version = 1.17.2
    /usr/libexec/gdm-x-session[7077]: Module class: X.Org Video Driver
    /usr/libexec/gdm-x-session[7077]: ABI class: X.Org Video Driver, version 19.0
    /usr/libexec/gdm-x-session[7077]: (II) UnloadModule: "modesetting"
    /usr/libexec/gdm-x-session[7077]: (II) Unloading modesetting
    /usr/libexec/gdm-x-session[7077]: (II) Failed to load module "modesetting" (already loaded, 0)
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): using drv /dev/dri/card6
    /usr/libexec/gdm-x-session[7077]: (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
    /usr/libexec/gdm-x-session[7077]: (==) modeset(G0): RGB weight 888
    /usr/libexec/gdm-x-session[7077]: (==) modeset(G0): Default visual is TrueColor
    /usr/libexec/gdm-x-session[7077]: (II) Loading sub module "glamoregl"
    /usr/libexec/gdm-x-session[7077]: (II) LoadModule: "glamoregl"
    /usr/libexec/gdm-x-session[7077]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    /usr/libexec/gdm-x-session[7077]: (II) Module glamoregl: vendor="X.Org Foundation"
    /usr/libexec/gdm-x-session[7077]: compiled for 1.17.2, module version = 1.0.0
    /usr/libexec/gdm-x-session[7077]: ABI class: X.Org ANSI C Emulation, version 0.4
    /usr/libexec/gdm-x-session[7077]: (II) glamor: OpenGL accelerated X.org driver based.
    /usr/libexec/gdm-x-session[7077]: gbm: failed to open any driver (search paths /usr/lib/dri)
    /usr/libexec/gdm-x-session[7077]: gbm: Last dlopen error: /usr/lib/dri/udl_dri.so: cannot open shared object file: No such file or directory
    /usr/libexec/gdm-x-session[7077]: failed to load driver: udl
    /usr/libexec/gdm-x-session[7077]: (II) glamor: EGL version 1.4 (DRI2):
    /usr/libexec/gdm-x-session[7077]: EGL_MESA_drm_image required.
    /usr/libexec/gdm-x-session[7077]: (EE) modeset(G0): glamor initialization failed
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): ShadowFB: preferred NO, enabled NO
    gnome-session[1928]: (gnome-settings-daemon:2202): color-plugin-WARNING **: could not find device: property match 'XRANDR_name'='HDMIA35' does not exist
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Output DVI-1-5 has no monitor section
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    /usr/libexec/gdm-x-session[7077]: (**) modeset(G0): Display dimensions: (340, 190) mm
    /usr/libexec/gdm-x-session[7077]: (WW) modeset(G0): Probed monitor is 470x290 mm, using Displaysize 340x190 mm
    /usr/libexec/gdm-x-session[7077]: (**) modeset(G0): DPI set to (76, 102)
    /usr/libexec/gdm-x-session[7077]: (II) Loading sub module "fb"
    /usr/libexec/gdm-x-session[7077]: (II) LoadModule: "fb"
    /usr/libexec/gdm-x-session[7077]: (II) Loading /usr/lib/xorg/modules/libfb.so
    /usr/libexec/gdm-x-session[7077]: (II) Module fb: vendor="X.Org Foundation"
    /usr/libexec/gdm-x-session[7077]: compiled for 1.17.2, module version = 1.0.0
    /usr/libexec/gdm-x-session[7077]: ABI class: X.Org ANSI C Emulation, version 0.4
    /usr/libexec/gdm-x-session[7077]: (==) modeset(G0): Backing store enabled
    /usr/libexec/gdm-x-session[7077]: (==) modeset(G0): Silken mouse enabled
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): RandR 1.2 enabled, ignore the following RandR disabled message.
    /usr/libexec/gdm-x-session[7077]: (==) modeset(G0): DPMS enabled
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Damage tracking initialized
    /usr/libexec/gdm-x-session[7077]: xf86: found device 2
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): EDID vendor "BTC", prod id 8867
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Using hsync ranges from config file
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Using vrefresh ranges from config file
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Printing DDC gathered Modelines:
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Modeline "1680x1050"x0.0 146.00 1680 1784 1960 2240 1050 1053 1059 1089 -hsync -vsync (65.2 kHz eP)
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    ...
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Modeline "1440x900"x0.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): EDID vendor "BTC", prod id 8867
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Using hsync ranges from config file
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Using vrefresh ranges from config file
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Printing DDC gathered Modelines:
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Modeline "1680x1050"x0.0 146.00 1680 1784 1960 2240 1050 1053 1059 1089 -hsync -vsync (65.2 kHz eP)
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    ...
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Modeline "1440x900"x0.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
    /usr/libexec/gdm-x-session[7077]: (II) modeset(G0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    gnome-session[1928]: (gnome-settings-daemon:2202): color-plugin-WARNING **: no xrandr-Bit 3 Computer-LE22A3-82700543 device found: Failed to find output xrandr-Bit 3 Computer-LE22A3-82700543


    The display won't light up (no power light). It does show under 'Displays' and I can set it as a secondary display, but it won't turn on. [Again the USB-DH88 and monitor are 'fine' given libdio's make check works 'fine'.]

    Ideas? What device id's are working for people and which aren't?
    Has anyone dropped back from the 'newer' udl to udlfb with success?
    Again it claims to be Linux Compatible and points the user to http://displaylink.org

    Thanks,

    -Jeff

Similar Threads

  1. Wired connection not working in F20
    By MuadNu in forum Hardware
    Replies: 2
    Last Post: 12th March 2014, 08:11 PM
  2. F20 Skype not working.
    By jgsheppard in forum Installation, Upgrades and Live Media
    Replies: 9
    Last Post: 27th February 2014, 06:08 PM
  3. [SOLVED]
    F20 - resume from S3 sleep state WAS working until...
    By weitjong in forum Using Fedora
    Replies: 1
    Last Post: 31st December 2013, 10:32 AM
  4. Video full screen not working in F20
    By Hewjr100 in forum F-20 Development Forum
    Replies: 14
    Last Post: 27th November 2013, 02:46 AM
  5. F20 - Xfce - CTRL-C no longer working in terminals
    By PabloTwo in forum F-20 Development Forum
    Replies: 10
    Last Post: 12th November 2013, 08:21 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •