4.16.2 + nvidia

You can still use yast2 to check if the kernel are all match with all the packages like devel, source etc.
before zypper dupping.

I correct zypper dup does not install 32-bit kernels but installs the default and the devel of different version without reporting anything!

The update repositories seem to be in some corrupt state. Luckily my boot system is on btrfs and a snapper rollback to 4.16.0 has allowed my system to recover for now. What a mess!

There is not kernel-devel 4.16.1-1 in repositories. Yet.
You can boot with the old kernel and everything will be fine until the kernel-devel 4.16.1-1 appear.
The way that TW goes, I think today or tomorrow we will have it.

kernel-devel 4.16.1 will probably never appear in the TW repo though, as it has been updated to 4.16.2 already… :wink:

The reason for this “mess” was apparently indeed a build failure.
kernel 4.16.2 failed to build (on 64bit) for some reason and therefore is missing in the snapshot.
It has been successfully built meanwhile, so the next snapshot will have kernel-default-4.16.2 (for x86_64) as well.

I am not upset at all.
I will be also happy with 4.16.2. :wink:

Please, can you tell me where I can find the kernel so that I will not wait any longer the next snapshot?

You could download it from build.opensuse.org, either via the webinterface or the osc commandline client.
But you’d need an OBS account for that I think.

The Kernel:stable repo also still contains 4.16.2 currently, but that will probably get updated to 4.16.3 soon.
https://download.opensuse.org/repositories/Kernel:/stable/standard/

But why bother?
Uninstall kernel 4.16.1, and don’t update until the next snapshot is published. There won’t be any other updates before that anyway…

Thank you.
I did not bother. I want to learn. I hope that next step will be compile a kernel.
From build.opensuse.org I believe that is working with my forum’s account.

Tried to uninstall 4.16.1 and 4.16.2, but virtualbox packages are unhappy about that, and also there’s only kernel-macros-4.16.2 available.

Yes, indeed.
The same username/password as here should work.

Well, to use VirtualBox with kernel 4.16.0, you’d need to install the kernel modules for kernel 4.16.0.
As the virtualbox-host-kmp-default package in Tumbleweed is built with/for kernel-default 4.16.1, it won’t work.
You’d need to compile them yourself, the source code is in virtualbox-host-source.

and also there’s only kernel-macros-4.16.2 available.

That shouldn’t matter much. kernel-macros only contains some rpm macros that let you build kmp packages yourself.

It is working!!
Kernel 4.16.2-1 and nvidia 396.18, hard way.
Thank you to all.

4.16.2 kernel + Nvidia Driver from Repository works

This is what’s installed after 20180417 update. Should there be 3 of some packages, and a mix’n’max of 4 versions? I see something about failing to purge kernels when I boot up. 4.16.0-1.5, 4.16.0-1.6, 4.16.1-1.6, 4.16.2-1.6


kernel-default-4.16.0-1.6.x86_64
kernel-default-4.16.1-1.6.x86_64
kernel-default-4.16.2-1.6.x86_64

kernel-default-devel-4.16.0-1.6.x86_64
kernel-default-devel-4.16.2-1.6.x86_64

kernel-devel-4.16.0-1.6.noarch
kernel-devel-4.16.2-1.5.noarch
kernel-devel-4.16.2-1.6.noarch

kernel-firmware-20180402-1.1.noarch
kernel-macros-4.16.2-1.6.noarch

kernel-syms-4.16.0-1.5.x86_64
kernel-syms-4.16.0-1.6.x86_64
kernel-syms-4.16.2-1.6.x86_64

Hi
You might need to clean up manually…

I have;


zypper se -si kernel

S  | Name                 | Type    | Version      | Arch   | Repository             
---+----------------------+---------+--------------+--------+------------------------
i+ | kernel-default       | package | 4.16.1-1.6   | x86_64 | (System Packages)      
i+ | kernel-default       | package | 4.16.2-1.6   | x86_64 | openSUSE-Tumbleweed-Oss
i  | kernel-default-devel | package | 4.16.2-1.6   | x86_64 | openSUSE-Tumbleweed-Oss
i+ | kernel-devel         | package | 4.16.2-1.6   | noarch | openSUSE-Tumbleweed-Oss
i+ | kernel-firmware      | package | 20180402-1.1 | noarch | openSUSE-Tumbleweed-Oss
i  | kernel-macros        | package | 4.16.2-1.6   | noarch | openSUSE-Tumbleweed-Oss

I build the older 340.106 driver the hard way as well…

I have remained these two Kernel 4.16.0 and 4.16.2

S  | Nome                             | Tipo      | Versione     | Arch.  | Repository                 
---+----------------------------------+-----------+--------------+--------+----------------------------
i+ | devel_kernel                     | modello   | 20170319-4.2 | x86_64 | Repository principale (OSS)
i+ | kernel-default                   | pacchetto | 4.16.0-1.6   | x86_64 | (Pacchetti di sistema)     
i+ | kernel-default                   | pacchetto | 4.16.2-1.6   | x86_64 | Repository principale (OSS)
i+ | kernel-default-devel             | pacchetto | 4.16.0-1.6   | x86_64 | (Pacchetti di sistema)     
i+ | kernel-default-devel             | pacchetto | 4.16.2-1.6   | x86_64 | Repository principale (OSS)
i+ | kernel-devel                     | pacchetto | 4.16.0-1.6   | noarch | (Pacchetti di sistema)     
i+ | kernel-devel                     | pacchetto | 4.16.2-1.6   | noarch | Repository principale (OSS)
i+ | kernel-firmware                  | pacchetto | 20180402-1.1 | noarch | Repository principale (OSS)
i+ | kernel-macros                    | pacchetto | 4.16.2-1.6   | noarch | Repository principale (OSS)
i+ | kernel-source                    | pacchetto | 4.16.0-1.6   | noarch | (Pacchetti di sistema)     
i+ | kernel-source                    | pacchetto | 4.16.2-1.6   | noarch | Repository principale (OSS)
i+ | kernel-syms                      | pacchetto | 4.16.0-1.6   | x86_64 | (Pacchetti di sistema)     
i+ | kernel-syms                      | pacchetto | 4.16.2-1.6   | x86_64 | Repository principale (OSS)
i+ | patterns-devel-base-devel_kernel | pacchetto | 20170319-4.2 | x86_64 | Repository principale (OSS)

Hi
No that’s all correct if you waited to update and skipped the .1 kernel.

Actually I have 5 mix’n’match versions above if you look carefully, 4.16.0-1.5, 4.16.0-1.6, 4.16.1-1.6, 4.16.2-1.5, 4.16.2-1.6. I erased everything except 4.16.2-1.6 since it’s working fine. And ran mkinitrd (not sure if needed or not).

@xorbe
Look at you /etc/zypp/zypp.conf
You will find multiversion.kernels=latest,latest-1,running - or what you find it…
Above you will find explanations.
My opinion, keep only two kernels. It is enough.

I think you need a mkinitrd.
After you manual uninstall an kernel that is on your boot menu, I think that you need to generate it:
grub2-mkconfig -o /boot/grub2/grub.cfg.