Hi, I’ve spent weeks trying to get everything working again since upgrading to 13.1 from 12.3 using the 13.1 x86_64 cd. My sound no longer works, mythtv no longer works, and the only way I can get the system to reboot or shutdown is by using the reset button or power switch, because the system hangs unless I boot to the 3.7.10 kernel from 12.3. I’ve submitted bugs but the future doesn’t look good for getting them fixed anytime soon since TV cards are a low priority. I just want to have a working system again without starting over with a fresh install of 12.3
On 2014-05-10 00:36, motonut wrote:
>
> Hi, I’ve spent weeks trying to get everything working again since
> upgrading to 13.1 from 12.3 using the 13.1 x86_64 cd. My sound no
> longer works, mythtv no longer works, and the only way I can get the
> system to reboot or shutdown is by using the reset button or power
> switch, because the system hangs unless I boot to the 3.7.10 kernel from
> 12.3. I’ve submitted bugs but the future doesn’t look good for getting
> them fixed anytime soon since TV cards are a low priority. I just want
> to have a working system again without starting over with a fresh
> install of 12.3
We can try to help you solve the issues, but going back is next to
impossible.
The easiest way is to recover from backup. No kidding.
Then you could try a zypper dup backwards, but it can fail or leave you
an unusable system or broken who knows where. Then it might just work…
nobody can know.
Or, reinstall.
So instead just post here links to the forum threads where you asked for
help on each of those separate issues.
I also would like to know how exactly did you upgrade from 12.3 to 13.1.
Which CD, the netinstall CD? That’s the only one I know. Then what did
you do?
I typed CD when I meant DVD. I downloaded the 13.1 x86_64 DVD (I used to buy the boxed DVDs, but the only one available now seems to be the German one).
I booted from the 13.1 DVD and selected upgrade from the menu. That’s when I descended into Hell.
I have posted a bug on bugzilla.novell.com (Bug 876806), where I was directed to post a bug on bugzilla.kernel.org (Bug 75821). In the meantime, I no longer have sound, (probably from installing 3.14.2 and 3.7.10 per the request from wolfi323). That was working before the upgrade.
I am using the KDE desktop.
I was planning to just copy my /home directory to another location, boot from the 12.3 dvd and “upgrade” the 13.1 partition. Then I will copy my /home directory back.
At this point, I don’t care if I have to reinstall/reconfigure apache2, mythtv, libreoffice, and audacity. That part is easy compared to the frustration that 13.1 has put me through.
At this point, I think 12.3 is going to be my last version. Mythtv has become a backwater as far as openSUSE is concerned, so there is not likely to be a kernel fix any time soon. I understand that, which is why I would rather go back to something that works.
If it was my system, I would also try options in the following order:
Restore from a partition backup (preferably clone where only used blocks are saved), if you have one.
Remove unwanted kernels (in case zypper dup doesn’t). Change repos back to 12.3 versions. Consider just enabling the four main openSUSE repos, but that means extra update(s) for additional repos later. Perform “zypper dup”, it might work.
Clean install (formatting root partition) from 12.3 original media. The most work, to change settings, and reinstall applications. The 13.1 KDE settings in /home (e.g. ~/.kde4/) might cause problems. You can delete those .kde4 settings and logout/re-login, but you will then need to repeat your previous customizations.
Good luck, 12.3 is a pretty good release (I was using it recently until upgrading it online to 13.1).
Hi again,
since I never used zypper dup before, I looked up the procedure in the SDB. Here is what I have done so far:
As an example, we will be showing upgrade from 12.3 to 13.1 here:
- Take a look at all repos you have
- zypper lr
and remove all third party/OBS repos you no longer need#
- zypper rr <alias>
- Change all remaining repo URLs to the new version of the distribution (needs to be run as root)#
- cp -Rv /etc/zypp/repos.d /etc/zypp/repos.d.Old
(for a backup copy), then:
- # sed -i 's/12\.3/13\.1/g' /etc/zypp/repos.d/*
I am not ready to do the zypper dup yet, just in case some more information is needed for the bugs I entered, but since they are relatively low priority, I am not going to wait too long.
In the meantime, I copied /home/alfredr/* to a different drive.
Well, that grep only shows the lines that contain 12.3, so doesn’t really help to verify.
Just run “zypper lr -d” and check that all the URLs have 12.3 in them.
What the grep produced does look reasonable, only one note:
you don’t need packman-essentials and packman-multimedia, remove them. You seem to have the full Packman repo as well anyway, which of course includes everything from essentials and multimedia.
But again, that grep output isn’t really helpful. It doesn’t even show which repos are enabled and which are not.
I prefer to use YaST for reviewing and editing repos, not surprisingly it’s graphically superior to the terminal [on my system]. However “zypper lr -d” also has its uses, e.g. for reporting in forum posts.
Three packman repos is unnecessary. I use the “Essential” and “Multimedia” repos, where I only need a few packages from “Multimedia”, so I can restrict Packman’s upgrades to that area of the system. For any other packages from Packman, I install from their website using 1-click.
Personally, “zypper dup” has been as good downgrading as it is upgrading when I’ve had to do so. There’s always one or two packages that I forget to manually upgrade afterwards. I usually hunt for those with YaST, as they show up in “red” without a repo selected (see versions tab).
zypper: /usr/lib64/libstdc++.so.6: version GLIBCXX_3.4.18' not found (required by zypper) zypper: /usr/lib64/libstdc++.so.6: version GLIBCXX_3.4.18’ not found (required by /usr/lib64/libzypp.so.1306)
I think the problem is:
/usr/lib/libstdc++.so.6 has versions up to:
GLIBCXX_3.4.18
GLIBCXX_3.4.19
but /usr/lib64/libstdc++.so.6 only has versions up to:
GLIBCXX_3.4.17
Does anyone know where I can download the correct version? I assume it is from 13.1, but I can’t figure out where to download it.
and the zypper error message is gone, but I don’t know what to do to finish up because it halted on the mkinitrd step. Do I do zypper dup again, or is there something else to do.
What I do is have 2 root partitions and alternate between them. With a new version I install (new) to the partition with the older version I don’t mount my home at first and just allow /home to reside on root partition. Once I’m sure that all is stable and working I mount the home partition getting rid of the temp one I used for testing.
Note I do a fresh install so have to reinstall any programs I want. But I see this as a purge of old stuff I don’t need or use anymore and all my personal configuration are in home which I do reuse.
Note if you use database or web-server etc that may normally live on root you may want to reconfig so the those Database live on a separate partition and treat them like home You can always look at or copy the old /etc configs because they are still on the now old version partition.
On 2014-05-13 03:06, gogalthorp wrote:
>
> What I do is have 2 root partitions and alternate between them.
Many do that, it is a wise procedure.
What I do is have a big, normal system, which I upgrade to the next
version, or not, and a small test partition where I test the next
release, as factory if I can. Thus when I finally upgrade the main
partition I already know that it will work. I don’t jump without a net.
What do you mean with “halted”? Did it abort?
Then you should of course run “zypper dup” again to finish the update. But this will try to install the 12.3 glibc again, and you will supposedly run into the same problem.
In the worst case scenario, maybe he could just backup /home and /etc and make a fresh new install?
I’m not very familiar with openSUSE yet, but that’s how I would do.
What I usually do when changing Linux versions regardless of distributions is to have a /home in a separate partition and just to make a “system” directory inside it and copy everything from “/” with “preserve all” option to it from a live media, so I don’t get garbage from /tmp, etc.
The “rollback” is easy, boot to the live media, format the main partition, mount “/home” and copy everything back. There may be some extra procedures to reinstall the boot manager if not on a separate partition, but the main idea always worked for me.
