Re: Re: Slow performance due to llvmpipe being used despite Radeon kernel and X modules being loaded
Some progress has been made. Today, I have gone to the TTY1 console, logged in to my account, stopped the LightDM service, and started X. I looked at glxinfo, and saw the correct info instead of llvmpipe. It now says that I have "DRI Radeon R200..." in renderer string, and when I started Compiz, it is smooth. I even added lightdm user to the video group because I suspect that lightdm is starting X server with the session of lightdm user, but it didn't change from llvmpipe to DRI Radeon. I don't want to kill lightdm and restart X from TTY1 to have a usable accelerated desktop, so I was wondering if there is some kind of configuration in lightdm that would enable hardware acceleration. If not, then what should I do to force lightdm to use hardware acceleration?
Re: Re: Slow performance due to llvmpipe being used despite Radeon kernel and X modules being loaded
Thanks for the response. However, I am not using VMware on my old PC to virtualize Debian; I have installed it as a dual-boot system. By the way, when I have executed "sudo apt list firmware-amd-graphics", it returns the following: Listing... Done firmware-amd-graphics/testing,now 20190717-2 all [installed] So, it means that the firmware is installed. Also, when I run Linux 5.5 and 5.6, the elements seem to be broken as you can see in the following images: 1. https://i.imgur.com/9tiIBlW.jpg 2. https://i.imgur.com/Kis3HpV.jpg 3. https://i.imgur.com/MYFwaGi.jpg 4. https://i.imgur.com/ekRi0SR.jpg 5. https://i.imgur.com/HAm0IR1.jpg 6. https://i.imgur.com/m8OwQmt.jpg 7. https://i.imgur.com/1aEcUCX.jpg But when I run Linux 4.19, all elements (buttons, text, etc.) seem to be fine. However, all versions of Linux lead to the llvmpipe issue.
Re: Slow performance due to llvmpipe being used despite Radeon kernel and X modules being loaded
Le 07/05/2020 à 19:28, Sven Joachim a écrit : > No, it is just listed because the llvmpipe driver was developed by > VMWare. You can see this for yourself, setting LIBGL_ALWAYS_SOFTWARE=1 > in the environment makes libgl use the llvmpipe driver: > > , > | LIBGL_ALWAYS_SOFTWARE=1 glxinfo | grep OpenGL | head -n2 > | OpenGL vendor string: VMware, Inc. > | OpenGL renderer string: llvmpipe (LLVM 10.0.0, 128 bits) [...) Thanks for the info, Sven :-)
Re: Slow performance due to llvmpipe being used despite Radeon kernel and X modules being loaded
On 2020-05-07 09:50 +0200, didier gaumet wrote: > Le 06/05/2020 à 22:15, EoflaOE ViceCity a écrit : >> Hello. Sorry for the length of this problem, but I am trying to get the >> X server to use my graphics card, AMD Radeon 9200 SE (RV280), instead of >> my CPU to render things on the desktop. I actually have a newer >> computer, but I use the older computer for experiments. Here's how the >> problem goes. >> >> Last month, I have installed Debian 10 on my old computer for testing >> purposes, and upgraded it to testing to test newer versions of packages >> to see if there are bugs. > |...] >> "glxinfo | grep OpenGL": >> >> OpenGL vendor string: *VMware, Inc.* >> OpenGL renderer string: *llvmpipe (LLVM 9.0.1, 128 bits)* > [...] >> X server logs "cat /var/log/Xorg.0.log | grep -i radeon": > [...] >> [ 57.917] (II) RADEON(0): [DRI2] Setup complete >> [ 57.917] (II) RADEON(0): [DRI2] DRI driver: r200 >> [ 57.918] (II) RADEON(0): Front buffer size: 5175K >> [ 57.918] (II) RADEON(0): VRAM usage limit set to 108490K >> [ 57.935] (==) RADEON(0): DRI3 disabled >> [ 57.935] (==) RADEON(0): Backing store enabled >> [ 57.935] (II) RADEON(0): Direct rendering enabled >> [ 57.936] (II) RADEON(0): Render acceleration enabled for R200 type >> cards. > [...] >> By the way I am >> using Linux 5.6 from testing, if that matters. > > Hello, > > what puzzles me is VMWare as OpenGL vendor: am I wrong or does it mean > that you have installed Debian as a VMWare guest? No, it is just listed because the llvmpipe driver was developed by VMWare. You can see this for yourself, setting LIBGL_ALWAYS_SOFTWARE=1 in the environment makes libgl use the llvmpipe driver: , | LIBGL_ALWAYS_SOFTWARE=1 glxinfo | grep OpenGL | head -n2 | OpenGL vendor string: VMware, Inc. | OpenGL renderer string: llvmpipe (LLVM 10.0.0, 128 bits) ` Why in the OP's system the llvmpipe driver is used instead of r200, I don't know. Maybe firmware-amd-graphics is not installed, although the logs suggest to me that it is. Cheers, Sven
Re: Slow performance due to llvmpipe being used despite Radeon kernel and X modules being loaded
Le 06/05/2020 à 22:15, EoflaOE ViceCity a écrit : > Hello. Sorry for the length of this problem, but I am trying to get the > X server to use my graphics card, AMD Radeon 9200 SE (RV280), instead of > my CPU to render things on the desktop. I actually have a newer > computer, but I use the older computer for experiments. Here's how the > problem goes. > > Last month, I have installed Debian 10 on my old computer for testing > purposes, and upgraded it to testing to test newer versions of packages > to see if there are bugs. |...] > "glxinfo | grep OpenGL": > > OpenGL vendor string: *VMware, Inc.* > OpenGL renderer string: *llvmpipe (LLVM 9.0.1, 128 bits)* [...] > X server logs "cat /var/log/Xorg.0.log | grep -i radeon": [...] > [ 57.917] (II) RADEON(0): [DRI2] Setup complete > [ 57.917] (II) RADEON(0): [DRI2] DRI driver: r200 > [ 57.918] (II) RADEON(0): Front buffer size: 5175K > [ 57.918] (II) RADEON(0): VRAM usage limit set to 108490K > [ 57.935] (==) RADEON(0): DRI3 disabled > [ 57.935] (==) RADEON(0): Backing store enabled > [ 57.935] (II) RADEON(0): Direct rendering enabled > [ 57.936] (II) RADEON(0): Render acceleration enabled for R200 type > cards. [...] > By the way I am > using Linux 5.6 from testing, if that matters. Hello, what puzzles me is VMWare as OpenGL vendor: am I wrong or does it mean that you have installed Debian as a VMWare guest? If it is the case, I do not know VMWare at all, but I think there is a form of passthrough for your graphic card, VMWare recognises it as a Radeon (not a generic card) but by default 3D acceleration (DRI3?) is disabled in VMWare and you have to enable it on your VMWare host. Debian Testing is for testing a possibly broken Debian in order for the contributors to build the next stable release without bugs. It is not really for testing new functionnalities
Slow performance due to llvmpipe being used despite Radeon kernel and X modules being loaded
Hello. Sorry for the length of this problem, but I am trying to get the X server to use my graphics card, AMD Radeon 9200 SE (RV280), instead of my CPU to render things on the desktop. I actually have a newer computer, but I use the older computer for experiments. Here's how the problem goes. Last month, I have installed Debian 10 on my old computer for testing purposes, and upgraded it to testing to test newer versions of packages to see if there are bugs. When I installed XScreenSaver to have fancy idling animations because MATE Screensaver has only generic ones, I have noticed that the screensavers were running slower than usual, even after increasing frame rate (-delay 0) in screensavers. I have looked up for clues, and found the command, glxinfo, to list details about the OpenGL rendering. So, I executed the command, and found that it is using llvmpipe instead of the Radeon driver (open source, not fglrx). "glxinfo | grep OpenGL": OpenGL vendor string: *VMware, Inc.* OpenGL renderer string: *llvmpipe (LLVM 9.0.1, 128 bits)* OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.3.3 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.3.3 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.3.3 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 OpenGL ES profile extensions: To ensure that all of the necessary Radeon modules were loaded correctly, I have grepped the X server logs (/var/log/Xorg.0.log) and dmesg with "radeon" and "drm", as well as the "inxi -G" output, and found the following information: X server logs "cat /var/log/Xorg.0.log | grep -i radeon": [55.616] (II) Applying OutputClass "Radeon" to /dev/dri/card0 [55.616]loading driver: radeon [55.617] (==) Matched radeon as autoconfigured driver 0 [55.617] (II) LoadModule: "radeon" [55.859] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [56.161] (II) Module radeon: vendor="X.Org Foundation" [56.951] (II) RADEON: Driver for ATI/AMD Radeon chipsets: -truncated- ..., ATI Radeon 9200, ATI Radeon 9200SE, ... -truncated- [57.164] (II) RADEON(0): Creating default Display subsection in Screen section [57.164] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [57.165] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [57.165] (==) RADEON(0): Default visual is TrueColor [57.165] (==) RADEON(0): RGB weight 888 [57.165] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [57.165] (--) RADEON(0): Chipset: "ATI Radeon 9200SE" (ChipID = 0x5964) [57.527] (II) RADEON(0): KMS Color Tiling: disabled [57.527] (II) RADEON(0): KMS Color Tiling 2D: disabled [57.527] (==) RADEON(0): TearFree property default: auto [57.527] (II) RADEON(0): KMS Pageflipping: enabled [57.527] (II) RADEON(0): SwapBuffers wait for vsync: enabled [57.756] (II) RADEON(0): Output VGA-0 has no monitor section [57.766] (II) RADEON(0): Output S-video has no monitor section [57.828] (II) RADEON(0): EDID for output VGA-0 [57.831] (II) RADEON(0): Manufacturer: ACR Model: 1a Serial#: 2451600041 [57.831] (II) RADEON(0): Year: 2009 Week: 22 [57.831] (II) RADEON(0): EDID Version: 1.3 [57.831] (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V [57.831] (II) RADEON(0): Sync: Separate [57.831] (II) RADEON(0): Max Image Size [cm]: horiz.: 41 vert.: 26 [57.831] (II) RADEON(0): Gamma: 2.20 [57.831] (II) RADEON(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display [57.831] (II) RADEON(0): First detailed timing is preferred mode [57.831] (II) RADEON(0): redX: 0.636 redY: 0.349 greenX: 0.290 greenY: 0.589 [57.831] (II) RADEON(0): blueX: 0.143 blueY: 0.080 whiteX: 0.313 whiteY: 0.329 [57.831] (II) RADEON(0): Supported established timings: [57.831] (II) RADEON(0): 720x400@70Hz [57.831] (II) RADEON(0): 640x480@60Hz [57.831] (II) RADEON(0): 640x480@67Hz [57.831] (II) RADEON(0): 640x480@72Hz [57.831] (II) RADEON(0): 640x480@75Hz [57.831] (II) RADEON(0): 800x600@56Hz [57.831] (II) RADEON(0): 800x600@60Hz [57.831] (II) RADEON(0): 800x600@72Hz [57.831] (II) RADEON(0): 800x600@75Hz [57.831] (II) RADEON(0): 832x624@75Hz [57.831] (II) RADEON(0): 1024x768@60Hz [57.832] (II) RADEON(0): 1024x768@70Hz [57.832] (II) RADEON(0): 1024x768@75Hz [57.832] (II) RADEON(0): 1280x1024@75Hz [57.832] (II) RADEON(0): 1152x864@75Hz [57.832] (II) RADEON(0): Manufacturer's mask: 10 [57.832] (II) RADEON(0): Supported standard timings: [57.832] (II) RADEON(0): #0: hsize: 1440 vsize 900 refresh: 60 vid: 149 [57.832] (II) RADEON(0): #1: hsize: 1440 vsize 900
