-
-
Notifications
You must be signed in to change notification settings - Fork 20
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 stays just lit black (HDMI) Notebook Intel integrated + Nvidia but should work on Intel #40
Comments
ye idk whats up here, looks like some driver bug |
I know, just very insteresting that it works on wlroots but not on AQ. it doesn't work on in the wiki we have
but the journal says that fbdev is unknown (probably deprecated)
Because I get an image on sway and also on HL <0.42 Unfortunately, I have absolutely no clue about the GFX stack. OK on 0.41.2 when starting with
It basically crashes the same with not as KMS device In my understanding, then the KMS "config/settings" must come from the iGPU. Because the internal monitor works which is connected to the iGPU
|
Experiencing what looks like the same on my single-gpu laptop (integrated intel)
When logging in, eDP-1 stays lit black, to fix I have to run |
Very similar issue here, on my hybrid Intel/Nvidia laptop. I'm getting a completely black screen on an HDMI output driven by the Nvidia dGPU — but not a "no signal" screen; the contents are just empty. Interestingly, I've discovered that mirroring my laptop's own eDP display (driven by the Intel iGPU) to the HDMI output, and then relaunching Hyprland, allows content to be displayed. Feels like some weird multi-GPU franebuffer copy shenanigans happening? Feel free to let me know if there's more I can do to test this! |
Hi, just to add to the stack - I'm experiencing similar issues, though on a single GPU laptop (Intel UHD 620). Back then on wlroots I had issues with running second external monitor (third overall), where on Hyprland launch it would only display one of the two connected external monitors - second would end up with No Signal. I actually got it working by launching Hyprland with only one external monitor connected, and physically connecting the second after launching hyprland. unfortunately, this stopped working somewhere along migration to aquamarine, and now I'm able to launch only (any) single external monitor again (I'm using HDMI + DP Alt mode). When both connected, I can see the black screen monitor in If I can be of any assistance, just let me know! |
...okay, I'm very confused now. As of today, with seemingly no relevant changes, my system, uh, partially works? If my external monitor is connected when Hyprland starts, it works as expected (and can even be reconfigured on-the-fly by (re: updates, mesa and vulkan were bumped earlier today, but a) not by much, and b) would that even affect aquamarine?) |
please try the above mr |
will do when I get home in 2 hours or so (if not too drunk) |
Issue still exists on my end |
It doesn't fix my monitor issue. when I install HL-git and start HL from tty , the external monitor first blinks as it would be inactive/disabled, what I found out is, |
ok lets do this, I'll need two logs:
|
Here you go PS: Mesa 24.1 or 24.3 doesn't change a thing PS2: I was not focused |
hyprland_git-aquamarine_git.log Both with |
@Hannes1909 are you on 10b? Can you disable it? If that doesn't help, can you get a drm log https://wiki.hyprland.org/Crashes-and-Bugs/#debugging-drm-issues @romanstingler I need a git log too |
Sorry can you elaborate on 10b? Doesnt Ring a bell :( |
10 bit |
During earlier testing, I found that I could get Hyprland to crash by playing around with monitor settings — specifically, starting with my external HDMI output set to mirror my laptop's eDP port, then editing Hyprland's config to disable the output altogether (i.e. the only I'm completely guessing, but based on my general feeling that framebuffer shenanigans are happening, a crash (which could occur due to said memory shenanigans) seems like it might help pinpoint what's going on here. |
not by choice, thats why i didnt know what that meant :) I have my internal laptop display on the left, DP-4 (working) in the middle and DP-5 to the right and rotated.
Ill add an DRM Log when i find the time today. Thanks! |
DRM Log from starting Hyprland, since the monitor is black from the beginning I just kept it running for a minute or so. |
560.35.03 doesn't fix it |
tldr +1 trying to serve two monitors with my dgpu nvidia. one connected to nvidia card, one connected to amd igpu. amd connected monitor is just black. both connected via separate displayports, no hdmi potentially relevant settings? env = LIBVA_DRIVER_NAME,nvidia |
FWIW, this appears to be fixed(?) in Git now; we just need to wait for a new release by the Arch team. Or, of course, use the |
My issue is a different one |
I can finally use 0.42 and bug Vaxry with all the bugs :P I got a new "screen" and played around and for me, After unplugging and re-plugging the HDMI cable, sometimes 1x sometimes 2,3x, Here is my Log
|
The latest changes fix the HDMI output. Now my internal screen and my HDMI external screen work just fine out-of-the-box. The only remaining issue is that I get no image on the UsbC=>Hdmi output. |
Confirmed here as well — mu dGPU's HDMI output now hotplugs properly. |
latest aq fixed it for me too :) thanks! |
From the AQ PR my outstanding MultiMonitor Bug.
I am using
Tag: v0.41.2-48-gf642fb97, commits: 4934
for now, as this is my office laptop, there everything is fine,DP-3
is my external HDMI monitor which stays blackI clean-built
hyprland-git 0.41.2.r166.0e86808e-1
the issue is still present.hyprland.log
hyprland.conf.txt
I have seen
[LOG] [AQ] libseat: Device /dev/dri/card1 does not support kms
no clue if I need
linux-headers
package, but on the stable release everything is fine.PS: for testing I used only
monitor=,preferred, auto, auto
which also doesn't work.No pressure guys, I just wanted to have it documented
The text was updated successfully, but these errors were encountered: