Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to use on debian? #172

Closed
kopax opened this issue Nov 19, 2018 · 25 comments
Closed

How to use on debian? #172

kopax opened this issue Nov 19, 2018 · 25 comments

Comments

@kopax
Copy link

kopax commented Nov 19, 2018

I have downloaded debian and bought a new desktop computer.

I tried the plugin and the screen is available in Display. However, I can't make it work, if it's enabled, then all the desktop get frozen, even if the screen is on and I can't move my mouse inside.

Why?

Thanks in advance

@kopax kopax changed the title This plugin is not recommended How to use on debian? Nov 19, 2018
@AdnanHodzic
Copy link
Owner

@kopax what happens if you mv /etc/X11/xorg.conf.d/20-displaylink.conf /tmp/20-displaylink.conf and restart X (log out and log in).

Also which version of Debian are using?

@kopax
Copy link
Author

kopax commented Nov 20, 2018

Thanks for the quick reply @AdnanHodzic I appreciate.

I am using this version of Debian:

Linux dev-12 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU/Linux

I will redo the test once I am done working on this computer.

@AdnanHodzic, thanks for doing this module. I only use Debian and for about 3 years I was not able to use that MB168+ screen. An old version of this project used to work with Debian but that wasn't stable. After doing a Linux kernel update on my laptop (required by latest docker daemon for storage v2 driver), it stopped completely to work.

I expected to use a default Debian install would be working fine but it is not.
I would gladly contribute to testing if you can help me get this screen working in a reliable way, I don't have any knowledge with xrandr, I am web developer.

@kopax
Copy link
Author

kopax commented Nov 20, 2018

I have just followed your recommendation

dka@dev-12:[~]: xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x45 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 3 associated providers: 0 name:Intel
Provider 1: id: 0x18a cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
dka@dev-12:[~]: sudo mv /etc/X11/xorg.conf.d/20-displaylink.conf /tmp/20-displaylink.conf
dka@dev-12:[~]: cat /tmp/20-displaylink.conf
Section "Device"
  Identifier  "Intel"
  Driver      "intel"
EndSection

After log out and log in, I am doing

dka@dev-12:[~]: xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x45 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 3 associated providers: 0 name:Intel
Provider 1: id: 0x18a cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
dka@dev-12:[~]: xrandr --setprovideroutputsource 1 0

On cinnamon, if I go in Display and activate my display, the screen turn on, I can see the background, I can see windows from another screen, I can move my mouse, but I can't bring window into that screen. It is like if the desktop environment is frozen.

By doing mv /etc/X11/xorg.conf.d/20-displaylink.conf /tmp/20-displaylink.conf, I am not crashing my configuration, but it is not working better.

$ uname -a
Linux dev-12 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 9.5 (stretch)
Release:	9.5
Codename:	stretch

It seems to be close to work, do you know how I can fix this @AdnanHodzic ?

@AdnanHodzic
Copy link
Owner

@kopax ok forget about removing mv /etc/X11/xorg.conf.d/20-displaylink.conf /tmp/20-displaylink.conf.

Every time you upgrade a new kernel you need to re-install, so could you please run "uninstall" and then reboot the computer and then do "reinstall". It seems like your displays are recognized just fine from what I see here.

@kopax
Copy link
Author

kopax commented Nov 22, 2018

Every time you upgrade a new kernel you need to re-install

As I said, I have one Lenovo X1Carbon Gen 1, I have updated the kernel once and since I am not able to use the screen, even with reunstalling, formating etc... I have no clue why, I am juste reporting.

It seems like your displays are recognized just fine from what I see here.

Yes it is, but again, that's a desktop brand new computer. I did not upgrade the kernel or do any things with the core of linux since I installed it. Using that fresh install, the driver does not make it work and I have a freeze effect. I think this is the most common setup people will have.

@AdnanHodzic
Copy link
Owner

@kopax did you pull latest changes (as of today), and run reinstall?

@kopax
Copy link
Author

kopax commented Nov 24, 2018

You mean this one ? https://github.com/AdnanHodzic/displaylink-debian/pull/175/files

Basically, that's the revert of what you already asked me to do before with mv /etc/X11/xorg.conf.d/20-displaylink.conf /tmp/20-displaylink.conf.

I can pull but looking at the operation, you have not changed anything so there is no reason to see it working. Do you want me to still do it, film me and post it on youtube? Maybe that would help see you how the screen freeze.

@AdnanHodzic
Copy link
Owner

Sorry, I got mixed up with a different issue I saw your name in.

Let's start from the beginning, can you please verify that you went through post installation guide?

To be 100% if possible I would like if you could "Uninstall" the driver reboot, run "Install" again reboot and see if you still have the same problem.

Please paste output of whole "Install" process here.

@kopax
Copy link
Author

kopax commented Nov 24, 2018

Let's start from the beginning, can you please verify that you went through post installation guide?

Yes I did a few times.

To be 100% if possible I would like if you could "Uninstall" the driver reboot, run "Install" again reboot and see if you still have the same problem.

  1. Sure, I've updated my branch:
From github.com:AdnanHodzic/displaylink-debian
   a236153..56b72e6  master     -> origin/master
  1. I've stopped the dlm.service with systemctl stop dlm.service.
  2. Run the script as root and choose Uninstall, I got Uninstall complete message
  3. Reboot
  4. Run the script as root and choose Install (log below)
root@dev-12:/home/dka/workspace/github.com/AdnanHodzic/displaylink-debian# ./displaylink-debian.sh 

--------------------------- displaylink-debian ----------------------------

DisplayLink driver installer for Debian based Linux distributions:

* Debian GNU/Linux
* Ubuntu
* Elementary OS
* Linux Mint
* Kali Linux
* Deepin

Options:

[I]nstall
[U]ninstall
[R]e-install
[Q]uit

Select a key: [i/u/r/q]: i

-------------------------------------------------------------------

Checking dependencies

unzip is installed
linux-headers-4.9.0-8-amd64 is installed
dkms is installed
lsb-release is installed
linux-source is installed

Platform requirements satisfied, proceeding ...

-------------------------------------------------------------------

Please read the Software License Agreement
available at https://www.displaylink.com/downloads/file?id=1261
and accept here: [Y]es or [N]o: y

Downloading DisplayLink Ubuntu driver:

--2018-11-24 22:08:26--  https://www.displaylink.com/downloads/file?id=1261
Resolving www.displaylink.com (www.displaylink.com)... 52.208.143.240, 34.252.223.12, 54.72.7.162, ...
Connecting to www.displaylink.com (www.displaylink.com)|52.208.143.240|:443... connected.
HTTP request sent, awaiting response... 303 See Other
Location: http://assets.displaylink.com/live/downloads/software/f1261_DisplayLink%20USB%20Graphics%20Software%20for%20Ubuntu%204.4.zip?AWSAccessKeyId=AKIAJHGQWPVXWHEDJUEA&Expires=1543072882&Signature=n7BbLe9VuKiz51JXY4YsN31bPxU%3D [following]
--2018-11-24 22:08:28--  http://assets.displaylink.com/live/downloads/software/f1261_DisplayLink%20USB%20Graphics%20Software%20for%20Ubuntu%204.4.zip?AWSAccessKeyId=AKIAJHGQWPVXWHEDJUEA&Expires=1543072882&Signature=n7BbLe9VuKiz51JXY4YsN31bPxU%3D
Resolving assets.displaylink.com (assets.displaylink.com)... 52.218.80.194
Connecting to assets.displaylink.com (assets.displaylink.com)|52.218.80.194|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 17626360 (17M) [application/octet-stream]
Saving to: ‘DisplayLink_Ubuntu_4.4.zip’

DisplayLink_Ubuntu_4.4.zip                           100%[=====================================================================================================================>]  16.81M   259KB/s    in 48s     

2018-11-24 22:09:18 (360 KB/s) - ‘DisplayLink_Ubuntu_4.4.zip’ saved [17626360/17626360]


-------------------------------------------------------------------

Preparing for install

Archive:  DisplayLink_Ubuntu_4.4.zip
  inflating: 4.4/LICENSE             
  inflating: 4.4/displaylink-driver-4.4.24.run  
Creating directory displaylink-driver-4.4.24
Verifying archive integrity...  100%   All good.
Uncompressing DisplayLink Linux Driver 4.4.24  100%  

-------------------------------------------------------------------

Installing driver version: 4.4

DisplayLink Linux Software 4.4.24 install script called: install
Distribution discovered: Debian GNU/Linux 9.5 (stretch)
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64-ubuntu-1604/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing licence file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices

Please read the FAQ
http://support.displaylink.com/knowledgebase/topics/103927-troubleshooting-ubuntu

-------------------------------------------------------------------

Performing post install steps

ln: failed to create symbolic link '/opt/displaylink/libstdc++.so.6': File exists
root is not in the sudoers file.  This incident will be reported.
Disabling PageFlip for modesetting

-------------------------------------------------------------------

Performing clean-up
Removing redundant: "DisplayLink_Ubuntu_4.4.zip" file
Removing redundant: "4.4" directory

-------------------------------------------------------------------

Install complete, please reboot to apply the changes

-------------------------------------------------------------------

root@dev-12:/home/dka/workspace/github.com/AdnanHodzic/displaylink-debian# 
  1. Reboot

Post installation

dka@dev-12:[~]: systemctl status dlm.service
● dlm.service - DisplayLink Manager Service
   Loaded: loaded (/lib/systemd/system/dlm.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
dka@dev-12:[~]: 
dka@dev-12:[~]: sudo systemctl status dlm.service
[sudo] password for dka: 
● dlm.service - DisplayLink Manager Service
   Loaded: loaded (/lib/systemd/system/dlm.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
dka@dev-12:[~]: sudo systemctl start dlm.service
dka@dev-12:[~]: sudo systemctl enable dlm.service
dka@dev-12:[~]: xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x43 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 2 associated providers: 0 name:modesetting
  1. Reboot
  2. Same result, only 1 provider, so I unplug, replug my screen in USB
  3. New result:
root@dev-12:/home/dka# xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x43 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 2 associated providers: 0 name:modesetting
Provider 1: id: 0x124 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
  1. Activate the screen:
$ root@dev-12:/home/dka# xrandr --setprovideroutputsource 1 0
  1. Open in Cinnamon Display:
  2. Activate the screen Asus

Result

The Asus MB168+ is having a black screen.

I've recorded a youtube video to show the bug:

https://youtu.be/RvzCU2OVqJo

Logs

root@dev-12:~# dmesg | grep evdi --color=auto
[    5.806122] evdi: loading out-of-tree module taints kernel.
[    5.806714] evdi: [I] Initialising logging on level 5
[    5.806714] evdi: [I] Atomic driver:no
[   75.988439] evdi: [D] evdi_add_devices:134 Increasing device count to 1
[   75.988689] evdi: [D] evdi_crtc_init:353 drm_crtc_init: 0
[   75.988753] evdi: [W] evdi_painter_crtc_state_notify:486 Painter does not exist!
[   75.988755] evdi: [D] evdi_detect:79 Painter is disconnected
[   75.988757] evdi evdi.0: No connectors reported connected with modes
[   75.989571] evdi evdi.0: fb1: evdidrmfb frame buffer device
[   75.989574] [drm] evdi: evdi_stats_init
[   75.989577] [drm] Initialized evdi 1.5.1 20180731 on minor 1
[   76.032273] evdi: [D] evdi_painter_connect:574 (dev=1) Connected with ffff987ac2326a00
[   76.032275] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[   76.032294] evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 3
[   76.052251] evdi: [W] evdi_painter_disconnect:595 (dev=1) An unknown connection to ffff987ad2893800 tries to close us
[   76.052252] evdi: [W] evdi_painter_disconnect:596  - ignoring
[   76.052369] evdi: [W] evdi_painter_disconnect:595 (dev=1) An unknown connection to ffff987ad2893800 tries to close us
[   76.052370] evdi: [W] evdi_painter_disconnect:596  - ignoring
[   76.242231] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[   76.242239] evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
[   76.242413] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[   76.242418] evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
[   76.243253] evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 3
[   76.246320] evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 3
[   77.013113] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[   77.013121] evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
[  131.684563] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[  131.684567] evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
[  171.378376] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[  171.378378] evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
[  187.156327] evdi: [D] evdi_painter_mode_changed_notify:507 (dev=1) Notifying mode changed: 1366x768@60; bpp 32; 
[  187.156331] evdi: [D] evdi_painter_mode_changed_notify:508 pixel format 875713112
[  187.156346] evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 0
[  187.381156] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[  187.381167] evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
[  204.872930] evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 3
[  205.183933] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[  205.183935] evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
[  214.685089] evdi: [D] evdi_painter_mode_changed_notify:507 (dev=1) Notifying mode changed: 1366x768@60; bpp 32; 
[  214.685093] evdi: [D] evdi_painter_mode_changed_notify:508 pixel format 875713112
[  214.685141] evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 0
[  214.685146] evdi: [D] evdi_painter_dpms_notify:470 (dev=1) Notifying dpms mode: 0
[  214.780702] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[  214.780704] evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
[  225.778808] evdi: [D] evdi_painter_crtc_state_notify:483 (dev=1) Notifying crtc state: 3
[  226.029311] evdi: [D] evdi_detect:76 (dev=1) Painter is connected
[  226.029313] evdi: [D] evdi_painter_get_edid_copy:217 (dev=1) 00 ff ff
root@dev-12:~# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    2
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 158
Model name:            Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz
Stepping:              9
CPU MHz:               799.871
CPU max MHz:           3800.0000
CPU min MHz:           800.0000
BogoMIPS:              5808.00
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              8192K
NUMA node0 CPU(s):     0-7
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch invpcid_single ibrs ibpb stibp kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
root@dev-12:~# lspci
00:00.0 Host bridge: Intel Corporation Device 591f (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 5912 (rev 04)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1)
00:1c.7 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #8 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

Note that:

  • Doing mv /etc/X11/xorg.conf.d/20-displaylink.conf /tmp/20-displaylink.conf permit the screen to display but not to respond.
  • Upgrading to latest master show a black screen.

Is the conf file wrong for my computer?

@AdnanHodzic
Copy link
Owner

AdnanHodzic commented Nov 24, 2018

  1. I remember your graphics card was i915. Because if you look at latest master: https://github.com/AdnanHodzic/displaylink-debian/blob/master/displaylink-debian.sh#L304

Your /etc/X11/xorg.conf.d/20-displaylink.conf file should contain following:

Section "Device"
  Identifier  "Intel"
  Driver      "intel"
EndSection

Can you confirm this is the case? If it is, what results do you get with this being as part of 20-displaylink.conf?

  1. What were the contents of /etc/X11/xorg.conf.d/20-displaylink.conf in that Youtube video?

  2. Are changes better or worse with latest changes from master?

@kopax
Copy link
Author

kopax commented Nov 24, 2018

It appear that I was not having this file.

root@dev-12:/home/dka# cat /etc/X11/xorg.conf.d/20-displaylink.conf
Section "Device"
  Identifier  "DisplayLink"
  Driver      "modesetting"
  Option      "PageFlip" "false"
EndSection

Using your version, I am able to use my screen. I hope it will be stable. Thanks a lot for supporting the display link driver on Debian. I've just saved 100$. Thanks a lot and keep up with the good work.

@kopax kopax closed this as completed Nov 24, 2018
@NoNeedForNames
Copy link
Contributor

Wait, you ran the script and it didn't create the 20-displaylink.conf at all?

@kopax
Copy link
Author

kopax commented Nov 24, 2018

It was here. Just wrong driver.

@NoNeedForNames
Copy link
Contributor

sorry for not letting this go, but which version are you using?
the "modesetting" or the "intel"-driver version?
and which one did the script install?

@kopax
Copy link
Author

kopax commented Nov 24, 2018

You are right not to let go.

  • I am using the intel driver version
  • the script installed the mode setting driver version

@kopax
Copy link
Author

kopax commented Nov 24, 2018

Sorry for asking you that, but we're on Linux, do you know a way to have it ON on boot ?

After each reboot I must do:

$ root@dev-12:/home/dka# xrandr --setprovideroutputsource 1 0

Then manually do:

  • Open Menu
  • Type search for Display,
  • Open Display
  • Select my screen
  • Toggle ON
  • Positionate my screen appropriatly
  • Click on Apply

@AdnanHodzic
Copy link
Owner

@kopax awesome, glad it's working as expected now. Spread the word :)

Regarding having to configure displays each time this is a problem with hotplug on Debian and Kali Linux, and you can adress this by following Automated (persistent) display configuration

@NoNeedForNames I looked into code again as part of last commit I fixed the problem I addressed the issue.

Problem was that check (if ([ "$drv" == "i915" ] && [ "$cardsub" == "530" ]);) was too specific.

Even if lspci -nnk | grep -i vga -A3 | grep 'in use'|cut -d":" -f2|sed 's/ //g' returned i915, it wouldn't matter because in conjunction with lspci -nnk | grep -i vga -A3|grep Subsystem|cut -d" " -f5 which if didn't return 530 it wouldn never validate as true.

Reason was && which means both conditions have to be true. That's why "intel" part was never used, and it always went for "modesetting" driver.

So in the end I removed cardsub part as it's too specific, for example on Lenovo X1 Carbon which I'm typing this on, although drv would return i915, cardsub part would return Core. Which would also go for "modesetting" driver although it should've went for "intel".

Either way, I should've noticed this as part of your second MR but I missed it, it happens :)

@kopax
Copy link
Author

kopax commented Nov 24, 2018

@AdnanHodzic Happy to help to fix bugs. I'm also interested to read that you are using a Lenovo X1 Carbon. Which generation do you use?

I have myself a X1 Carbon Lenovo with Debian Stretch, it is my main working tool and I often travel, that's why I have a USB screen at the first place.
Since I am notified from every change on GitHub, I have tried many times to reinstall your driver. I was still not able to use it with my Lenovo X1 Carbon, even after formatting my OS.

Do you mind if I re-open this and to have a second look if I go through the same diag?

@kopax kopax reopened this Nov 24, 2018
@NoNeedForNames
Copy link
Contributor

NoNeedForNames commented Nov 24, 2018

I thought this was the plan. in my first commit i was too wide (only grepping for not being the i915 driver). and for some users with different intel-graphics than mine (HD 530), the script didn't work properly, so i added a second statement "530" to exclude the other intel-graphics which had problems with my script-version... was there a mistake then in my first commit i didn't see?

@AdnanHodzic
Copy link
Owner

AdnanHodzic commented Nov 24, 2018

@kopax Let's close this story as it's getting out of its original scope. Could you please open new story, i.e: "Doesn't work on Debian Stretch" and just paste install output, and as first two steps of post installation guide suggest, make sure you have UEFI/secure boot disabled and you're logging in to X server and not Wayland. Because IIRC Wayland has been set as default in Stretch. Also include which kernel/X version you're using.

DisplayLink works fine on my Lenovo X1 Carbon which I don't use that often as I use for private use. For work I use MacBook Pro (2017 with TouchBar) on which you can also run Ubuntu :)

@NoNeedForNames right, I honestly don't remember, but here's an idea. If you wanted and still want to exclude 530 you can put it back, and just use something like if ([ "$drv" == "i915" ] && [ "$cardsub" != "530" ]); or maybe even add a seperate elif block which would explicitly say what do in case [ "$cardsub" != "530" ]

I apologize for confusion.

@kopax
Copy link
Author

kopax commented Nov 24, 2018

Ok @AdnanHodzic I close this and will open a new issue. Thanks in advance.

@kopax kopax closed this as completed Nov 24, 2018
@AdnanHodzic
Copy link
Owner

@kopax @NoNeedForNames JFYI, In latest commit, I've added code which will now allow "displaylink-debian" to automatically configure your Xorg config based on your graphics card.

This feature may still be bit rough around the edges and might need some improvement. So if you have still have problems after pulling latest changes and running "re-install", please re-open this story and add output of following commands:

cat /etc/X11/xorg.conf.d/20-displaylink.conf
lspci | grep -i vga
lspci -nnk | grep -i vga -A3 | grep 'in use'|cut -d":" -f2|sed 's/ //g'
lspci -nnk | grep -i vga -A3|grep Subsystem|cut -d" " -f5

@AdnanHodzic
Copy link
Owner

@kopax I remember a comment you made about saving $100, so I've just added project donate button in case you or anybody else is feeling like contributing :)

@stratemeyerjw
Copy link

stratemeyerjw commented Sep 23, 2019

In case anyone else finds this useful.
I got my AOC usb monitor to work near perfect after many hours of futzing with the lag/choppiness.
System is -
Lenovo E545,
Debian 10 (testing, Mate, updated), compiz window manager, compiz mate tweaks
Kernel 5.2.0-2-amd64
AMD A10 with Radeon APU
Monitor is - (lsusb) DisplayLink E1659Fwu

  1. used the displaylink debian installer
  2. changed /etc/X11/xorg.conf.d/20-displaylink.conf
    Section "OutputClass"
    Identifier "DisplayLink"
    # MatchDriver "evdi"
    # Driver "modesetting"
    Driver "amdgpu"
    Option "AccelMethod" "none"
    Option "Tiling" "true"
    Option "Pageflip" "true"
    Option "ExaNoComposite" "false"
    EndSection
  3. run at login as user (or make bash script to do so for you).
    xrandr --setprovideroutputsource 1 0 && mate-display-properties

hope this helps someone with this!

@jl2035
Copy link

jl2035 commented Jul 25, 2020

Wait, you ran the script and it didn't create the 20-displaylink.conf at all?

@NoNeedForNames that happened to me on 20.04. I even tried to manually create a directory /etc/X11/xorg.conf.d and ran the installation again, but no success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants