Microarchitecture support?

Support
1

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:

NAME=“OpenMandriva Lx”
VERSION=“25.06 (ROME) Rolling”
VERSION_ID=“25.06”
PRETTY_NAME=“OpenMandriva Lx 25.06 (ROME) Rolling”
BUILD_ID=“20250605.11”

Kde vault fail to create. So i ran cryfs from the command line and it crashed with illegal instruction. I was wandering what microarchitecture “level” do you support? Or the oldest cpu supported? I have Intel Pentium Dual CPU T3400, its my current play around computer. Thanks.

Download options:
ROME Plasma6 slim x86_64 (im running this one)

ROME Plasma5 slim x86_64
ROME Plasma5 slim AMD CPU (newer than 2017)

2

Huh? What the heck to you mean by micro-architecture? I suspect you would not have been able to install OMLx ROME on your computer if it were not x86_64. That would be the architecture.

As far as making a statement on what is the oldest cpu supported how would we answer that given we do not have access to every old hardware ever made? As a small group we only have access to the hardware that OM contributors own. Intel Pentium Dual CPU T3400 is what 2008 or older? It probably should work just fine if slow due to it’s age.

OK, that amounts to saying “It’s broke”, and we can not fix “It’s broke”. Please start a new thread about your specific issue with a descriptive title and enough information so someone could help you. You can find more about providing information for support requests here:

How to get better results when posting about problems

I do not mean to be mean or snarky, in fact I want to help, but we actually do need information to help users with problems.

FWIW: I do suspect KDE Vault is broken in OMLx. But no one can do anything without something to work on like Konsole output or logs. And for users please post all the output not the part you believe is important. You can’t know what someone else might need to know to help.

3

The x86_64 images are supposed to work on any x86_64 device without requiring any specific microarchitecture (that’s what we have the znver1 images for…)
But of course most testing happens on higher end machines, so it’s not too surprising if something that uses an AVX instruction goes unnoticed. Unfortunately a few projects are “good” at knowing “better” than the packager what the preferred compiler flags are.
cryfs uses cryptopp, which does some magic to get avx/avx2/… support into it. Chances are we need to adjust the flags on cryptopp and rebuild.

4

Microarchitecture_levels
[x86-64 - Wikipedia]

5

Sounds like you know what the problem probably is, would you like the stack trace any way?

6

Yes, would be good, cryptopp being at the core of it is an educated guess, but not (yet) a proven fact.

7

Thanks I was forgetting about that. My mistake.

8

Back to this. First again thanks to @TheKingsIdiot for educating me on this.

Restricting the discussion for now to x86_64. So by Microarchitecture we are referring to this:

$ /lib64/ld-linux-x86-64.so.2 --help
...
  x86-64-v4
  x86-64-v3 (supported, searched)
  x86-64-v2 (supported, searched)

Meaning v4 not supported on my laptop, v3 and v2 are. Does this also have to do with which kernel flags are enabled in the kernel in use? And based on the original question could there be things needed on older x86_64 hardware that are not enabled? And apparently there is some software that has flags that need to be enabled, like cryptopp, something else I did not know.

9

bero suggested, it could be a compiler flag for a crypto lib.

10

OK compiler flags and kernel flags. I am vaguely aware of compiler flags more so kernel flags. But as user level knowledge it is knowing words more that understanding what they mean. Anyway learned a little bit more.

11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.