-
-
Notifications
You must be signed in to change notification settings - Fork 881
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
Monitors connected through displaylink dock get no signal #7292
Comments
linked to hyprwm/aquamarine#22 |
update aq to git check if it gets signal when you start hl with it connected |
The logs were made with 9b33a38f86135db1b26f21d8581d512dbe106549, so pretty much the latest git (apart from a docs update) |
I mean I do feel like it's a driver issue? Ubuntu Wayland is Gnome, it doesn't work. Does KDE work? If not, I'm fairly certain it's a driver issue |
I'll try on KDE and with the latest Nvidia beta drivers soon. Also, I added some more dmesg logs (with drm debugging enabled) in this comment: DisplayLink/evdi#484 (comment), might be useful to figure out what exactly happens. |
Im chippin' in on this one - after 0.42 update on Arch my third screen is no longer displaying anything, though it seems enabled and ready to hyprctl. I did an update to hyprland-git and aquamarine-git, both did not change the situation. Its a Dell laptop with a Dock, DP-4 (working) and DP-5 (the display in question) are connected via a docking station. I'd prefer to use the dGPU (NVIDIA MX250) since the laptop is used pretty stationary and power consumption is therefore not thaaaat important :) I also set X11 / Gnome worked fine, still need to test Wayland / Gnome (will update as soon as i have the time) hyprctl systeminfo
hyprctl monitors
Crashlog AQ on dGPU
|
Are the drivers for card1 installed? Can you post a log from 0.41.2 with |
Sure thing, downgraded via pacman cache, DP-5 startet working again right away. I did not change the drivers, at least im not aware of any change, maybe they were updated in the same pacman/yay run with hyprland - I didnt pay too much attention, sorry. Edit: Installed nvidia drivers:
Edit2: I found the upload-Button. Heres the Log, if I should grep for anything specific, just let me know: Logfile 0.41.2
|
please attach the file next time :P I'll take a look tomorrow. |
please try the above mr |
That should be in aquamrine-git (aur), right? |
no, it's a MR. You have to checkout it manually and install locally |
I hope i have it right --> pulled Aquamarine from MR above, built like in the readme, "sudo make install", installed hyprland-git (for 0.42), but still DP-5 is black. Logfile attached. |
Same problem here, and also seem related to #7321 Dell XPS laptop (have dual GPU's Intel and Nvidia but I have no NVIDIA kernel modules loaded). Everything is running fine on hyprland-0.41.2-3 but when I upgrade to 0.42 second screen goes black. The following config works works on 0.41 but not on 0.42 monitor=eDP-1,[email protected],0x0,2 On 0.42 I tried removing the resolutions and setting preferred does not work (just black) Setting the screen to highres does work but selects a lower resolution Any more info I can contribute with, or anything I can test to help out? |
on 0.41.2: Run hyprland with on git: install both aq-git and hl-git from right now, and run both logs would be nice. |
Thanks @vaxerski Here are both logs: 0.41.2.log Dont know exactly what Im looking for, but I can see some new errors related to the external monitor DP-3 in the latest 4.2 [ERR] [AQ] Wayland backend cannot start: wl_display_connect failed (is a wayland compositor running?) |
I should add that I'm also on a laptop with a dedicated and integrated GPU, but the integrated GPU is disabled in the BIOS with a MUX switch, so everything is done through the Nvidia GPU. I'll try the latest hyprland-git and aq-git sometime this weekend, as well as KDE. Also, I'm running an older release of Hyprland (I think 0.40.0 or something) on my work laptop (which has an intel integrated GPU), and my dock works fine on that system. So I guess it works due to either the Intel GPU, or wlroots instead of aquamarine, or both. I might test the latest release on my work laptop this weekend too, if I find the time. |
Decided to test the latest hyprland-git and aquamarine git already, Hyprland now crashes when I start it while a monitor was connected to my dock... hyprland.log (with HYPRLAND_TRACE and AQ_TRACE) |
@zjeffer debug stacktrace with aq in debug pls |
anyways should be fixed in aq |
The manual installation of the aq MR didnt work for me - did I make a mistake above? Sorry if that sounds noobish :) |
MR is merged, you can use normal aquamarine-git |
Thanks, gonna try on monday right away, for its my work Laptop. 0.42 on my main desktop worked flawless on nix :) |
Tested on KDE Plasma: display connected to dock works on X11, but no display on Wayland, though the monitor is visible in the display settings (same behaviour as Gnome). It doesn't crash anymore on startup but I notice unplugging and replugging my amplifier (connected directly to my laptop with HDMI) now crashes Hyprland on the latest Hyprland and aquamarine git commits. I'll do some more testing and get some logs. EDIT: I can't get it to crash anymore but here's the crash report from when it happened: |
On latest commits, this is now present in dmesg when connecting the monitor:
And this nvidia-drm error keeps going for as long as the monitor is connected to the dock. |
The monitor connected to the dock does work when I enable hybrid graphics in my BIOS (intel+Nvidia) instead of only using the Nvidia GPU. Sadly, for my laptop (Lenovo Legion 5 Pro) hybrid graphics on linux results in incredibly bad screen burn-in on my laptop display in mere seconds of usage. Some people in this reddit thread report the same thing: https://old.reddit.com/r/LenovoLegion/comments/miqbv4/lenovo_legion_5_pro_actual_linux_experience_and/. So this is not an option for me. Luckily the burn-in is only temporary and goes away after a couple of minutes. |
wait so the monitors are broken on gnome wayland and kde wayland? If that's the case I don't think this is a hl issue |
I think so too, like I mentioned in the description of the issue:
Now that I've tested on both gnome wayland and KDE wayland, I think we can indeed conclude it's probably not a Hyprland issue. |
Regression?
No
System Info and Version
System/Version info
Description
The dock works on Windows and Ubuntu through X11, doesn't work on Ubuntu with Wayland and on Hyprland. Likely an Nvidia issue? I opened an issue about this in the
DisplayLink/evdi
repo (DisplayLink/evdi#484), but I thought I might try my luck here as well, if only to gather more info on the cause of the issue.When connecting the monitor, it turns on, notices it gets no signal and goes back into standby. The monitor (DVI-I-1) is in the list of monitors reported by
hyprctl monitors
, and workspaces are assigned to it:monitors
I notice
currentFormat
isInvalid
🤔How to reproduce
Connect the monitor to a docking station. Monitor gets no signal.
Crash reports, logs, images, videos
Starting Hyprland with the monitor disconnected, then connecting the monitor to the dock: hyprland-trace.log
Monitor (
Acer Technologies K222HQL T0EEE0018512
) is connected at19:59:50.463896533
The text was updated successfully, but these errors were encountered: