[SOLVED] missing libhsakmt.so

nixIT · 2023-03-12 21:12:48

hello all,

finally got rocm-opencl-runtime installed, however when I run clinfo, I get the following:

dlerror: libhsakmt.so.1: cannot open shared object file: No such file or directory

not sure what package this library is associated with.

any ideas where to look?

-nixit

Last edited by nixIT (2023-03-15 13:23:32)

Trilby · 2023-03-12 21:15:40

nixIT wrote:

finally got rocm-opencl-runtime installed

And how did you do that? It would seem not through pacman. Either that or you've done a partial upgrade. That lib is provided by one of the dependencies of the package.

And why have you created another thread for this?

Last edited by Trilby (2023-03-12 21:17:06)

nixIT · 2023-03-13 02:32:45

Trilby wrote:

And how did you do that? It would seem not through pacman. Either that or you've done a partial upgrade. That lib is provided by one of the dependencies of the package.
And why have you created another thread for this?

I thought the issues were independent, however, from you asking how I did that I presume something in my gpu driver install/uninstall/reinstall didn't go so well.

I finally got rocm-opencl-runtime installed by the following:

sudo pacman -S rocm-opencl-runtime hsa-rocr rocm-device-libs

it appears that hsa-rocr and rocm-device-libs are dependencies, they aren't installed automatically by rocm-opencl-runtime.

any idea, besides starting with a fresh install, on how to completely remove all added amdgpu drivers (open and closed), including opencl and rocm? I'd like to see where I somehow screwed up my system.

Last edited by nixIT (2023-03-13 02:55:47)

Trilby · 2023-03-13 13:48:21

You posted the exact same error message from the same command in both threads. That seems related to me.

Anyhow, that's neither here nor there. Pacman handles dependencies for you so long as you haven't done something to break pacman (e.g., partial upgrades). This is why I was asking how you initially installed rocm-opencl-runtime. You said you "finally" got it installed, which implies it was difficult to do so. Typing `pacman -S rocm-opencl-runtime` should not be difficult - so I gather you infact did something else. That something else is what we'd need to know about. Why / how was it difficult to get this package installed? What steps did you end up taking?

EDIT: however, as seth notes in the other thread [and now below], that lib file is packaged under /opt/ ... I'm not sure why it is, but I hadn't noticed this before. If that path isn't properly added to the lib search path you could easily get this error message.

Last edited by Trilby (2023-03-13 14:53:57)

seth · 2023-03-13 14:02:55

seth on your other soon to be dustbinned thread wrote:

pacman -Qikk hsakmt-roct
stat /opt/rocm/lib/libhsakmt.so.1
Might be an issue w/ $LD_LIBRARY_PATH

V1del · 2023-03-13 14:16:21

FWIW Trilby reported this thread and you reported the other now and I judged the problem scopes to be sufficiently distinct as to not do a corrective action in either direction.

To avoid further confusion and as this one contains more info on the current issue, I'll dustbin the other one.

nixIT · 2023-03-13 19:40:06

Trilby wrote:

You posted the exact same error message from the same command in both threads. That seems related to me.
Anyhow, that's neither here nor there. Pacman handles dependencies for you so long as you haven't done something to break pacman (e.g., partial upgrades). This is why I was asking how you initially installed rocm-opencl-runtime. You said you "finally" got it installed, which implies it was difficult to do so. Typing `pacman -S rocm-opencl-runtime` should not be difficult - so I gather you infact did something else. That something else is what we'd need to know about. Why / how was it difficult to get this package installed? What steps did you end up taking?
EDIT: however, as seth notes in the other thread [and now below], that lib file is packaged under /opt/ ... I'm not sure why it is, but I hadn't noticed this before. If that path isn't properly added to the lib search path you could easily get this error message.

I apologize for the duplicate, and thanx to all for dustbinning the old one.

I was "finally" able to get rocm-opencl-runtime to install by also installing:

hsa-rocr
rocm-device-libs

it would not install unless these were install, and I would have thought they would have been dependencies and been automatically installed. I was mistaken as I had to manually install them.

if that package is installed in /opt/ (you're unsure why), how would this get added to my lib search path? is that something I would have to manually do? if it was, I did not see a mention of doing so during install.

--nixit

seth · 2023-03-13 20:42:10

I was mistaken as I had to manually install them.

No?
rocm-device-libs is a hard dependency for hsa-rocr which is a hard dependency for rocm-opencl-runtime

How are you actually installing these packages??
(Post the exact IO)

Before we start to worry whether or not hsakmt-roct is resolved by rocm-opencl-runtime (and what if not), pelase post the output of the commands in #5

nixIT · 2023-03-14 03:09:35

seth wrote:

I was mistaken as I had to manually install them.
No?
rocm-device-libs is a hard dependency for hsa-rocr which is a hard dependency for rocm-opencl-runtime
How are you actually installing these packages??
(Post the exact IO)
Before we start to worry whether or not hsakmt-roct is resolved by rocm-opencl-runtime (and what if not), pelase post the output of the commands in #5

when I update my system, it's always with

sudo pacman -Syu

I have never forcefully removed a package if it was a dependency of another package.

here is the output of the two commands:

$ pacman -Qikk hsakmt-roct
Name            : hsakmt-roct
Version         : 5.4.3-1
Description     : Radeon Open Compute Thunk Interface
Architecture    : x86_64
URL             : https://rocmdocs.amd.com/en/latest/Installation_Guide/ROCt.html
Licenses        : MIT
Groups          : None
Provides        : None
Depends On      : numactl  pciutils  libdrm
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 277.24 KiB
Packager        : Torsten Keßler <tpkessler@archlinux.org>
Build Date      : Wed Feb 8 14:11:32 2023
Install Date    : Sun Feb 12 23:19:20 2023
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

warning: hsakmt-roct: /opt/rocm (File type mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmt.h (Modification time mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmt.h (Size mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmt.h (MD5 checksum mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmt.h (SHA256 checksum mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmttypes.h (Modification time mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmttypes.h (Size mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmttypes.h (MD5 checksum mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmttypes.h (SHA256 checksum mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmt/hsakmt.h (Modification time mismatch)
warning: hsakmt-roct: /opt/rocm/include/hsakmt/hsakmttypes.h (Modification time mismatch)
warning: hsakmt-roct: /opt/rocm/lib/libhsakmt.so (No such file or directory)
warning: hsakmt-roct: /opt/rocm/lib/libhsakmt.so.1 (No such file or directory)
warning: hsakmt-roct: /opt/rocm/lib/libhsakmt.so.1.0.6 (No such file or directory)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmt-config-version.cmake (Modification time mismatch)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmt-config-version.cmake (Size mismatch)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmt-config-version.cmake (MD5 checksum mismatch)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmt-config-version.cmake (SHA256 checksum mismatch)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmt-config.cmake (Modification time mismatch)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmtTargets-none.cmake (No such file or directory)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmtTargets.cmake (Modification time mismatch)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmtTargets.cmake (Size mismatch)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmtTargets.cmake (MD5 checksum mismatch)
warning: hsakmt-roct: /opt/rocm/lib/cmake/hsakmt/hsakmtTargets.cmake (SHA256 checksum mismatch)
warning: hsakmt-roct: /opt/rocm/share/doc/hsakmt/LICENSE.md (Modification time mismatch)
warning: hsakmt-roct: /opt/rocm/share/pkgconfig/libhsakmt.pc (Modification time mismatch)
warning: hsakmt-roct: /opt/rocm/share/pkgconfig/libhsakmt.pc (Size mismatch)
warning: hsakmt-roct: /opt/rocm/share/pkgconfig/libhsakmt.pc (MD5 checksum mismatch)
warning: hsakmt-roct: /opt/rocm/share/pkgconfig/libhsakmt.pc (SHA256 checksum mismatch)
hsakmt-roct: 32 total files, 14 altered files

here is what I get when I try to install rocm-opencl-runtime

$ sudo pacman -S rocm-opencl-runtime
[sudo] password for nixit: 
resolving dependencies...
looking for conflicting packages...
:: rocm-opencl-runtime and opencl-amd are in conflict. Remove opencl-amd? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'hsa-rocr' required by rocm-opencl-runtime
:: removing opencl-amd breaks dependency 'rocm-device-libs' required by comgr

if I also add hsa-rocr and rocm-device-libs to my pacman -S line, then it will install.

I am curious as to why I get the above if hsa-rocr and rocm-device-libs are hard dependencies.

I appreciate your help with this, as I'd love to find an answer.

--nixit

seth · 2023-03-14 05:24:09

here is the output of the two commands:

Obviously the package is massively corrupted?

here is what I get when I try to install rocm-opencl-runtime

Your problem is https://aur.archlinux.org/packages/opencl-amd and for some reason https://archlinux.org/packages/communit … /hsa-rocr/ cannot be resolved, but is in community so either your mirrot is broken or your pacman database got corrupted by maybe whatever corrupted hsakmt-roct or your using some shady 3rd party repo.

Please post your entire pacman log.

Lone_Wolf · 2023-03-14 13:03:39

I expect the issue is not corruption of the db, but conflicts between rocm packages (including opencl-amd) installed from aur or a 3rd party repo and the new versions from community .

Pleaase post /etc/pacman.conf AND pacman log .

nixIT · 2023-03-14 14:24:40

@lone_wolf, thank you for your help.

pacman.conf

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#NoProgressBar
CheckSpace
#VerbosePkgLists
ParallelDownloads = 5

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

#[testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

#[community-testing]
#Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

my pacman.log is too long to fit here, how do I post it?

nixIT · 2023-03-14 14:28:06

seth wrote:

here is the output of the two commands:
Obviously the package is massively corrupted?
here is what I get when I try to install rocm-opencl-runtime
Your problem is https://aur.archlinux.org/packages/opencl-amd and for some reason https://archlinux.org/packages/communit … /hsa-rocr/ cannot be resolved, but is in community so either your mirrot is broken or your pacman database got corrupted by maybe whatever corrupted hsakmt-roct or your using some shady 3rd party repo.
Please post your entire pacman log.

thank you for your help!
I don't use (to my knowledge) any shady 3rd party repos, and just stick with what is in core, community, extra, multilib and aur.

dumb question, how can I post my log, when I tried to put it in code snippets, the message exceeded the limit.

--nixit

V1del · 2023-03-14 14:30:53

https://wiki.archlinux.org/title/List_o … n_services

nixIT · 2023-03-14 14:46:30

V1del wrote:

https://wiki.archlinux.org/title/List_o … n_services

thank you, I tried 0x0.st and here is the results:

$ curl -F 'file=@-' 0x0.st < /var/log/pacman.log
curl: (52) Empty reply from server
$ cat /var/log/pacman.log | curl -F 'file=@-' 0x0.st
curl: (52) Empty reply from server

first time doing this, not sure what I'm missing.

EDIT:
hows this:

https://0x0.st/s/W11fgiHaepTt0dFX1osixA/H--j.log

Last edited by nixIT (2023-03-14 14:49:53)

seth · 2023-03-14 14:50:14

Edit: OP figured a way.
The log might be quota'd

tail -8192 /var/log/pacman.log | curl -F 'file=@-' 0x0.st

Last edited by seth (2023-03-14 14:51:40)

seth · 2023-03-14 15:25:57

You're *very* frequently running "pacman -Syyu" and while this would not damage eg. the hsakmt-roct package, it might be the cause for the hsa-rocr resolution issue - though

[2023-02-12T23:17:36-0500] [PACMAN] Running 'pacman -S rocm-opencl-runtime'
[2023-02-12T23:18:45-0500] [PACMAN] Running 'pacman -S hsa-rocr'
[2023-02-12T23:19:13-0500] [PACMAN] Running 'pacman -S rocm-opencl-runtime hsa-rocr rocm-device-libs'
[2023-02-12T23:19:20-0500] [ALPM] transaction started
[2023-02-12T23:19:20-0500] [ALPM] removed opencl-amd (1:5.4.3-1)
[2023-02-12T23:19:20-0500] [ALPM] installed hsakmt-roct (5.4.3-1)
[2023-02-12T23:19:20-0500] [ALPM] installed rocm-device-libs (5.4.3-1)
[2023-02-12T23:19:20-0500] [ALPM] installed comgr (5.4.3-1)
[2023-02-12T23:19:20-0500] [ALPM] installed hsa-rocr (5.4.3-1)
[2023-02-12T23:19:20-0500] [ALPM] installed rocm-opencl-runtime (5.4.3-1)
[2023-02-12T23:19:20-0500] [ALPM] transaction completed
[2023-02-12T23:19:20-0500] [ALPM] running '30-systemd-update.hook'...
[2023-02-12T23:20:19-0500] [PACMAN] Running 'pacman -Rsn opencl-amd'
[2023-02-13T11:10:01-0500] [PACMAN] Running 'pacman -Syyu'

you installed it ~1 month ago before

[2023-02-15T22:57:36-0500] [PACMAN] Running 'pacman -U --config /etc/pacman.conf -- /home/drave/.cache/yay/opencl-amd/opencl-amd-1:5.4.3-1-x86_64.pkg.tar.zst'
[2023-02-15T23:01:59-0500] [PACMAN] Running 'pacman -Rdd rocm-opencl-runtime hsa-rocr rocm-device-libs'
[2023-02-15T23:02:00-0500] [ALPM] transaction started
[2023-02-15T23:02:00-0500] [ALPM] removed rocm-opencl-runtime (5.4.3-1)
[2023-02-15T23:02:00-0500] [ALPM] removed hsa-rocr (5.4.3-1)
[2023-02-15T23:02:00-0500] [ALPM] removed rocm-device-libs (5.4.3-1)
[2023-02-15T23:02:00-0500] [ALPM] transaction completed
[2023-02-15T23:02:00-0500] [ALPM] running '30-systemd-update.hook'...
[2023-02-15T23:02:11-0500] [PACMAN] Running 'pacman -U --noconfirm --config /etc/pacman.conf -- /home/drave/.cache/yay/opencl-amd/opencl-amd-1:5.4.3-1-x86_64.pkg.tar.zst'
[2023-02-15T23:04:02-0500] [PACMAN] Running 'pacman -U --noconfirm --config /etc/pacman.conf -- /home/drave/.cache/yay/opencl-amd/opencl-amd-1:5.4.3-1-x86_64.pkg.tar.zst'
[2023-02-15T23:04:02-0500] [ALPM] transaction started

you removed it again (and then recently installed and removed it again in a flurry, starting *before* this thread

[2023-03-12T12:29:05-0400] [PACMAN] Running 'pacman -S rocm-opencl-runtime'
[2023-03-12T12:30:14-0400] [PACMAN] Running 'pacman -S rocm-opencl-runtime hsa-rocr'
[2023-03-12T12:31:29-0400] [PACMAN] Running 'pacman -S rocm-opencl-runtime hsa-rocr rocm-device-libs'
[2023-03-12T12:31:33-0400] [ALPM] transaction started
[2023-03-12T12:31:34-0400] [ALPM] removed opencl-amd (1:5.4.3-2)
[2023-03-12T12:31:34-0400] [ALPM] installed rocm-device-libs (5.4.3-1)
[2023-03-12T12:31:34-0400] [ALPM] installed hsa-rocr (5.4.3-1)
[2023-03-12T12:31:34-0400] [ALPM] installed rocm-opencl-runtime (5.4.3-1)
[2023-03-12T12:31:34-0400] [ALPM] transaction completed
[2023-03-12T12:31:34-0400] [ALPM] running '30-systemd-update.hook'...

The shady part in the equation is ///obviously/// "yay".

Finally: nothing of this can explain what happened to hsakmt-roct - reinstall the package to sanitize it to deal w/ your original problem.
Stop casually using pacman -Syyu and if the resolution issues actually came from a "yay" invocation, maybe try pacman.

nixIT · 2023-03-14 16:20:40

thank you for looking and explaining, I am trying to understand what this means.
I use pacman to install from normal repos, and only use yay for aur, which I know is frowned upon since it's a "helper".

I will stop using -Syyu in pacman, and instead use -Syu, correct? I guess the double y was from years ago when I started using arch (mid 2000's) and it's just carried over.

the constant install/uninstall was trying to get things to work with davinci resolve, hence why there is so many install/uninstall.

I currently have opencl-amd installed, removed rocm-opencl-runtime, again to see if I can get DR to open and not crash.

in your opinion what should be done to get this fixed? I'm all for doing it, just now sure the correct way to begin, without uninstalling opencl-amd and installing rocm-opencl-runtime... or buy an nvidia card because it "just works" with davinci resolve.

I am open, and again, THANK YOU for the help.

--nixit

seth · 2023-03-14 16:34:25

instead use -Syu

"correct"

I can't really tell you what your best approach to DVR is, but the error in the OP is because hsakmt-roct is corrupted.
If you've not yet successfully tried rocm-opencl-runtime, I'd fix that by re-installing the package and try rocm-opencl-runtime (again)

According to https://wiki.archlinux.org/title/DaVinci_Resolve your GPU generation will matter, so if you don't know what hat is, post the output of

lspci

nixIT · 2023-03-14 17:40:10

hope this is enough:

$ lspci  -v -s  $(lspci | grep ' VGA ' | cut -d" " -f 1)
0e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] (rev c5) (prog-if 00 [VGA controller])
	Subsystem: ASRock Incorporation Device 5210
	Flags: bus master, fast devsel, latency 0, IRQ 93
	Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Memory at e0000000 (64-bit, prefetchable) [size=2M]
	I/O ports at e000 [size=256]
	Memory at fcc00000 (32-bit, non-prefetchable) [size=1M]
	Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
libkmod: kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 1: ignoring bad line starting with 'options'
libkmod: kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 2: ignoring bad line starting with 'options'
lspci: Unable to load libkmod resources: error -2

interesting I have an unable to load libkmod resource error message. oy vey.

I would love to give rocm-opencl-runtime a legitimate shot, how would you recommend I try re-installing it instead of my opencl-amd, to get it installed properly?

thank you again @seth, you've been an incredible help.

nixIT · 2023-03-14 20:00:56

in trying to get rocm-opencl-runtime installed again, here is what I did:

$ sudo pacman -Rsn opencl-amd
[sudo] password for nixit: 
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing opencl-amd breaks dependency 'rocm-device-libs' required by comgr
:: removing opencl-amd breaks dependency 'opencl-driver' required by davinci-resolve-studio
$ sudo pacman -Rsn comgr
checking dependencies...

Packages (1) comgr-5.4.3-1

Total Removed Size:  149.86 MiB

:: Do you want to remove these packages? [Y/n] y
:: Processing package changes...
(1/1) removing comgr                               [######################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
$ sudo pacman -S rocm-opencl-runtime
resolving dependencies...
looking for conflicting packages...
:: rocm-opencl-runtime and opencl-amd are in conflict. Remove opencl-amd? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'hsa-rocr' required by rocm-opencl-runtime
:: unable to satisfy dependency 'rocm-device-libs' required by comgr

even though comgr is not installed, pacman still thinks it is. ugg my system is fubar.

I am not sure how to fix this short of wiping my system and re-installing (uggg).

--nixit

seth · 2023-03-14 20:26:19

You've a Navi chip, so according to the wiki, rocm-opencl-runtime is the preferred opencl driver for davinci resolve.

pacman -Qikk comgr

In doubt you can just "pacman -Rdd opencl-amd" and then install "pacman -S rocm-opencl-runtime"
You'll still have to re-install hsakmt-roct to sanitize that package.

On an unrelated note, "/etc/modprobe.d/alsa-base.conf" seems to include some garbage.

ugg my system is fubar.

"fu", seems so - "bar" we shall see.

nixIT · 2023-03-14 22:00:27

seth wrote:

You've a Navi chip, so according to the wiki, rocm-opencl-runtime is the preferred opencl driver for davinci resolve.
pacman -Qikk comgr
In doubt you can just "pacman -Rdd opencl-amd" and then install "pacman -S rocm-opencl-runtime"
You'll still have to re-install hsakmt-roct to sanitize that package.
On an unrelated note, "/etc/modprobe.d/alsa-base.conf" seems to include some garbage.
ugg my system is fubar.
"fu", seems so - "bar" we shall see.

thanx! you have been a huge help... here is what I literally just performed:

reinstalled comgr and then pacman -Qikk

$ sudo pacman -S comgr
resolving dependencies...
looking for conflicting packages...

Packages (1) comgr-5.4.3-1

Total Download Size:    40.23 MiB
Total Installed Size:  149.86 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 comgr-5.4.3-1-x86_64   40.2 MiB  21.2 MiB/s 00:02 [######################] 100%
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Processing package changes...
(1/1) installing comgr                             [######################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

$ sudo pacman -Qikk comgr
Name            : comgr
Version         : 5.4.3-1
Description     : Compiler support library for ROCm LLVM
Architecture    : x86_64
URL             : https://github.com/RadeonOpenCompute/ROCm-CompilerSupport
Licenses        : custom:NCSAOSL
Groups          : None
Provides        : None
Depends On      : rocm-device-libs
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 149.86 MiB
Packager        : Torsten Keßler <tpkessler@archlinux.org>
Build Date      : Wed Feb 8 14:16:36 2023
Install Date    : Tue Mar 14 17:52:20 2023
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

comgr: 27 total files, 0 altered files

removed opencl-amd

$ sudo pacman -Rdd opencl-amd

Packages (1) opencl-amd-1:5.4.3-2

Total Removed Size:  262.48 MiB

:: Do you want to remove these packages? [Y/n] y
:: Processing package changes...
(1/1) removing opencl-amd                          [######################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

installed rocm-opencl-runtime

$ sudo pacman -S rocm-opencl-runtime
resolving dependencies...
looking for conflicting packages...

Packages (3) hsa-rocr-5.4.3-1  rocm-device-libs-5.4.3-1
             rocm-opencl-runtime-5.4.3-1

Total Download Size:   1.71 MiB
Total Installed Size:  9.00 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 rocm-device-libs...   551.4 KiB  2.02 MiB/s 00:00 [######################] 100%
 rocm-opencl-runt...   650.0 KiB  1912 KiB/s 00:00 [######################] 100%
 hsa-rocr-5.4.3-1...   546.5 KiB  1477 KiB/s 00:00 [######################] 100%
 Total (3/3)          1747.9 KiB  4.06 MiB/s 00:00 [######################] 100%
(3/3) checking keys in keyring                     [######################] 100%
(3/3) checking package integrity                   [######################] 100%
(3/3) loading package files                        [######################] 100%
(3/3) checking for file conflicts                  [######################] 100%
(3/3) checking available disk space                [######################] 100%
:: Processing package changes...
(1/3) installing rocm-device-libs                  [######################] 100%
(2/3) installing hsa-rocr                          [######################] 100%
(3/3) installing rocm-opencl-runtime               [######################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

re-installed hsakmt-roct

$ sudo pacman -S hsakmt-roct
warning: hsakmt-roct-5.4.3-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) hsakmt-roct-5.4.3-1

Total Download Size:   0.08 MiB
Total Installed Size:  0.27 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 hsakmt-roct-5.4....    80.9 KiB   378 KiB/s 00:00 [######################] 100%
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
warning: could not get file information for opt/rocm/include/hsakmt.h
warning: could not get file information for opt/rocm/include/hsakmt/
warning: could not get file information for opt/rocm/include/hsakmt/hsakmt.h
warning: could not get file information for opt/rocm/include/hsakmt/hsakmttypes.h
warning: could not get file information for opt/rocm/include/hsakmttypes.h
warning: could not get file information for opt/rocm/lib/cmake/hsakmt/
warning: could not get file information for opt/rocm/lib/cmake/hsakmt/hsakmt-config-version.cmake
warning: could not get file information for opt/rocm/lib/cmake/hsakmt/hsakmt-config.cmake
warning: could not get file information for opt/rocm/lib/cmake/hsakmt/hsakmtTargets-none.cmake
warning: could not get file information for opt/rocm/lib/cmake/hsakmt/hsakmtTargets.cmake
warning: could not get file information for opt/rocm/lib/libhsakmt.so
warning: could not get file information for opt/rocm/lib/libhsakmt.so.1
warning: could not get file information for opt/rocm/lib/libhsakmt.so.1.0.6
warning: could not get file information for opt/rocm/share/doc/hsakmt/
warning: could not get file information for opt/rocm/share/doc/hsakmt/LICENSE.md
warning: could not get file information for opt/rocm/share/pkgconfig/
warning: could not get file information for opt/rocm/share/pkgconfig/libhsakmt.pc
:: Processing package changes...
(1/1) reinstalling hsakmt-roct                     [######################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

not sure about those warnings.

should this take care of it? is there anything else I need to do for this?

now about my /etc/modprobe.d/alsa-base.conf? what garbage are you referring to?

thank you again @seth

cheers,
--nixit

seth · 2023-03-14 22:05:30

Make sure that

pacman -Qkk hsakmt-roct

no longer reports errors and see whether you can run clinfo now.

what garbage are you referring to?

libkmod: kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 1: ignoring bad line starting with 'options'
libkmod: kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 2: ignoring bad line starting with 'options'

Post the file.

nixIT · 2023-03-14 22:38:04

seth wrote:

Make sure that
pacman -Qkk hsakmt-roct
no longer reports errors and see whether you can run clinfo now.
what garbage are you referring to?
libkmod: kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 1: ignoring bad line starting with 'options'
libkmod: kmod_config_parse: /etc/modprobe.d/alsa-base.conf line 2: ignoring bad line starting with 'options'
Post the file.

I did not notice any errors in clinfo. thank you.

/etc/modprobe.d/alsa-conf

    options snd_hda_intel=0
    options snd_usb_audio=-2
    options bt87x index=-2
    options cx88_alsa index=-2
    options saa7134-alsa index=-2
    options snd-atiixp-modem index=-2
    options snd-intel8x0m index=-2
    options snd-via82xx-modem index=-2
    options snd-usb-caiaq index=-2
    options snd-usb-ua101 index=-2
    options snd-usb-us122l index=-2
    options snd-usb-usx2y index=-2
    options snd-pcsp index=-2
    options snd-usb-audio index=-2

this was done b/c I have a scarlet 2i2 connected to my audio recording booth. it may no longer be need, it was what I originally had to do in the early 2010's to get it working properly.

Arch Linux

#1 2023-03-12 21:12:48

[SOLVED] missing libhsakmt.so

#2 2023-03-12 21:15:40

Re: [SOLVED] missing libhsakmt.so

#3 2023-03-13 02:32:45

Re: [SOLVED] missing libhsakmt.so

#4 2023-03-13 13:48:21

Re: [SOLVED] missing libhsakmt.so

#5 2023-03-13 14:02:55

Re: [SOLVED] missing libhsakmt.so

#6 2023-03-13 14:16:21

Re: [SOLVED] missing libhsakmt.so

#7 2023-03-13 19:40:06

Re: [SOLVED] missing libhsakmt.so

#8 2023-03-13 20:42:10

Re: [SOLVED] missing libhsakmt.so

#9 2023-03-14 03:09:35

Re: [SOLVED] missing libhsakmt.so

#10 2023-03-14 05:24:09

Re: [SOLVED] missing libhsakmt.so

#11 2023-03-14 13:03:39

Re: [SOLVED] missing libhsakmt.so

#12 2023-03-14 14:24:40

Re: [SOLVED] missing libhsakmt.so

#13 2023-03-14 14:28:06

Re: [SOLVED] missing libhsakmt.so

#14 2023-03-14 14:30:53

Re: [SOLVED] missing libhsakmt.so

#15 2023-03-14 14:46:30

Re: [SOLVED] missing libhsakmt.so

#16 2023-03-14 14:50:14

Re: [SOLVED] missing libhsakmt.so

#17 2023-03-14 15:25:57

Re: [SOLVED] missing libhsakmt.so

#18 2023-03-14 16:20:40

Re: [SOLVED] missing libhsakmt.so

#19 2023-03-14 16:34:25

Re: [SOLVED] missing libhsakmt.so

#20 2023-03-14 17:40:10

Re: [SOLVED] missing libhsakmt.so

#21 2023-03-14 20:00:56

Re: [SOLVED] missing libhsakmt.so

#22 2023-03-14 20:26:19

Re: [SOLVED] missing libhsakmt.so

#23 2023-03-14 22:00:27

Re: [SOLVED] missing libhsakmt.so

#24 2023-03-14 22:05:30

Re: [SOLVED] missing libhsakmt.so

#25 2023-03-14 22:38:04

Re: [SOLVED] missing libhsakmt.so

Board footer