Hello,
I need to migrate from 42.2 to 42.3. The system upgrade page talks a lot about live upgrade, and says very little about offline DVD upgrade excepts it cleans up the system. If I get a 42.3 DVD, does it have an upgrade option that I can choose? I am obviously not a super user, and this seems to be a fairly simple approach.
regards – Roger
Yes, it will detect your installed 42.2 and will offer an upgrade option.
If you run into any problems, Roger, you can always come back here for help. Many of us would be pleased to assist.
Thanks very much. Just need to get the DVD and I should be set. Usually SUSE works pretty smoothly, and hopefully I will be upgraded before I know it…
Biggest problem I have is knowing when the release becomes unsupported. I should have figured it out when the periodic updates stopped.
regards – Roger
When nervous about mucking things up, still am occasionally, with enough HD space it was helpful and useful to organize a separate root partition eg 50GB and separate /home.
Then did clean installation of newer version openSUSE using the new / root and /home partitions.
Once knew up and running, changed home, or copied or moved, my essential documents across.
BTW always do back up essential documents.
As found my way around, became more adventurous.
You can also change the repo URL’s “openSUSE_42.2” part to “openSUSE_42.3”, then run
sudo zypper ref
sudo zypper dup
If in doubt, show us your repos first:
zypper lr -d
Should show us this, anyway. It is usually important to only have the main repos enabled until after the upgrade, and some non-standard repos can actually mess you up.
Hello,
Here is the result. I know there is a way to put this in a confined space box with up and down arrows, but it has been a while…
regards – Roger
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+----------------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------+--------
1 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/leap/42.2 |
2 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/non-oss/ |
3 | download.opensuse.org-non-oss_1 | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.2/non-oss/ |
4 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/oss/ |
5 | download.opensuse.org-oss_1 | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.2/oss |
6 | http-opensuse-guide.org-b3334424 | libdvdcss repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/openSUSE_Leap_42.2/ |
7 | http-packman.inode.at-832ba8ed | Packman Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://packman.inode.at/suse/openSUSE_Leap_42.2/ |
8 | openSUSE-42.2-0 | openSUSE-42.2-0 | No | ---- | ---- | 99 | yast2 | cd:///?devices=/dev/disk/by-id/usb-PIONEER_DVD-RW_DVR-109_38089D-0:0 |
9 | repo-debug | openSUSE-Leap-42.2-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.2/repo/oss/ |
10 | repo-debug-non-oss | openSUSE-Leap-42.2-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.2/repo/non-oss/ |
11 | repo-debug-update | openSUSE-Leap-42.2-Update-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.2/oss/ |
12 | repo-debug-update-non-oss | openSUSE-Leap-42.2-Update-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.2/non-oss/ |
13 | repo-source | openSUSE-Leap-42.2-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.2/repo/oss/ |
14 | repo-source-non-oss | openSUSE-Leap-42.2-Source-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.2/repo/non-oss/ |
Please, use CODE tags, the # in the editor, around your output. I’ve editted your post, so you can see the difference.
Thanks, I will remember that. And write it in my Linux book in case I don’t…
Remove the unnecessary repos:
sudo zypper rr 8 9 10 11 12 13 14
Next, use YaST - Software - Repostiries to edit the URLs ( all of them ) and replace 42.2 by 42.3, disable the Packman, libdvdcss repos.
Open a terminal window and do
sudo zypper ref && sudo zypper dup
I’ve tested this procedure last week on a 42.2 → 42.3 upgrade where the nvidia driver was included and ended up with a smoothly running KDE desktop. Afterwards I re-enabled the Packman repo and ran
sudo zypper dup --from Packman\ Repository --allow-vendor-change
and all was back to what the user was used to.
** After the upgrade, never forget, with the user “root”, to execute ‘rcrpmconfigcheck’. **
** Before the upgrade, never forget to execute ‘zypper verify’. **
** Before the upgrade, it pays to check for issues and problems in the systemd journal: ‘journalctl --verify’. **
** Before the upgrade, it pays to check and/or rebuild the “rpm” database. **
The openSUSE Support Database (SDB) has the following information:
As for the live upgrade, it is to be considered a “best effort”: it should work, but it can also fail. It is strongly recommended to make a full backup previous to the undertaking. If the upgrade fails, you can then restore and try again, changing whatever is needed to avoid the previous problem, install fresh, or attempt a live upgrade.
… and, even more important: Before the upgrade, make sure to back up your system.
Upgrade seemed to go seamlessly, but when I did the initial boot I got a fault - Plasma failed to start, could not correctly use OpenGL.2, please check drivers’, and then of course it just stalled. Re-entered using a recovery mode option, so don’t know if that ‘solution’ will remain sticky and I will be able to reboot.
The system is using a Nvidia graphics card and Nvidia drivers. The Nvidia repository was deleted in the install, and my guess is that no Nvidia drivers were loaded as part of the upgrade, and when the system went looking for the nvidia drivers on boot, and couldn’t find them…Just a guess.
I was going to add the nvidia repository, but had a question. I have in the past followed the instructions in: https://en.opensuse.org/SDB:NVIDIA_drivers. I understand adding the repository. The note on Leap 42.3 would indicate I have to go through a process outside of yast - is this accurate?? A little concerned I will put myself in a position I will not be able to recover from…
regards – Roger
Well, the message is clear, isn’t it?
And in recovery mode, OpenGL will not work if nvidia is installed, although it seems that works for you at the moment(?).
The system is using a Nvidia graphics card and Nvidia drivers. The Nvidia repository was deleted in the install, and my guess is that no Nvidia drivers were loaded as part of the upgrade, and when the system went looking for the nvidia drivers on boot, and couldn’t find them…Just a guess.
Actually it should work without the nvidia driver installed.
But I suppose you had it installed before, and it didn’t get updated (and therefore doesn’t work anymore).
Reinstall (or at least uninstall) it, and it should work.
You can use YaST in text mode, or you can also use zypper of course.
Actually you should still be able to boot the old 42.2 kernel (in Advanced Options in the boot menu) where the old driver should still work.
I was going to add the nvidia repository, but had a question. I have in the past followed the instructions in:https://en.opensuse.org/SDB:NVIDIA_drivers. I understand adding the repository. The note on Leap 42.3 would indicate I have to go through a process outside of yast - is this accurate??
Not necessarily. You can also use YaST to install it, but you have to select the matching driver manually then, depending on your graphics card.
Hi,
Thanks for the fast reply. Sadly, I am not knowledgeable enough for it to be obvious. I had to go down to the 2nd recovery option (4th in the list of ‘system’ to choose) before it would work. The first recovery option faulted out just like a standard boot.
I did add the Nvidia repository. When I went to software management the driver packages were listed in blue?? and indicated as installed. I hit accept, but apparently nothing was loaded (because it was already there??). Is there possibly a conflict such that I need to uninstall the drm-kmp-default package ?? I searched for that in the YAST software manager and ‘no results’. Possibly outside the realm of the software manager??
I am just keeping my system up for the moment - unclear I could get it to reboot again… Although I will have to see at some point in time.
regards – Roger
Also, is it possible to change the video driver to something standard that will at least allow boot until this gets resolved?? I realize the performance will not be as good, but being able to boot the system is a useful feature. If I can/should change the driver, where do I go about doing that??
thanks — Roger
I decided to see if there were any upgrades that the system needed, and there were three. The first was drm-kmp-default. I am getting a bit lost in all of this. So now the system is supposedly fully updated, and with the file that was recommended to delete.
sorry for all of the posts…
regard – Roger
That means that a newer version is available, and especially in this case it would be a good idea to update them.
and indicated as installed. I hit accept, but apparently nothing was loaded (because it was already there??).
Yes.
You need to explicitly update them, right-click and choose “Update unconditionally” (although, just update should work as well I suppose)
Is there possibly a conflict such that I need to uninstall the drm-kmp-default package ?? I searched for that in the YAST software manager and ‘no results’. Possibly outside the realm of the software manager??
No.
The nvidia driver packages do indeed not work if drm-kmp-default is installed, but there is a package level conflict anyway.
I.e. if nvidia packages are installed, drm-kmp-default cannot (and vice-versa).
This is only something to consider if you install the driver “the hard way”, using nvidia’s .run download.
Sure, just uninstall all nvidia packages.
But then, the above should already fix it I think.
Using unconditional worked with the software manager, and it provided a notice that drm-kmp-default would be deinstalled. Good news on that front. The packages were successfully uploaded, but the software manager seems to have locked up after installing the first package - it is listed as 100% installed (for the last 15 minutes), the hard drive keeps ticking over (red light), but the software manager will not move on to installing the other 3 packages it downloaded.
I tried the abort, but it is just spinning along, and will not recognize it. Any other options?? I am not sure shutting down the system is possible, but seems my only other option.
regards – Roger