555 release feedback & discussion

I am becoming more and more convinced of the uselessness of this forum and Nvidia’s “wonderful” attitude towards its clients. The problem remained the same. Vulkan did not work and does not work in Flatpak under a Wayland session.

fixed for me using these options:
options nvidia NVreg_EnableS0ixPowerManagement=1
options nvidia NVreg_S0ixPowerManagementVideoMemoryThreshold=1024

in 555.54.xx

Hi,
my Debian testing since yesterday after an update is totally inusable. I get a black screen with the arrow of my mouse.

I use kernel 6.9.10 and drivers 555.42.06 from cuda repo.

This is the log from sddm:

00:00:00.040 [ERROR] [EGL] command: eglQueryDmaBufModifiersEXT, error: EGL_BAD_PARAMETER (0x300c), message: "EGL_BAD_PARAMETER error: In eglQueryDmaBufModifiersEXT: Invalid format
"
00:00:00.040 [ERROR] [render/egl.c:856] Failed to query dmabuf number of modifiers
00:00:00.040 [ERROR] [EGL] command: eglQueryDmaBufModifiersEXT, error: EGL_BAD_PARAMETER (0x300c), message: "EGL_BAD_PARAMETER error: In eglQueryDmaBufModifiersEXT: Invalid format
"
00:00:00.040 [ERROR] [render/egl.c:856] Failed to query dmabuf number of modifiers
00:00:00.128 [ERROR] [xwayland/sockets.c:63] Failed to bind socket @/tmp/.X11-unix/X0: Indirizzo già in uso
00:00:00.413 [ERROR] [../src/action.c:474] Invalid action: lxqt-leave --logout
isPrimaryInstance
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
(EE) 
(EE) Backtrace:
(EE) 0: Xwayland (0x55f200844000+0x188552) [0x55f2009cc552]
(EE) 1: Xwayland (0x55f200844000+0x18c08d) [0x55f2009d008d]
(EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5fdb229000+0x3f590) [0x7f5fdb268590]
(EE) 3: /lib/x86_64-linux-gnu/libnvidia-tls.so.555.42.06 (0x7f5fdaa56000+0x34c0) [0x7f5fdaa594c0]
(EE) 
(EE) Segmentation fault at address 0x7f5fdaa594c0
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
00:05:48.544 [ERROR] [../src/xwayland.c:1028] Failed to create xcb connection
(EE) could not connect to wayland server

and dmesg:

[ 251.417089] sddm-greeter[1483]: segfault at 7fbef34714c0 ip 00007fbef34714c0 sp 00007ffd33364098 error 15 in libnvidia-tls.so.555.42.06[7fbef3471000+1000] likely on CPU 11 (core 5, socket 0)

It is the first time i get a such critical bug like this.
Regards

My Second Monitor that is attached to a DVI Port is not getting any signal hence showing a black screen. My audio does not work either. here is my inxi -Fzxx output in my terminal:

System:
Kernel: 6.9.9-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.41-37.fc40
Desktop: GNOME v: 46.3.1 tk: GTK v: 3.24.43 wm: gnome-shell dm: 1: GDM
2: SDDM note: stopped Distro: Fedora Linux 40 (Workstation Edition)
Machine:
Type: Desktop Mobo: Micro-Star model: B450-A PRO MAX (MS-7B86) v: 4.0
serial: UEFI: American Megatrends LLC. v: M.D0
date: 05/17/2021
CPU:
Info: 12-core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen 2
rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB
Speed (MHz): avg: 2200 high: 2201 min/max: 2200/4672 boost: enabled cores:
1: 2200 2: 2200 3: 2200 4: 2200 5: 2200 6: 2201 7: 2200 8: 2200 9: 2200
10: 2200 11: 2200 12: 2200 13: 2200 14: 2200 15: 2200 16: 2200 17: 2200
18: 2200 19: 2200 20: 2200 21: 2200 22: 2199 23: 2200 24: 2200
bogomips: 182398
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] driver: nvidia v: 555.58.02
arch: Turing pcie: speed: 2.5 GT/s lanes: 16 ports: active: none
off: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 26:00.0 chip-ID: 10de:1f06
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 24.1.1
compositor: gnome-shell driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled
model: Lenovo LEN D27-20B res: 1920x1080 dpi: 82 diag: 686mm (27")
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2060
SUPER/PCIe/SSE2
API: Vulkan v: 1.3.283 surfaces: xcb,xlib device: 0 type: discrete-gpu
driver: N/A device-ID: 10de:1f06 device: 1 type: cpu driver: N/A
device-ID: 10005:0000
Audio:
Device-1: NVIDIA TU106 High Definition Audio driver: snd_hda_intel v: kernel
pcie: speed: 8 GT/s lanes: 16 bus-ID: 26:00.1 chip-ID: 10de:10f9
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 28:00.4 chip-ID: 1022:1487
Device-3: C-Media Blue Snowball driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-9:4 chip-ID: 0d8c:0005
API: ALSA v: k6.9.9-200.fc40.x86_64 status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168
IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac:
Drives:
Local Storage: total: 931.51 GiB used: 373.16 GiB (40.1%)
ID-1: /dev/nvme0n1 vendor: Kingston model: SA2000M81000G size: 931.51 GiB
speed: 31.6 Gb/s lanes: 4 serial: temp: 35.9 C
Partition:
ID-1: / size: 929.91 GiB used: 372.83 GiB (40.1%) fs: btrfs dev: /dev/dm-0
mapped: luks-699f94b8-5c7b-4629-b809-e4c36e94d587
ID-2: /boot size: 973.4 MiB used: 323.6 MiB (33.2%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 19 MiB (3.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 929.91 GiB used: 372.83 GiB (40.1%) fs: btrfs
dev: /dev/dm-0 mapped: luks-699f94b8-5c7b-4629-b809-e4c36e94d587
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 47.4 C mobo: N/A gpu: nvidia temp: 53 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 6.51 GiB (20.8%)
Processes: 593 Power: uptime: 20h 3m wakeups: 1 Init: systemd v: 255
target: graphical (5) default: graphical
Packages: pm: flatpak pkgs: 51 Compilers: gcc: 14.1.1 Shell: Bash
v: 5.2.26 running-in: gnome-terminal inxi: 3.3.34

I am having the same issues with a kernel panic on resume from suspend on 555.58.02 on a Quadro M1000.

We have submitted a bug report regarding the H100 GPU issue with the 555 driver.
FWIW: We have encountered the same issue with the 550 driver version.

Is there any plan to fix these small stutters in Wayland regardless of using GNOME or KDE? I have noticed that this happens in both version 550.xx and 555.xx. I use nvidia_drm.modeset=1 along with NVreg_EnableGpuFirmware=0 and I notice that even so there are small stutters in the interface.

My GPU is a RTX A2000 6GB with a i7 8700, 24GB DDR4 2666 and a KC3000 1TB. This happens on Fedora, OpenSUSE, Arch, Ubuntu…

EDIT: Firefox become a trash using Nvidia + Wayland. Stuck on 60fps instead 180Hz of my monitor, scroll with stutters so much etc.

1 Like

560 should pretty much solve this.
I would suggest you to use the open kernel module and patch Patches for testing r555 stutter issues by mtijanic · Pull Request #658 · NVIDIA/open-gpu-kernel-modules · GitHub on top of it.

Also, these stutters seems to be mainly also introduced, when nvidia-smi gets all the time called.
Programs, like coolercontrol and Plasma Monitor so far doing this.

See: [MAJOR] KDE Plasma Wayland & X11 poor performance & frame drops when opening apps · Issue #538 · NVIDIA/open-gpu-kernel-modules · GitHub

1 Like

The variable MUTTER_DEBUG_FORCE_KMS_MODE=simple improves the stuttering situation a bit.
I also noticed that running the xwayland process makes the stuttering worse.

1 Like

Did Nvidia test this release? DVI output seems completely broken on my 3050. Why have they not released a fix?

Nope. People reported multiple issues specific to this release on this thread and they just ignored everything. Nevermind the thousands of other threads with zero replies or ones with unresolved issues. You want to use your RTX GPU to play games with Ray Tracing? Too bad, enjoy XID 109 errors.

1 Like

You want to use your Nvidia GPU? Stay on Windows and get the work done. On Linux? Forget.

1 Like

I would love to…

too bad it doesnt look like the 1070 / 1080 cards will be supported with the open drivers :(

NVIDIA… DO YOU HAVE ANY PLANS TO SUPPORT THE 1070 / 1080 CARDS?? THEY AREN’T THAT OLD AND THEY STILL HANDLE WHAT I’M DOING!

PLEASE CONSIDER ADDING 1070 TO SUPPORT WITH THE OPEN DRIVERS!!

IF YOU WONT RELEASE THE OPEN DRIVERS FOR THE “NOT TOO OLD” 1070 / 1080 CARDS… I WILL ASSUME YOU ARE TAKING ADVANTAGE AND TRYING TO GET PEOPLE TO BUY NEW CARDS!

I WILL THEN JUST GET A RADEON INSTEAD OF NVIDIA … WHICH IF I UNDERSTAND, IS BETTER SUPPORTED UNDER LINUX ANYWAYS!

THANK YOU!

I’ve noticed that after the latest 555.58.02 update, every time I wake up my computer from suspend, I don’t see the login screen. I use a GTX card over HDMI. Is this a known issue? Should I do a full-report?

I have this issue too if i leave the GPU enabled, so yes it seems like a common issue, but its not related to this problem, at least for me it would like cool-down and return to login eventually.

Better report it elsewhere more proper or create one new thread.

Note, with VRR enabled, the system is unable to go idle idle Power states and maintains a minimum of 80W, if I disable adaptive sync or enable a second monitor (disabling adaptive sync or gsync) then usage drops to 20W idle. This is on wayland with river hyperland and sway. Issue is not as present in KDE because of the automatic mode (always on mode exhibits the same behavior), however unsure if it is a driver issue or wayland issue.

I can also repro this issue on the 560 beta drivers. Although not to as large an extent. With VRR enabled my rtx 3070 idles at 34W whereas with it disables it drops down to 11W. @amrits , are you able to repro this issue?

I am also still seeing the higher power draw with vrr enabled on the new 560 beta release (560.31.02)

Tbf, VRR does draw more power, that’s why it’s only enabled for fullscreen applications in KDE by default.

I can confirm this both on nvidia 555 and 560 (560.35.03). The same issuse when pressing play in the unreal editor. It runs for a few seconds then crashes.

1 Like