-
-
Notifications
You must be signed in to change notification settings - Fork 230
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
Monitor is not being detected post installation #430
Comments
I think I have the exact same problem to the letter. I had to fix the ln problem you mentioned in the linked separate issue, xrandr doesn't show the device, the 20-displaylink.conf files don't exist, xrandr --listproviders lists 5 entries... |
@pafribouf yes, I don't know. I audit the code hopefully I can spot the problem and resolve it. I'll be posting the same issue on StackExchange too. |
@Engineer22 Have you tried with this configuration?
|
@Barabazs should I erase everything inside the 20-displaylink.conf files, and replace them with your suggestion? Or should I add them in the config? |
Yes, replace the content with what I suggested. But first, backup the files... |
@Barabazs got it. I'll try it, and report back whether or not something changed. |
@Barabazs UPDATE: After I made the changes, I'm unable to login. I had to login via Wayland and revert the changes so I can login via xorg. I'm not sure if this is a good sign or not. Any guess on why it may be happening and any other suggestions? |
@Engineer22 Is there anything in the file /etc/X11/xorg.conf ? |
@Barabazs there is no such file. I though I had to create it, tried to genetate it via init, and failed. I then informed that you don't need that file at all, since we use files such as the 20-displaylink.conf, to create this type of configs. Do you think I need it, and how do you generate it. I read a couple of tutorials, but init keeps saying that an xorg session is running. TIA! |
Can't say for sure, but I don't think it's necessary. The reason I asked is, because according to previous issues, a difference between both files could lead to issues. My last guess would be try with this config:
|
@Barabazs I think that was my original config content, but I will try it again. Did you see any other user using the config file you mentioned? I'm still not 100% sure if I need it or not, but I cant generate it. |
@Barabazs just tried it. I login, but the resoult is same as the beginning of my issue. |
I'm out of ideas... Except maybe trying to uninstall, try to remove any leftover related files and retry the complete install procedure. |
I am experiencing the same problem on Debian 10 (buster). Once the driver got installed, the service wasn't running and no config file was created. I ran the service & created the file manuallly but xrandr is totally unable to detect the monitor. Here is the --debug output :
At the bottom you can see by yourself that 5 providers are listed. Providers got associated to the output after I ran xrandr --setprovideroutputsource 1 0 (I did that for 2 0, 3 0, 4 0 aswell) but it didn't changed anything. The displaylink device is listed in the |
I am having the same issue and I've tried everything at this point and nothing has worked. One thing I'm noticing right now is that unlike the --debug output in Adnan's example, is that in the above (and in mine) the DisplayLink Info only show's the EVDI version. Maybe its just a line of code that was forgotten and its no big deal. Second, in my case I noted that the DisplayLink driver that is installed is the version designed for Ubuntu 20.04 (5.3) while I'm currently on 18.04.5 and should be using 5.2. Again, I'm not sure if that is causing an issue. Lastly, I've noted that using the 20-displaylink configuration files forces the provides to be shown even when (as it is in my case) the docking station or monitors are not plugged in; and xrandr --current 'recognizes' displays that aren't plugged in show up as disconnected PS. @AdnanHodzic if you reading this there's a small bug in the script it occurs at the very end of the installation when the script asks whether it should restart now or later. If I say no, then and only then is the 20-displaylink.conf files written, but has the consequence of crashing my system and I have to REISUB, and if I say 'yes' then the system restarts without writing the files. Note in my --debug output that there is not file created this was in the 'yes' case. `Starting Debug ... Did you read Post Installation Guide? http://bit.ly/2TbZleK [y/N] y Did you read Troubleshooting most common issues? http://bit.ly/2Rofd0x [y/N] y --------------- Linux system info ---------------- Distro: Ubuntu ---------------- DisplayLink info ---------------- Driver version: 1.8.0 ------------------ Graphics card ----------------- Vendor: i915 -------------- DisplayLink xorg.conf ------------- File: /etc/X11/xorg.conf.d/20-displaylink.conf -------------------- Monitors -------------------- Providers: number : 5 Use this information when submitting an issue (http://bit.ly/2GLDlpY) $ xrandr --current Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 |
Please uninstall and reinstall with the latest version. The latest fixes should resolve your issue. #457 |
I'm a dummy - the screen was disconnected. Thank you for the fix! |
Closing this issue due to inactivity. Please reopen this issue if it still persists. |
Hello,
As a follow up of my previous issue, post-installation problems continue.
After rebooting the system I checked xrandr and the new monitor didn't apper. Running the debugger, I get these results after trying to apply this method. I tried this method, and also this one. Both failed to make the monitor detectable.
Additionally, /etc/X11/xorg.conf.d/20-displaylink.conf and /usr/share/X11/xorg.conf.d/20-displaylink.conf did not exist. I had to make them on my own and apply both suggested methods listed above.
Running xrandr it doesn't find the new monitor, but running xrandr --listproviders gives me 5 results. What should I try next? The debugging log is this (keep in mind that I already have an external monitor plugged in via HDMI, the problem occures on the new monitor which is an identicall one connected via HDMI-USB3 adapter):
Starting Debug ...
Did you read Post Installation Guide? http://bit.ly/2TbZleK [y/N] y
Did you read Troubleshooting most common issues? http://bit.ly/2Rofd0x [y/N] y
--------------- Linux system info ----------------
Distro: Debian
Release: buster
Kernel: 4.19.0-9-amd64
---------------- DisplayLink info ----------------
Driver version: 1.7.0
DisplayLink service status: up and running
EVDI service version: 1.7.0
------------------ Graphics card -----------------
Vendor: i915
Subsystem: Processor
VGA: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
VGA (3D):
X11 version: 1.20.4-1
X11 configs: /etc/X11/xorg.conf.d/20-displaylink.conf
-------------- DisplayLink xorg.conf -------------
File: /etc/X11/xorg.conf.d/20-displaylink.conf
Contents:
Section "Device"
Identifier "DisplayLink"
Driver "modesetting"
Option "PageFlip" "false"
EndSection
-------------------- Monitors --------------------
Providers: number : 5
Provider 0: id: 0xe9 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 4 associated providers: 0 name:modesetting
Provider 1: id: 0xc3 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
Provider 2: id: 0xa1 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
Provider 3: id: 0x7f cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
Provider 4: id: 0x41 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
The text was updated successfully, but these errors were encountered: