| View previous topic :: View next topic |
| Author |
Message |
satanail
n00b
Joined: 18 Feb 2018
Posts: 21
|
 Posted: Sun Feb 18, 2018 10:45 pm Post subject: Intel, Nvidia Xserver, GLSL, Wine-Staging and a game |
 |
|
Hello fellow gentoo users, I just registered here! First I'd like you to excuse me for my english skills and I'll try to be as clear as possible. I never felt the need to enter a forum or anything, cause I could always find a solution on my own, but now I'm really lost... I really hope someone can help me out... So thread's name is like that cause I'm not 100% sure what to blame, but I'm close to 99% want to hear your opinion about this.
So I'm using nvidia-xrun to open up a xserver, running with nvidia. It's a multilib setup and I've setup the libraries like this:
/etc/X11/xinit/nvidia-xinitrc: | Code: | export LD_LIBRARY_PATH=/usr/lib64/opengl/nvidia/extensions:/usr/lib64/opengl/nvidia/lib:/usr/lib32/opengl/nvidia/lib:/usr/lib:$ LD_LIBRARY_PATH}
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
|
~/.nvidia-xinitrc
/etc/X11/nvidia-xorg.conf
| Code: |
Section "Files"
ModulePath "/usr/lib64/opengl/nvidia/lib"
ModulePath "/usr/lib/opengl/nvidia/lib"
ModulePath "/usr/lib64/opengl/nvidia/extensions"
ModulePath "/usr/lib64/xorg/modules/drivers"
ModulePath "/usr/lib64/xorg/modules"
EndSection
Section "ServerLayout"
Identifier "layout"
Screen 1 "nvidia"
Inactive "intel"
EndSection
Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:1:0:0"
Option "NoLogo" "true"
Option "UseEDID" "true"
Option "UseEDIDFreqs" "false"
Option "SyncToVBlank" "0"
Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x2222; PowerMizerDefaultAC=0x1"
Option "Coolbits" "31"
Option "Interactive" "0"
EndSection
Section "Screen"
Identifier "nvidia"
Device "nvidia"
# Option "AllowEmptyInitialConfiguration" "Yes"
# Option "UseDisplayDevice" "none"
EndSection
Section "Device"
Identifier "intel"
Driver "modesetting"
Option "AccelMethod" "none"
EndSection
Section "Screen"
Identifier "intel"
Device "intel"
EndSection
|
It opens fine, eselecting opengl to nvidia works and glxinfo is outputting the correct data, but when I enter a game in League, I get a massive fpsdrop, everything is setup-ed the same way as always, with the exception that I switched gcc from 6.4.0 to 7.3.0, glibc2.25, kernel 4.15.2-gentoo. I get only the following errors:
| Code: | fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
ALSA lib /var/tmp/portage/media-libs/alsa-lib-1.1.2/work/alsa-lib-1.1.2/src/seq/seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work.
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
Please configure the application to use double buffering (1 back buffer) if possible.
fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #3:
fixme:d3d_shader:print_glsl_info_log Vertex info
fixme:d3d_shader:print_glsl_info_log -----------
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[0].zw" might be used before being
initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[1]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[2]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[3]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[4]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[5]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[6]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[7]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[9]" might be used before being initialized
fixme:d3d_shader:print_glsl_info_log 0(19) : warning C7050: "vs_out[11]" might be used before being initialized
|
I get these shaders errors like 600 times, you'd probably say they are negligible, cause after the first frame they will get reinitialized anyway, but when I wasn't getting these errors, my fps was pretty stable, between 120~180, now since I started getting these(plus the backbuffer error) I am playing with 30-60fps, which is super annoying, considering that I know what my notebook is capable of :/
Wine-staging 2.21 from the main repo. Tried every version, so far.
What is strange for me is when I'm in Intel's Xserver, and I run primusrun wine <game> I don't get these issues and my fps is at stable 80-100! Primusrun is always worse than a standalone nvidia xserver, thats why it isn't 200. Running under Intel LIBGL_DEBUG=verbose primusrun glxgears gives out:
| Code: |
libGL: Can't open configuration file /home/mofo/.drirc: No such file or directory.
libGL: pci id for fd 7: 8086:191b, driver i965
libGL: OpenDriver: trying /usr/lib64/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/i965_dri.so
libGL: Can't open configuration file /home/mofo/.drirc: No such file or directory.
libGL: Can't open configuration file /home/mofo/.drirc: No such file or directory.
libGL: Using DRI3 for screen 0
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 950M/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 390.25
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 390.25
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
|
It apparently uses i965 as the glx driver, not nvidia, that's why I dont have issues, so It must be something with my nvidia setup, right? But why then when I run in an nvidia xserver LIBGL_DEBUG=verbose glxinfo I don't get any debug info, but just the correct output? I tried piping it to >dev/null to see if the debug info is lost somewhere inbetween the big glxinfo output, but there's nothing in there.
I tried running LIBGL_DEBUG=verbose primusrun glxinfo under the nvidia session and I get:
| Code: |
name of display: :1
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so
libGL: Can't open configuration file /home/mofo/.drirc: No such file or directory.
libGL: Can't open configuration file /home/mofo/.drirc: No such file or directory.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Segmentation fault
|
But I guess primus uses different libGL driver, so it's not related to my nvidia driver or I'm mistaken?
Its libGL.so.1 is in /usr/lib64/primus/ Maybe glxgears is only 32bit and primusrun's libgl is 64bit only? I don't care about primusrun, as I'll only use it in Intel's X and its working as expected there, but I find it interesting tho and that is why I decided to just mention it.
I don't have any errors in dmesg, everything is beautiful there. I tried downgrading to lower kernel version and 387 drivers, because I've read there's some performance degradation with 390, but it was the same stuff, unfortunately. What haven't I setuped right? Can it be becaulse of that "use more than 1 backbuffer" error? How can I setup wine to use more than 1 to atleast test how it will be afterwards? |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gamers & Players
