Skip to content
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

Black screen when setting env = AQ_DRM_DEVICES. On *dGPU Only*-capable laptop. #9124

Closed
4 of 6 tasks
gridrek opened this issue Jan 20, 2025 · 12 comments
Closed
4 of 6 tasks
Labels
bug Something isn't working

Comments

@gridrek
Copy link

gridrek commented Jan 20, 2025

Already reported ? *

  • I have searched the existing open and closed issues.

Regression?

I don't know, I started using Hyprland only recently

System Info and Hyprland Version

System/Version info
Hyprland 0.46.2 built from branch  at commit 0bd541f2fd902dbfa04c3ea2ccf679395e316887  (version: bump to 0.46.2).
Date: Thu Dec 19 19:26:47 2024
Tag: v0.46.2, commits: 5566
built against:
 aquamarine 0.7.0
 hyprlang 0.6.0
 hyprutils 0.3.3
 hyprcursor 0.1.11
 hyprgraphics 0.1.1


flags set:
debug


System Information:
System name: Linux
Node name: nobara-pc
Release: 6.12.10-200.nobara.fc41.x86_64
Version: #1 SMP PREEMPT_DYNAMIC Fri Jan 17 22:11:22 UTC 2025


GPU information:
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-P GT1 [UHD Graphics] [8086:46a3] (rev 0c) (prog-if 00 [VGA controller])
0000:01:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD107M [GeForce RTX 4060 Max-Q / Mobile] [10de:28a0] (rev a1) (prog-if 00 [VGA controller])
NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  565.77  Release Build  (dvs-builder@U16-A21-31-3)  Wed Nov 27 23:09:12 UTC 2024


os-release: NAME="Nobara Linux"
VERSION="41 (KDE Plasma)"
ID=nobara
ID_LIKE="rhel centos fedora"
VERSION_ID=41
VERSION_CODENAME=""
PLATFORM_ID="platform:f41"
PRETTY_NAME="Nobara Linux 41 (KDE Plasma)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=nobara-logo-icon
CPE_NAME="cpe:/o:nobaraproject:nobara:41"
DEFAULT_HOSTNAME="nobara"
HOME_URL="https://nobaraproject.org/"
DOCUMENTATION_URL="https://www.nobaraproject.org/"
SUPPORT_URL="https://www.nobaraproject.org/"
BUG_REPORT_URL="https://gitlab.com/gloriouseggroll/nobara-images"
REDHAT_BUGZILLA_PRODUCT="Nobara"
REDHAT_BUGZILLA_PRODUCT_VERSION=41
REDHAT_SUPPORT_PRODUCT="Nobara"
REDHAT_SUPPORT_PRODUCT_VERSION=41
SUPPORT_END=2025-12-15
VARIANT="KDE Plasma"
VARIANT_ID=kde


plugins:

Description

Same as this issue

"I want to use NVIDIA dgpu to start hyprland, so I found in the wiki.
But when setting environment variable by env = AQ_DRM_DEVICES,/dev/dri/card1:/dev/dri/card0 (where card1 is my nvidia card), it shows black screen"

note: my nvidia card is card1


What is different in my case is that i CAN run everything through the dGPU.
On Nobara i setup all-ways-egpu which enables using only the dGPU.

Image


I have a second monitor and that one works fine with env = AQ_DRM_DEVICES,/dev/dri/card1:/dev/dri/card0
Actually hyprland feels buttery smooth while using that setting. But the laptop monitor is just black.

NOT using env = AQ_DRM_DEVICES,/dev/dri/card1:/dev/dri/card0 makes hyprland feel choppy and sluggish. Especially for the second monitor.

How to reproduce

Select nvidia card by env = AQ_DRM_DEVICES,/dev/dri/<NVIDIA_CARD> in configuration file.
Launch Hyprland.

Attach not paste

  • I understand that all text files must be attached, and not pasted directly. If not respected, this issue will likely get closed as spam

Checklist of files to include below

  • Hyprland config - hyprctl systeminfo -c (always include)
  • Crash report (always include in case of crash)
  • Video (always include in case of a visual bug)
  • Logs (might contain useful info such as errors)

Additional info & File uploads

Logs: log1.log

config: hyprland_config.txt

Crash logs: Unable to obtain crash log due to computer just freezing when attempting to move the cursor to the laptop screen.

@gridrek gridrek added the bug Something isn't working label Jan 20, 2025
@gridrek
Copy link
Author

gridrek commented Jan 20, 2025

Comment

sirkrypt0:
I can confirm this issue (using nearly identical hardware). Although not recommended, setting AQ_NO_ATOMIC=1 in addition to AQ_DRM_DEVICES=/dev/dri/card1 makes eDP-1 come up properly and I can use Hyprland normally. Note that you'll have to set cursor.no_hardware_cursors = true then to not have an offset cursor.

ottersome:
Can confirm @sirkrypt0 's approach "fixes" the issue.

For me when AQ_NO_ATOMIC=1 is NOT set the laptop monitors backlight is ON.
when AQ_NO_ATOMIC=1 IS set the backlight of the laptops monitor is OFF.
Either way the laptop monitor is still "black"

@vaxerski
Copy link
Member

ok, does sway produce something other than a black screen when forced to do dgpu?

@gridrek
Copy link
Author

gridrek commented Jan 20, 2025

@vaxerski
I don't use sway. and Sway does not permit the use of proprietary nvidia drivers. It states nouveau drivers are needed.
I'm not very well versed when it comes to handling different nvidia drivers to be frank. But would love to find a way to test it if it can help.

@arminius-smh
Copy link

Sway does not permit the use of proprietary nvidia drivers. It states nouveau drivers are needed

you can start sway using proprietary nvidia drivers with sway --unsupported-gpu

@gridrek
Copy link
Author

gridrek commented Jan 21, 2025

Okay so i tried and the results are similar to Hyprland.

with exec env WLR_DRM_DEVICES=/dev/dri/card1:/dev/dri/card0 in the sway config:
Black screen, only second monitor working. Although feels a bit sluggish.

with DRI_PRIME=1 sway --unsupported-gpu:
Sway won't start at all.
Although i can run apps with a DRI_PRIME=1 prefix and they run entirely on the dGPU no problem.

These are the only things i've found to test. Please let me know if there is something i'm missing or something else i should try.

@gulafaran
Copy link
Contributor

Okay so i tried and the results are similar to Hyprland.

with exec env WLR_DRM_DEVICES=/dev/dri/card1:/dev/dri/card0 in the sway config: Black screen, only second monitor working. Although feels a bit sluggish.

with DRI_PRIME=1 sway --unsupported-gpu: Sway won't start at all. Although i can run apps with a DRI_PRIME=1 prefix and they run entirely on the dGPU no problem.

These are the only things i've found to test. Please let me know if there is something i'm missing or something else i should try.

well yeah your laptop monitor is hardwired to the intel gpu so unless you have a mux switch that is changeable in the bios settings, like i do. i dont think this is possible, windows drivers has the capabilites to flip that mux switch on demand but as far as i know linux doesnt.

@gridrek
Copy link
Author

gridrek commented Jan 21, 2025

well yeah your laptop monitor is hardwired to the intel gpu so unless you have a mux switch that is changeable in the bios settings, like i do. i dont think this is possible, windows drivers has the capabilites to flip that mux switch on demand but as far as i know linux doesnt.

Okay that may be the case then. Sad to hear though as i super like Hyprland and would love to use it.

Still makes me wonder how Nobara does it.

@gulafaran
Copy link
Contributor

well yeah your laptop monitor is hardwired to the intel gpu so unless you have a mux switch that is changeable in the bios settings, like i do. i dont think this is possible, windows drivers has the capabilites to flip that mux switch on demand but as far as i know linux doesnt.

Okay that may be the case then. Sad to hear though as i super like Hyprland and would love to use it.

Still makes me wonder how Nobara does it.

why are you trying to force hyprland to run on nvidia? works just fine without that. DRI_PRIME isnt used by nvidia either

@gridrek
Copy link
Author

gridrek commented Jan 21, 2025

why are you trying to force hyprland to run on nvidia? works just fine without that. DRI_PRIME isnt used by nvidia either

Because when using Hyprland on my second monitor, any window movement or any input feels choppy and sluggish.
There also seems to be input latency. And framerate is all over the place.

https://www.youtube.com/watch?v=9UuZfWMM8j4
https://www.youtube.com/watch?v=zKWbyq7M-zU
https://www.youtube.com/watch?v=5gJYIruGSDE

@gulafaran
Copy link
Contributor

why are you trying to force hyprland to run on nvidia? works just fine without that. DRI_PRIME isnt used by nvidia either

Because when using Hyprland on my second monitor, any window movement or any input feels choppy and sluggish. There also seems to be input latency. And framerate is all over the place.

https://www.youtube.com/watch?v=9UuZfWMM8j4 https://www.youtube.com/watch?v=zKWbyq7M-zU https://www.youtube.com/watch?v=5gJYIruGSDE

yeah i suspect there is a bit of driver issues NVIDIA/open-gpu-kernel-modules#767 and NVIDIA/open-gpu-kernel-modules#743 , however the situation isnt entirerly perfect over here either hyprwm/aquamarine#134

@gridrek
Copy link
Author

gridrek commented Jan 21, 2025

why are you trying to force hyprland to run on nvidia? works just fine without that. DRI_PRIME isnt used by nvidia either

Because when using Hyprland on my second monitor, any window movement or any input feels choppy and sluggish. There also seems to be input latency. And framerate is all over the place.
https://www.youtube.com/watch?v=9UuZfWMM8j4 https://www.youtube.com/watch?v=zKWbyq7M-zU https://www.youtube.com/watch?v=5gJYIruGSDE

yeah i suspect there is a bit of driver issues NVIDIA/open-gpu-kernel-modules#767 and NVIDIA/open-gpu-kernel-modules#743 , however the situation isnt entirerly perfect over here either hyprwm/aquamarine#134

NVIDIA/open-gpu-kernel-modules#743 (comment)
Can confirm Setting intel_gpu_frequency=1000 helps a ton.
Dunno if this is a good idea for long sessions though.

@gulafaran
Copy link
Contributor

this can probably be closed btw, if no mux switch, your laptop will remain hardwired to the igpu. so trying to force everything on the nvidia dgpu will surely make it black screened.

@gridrek gridrek closed this as not planned Won't fix, can't repro, duplicate, stale Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants