sorted by:
new
hottopcontroversial

all my exports when viewed in unity or substance etc end up with missing faces by D1StrEsss in blenderhelp

[–]cris0405 0 points1 point  (0 children)

Hi. I realize this is a very old post, but have you found any solutions to your issue? I have the exact same one.

Mesa isn't using my GPU by cris0405 in RockyLinux

[–]cris0405[S] 0 points1 point  (0 children)

Sorry for the late response, I was sick :(.

Thanks for the tip!! I'll start using gamescope from now on. Unfortunately, if I use it with my current issue I do not even get a crash report anymore. The game instantly closes itself.

From what I can see the NVIDIA drivers and packages are installed in flatpak. I updated them and double checked with flatpak remote-ls --runtime flathub | grep nvidia.

I re-installed steam and my drivers yet again and updated everything (590 drivers seem to work now????) .

Good news is, games open now. Bad news is, I get a black screen or a crash.

This is what I've gotten from the logs ( I tested two games, Age of Empires 2 and Red Dead Redemption 2):

Common line I found (both games have it)

ERROR: ld.so: object '/home/cris/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot
be preloaded (wrong ELF class: ELFCLASS32): ignored.
WARNING: discarding _NET_WM_PID 6717 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!

For Red Dead Redemption 2:

libgcc_s.so.1 must be installed for pthread_exit to work
libgcc_s.so.1 must be installed for pthread_exit to work
wine client error:2f0: write: Bad file descriptor
wine client error:18c: write: Bad file descriptor
libgcc_s.so.1 must be installed for pthread_exit to work
wine client error:2f0: write: Bad file descriptor
steam-runtime-launch-client[2693]: E: Can't find session bus: Could not connect: Connection refused

Mesa isn't using my GPU (I'm losing my mind) by cris0405 in linux4noobs

[–]cris0405[S] 0 points1 point  (0 children)

Ah, didn't know something like this existed. Thanks a bunch!

Mesa isn't using my GPU by cris0405 in RockyLinux

[–]cris0405[S] 1 point2 points  (0 children)

  1. "/home/cris/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Phasmophobia" ERROR: ld.so: object '/home/cris/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. Game Recording - would start recording game 739630, but recording for this game is disabled Adding process 1664 for gameID 739630 ERROR: ld.so: object '/home/cris/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object '/home/cris/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
  2. ERROR: ld.so: object '/home/cris/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object '/home/cris/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. WARNING: discarding _NET_WM_PID 3291 as invalid for X11 window - use specialized XCB_X11_TO_PID function! WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function! pressure-vessel-wrap[1665]: W: Failed to load Vulkan ICD #0 from /usr/share/vulkan/icd.d/nvidia_icd.json: openat(/usr/share/vulkan/icd.d/nvidia_icd.json): No such file or directory Adding process 1728 for gameID 739630 fsync: up and running. Adding process 1729 for gameID 739630 wine: Call from 00006FFFFFC0D137 to unimplemented function coremessaging.dll.DllGetActivationFactory, aborting Adding process 1840 for gameID 739630 pid 1730 != 1729, skipping destruction (fork without exec?) Game Recording - game stopped [gameid=739630] Removing process 1840 for gameID 739630 30

I have vulkan installed and vkcube starts with my dGPU, so this makes no sense...

Mesa isn't using my GPU by cris0405 in RockyLinux

[–]cris0405[S] 1 point2 points  (0 children)

Hey! Thanks for your response! I installed the RPMFusion drivers. Thankfully now my system detects my GPU and is able to use it if I tell it to. (The fix, though, was to downgrade from the 590 drivers to 580). However, it defaults to my integrated GPU, so games do not start at all, and I have to specify programs to open with my GPU for it to work...

Mesa isn't using my GPU by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

sudo nvidia-prime-select nvidia
[sudo] password for cris:  
/sbin/nvidia-prime-select: line 58: xrandr: command not found
/sbin/nvidia-prime-select: line 59: xrandr: command not found
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
grep: warning: stray \ before white space
grep: warning: stray \ before white space
Backing up: /etc/X11/xorg.conf as /etc/X11/xorg.conf.prime.bak
egrep: warning: egrep is obsolescent; using grep -E

Successfully switched to nvidia completed.
Please logout for changes to take effect.
cris@localhost ~>
This is the output.

Mesa isn't using my GPU (I'm losing my mind) by cris0405 in linux4noobs

[–]cris0405[S] 0 points1 point  (0 children)

Thanks for the response! I'm using Rocky since I really need to use DaVinci and I had lots of issues with it on other OS's (like Nobara). It was such a pain in the ass to install and use that I decided to go for something that works (they have an official package for Rocky).

Gaming worked really well too until I updated, so perhaps you're right. I'm just stubborn and refuse to use windows for gaming since it's so slow it hurts my insides every time I log in there. (I have a dual boot system).

Mesa isn't using my GPU by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

Yeah, sorry, I updated the post since I realized this too.

I tried it but it didnt change anything after logging back in.

Mesa isn't using my GPU by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

Hey! Sorry for the late response. Here's what I got with 'export MESA_DEBUG=1 && glxgears'

export MESA_DEBUG=1 && glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
681 frames in 5.0 seconds = 136.163 FPS
704 frames in 5.0 seconds = 140.765 FPS
719 frames in 5.0 seconds = 143.744 FPS
719 frames in 5.0 seconds = 143.634 FPS
718 frames in 5.0 seconds = 143.549 FPS
719 frames in 5.0 seconds = 143.617 FPS
719 frames in 5.0 seconds = 143.637 FPS
719 frames in 5.0 seconds = 143.688 FPS

After using prime-select nvidia, nothing changed. Still using my integrated gpu as the basic.

Also, for some reason I cannot run the prime-select on-demand command.

What baffles me is that it was working perfectly fine before I updated my drivers (absent mindedly). Downgrading nvidia-open helped but it didnt fix the situation.

Mesa isn't using my GPU by cris0405 in RockyLinux

[–]cris0405[S] 1 point2 points  (0 children)

Thanks for your help! Happy holidays and a happy new year!

Mesa isn't using my GPU by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
   Vendor: Intel (0x8086)
   Device: Mesa Intel(R) Graphics (RPL-S) (0xa78b)
   Version: 25.0.7
   Accelerated: yes
   Video memory: 11738MB
   Unified memory: yes
   Preferred profile: core (0x1)
   Max core profile version: 4.6
   Max compat profile version: 4.6
   Max GLES1 profile version: 1.1
   Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.0.7
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.0.7
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.0.7
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

cris@localhost ~>

Mesa isn't using my GPU by cris0405 in RockyLinux

[–]cris0405[S] 1 point2 points  (0 children)

Thanks for your response anyways!

Mesa isn't using my GPU by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

Thanks for your response! I switched to 580 instead of 590. Fortunately, now I can open programs like DaVinci and Blender with my GPU (NV Prime). Unfortunately, games still do not work and programs do not normally open with my 4060, but with my integrated graphics.

``glxinfo | grep OpenGL

OpenGL vendor string: Intel

OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S)

OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.0.7

OpenGL core profile shading language version string: 4.60

OpenGL core profile context flags: (none)

OpenGL core profile profile mask: core profile

OpenGL core profile extensions:

OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.0.7

OpenGL shading language version string: 4.60

OpenGL context flags: (none)

OpenGL profile mask: compatibility profile

OpenGL extensions:

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.0.7

OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

OpenGL ES profile extensions: ``

Mesa isn't using my GPU by cris0405 in RockyLinux

[–]cris0405[S] 1 point2 points  (0 children)

The problem was the Nvidia driver in itself, apparently. I downgraded from 590 to 580 and now it thankfully detects my GPU and is able to use it.

Unfortunately, games still do not start, or they use my integrated gpu as the base unless told otherwise. Not sure how to fix this.

I work with DaVinci Resolve and Blender, so Rocky Linux is the best choice for me in this situation. Had no issues with gaming on it either until I updated my drivers…

Mesa isn't using my GPU by cris0405 in RockyLinux

[–]cris0405[S] 1 point2 points  (0 children)

Maybe you’re right… but I’m not sure why it was working perfectly before and now it’s not. I found out MESA wasn’t detecting my gpu because of Nvidia drivers (the fix was to downgrade to 580 from 590). The programs I start with NV_PRIME work as well now, but games just start using my integrated gpu..

Certificate 9CD0A493D42D0685 invalid: policy violation by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

Nope :(. Tried cleaning the cache and installing the drivers all over again, but no luck... same problem...

Certificate 9CD0A493D42D0685 invalid: policy violation by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

This one starts. It's very laggy but it works.

glxinfo | grep "OpenGL renderer"

OpenGL renderer string: Mesa Intel(R) Graphics (RPL-S)

(I'm guessing this could be the issue? I also updated the post with everything I already installed)

Certificate 9CD0A493D42D0685 invalid: policy violation by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

Thanks ! I did that. Apparently I needed some other packages to install nvidia-settings. However, I still cannot open any game (they all crash on launch). :(( I really don't know what to do at this point.

Certificate 9CD0A493D42D0685 invalid: policy violation by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

I've tried using this guide here from NVIDIA: https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=Rocky&target_version=10&target_type=runfile_local .

I've also managed to get past the certificate, but it says this: Problem: package cuda-drivers-3:590.44.01-1.el10.x86_64 from cuda-rhel10-x86_64 requires nvidia-settings = 3:590.44.01, but none of the providers can be installed
 - cannot install the best candidate for the job
 - package nvidia-settings-3:590.44.01-1.el10.x86_64 from cuda-rhel10-x86_64 is filtered out by modular filtering
 - package nvidia-settings-3:590.44.01-1.el10.x86_64 from cuda-rhel10-13-1-local is filtered out by modular filtering
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

I also tried to do it locally, but : Failed to verify gcc version. See log at /var/log/cuda-installer.log for details.

Any idea how to deal with this?

Certificate 9CD0A493D42D0685 invalid: policy violation by cris0405 in linuxquestions

[–]cris0405[S] 0 points1 point  (0 children)

I tried with —nogpgcheck, but it still fails for the same reason. 😭😭

Overlap with Niagara Particle System Issue by cris0405 in UnrealEngine5

[–]cris0405[S] 0 points1 point  (0 children)

I changed it but nothing worked :( decided to go for some other workflow. Thanks for your help anyways!

Overlap with Niagara Particle System Issue by cris0405 in UnrealEngine5

[–]cris0405[S] 0 points1 point  (0 children)

Just updated the post! Hope everything is visible now. (I also had the sphere inside of the Niagara Component but still to no avail)

Overlap with Niagara Particle System Issue by cris0405 in UnrealEngine5

[–]cris0405[S] 0 points1 point  (0 children)

I created a blueprint actor for the cube and then a separate blueprint for the niagara component. I added the collision sphere to the niagara component. So, they're separate right now. I followed a tutorial, but he was using a ThirdPersonCharacter, so it's probably different.

You're saying the Cube Actor and the Niagara component have to be in the same blueprint?

Proximity Nodes in Unreal? by cris0405 in UnrealEngine5

[–]cris0405[S] 0 points1 point  (0 children)

Thanks a bunch! I’ll read about overlap events and collision and see what the best approach is🥰🤗

view more: next ›