I’m have been testing for the latest 3 hours the update today from RC1 to…(i hope thats final Leap 42.1)
Away is a lot of small annoying problems like HP-lip, KDE crashes and working 32-bit printer drivers etc. This i a different animal(Gecko) compared with RC1. Stabillity OK! I haven’t a crash in that time.
The two first things I notice directly was that my set up with two monitors at different resolutions was working all the way from start:
wow cool
I’m still using 13.2, been looking for an iso of 42.1 gold but I can only find the RC1 iso’s, as I don’t want to redownload the whole OS twice I’ll try and dup from 13.2 to 42.1.
I have a couple of extra repo’s including wolfy’s kde5 and am not sure how the upgrade will go, hopefully I won’t end up with a dead system.
The repos do have 42.1 final already, but there’s no iso available yet (or at least not accessable).
A “zypper dup” from 13.2 should work after changing the repos accordingly.
I have a couple of extra repo’s including wolfy’s kde5 and am not sure how the upgrade will go, hopefully I won’t end up with a dead system.
Well, at least my repo is available for Leap 42.1 too, already.
Haven’t tested it yet though, but feedback would be welcome…
Although, most of that is similar to what is in Leap, so I don’t expect any problems really.
Of course, you should do a “zypper dup” to my repo, and then you probably have to reinstall some KDE4 ones, but it should work from the feedback I got about Tumbleweed.
It might be a good idea now to add some patterns to my repo, but I never got the time to do that.
Help is welcomed with this too…
Some packages are missing still though (nothing critical), because they don’t build at the moment, but the main stuff should be ok.
But anyway, I suppose we should start a new thread about this (my repo).
Drats! upgraded from the beta last week to the RC, logged in and got a big greyish/white screen an oops something went wrong and the system cannot recover message engraved on it with a sad smiley (iirc)
I managed to fix it last week and had the RC running beautifully.
Today, well, today is much the same. here is the sequence of events:
logged out of RC. dropped to terminal alt -ctrl -1
logged in as root
init 3 (don’t ask I just did OK?)
zypper ref; zypper dup
downloaded 900+ packages
sat with the upgrade all the way and watched for error messages. might have been one about unable to find boot/grub map device - something like that
issued init 5 after the usual stuff about running ps to see list of blah blah programs I might want to restart.
got back to graphic log in and logged in only to be met with the message at the top of this post.
Rebooted which I should have done earlier got back to the graphic log in and tried again - me an my test user accounts both produced the same sorry etc screen.
Any thoughts. I wish I could recall how I fixed it last week.
It took a lot of chrooting from another linux distro and installing and re-installing graphic drivers and running grub-mkconfig - o and al that stuff and reinstalling grub everything I could think of and have now forgotten.
That has already been done. I no longer get to the graphical login after I discovered that the nvidia drivers had been uninstalled.
They were duly reinstalled, no errors thrown up.
Now dropped to terminal on reboot.
I had a look at my /etc/default/grub and apart from quiet and showopts there was nothin in the linux line.
I added nomodeset and did the
removed nomodest from linux line - rmembered it was not necessary last week for the proprietary drivers.
After running grub2-mkconfig yada yada rebooted and was not surprised to be still dumped to the command line.
From this command line I read the /var/log/X11. whatever it is log and discovered that the nvidia module(s) are not being loaded.
This is right down near the bottom of the file.
I also ran another command - not given in full here as I am back in front of a working other distro - but involves lspci with a switch and grep searching for 03 and A2- something like that.
Anyway the command reports that the VGA controller is 03 nvidia (again this is not accurate reporting of the actual output but enough to get the drift) and the last line indicated the module was nouveau. So, report of the driver for nvidia is accurate but kernel module is nouveau. What? Are they fighting and nobody is winning?
So my nvidia drivers haven’ taken so to speak.
Might it be an idea to get rid of them and see if nouveau kicks in?
I’d rather not be rid of them but the problem is frustrating.
First I could see the graphical login (lightdm by the way) and now I can’t get back there at all.
The output I saw verified the controller was nvidia.
It also verified that the only entry in the modules line was nouveau.
I had to add this in a new post as I missed the 10 minute edit limit.
Hi wolfi I saw that you build your kf5 packages for leap but I didn’t want to use them for 2 reasons, #1 there is no kde4 for Leap so no need for an extra tweaked kde5, #2 as there is no kde4 there is no reason to use /opt/kf5 and I wanted all of kde5 to go in /usr.
I has some issues with your kf5 13.2 packages not all wore dup-ed to the appropriate 42.1 packages so I had around 20 file conflicts, and the packages that wore not duped wore not removed, going to yast->software->orphaned packages I removed them manually.
The only real issue I had was that the I had no Network after the upgrade, I had a 10 second panic attack then I remembered to check the network in yast->Network Settings it seams that the Network was off, not sure why but it was easy to start Wicked.
I had 1 more issue my Firefox home page about:home is still the old google search page not jonte1’s, could be the old 13.2 Firefox profile.
ps people thinking of upgrading remove nvidia drivers and the nvidia repo’s, use nouveau during the dup-ing as the nvidia kernel is way too old and not compatible with Leap’s, remember to remove old xorg.conf files as nouveau will not start with the old nvidia X config files present.
My solution: uninstall all instances of nvidia rpms - in my case 4 packages. Reboot and restart with nomodeset and level 3 (I was there already!) then install nvidia the hard way.
Now I have my memory back I recall I did the reverse of this last week after the upgrade from Beta to RC
Well, the point of my repo is to have both KDE4 and Plasma5/KF5 applications, so I added the KDE4 related things that are missing in Leap to my repo too. (I hope I haven’t overlooked something)
If you prefer to stay with the standard packages, that’s fine with me though…
I has some issues with your kf5 13.2 packages not all wore dup-ed to the appropriate 42.1 packages so I had around 20 file conflicts, and the packages that wore not duped wore not removed, going to yast->software->orphaned packages I removed them manually.
I do have many KF5 appliciations in my repo that are not even released yet (and therefore are not even in Tumbleweed), those do not get removed if you have them installed already.
Also, the standard KF5 applications packages do not have a ‘5’ appended, so not all will probably be correctly updated. Although at least some of them do obsolete the corresponding xxx5 package. Probably doesn’t make sense to do that for all of them though.
I had 1 more issue my Firefox home page about:home is still the old google search page not jonte1’s, could be the old 13.2 Firefox profile.
Probably.
User settings are normally not modified on upgrades (or fresh installs with reusing /home).
ps people thinking of upgrading remove nvidia drivers and the nvidia repo’s, use nouveau during the dup-ing as the nvidia kernel is way too old and not compatible with Leap’s, remember to remove old xorg.conf files as nouveau will not start with the old nvidia X config files present.
It is always advisable to uninstall the nvidia driver before an upgrade, otherwise strange problems might occur.
But what’s an “nvidia kernel”? Never noticed that they offer their own kernel now too… rotfl!
You probably mean nvidia’s kernel modules, i.e. the kmp packages.
Well, actually a mere reinstallation should help (even of the 13.2 version), as that also recompiles the kernel modules.
It’s still recommended to remove the driver before an upgrade though.
If you have Optimus notebook then you have to deal with things differently and use bumblebee. It is not uncommon for NVIDIA driver not to be ready at release of the OS. Remember that the drivers do not come from openSUSE they come from NVIDIA
yes I noticed you had some packages not available from the standard repo’s, my biggest reason to use the standard was the /opt/kf5 folder OCD won
Probably.
User settings are normally not modified on upgrades (or fresh installs with reusing /home).
after crating a new profile I noticed that LEAP does still come with the old google search it was the opensuse search page that was updated
I prefer about:home as my home page
But what’s an “nvidia kernel”? Never noticed that they offer their own kernel now too… rotfl!
You probably mean nvidia’s kernel modules, i.e. the kmp packages.
Well, actually a mere reinstallation should help (even of the 13.2 version), as that also recompiles the kernel modules.
It’s still recommended to remove the driver before an upgrade though.
Yes the binary kernel modules, doing a dup with the nvidia modules still present will cause issues.
Yes the binary kernel modules, doing a dup with the nvidia modules still present will cause issues.
You mean the “zypper dup” itself doesn’t work?
Do you get conflicts?
Might be because there is no kernel-desktop any more, it has been replaced by kernel-default. The kmp-desktop packages require kernel-desktop though. But “zypper dup” should want to remove them then, no?
what consused said having an extra dir was bugging the hell out of me had ti get rid of it
You mean the “zypper dup” itself doesn’t work?
Do you get conflicts?
Might be because there is no kernel-desktop any more, it has been replaced by kernel-default. The kmp-desktop packages require kernel-desktop though. But “zypper dup” should want to remove them then, no?
no I had no problems I usually install from a usb but I remembered a lot of threads people having issues with the nvidia kernel modules after they dup-ed from 13.1 to 13.2.
My upgrade was semi smooth, I removed the nvidia repo, then removed the nvidia kernel modules, had to remove xorg.conf as nouveau didn’t want to start with the old conf files, then it was just a matter of replacing the 13.2 repo’s with Leap and executing a zypper dup, I did it in run level 3 as wiki suggested.
the only issue I had was the old kde4 and kde5 config files I had some different desktop elements/decorations/icons/color then the default one I just deleted the old config files from my home.
The upgrade wiki was a great source of information https://en.opensuse.org/SDB:System_upgrade#Command_line
except that the Leap update server URL’s wore different I had to add them manually the update URL’s you get executing
# sed -i 's/13\.2/leap\/42\.1/g' /etc/zypp/repos.d/*
It was not so much about the kernel modules, but rather about libglx. If you upgraded without uninstalling the nvidia driver, it could happen that the old file was left and overrode the new one (since 13.2 the libglx is installed to a different location, that’s a change in the Xorg packaging).
The kernel modules can mainly be a problem if you switch from one driver version to another (e.g. G03 to G04) because they have the same file, zypper/rpm can remove the old one after installing the new one which would remove the actual (new) kernel module too.
But yes, there is a reason why the openSUSE nvidia wiki page mentions that you should remove the driver completely before an upgrade (I added that paragraph btw ).
But yes, there is a reason why the openSUSE nvidia wiki page mentions that you should remove the driver completely before an upgrade (I added that paragraph btw
Hi wolfi,
Accustomed as I am to reading the openSUSE portals to refresh my memory about the various ways of installing proprietary drivers I have never seen this paragraph.
Have you only just added it? In the last couple of days perhaps?
I’d like to read it and bookmark it.
