Superposition Shows How Far RadeonSI Gallium3D Has Evolved vs. AMDGPU-PRO

[duby229]

you are from fantasy world where mesa works on windows or amd does not have almost all customers on windows. in reality fixes from amd vulkan driver get into radv via radeonsi

And that's bad how exactly?

[pal666]

Then where's the open source code? I'll tell you, it's in radv right now, and no thanks to AMD at all.

you are from fantasy world where mesa works on windows or amd does not have almost all customers on windows. in reality fixes from amd vulkan driver get into radv via radeonsi

[pal666]

Why doesn't AMD instead decide to take the financial and human resources it wastes on proprietary drivers and use them to assist it's customers in modernizing their codebases to actually work with correct modern drivers? It seems like that -would- actually benefit linux and AMD and foremost their customers.

why don't you enable your brain and understand that mesa does not work on windows?

[pal666]

I was never able to make it work correctly with the driver provided.

card does not provide driver. your linux distro does, so switch distro if your is broken

[pal666]

again?! why AMD continues with two official drivers? Why they don't simply give up from closed one? and put more ppl working with open ones?

again?! why you continue spewing bullshit? why you don't simply listen to answers? and put more time educating yourself?

[pal666]

I can never expect open source driver to preform as well as ones provided by the manufactures.

most of open source drivers are provided by the manufactures

[duby229]

Wth does an application profile have to do with non-standard behaviour? App profiles are about knowing what an application does and letting the driver take a specific code path instead of a generic one. You know, the power devs have been asking in lower level APIs?

It's basically the same as applying quick sort by default, but using bubble sort when you know some specific app uses mostly sorted collections.

Because compatibility profiles are specified in 3.0 only. It was in the specs at 3.0, it was not in the specs at 4.0. Behaviour outside of specifications is non-standard. Relying on compatibility profiles and using specifications outside of OpenGL 3.0 is non-standard behaviour.

EDIT: Actually, that's not right, I misunderstood. See here. https://www.phoronix.com/forums/foru...655#post945655

[dungeon]

This is what Debian gives me, and digging around it appears due to symbols Debian has stripped from their Qt stack.

./Superposition
mdriftmeyer@horus:~/Downloads/Unigine_Superposition-1.0$ qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function sk_num

From another thread, ssl is in transit in Debian testing/sid... and this one wanna older

https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/945241-unigine-superposition-is-a-beautiful-way-to-stress-your-gpu-in-2017-17-way-graphics-card-comparison?p=945363#post945363

[bug77]

Idiot. This conversatrion doesn't have anything at all to do with Gentoo. It has to do with Proprietary graphics drivers allowing compatibility profiles in situations where they are non-standard. Those same proprietary drivers allow that non-standard behaviour regardless of distro or kernel used. Whether it's Gentoo, Debian, Redhat, Ubuntu, Or even Windows or OSX, It's still the wrong non-standard behaviour.

Wth does an application profile have to do with non-standard behaviour? App profiles are about knowing what an application does and letting the driver take a specific code path instead of a generic one. You know, the power devs have been asking in lower level APIs?

It's basically the same as applying quick sort by default, but using bubble sort when you know some specific app uses mostly sorted collections.

[Marc Driftmeyer]

This is what Debian gives me, and digging around it appears due to symbols Debian has stripped from their Qt stack.

./Superposition
mdriftmeyer@horus:~/Downloads/Unigine_Superposition-1.0$ qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function sk_num