You are not logged in.

Pages: 1

#1 2023-10-18 15:56:22

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

[SOLVED]Nvidia proprietary drivers not working before starting Wayland

Hi all, thanks for taking the time to try and help.

The issue: the screen goes black right before the login prompt is supposed to appear, and I can't get to the TTY unless I blindly log in, launch a Hyprland session and quit out of it. Then the TTYs work fine.
The drivers are from the "nvidia" package. Tried nvidia-dkms too - same behavior.

Things I've checked so far:
1. The following integrated graphics modules are unloaded: i915, intel_agp, viadb, radeon, amdgpu
2. Nouveau is also blacklisted in /usr/lib/modprobe.d/nvidia-utils.conf
3. Rebuilt initramfs with MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
        --this makes the screen go black earlier in the boot process
4. Tried with and without the nvidia_drm.modeset=1 boot option
        --without the option, hyprland refuses to launch at all (crash log below)

00:00:00.000 [INFO] [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
00:00:00.000 [INFO] [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
00:00:00.006 [INFO] [libseat] [libseat/libseat.c:73] Seat opened with backend 'logind'
00:00:00.006 [INFO] [backend/session/session.c:109] Successfully loaded libseat session
00:00:00.008 [INFO] [backend/backend.c:220] Found 1 GPUs
00:00:00.008 [INFO] [backend/drm/backend.c:202] Initializing DRM backend for /dev/dri/card0 (simpledrm)
00:00:00.008 [INFO] [backend/drm/drm.c:249] Found 1 DRM CRTCs
00:00:00.008 [INFO] [backend/drm/drm.c:207] Found 1 DRM planes
00:00:00.016 [INFO] [render/egl.c:206] Supported EGL client extensions: EGL_EXT_platform_base EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_KHR_platform_x11 EGL_EXT_platform_x11 EGL_EXT_platform_device EGL_MESA_platform_surfaceless EGL_EXT_explicit_device EGL_KHR_platform_wayland EGL_EXT_platform_wayland EGL_KHR_platform_gbm EGL_MESA_platform_gbm EGL_EXT_platform_xcb
00:00:00.018 [ERROR] [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
00:00:00.018 [ERROR] [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
MESA-LOADER: failed to open simpledrm: /usr/lib/dri/simpledrm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
kmsro: driver missing
00:00:00.045 [ERROR] [render/egl.c:320] Software rendering detected, please use the WLR_RENDERER_ALLOW_SOFTWARE environment variable to proceed
00:00:00.045 [ERROR] [render/egl.c:572] Failed to initialize EGL context
00:00:00.045 [ERROR] [render/gles2/renderer.c:804] Could not initialize EGL
terminate called after throwing an instance of 'std::runtime_error'
  what():  wlr_gles2_renderer_create_with_drm_fd() failed!
./hl.sh: line 2:   832 Aborted                 (core dumped) Exec=env QT_QPA_PLATFORMTHEME="qt5ct" LIBVA_DRIVER_NAME=nvidia WLR_NO_HARDWARE_CURSORS=1 Hyprland

dmesg output:

> sudo dmesg | grep -i nvidia
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=ee04c463-4651-453d-89ee-171d0e08f315 rw loglevel=3 nvidia_drm.modeset=1
[    0.039680] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=ee04c463-4651-453d-89ee-171d0e08f315 rw loglevel=3 nvidia_drm.modeset=1
[    3.189292] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input3
[    3.189329] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input4
[    3.189358] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input5
[    3.189387] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input6
[    3.266988] nvidia: loading out-of-tree module taints kernel.
[    3.266998] nvidia: module license 'NVIDIA' taints kernel.
[    3.267002] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    3.267003] nvidia: module license taints kernel.
[    3.660889] nvidia-nvlink: Nvlink Core is being initialized, major device number 237
[    3.662037] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[    3.778704] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  535.113.01  Tue Sep 12 19:41:24 UTC 2023
[    3.851527] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[    4.031423] nvidia-uvm: Loaded the UVM driver, major device number 235.
[    4.186592] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  535.113.01  Tue Sep 12 19:45:42 UTC 2023
[    4.192245] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    4.210418] caller _nv039908rm+0x35/0x70 [nvidia] mapping multiple BARs
[    5.198416] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0

What should I try next? Thanks!

Last edited by cyanbun96 (2023-10-21 16:12:53)

Offline

#2 2023-10-18 19:46:15

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,234

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

The simpledrm device shouldn't get loaded but IIRC it might only be actively unloaded if you use the nvidia-drm.modeset=1 kernel parameter syntax, try that. (note the hyphen as opposed to an underscore)

FWIW while I haven't seen the problem pop up lately, you do not happen to have an integrated GPU not attached to anything that is still active? Disable that in your BIOS/UEFI in case.

Offline

#3 2023-10-18 20:40:40

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

V1del wrote:

nvidia-drm.modeset=1 kernel parameter syntax, try that. (note the hyphen as opposed to an underscore)

Same effect (or lack of thereof) as nvidia_drm with underscore.

V1del wrote:

integrated GPU not attached to anything that is still active? Disable that in your BIOS/UEFI in case.

It was disabled. Willing to try anything I enabled it and noticed that it breaks the TTY when I log out of Hyprland, but doesn't affect the first TTY that I use to log in blindly.

Offline

#4 2023-10-19 01:37:49

i_hate_windows
Banned
Registered: 2023-10-19
Posts: 8

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

try garuda or manjaro and when installing pick proprietary nvidia drivers, or just get an amd gpu lmao

Offline

#5 2023-10-19 07:10:21

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,074

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

The "nvidia_drm.modeset=1 to kill the simplydum"" hack isn't present in all kernels

uname -a

Then please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

And in doubt add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2023-10-19 14:09:05

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

seth wrote:

add "initcall_blacklist=simpledrm_platform_driver_init"

Same behavior.

seth wrote:

uname -a

Linux archlinux 6.5.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 10 Oct 2023 21:10:21 +0000 x86_64 GNU/Linux

seth wrote:

complete system journal for the boot

http://0x0.st/HJQ8.txt

Offline

#7 2023-10-19 14:37:23

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,074

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

Oct 19 16:55:51 archlinux kernel: The simpledrm driver will not be probed
Oct 19 16:55:51 archlinux kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=ee04c463-4651-453d-89ee-171d0e08f315 rw loglevel=3 nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init
Oct 19 16:55:51 archlinux kernel: blacklisting initcall simpledrm_platform_driver_init
Oct 19 16:55:51 archlinux kernel: initcall simpledrm_platform_driver_init blacklisted

Going back to the OP, simeledrm is a red herring in ITT

Tried with and without the nvidia_drm.modeset=1 boot option --without the option, hyprland refuses to launch at all (crash log below)

You could try to add the nvidia modules to the iniramfs, https://wiki.archlinux.org/title/NVIDIA#Early_loading

Then please check/post

for OUT in /sys/class/drm/card0*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

so we know what outputs are attached
You'll need https://aur.archlinux.org/packages/edid-decode-git

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2023-10-19 15:26:47

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

seth wrote:

You could try to add the nvidia modules to the iniramfs, https://wiki.archlinux.org/title/NVIDIA#Early_loading
Then please check/post

for OUT in /sys/class/drm/card0*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

so we know what outputs are attached

The monitor used throughout the boot process says "no signal" when the screen goes black and turns the backlight off, so that might be the issue.

Edid-decode output (was taken after launching Hyprland, but the output during "no signal" phase seems identical, with same checksums. The monitor that's supposed to show TTY is X223W  Q):

/sys/class/drm/card0
/sys/class/drm/card0/edid: No such file or directory
=================
/sys/class/drm/card0-DP-1
edid-decode (hex):

00 ff ff ff ff ff ff 00 10 ac 73 40 4c 35 4a 45
2f 16 01 04 a5 33 1d 78 3b dd 45 a3 55 4f a0 27
12 50 54 a5 4b 00 71 4f 81 80 d1 c0 01 01 01 01
01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
45 00 fe 1f 11 00 00 1e 00 00 00 ff 00 4b 46 38
37 59 32 42 4b 45 4a 35 4c 0a 00 00 00 fc 00 44
45 4c 4c 20 55 32 33 31 32 48 4d 0a 00 00 00 fd
00 38 4c 1e 53 11 00 0a 20 20 20 20 20 20 00 6d

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
    Manufacturer: DEL
    Model: 16499
    Serial Number: 1162491212
    Made in: week 47 of 2012
  Basic Display Parameters & Features:
    Digital display
    Bits per primary color channel: 8
    DisplayPort interface
    Maximum image size: 51 cm x 29 cm
    Gamma: 2.20
    DPMS levels: Off
    Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2
    First detailed timing includes the native pixel format and preferred refresh rate
    Display supports continuous frequencies
  Color Characteristics:
    Red  : 0.6396, 0.3330
    Green: 0.3115, 0.6259
    Blue : 0.1533, 0.0703
    White: 0.3134, 0.3291
  Established Timings I & II:
    IBM     :   720x400    70.081663 Hz   9:5     31.467 kHz     28.320000 MHz
    DMT 0x04:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    DMT 0x06:   640x480    75.000000 Hz   4:3     37.500 kHz     31.500000 MHz
    DMT 0x09:   800x600    60.316541 Hz   4:3     37.879 kHz     40.000000 MHz
    DMT 0x0b:   800x600    75.000000 Hz   4:3     46.875 kHz     49.500000 MHz
    DMT 0x10:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz
    DMT 0x12:  1024x768    75.028582 Hz   4:3     60.023 kHz     78.750000 MHz
    DMT 0x24:  1280x1024   75.024675 Hz   5:4     79.976 kHz    135.000000 MHz
  Standard Timings:
    DMT 0x15:  1152x864    75.000000 Hz   4:3     67.500 kHz    108.000000 MHz
    DMT 0x23:  1280x1024   60.019740 Hz   5:4     63.981 kHz    108.000000 MHz
    DMT 0x52:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
  Detailed Timing Descriptors:
    DTD 1:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz (510 mm x 287 mm)
                 Hfront   88 Hsync  44 Hback  148 Hpol P
                 Vfront    4 Vsync   5 Vback   36 Vpol P
    Display Product Serial Number: 'KF87Y2BKEJ5L'
    Display Product Name: 'DELL U2312HM'
    Display Range Limits:
      Monitor ranges (GTF): 56-76 Hz V, 30-83 kHz H, max dotclock 170 MHz
Checksum: 0x6d
=================
/sys/class/drm/card0-DP-2
EDID of '/sys/class/drm/card0-DP-2/edid' was empty.
=================
/sys/class/drm/card0-DVI-D-1
edid-decode (hex):

00 ff ff ff ff ff ff 00 04 72 0d 00 87 b8 91 81
13 12 01 03 80 2f 1e 78 ea de 95 a3 54 4c 99 26
0f 50 54 bf ef 90 a9 40 71 4f 81 40 01 01 95 00
95 0f 90 40 01 01 21 39 90 30 62 1a 27 40 68 b0
36 00 da 28 11 00 00 19 00 00 00 fd 00 38 4d 1f
54 11 00 0a 20 20 20 20 20 20 00 00 00 ff 00 4c
41 56 30 43 31 33 37 34 30 31 30 0a 00 00 00 fc
00 58 32 32 33 57 20 20 51 0a 20 20 20 20 00 9a

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.3
  Vendor & Product Identification:
    Manufacturer: ACR
    Model: 13
    Serial Number: 2173810823
    Made in: week 19 of 2008
  Basic Display Parameters & Features:
    Digital display
    Maximum image size: 47 cm x 30 cm
    Gamma: 2.20
    DPMS levels: Standby Suspend Off
    RGB color display
    First detailed timing is the preferred timing
  Color Characteristics:
    Red  : 0.6396, 0.3291
    Green: 0.2998, 0.5996
    Blue : 0.1503, 0.0595
    White: 0.3134, 0.3291
  Established Timings I & II:
    IBM     :   720x400    70.081663 Hz   9:5     31.467 kHz     28.320000 MHz
    DMT 0x04:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    Apple   :   640x480    66.666667 Hz   4:3     35.000 kHz     30.240000 MHz
    DMT 0x05:   640x480    72.808802 Hz   4:3     37.861 kHz     31.500000 MHz
    DMT 0x06:   640x480    75.000000 Hz   4:3     37.500 kHz     31.500000 MHz
    DMT 0x08:   800x600    56.250000 Hz   4:3     35.156 kHz     36.000000 MHz
    DMT 0x09:   800x600    60.316541 Hz   4:3     37.879 kHz     40.000000 MHz
    DMT 0x0a:   800x600    72.187572 Hz   4:3     48.077 kHz     50.000000 MHz
    DMT 0x0b:   800x600    75.000000 Hz   4:3     46.875 kHz     49.500000 MHz
    Apple   :   832x624    74.551266 Hz   4:3     49.726 kHz     57.284000 MHz
    DMT 0x10:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz
    DMT 0x11:  1024x768    70.069359 Hz   4:3     56.476 kHz     75.000000 MHz
    DMT 0x12:  1024x768    75.028582 Hz   4:3     60.023 kHz     78.750000 MHz
    DMT 0x24:  1280x1024   75.024675 Hz   5:4     79.976 kHz    135.000000 MHz
    Apple   :  1152x870    75.061550 Hz 192:145   68.681 kHz    100.000000 MHz
  Standard Timings:
    DMT 0x33:  1600x1200   60.000000 Hz   4:3     75.000 kHz    162.000000 MHz
    DMT 0x15:  1152x864    75.000000 Hz   4:3     67.500 kHz    108.000000 MHz
    DMT 0x20:  1280x960    60.000000 Hz   4:3     60.000 kHz    108.000000 MHz
    DMT 0x2f:  1440x900    59.887445 Hz  16:10    55.935 kHz    106.500000 MHz
    DMT 0x30:  1440x900    74.984427 Hz  16:10    70.635 kHz    136.750000 MHz
    DMT 0x2a:  1400x1050   59.978442 Hz   4:3     65.317 kHz    121.750000 MHz
  Detailed Timing Descriptors:
    DTD 1:  1680x1050   59.954250 Hz  16:10    65.290 kHz    146.250000 MHz (474 mm x 296 mm)
                 Hfront  104 Hsync 176 Hback  280 Hpol N
                 Vfront    3 Vsync   6 Vback   30 Vpol N
    Display Range Limits:
      Monitor ranges (GTF): 56-77 Hz V, 31-84 kHz H, max dotclock 170 MHz
    Display Product Serial Number: 'LAV0C1374010'
    Display Product Name: 'X223W  Q'
Checksum: 0x9a
=================
/sys/class/drm/card0-HDMI-A-1
edid-decode (hex):

00 ff ff ff ff ff ff 00 4c 2d d3 03 00 00 00 00
33 11 01 03 80 29 1a 8c 2a e5 b1 a3 55 49 99 83
13 50 54 ad ce 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 66 21 50 b0 51 00 1b 30 40 70
36 00 9a 00 11 00 00 1e 64 19 00 40 41 00 26 30
18 88 36 00 9a 00 11 00 00 18 00 00 00 fd 00 3c
4b 1e 3d 09 00 0a 20 20 20 20 20 20 00 00 00 fc
00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20 01 8b

02 03 1b 71 23 09 07 07 83 01 00 00 67 03 0c 00
20 00 80 2d 43 10 04 03 e2 00 0f 8c 0a d0 8a 20
e0 2d 10 10 3e 96 00 a0 5a 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.3
  Vendor & Product Identification:
    Manufacturer: SAM
    Model: 979
    Made in: week 51 of 2007
  Basic Display Parameters & Features:
    Digital display
    Maximum image size: 41 cm x 26 cm
    Gamma: 2.40
    DPMS levels: Off
    RGB color display
    First detailed timing is the preferred timing
  Color Characteristics:
    Red  : 0.6396, 0.3339
    Green: 0.2861, 0.5986
    Blue : 0.5136, 0.0771
    White: 0.3125, 0.3291
  Established Timings I & II:
    IBM     :   720x400    70.081663 Hz   9:5     31.467 kHz     28.320000 MHz
    DMT 0x04:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    DMT 0x05:   640x480    72.808802 Hz   4:3     37.861 kHz     31.500000 MHz
    DMT 0x06:   640x480    75.000000 Hz   4:3     37.500 kHz     31.500000 MHz
    DMT 0x09:   800x600    60.316541 Hz   4:3     37.879 kHz     40.000000 MHz
    DMT 0x0a:   800x600    72.187572 Hz   4:3     48.077 kHz     50.000000 MHz
    DMT 0x0b:   800x600    75.000000 Hz   4:3     46.875 kHz     49.500000 MHz
    DMT 0x10:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz
    DMT 0x11:  1024x768    70.069359 Hz   4:3     56.476 kHz     75.000000 MHz
    DMT 0x12:  1024x768    75.028582 Hz   4:3     60.023 kHz     78.750000 MHz
  Standard Timings: none
  Detailed Timing Descriptors:
    DTD 1:  1360x768    60.015162 Hz  85:48    47.712 kHz     85.500000 MHz (410 mm x 256 mm)
                 Hfront   64 Hsync 112 Hback  256 Hpol P
                 Vfront    3 Vsync   6 Vback   18 Vpol P
    DTD 2:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz (410 mm x 256 mm)
                 Hfront   24 Hsync 136 Hback  160 Hpol N
                 Vfront    3 Vsync   6 Vback   29 Vpol N
    Display Range Limits:
      Monitor ranges (GTF): 60-75 Hz V, 30-61 kHz H, max dotclock 90 MHz
    Display Product Name: 'SAMSUNG'
  Extension blocks: 1
Checksum: 0x8b

----------------

Block 1, CTA-861 Extension Block:
  Revision: 3
  Basic audio support
  Supports YCbCr 4:4:4
  Supports YCbCr 4:2:2
  Native detailed modes: 1
  Audio Data Block:
    Linear PCM:
      Max channels: 2
      Supported sample rates (kHz): 48 44.1 32
      Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block:
    FL/FR - Front Left/Right
  Vendor-Specific Data Block (HDMI), OUI 00-0C-03:
    Source physical address: 2.0.0.0
    Supports_AI
    Maximum TMDS clock: 225 MHz
  Video Data Block:
    VIC  16:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
    VIC   4:  1280x720    60.000000 Hz  16:9     45.000 kHz     74.250000 MHz
    VIC   3:   720x480    59.940060 Hz  16:9     31.469 kHz     27.000000 MHz
  Video Capability Data Block:
    YCbCr quantization: No Data
    RGB quantization: No Data
    PT scan behavior: No Data
    IT scan behavior: Supports both over- and underscan
    CE scan behavior: Supports both over- and underscan
  Detailed Timing Descriptors:
    DTD 3:   720x480    59.940060 Hz   3:2     31.469 kHz     27.000000 MHz (analog composite, sync-on-green, 160 mm x 90 mm)
                 Hfront   16 Hsync  62 Hback   60 Hpol N
                 Vfront    9 Vsync   6 Vback   30 Vpol N
Checksum: 0x18  Unused space in Extension Block: 82 bytes
=================
/sys/class/drm/card0-HDMI-A-2
EDID of '/sys/class/drm/card0-HDMI-A-2/edid' was empty.
=================

Offline

#9 2023-10-19 15:29:08

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

i_hate_windows wrote:

try garuda or manjaro and when installing pick proprietary nvidia drivers

Tried both - when trying to live boot and choosing the proprietary drivers both hang somewhere in the boot process. No ports are open, so I don't know if anything useful can be pulled out of that. Don't have a spare HDD to do a full install on ATM either.

Offline

#10 2023-10-19 15:51:13

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,074

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

For clarification, there're 3 outputs: DP-1, DVI-D-1 and HDMI-A-1
*None* of them shows anything? Or is it that you want the display on DVI-D-1 b/c the other two ar powerd off or so?

Does the system behave if you detach the other two outputs?

The desired one seems 1680x1050  while the other two are FullHD
What if you add  "video=DVI-D-1:1680x1050@60e" to the kernel parameters?
https://www.kernel.org/doc/Documentation/fb/modedb.rst

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2023-10-19 17:11:18

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

seth wrote:

For clarification, there're 3 outputs: DP-1, DVI-D-1 and HDMI-A-1
*None* of them shows anything? Or is it that you want the display on DVI-D-1 b/c the other two ar powerd off or so?

None of them show anything. No signal, not even a black screen with backlight.

I don't really care which monitor displays a TTY, as long as it's there for logging in without a manager and debugging issues like this.

seth wrote:

What if you add  "video=DVI-D-1:1680x1050@60e" to the kernel parameters?

This doesn't work either

BUT

seth wrote:

Does the system behave if you detach the other two outputs?

Disconnecting the DP-1 fixes the issue. DVI-D-1 gets a TTY output like it should. DP-1 is my main monitor though, so a bigger issue arises.
HDMI-A-1's presence doesn't affect anything. It works fine with it connected.

Offline

#12 2023-10-19 19:37:00

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,074

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

Does "video=DP-1:d" do anything?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2023-10-19 20:34:57

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

seth wrote:

Does "video=DP-1:d" do anything?

Yes, it disables DP-1. In Hyprland too. DVI-D-1 still, somehow, doesn't work with it connected.

Offline

#14 2023-10-19 21:04:51

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,074

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

Do you get any drm/nvidia/nvrm related errors/warnings in the system journal that are not present when detaching the DP-1 output?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#15 2023-10-19 22:42:54

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

seth wrote:

Do you get any drm/nvidia/nvrm related errors/warnings in the system journal that are not present when detaching the DP-1 output?

Nope, no video-related errors of any kind, and the logs are virtually identical.

journalctl -b 0

With DP-1 connected: http://0x0.st/HJjD.txt
With DP-1 disconnected: http://0x0.st/HJjG.txt
(Let me know if there are any more complete log sources)

Offline

#16 2023-10-20 13:58:35

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,074

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

Can you juggle outputs and monitors, ie. eg. attach the monitor that's currently on DP-1 to HDMI-A-1 et vv. to see whether it's the output or the monitor that's acting up?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#17 2023-10-20 18:44:54

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

seth wrote:

Can you juggle outputs and monitors, ie. eg. attach the monitor that's currently on DP-1 to HDMI-A-1 et vv. to see whether it's the output or the monitor that's acting up?

Nope, that's the only monitor that has a DP input.

What I ended up doing is plugging the DP monitor into an HDMI output through a VGA>HDMI converter, bypassing the issue.
That's very suboptimal, and wouldn't help if I had a fourth monitor, but if I'm the only one with this issue I'm willing to call it here.
Unless there are any more suggestions in the next 24 hours I'm proclaiming the DP port cursed and closing the thread.

Offline

#18 2023-10-20 19:49:35

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,074

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

With a fourth monitor you could test whether it's the output or the monitor wink

Is this also an issue w/ nouveau (eg. on the install iso or various live distros)?
If you're using grub and don't care for a framebuffer console, you could also attempt https://wiki.archlinux.org/title/GRUB/T … ramebuffer

The weird part is that this kills all output - I'd get why a hdcp failure might occur during the early boot phase and require a mode change to re-trigger the connection, but that would not affect all outputs.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#19 2023-10-20 21:04:41

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,234

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

FWIW the next (current beta) driver seems to have a bunch of work done for enabling an early boot fbterm driver so chances the problem will get fixed there are here: https://www.nvidia.de/download/driverRe … /213004/de

Offline

#20 2023-10-20 21:42:31

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

seth wrote:

With a fourth monitor you could test whether it's the output or the monitor wink

I've had a fourth monitor for a bit and the issue was still there! It wasn't DP and I didn't juggle them that much, but can't do that now.

seth wrote:

Is this also an issue w/ nouveau (eg. on the install iso or various live distros)?

Nope - booting with nouveau works fine, as does the install ISO.

seth wrote:

If you're using grub and don't care for a framebuffer console, you could also attempt https://wiki.archlinux.org/title/GRUB/T … ramebuffer

Disabling framebuffer works too! Well, "bypasses the issue" if you don't need the framebuffer. Still better than SSHing into the machine, for sure.

Offline

#21 2023-10-20 22:07:19

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

V1del wrote:

FWIW the next (current beta) driver seems to have a bunch of work done for enabling an early boot fbterm driver so chances the problem will get fixed there are here: https://www.nvidia.de/download/driverRe … /213004/de

Attempting to install "nvidia-beta" from AUR pulls on a dependency spaghetti ball, so it'll have to wait until it's in the main branch. I'll try and remember to write an update if anything changes.

Offline

#22 2023-10-21 16:11:58

cyanbun96
Member
Registered: 2023-10-18
Posts: 12

Re: [SOLVED]Nvidia proprietary drivers not working before starting Wayland

Alright, calling it here. For anyone having a similar issue, here's what ended up helping:

Disabling framebuffer https://wiki.archlinux.org/title/GRUB/T … ramebuffer
OR
Not using the DispalyPort output.

The latest drivers (545.23.06 ATM) might also help. (untested)

Thanks everyone for help, and good luck anyone with the same problem!

10/11/23 edit: 545.29.02 drivers, the problem's still there but disabling framebuffer is broken too
and now there's flickering in proton games on wayland but that's apparently known 
thanks nvidia

Last edited by cyanbun96 (2023-11-09 23:04:49)

Offline

Pages: 1

Board footer

Powered by FluxBB