Closed gungun974 closed 2 months ago
why are you launching hyprland on an existing wayland session? launch it from the tty
I'm sorry @vaxerski, I made some error in my Hyprland configuration when I was initially testing.
First I didn't see logs were not the same between a pure tty and an already running wayland session. Second I'm stupid and I didn't see I got some bunch of stupid override in my Hyprland configuration for Nvidia on an Amd computer :eyes:
But Hyprland is still not running but I got the feeling from the stacktrace it's like an issue more with Mesa than Aquamarine now. But I'm not sure since I can get sway
running.
So here the logs from Hyprland and also my Hyprland config files that I scrap everything out I can :
--------------------------------------------
Hyprland Crash Report
--------------------------------------------
Well this is awkward.
Hyprland received signal 11(SEGV)
Version: 155d44016d0cb11332c454db73d59030cdbd7b13
Tag:
Date: 2024-09-10
Flags:
System info:
System name: Linux
Node name: GungunZen
Release: 6.11.0-rc6
Version: #1-NixOS SMP PREEMPT_DYNAMIC Tue Jan 1 00:00:00 UTC 1980
GPU:
os-release:
ANSI_COLOR="1;34"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="24.11.20240728.52ec9ac"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
IMAGE_ID=""
IMAGE_VERSION=""
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 24.11 (Vicuna)"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="24.11 (Vicuna)"
VERSION_CODENAME=vicuna
VERSION_ID="24.11"
Backtrace:
# | /home/gungun974/.nix-profile/bin/Hyprland(_Z12getBacktracev+0x46) [0x767a06]
getBacktrace()
??:?
#1 | /home/gungun974/.nix-profile/bin/Hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0x854) [0x6bfea4]
CrashReporter::createAndSaveCrash(int)
??:?
#2 | /home/gungun974/.nix-profile/bin/Hyprland(_Z25handleUnrecoverableSignali+0x5f) [0x625e7f]
handleUnrecoverableSignal(int)
??:?
#3 | /nix/store/wlffq5p6mxxgfap10sav3ij936jzqm59-glibc-2.39-52/lib/libc.so.6(+0x405c0) [0x7f6541f355c0]
??
??:0
#4 | /nix/store/wlffq5p6mxxgfap10sav3ij936jzqm59-glibc-2.39-52/lib/libc.so.6(+0x17995c) [0x7f654206e95c]
??
??:0
#5 | /nix/store/wlffq5p6mxxgfap10sav3ij936jzqm59-glibc-2.39-52/lib/libc.so.6(__strdup+0x12) [0x7f6541f9cd32]
??
??:0
#6 | /nix/store/9ivppw10bkh9bhizccmaw7z0bv3cx0jz-mesa-24.1.4-drivers/lib/libEGL_mesa.so.0(+0x2bcea) [0x7f6535845cea]
??
??:0
#7 | /nix/store/9ivppw10bkh9bhizccmaw7z0bv3cx0jz-mesa-24.1.4-drivers/lib/libEGL_mesa.so.0(+0x25f88) [0x7f653583ff88]
??
??:0
#8 | /nix/store/9ivppw10bkh9bhizccmaw7z0bv3cx0jz-mesa-24.1.4-drivers/lib/libEGL_mesa.so.0(+0x14740) [0x7f653582e740]
??
??:0
#9 | /nix/store/6n7mjzp32m0srz21s5n82cgly7pg1h00-aquamarine-0.3.3+date=2024-09-01_f8a687d/lib/libaquamarine.so.2(_ZN10Aquamarine12CDRMRenderer7attemptEN9Hyprutils6Memory14CSharedPointerINS_13CGBMAllocatorEEENS3_INS_8CBackendEEE+0x611) [0x7f6542f06b11]
??
??:0
#1 | /nix/store/6n7mjzp32m0srz21s5n82cgly7pg1h00-aquamarine-0.3.3+date=2024-09-01_f8a687d/lib/libaquamarine.so.2(_ZN10Aquamarine11CDRMBackend7onReadyEv+0x7b2) [0x7f6542eee282]
??
??:0
#11 | /nix/store/6n7mjzp32m0srz21s5n82cgly7pg1h00-aquamarine-0.3.3+date=2024-09-01_f8a687d/lib/libaquamarine.so.2(_ZN10Aquamarine8CBackend5startEv+0x676) [0x7f6542eb6916]
??
??:0
#12 | /home/gungun974/.nix-profile/bin/Hyprland(_ZN11CCompositor10initServerENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi+0x2c1) [0x641a51]
CCompositor::initServer(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int)
??:?
#13 | /home/gungun974/.nix-profile/bin/Hyprland(main+0xcd2) [0x5e3e92]
main
??:?
#14 | /nix/store/wlffq5p6mxxgfap10sav3ij936jzqm59-glibc-2.39-52/lib/libc.so.6(+0x2a14e) [0x7f6541f1f14e]
??
??:0
#15 | /nix/store/wlffq5p6mxxgfap10sav3ij936jzqm59-glibc-2.39-52/lib/libc.so.6(__libc_start_main+0x89) [0x7f6541f1f209]
??
??:0
#16 | /home/gungun974/.nix-profile/bin/Hyprland(_start+0x25) [0x625b15]
_start
??:?
Log tail:
[LOG] [AQ] drm: Skipping connector eDP-1, has crtc 79 and is connected
[LOG] [AQ] drm: connector HDMI-A-1, has crtc -1, will be rechecked
[LOG] [AQ] drm: connector DP-1, has crtc -1, will be rechecked
[LOG] [AQ] drm: connector DP-2, has crtc -1, will be rechecked
[LOG] [AQ] drm: connector DP-3, has crtc -1, will be rechecked
[LOG] [AQ] drm: connector DP-4, has crtc -1, will be rechecked
[LOG] [AQ] drm: connector DP-5, has crtc -1, will be rechecked
[LOG] [AQ] drm: connector DP-6, has crtc -1, will be rechecked
[LOG] [AQ] drm: connector DP-7, has crtc -1, will be rechecked
[LOG] [AQ] drm: slot 0 crtc 79 taken by eDP-1, skipping
[LOG] [AQ] drm: slot 1 crtc 83 unassigned
[LOG] [AQ] drm: slot 2 crtc 87 unassigned
[LOG] [AQ] drm: slot 3 crtc 91 unassigned
[LOG] [AQ] drm: Connector HDMI-A-1 is not connected
[LOG] [AQ] drm: Connector DP-1 is not connected
[LOG] [AQ] drm: Connector DP-2 is not connected
[LOG] [AQ] drm: Connector DP-3 is not connected
[LOG] [AQ] drm: Connector DP-4 is not connected
[LOG] [AQ] drm: Connector DP-5 is not connected
[LOG] [AQ] drm: Connector DP-6 is not connected
[LOG] [AQ] drm: Connector DP-7 is not connected
[LOG] [AQ] drm: rescanning after realloc
[LOG] [AQ] drm: Scanning connectors for /dev/dri/card1
[LOG] [AQ] drm: Scanning connector id 93
[LOG] [AQ] drm: Connector id 93 already initialized
[LOG] [AQ] drm: Connector 93 connection state: 1
[LOG] [AQ] drm: Connector eDP-1 connected
[LOG] [AQ] drm: Connecting connector eDP-1, CRTC ID 79
[LOG] [AQ] drm: Dumping detected modes:
[LOG] [AQ] drm: Mode 0: 2880x1800@120.00Hz (preferred)
[LOG] [AQ] drm: Mode 1: 2880x1800@60.00Hz (preferred)
[LOG] [AQ] drm: Mode 2: 1920x1200@120.00Hz
[LOG] [AQ] drm: Mode 3: 1920x1080@120.00Hz
[LOG] [AQ] drm: Mode 4: 1600x1200@120.00Hz
[LOG] [AQ] drm: Mode 5: 1680x1050@120.00Hz
[LOG] [AQ] drm: Mode 6: 1280x1024@120.00Hz
[LOG] [AQ] drm: Mode 7: 1440x900@120.00Hz
[LOG] [AQ] drm: Mode 8: 1280x800@120.00Hz
[LOG] [AQ] drm: Mode 9: 1280x720@120.00Hz
[LOG] [AQ] drm: Mode 10: 1024x768@120.00Hz
[LOG] [AQ] drm: Mode 11: 800x600@120.00Hz
[LOG] [AQ] drm: Mode 12: 640x480@120.00Hz
[LOG] [AQ] drm: Physical size [Vector2D: x: 340, y: 220] (mm)
[LOG] [AQ] drm: Description Samsung Display Corp. ATNA60CL10-0 (eDP-1)
[LOG] [AQ] drm: connector eDP-1 crtc is capable of vrr: props.vrr_capable -> 96, crtc->props.vrr_enabled -> 24
[LOG] [AQ] drm: Explicit sync supported
[LOG] [AQ] drm: Scanning connector id 101
[LOG] [AQ] drm: Connector id 101 already initialized
[LOG] [AQ] drm: Connector 101 connection state: 2
[LOG] [AQ] drm: Scanning connector id 107
[LOG] [AQ] drm: Connector id 107 already initialized
[LOG] [AQ] drm: Connector 107 connection state: 2
[LOG] [AQ] drm: Scanning connector id 113
[LOG] [AQ] drm: Connector id 113 already initialized
[LOG] [AQ] drm: Connector 113 connection state: 2
[LOG] [AQ] drm: Scanning connector id 118
[LOG] [AQ] drm: Connector id 118 already initialized
[LOG] [AQ] drm: Connector 118 connection state: 2
[LOG] [AQ] drm: Scanning connector id 123
[LOG] [AQ] drm: Connector id 123 already initialized
[LOG] [AQ] drm: Connector 123 connection state: 2
[LOG] [AQ] drm: Scanning connector id 128
[LOG] [AQ] drm: Connector id 128 already initialized
[LOG] [AQ] drm: Connector 128 connection state: 2
[LOG] [AQ] drm: Scanning connector id 133
[LOG] [AQ] drm: Connector id 133 already initialized
[LOG] [AQ] drm: Connector 133 connection state: 2
[LOG] [AQ] drm: Scanning connector id 138
[LOG] [AQ] drm: Connector id 138 already initialized
[LOG] [AQ] drm: Connector 138 connection state: 2
[LOG] [AQ] drm: gpu /dev/dri/card1 becomes primary drm
[LOG] [AQ] Starting the Aquamarine backend!
[LOG] [AQ] Starting the Wayland backend!
[ERR] [AQ] Wayland backend cannot start: wl_display_connect failed (is a wayland compositor running?)
[ERR] [AQ] Requested backend (wayland) could not start, enabling fallbacks
[ERR] [AQ] Implementation wayland failed, erasing.
[LOG] [AQ] Created a GBM allocator with drm fd 27
[LOG] [AQ] drm: Connectors size2 9
[LOG] [AQ] Created a GBM allocator with drm fd 131
exec-once = /nix/store/j8l2v22xypah1srykhwjlkgwwgdxnnpw-dbus-1.14.10/bin/dbus-update-activation-environment --systemd DISPLAY HYPRLAND_INSTANCE_SIGNATURE WAYLAND_DISPLAY XDG_CURRENT_DESKTOP && systemctl --user stop hyprland-session.target && systemctl --user start hyprland-session.target
env = debug:disable_logs = false
I update my computer Mesa version and now it's works...
Sorry to have disturbed you
Hello, sorry to bother you with a very recent product, but today I received the Asus Zenbook S16 laptop equipped with the brand new AMD AI 370, and since this morning I’ve been configuring my NixOS environment, which I typically use with Hyprland.
However, Hyprland is not able to start on this laptop, even though the GPU works very well under Gnome.
I'm not an expert in how it all works, but from the logs I've been able to read, it seems like Aquamarine can't determine what the GPU is on my laptop?
I tried forcing it with
AQ_DRM_DEVICES
/dev/dri/card1
, but even with this, I still encounter the same problem.I understand that my issue is specifically related to my hardware and will not be easy to reproduce, but if you need any information to help understand the cause, feel free to ask.
In the meantime, here are some commands and logs that I have already gathered:
Here the logs of Hyprland :
Here
lspci -k
:Note: My GPU is at PCIe
c4:00.0
and calledDisplay controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 150e (rev c1)
It's the first time for me to see a GPU without the words "VGA" in its name.ls -lha /dev/dri
cat /sys/class/drm/*/status
:ls -lha /sys/bus/pci/devices/0000:00:08.3/
:Note: On my system, nobody can't read
/sys/bus/pci/devices/0000:00:08.3/label
. Even root.uname -a
:Note: I used an testing kernel since I got some issue on the lastest for sleep crash.
My kernel boot options :
dmseg
: