Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

seth · 2025-06-12 13:08:34

tekstryder wrote:

have the same GP107 (1050 Ti) gen card as you and zero issue.

nb.

The OP wrote:

And my secondary display doesn't work in Wayland anymore, however my third display, which is connected via Displayport chaining to the second one works. … SDDM correctly outputs to all 3 displays, X11 as well. It is just when I login to Wayland that it doesnt show any image.

https://bbs.archlinux.org/viewtopic.php … 5#p2245875

my compositor (picom) still has nice transparency blur effects and all, display still 3840x2160 @ 120Hz … But I tried to open minecraft and it is broken. … other games with varying luck … Very hit or miss.

There're multiple regression reports, but they vary in symptoms and probably GPU generation.
I will however say that nvidia officially still supports those devices, so this is simply a bug in the driver that will likely get addressed and not be ignored because the VBIOS is too old.

Edit: the caveat is btw specific to Hopper GPUs (datacenter version of Ada) and doesn't cover Ampere chips at all. Ie. doesn't apply here.

Last edited by seth (2025-06-12 13:13:04)

phpTANKER · 2025-06-12 13:19:10

tekstryder wrote:

seth wrote:
yeah - the 575xx driver has some serious issues.
phpTANKER wrote:
My old 1080 Ti is on VBIOS 86.02.39.00.23 and I don't think I can update it..
You can't. And you don't need nor want to.
Lots of FUD being thrown around in various threads.
I have the same GP107 (1050 Ti) gen card as you and zero issue.
Did you get yours straightened out? I can't even tell from this mangled thread with so many tangents.

Never got it sorted out. I tried:
- Blacklisting nova_core, nouveau (mkinitcpio -P after)
- Adding nouveau modeset=0 to modprobe.d and kernel parameters
- Adding kernel parameters and verified that they were loaded: vidia-drm.modeset=1 nvidia-drm.fbdev=0 + nvidia.NVreg_EnableGpuFirmware=0 as suggested later.
The only thing I didn't try was adding nvidia.NVreg_EnableGpuFirmware=0 to modprode and running mkinitcpio again. I will take a look later tonight.

seth · 2025-06-12 13:34:23

The only thing I didn't try was adding nvidia.NVreg_EnableGpuFirmware=0 to modprode and running mkinitcpio again.

That's a kernel parameter. They all are. They have nothing to do w/ the iniramfs, you pass them at the commandline

Can you switch the monitors around, ie. check whether it's related to the monitor or the used output?

tekstryder · 2025-06-12 13:38:40

Right. I'm following the other threads as well.

Neither GSP (there is none) nor datacenter GPU/drivers are relevant to this thread.

seth wrote:

The OP wrote:
And my secondary display doesn't work in Wayland anymore, however my third display, which is connected via Displayport chaining to the second one works. … SDDM correctly outputs to all 3 displays, X11 as well. It is just when I login to Wayland that it doesnt show any image.

Okay, so nothing has changed from original symptom.

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 5#p2245875

I don't see the correlation. Maybe I'm missing something.

seth wrote:

There're multiple regression reports, but they vary in symptoms and probably GPU generation.

That's fine. They should be reported here as well:

• 575 release feedback & discussion

Tangent: I've been having much success recently in having my issues reported upstream acked by devs/mods, assigned internal tracking numbers, and some fixed and/or worked around.
Most recently this one, which is kind of a biggie, and I'll be updating the relevant Arch GitLab bug with my new information.

I see OP has replied...

Last edited by tekstryder (2025-06-12 13:52:17)

tekstryder · 2025-06-12 13:43:51

phpTANKER wrote:

Never got it sorted out. I tried:
- Blacklisting nova_core, nouveau (mkinitcpio -P after)
- Adding nouveau modeset=0 to modprobe.d and kernel parameters
- Adding kernel parameters and verified that they were loaded: vidia-drm.modeset=1 nvidia-drm.fbdev=0 + nvidia.NVreg_EnableGpuFirmware=0 as suggested later.
The only thing I didn't try was adding nvidia.NVreg_EnableGpuFirmware=0 to modprode and running mkinitcpio again. I will take a look later tonight.

- Get rid of any blacklisting. nvidia-utils handles all of this that's required.
- Purge anything you added nouveau related. Again handled by nvidia-utils.
- GPU firmware is irrelevant to our generation card. Remove that.

Try to isolate each display and check the result. E.g..move one of the working displays into the daisy chain to replace the non-functioning one.

Are the displays all of disparate native resolutions?

EDIT: ninja'd by:

seth wrote:

Can you switch the monitors around, ie. check whether it's related to the monitor or the used output?

Last edited by tekstryder (2025-06-12 13:48:00)

phpTANKER · 2025-06-25 18:36:57

Sorry for the very late responses:

- Get rid of any blacklisting. nvidia-utils handles all of this that's required.
Done

- Purge anything you added nouveau related. Again handled by nvidia-utils.
Done

- GPU firmware is irrelevant to our generation card. Remove that.
Done

Try to isolate each display and check the result. E.g..move one of the working displays into the daisy chain to replace the non-functioning one.
Done, the issue seems to be the 2nd display attached to the daisy chain, no matter which one.

Are the displays all of disparate native resolutions?
Yes, but they are not the same resolutions: (DP-1: 1920x1080 144Hz @ 100% Scale, DP-2-3-CHAIN: 2560x1440 60Hz @ 130% Scale)

Last edited by phpTANKER (2025-06-25 22:45:51)

seth · 2025-06-25 21:39:40

And my secondary display doesn't work in Wayland anymore, however my third display, which is connected via Displayport chaining to the second one works.
…
the issue seems to be the 2nd display attached to the daisy chain, no matter which one.

The 2 chained ones are, but my main one differs (DP-1: 1920x1080 144Hz @ 100% Scale, DP-2-3-CHAIN: 2560x1440 60Hz @ 130% Scale)

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General and

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

You'll need https://archlinux.org/packages/extra/x86_64/v4l-utils/
Also test the behavior of a different WL compositor like weston, sway or hyprland and nb. https://wiki.archlinux.org/title/KDE#Un … lution_set

phpTANKER · 2025-06-27 01:07:31

seth wrote:

And my secondary display doesn't work in Wayland anymore, however my third display, which is connected via Displayport chaining to the second one works.
…
the issue seems to be the 2nd display attached to the daisy chain, no matter which one.
The 2 chained ones are, but my main one differs (DP-1: 1920x1080 144Hz @ 100% Scale, DP-2-3-CHAIN: 2560x1440 60Hz @ 130% Scale)
Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General and
for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
You'll need https://archlinux.org/packages/extra/x86_64/v4l-utils/
Also test the behavior of a different WL compositor like weston, sway or hyprland and nb. https://wiki.archlinux.org/title/KDE#Un … lution_set

Maybe I'm missing something but I'm not sure I have any Xorg logs, both ~/.local/share/xorg and grep -e Log -e tty Xorg.0.log/Xorg.*.log return nothing.

I'll try the for loop once I have the chance to try the drivers again. It's a bit difficult since it's my daily driver desktop.

seth · 2025-06-27 05:15:44

grep -e Log -e tty Xorg.0.log/Xorg.*

is a (useless) example on how to filter random stuff out of that log - and assumes teh log to be in the $PWD

cat /var/log/Xorg.*.log ~/.local/share/xorg/Xorg.*.log

*read* the articles, don't blindly copypaste the blue boxes.

priultimus · 2025-07-18 23:44:37

I don't know if any resolution was found here, but I have seemingly an identical issue. I'm using the GA104M GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] (rev a1). I'm using with the Nvidia driver 575.64.03, Hyprland 0.49.0, Linux version 6.15.6-arch1-1.
This is a full log of my most recent boot with this issue: http://0x0.st/8dV4.txt
These are the two errors I got from that log:

Jul 18 15:00:44 archlinux kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to add connector for NvKmsKapiDisplay 0x00000400
Jul 18 15:00:54 archlinux kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to get dynamic displays

I have never intentionally installed X11 on this machine. So I do not believe I have any logs from xorg.
Here's the output of that for-loop posted a little earlier: http://0x0.st/8dVy.txt
I tried the kernel parameters with and without "nvidia-drm.modeset=1 nvidia-drm.fbdev=0", to no avail.
I have two monitors, the Dell U2725QE and the Dell U2723QE, I've got the U2725QE plugged into the U2723QE via displayport, and I have the U2725QE plugged into my laptop via USB-C to DisplayPort.
What I've observed is that if MST is turned ON in the U2725QE's settings, and the monitor is plugged into my laptop *while* it is booting, it will not function. Even if I unplug and plug it back in. However, if I shut my laptop down, unplug the monitor, turn my laptop back on, wait until I get to the lock screen, and THEN plug it in, both monitors work.
This is a log of my laptop booting without the monitor plugged in: http://0x0.st/8dV3.txt
The highlighted error log is not present in this boot.
Unsure where to go from here, hopefully anyone can give some insight!

seth · 2025-07-19 07:24:26

Jul 18 15:00:32 archlinux kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  575.64.03  Release Build  (root@)  
Jul 18 15:00:32 archlinux systemd-modules-load[196]: Inserted module 'nvidia'
Jul 18 15:00:32 archlinux kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  575.64.03  Release Build  (root@)  
Jul 18 15:00:32 archlinux systemd-modules-load[196]: Inserted module 'nvidia_modeset'
Jul 18 15:00:32 archlinux kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Jul 18 15:00:33 archlinux systemd-modules-load[196]: Inserted module 'nvidia_uvm'
Jul 18 15:00:44 archlinux kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to add connector for NvKmsKapiDisplay 0x00000400
Jul 18 15:00:54 archlinux kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to get dynamic displays
Jul 18 15:00:54 archlinux systemd-modules-load[196]: Inserted module 'nvidia_drm'
Jul 18 15:00:54 archlinux kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 0

Jul 18 15:00:32 archlinux kernel: NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.
Jul 18 15:00:34 archlinux kernel: NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.

1. you're using nvidia-open (tried nvidia instead and disable GSP)
2. remove the nvidia modules from the initramfs
3. you're force providing "drm.edid_firmware=eDP-1:edid/internal_display" which may or not impact the findings wrt external monitor

priultimus · 2025-07-19 15:54:26

seth wrote:

Jul 18 15:00:32 archlinux kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  575.64.03  Release Build  (root@)  
Jul 18 15:00:32 archlinux systemd-modules-load[196]: Inserted module 'nvidia'
Jul 18 15:00:32 archlinux kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  575.64.03  Release Build  (root@)  
Jul 18 15:00:32 archlinux systemd-modules-load[196]: Inserted module 'nvidia_modeset'
Jul 18 15:00:32 archlinux kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Jul 18 15:00:33 archlinux systemd-modules-load[196]: Inserted module 'nvidia_uvm'
Jul 18 15:00:44 archlinux kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to add connector for NvKmsKapiDisplay 0x00000400
Jul 18 15:00:54 archlinux kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to get dynamic displays
Jul 18 15:00:54 archlinux systemd-modules-load[196]: Inserted module 'nvidia_drm'
Jul 18 15:00:54 archlinux kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 0

Jul 18 15:00:32 archlinux kernel: NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.
Jul 18 15:00:34 archlinux kernel: NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.

1. you're using nvidia-open (tried nvidia instead and disable GSP)
2. remove the nvidia modules from the initramfs
3. you're force providing "drm.edid_firmware=eDP-1:edid/internal_display" which may or not impact the findings wrt external monitor

Did all 3 (EDIT: To be clear, I removed the forced EDID from the kernel parameters, as well as removing nvidia modules from initramfs), here's the log of the boot: http://0x0.st/8dxI.txt
Below are the steps I took, just in case I did anything wrong / misunderstood you. I did not know what the GSP was before now, so I'm putting it here in case I made any mistakes. For example, I'm unsure if I needed to switch remove and reinstall any other packages other than the nvidia-open package.
I did this to uninstall the nvidia-open drivers

pacman -R nvidia-open

and then

pacman -S nvidia

to install the proprietary ones. Then I ran

echo "options nvidia NVreg_EnableGpuFirmware=0" | sudo tee -a /etc/modprobe.d/nvidia-gsp.conf

to disable the GSP. I used

❯ nvidia-smi -q | grep GSP
    GSP Firmware Version                  : N/A

to confirm it was disabled.
Nonetheless, the issue remains.

Last edited by priultimus (2025-07-19 15:55:33)

phpTANKER · 2025-07-19 18:30:51

seth wrote:

grep -e Log -e tty Xorg.0.log/Xorg.*
is a (useless) example on how to filter random stuff out of that log - and assumes teh log to be in the $PWD
cat /var/log/Xorg.*.log ~/.local/share/xorg/Xorg.*.log
*read* the articles, don't blindly copypaste the blue boxes.

Xorg log for boot with broken drivers:
https://0x0.st/8dYe.txt

Looks like some conflicts between nvidia, nouveau and other modules but not sure what to make of it.

Tried running the loop both in an interactive shell and bash script but no output. I tried looking inside the folders and it seems quite empty:
less /sys/class/drm/card*/edid <- This shows absolutely nothing

seth · 2025-07-19 19:29:33

@priultimus

Jul 19 11:39:48 arch systemd-coredump[1092]: Process 1045 (Hyprland) of user 964 dumped core.
…
Jul 19 11:39:56 arch systemd[1]: greetd.service: Failed with result 'start-limit-hit'.
Jul 19 11:39:56 arch systemd[1]: Failed to start Greeter daemon.
Jul 19 11:39:58 arch kernel: [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to add connector for NvKmsKapiDisplay 0x00000400

hyprland (and greetd) crash a couple of times before nvidia even shows up.

Jul 19 11:39:42 archlinux kernel: Command line: zswap.enabled=0

Try to add "nvidia_drm.modeset=1" here to block the simpledrm device and see what happens.
Also only boot the multi-user.target (2nd link below) and start Hyprland (or better: some X11 session) manually and avoid all the other OOT modules:
· evdi(OE)
· vmnet(OE)
· vmmon(OE)
· vmw_vmci vboxnetflt(OE)
· vboxnetadp(OE)
· vboxdrv(OE)
· legion_laptop(OE)

(I get that you're probably using those for a reason, but we need to find some stable base to operate from)
Last resort: downgrade to 570xx nvidia-dkms to see whether this is actually related to the 575xx drivers.

Last edited by seth (2025-07-19 19:29:59)

seth · 2025-07-19 19:36:53

@phpTANKER
There's no conflict, the X11 log looks harmless enough
But add "nvidia_drm.modeset=1 nvidia_drm.fbdev=0" to the https://wiki.archlinux.org/title/Kernel_parameters (you've a pascal chip and there's apparently a bug w/ multihead systems that's supposed to be fixed in a later driver)
https://bbs.archlinux.org/viewtopic.php … 6#p2250676

phpTANKER · 2025-07-19 19:40:41

seth wrote:

@phpTANKER
There's no conflict, the X11 log looks harmless enough
But add "nvidia_drm.modeset=1 nvidia_drm.fbdev=0" to the https://wiki.archlinux.org/title/Kernel_parameters (you've a pascal chip and there's apparently a bug w/ multihead systems that's supposed to be fixed in a later driver)
https://bbs.archlinux.org/viewtopic.php … 6#p2250676

Did a quick cat just to make sure:

philip@arch-base ~> sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
philip@arch-base ~> sudo cat /sys/module/nvidia_drm/parameters/fbdev
Y

Although this cat was made with the older drivers installed, but it shouldn't matter right? Just upgrading drivers shouldn't change the kernel params afaik.

Last edited by phpTANKER (2025-07-19 19:50:24)

seth · 2025-07-19 19:47:30

1. you want "fbdev=0" ("N"), not "Y"
2. The important part of the "nvidia_drm.modeset=1" kernel parameter is that it'll also block the simpledrm device (which will be very necessary once you disable fbdev)
Please add those parameters.

phpTANKER · 2025-07-19 19:51:52

seth wrote:

1. you want "fbdev=0" ("N"), not "Y"
2. The important part of the "nvidia_drm.modeset=1" kernel parameter is that it'll also block the simpledrm device (which will be very necessary once you disable fbdev)
Please add those parameters.

On the latest drivers now:

philip@arch-base ~> sudo cat /sys/module/nvidia_drm/parameters/fbdev
N
philip@arch-base ~> sudo cat /sys/module/nvidia_drm/parameters/modeset
Y

Xorg logs if that's of interest: https://0x0.st/8dgL.txt

seth · 2025-07-19 20:06:26

Jul 19 21:51:32 [    34.429] (==) NVIDIA(0): 
Jul 19 21:51:32 [    34.429] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
Jul 19 21:51:32 [    34.429] (==) NVIDIA(0):     will be used as the requested mode.
Jul 19 21:51:32 [    34.429] (==) NVIDIA(0): 
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0): Validated MetaModes:
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0):    
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0):     "DFP-5:nvidia-auto-select,DFP-3.1.8:nvidia-auto-select,DFP-3.8:nvidia-auto-select"
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0): Virtual screen size determined to be 7040 x 1440
Jul 19 21:51:32 [    34.431] (--) NVIDIA(0): DPI set to (92, 91); computed from "UseEdidDpi" X config
Jul 19 21:51:32 [    34.431] (--) NVIDIA(0):     option

looks completely ok and matches 1x1920x1080 + 2x2560x1440
Are the EDIDs still missing??
Did anything change about the wayland situation?

phpTANKER · 2025-07-19 20:48:08

seth wrote:

Jul 19 21:51:32 [    34.429] (==) NVIDIA(0): 
Jul 19 21:51:32 [    34.429] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
Jul 19 21:51:32 [    34.429] (==) NVIDIA(0):     will be used as the requested mode.
Jul 19 21:51:32 [    34.429] (==) NVIDIA(0): 
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0): Validated MetaModes:
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0):    
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0):     "DFP-5:nvidia-auto-select,DFP-3.1.8:nvidia-auto-select,DFP-3.8:nvidia-auto-select"
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0): Virtual screen size determined to be 7040 x 1440
Jul 19 21:51:32 [    34.431] (--) NVIDIA(0): DPI set to (92, 91); computed from "UseEdidDpi" X config
Jul 19 21:51:32 [    34.431] (--) NVIDIA(0):     option

looks completely ok and matches 1x1920x1080 + 2x2560x1440
Are the EDIDs still missing??
Did anything change about the wayland situation?

Yes,
less /sys/class/drm/card*/edid still shows nothing.

I haven't tried another DE yet, I've been a bit worried I might screw up something since it's my daily driver machine.

phpTANKER · 2025-07-19 21:01:27

seth wrote:

Jul 19 21:51:32 [    34.429] (==) NVIDIA(0): 
Jul 19 21:51:32 [    34.429] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
Jul 19 21:51:32 [    34.429] (==) NVIDIA(0):     will be used as the requested mode.
Jul 19 21:51:32 [    34.429] (==) NVIDIA(0): 
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0): Validated MetaModes:
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0):    
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0):     "DFP-5:nvidia-auto-select,DFP-3.1.8:nvidia-auto-select,DFP-3.8:nvidia-auto-select"
Jul 19 21:51:32 [    34.430] (II) NVIDIA(0): Virtual screen size determined to be 7040 x 1440
Jul 19 21:51:32 [    34.431] (--) NVIDIA(0): DPI set to (92, 91); computed from "UseEdidDpi" X config
Jul 19 21:51:32 [    34.431] (--) NVIDIA(0):     option

looks completely ok and matches 1x1920x1080 + 2x2560x1440
Are the EDIDs still missing??
Did anything change about the wayland situation?

Just tried Weston, same issue, here is the Xorg log:
https://0x0.st/8dEV.txt

seth · 2025-07-19 21:54:11

The xorg log is only relevant for X11 sessions, not any wayland compositor.
The whole thing probably hinges on

less /sys/class/drm/card*/edid still shows nothing.

though it ("less") won't ever (save some binary garbage) - did you check edid-decode?
If you're not getting the edids to show up there the closest thing you could do is https://wiki.archlinux.org/title/Kernel … s_and_EDID

xrandr --verbose

on X11 will print the edid's as hexadecimal strings which you can convert w/ hex2bin

phpTANKER · 2025-07-19 22:11:00

seth wrote:

The xorg log is only relevant for X11 sessions, not any wayland compositor.
The whole thing probably hinges on
less /sys/class/drm/card*/edid still shows nothing.
though it ("less") won't ever (save some binary garbage) - did you check edid-decode?
If you're not getting the edids to show up there the closest thing you could do is https://wiki.archlinux.org/title/Kernel … s_and_EDID
xrandr --verbose
on X11 will print the edid's as hexadecimal strings which you can convert w/ hex2bin

I tried read-edid on 570 (with all 3 monitors working correctly):

This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 7
No EDID on bus 8
No EDID on bus 9
No EDID on bus 10
Looks like no busses have an EDID. Sorry!
Attempting to use the classical VBE interface

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
	Function unsupported
	Call failed

	VBE version 0
	VBE string at 0x0 "O"

VBE/DDC service about to be called
	Report DDC capabilities

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
	Function unsupported
	Call failed

Reading next EDID block

VBE/DDC service about to be called
	Read EDID

	Performing real mode VBE call
	Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
	Function unsupported
	Call failed

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged

xrandr --verbose:
https://0x0.st/8d66.txt

seth · 2025-07-19 22:15:56

edid-decode, not read-edid
https://bbs.archlinux.org/viewtopic.php … 5#p2248205
Did you ever actually run that?

Edit:

RANDR Emulation: 1

xrandr on wayland is borderline useless.

Last edited by seth (2025-07-19 22:17:03)

phpTANKER · 2025-07-19 22:25:16

seth wrote:

edid-decode, not read-edid
https://bbs.archlinux.org/viewtopic.php … 5#p2248205
Did you ever actually run that?
Edit:
RANDR Emulation: 1 
xrandr on wayland is borderline useless.

Yes, edid-decode runs with no output and doesn't stop running until i kill the process.

Arch Linux

#26 2025-06-12 13:08:34

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#27 2025-06-12 13:19:10

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#28 2025-06-12 13:34:23

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#29 2025-06-12 13:38:40

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#30 2025-06-12 13:43:51

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#31 2025-06-25 18:36:57

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#32 2025-06-25 21:39:40

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#33 2025-06-27 01:07:31

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#34 2025-06-27 05:15:44

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#35 2025-07-18 23:44:37

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#36 2025-07-19 07:24:26

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#37 2025-07-19 15:54:26

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#38 2025-07-19 18:30:51

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#39 2025-07-19 19:29:33

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#40 2025-07-19 19:36:53

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#41 2025-07-19 19:40:41

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#42 2025-07-19 19:47:30

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#43 2025-07-19 19:51:52

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#44 2025-07-19 20:06:26

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#45 2025-07-19 20:48:08

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#46 2025-07-19 21:01:27

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#47 2025-07-19 21:54:11

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#48 2025-07-19 22:11:00

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#49 2025-07-19 22:15:56

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

#50 2025-07-19 22:25:16

Re: Possible Wayland bug introduced with latest nvidia-dkms-575.57.08

Board footer