Kernel 5.3-rc3-4 Mainline Server Issue

English Install/Boot/Login
1

It is the second time that we have the same issue in the 5.3 cycle. As for RC-1, we were asked to download Kernel 5.3-rc3-4 and it was not listed on the mainline Kernel server.

As for the previous issue, we are getting only 3 packages out of 6. The Kernel is not shown in the Grub menu, therefore it does not compile properly.

We were forced to redo the clean install with the latest snapshot for many reasons.

 rpm -qa | grep -i kernel
kernel-firmware-20190712-272.1.noarch
kernel-default-5.2.8-1.1.gbf37e83.x86_64
kernel-default-devel-5.2.8-1.1.gbf37e83.x86_64
kernel-source-5.3.rc3-4.1.g7de292a.noarch
kernel-devel-5.2.8-1.1.gbf37e83.noarch
kernel-default-devel-5.3.rc3-4.1.g7de292a.x86_64
kernel-syms-5.2.8-1.1.gbf37e83.x86_64
kernel-default-5.3.rc3-4.1.g7de292a.x86_64
kernel-devel-5.3.rc3-4.1.g7de292a.noarch
kernel-source-5.2.8-1.1.gbf37e83.noarch
kernel-syms-5.3.rc3-4.1.g7de292a.x86_64
kernel-macros-5.3.rc3-4.1.g7de292a.noarch
patterns-devel-base-devel_kernel-20170319-8.4.x86_64

We won’t get caught the next time by an unknown (not listed) Kernel. Otherwise, as in the previous cycle, our motherboard grabs them all with no issues.

2

Hi
All from the same repo? Can you post the output from;


zypper se -si kernel
3

How can I talk to a server that does not have what Dup display? This is a source of disturbance. Software updates indication is a false one, it is not on the server yet. So, the next time will be waiting to see it on the server before running dup.

In any cases, I should not have a false reading of the notifications panel regarding an update.

Fresh install output with mainline Kernel enabled only. This output has nothing in common with the bug. The stable Kernel repo was deleted, but it remains our backup.

zypper se -si kernel
S  | Name                             | Type    | Version              | Arch   | Repository             
---+----------------------------------+---------+----------------------+--------+------------------------
i+ | devel_kernel                     | pattern | 20170319-8.4         | x86_64 | openSUSE-Tumbleweed-Oss
i+ | kernel-default                   | package | 5.2.8-1.1.gbf37e83   | x86_64 | (System Packages)      
i+ | kernel-default                   | package | 5.3.rc3-4.1.g7de292a | x86_64 | kernel-repo            
i+ | kernel-default-devel             | package | 5.2.8-1.1.gbf37e83   | x86_64 | (System Packages)      
i+ | kernel-default-devel             | package | 5.3.rc3-4.1.g7de292a | x86_64 | kernel-repo            
i+ | kernel-devel                     | package | 5.2.8-1.1.gbf37e83   | noarch | (System Packages)      
i+ | kernel-devel                     | package | 5.3.rc3-4.1.g7de292a | noarch | kernel-repo            
i+ | kernel-firmware                  | package | 20190712-272.1       | noarch | kernel-repo            
i+ | kernel-macros                    | package | 5.3.rc3-4.1.g7de292a | noarch | kernel-repo            
i+ | kernel-source                    | package | 5.2.8-1.1.gbf37e83   | noarch | (System Packages)      
i+ | kernel-source                    | package | 5.3.rc3-4.1.g7de292a | noarch | kernel-repo            
i+ | kernel-syms                      | package | 5.2.8-1.1.gbf37e83   | x86_64 | (System Packages)      
i+ | kernel-syms                      | package | 5.3.rc3-4.1.g7de292a | x86_64 | kernel-repo            
i+ | patterns-devel-base-devel_kernel | package | 20170319-8.4         | x86_64 | openSUSE-Tumbleweed-Oss
4

Hi
In your terminology, Mainline Kernel repository==kernel-repo?, which is what, stable, HEAD, vanilla etc?

If you use verbosity with zypper dup, eg I use zypper -vvv dup it will show exactly what is happening and what is coming from where…

Why running a non-standard Tumbleweed kernel? Is the current 5.2.5 kernel not new enough?