View previous topic :: View next topic |
Author |
Message |
AndrewAmmerlaan Developer
Joined: 25 Jun 2014 Posts: 302 Location: Nijmegen
|
Posted: Sun May 07, 2017 7:10 am Post subject: [SOLVED]libgl error: unable to load driver: r600_dri.so |
|
|
So the other day I was reading up on wayland, and decided to give it a shot. I added the waylamd USE flag, and ran emerge -uDN @world. However after reboot the screen stayed black, trying to startx resulted in just a black screen and the following errors:
Code: |
libGL error : unable to load driver r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver
libGL error: unable to load driver swrast_dri.so
libGL error: failed to loaf driver swrast
Unrecognized opengl version
Unrecognized opengl version
|
After installing weston aswell, and elogind (as I read that it was required to make sddm work with wayland). Weston-launch also failed with similar error messages, it also failed to load r600.
Giving up on trying to get wayland to work for the moment, I reverted all the changes I made. Yet the weird thing is that after rebuilding, x still fails to start with the same error message, how can this be? How is it that this driver pointer is still missing, and how do I get it back? _________________ OS: Gentoo 6.8.10-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400
Last edited by AndrewAmmerlaan on Wed May 10, 2017 3:49 pm; edited 2 times in total |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9709 Location: almost Mile High in the USA
|
Posted: Sun May 07, 2017 5:48 pm Post subject: |
|
|
Just a guess here:
These modules are supplied by mesa, though probably this is unnecessary:
# emerge -1 mesa
However, this may be the problem: make sure you update your eselect for mesa and opengl to have a provider:
# eselect mesa list
# eselect opengl list
Make sure one of each section is still starred by setting one of them _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
AndrewAmmerlaan Developer
Joined: 25 Jun 2014 Posts: 302 Location: Nijmegen
|
Posted: Mon May 08, 2017 2:49 pm Post subject: |
|
|
Sadly, that didn't work. I also checked /var/log/messages for any additional output, but it didn't show anything out of the ordinary.
Also, here is my make.conf: https://bpaste.net/show/5918da83f273
EDIT: It seems that x does start when eselect mesa 64/32 bit software renderer is set to classic instead of gallium, it is however much slower and kwin crashes immediatly with a seg fault. _________________ OS: Gentoo 6.8.10-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
Back to top |
|
|
AndrewAmmerlaan Developer
Joined: 25 Jun 2014 Posts: 302 Location: Nijmegen
|
Posted: Wed May 10, 2017 3:48 pm Post subject: |
|
|
The good news is that I fixed it, the bad news is that I don't know exactly what fixed it. But I'll just leave what I did here for anyone else having a similar problem.
So basically I rebuilt everything with emerge -e @world which also rebuilt whatever was causing this problem. Consequently I don't know which package rebuild fixed it, however I do know that mesa nor xorg-server were the cause of it as I had already rebuilt those prior to rebuilding everything else. _________________ OS: Gentoo 6.8.10-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
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
|
|