Hy, read about x64-v2 requirement for Leap 16 and found this:
https://en.opensuse.org/X86-64_microarchitecture_levels
but my machine gives:
inxi -Cx | grep sse4_2
and
lscpu | grep sse4_2
And now? Stay with 15.6? Switch to Debian?
A little lost here…
Get better hardware, switch to Slowroll or Tumbleweed…
Due to frequent problems with graphics in TW I switched to Leap some years ago with good results.
Not going to replace a notebook with 1920 x 1200, needed for productive work.
With all the respect to community and not by any chance offend anyone, as I’m new the Get better hardware advice goes somewhat against the End of 10 project .
I get the switch to Tumbleweed or Slowroll. But for some people like me we just can’t afford even a used more recent machine.
Now from curiosity the commands @suse_rasputin provided, on my end are giving these
inxi -Cx | grep sse4_2
Flags-basic: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
and
lscpu | grep sse4_2
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate ssbd ibpb vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
I’m on Tumbleweed with AMD FX-6300 processor, should I concern from the point if the x64-v2 will ever come on TW too?
Have a nice October to you and the whole community!!!.
@racoonez all due respect, but there are likely many features that can’t be used on newer generation CPU’s at the expense of supporting power hungry old hardware 
Keep an eye out for second hand hardware in your locale?
You should be fine on Tumbleweed, hard to say when something might happen, keep an eye on the Factory Mailing list?
You appear to be on a X64-v3 cpu, so safe for the foreseeable future.
Better check with:
bruno@LT-B:~> ld.so --help |tail
Shared library search path:
(libraries located via /etc/ld.so.cache)
/lib64 (system search path)
/usr/lib64 (system search path)
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched) <<<<<<<<<<<<<<<<<
bruno@LT-B:~>
Windows 11 is marking machines older than about 4 years (some younger depending on how cheap the motherboard is) as incompatible. x86-64-v2 was introduced in 2008, there is a slight difference there.
That some can’t upgrade almost 20 year old hardware doesn’t mean that the whole project should hold back new releases.
Sometimes, the only answer you’ll get is upgrade your hardware. The older it is, the more likely you’re going to hear it.
I think it’s only v2, right?
ld.so --help |tail
Shared library search path:
(libraries located via /etc/ld.so.cache)
/lib64 (system search path)
/usr/lib64 (system search path)
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3
x86-64-v2 (supported, searched)
Yes, “only” v2 so you will be OK with Leap 16 till 2032 or presumably with Tumbleweed at least to that year (assuming that the power supply will be still functional after 20 years…)
haha… I think it will be, I changed it back around in 2016 and it still working and I clean up the case with an air blower every 5-6 months, I’ll think it for the move onto Leap and if it will benefit me Audio wise because I have configured it via the Geekos DAW rt-config package (thankfully to openSUSE/Geekos DAW magicians works nice on that part too). 
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.