-
-
Notifications
You must be signed in to change notification settings - Fork 900
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
External Monitor via Thunderbolt Dock not Working after 0.42 Update #7321
Comments
what's your aquamarine version? have you tried aq-git and hl-git? |
Aquamarine 0.3.1. Neither is -git but I'll switch over to those and see if that works. Thanks! |
Updated both hyprland and aquamarine to -git from chaotic AUR and still having the same issue. Perhaps it is related to this: hyprwm/aquamarine#40 (comment) |
does dynamically disabling and re-enabling them fix it? |
Not sure I follow correctly. If by "dynamically disable and reenable" you mean disabled and reenabled in hyprland config, then that does not work. Disabling any display via the config disables it but rather than turning the display off it is left with a freeze-frame of it's contents when disabled. The third display does not turn on even if it is the only enabled display in the config. I also tried sticking with just ",preferred,auto,auto" and the third display still does not work. |
Same symptoms, Dell TB16 dock. Will try to narrow down the specific issues later, but had to roll back to 0.41 for now. |
Same. Rolled back to 41.2 and it immediately worked on reboot. It seems my issue is almost the exact same as #7292 (comment) One of my external monitors works fine, the other says no signal despite hyprctl displaying it as connected and active. |
I experience this problem too, on both my TB16 docks. I don't want to push anyone in the wrong direction but I did have to add the environment variable |
Thanks! -- but fwiw I'd never come across that env var before and am not / have never used it, but have no problems on Hyprland < 0.42, so I dunno 🤷 |
can you test the above MR? |
Just checked out the branch and installed it locally, still no dice. I've attached logs from this session below if they are of any help |
And cause I'm an idiot and didnt have debug logs enabled... here you go Noticing this line in particualr
|
Also may be worth mentioning, my CPU is pegged at 60-70% usage by Hyprland with the third (no signal) Monitor enabled, disabling the monitor in my config drops Hyprland back down to its normal CPU utilization around 10-15% according to btop |
Found a page from Sway on DRM debugging for wayland compositors and followed along since it seems to be tied to the issue in my logs. Here's DRM logs (with KMS and Atomic messages enabled) in case this helps (very verbose). |
And now in a strange turn of events, DP-2 sometimes receives a black screen with 720x400@70Hz, and sometimes receives no signal when enabling it in my config. I think I'm done spamming updates now haha |
FWIW, this may be related to #7356, which has a fix in e947af7. That issue apparently relates to damage clip boxes, which seems like it miiight be close enough to be affected by whatever our monitor problem is. |
Nope that's not it. Just installed latest -git and still not fixed. The CPU usage is surely related to the many log messages regarding drm modesetting for DP-2. |
Had to work in the office today so figured I'd do a bit more testing with another adapter and more displays. Our 4K display was displaying black at native resolution with existing config, also reported as via DP-2. Changing that to 1080@60 does indeed work, changing back to 3840x2160 causes the display the freeze and the computer to slog. Some new errors about drm mismatches not seen on my dock at home so I included a log here. The news lines are about buffer format mismatch: |
post a trace log please with kms issues the regular one isnt verbose enough https://wiki.hyprland.org/Crashes-and-Bugs/#obtaining-a-trace-log |
Here you go Vaxry! Tried to keep it as short as possible, let me know if you need me to let it run a bit longer. Thanks for your patience with all these monitor woes This is on my work display with a usb-c adapter (wherein DP-2 is working at 1920x1080@60 but not with 3840x2160@30). I can also get logs from my home TB dock where even 1080p with another Samsung display does not work in a couple hours in case the issue differs there. |
And here are trace logs from my TB4 Dock (DP-2 monitor not receiving signal, integrated display and DP-1 work fine) |
I have some not so great updates, something must have changed in recent -git builds from today. Now when booting with all 3 monitors integrated display(eDP-1) is just black unless DP-2 is disabled. If DP-2 is enabled at boot, and I disable it to get eDP-1 working, the mouse stops working properly on DP-1 but works fine on eDP-1. Perhaps new issues introduced with 912e7ba ? I can do some more testing, get logs, and try bisecting tomorrow if you want. Sorry for the further complications :( |
Getting a similar error on that commit - I posted #7381 a few hours ago with the logs. |
Here are some logs I got today, these of all 3 monitors connected and enabled at boot, both eDP-1 and DP-2 receive a black signal at proper resolution and framerate this time, DP-1 works fine. Disabling DP-2 makes eDP-1 work properly. I didnt get logs while executing changes to keep them short but can if that would be helpful |
I have the same problem, but running through HDMI and not Thunderbolt. Had some discussion in #7292 (comment) but that ticket is closed now. I have tried today with the latest aq-git and hl-git from today |
Getting the same issue as this and #7431. Let me know if its needed and I'd be happy to provide logs I was also getting a hyprland crash in prior versions when I woke from hibernation in a different state then when I slept (ie crash on wake if I unplug my laptop while it was hibernating), something about monitors not being found. but I never got around to reporting it. I don't know if its related. |
I have the same problem. Hot-(un)plugging any kind of monitor (does not matter whether USB-C, HDMI, DP, or via Thunderbolt Dock) causes Hyprland to crash. Didn't create a new issue, since there are already many of those issues open. But if there is any need, I am happy to provide logs. For now my workaround was a downgrade to version 0.41 |
aq-git has just recently got a few fixes for it. my dual gpu laptop now hotplugs. but might be more things to work out. so test -git |
Upgraded to I have not observed crashes for the following scenarios anymore
The same is true for connection to multiple monitors via Thunderbolt Dock. I still have an issue with too many monitors attached to my laptop via the Dock (my laptop's graphics card supports 3 simultaneous outputs, but I have 4 screens: Laptop internal screen + 3 external Monitors via the Dock). In this scenario, even if disabling one of them (e.g. the internal laptop screen), does not allow me to enable the other extra external screen. The screen stays blank and the output displayed with But for all I am concerned, this is a different issue. If an issue at all and not just a hardware limitation. So consider this non-important for this specific issue. |
I have a very similar issue. Opened an issue about VRR causing the monitor to dis- and reconnect. I have the proprietary NVIDIA drivers installed using this script https://github.com/Frogging-Family/nvidia-all I am on hyprland-git and aquamarine-git and update with yay -Syu --devel. Also I am using evdi-git and displaylink, because without them I didn't really get any output whatsoever through DP-1. Before 0.42 I used to do this to get output through DP-1
When I first updated to 0.42, the monitor connected through DP-1 had a broken output. If I moved the cursor over that monitor, I would see movements in pixels, but it stayed broken. While writing this comment I decided to update again aquamarine and hyprland and the latest one finally gives me stable output through DP-1 (type c hub). Here is the
|
Not working on my side with latest hl-git and aq-git: hl: v0.42.0-58-gf634b9e6 Starting hyprland with monitor connected - works. If i re-plug the monitor (docking station) - monitor stays black. Here are the logs at the moment of plugging in the docking station with monitor:
[LOG] [AQ] [libinput] event8 - palm: keyboard timeout
[LOG] [AQ] udev: new udev add event for card1-DP-3 [LOG] [AQ] [libinput] event16 - Wacom One by Wacom M Pen: device is a tablet [LOG] [AQ] libinput: New device Wacom One by Wacom M Pen: 1386-891 [LOG] Binding tablet wacom-one-by-wacom-m-pen to output |
can you retry re-plugging it on git again |
@ikalco latest -git brought back my problem in #7322 :(. I'll post the logs tomorrow (what logs would help? the same as #7322 (comment)?) |
at a glance the dmesg.log from before has some weird errors in it, which could be because of this
if you are crashing again then post crashdump and hyprlandd.log |
Hi!
hl-git: 0.42.0.r86.b9b8e622-1 Regards! |
Still no luck here. Starting with external monitor DP-3 plugged in or plug/unplug does not matter, always black screen while connected since upgrade. Seems like its a DRM issue. Should this issue be reported in the aquamarine project? Host: XPS 15 9500 hl-git: b9b8e62
|
@stjernstrom can you get a kernel drm log of when you plug it in echo 0x19F | sudo tee /sys/module/drm/parameters/debug # Enable verbose DRM logging
sudo dmesg -C # Clear kernel logs
dmesg -w >dmesg.log & # Continuously write DRM logs to a file, in the background
Hyprland
fg # Kill dmesg -w with Ctrl+C
echo 0 | sudo tee /sys/module/drm/parameters/debug # Disable DRM logging you just need to run this, plug in monitor, then exit Hyprland, finally ctrl+c |
@stjernstrom you should start a new issue, something like from what I can see in the dmesg.log
it seems your gpu isn't capable of using 3 monitors? try only plugging in 2 to test |
Thanks @ikalco I'll start a new issue if it seems to be different problems than the original issue 👍 For clarity and history of this thread I have been running this exact hardware configuration since I started using Hyprland and Its just when I upgrade to 0.42 I does not work _ (and I'm just using one external monitor :) _ |
please build if it resolves your issue, please close the ticket, thx |
I did not have the same setup the initial reporter, I'm using HDMI and no dock, but I can confirm that it now works for me. I'm running lastest Awesome work! I appreciates the effort and support! |
That seems to have done the trick! All monitors working for me without issue now. Thanks for all the hard work it is much appreciated, closing the issue now. |
This doesnt seem to have fixed my issue. Still get a black screen on connect / disconnect with latest aquamarine-git (not sure how to check specific version) and hyprland-gt (b0fca6e), using a thunderbolt port and a thunderbolt-enabled monitor. |
@croots can you make a new issue, something like btw look at hyprwm/aquamarine#76 and test if you have the same issue |
@croots have you set the ENV variable? 'env = AQ_NO_MODIFIERS,1' |
@romanstingler yep, set in my config, appears correctly in a terminal emulator when I echo it. |
New updates with AQ_NO_MODIFIERS did for me, all is well again :-). Thanks for the work, guys. |
Possible I missed a version, but I think only around 2-3 weeks since last update. This hit me when grabbing 0.44.1-1 from As instructed in this Issue, I updated to Based on comments in this issue, I reduced the resolution to My display supports up to So for me at least, the trigger is not the resolution, but the refresh rate. And the |
Regression?
Yes
System Info and Version
System/Version info
Description
After updating to v0.42 one of my external monitors is no longer working. Hyprctl lists the display as active (see logs) but the monitor does not display a signal.
Monitors are connected via a TB4 dock, I typically use a 3 monitor setup including laptop display. Editing config to disable built-in display also no longer turns the display off but rather leaves a still image on the disabled display.
Problem persists whether monitors are plugged in at boot or disconnected. This was working fine prior on wlroots and v<0.42.
How to reproduce
On a laptop with an iGPU, connect 2 moitors via TB4 dock. Built-in and first external display state,
Crash reports, logs, images, videos
Monitor Config
boltctl
Hyprctl - Monitors
The text was updated successfully, but these errors were encountered: