[NVIDIA] 555 Driver Status #1320
Comments
|
This is worse than driver 550. Gamescope crashes before it even has a chance at initializing. |
|
Mine experience is not the great c5@bh*zx@2!54kKF#&y8also when trying to run steam big picture mode from tty gamescope-session repo: https://github.com/MrDuartePT/deckifier/tree/kde gamescope command: gamescope logs: ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment.
DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.
vulkan: selecting physical device 'NVIDIA GeForce RTX 3070 Laptop GPU': queue family 2 (general queue family 0)
vulkan: physical device supports DRM format modifiers
wlserver: [backend/headless/backend.c:67] Creating headless backend
wlserver: [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
wlserver: [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
wlserver: [libseat] [libseat/libseat.c:73] Seat opened with backend 'logind'
wlserver: [backend/session/session.c:108] Successfully loaded libseat session
drm: opening DRM node '/dev/dri/card0'
drm: Connector eDP-1 -> AUO -
drm: [colorimetry]: EDID with colorimetry detected. Using it
drm: [colorimetry]: r 0.639648 0.330078
drm: [colorimetry]: g 0.299805 0.599609
drm: [colorimetry]: b 0.150391 0.059570
drm: [colorimetry]: w 0.313477 0.329102
drm: Connector eDP-1 -> AUO -
drm: [colorimetry]: EDID with colorimetry detected. Using it
drm: [colorimetry]: r 0.639648 0.330078
drm: [colorimetry]: g 0.299805 0.599609
drm: [colorimetry]: b 0.150391 0.059570
drm: [colorimetry]: w 0.313477 0.329102
drm: Connectors:
drm: eDP-1 (connected)
drm: HDMI-A-1 (disconnected)
drm: DP-2 (disconnected)
drm: DP-1 (disconnected)
drm: selecting connector eDP-1
drm: selecting mode 1920x1080@165Hz
vulkan: vkGetPhysicalDeviceFormatProperties2 returned zero modifiers for DRM format 0x38344241 (VkResult: 0)
vulkan: vkGetPhysicalDeviceFormatProperties2 returned zero modifiers for DRM format 0x38344258 (VkResult: 0)
vulkan: supported DRM formats for sampling usage:
vulkan: AR24 (0x34325241)
vulkan: XR24 (0x34325258)
vulkan: AB24 (0x34324241)
vulkan: XB24 (0x34324258)
vulkan: RG16 (0x36314752)
vulkan: NV12 (0x3231564E)
vulkan: AB4H (0x48344241)
vulkan: XB4H (0x48344258)
vulkan: AB30 (0x30334241)
vulkan: XB30 (0x30334258)
wlserver: Using explicit sync when available
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:17] Starting headless backend
wlserver: [backend/libinput/backend.c:88] Starting libinput backend
wlserver: [backend/libinput/events.c:69] Adding Power Button [0:1]
wlserver: [backend/libinput/events.c:69] Adding Video Bus [0:6]
wlserver: [backend/libinput/events.c:69] Adding Video Bus [0:6]
wlserver: [backend/libinput/events.c:69] Adding Power Button [0:1]
wlserver: [backend/libinput/events.c:69] Adding Lid Switch [0:5]
wlserver: [backend/libinput/events.c:69] Adding Razer Razer Kraken Tournament Edition Consumer Control [5426:1312]
wlserver: [backend/libinput/events.c:69] Adding Razer Razer Kraken Tournament Edition [5426:1312]
wlserver: [backend/libinput/events.c:69] Adding Razer Razer Basilisk [5426:100]
wlserver: [backend/libinput/events.c:69] Adding Razer Razer Basilisk Keyboard [5426:100]
wlserver: [backend/libinput/events.c:69] Adding Razer Razer Basilisk [5426:100]
wlserver: [backend/libinput/events.c:69] Adding ITE Tech. Inc. ITE Device(8910) Keyboard [1165:49409]
wlserver: [backend/libinput/events.c:69] Adding ITE Tech. Inc. ITE Device(8910) Wireless Radio Control [1165:49409]
wlserver: [backend/libinput/events.c:69] Adding Ideapad extra buttons [0:0]
wlserver: [backend/libinput/events.c:69] Adding ELAN06FA:00 04F3:31DD Mouse [1267:12765]
wlserver: [backend/libinput/events.c:69] Adding ELAN06FA:00 04F3:31DD Touchpad [1267:12765]
wlserver: [backend/libinput/events.c:69] Adding AT Translated Set 2 keyboard [1:1]
wlserver: [backend/libinput/backend.c:127] libinput successfully initialized
wlserver: Successfully initialized libei for input emulation!
wlserver: [util/env.c:9] Loading WLR_NO_HARDWARE_CURSORS option: 1
wlserver: [types/output/output.c:370] WLR_NO_HARDWARE_CURSORS set, forcing software cursors
wlserver: [util/env.c:9] Loading WLR_NO_HARDWARE_CURSORS option: 1
wlserver: [types/output/output.c:370] WLR_NO_HARDWARE_CURSORS set, forcing software cursors
wlserver: [xwayland/server.c:107] Starting Xwayland on :0
wlserver: [xwayland/server.c:107] Starting Xwayland on :1
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x55efd6719130 (res 0x55efd6a52e10)
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x55efd671da20 (res 0x55efd6a4b550)
wlserver: [xwayland/server.c:272] Xserver is ready
wlserver: [xwayland/server.c:272] Xserver is ready
pipewire: stream state changed: connecting
pipewire: stream state changed: paused
pipewire: stream available on node ID: 83
xwm: Embedded, no cursor set. Using left_ptr by default.
xwm: Embedded, no cursor set. Using left_ptr by default.
vblank: Using timerfd.
wlserver: Updating mode for xwayland server #0: 1920x1080@165
pipewire: renegotiating stream params (size: 1920x1080)
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x55efd6685940 (res 0x55efd69934e0)
xwm: Rejecting WM_CHANGE_STATE to ICONIC for window 0x400007
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x55efd6684980 (res 0x55efd6a05280)
xwm: got the same buffer committed twice, ignoring.
drmModeAtomicCommit: Operation not permitted
xwm: We failed our modeset and have no mode to fall back to! (Initial modeset failed?): Operation not permitted
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported maximum keycode 708, clipping.
> X11 cannot support keycodes above 255.
> Warning: Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning: Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported maximum keycode 708, clipping.
> X11 cannot support keycodes above 255.
> Warning: Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning: Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
(EE) failed to read Wayland events: Broken pipe
(EE) failed to write to Xwayland fd: Broken pipeEdit: Nested seems to work fine |
|
Using gamescope nested mode in KDE plasma 6.0.4 with Kwin 6.0.4.1 patched with explict sync support works fine. logs: user@Gentoo ~ $ gamescope -- mangohud vkcube
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.
vulkan: selecting physical device 'NVIDIA GeForce RTX 3070 Laptop GPU': queue family 2 (general queue family 0)
vulkan: physical device supports DRM format modifiers
wlserver: [backend/headless/backend.c:67] Creating headless backend
xdg_backend: Seat name:
vulkan: vkGetPhysicalDeviceFormatProperties2 returned zero modifiers for DRM format 0x38344241 (VkResult: 0)
vulkan: vkGetPhysicalDeviceFormatProperties2 returned zero modifiers for DRM format 0x38344258 (VkResult: 0)
vulkan: supported DRM formats for sampling usage:
vulkan: AR24 (0x34325241)
vulkan: XR24 (0x34325258)
vulkan: AB24 (0x34324241)
vulkan: XB24 (0x34324258)
vulkan: RG16 (0x36314752)
vulkan: NV12 (0x3231564E)
vulkan: AB4H (0x48344241)
vulkan: XB4H (0x48344258)
vulkan: AB30 (0x30334241)
vulkan: XB30 (0x30334258)
vulkan: AR30 (0x30335241)
vulkan: XR30 (0x30335258)
wlserver: Running compositor on wayland display 'gamescope-0'
wlserver: [backend/headless/backend.c:17] Starting headless backend
wlserver: Successfully initialized libei for input emulation!
wlserver: [util/env.c:9] Loading WLR_NO_HARDWARE_CURSORS option: 1
wlserver: [types/output/output.c:370] WLR_NO_HARDWARE_CURSORS set, forcing software cursors
wlserver: [xwayland/server.c:107] Starting Xwayland on :1
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x55cb548b4860 (res 0x55cb55088ea0)
wlserver: [xwayland/server.c:272] Xserver is ready
pipewire: stream state changed: connecting
pipewire: stream state changed: paused
pipewire: stream available on node ID: 95
xwm: Embedded, no cursor set. Using left_ptr by default.
vblank: Using timerfd.
xdg_backend: PreferredMetadata: Red: 0.64 0.33, Green: 0.3 0.6, Blue: 0.15 0.06, White: 0.3127 0.329, Max Luminance: 100 nits, Min Luminance: 0 nits, Max Full Frame Luminance: 100 nits
josh edid: Patching res 800x1280 -> 1280x720
pipewire: renegotiating stream params (size: 1280x720)
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
ATTENTION: default value of option vk_khr_present_wait overridden by environment.
DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau.
[2024-05-21 18:31:22.950] [MANGOHUD] [error] [overlay_params.cpp:1003] Failed to read presets file: '/home/mrduarte/.config/MangoHud/presets.conf'
Selected GPU 0: NVIDIA GeForce RTX 3070 Laptop GPU, type: DiscreteGpu
[Gamescope WSI] Creating Gamescope surface: xid: 0x400000
[Gamescope WSI] Atom of T was wrong type. Expected XCB_ATOM_CARDINAL.
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x55cb5505fc90 (res 0x55cb5508fa50)
[Gamescope WSI] Made gamescope surface for xid: 0x400000
[Gamescope WSI] Surface state:
steam app id: 0
window xid: 0x400000
wayland surface res id: 5
layer client flags: 0x0
server hdr output enabled: false
hdr formats exposed to client: false
[Gamescope WSI] Forcing on VK_EXT_swapchain_maintenance1.
wlserver: [types/wlr_compositor.c:771] New wlr_surface 0x55cb5505d150 (res 0x55cb55090470)
xwm: got the same buffer committed twice, ignoring.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported maximum keycode 708, clipping.
> X11 cannot support keycodes above 255.
> Warning: Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning: Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
xdg_backend: Changed refresh to: 165.010hz
[Gamescope WSI] Creating swapchain for xid: 0x400000 - minImageCount: 3 - format: VK_FORMAT_B8G8R8A8_UNORM - colorspace: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR - flip: true
[Gamescope WSI] Created swapchain for xid: 0x400000 - imageCount: 3
[Gamescope WSI] Swapchain recieved new refresh cycle: 6.06ms |
|
Plasma 6.0.4-1 with kwin patched with explicit sync support, from the |
|
|
Sounds like NVIDIA/open-gpu-kernel-modules#622 |
If nvidia provides a PR for the fix I might try patch kernel-open on my machine to see if solve it. But seems to be that the problem |
|
Sorry that we missed this in our testing prior to release. We checked internally to see why, and our testing team was using a gamescope build from before this use of explicit sync in DRM-KMS was added, so we didn't notice the issue. This is indeed due to NVIDIA/open-gpu-kernel-modules#622, which is not fixed in the 555 series drivers. The fix for that issue will arrive in the 560 series. In the meantime, I've pushed this work-around: #1330 Give it a try and let us know if you run into any other issues. Note this shouldn't actually result in any negative side effects on NVIDIA proprietary drivers, and it should be a no-op on other drivers. Gamescope only uses explicit sync to disable implicit sync. It already manually waits for rendering to complete before presenting its buffers, and the NVIDIA driver doesn't support implicit synchronization of DRM-KMS presentation, so there's nothing to disable. |
|
#1330 makes it work now but with accelerated web views on this happens |
|
another issue when this menu is open the mouse vanishes |
Outdated See comment: #1320 (comment) |
@MrDuartePT distro? built fine for me with my usual .spec on Fedora |
|
I on gentoo using the gentoo ebuild I updated libliftoff to the latest commit and now I getting this error on wlroots. Strange is that 3.14.17 install just fine Files of libliftoff: * Searching for libliftoff ...
* Contents of dev-libs/libliftoff-9999:
/usr
/usr/include
/usr/include/libliftoff.h
/usr/lib64
/usr/lib64/libliftoff.so -> libliftoff.so.0
/usr/lib64/libliftoff.so.0 -> libliftoff.so.0.5.0
/usr/lib64/libliftoff.so.0.5.0
/usr/lib64/pkgconfig
/usr/lib64/pkgconfig/libliftoff.pc
/usr/share
/usr/share/doc
/usr/share/doc/libliftoff-9999
/usr/share/doc/libliftoff-9999/README.md.bz2 |
|
I'm not sure how Gentoo does their build but I'd recommend forcing fallback for |
|
Even after fallblack I get the same error, full build log, I was expecting to get this error since the libliftoff version was the same: Note the txt is just to fool github, think the ebuild as sh file Edit: get to compile directaly from source I need to give a look at vkroots, maybe is outdaded and giving this problem |
|
@cubanismo @Joshua-Ashton can confirm it work from tty: And the tearing is also solve on nvidia Sorry for all the problems why compiling gonna solve the issue on gentoo For people are interesting on how I get the deck ui working is the deckfier repo on my GitHub |
You're right, I'm stupid. Gamescope seems to work fine after downloading vkcube. |
|
@ryzendew, I experienced the same problem with the menu on previous versions of the driver. |
Found the problem is when I build wlroots with You have any ideia why @Joshua-Ashton, at least dosent seem to be needed for gamescope to work in tty/drm mode |
|
Has anyone been running into the same issue as me? I run Fedora and I have not been able to get steam embedded to work for more than 15 seconds. Steam seems to crash whenever it finishes loading and tries to enter the Home Screen. I filed an issue report here: ValveSoftware/steam-for-linux#10916 but I'm pretty lost how people have gotten Gamescope-session to work on their NVIDIA cards while I haven't. |
|
@matte-schwartz, Check out my repository. I hope he helps you: https://github.com/Algorithm0/GamescopeSession Next, run the video card selection setting for your session: After this setting, log out. Next, click the gear in the lower left corner (if you are using a gnome), select a Steam session and log in as usual. |
Can try run my script directly from tty: https://github.com/MrDuartePT/deckifier/blob/kde/rootfs/usr/share/gamescope-session/gamescope-session-script If this what I use to run steam big picture on tty |
|
thanks for the advice everyone, already tried all of that unfortunately. I've got gamescope-session on several rigs (AMD) that work perfectly so I tried to follow the same process. i can even trigger a crash of steam with |
|
Strange because on my machine is working fine as you can see here: https://github.com/ValveSoftware/gamescope/assets/68701049/396911c4-e359-4805-976b-629a2ccad53f |
|
From what I can tell it's my Steam client causing issues and not Gamescope... very confusing. |
Closed
5 tasks
|
I've been testing this for the past couple days now, particularly embedded gamescope, and for the most part things seem to be working now compared to 545 and earlier. The main issues I still notice particularly with Steam and Gamescope are:
IMG_1433.movthis same strobing is also present on my 4070 laptop with an internal HDR display, so it does not seem exclusive to external connections. the strobing seems to stop temporarily whenever gamescope stops compositing, like when my cursor was not moving and the menu was static at the very end of the clip. |
|
It disappear if you open a game? |
|
No, happens in-game for me too along with swapchain errors: gamescope-session.log has a lot of |
gentoo-bot
pushed a commit
to gentoo/gentoo
that referenced
this issue
Jun 2, 2024
* in the latest version also wlroots subproject fails to compile using drm backend to my testing gamescope on tty seems to work without it also gamescope meson dosen't seem to use it * see: https://github.com/ValveSoftware/gamescope/blob/420eb91387a484fd7b1ea71449091f0480d9e538/src/meson.build#L31C86-L31C94 * see: ValveSoftware/gamescope#1320 (comment) Signed-off-by: Gonçalo Negrier Duarte <[email protected]> Signed-off-by: James Le Cuirot <[email protected]>
IN_FENCE_FD support won't affect Gamescope's usage, as of the latest gamescope code. It's very, very unlikely Vulkan explicit sync will affect anything you're running in gamescope either, unless you're using a native Linux Vulkan app with direct Wayland support or you've forced WINE to use its very early Wayland backend. Sync issues for Gamescope purposes should all be resolved in 555 baring bugs. |
Well I notice the cs2 crash Steam big picture after open when gamescope is run from tty, since is a Vulkan Linux native game might have some improvement with the protocol (if valve decides to enable Wayland support, for now the cs2.sh force SDL to use X11 if I not wrong, can be edited but might trigger VAC and disable online), let see if get solve after 555 stable. Thanks for correcting me tho. |
I got a chance to test them and did not see any discernible sync behavior changes between 550 with gamescope master and 555, with all the config variations. I'm guessing all my issues are stemming from Steam under Wayland with gamescope integration at this point, not gamescope. So I think
is correct, assuming gamescope drm is compositing a well-behaving application, which Steam with gamescope integration (-steampal, etc) does not appear to be under NVIDIA. I do not experience any of the crashing that OP mentions. *All tested on proprietary modules, not the OpenGPU ones. I don't believe Pascal is supported with their open modules. |
The only think I notice is low refresh rate (stuck between 15-25fps) in the steam big picture ui itself, but besides that inside games everthink work fine (besides the cs2 crash), but I on the OpenGPU driver. |
Interesting, thanks for the additional context here. I've found that right now, if I run nested gamescope (i.e. from my Plasma 6 desktop) with However, if I attempt to use I plan on filing this in the NVIDIA dev forum's 555.42.02 feedback thread just in case anyone is running into similar issues specifically with embedded gamescope/HDR. Edit: actually, if i force 720p in the display resolution settings of gamescope-session/embedded gamescope, HDR works without flickering. I wonder if maybe HDR metadata is "larger" or different than through kwin? not too sure yet. |
|
I am facing an issue, It crashes my Desktop. I am using KDE 6.1 beta. also tried running with |
|
Those errors from the DRM driver shouldn't be fatal. Do you have any info on the actual failure/crash? |
|
I was able to get the output stored into file, so it crashes i still have the log Gamescope log of crashing desktop: and journactl log Edited: |
The problem you describe is very close to mine, it seems to me - but in general, all this ends in the fall of the gamescope. |
|
I've made progress on my HDR issue. It appears that anything above 2560x1440p@120hz causes the intense flickering I noted in previous clips I posted. It happens across both my ultrawide monitor with DisplayPort and also my HDMI 2.1 port to my 4K TV. Artifacting happens over that resolution/refresh rate for both ports. At 2560x1440@120hz or less HDR is perfect in Gamescope-session. Should also be noted I'm able to go above that resolution on nested Gamescope in Plasma 6 |
|
That's interesting. I'm not a monitor/display expert myself, but I wonder if that is at the limit of some threshhold in bandwidth where things go from single-channel->mutli-channel, switch to some decimated YUV mode, etc. |
|
Hmm, I wish I knew more about this stuff! I've been trying to sift through gamescope code to see if I could find any differentiation between using Plasma 6's HDR with nested gamescope vs using gamescope-session's HDR colorspace and haven't turned anything useful up yet. I'll probably post about this on the Nvidia dev forums as well to see if anyone is experiencing similar issues. |
I'm experiencing the same situation. Using gamescope-git, KDE Plasma 6.1 Beta + 555.42. It freezes and crashes immediately after starting it.
This error makes my journalctl logs almost 400MB |
|
I have a 4K120 display connected through a mini DP to HDMI converter (thank you HDMI forum for blocking 2.1): gamescope -W 3840 -H 2160 -r 120 -f -e -- steam -bigpicture # screen corruption
gamescope -W 2560 -H 1440 -r 120 -f -e -- steam -bigpicture # works but not ideal
gamescope -W 3840 -H 2160 -r 120 --hdr-enabled -f -e -- env DXVK_HDR=1 steam -bigpicture # crash
gamescope -W 1920 -H 1080 -r 120 --hdr-enabled -f -e -- env DXVK_HDR=1 steam -bigpicture # crash
gamescope --hdr-enabled -f -e -- env DXVK_HDR=1 steam -bigpicture # works but it's 60 HZ |
|
Works fine on Arch/Hyprland with 555 for me on a 3090. |
|
Giving my two cents on this: On my system under Wayland with driver 555 gamescope will always work properly in any situation. On X11 sometimes the underlying nested Wayland system will crash with no error. It's consistent, but it's per-game. |
|
I have same problem as well with GTX 1050Ti Launch command Logs |
|
I'm having issues with Hunt: Showdown crashing gamescope after a while. It starts properly, but then crashes at some point. Sometimes it's in the menu, sometimes after half an our of play. Trying to get HDR to work properly, but it seems that even the minimal configuration without any HDR crashes, if I use the following command: It's not the easiest to reproduce. glxgears and vkcube just seem to work. Forza Horizon 4 also does not seem to have any issues. Maybe this is something more game specific. Log: |
|
Still having crashing issues under the latest 565 drivers on Fedora KDE 41. It seems to be random &or varying depending on whether I make use of my actual HDR screen, or if I launch it on my SDR screen (still running HDR internally) |
|
Happens under 565 too. Log: |
|
I am running currently 565.77 and there is no way to get a gamescope window up. i tried with nvidia patches. With disabled HDR , with disabled kwin layers so basically everything. ENABLE_HDR_WSI=0 gamescope -F fsr -W 1360 -H 1020 -- vkcube >>./gamescope_log.txt 2>&1 550.40.80 with disabled HDR works ( latest vulkan dev ) |
I'm not really sure what NVIDIA patches you're referring to here. Either way, I checked on my 4090 and using gamescope's upscaling + Gamescope WSI while on NVIDIA with a Wayland desktop compositor results in a Vulkan semaphore error:
gamescope generates a coredump when this happens:You can work around the issue in a couple different ways:
I wasn't able to reproduce this on my AMD 7900XTX rig at all. |
6 tasks
|
@matte-schwartz thank you for the environment variable , you saved my life :) not the perfect solution but the most easy one |
|
Thanks @matte-schwartz, I followed up in that issue. Some meta-thoughts: This bug appears to have become a dumping ground of Gamescope+NVIDIA problems. All the recent comments are feedback on 565-series drivers, not 555. Most of the feedback here is great, and I love seeing all the genuine attempts to crowd-source solutions/workarounds/etc. and characterize things. However, mega-bugs inevitably lose traction with those of us trying to fix things over time, because it gets too hard to follow the various sub-conversations and separate issues involved, so I'll share some advice: You'll get our attention better with issues such as #1662 that:
I understand everyone is busy and has better things to do, and that it's no one else's job to help us fix our bugs. Us NVIDIAns continue to do our best to read through all the github, forum, etc. traffic, but we're not infinite. We have to allocate our time carefully too, and the above advice can only improve your odds of a response and follow-up. Keep up the broad discussions on communal issues like this while you're working out what is and isn't a related issue, but please also continue to break out separate issues when you've found a common thread and pulled on it a little. We'll try to help guide that process and respond as best we can. |
|
Fully agreed on all points, mega-issues make it very difficult to track multiple bugs and differentiate them from each other on my end as well. Moving forward, I'll continue splitting off separate issues where appropriate for the sake of tracking and clarity. I'm going to clean up the issue report form to give instructions for attaching nvidia-bug-report.log.gz archives when reporting issues on Nvidia GPUs as well. @cubanismo, while we're on this topic, I've been brainstorming some ways of organizing issue reports in this repo better, especially driver-related bug reports. Would having a Also open to any other suggestions that you have that would help make tracking easier on your side. I can't make any promises, but I'll do my best to work on ideas you would find helpful. |
|
Yes, an NVIDIA label would help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Status: Fully broken
Observed Behavior: Crashes instantly
Expected behavior: launch
Log messages:
The text was updated successfully, but these errors were encountered: