16.0 doesn't support my PC: What are others like me doing?

[Fraser_Bell]

Yes, I did try searching the forums for the answer, nothing similar shows up in my search.

I was preparing to install openSUSE Leap 16.0 on my PC, only to discover it does not support my architecture. After all these years of using openSUSE, I am extremely unhappy I now have to search for a replacement distro. (Note that “extremely unhappy” is an understatement.)

Can anyone give me hints on what distro(s) most of the other users who have to leave openSUSE for this reason are choosing?

And, no, I cannot buy a new PC just to run openSUSE.

[malcolmlewis]

Hi, switch to Slowroll or Tumbleweed

[deano_ferrari]

Hi Gerry

Can you tell us more about the hardware in question?

inxi -GMSaz

TW/SR might still be an option for you? I’m using the latter happily on my old Dell laptop.

[Fraser_Bell]

Oh, TW still allows ?? >>

  x86-64-v3 (supported, searched)
  x86-64-v2 (supported, searched)

Any idea how long that will continue?
Thanks, Malcolm

[Fraser_Bell]

StudioAsus01:~ # /lib64/ld-linux-x86-64.so.2 --help
Usage: /lib64/ld-linux-x86-64.so.2 [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]
You have invoked 'ld.so', the program interpreter for dynamically-linked
ELF programs.  Usually, the program interpreter is invoked automatically
when a dynamically-linked executable is started.

You may invoke the program interpreter program directly from the command
line to load and run an ELF executable file; this is like executing that
file itself, but always uses the program interpreter you invoked,
instead of the program interpreter specified in the executable file you
run.  Invoking the program interpreter directly provides access to
additional diagnostics, and changing the dynamic linker behavior without
setting environment variables (which would be inherited by subprocesses).

  --list                list all dependencies and how they are resolved
  --verify              verify that given object really is a dynamically linked
                        object we can handle
  --inhibit-cache       Do not use /etc/ld.so.cache
  --library-path PATH   use given PATH instead of content of the environment
                        variable LD_LIBRARY_PATH
  --glibc-hwcaps-prepend LIST
                        search glibc-hwcaps subdirectories in LIST
  --glibc-hwcaps-mask LIST
                        only search built-in subdirectories if in LIST
  --inhibit-rpath LIST  ignore RUNPATH and RPATH information in object names
                        in LIST
  --audit LIST          use objects named in LIST as auditors
  --preload LIST        preload objects named in LIST
  --argv0 STRING        set argv[0] to STRING before running
  --list-tunables       list all tunables with minimum and maximum values
  --list-diagnostics    list diagnostics information
  --help                display this help and exit
  --version             output version information and exit

This program interpreter self-identifies as: /lib64/ld-linux-x86-64.so.2

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)
StudioAsus01:~ # 

No v4 support.

lscpu | grep sse4_2 || echo "Your CPU is not compatible with Leap 16.0"

[malcolmlewis]

V3 will run Leap 16.0

[deano_ferrari]

Ok, so your hardware is supported by Leap 16 then.

https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/16.0/release-notes-leap-160_color_en.pdf?

[Fraser_Bell]

Oh? Hmm, okay. Thank you.

And, I could only mark one of you as Solution, though you both provide it.

Reading back, I see if I had been able to read a little more accurately, I would have known. I was focusing on the “4”, missed the 4_2, which threw me. And the echo in the above command confused me. Duh.

Guess I am getting old a lot faster than you and Malcolm.

[deano_ferrari]

All good. Let us know which way you decided to jump when the time comes.

Just a note if you do choose Leap 16: For graphical package management there’s Myrlyn , (developed by Stefan Hundhammer), which evolved from YaST’s package management work, and Cockpit (web-based GUI) for a lot of the general system management tasks.

[Fraser_Bell]

Guess the grey matter got in my way last night. I recall I ran the /lib64/ld-linux-x86-64.so.2 --help command a few months back and read it correctly at the time, determined my Desktop PC was compatible. I have v3, and a user only needs up to v2 to run 16.0.

But, the OP question and the offered solutions are still valid, because I also ran the command back then on my two laptops to discover they are too old and won’t run 16.0.

So, thank you for the alternate solutions.

Also, someone else might find this thread usefull.

[tckosvic]

I had an old lenovo thinkpad r500 with leap 15.6 from about 2007 in a dual boot with windows xp. Leap 16.0 would not install based upon byte size-- 32 vs 64.

But tumbleweed did install. It now runs tumbleweed in a dual boot with windows xp.

tom kosvic