13.1 -> 13.2 problem

English Install/Boot/Login
1

KDE & v13.1x64 fully updated including recent kernel update.

I tried to do the 13.2 update from DVD I downloaded in November. On reboot I get a “failed to start load kernel modules”. The system starts but some things don’t work, most notably, YaST/2 won’t start.

systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
   Active: failed (Result: exit-code) since Thu 2014-12-25 16:33:13 PST; 4min 9s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 678 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 678 (code=exited, status=1/FAILURE)

And from messages, an entry for YaST2:

2014-12-25T17:03:44.272605-08:00 linux-shpr kernel:  1838.372142] y2controlcenter[6276]: segfault at c ip 00007f4253177120 sp 00007fff2b853748 error 4 in libxcb-glx.so.0.0.0[7f425316b000+16000]

I tried running the update a second time with the same results.

Any suggestion on how to fix this?

Thanks, Jon

2

On 2014-12-26 02:16, 6520302 wrote:
>
> KDE & v13.1x64 fully updated including recent kernel update.
>
> I tried to do the 13.2 update from DVD I downloaded in November. On
> reboot I get a “failed to start load kernel modules”. The system starts
> but some things don’t work, most notably, YaST/2 won’t start.

Run this in a terminal:


rpm -q -a --queryformat "%{INSTALLTIME}	%{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME}	%15{VERSION}-%-7{RELEASE}	%{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" | tee rpmlist \
| egrep -v "openSUSE.13\.2" | less -S

(‘q’ to exit)

If there is output, you have to check each line. It is a package list,
sorted by dates, with release info, that don’t have the string
“openSUSE.13.2”; ie, packages that were possibly not upgraded, and
which you have to consider to upgrade or not.

(If you want me to check the list for you, upload the file “rpmlist” to
susepaste.org for a limited time)

The DVD upgrade method can not upgrade everything, it is too small.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

3

It’s a long list. When I tried to post it as susepaste it returned a msg that I was a spammer. Have no idea if I did something wrong in my attempt to post it.

But shouldn’t an update from 13.1 -> 13.2 have the necessary files to run YaST2? Is there a pkg that contains libxcb-glx.so.0.0.0 that I can install w/ zypper or is that not adviseable?

During the upgrade, when it offered to remove repositories, I selected some and changed to ‘disable’ so that I could re-enable them later. I am wondering if that confused the upgrade?

Jon

4

You probably got an incomplete upgrade for some reason. Don’t know why it normally does not happen. Disabling the wrong repos could maybe be the problem.Also did you check the checksums of the ISO download and run media check on the DVD??

5

Yes, I checked the checksums before I wrote the DVD. I don’t recall if I did the media check, I’ll do that.

This is my repo list:


#  | Alias                              | Name                               | Enabled | Refresh
---+------------------------------------+------------------------------------+---------+--------
 1 | PTA                                | PTA                                | No      | Yes    
 2 | download.opensuse.org-13.2-non-oss | Update Repository (Non-Oss)        | Yes     | Yes    
 3 | download.opensuse.org-non-oss      | Main Repository (NON-OSS)          | Yes     | Yes    
 4 | download.opensuse.org-oss          | Main Repository (OSS)              | Yes     | Yes    
 5 | download.opensuse.org-update       | Main Update Repository             | Yes     | Yes    
 6 | google-earth                       | google-earth                       | No      | Yes    
 7 | home:luckyb69                      | home:luckyb69                      | No      | Yes    
 8 | home:steffens:SmartClient:client   | home:steffens:SmartClient:client   | No      | Yes    
 9 | openSUSE-13.2-0                    | openSUSE-13.2-0                    | Yes     | No     
10 | repo-debug                         | openSUSE-13.2-Debug                | No      | Yes    
11 | repo-debug-update                  | openSUSE-13.2-Update-Debug         | No      | Yes    
12 | repo-debug-update-non-oss          | openSUSE-13.2-Update-Debug-Non-Oss | No      | Yes    
13 | repo-source                        | openSUSE-13.2-Source               | No      | Yes    
14 | v13.2_FGLRX                        | v13.2 FGLRX                        | Yes     | Yes    
15 | virtualbox                         | virtualbox                         | No      | No

Jon

6

My media check was good.

Jon

7

On 2014-12-26 06:46, gogalthorp wrote:
>
> You probably got an incomplete upgrade for some reason. Don’t know why
> it normally does not happen.

On the contrary, it must happen when using the Offlline Upgrade method,
ie, boot the DVD, choose upgrade. There is no way around it, because the
DVD is too small to hold the entire OSS repo. Anything that is installed
but is not included in the DVD.

It is documented.

Offline upgrade
method

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

8

On 2014-12-26 06:06, 6520302 wrote:
>
> robin_listas;2685195 Wrote:

> It’s a long list. When I tried to post it as susepaste it returned a
> msg that I was a spammer. Have no idea if I did something wrong in my
> attempt to post it.

Sigh… it happens now and then :-/

> But shouldn’t an update from 13.1 -> 13.2 have the necessary files to
> run YaST2? Is there a pkg that contains libxcb-glx.so.0.0.0 that I can
> install w/ zypper or is that not adviseable?

yes, it comes in “libxcb-glx0-1.11-2.1.2.x86_64”, so


zypper upgrade libxcb-glx0

should do it.

During the upgrade, when it offered to remove repositories, I selected
some and changed to ‘disable’ so that I could re-enable them later. I
am wondering if that confused the upgrade?

No, I don’t think so. I will have a look at your list in the other post
in a minute.

You can do something else.

Disable temporarily all repos, except oss and non-oss, then run this
sequence:


zypper dup
zypper up
zypper patch

Make sure you only have the 4 official repos active before running that
(an exception could be nvidia/ati repo, if it was used previously).

Then run again the rpm query and check the list.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

9

On 2014-12-26 07:36, 6520302 wrote:

> This is my repo list:

I see no problem with it.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

10

Didn’t help.

# zypper up libxcb-glx0     
Loading repository data...
Reading installed packages...
No update candidate for 'libxcb-glx0-1.11-2.1.2.x86_64'. The highest available version is already installed.
Resolving package dependencies...

Nothing to do.

So there must be a deeper problem since log/messages indicated a segment fault & error in y2controlcenter (my original post).

That is what I will try next however I have 5 official repos active, not 4, I don’t know which one I should deactivate (prior post).
And I don’t know how to do that from the cmdline, I’m still researching how to do that.

Thanks for your suggestions,
jon

11

On 2014-12-26 17:06, 6520302 wrote:

> Didn’t help.
>
>
> Code:
> --------------------
> # zypper up libxcb-glx0
> Loading repository data…
> Reading installed packages…
> No update candidate for ‘libxcb-glx0-1.11-2.1.2.x86_64’. The highest available version is already installed.
> Resolving package dependencies…
>
> Nothing to do.
>
> --------------------

Well, it is installed, and the correct version.

>> Make sure you only have the 4 official repos active before running
>> that
>> (an exception could be nvidia/ati repo, if it was used previously).
>>
>
> That is what I will try next however I have 5 official repos active, not
> 4, I don’t know which one I should deactivate (prior post).

No problem, the other one is the DVD. No problem.
I think you also have the ati repo, leave it. Virtualbox should not be a
problem either.

What could be a problem at this stage is packman, and you don’t have it,
or extra repos for kde/gnome, etc.

Restricting the list of active repos is done in order to limit the
number of possible conflicts. Zypper dup makes some rather drastic
decisions, and having available several sources for the same packages
sometimes works right, some times not. So better avoid the conflicts in
advance.

> And I don’t know how to do that from the cmdline, I’m still researching
> how to do that.

Your repo list is fine as it is, so just go ahead with the zypper dup,
zypper up, and zypper patch sequence.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

12

Although it won’t address any other problems which might exist, you might try force re-installing yast to make sure you have the proper packages installed (and uncorrupted).

zypper in -f yast2

Also, if you prefer to use yast, although the GUI YAST might not work it’s possible the curses mode (text) version of yast is working, simply invoke yast in a root console(The following has a hash character only to denote is in a root console, do not type it)

# yast

TSU

13

This is yast cmdline:

# yast2
/sbin/yast2: line 440:  4978 Segmentation fault      $y2ccbin $Y2UI_ARGS "$@"

I will next try to reinstall yast2 with the above zypper cmd and if that doesn’t work I will do the zypper dup. up, & patch sequence.

Thank You Robin & Tsu.
jon

14

OK, reinstalling yast2 worked, I can get the cmdline program to run, some progress!!

Still cannot get gui to run, still has same segmentation fault.

Next step will be the 3 zypper cmds.

Thanks, Jon

15

This didn’t fix my problem.

On boot I still get the original service error I posted at the start of this thread and the same segmentation error I originally posted for starting yast2.

So far, the only improvment is I can run yast from the cmdline which I could do before.

During zypper dup I received the following error but I don’t believe it relates to the yast3 problem, it might be related to the load kernel module error I see on booting? This seems to be the AMD video driver.

*** Installing kernel module dependencies and firmware ***
    dracut-install: ERROR: installing '/lib/modules/3.11.10-21-desktop/extra/fglrx.ko'
    modinfo: ERROR: Module /lib/modules/3.11.10-21-desktop/extra/fglrx.ko not found.

What should I try to do now? Online upgrade?

Thanks, jon

16

Correction, referring to running yast from cmdline:

So far, the only improvment is I can run yast from the cmdline which I could NOT do before.

Jon

17

On 2014-12-26 19:26, 6520302 wrote:
>
> robin_listas;2685282 Wrote:
>> On 2014-12-26 17:06, 6520302 wrote:
>>
>> Your repo list is fine as it is, so just go ahead with the zypper dup,
>> zypper up, and zypper patch sequence.
>
> This didn’t fix my problem.

What is now the output of the rpm query command I posted the first day?
It should be pretty short. You probably need to reboot after it, I
forgot to say.

> On boot I still get the original service error I posted at the start of
> this thread and the same segmentation error I originally posted for
> starting yast2.

Oh, so you rebooted.

> So far, the only improvment is I can run yast from the cmdline which I
> could not do before.

Yes, that’s something.

> During zypper dup I received the following error but I don’t believe it
> relates to the yast3 problem, it might be related to the load kernel
> module error I see on booting? This seems to be the AMD video driver.

Yes, probably you also need to upgrade that driver from its repo. I’m
not familiar with amd video, though, but perhaps there is something else
on that respect you should do. I don’t know.

> What should I try to do now? Online upgrade?

No, the “zypper dup” sequence /is/ an online upgrade. That three command
sequence is a modified online upgrade sequence, intended to upgrade
whatever the offline upgrade missed.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

18

Robin:

Thank you for you help. I have spent 2 days on this problem and still failing to progress to a useable system.
I have thrown in the towel and restored my system to v13.1, although it now has it’s own set of problems.

I have a grub2 issue now and I will create a new post for that.

I now need to boot my system w/ super-grub and select recovery mode to get v13.1 up and running, but at least I can keep current with my computing chores.

Thanks again.
jon

19

jon,

I suspect you did the following instead of yast2

zypper in -f yast

The above re-installs yast running in curses mode, whereas “yast2” as follows re-installs the GUI mode version

zypper in -f yast2

I also need a better explanation what the result is.
It’s unclear how well yast is working, even in ncorses mode. If you in any way find searching and installing packages isn’t working as expected, then you would next remove the repositories cache and allow it to re-build.

TSU

20

That sounds plausable. I’ve overwritten that partition, reverting back to v13.1, so I can no longer check this.

Thanks, Jon