Query about upgrading to Leap 16

English Install/Boot/Login
,
1

Hi there. In the documentation from the opensuse.org home page, it used to link to a guide/ebook on how to upgrade the system from the command line. I thought I saved the link but sadly I didn’t. Now when I follow the documentation link from the home page, the ebook is no longer there. It now links to a Leap 16 guide but that guide doesn’t have upgrade instructions and prerequisites like the ebook.
openSUSE Documentation

I’ve heard about a migration tool. Is this the preferred way of upgrading? I would have liked to learn using zypper but I’m not against using the migration tool. Could someone please advise me on the best way forward?

I saw this tutorial on upgrading with the migration tool, but if you read the comments, users are complaining it doesn’t upgrade, and the author is not responding. So I’m wary of using this method. Here’s the link:
How to Upgrade to openSUSE Leap 16 from Leap 15.6

On this page I’m about to link: I’m finding it hard to follow along. It speaks of changes in the Leap 16 repos from older versions, but I’m not sure what I need to alter or modify for zypper dup to run smoothly. It also has this line at the end:

" Adjust your repository definitions in /etc/zypp/repos.d/ to match the Leap 16.0 repository definitions from openSUSE-repos."

Does that mean I should copy and paste that github page into /etc/zypp/repos.d?

And finally. I read something very worrying. It said:
Leap 16.0 will no longer run on machines that do not support x86_64-v2 .

My machine that runs Leap is from 2013. It’s 64 bit but I have no idea if it’s v2. I highly doubt it. Does this mean my machine is not compatible with Leap 16? Is it a risk upgrading?

If there are responses, I may take a while to reply so please bare with me.
Thanks

2

I have a laptop, purchased in 2010. It is v2. You will probably be okay.

To upgrade, I just deleted all repos except “repo-oss” (Main repository) and packman. I made sure those two were using $releasever in their definitions. Then I did:

zypper --releasever=16.0 dup

This upgraded without a problem. I even upgraded a couple of 15.5 systems that way.

1 Like
3

Oh that’s good to know!

When you say “deleted all repos”, do you mean delete or disable? And after you installed Leap 16, did you have to add back the repos, re-enable the repos or the installation automatically did that for you?
If you had to re enable repos manually and the installation didn’t do it for you, is this a straight forward process? is it best I keep a note of all the names of repos I delete in order to add them back after I install Leap 16?

One last thing. I see repo-oss (Main repository), but I don’t see packman. Is packman a repo you previously added or should it be added by default on Leap?

Thanks a lot… I’m really a Linux noob so I appreciate your help :slight_smile:

4

What I actually did was:

cd /etc/zypp
mv repos.d repos.d.old
mkdir repos.d
cd repos.d
cp -p ../repos.d.old/{repo-oss,packman}.repo .

Note, however, that your packman repo (if you have one) might have a different name.

So I started with just the two kept repos, but I retained the old definitions in the “repos.d.old” directory just in case.

2 Likes
5

I have successfully done multiple 15.6 → 16.0 upgrades using opensuse-migration-tool. This takes care of all the changes and performs the upgrade.
You can check the capabilities of your CPU like this:

knurpht@Lenovo-P16:~> ld.so --help | tail -5

Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4 (supported, searched)
  x86-64-v3 (supported, searched)
  x86-64-v2 (supported, searched)
knurpht@Lenovo-P16:~>

As you can see v2 in my case is supported

1 Like
6

Dear @knurpht or others

just out of interest, I tough get

gunnersson@tulicube:~> ld.so --help | tail -5

Subdirectories of glibc-hwcaps directories, in priority order:
  x86-64-v4
  x86-64-v3 (supported, searched)
  x86-64-v2 (supported, searched)
gunnersson@tulicube:~>

Do you know when v4 was introduced, i.e. by which generation of Intel CPU?

7

After 7 & by 11 generally. The Celerons and Pentiums have lagged the Cores. e.g., Gen4 Pentium is only v2, while Gen4 Cores are v3.

1 Like
8

There is also non-oss, although it is disabled by default when one is using repository service (e.g. by installing openSUSE-repos-Leap).

9 
gunnersson@tulicube:~> inxi -C
CPU:
  Info: quad core model: Intel Core i3-9100 bits: 64 type: MCP cache:
    L2: 1024 KiB
  Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800
gunnersson@tulicube:~>

Well yes, somehow “after” 7…

Thank you!

10

According to openSUSE wiki, v4 appears to require instruction AVX512, while according to cpu-world, AVX512 is absent from i3-9100, so must be v3. i3-10100 on cpu-world.com also lacks AVX512, while i5-11400 has it, so it seems Gen11 is probably minimum v4.

1 Like
11

Thank you very, very much!

Does anyone know if there is any distribution (not necessarily SUSE, openSUSE) out there using v3 or v4, i.e. higher than v2 (used by openSUSE currently now)?

12 
zypper se x86-64-v3
13

@C7NhtpnK I have a Xeon W-2102 from Q3/2017 it’s a v4 Intel® SSE4.2, Intel® AVX, Intel® AVX2, Intel® AVX-512

14

Thanks for the help guys. I’ll get to try upgrading early next week. I hope it’s okay to post back here if I run into any issues. Thanks again.

15

determined_suse_noob

What upgrade method have you decided to try? migration tool or zypper dup releasever

List the exact steps you are to do.

Report your success

thanks

16

Hi… I decided to go with the migration tool. I’ll follow the steps here:
How to Upgrade to openSUSE Leap 16 from Leap 15.6

I’ll report back my results after attempting the upgrade.

1 Like
17

I successfully used the migration tool on several systems.
One addition to the instructions you cite: The tool first runs in non-interactive mode, and if it finds file conflicts it stops itself. If you immediately start it again, it runs interactively, so you can choose what to do about conflicts. Unfortunately, when the tool stops itself it deletes everything it downloaded, so that has to happen again.
All my systems had conflicts with some gstreamer files. In interactive mode I chose to continue. It again downloaded 3+GB and the migration finished OK.

18

Oh, so even though you had conflicts (non-interactive), you ran it again (interactive) and the conflicts didn’t stop the installation from completing?
Thanks for the tips

19

Hi, I would like to upgrade but I’m a little scared about it :slight_smile:
about you say in your comment, it means that if there are no conflicts the tool go ahead without problems?
and, for immediately, you intend run

sudo opensuse-migration-tool

again in few seconds?
and, the site for the instructions
doesn’t say anything about choices about
-switch to selinux
-keep apparmor
-allow 32 bit binary execution
-switch to pipewire
what was your choices?
does somebody suggest choices?
@determined_suse_noob please when you will post your success say something about the choices you made
manythanks

20

No, the migration worked fine in spite of the conflicts, after I got to respond “yes” to “Continue?” I forget the wording about the consequence of the gstreamer conflict, but there was no problem.

1 Like