Github messages for voidlinux
 help / color / mirror / Atom feed
From: Dko1905 <Dko1905@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] nvidia-470.74_1: BadAlloc & black box
Date: Mon, 11 Oct 2021 17:39:07 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33482@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]

New issue by Dko1905 on void-packages repository

https://github.com/void-linux/void-packages/issues/33482

Description:
### System

* xuname:  
  `Void 5.10.71_1 x86_64 GenuineIntel uptodate hold rrmFFFFFFFFFF`
* package:  
  `nvidia-470.74_1`

I am using bspwm on a laptop, and I run `glxgears` using PRIME Render Offload.
I do **not** have `xf86-video-intel` installed, but instead use modesetting.
I have one xorg config file `/etc/X11/xorg.conf.d/20-intel-graphics.conf`:
```conf
Section "Device"
	Identifier "modesetting"
	Driver "modesetting"
	Option "TearFree" "True"
EndSection
```

### Expected behavior
I expect `glxgears` to successfully start up and work all the time.

### Actual behavior
Three different things happen, either `glxgears` starts up successfully and runs successfully, `glxgears` starts up successfully but does not render anything or `glxgears` fails to allocate proper resources.
Here is a video demonstrating the three outputs:
[video of glxgears](https://files.catbox.moe/3fnc2b.mp4)
It is random what happens, but black windows are more common than it working or it failing.

### Steps to reproduce the behavior
1. Install (at this time) latest `nvidia` drivers together with `xorg-minial`, `xorg-apps`, `xorg-fonts` and `xorg-util-macros`.
2. Run `glxgears` using `prime-run` in xorg session.

Other application are also affected, when I start Steam using `prime-run`, I get a see through window, when I start it on the Intel video card, it works as expected.

This is a new issue, since I haven't had it before I upgraded and switched to modesetting. I've tried to downgrade nvidia and go back to `xf86-video-intel`, but it didn't fix the issue.

             reply	other threads:[~2021-10-11 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 15:39 Dko1905 [this message]
2022-05-17 14:14 ` Dko1905
2022-05-17 14:14 ` [ISSUE] [CLOSED] " Dko1905

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33482@inbox.vuxu.org \
    --to=dko1905@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).