[SOLVED] No Graphical Acceleration With ATI Card on Mesa

archerbarcher · 2025-06-13 23:34:35

Hello all, up until recently my system has been working with OpenGL, until I turned it on today and all my windows were juttery and nothing was running well. Running glxinfo responds that my render device is llvmpipe and acceleration is disabled. I already have mesa, xf86-video-ati, and the radeon driver running, and eglinfo does report the presence of my device, but for some reason llvmpipe is still being used. How might I be able to regain functionality of my video card?

Here are the images of my issue:
Glxinfo

Eglinfo -B

lsmod

Last edited by archerbarcher (2025-06-30 21:33:59)

seth · 2025-06-14 05:32:40

Please replace the oversized images with links and generally do not post screenshots of text, post the text.

https://wiki.archlinux.org/title/OpenGL#Installation
You've an RV370 from ~2008, make a fair assessment whether that counts as "older".

However, why is amdgpu loaded?

lspci -k

archerbarcher · 2025-06-14 06:16:49

Running lspci -k yields this for my graphics card:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0602
	Kernel driver in use: radeon
	Kernel modules: radeon, amdgpu
01:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300 SE]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0603
	Kernel modules: amdgpu

As for it being an older card, I did try mesa-amber, but this failed to load the driver, so I'm guessing given it's on r300 architecture it should (hopefully) be fine on the regular branch.

seth · 2025-06-14 07:29:12

In what world is an RV370 supported by amdgpu??

lspci -nn
uname -a
cat /proc/cmdline

Also 01:00.1 is *only* supported by amdgpu, but the module doesn't assign? Then why in gods name is amdgpu loaded?
Do you load it explicitly?
In doubt please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

and do not try to force the system to run on amdgpu

But yeah, that should™ still be supported by the r300 driver - sorry.
Speaking of which

MESA_LOADER_DRIVER_OVERRIDE=r300 glxinfo -B

archerbarcher · 2025-06-14 07:47:01

seth wrote:

lspci -nn
uname -a
cat /proc/cmdline

Here is the output.

 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02)
00:01.0 PCI bridge [0604]: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port [8086:2771] (rev 02)
00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01)
00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 01)
00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 [8086:27c8] (rev 01)
00:1d.1 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 [8086:27c9] (rev 01)
00:1d.2 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 [8086:27ca] (rev 01)
00:1d.3 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 [8086:27cb] (rev 01)
00:1d.7 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller [8086:27cc] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01)
00:1f.2 IDE interface [0101]: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] [8086:27c0] (rev 01)
00:1f.3 SMBus [0c05]: Intel Corporation NM10/ICH7 Family SMBus Controller [8086:27da] (rev 01)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300] [1002:5b60]
01:00.1 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X300 SE] [1002:5b70]
03:08.0 Ethernet controller [0200]: Intel Corporation NM10/ICH7 Family LAN Controller [8086:27dc] (rev 01)
Linux pc 6.15.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 10 Jun 2025 21:32:33 +0000 x86_64 GNU/Linux
BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=1751f7f6-2db9-4fe6-9413-ab8b43080919 rw

seth wrote:

Do you load it explicitly?

I don't think so...? I shouldn't have changed anything except for updating all my packages from the last time everything was working. Although, it had been several months since I last used the computer, so there may have been some major updates.

seth wrote:

In doubt please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

Here is the link to my journal:
http://0x0.st/8EhW.txt

seth wrote:

MESA_LOADER_DRIVER_OVERRIDE=r300 glxinfo -B

name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0xffffffff)
    Device: llvmpipe (LLVM 20.1.6, 128 bits) (0xffffffff)
    Version: 25.1.3
    Accelerated: no
    Video memory: 2965MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 4.5
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 0 MB, largest block: 0 MB
    VBO free aux. memory - total: 1677 MB, largest block: 1677 MB
    Texture free memory - total: 0 MB, largest block: 0 MB
    Texture free aux. memory - total: 1677 MB, largest block: 1677 MB
    Renderbuffer free memory - total: 0 MB, largest block: 0 MB
    Renderbuffer free aux. memory - total: 1677 MB, largest block: 1677 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 0 MB
    Total available memory: 2965 MB
    Currently available dedicated video memory: 0 MB
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 20.1.6, 128 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 25.1.3-arch1.3
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.5 (Compatibility Profile) Mesa 25.1.3-arch1.3
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.1.3-arch1.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

I've tried other flags too in order to force the graphics card and Mesa seemingly ignores all of them.

seth · 2025-06-14 08:27:11

This is a regression?
amdgpu "just loads", blacklist amdgpu and add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters to also block the simpledrm device, see where that gets us.

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General - what is in

Jun 13 23:05:01 pc sudo[526]:      dav : TTY=tty2 ; PWD=/usr/share/X11/xorg.conf.d ; USER=root ; COMMAND=/usr/bin/nano 10-radeon.conf

and why? Do you use xf86-video-ati? What if you remove that and run on the modesetting driver.

archerbarcher · 2025-06-15 18:06:12

Just blacklisted amdgpu and drm in Grub, can confirm amdgpu is no longer being loaded in the modules.
My X11 log is here
"10-radeon.conf" is the X11 entry that the package xf86-video-ati inserts, and it contains the parameters:

Section "OutputClass"
	Identifier "Radeon"
	MatchDriver "radeon"
	Driver "radeon"
EndSection

I have tried removing this and relying on modesetting, but then I just get a blank screen with a blinking cursor when LightDM is supposed to start (Picture here).

Sorry for the late response, I had a lot of stuff going on yesterday.

cryptearth · 2025-06-15 22:11:56

is there any reason for still running 20 year old hardware?
or to turn it around: what makes you believe that todays software still supports 20 year old hardware? if you want to run 20 year old hardware - ok, fine - that's up to you - but I recommend you run era-correct software - which, for mid-200s, is about Debian 4 or suse 9/10 - but certainly not current arch from 2025
either upgrade the hardware or downgrade the software - but don't expect stuff 20 years apart to work together - this just doesn't work in computer technology

archerbarcher · 2025-06-15 22:31:51

I understand the hardware I am using is very old and obsolete. The main reason I am using this computer is because I'm in a rough financial spot and this is the only thing I have while I put together a newer computer.

cryptearth wrote:

either upgrade the hardware or downgrade the software - but don't expect stuff 20 years apart to work together - this just doesn't work in computer technology

I understand it may have stopped working in modern arch, but I know it was working as of roughly 6 months ago, and given a new driver was released roughly 3 years ago and it is still mentioned as supported in the wiki, I would hope it works. I don't know if I can use any older distribution of Linux because I need to do things like browse the web, play games, and use messaging software.

seth · 2025-06-19 12:55:19

Sorry for the long delay.

[    11.571] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun 15 10:52:43 2025
[    11.845] (II) RADEON(0): Render acceleration enabled for R300/R400/R500 type cards.
[    11.845] (II) EXA(0): Driver allocated offscreen pixmaps
[    11.846] (II) EXA(0): Driver registered support for the following operations:
[    11.846] (II)         Solid
[    11.846] (II)         Copy
[    11.846] (II)         Composite (RENDER acceleration)
[    11.846] (II)         UploadToScreen
[    11.846] (II)         DownloadFromScreen
[    11.846] (II) RADEON(0): Acceleration enabled
[    11.858] (II) Initializing extension GLX
[    12.327] (II) AIGLX: Loaded and initialized r300
[    12.327] (II) GLX: Initialized DRI2 GL provider for screen 0

This looks properly accelerated and running

MESA_LOADER_DRIVER_OVERRIDE=r300 glxinfo -B

on an intel system gets me

name of display: :0
do_winsys_init: DRM version is 1.6.0 but this driver is only compatible with 2.50.0 (kernel 4.12) or later.
glx: failed to create dri3 screen
failed to load driver: r300

and falls back to zink (opengl via vulkan) - so it's not like r300 wouldn't load.

=> https://gitlab.freedesktop.org/mesa/mes … 300-driver

the r300 driver that builds and installs but since 6292dfb9 is unusable unless -Dlegacy-x11=dri2 is used. I expect Linux distributions to distribute broken builds of r300 in the near future without being aware of the brokenness

=> https://gitlab.archlinux.org/archlinux/ … /issues/31
It would be great if you could build and test a local mesa version w/ that flag enabled to confirm the problem.

@cryptearth

either upgrade the hardware or downgrade the software - but don't expect stuff 20 years apart to work together - this just doesn't work in computer technology

As long as mesa lists this as supported it either works or is a bug (likely in the DRIL shim) - or an undocumented "feature"… which is a documentation bug.
ELOLYOURSYSTEMOLD is still not a proper bug resolution.

Also, fwwi, I need to update but rn I cannot override the driver to swrast or llvmpipe

MESA_LOADER_DRIVER_OVERRIDE=swrast glxinfo -B                                                                                                                                                                                      
name of display: :0                                                                                                                                                                                                                                       
kmsro: driver missing                                                                                                                                                                                                                                     
glx: failed to create dri3 screen                                                                                                                                                                                                                         
failed to load driver: swrast

archerbarcher · 2025-06-30 18:20:43

Hello, sorry for such a long delay, I have been very busy this summer. I also needed to find a time I could let my machine run for a extended period uninterrupted to build Mesa. After building from source with the required flag, I can indeed confirm my video card is back to functioning. Running glxinfo I get this output:

[dav@pc ~]$ ./mesa-run.sh glxinfo | grep "OpenGL"
OpenGL vendor string: Mesa
OpenGL renderer string: ATI RV370
OpenGL version string: 2.1 Mesa 25.2.0-devel (git-153857fb64)
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 25.2.0-devel (git-153857fb64)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:

Additionally, glxgears runs as expected using my video card. Thank you so much for helping me resolve this issue, seth. I was going crazy having my desktop struggle to run. Now I just need to figure out how to install the compiled files system-wide. Should I file an official bug report with Mesa regarding this issue? I saw you already opened a ticket with them.
Thanks

seth · 2025-06-30 20:34:08

There's a mesa bug because of the r300 situation (DRI3 support) and an arch ticket to allow DRI2 - no need to open more bugs.
How this will move onward is to be seen.
Falling into a gap between mesa-amber and mesa and behind the support much older GPUs get certainly sucks
But we'll also have to cleanse the wiki from "hey, just disable DRI3 to avoid glitches" if this remains the status quo, so inaction isn't an option here and /a/ decision will have to be taken.
Stay tuned and hope for the best. Or keep compiling mesa yourself.

archerbarcher · 2025-06-30 21:32:37

Thanks! I'll go ahead and mark the thread as solved. I can't wait to get back to playing some video games now that this is fixed My desktop still runs slowly, although at this point I think that's just the fault of the card. It's so crappy I have to reduce my desktop resolution before I launch games otherwise they will crash.....
Thank you so much again for the help.

seth · 2025-07-01 06:03:33

I'm pretty sure I was playing Q3 on a geforce2… but I also think in 800x600 or maybe XGA

Going forward: does the modesetting driver now work w/ the DRI2 enabled version of mesa? (And which version exactly did you build?)
If it doesn't, can you please post the X11 and lightdm log of that attempt?

cryptearth · 2025-07-01 09:23:45

seth wrote:

LOLYOURSYSTEMOLD is still not a proper bug resolution.

well - if the actual reason is that the hardware is too old for the software one wants to run on I see either upgrade the hardware or downgrade the software at least >a valid< solution - and given that quite broken screenshot it seems a rather good one (unless that bad textures are caused by something else - which, unless an actual hardware failure, very likely is also caused by way too new software forced to run on way too old hardware)

seth · 2025-07-01 12:24:51

Not sure about the textures - look at the bezel logo (the OP might have to explain the screenshot, from his previous remarks maybe lack of VRAM) - also the original problem was that HW acceleration wasn't available at all, not even w/ glxgears.

About reasoning: It's perfectly possible and fine to state "with commit foobar your hardware is no longer supported because snafu, sorry", BUT:
If something doesn't work and that's not intended or deliberate or announced, you cannot then just bail on "dunno, probably your HW is just to old".
Not understanding the cause of undesired behavior is a bug and the above stance is equivalent to "i don't care" what is equivalent to "I'm too lazy to figure what's going on" and you're not reasoning anything.

We figured that this is because mesa (unlike mesa-amber) now defaults to demanding DRI3 and that the DRI3 implementation of that GPU is lagging because it's limited to OGL2 or OGL2.1 and - for now - the resolution has been to reactivate DRI2 in the repo builds rather than announcing the DRI3 mandate (which in any event would have required to fix what would then have become severe documentation bugs)

It's not about supporting old HW at all costs (arch dropped i686 support quite a while ago and there're ongoing discussions to require SSE2…) but to be in control of what's going on rather than dodging problems with para-religious explanations "you've probably fallen out of the gods favor".

archerbarcher · 2025-07-04 01:27:39

seth wrote:

Going forward: does the modesetting driver now work w/ the DRI2 enabled version of mesa? (And which version exactly did you build?)
If it doesn't, can you please post the X11 and lightdm log of that attempt?

I built version 25.2 of Mesa, and modesetting still isn't working. Same as before with just a blank blinking cursor.
Here are the respective links to the Xorg and LightDM logs:
http://0x0.st/80y4.txt
http://0x0.st/80yw.txt

cryptearth wrote:

well - if the actual reason is that the hardware is too old for the software one wants to run on I see either upgrade the hardware or downgrade the software at least >a valid< solution - and given that quite broken screenshot it seems a rather good one (unless that bad textures are caused by something else - which, unless an actual hardware failure, very likely is also caused by way too new software forced to run on way too old hardware)

You are right that the system is very old, although I don't think running an obscenely outdated version of an operating system would be a good idea either. I'm working on upgrading the hardware, but that takes time so for right now I'm just limping along with this. I agree it's sub optimal but I was mainly looking at getting some basic 3d acceleration going so I can enjoy some games in the meantime. And besides the poor game performance it's perfectly fine for desktop usage/internet browsing.

seth wrote:

Not sure about the textures - look at the bezel logo (the OP might have to explain the screenshot, from his previous remarks maybe lack of VRAM)

Yes, I think it is something with the textures, although strangely it only occurs in Xonotic (or at least I haven't yet stumbled into another game that has this issue). I can confirm it is recent though because on earlier mesa versions it wasn't present (I was looking through the mesa changelog and saw something related to textures for the r300 driver, so maybe this is the source of the issue).
An unaffected game

seth · 2025-07-04 07:28:58

Thanks for the update.

You don't have to build mesa version anymore, the repo builds have DRI2 re-enabled, glamor fails on

[    23.420] (WW) glamor requires at least 128 instructions (64 reported)

That's not work-a-roundable and you'll require xf86-video-amdgpu (and therefore currently DRI2 support)

The shader limitations also might cause the discoloring in xonotic, you can maybe deactivate some fancyness (bloom or so?) to prevent that?

Last edited by seth (2025-07-04 07:29:15)

archerbarcher · 2025-07-04 18:59:18

I'm glad to hear they re-enabled this in the Mesa builds, constantly building myself is unrealistic as each build takes ~4-5 hours. Thanks for bringing this to their attention and getting my graphics drivers functional again. There are very few games I can play (wine often crashes with a myriad of different errors) but of the games I have been able to play I've been enjoying immensely over the past few days.

Arch Linux

#1 2025-06-13 23:34:35

[SOLVED] No Graphical Acceleration With ATI Card on Mesa

#2 2025-06-14 05:32:40

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#3 2025-06-14 06:16:49

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#4 2025-06-14 07:29:12

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#5 2025-06-14 07:47:01

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#6 2025-06-14 08:27:11

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#7 2025-06-15 18:06:12

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#8 2025-06-15 22:11:56

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#9 2025-06-15 22:31:51

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#10 2025-06-19 12:55:19

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#11 2025-06-30 18:20:43

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#12 2025-06-30 20:34:08

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#13 2025-06-30 21:32:37

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#14 2025-07-01 06:03:33

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#15 2025-07-01 09:23:45

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#16 2025-07-01 12:24:51

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#17 2025-07-04 01:27:39

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#18 2025-07-04 07:28:58

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

#19 2025-07-04 18:59:18

Re: [SOLVED] No Graphical Acceleration With ATI Card on Mesa

Board footer