You are not logged in.
This is before the 2023 archiso it was installed with the Dec2022 archiso after the 25th
I went with the arch installation method (previously ran well but ran into errors like screen freezes)
I have purchased a new Card AMD Radeon RX 6700 XT and installed drivers, for it.
Drivers.
sudo pacman -S --needed lib32-mesa vulkan-radeon lib32-vulkan-radeon vulkan-icd-loader lib32-vulkan-icd-loader
I still had issues so I went and got amdgpu and installed that too.
While this seems to work I am left with wayland session, I wish to not run wayland the wiki seems to say
that one can modify an "environment variable GDK_BACKEND=x11" under
https://wiki.archlinux.org/title/wayland 4.1 GTK
But altering this environment variable, where it is stored, how to alter it ....
Is unclear howto to do it and where.
Some of my programs flameshot do not run under wayland.
So How to fix all of these problems ?
How to suppress wayland start?
I am unsure whether to post here or in the newbie, forum.
Last edited by Data007 (2023-03-24 13:38:47)
Offline
What are you actually booting into? Whether you pick a xorg or wayland session is dependant on the display manager you are using. I¨m assuming "arch installation method" was using the archinstall script? Nothing about amdgpu or mesa will be inherently relevant here.
Moving to NC
Offline
Hi
Kde plasma was chosen which defaults to sddm
I have tried lightdm that agreed even less with the system(prompting insane pops from kde wallet)
So I returned to sddm
--
Data
Offline
In SDDM you will have a dropdown to choose whether you want to boot an X11 or a wayland session.
Offline
Hi Thanks, you think I was born yesterday thanks.
I have been typing my password in the box forgetting that there are options.
Thanks can we leave this open to see if I still get freezes? now
on a wayland less setup.
--
Data007
Last edited by Data007 (2023-01-03 12:17:16)
Offline
Yes, if you do still get issues/freezes, after rebooting from such a freeze please post
sudo journalctl -b-1
Offline
Hi
Yeah will do I think its more or less sorted at the moment, but I will look at the logs
you have posted about should any more problems occur.
It seems to lock up or at least did, as I say I will thanks.
-
Data 007
Offline
Yes, if you do still get issues/freezes, after rebooting from such a freeze please post
sudo journalctl -b-1
Hi
Should say I have just had oddity.
It's rather big to post so I will attach it if I figure out how.
I've even gone to pastebin to post the log however it says I have gone over the limit
Is there a way to cut down the size of it(log)
@V1del Any help greatly appreciated! I did journalctl -b-1 >log.txt But the file is 2.3Mb too big for Pbin
I have a website the file can be downloaded from there.
https://stevedoeslinux.com/graphical-problems
Last edited by Data007 (2023-01-05 12:20:21)
Offline
Hi @V1del another computer freeze
Is this a complete failure this card?
--
Data007
Offline
I'd test a stable mesa release first and foremost but this is a kernel failure try booting with the kernel parameters
amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0 pcie_aspm=off
to disable some power saving features.
Offline
I'd test a stable mesa release first and foremost but this is a kernel failure try booting with the kernel parameters
amdgpu.aspm=0 amdgpu.runpm=0 amdgpu.bapm=0 pcie_aspm=off
to disable some power saving features.
I am unsure how to do what you suggest, can you explain how??!
Booting with parameters? What must I edit, please?
I am not on grub
inxi -b Says in part.....
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M]
driver: amdgpu v: kernel
Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7 driver: X:
loaded: amdgpu unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu
resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz
API: OpenGL v: 4.6 Mesa 23.0.0-devel (git-22543653d5) renderer: AMD
Radeon RX 6700 XT (navi22 LLVM 14.0.6 DRM 3.49 6.1.3-arch1-1)
HIH
--
Data 007
Last edited by Data007 (2023-01-05 18:32:45)
Offline
Hi V1del
A Linux dev made a video explaining how, so I managed to add those parameters to the kernel.
You also mention that I should install/add a full-blown mesa!
When I take the prompt and do paru -S mesa ; I find that mesa and mesa-git are in conflict.
So I don't know what else to do there seem's to already be a mesa package installed.
In fact Davinci Resolve which won't run without proper graphics drivers has no difficulties running.
Any thoughts?
Data007.
Offline
The question is why you have mesa-git instead of normal mesa. One is a development version that potentially has some in devolpment/unstable issues and the other is a stable and tested release. While I doubt it to be hugely relevant to the system freezes per se you'd probably want a "stable" stack if you are running into graphics issues.
Offline
Hi V1del
I guess it boils down to my inexperience with installing drivers for and cards, always had NVIDIA before.
Iam aware I can remove via force pacman -Rdd mesa
But I am faced with this trying to set matters straight.
[data007@archlinux ~]$ paru -S mesa
[sudo] password for Data007:
resolving dependencies...
looking for conflicting packages...
:: mesa and mesa-git are in conflict (mesa-libgl). Remove mesa-git? [y/N] Y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing mesa-git breaks dependency 'vulkan-radeon' required by lib32-vulkan-radeon
Think possibly just leave it, its stablish at the moment.
--
Data007
Offline
Stuff like this happens if you use AUR helpers "by default" and then don't pay attention to what they are installing. If you have no good reason for a git package you generally shouldn't be using the git package. You don't need to force remove anything, you should be able to do
pacman -Syu {lib32-,}{mesa,vulkan-radeon}
to get past this particular failure
Offline
Stuff like this happens if you use AUR helpers "by default" and then don't pay attention to what they are installing. If you have no good reason for a git package you generally shouldn't be using the git package. You don't need to force remove anything, you should be able to do
pacman -Syu {lib32-,}{mesa,vulkan-radeon}
to get past this particular failure
While this has worked the app Davinchi Resolve18 which was working has now, gone to "unsupported GPU processing mode".
So that is not now working as in I can not edit my videos.
Inxi reports the following now.
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M]
driver: amdgpu v: kernel
Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7 driver: X:
loaded: modesetting unloaded: radeon dri: radeonsi gpu: amdgpu resolution:
1: 1920x1080~60Hz 2: 1920x1080~60Hz
API: OpenGL v: 4.6 Mesa 22.3.2 renderer: AMD Radeon RX 6700 XT (navi22
LLVM 14.0.6 DRM 3.49 6.1.3-arch1-1)
--
Data007
Offline
EDITED:
I took to long write this.
Please post pacman -Qs vulkan
<end-of-edit>
There will likely be more error messages and combining such a change with a full upgrade complicates things further.
I advise to do a full pacman -Syu first
After that has finished, run
pacman -S {lib32-,}{mesa,vulkan-radeon}
Depending on your installed packages you may also get errors for
libva-mesa-driver, mesa-libgl, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-mesa-layer, vulkan-swrast
and lib32-libva-mesa-driver, lib32-mesa-libgl, lib32-mesa-vdpau, lib32-vulkan-intel, lib32-vulkan-mesa-layer .
Add the ones you get to the pacman -S command one by one , rerun until you have covered everything. and the switch is made succesfully .
After the switch has been made, run pacman -Syu again to confirm your system state is fully uptodate.
Last edited by Lone_Wolf (2023-01-06 11:35:56)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi
local/lib32-vulkan-icd-loader 1.3.235-1
Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/lib32-vulkan-radeon 22.3.2-2
Radeon's Vulkan mesa driver (32-bit)
local/spirv-tools 2022.4-1 (vulkan-devel)
API and commands for processing SPIR-V modules
local/vulkan-amdgpu-pro 22.40_1518373-1 (Radeon_Software_for_Linux)
AMDGPU Pro Vulkan driver
local/vulkan-icd-loader 1.3.235-1
Vulkan Installable Client Driver (ICD) Loader
local/vulkan-radeon 22.3.2-3
Radeon's Vulkan mesa driver
local/vulkan-tools 1.3.235-2 (vulkan-devel)
Vulkan Utilities and Tools
Packages (4) lib32-mesa-22.3.2-2 lib32-vulkan-radeon-22.3.2-2 mesa-22.3.2-3
vulkan-radeon-22.3.2-3
sudo pacman -S lib32-libva-mesa-driver, lib32-mesa-libgl, lib32-mesa-vdpau, lib32-vulkan-intel, lib32-vulkan-mesa-layer
error: target not found: lib32-libva-mesa-driver,
error: target not found: lib32-mesa-libgl,
error: target not found: lib32-mesa-vdpau,
error: target not found: lib32-vulkan-intel,
Offline
Hi @Lone Wolf Many thanks for the hard work I've copied the commands and output below. DaVinchi Resolve refuses still to work
this is possibly down to missed packages.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
sudo pacman -Qs vulkan
[sudo] password for steve:
local/lib32-vulkan-icd-loader 1.3.235-1
Vulkan Installable Client Driver (ICD) Loader (32-bit)
local/lib32-vulkan-radeon 22.3.2-2
Radeon's Vulkan mesa driver (32-bit)
local/spirv-tools 2022.4-1 (vulkan-devel)
API and commands for processing SPIR-V modules
local/vulkan-amdgpu-pro 22.40_1518373-1 (Radeon_Software_for_Linux)
AMDGPU Pro Vulkan driver
local/vulkan-icd-loader 1.3.235-1
Vulkan Installable Client Driver (ICD) Loader
local/vulkan-radeon 22.3.2-3
Radeon's Vulkan mesa driver
local/vulkan-tools 1.3.235-2 (vulkan-devel)
Vulkan Utilities and Tools
pacman -S {lib32-,}{mesa,vulkan-radeon}
warning: lib32-mesa-22.3.2-2 is up to date -- reinstalling
warning: lib32-vulkan-radeon-22.3.2-2 is up to date -- reinstalling
warning: mesa-22.3.2-3 is up to date -- reinstalling
warning: vulkan-radeon-22.3.2-3 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (4) lib32-mesa-22.3.2-2 lib32-vulkan-radeon-22.3.2-2 mesa-22.3.2-3
vulkan-radeon-22.3.2-3
Total Installed Size: 160.40 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] Y
(4/4) checking keys in keyring [######################] 100%
(4/4) checking package integrity [######################] 100%
(4/4) loading package files [######################] 100%
(4/4) checking for file conflicts [######################] 100%
:: Processing package changes...
(1/4) reinstalling mesa [######################] 100%
(2/4) reinstalling lib32-mesa [######################] 100%
(3/4) reinstalling vulkan-radeon [######################] 100%
(4/4) reinstalling lib32-vulkan-radeon [######################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
sudo pacman -S libva-mesa-driver, mesa-libgl, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-mesa-layer, vulkan-swrast
and lib32-libva-mesa-driver, lib32-mesa-libgl, lib32-mesa-vdpau, lib32-vulkan-intel, lib32-vulkan-mesa-layer
error: target not found: libva-mesa-driver,
error: target not found: mesa-libgl,
error: target not found: mesa-vdpau,
error: target not found: opencl-mesa,
error: target not found: vulkan-intel,
error: target not found: vulkan-mesa-layer,
bash: and: command not found
:: Starting full system upgrade...
there is nothing to do
XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
I await help @Lone Wolf ... Should I use yay or paru?
--
Data007
Offline
the set of packages you have is correct now (... though especially for davinci you probably want to make sure you have mesa-opencl ), what's the exact error you get from davinci ? Post it and use code tags to post them.
Also
pacman -Qs mesa
glxinfo -B
clinfo
You should ideally not use either of the two until you understand the difference between repository and AUR packages, after you understand said difference and are aware of the pitfalls and dangers of the AUR it doesn't matter which you are using, but you need to be aware of the difference between an AUR and a repo package and what kind of issues that might entail and you aren't if you accidentally installed a -git version without meaning to.
Last edited by V1del (2023-01-06 16:44:48)
Offline
Hi the output from Davinci is a graphical dialog
Unsuported GPU Processing Mode
please review the GPU drivers and GPU
configuration under preferences.
local/glu 9.0.2-3
Mesa OpenGL utility library
local/lib32-glu 9.0.2-3
Mesa OpenGL utility library (32 bits)
local/lib32-mesa 22.3.2-2
An open-source implementation of the OpenGL specification (32-bit)
local/lib32-vulkan-radeon 22.3.2-2
Radeon's Vulkan mesa driver (32-bit)
local/mesa 22.3.2-3
An open-source implementation of the OpenGL specification
local/mesa-utils 8.5.0-2
Essential Mesa utilities
local/vulkan-radeon 22.3.2-3
Radeon's Vulkan mesa driver
glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon RX 6700 XT (navi22, LLVM 14.0.6, DRM 3.49, 6.1.3-arch1-1) (0x73df)
Version: 22.3.2
Accelerated: yes
Video memory: 12288MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
VBO free memory - total: 11511 MB, largest block: 11511 MB
VBO free aux. memory - total: 31985 MB, largest block: 31985 MB
Texture free memory - total: 11511 MB, largest block: 11511 MB
Texture free aux. memory - total: 31985 MB, largest block: 31985 MB
Renderbuffer free memory - total: 11511 MB, largest block: 11511 MB
Renderbuffer free aux. memory - total: 31985 MB, largest block: 31985 MB
Memory info (GL_NVX_gpu_memory_info):
Dedicated video memory: 12288 MB
Total available memory: 44392 MB
Currently available dedicated video memory: 11511 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 6700 XT (navi22, LLVM 14.0.6, DRM 3.49, 6.1.3-arch1-1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.3.2
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.3.2
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
clinfo
Number of platforms 0
Any further help is gratefully received ? as far as the DaVinci error it's standard I can post the output pic on my website if you really need to see it
however there inside is nothing to alter to recognize the drivers. It has to detect the driver its-self.
--
Data 007
Offline
clinfo needs to get something, and in the outptu we see opencl-mesa isn't installed which it implicitly was when you had the git version, install opencl-mesa
Offline
Hi I install the package I did try before.
:: Processing package changes...
(1/2) installing spirv-llvm-translator [######################] 100%
(2/2) installing opencl-mesa [######################] 100%
Optional dependencies for opencl-mesa
opencl-headers: headers necessary for OpenCL development
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Davichi Resolve now works
Offline
Hi V1del
Just had a crash (i was away from the computer when I returned it was locked, and unlocking led to the crash)
It's too big I feel to post here so I have deleted the original logs posted on my website and uploaded another file.
https://stevedoeslinux.com/graphical-problems
--
Data007
Offline
Hi
After rebooting and login got a straight crash.
https://pastebin.com/6m9Fnugd
Its small enough to pastebin.
Offline