NVIDIA / NVIDIA/open-gpu-kernel-modules

Integrated GPU broken from environment variable. X Error of failed request: BadValue (integer parameter out of range for operation)

Open
#678 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
17.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

NVIDIA Open GPU Kernel Modules Version

555.58.02

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
  • I confirm that this does not happen with the proprietary driver package.
Operating System and Version

Arch Linux

Kernel Release

Linux device 6.9.9-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Fri, 12 Jul 2024 00:06:19 +0000 x86_64 GNU/Linux

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
  • I am running on a stable kernel release.
Hardware: GPU

NVIDIA GeForce MX450

Describe the bug

When using the environment variable " __GLX_VENDOR_LIBRARY_NAME=nvidia" that I mentioned in archwiki to force GBM as a backend to use wayland, and launching glxinfo I get the error message:
[user@device ~]$ glxinfo
name of display: :1
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 156 (NV-GLX)
Minor opcode of failed request: 6 ()
Value in failed request: 0x0
Serial number of failed request: 96
Current serial number in output stream: 96
and when launching glxgears, I get:
glxgears
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 156 (NV-GLX)
Minor opcode of failed request: 6 ()
Value in failed request: 0x0
Serial number of failed request: 32
Current serial number in output stream: 32
When I remove this variable the system works fine.

To Reproduce

add this line to /etc/environment:
__GLX_VENDOR_LIBRARY_NAME=nvidia
launch glxinfo or glxgears

Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce with __GLX_VENDOR_LIBRARY_NAME=nvidia in /etc/environment, then compare glxinfo and glxgears behavior with and without the variable. Review the attached nvidia-bug-report.log.gz and the NV-GLX error details; done means both commands work correctly with the variable enabled on the reported setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
computer-graphics, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.