maldata wrote:
And now everything seems to look fine. This might be due to my old GPU with legacy nvidia drivers.
The games
minimum system requirements,
on Windows, are:
A. Minimum Requirements:
Processor: AMD Athlon 64 X2 Dual Core 5600+ or Equivalent
Graphics Card: GeForce GTX 8800 or Equivalent
RAM: 2 GB
Operating System: Windows 7
from:
MTG Arena FAQ.
Looking at:
Nvidia: Current graphics driver releases ...
You seem to be running a very out-of-date driver.
Surely you should be using at least Nvidia driver version:
304.137 ?!
That driver version supports way, way back to a
GeForce 6 card.
Are you really running such an old card?
I consider my Desktop machines
Nvidia Geforce 8800 GTX card to be completely obsolete - which is why that machine is currently in bits...
If that is the newest driver your card can run (i.e. it's a
Geforce 6 or
Geforce 7 series card), then it has truly had the Nvidia life support turned off...
So you'd probably be better off using the
nouveau driver.
Btw this also looks funky in your
app-emulation/wine-staging-3.17 build log:
Code: Select all
/sbin/ldconfig: /usr/lib64/libcuda.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib64/libnvidia-cfg.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib64/libvdpau.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib64/libvdpau_trace.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib64/libXvMCNVIDIA.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib64/libvdpau_nvidia.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib64/libnvidia-tls.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib32/libcuda.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib32/libvdpau_trace.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib32/libvdpau_nvidia.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib32/libnvidia-tls.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib64/tls/libnvidia-tls.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib64/tls/libnvidia-tls.so.1 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib32/tls/libnvidia-tls.so.185.18.14 is not an ELF file - it has the wrong magic bytes at the start.
/sbin/ldconfig: /usr/lib32/tls/libnvidia-tls.so.1 is not an ELF file - it has the wrong magic bytes at the start.
For everyone's sanity (especially mine!)...
It's nicer to pipe your Gentoo build logs through a ANSI colour code stripper, e.g.:
Code: Select all
gunzip -c app-emulation:wine-staging-3.17:20180930-141309.log.gz | perl -pe 's/\x1b\[[0-9;]*[mGKH]//g'
before posting them online. Otherwise the log file will be spammed by colour code sequences (well actually the printable parts of them).
I've got that perl command aliased in my shell:
Code: Select all
alias strip-ansi="perl -pe 's/\x1b\[[0-9;]*[mGKH]//g'"
Bob