Still using default kernel after upgrade...

So I did this Tumbleweed thing and upgraded using the following repos,

# | Alias                | Name                       | Enabled | Refresh | Priority | Type   | URI                                                                      | Service
1 | Tumbleweed           | Tumbleweed                 | Yes     | Yes     |   99     | rpm-md | |        
2 | libdvdcss repository | libdvdcss repository       | Yes     | Yes     |   99     | rpm-md |                                     |        
3 | openSUSE_Tumbleweed  | openSUSE_Tumbleweed        | Yes     | Yes     |   99     | rpm-md |                        |        
4 | repo-debug           | openSUSE-11.4-Debug        | No      | Yes     |   99     | NONE   |           |        
5 | repo-debug-update    | openSUSE-11.4-Update-Debug | No      | Yes     |   99     | NONE   |                          |        
6 | repo-non-oss         | openSUSE-11.4-Non-Oss      | Yes     | Yes     |   99     | yast2  |             |        
7 | repo-oss             | openSUSE-11.4-Oss          | Yes     | Yes     |   99     | yast2  |                 |        
8 | repo-source          | openSUSE-11.4-Source       | No      | Yes     |   99     | NONE   |          |        
9 | repo-update          | openSUSE-11.4-Update       | Yes     | Yes     |   99     | rpm-md |                                |        

with the command.

zypper dup

But it seems that I’m still using default kernel:

uname -a
Linux linux-qbqw #1 SMP PREEMPT 2011-04-25 21:48:33 +0200 x86_64 x86_64 x86_64 GNU/Linux

“zypper se -is kernel” shows:

S | Name                 | Type    | Version                | Arch   | Repository          
i | kernel               | patch   | 4437                   | noarch | openSUSE-11.4-Update
i | kernel-desktop       | package |         | x86_64 | openSUSE-11.4-Update
i | kernel-desktop-devel | package |          | x86_64 | Tumbleweed          
i | kernel-devel         | package |          | noarch | Tumbleweed          
i | kernel-firmware      | package | | noarch | openSUSE_Tumbleweed 
i | kernel-source        | package |          | noarch | Tumbleweed 

And the summary of “zypper dup -D --from Tumbleweed” gives this output (after I have chosen not to keep the default kernel):

Resolving dependencies...
Computing distribution upgrade...

The following packages are going to be REMOVED:
  ndiswrapper ndiswrapper-kmp-desktop open-vm-tools open-vm-tools-gui virtualbox-guest-kmp-desktop virtualbox-guest-tools virtualbox-guest-x11 vmware-guest-kmp-desktop 

The following package is going to be upgraded:

The following packages are going to be downgraded:
  gkeyfile-sharp gudev-sharp kernel-firmware libldb0 libtalloc2 libtalloc2-32bit libtdb1 libtevent0 

The following packages are going to change vendor:
  gkeyfile-sharp    openSUSE -> obs://                     
  gudev-sharp       openSUSE -> obs://                     
  kernel-desktop    openSUSE -> obs://                     
  kernel-firmware -> obs://
  libldb0           openSUSE -> obs://                     
  libtalloc2        openSUSE -> obs://                     
  libtalloc2-32bit  openSUSE -> obs://                     
  libtdb1           openSUSE -> obs://                     
  libtevent0        openSUSE -> obs://                     

1 package to upgrade, 8 to downgrade, 8 to remove, 9  to change vendor.
Overall download size: 45.2 MiB. After the operation, 8.7 MiB will be freed.
Continue? [y/n/?] (y):

As far as I’m aware, I’m not using ndiswrapper, vmvare or virtualbox for anything I’m aware of, so I was wondering if I should just do the upgrade, and continue installing the proprietary Nvidia driver.

Not an extremely experienced openSUSE user, but I kind of thought this could be a good learning experience, since 11.4 never seemed to have too many problems (so I found it a bit boring).


That looks pretty straightforward. No dependency issues. Kernel will upgrade (probably to Some 9 RPMs will swap over to Tumbleweed. And you don’t care if the unused RPMs are removed, so that’s OK.

I’d pull the trigger (and duck LOL).

Thanks swerdna! I pulled the trigger, installed the upgrade and installed drivers. Everything seems perfectly fine.

$ cat /etc/SuSE-release
openSUSE 11.4 (x86_64)
VERSION = 11.4
CODENAME = Celadon


I had the same thing when running zypper dup without --from Tumbleweed, led to various problems (some mentioned on another thread) which I think the OP avoided by running zypper dup --from Tumbleweed immediately after zypper dup

I solved the problems but decided to do a complete reinstall purely to test the idea that those issues, stemming from the newer kernel from Tumbleweed not getting installed with zypper, would probably not appear if I gave the Tumbleweed repo(s) a higher priority than the 11.4 ones

So I did that, left the 11.4 repos as priority 99 and set the Tumbleweed ones to 95, ran zypper dup and as I suspected no conflicts to resolve and the later kernel was installed

Excellent… BTW I don’t think there are plans to change the contents of the file SuSE-release. It marks the originating distro, although that would be almost completely eroded by the time 12.1 comes out.

You can use Clonezilla to backup your “/” (and “home”) partition if you are unsure.

It’s very handy tool, especially if you are using rolling distro or making big changes in the system (for example switching DE).
Saved me a couple of times. I highly recommend it :slight_smile:

If anyone wants to “spot upgrade” a package changing vendor, without starting Software Manager and going into the Versions radio button tab.

Say you have version 4.0.1 of package foobar and now you want a new shiny Tumbleweed version, but you don’t want to run zypper dup, because it’ll switch Packman packages to Tumbleweed versions that (likely) aren’t build for desired multi-media codecs, then :

zypper in foo-bar-5.0

Is all you need to do. Specifying the version “just works”. If you think about it, “zypper rm <package> && zypper in <package>” would by default install the latest version, without keeping Vendor constant. From what I can see, this “–from” is OK for mass upgrading packages with vendor change, after adding Packman repo say, but is going to risk unwanted Vendor changes after.

Life would be much simpler if “Tumbleweed” shared the same vendor as rest of openSUSE, so it was just an “upgrade” repo on steroids, where you can zypper up, without worries and only mess with “zypper dup --from Packman” on multi-media installation, and then you’ld probably have less package management maintenance worries if you get tempted by any other repos :slight_smile: