-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
Debian SID : Fail to connect screens #130
Comments
Are you logging into X11 session? WIth Sid/Booster Wayland has been set to be default, and Displaylink doesn't work on Wayland ATM. |
Hi, I'm aware of that and I'm logging into X11 session (choose Gnome on Xorg when logging) The only thing I've done is an aptitude upgrade, kernel was updated to 4.16 but I have the same issue with 4.15. |
to add more informations dlm.service is started xrandr --listproviders And you will find in attachment a dmesg |
What happens if you temporarily remove this file: If doesn't do anything, could you please add |
Ok so I tried to remove /usr/share/X11/xorg.conf.d/20-displaylink.conf but it does nothing And when adding nomodset nothing too (tried with nomodeset and it's not booting) Here is what I added : Maybe I've done something wrong ? I tried with Kernel 4.16, should I retry with 4.15 ? |
So after adding
|
After adding nomodeset it's not booting at all, I have a black screen and nothing (have to boot in recovery mode to remove nomodeset) I added elevator=deadline to change the I/O scheduler, and radeon.modeset=0 modprobe.blacklist=radeon is a workaround to solve a vce init error radeon 0000:08:00.0: failed VCE resume (-110) |
If I cannot solve this issue I think I will just migrate to Ubuntu for my professional Laptop Too much issues like that with Debian SID, maybe I've underestimated the unstability of Debian Unstable (Yeah I know many people would say that they never had problems for years) |
I'm really not sure what the problem is here. It definitely takes a lot of dedication to use Debian Sid as your work laptop. I would recommend using Testing/Buster, or even if Stable/Stretch with APT pinning. I wrote about this topic few years ago in case you decide to go down this path: Taking control over Debian and its package repositories Either way, let me know if you end up having same issue with whatever out of these you decide to go with. Similiar problem was reported on Ubuntu 18.04 yesterday but was resolved with |
Ok I think I will make a try with Ubuntu 18.04 and report if it work well Thanks for your time |
Ok so I moved to Ubuntu 18.04 and it's working fine For now I will keep Ubuntu and switch to Debian later |
Great, also out of curiosity did you have to make any customizations. Or |
It worked out of the box, But I think I will go back to Debian, I will try testing with apt pining |
I can second the issue, but I haven't figured out the cause yet. I've been successfully running a pair of displaylink adapters under Sid with 4.16 for a while and all of a sudden today while doing nothing out of the ordinary my session crashed and it kicked me out to the login screen. I haven't run an |
I too noticed this, using the latest install script, the only temporary solution I have found is to remove the /use/share/X11/xorg.config.d/20-xorg.displaylink.conf file and keep my old one that I made along with the very first install of this driver. |
I managed to get back up and running by @redjamesg -- can you share your |
Hi, Ok so I decided to reinstall Debian testing and it's working fine. I'm using apt pining for some softwares but displaylink is working with the last script Maybe a broken xorg that have been fixed |
This is my current xorg.conf
|
@redjamesg what happens for you if you add Would love to extend it so we could potentially have an universal file which we could use everywhere. |
What I was experiencing, was after installing with teh latest script my three monitors were working as expected without any issues, but two days later they startet acting up. I will on a later instance try the "VSync" "False" setting in the orriginal 20-displayling.conf to verify if that has an impact on my issues. |
OK, it turns out I have to use the
settings in the 20-displaylink.conf file else my monitors wont be correct activated and I will end up with the described freezing/black/grey screens described in #68 My setup is Dell XPS13 9360 with a Toshiba Dynadoc U3 PA3729E-1PRP displaylink and three monitors.
And my activation script for the screens are:
dmesg when connecting the dynadoc
And to clarify the USB identification some more info:
And the PCI bus:
And lastly the processor info:
|
Had a similar problem when using this on Debian Testing few months ago. I followed the advices in #68. My Edit: Just realized that my comment doesn’t help with this issue. I’m really sorry for posting this. But I experience the same issue with Debian Testing (kernel version |
I'm closing this issue for inactivity. Please re-open the issue If you're still experiencing same problem after pulling latest updates and running reinstall. |
Hi,
This morning I had an issue when trying to connect my displaylink device.
When I activate my screens it brings back to the login screen.
I thought it was kernel related (this weekend I updated to 4.16) so I reverted back to 4.15.0.3 and reinstalled the displaylink driver but I have the same issue.
Can you help me with this ?
Regards,
ODI
The text was updated successfully, but these errors were encountered: