Trying to recover from Oct. 24 kernel update

English Install/Boot/Login
1

The Oct. 24 kernel update broke my system and I tried rolling the kernel back to the previous version - which did not work - I got messages about things not supported by the version I was trying to remove … I just don’t know how to do that yet.

Today (10/29/16) I ran zypper lu and found the updated kernel

kernel-desktop-3.16.7-48.1

that I hoped would fix my hosed opensuse, but now I’m worried about all the

Failed to install
and
depmod: WARNING:
and
Warning: /lib/modules/3.16.7-45-default is inconsistent
lines.

3.16.7-45
isn’t even supposed to be there (?) because I tried to roll it back to
3.16.7-42

  • nothing seems to be working for me here.

I wanted to post the output from the “zypper up” action, but it’s too large to fit into a post.

With all the errors (?) I am afraid to reboot because I may not be able to access the forum to ask for help. Part of the damage from that kernel change causes me to have to jump through hoops to get internet access and sound working every time I reboot.

Thanks in advance…

2

Update your System as root:

zypper up
3

Your repos, please

zypper lr -d

And, what do you mean by rollback? Downgrading the kernel? Rather use the Advanced options in the GRUB2 boot menu, which allows you to boot the previous kernel.

4

Last time that I had a kernel update broke my system I used Yast to completly remove the new kernel version that was giving trouble.

So you can use GRUB to boot with the previous Kernel and then use Yast to remove (uninstall) the updated version that’s given you trouble.

5

Yup, that’s possible.

6

Hi Knurpht:

Pegasus:~ # zypper lr -d
# | Alias               | Name                         | Enabled | GPG  Check | Refresh | Priority | Type   | URI                                                           | Service
--+---------------------+------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------+--------
1 | ftp.gwdg.de-suse    | Packman Repository           | Yes     | (r )  Yes  | Yes     |   99     | rpm-md |  http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_13.2/     |        
2 | repo-non-oss        | openSUSE-13.2-Non-Oss        | Yes     | ( p)  Yes  | Yes     |   99     | yast2  |  http://download.opensuse.org/distribution/13.2/repo/non-oss/ |        
3 | repo-oss            | openSUSE-13.2-Oss            | Yes     | ( p)  Yes  | Yes     |   99     | yast2  |  http://download.opensuse.org/distribution/13.2/repo/oss/     |        
4 | repo-update         | openSUSE-13.2-Update         | Yes     | (r )  Yes  | Yes     |   99     | rpm-md |  http://download.opensuse.org/update/13.2/                    |        
5 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss | Yes     | (r )  Yes  | Yes     |   99     | rpm-md |  http://download.opensuse.org/update/13.2-non-oss/            |        
Pegasus:~ #

I’ve already tried using zypper up and that’s how I got that humongous update result showing all the errors and “fail” entries.

I would like to try:

                     https://forums.opensuse.org/images/misc/quote_icon.png Originally Posted by **mhunt0**                     https://forums.opensuse.org/images/buttons/viewpost-right.png](https://forums.opensuse.org/showthread.php?p=2798026#post2798026)                 

                 Last time that I had a kernel update broke my  system I used Yast to completly remove the new kernel version that was  giving trouble.

So you can use GRUB to boot with the previous Kernel and then use Yast  to remove (uninstall) the updated version that's given you trouble.

At this point I think I have a mixture of kernel *45 and *48. Do you think booting to the previous kernel (*42) will work without further complicating things?

Again - I’m reticent to even boot this thing since I’ll have to rebuild the network again, and until that’s done I can’t talk with you…

7

Hi again:

And, what do you mean by rollback? Downgrading the kernel? Rather use the Advanced options in the GRUB2 boot menu, which allows you to boot the previous kernel.

I’m running on 3.16.7-42.1.x86.64 right now, as chosen during boot. I don’t know why it’s working O.K. because Yast will only let me install 3.16.7-48.1.x86_64.

The “Updated” kernel breaks sound and doesn’t find my NIC (onboard the MB). I have no internet access with 3.16.7-48.1.x86_64.

Using Yast to attempt rollback:

kernel-desktop-base-3.16.7-42.1.x86.64 conflicts with kernel-desktop = 3.16.7-42.1 provided by kernel-desktop-3.16.7-42.1.x86_64

kernel-desktop-base-3.16.7-42.1.x86.64 conflicts with
___kernel-desktop = 3.16.7-42.1 provided by
_____kernel-desktop-3.16.7-42.1.x86_64

It “conflicts” with itself as provided by itself?

I can’t revert to 3.16.7-42.1.x86_64 because Yast installs it, then
immediately “upgrades” to 3.16.7-45.1.x86_64 and then 3.16.7-48.1.x86_64,
so I wind up right back with 3.16.7-48.1.x86_64, which breaks my system.

Bottom line - Yast will not let me use kernel-desktop-base-3.16.7-42.1.x86.64 except by booting to the existing “older” kernel.

depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_info_get_line
Warning: /lib/modules/3.16.7-45-desktop is inconsistent
Warning: weak-updates symlinks might not be created

Of course it’s “inconsistent”; I just uninstalled 3.16.7-45-desktop with Yast. It keeps coming back like a bad penny.

depmod: WARNING: //lib/modules/3.16.7-48-desktop/updates/hdj_mod.ko needs unknown symbol snd_info_get_line
Warning: /lib/modules/3.16.7-48-desktop is inconsistent
Warning: weak-updates symlinks might not be created

Of course it’s “inconsistent”; I just uninstalled 3.16.7-48-desktop with Yast. It keeps coming back like a bad penny.

Bottom line, until the kernel is properly fixed, and finds my NIC and sound on boot-up, I may not be able to continue to use opensuse. God help me if something goes wrong with my 3.16.7-42.1.x86.64. I don’t want to “update” anything now because it’ll only break things here.

Color me frustrated.

8

I understand your frustration, hope this gets fixed a.s.a.p. But, for now, you can lock the kernel for updating by declaring it “taboo” in yast’s software manager

9

Click on “Versions” below the package list, and you can see all available versions.

The “Updated” kernel breaks sound and doesn’t find my NIC (onboard the MB). I have no internet access with 3.16.7-48.1.x86_64.

Are you using a 3rd party driver like broadcom-wl?

Using Yast to attempt rollback:

kernel-desktop-base-3.16.7-42.1.x86.64 conflicts with kernel-desktop = 3.16.7-42.1 provided by kernel-desktop-3.16.7-42.1.x86_64

kernel-desktop-base-3.16.7-42.1.x86.64 conflicts with
___kernel-desktop = 3.16.7-42.1 provided by
_____kernel-desktop-3.16.7-42.1.x86_64

It “conflicts” with itself as provided by itself?

No.
kernel-desktop-base conflicts with kernel-desktop.

You should not try to install kernel-desktop-base, it is just a stripped down version of kernel-desktop that comes without most kernel modules/drivers.

I can’t revert to 3.16.7-42.1.x86_64 because Yast installs it, then
immediately “upgrades” to 3.16.7-45.1.x86_64 and then 3.16.7-48.1.x86_64,
so I wind up right back with 3.16.7-48.1.x86_64, which breaks my system.

Use "sudo zypper in kernel-desktop-3.16.7-42.1 to install it.
But YaST shouldn’t “immediately upgrade” it either, and apparently you already have it installed, no?

Bottom line - Yast will not let me use kernel-desktop-base-3.16.7-42.1.x86.64 except by booting to the existing “older” kernel.

As explained, you should not use kernel-desktop-base anyway, it won’t work.

depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_info_get_line
Warning: /lib/modules/3.16.7-45-desktop is inconsistent
Warning: weak-updates symlinks might not be created

The hdj_mod.ko module you have installed apparently is incompatible with kernel 3.16.7-45-desktop.

Of course it’s “inconsistent”; I just uninstalled 3.16.7-45-desktop with Yast. It keeps coming back like a bad penny.

No, that’s wrong.
It is inconsistent, because the hdj_mod.ko module you have installed apparently is incompatible with kernel 3.16.7-45 (and 48)-desktop.
This also breaks creating symlinks of other installed kernel modules (e.g. nvidia, broadcom-wl) to the new kernel.

Where does this module come from and what it’s for?
Uninstall it, and the kernel should work.

Maybe you need to recompile it against the latest kernel…

Bottom line, until the kernel is properly fixed, and finds my NIC and sound on boot-up, I may not be able to continue to use opensuse.

I don’t think there’s anything wrong with the kernel.
So there’s nothing to get fixed either.

10

PS: Apparently this is part of the package hdjmod-kmp-desktop, so uninstall this, reinstall the kernel 3.16.7-48-desktop, and it should work.

11

I set Yast to uninstall kernel-desktop-base-3.16.7-42.1.x86.64

It is downloading kernel-desktop (3 different files of differing sizes)
The bar that shows “Downloading Packages…” says

“Downloaded 2 of 1 packages”

???

Now I wonder what I’ll end up with…

OH! Now it’s installing 3.16.7-45.1.x86_64 and 3.16.7-48.1.x86_64 again!

****!.
Downloading kernel-desktop-base (download size 14.34 MiB)
Downloading kernel-desktop-base (download size 12.41 MiB)
Downloading kernel-desktop-base (download size 10.84 MiB)
Deleting kernel-desktop
Deleting kernel-desktop
Deleting kernel-desktop
Installing kernel-desktop-base-3.16.7-45.1.x86_64.rpm (installed size 49.87 MiB)
Installing kernel-desktop-base-3.16.7-48.1.x86_64.rpm (installed size 49.87 MiB)
Installing kernel-desktop-base-3.16.6-2.1.x86_64.rpm (installed size 49.85 MiB)

NO MATTER WHAT I DO, THIS THING IS GOING TO SHOVE 45 AND 48 UP MY KEISTER!

I have no clue where or why I have a “hdj_mod.ko” module. Everything I have is presumably from an opensuse repository.

Deleting hdjmod-kmp-desktop:

Deleting hdjmod-kmp-desktop
Additional rpm output:
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_matches
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_targets
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_targets
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_matches
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnetlink_subsys_register
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnl_unlock
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnetlink_subsys_unregister
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnl_lock
Warning: /lib/modules/3.16.6-2-desktop is inconsistent
Warning: weak-updates symlinks might not be created
depmod: WARNING: /lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_matches
depmod: WARNING: /lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_targets
depmod: WARNING: /lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_targets
depmod: WARNING: /lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_matches
depmod: WARNING: /lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnetlink_subsys_register
depmod: WARNING: /lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnl_unlock
depmod: WARNING: /lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnetlink_subsys_unregister
depmod: WARNING: /lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnl_lock
depmod: ERROR: fstatat(5, vboxguest.ko): No such file or directory
depmod: ERROR: fstatat(5, vboxvideo.ko): No such file or directory
depmod: ERROR: fstatat(5, vboxsf.ko): No such file or directory
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_rawmidi_receive
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_rawmidi_transmit_empty
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_rawmidi_transmit
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_card_register
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_card_free
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_card_proc_new
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_component_add
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_rawmidi_transmit_ack
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_card_new
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol __snd_printk
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_iprintf
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_card_free_when_closed
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_device_new
depmod: WARNING: //lib/modules/3.16.7-45-desktop/updates/hdj_mod.ko needs unknown symbol snd_rawmidi_new
Warning: /lib/modules/3.16.7-48-desktop is inconsistent
Warning: weak-updates symlinks might not be created
(list truncated for size limitation in forum)

Deleting hdjmod-kmp-desktop
Additional rpm output:
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_matches
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_targets
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_targets
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_matches
depmod: WARNING: //lib/modules/3.16.
(list truncated for size limitation in forum)
Warning: /lib/modules/3.16.7-48-desktop is inconsistent
Warning: weak-updates symlinks might not be created


Deleting hdjmod-kmp-desktop
Additional rpm output:
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_matches
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_targets
(list truncated for size limitation in forum)
Warning: /lib/modules/3.16.7-48-desktop is inconsistent
Warning: weak-updates symlinks might not be created


Deleting hdjmod-kmp-desktop
Additional rpm output:
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_matches
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_targets
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_targets
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_matches
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnetlink_subsys_register
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnl_unlock
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnetlink_subsys_unregister
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/ipset/ip_set.ko needs unknown symbol nfnl_lock
(list truncated for size limitation in forum)
Warning: /lib/modules/3.16.6-2-desktop is inconsistent
Warning: weak-updates symlinks might not be created
depmod: ERROR: fstatat(5, vboxguest.ko): No such file or directory
depmod: ERROR: fstatat(5, vboxvideo.ko): No such file or directory
depmod: ERROR: fstatat(5, vboxsf.ko): No such file or directory

Again - color me frustrated.

12

Tell it to install kernel-desktop-3.16.7-42.1 rather, then answer to uninstall kernel-desktop-base when you’re asked.

OH! Now it’s installing 3.16.7-45.1.x86_64 and 3.16.7-48.1.x86_64 again!

What did you do exactly?
That shouldn’t happen automatically as already mentioned.
Unless some other installed package requires this particular kernel version.

Maybe post the list of kernel packages you actually have installed now:

rpm -qa | grep -e "kmp|kernel"

Deleting hdjmod-kmp-desktop:

Deleting hdjmod-kmp-desktop
Additional rpm output:
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_matches
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_unregister_targets
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_targets
depmod: WARNING: //lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko needs unknown symbol xt_register_matches
depmod: WARNING: //lib/modules/3.16.
(list truncated for size limitation in forum)
Warning: /lib/modules/3.16.7-48-desktop is inconsistent
Warning: weak-updates symlinks might not be created

And what is this?

rpm -qf /lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko

That seems to be incompatible to, so uninstall it.

If there’s an incompatible module installed, weak-updates will not create symlinks for other modules, so you may be missing necessary modules/drivers.

Again - color me frustrated.

What would it help? :wink:

13

I have the same problem think it is some NVIDA modules that also refuse to go away. Removing old desktop kernels forces base kernels in. Trying to uninstall NVIDIA driver (GO3) to hopefully wants to install GO4. ARRRG

Any how there is no problem all things run fine just have some extraneous stuff. And any way I plane to move to 42.2 soon as a new install

14

Which one exactly?

The nvidia driver is only offered for kernel 3.16.6, so you probably cannot remove that one.
Others should not be blocked by nvidia though.

But did you really uninstall nvidia-gfxG03-kmp-desktop and nvidia-uvm-gfxG03-kmp-desktop too?

If something that’s installed requires a specific kernel version, you cannot uninstall that kernel version (YaST/zypper will try to pull in kernel-base-xxx to fulfill the dependency).

Trying to uninstall NVIDIA driver (GO3) to hopefully wants to install GO4. ARRRG

Apparently G04 claims to support your card too, so it will be installed as recommended package if the nvidia repo is active (and you try to remove G03).
You could lock G04 though, but what’s the point.
If you don’t want to have the nvidia driver installed, just remove or disable the nvidia repo before you uninstall it.

In any case, that “problem” is not really the topic of this thread here…

15

Only reason to remove NVIDIA driver was to try and get rid of the old kernels without base being drug in.

the kernels stuck are 3.16.7-21.1 and 3.16.6-2.1( which is listed twice?)

Don’t have a burning desire to try and fix since will soon be moving on to 42.2 and I always do a clean new install rather then upgrade

16 
 Pegasus:~ # rpm -qa | grep -e "kmp|kernel"
Pegasus:~ #

And what is this?

rpm -qf /lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko

Pegasus:~ # rpm -qf /lib/modules/3.16.6-2-desktop/extra/netfilter/xt_set.ko
ipset-kmp-desktop-6.23_k3.16.6_2-1.10.x86_64
Pegasus:~ #

That seems to be incompatible too, so uninstall it.

If there’s an incompatible module installed, weak-updates will not create symlinks for other modules, so you may be missing necessary modules/drivers.

I would love to install the stuff that does work and uninstall the stuff that doesn’t, but anything I’ve tried so far has wound up reinstalling 45 and then 48.

What would it help? :wink:

Nothing - except that it’s gentler than dragging out the mousepad I picked up back in Winders Days - with the message on it saying “BANG HEAD HERE”.

I’m about to try uninstalling or updating ipset-kmp-desktop-6.23_k3.16.6_2-1.10.x86_64 since Yast indicates I can update to the 3.16.7-42.1.x86.64 version. I’ll have to reboot, so if I can’t get back online I may not be with you for a while…

Crossed fingers, knock wood, etc…

17

O.K. Guys - I’m back, running on 3.16.7-42.1.x86.64, chosen from the boot menu.

ipset-kmp-desktop 6.23_k3.16.7_42-20.3 (6.23_k3.16.7_48-24.1)

shows in Yast as “not installed” now (no checkmarks).

I set Yast to UNinstall:

kernel-desktop-3.16.7-45.1.x86_64
kernel-desktop-3.16.7-48.1.x86_64 and
kernel-desktop-3.16.6-2.1.x86_64.rpm

and INstall:

kernel-desktop-base-3.16.7-42.1.x86.64

Result:

Downloading kernel-desktop (download size 46.21 MiB)
Downloading kernel-desktop (download size 44.27 MiB)
Downloading kernel-desktop (download size 42.69 MiB)
Deleting kernel-desktop-base
Deleting kernel-desktop-base
Deleting kernel-desktop-base
Installing kernel-desktop-3.16.7-45.1.x86_64.rpm (installed size 215.83 MiB)
Installing kernel-desktop-3.16.7-48.1.x86_64.rpm (installed size 215.82 MiB)
Installing kernel-desktop-3.16.6-2.1.x86_64.rpm (installed size 215.72 MiB)

Yast downloaded a fresh copy of all three wrong files and installed them - exactly reverse of what I set it to do. I believe Yast is also broken - I’ve been through this too many times, and it just doesn’t work … and by “doesn’t work” I mean it doesn’t bloody well do what I tell it to, which is UNinstall what I tell it to and then LEAVE it uninstalled.

I also believe a lot of these incompatible versions may have come in during that bogus “update” that got me in this mess in the first place.

I also wonder if that “update” contained a mixture of versions including possibly 13.2, “LEAP”, and who knows what else. The sheer size and length of time it took was extraordinary, and so was the list of errors and failures.

Is there some setting in Yast that will change the way it “chooses” what to download/update etc.? And also, have any of you gurus tried this process lately yourselves? I think maybe your expectations about the way Yast functions is based on earlier experience when it worked properly? Just wondering…

18

Sorry, I made a tying error, it should have been an upper case E.
Use this instead:

rpm -qa | grep -E "kmp|kernel"

Or this would work too:

rpm -qa | egrep "kmp|kernel"

I’m about to try uninstalling or updating ipset-kmp-desktop-6.23_k3.16.6_2-1.10.x86_64 since Yast indicates I can update to the 3.16.7-42.1.x86.64 version. I’ll have to reboot, so if I can’t get back online I may not be with you for a while…

Those kmp’s are always released as updates as well, and you should install the versions matching your kernel.
But if you don’t have a special need for ipset, you could just as well remove it.
It should not be necessary for normal usage, and is not installed by default anyway.

IP sets are a framework inside the Linux kernel, which can be
administered by the ipset utility. Depending on the type, currently
an IP set may store IP addresses, (TCP/UDP) port numbers or IP
addresses with MAC addresses in a way, which ensures lightning speed
when matching an entry against a set.

19

I already told you that you should not install kernel-desktop-base.
This will only give you problems.

Yast downloaded a fresh copy of all three wrong files and installed them - exactly reverse of what I set it to do. I believe Yast is also broken - I’ve been through this too many times, and it just doesn’t work … and by “doesn’t work” I mean it doesn’t bloody well do what I tell it to, which is UNinstall what I tell it to and then LEAVE it uninstalled.

Sorry, but I don’t believe this.
Maybe you misunderstand something? :wink:

If you want to make sure something stays uninstalled, you should lock (“taboo”) it though.

I also wonder if that “update” contained a mixture of versions including possibly 13.2, “LEAP”, and who knows what else. The sheer size and length of time it took was extraordinary, and so was the list of errors and failures.

Then please post your repo list:

zypper lr -d

Is there some setting in Yast that will change the way it “chooses” what to download/update etc.?

Again, it doesn’t “choose” anything, it just tries to fulfill the package dependencies.
There are some settings though, like allowing or disallowing the automatic installation of “recommended” packages.

And also, have any of you gurus tried this process lately yourselves? I think maybe your expectations about the way Yast functions is based on earlier experience when it worked properly? Just wondering…

Of course, I use it nearly every day.

Btw, YaST is only a different frontend to openSUSE’s package management (libzypp), so if it was broken, zypper would be broken too.

20

Hi
Wolfi:

Fine! Got that. But it is installed and I can’t get it UNinstalled.

Yast downloaded a fresh copy of all three wrong files and installed them - exactly reverse of what I set it to do. I believe Yast is also broken - I’ve been through this too many times, and it just doesn’t work … and by “doesn’t work” I mean it doesn’t bloody well do what I tell it to, which is UNinstall what I tell it to and then LEAVE it uninstalled.

I set Yast to UNinstall:

kernel-desktop-3.16.7-45.1.x86_64
kernel-desktop-3.16.7-48.1.x86_64 and
kernel-desktop-3.16.6-2.1.x86_64.rpm

and INstall:

kernel-desktop-base-3.16.7-42.1.x86.64

Result:

Downloading kernel-desktop (download size 46.21 MiB)
Downloading kernel-desktop (download size 44.27 MiB)
Downloading kernel-desktop (download size 42.69 MiB)
Deleting kernel-desktop-base
Deleting kernel-desktop-base
Deleting kernel-desktop-base
Installing kernel-desktop-3.16.7-45.1.x86_64.rpm (installed size 215.83 MiB)
Installing kernel-desktop-3.16.7-48.1.x86_64.rpm (installed size 215.82 MiB)
Installing kernel-desktop-3.16.6-2.1.x86_64.rpm (installed size 215.72 MiB)

What did I misunderstand?

I tried that last night. Same result. Yast simply cancels the “lock” and upgrades to versions that don’t work on this machine.

[quote=“wolfi323,post:19,topic:121769”]
Then please post your repo list:

zypper lr -d

Pegasus:~ # zypper lr -d
# | Alias               | Name                         | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                          | Service
--+---------------------+------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------+--------
1 | ftp.gwdg.de-suse    | Packman Repository           | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_13.2/     |        
2 | repo-non-oss        | openSUSE-13.2-Non-Oss        | Yes     | ( p) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.2/repo/non-oss/ |        
3 | repo-oss            | openSUSE-13.2-Oss            | Yes     | ( p) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.2/repo/oss/     |        
4 | repo-update         | openSUSE-13.2-Update         | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.2/                    |        
5 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.2-non-oss/            |        
Pegasus:~ #

Oboy, do I need a primer on Yast!

Thanks, Wolfi, for hanging in with me on this … it’s driving me crazy here…