Kernel 5.8 RC (Release Canidate) series

[IanW]

You can easily install a newer kernel if you need/want from https://kernel.ubuntu.com/~kernel-ppa/mainline/

I kinda think I need signed kernels, as I dual boot on a UEFI system.

EDIT: update-secureboot-policy says secureboot NOT enabled. I'm a derp!

EDIT 2: Now happily running kernel 5.7.0-050700-generic

[Doug S]

I see that -rc3 still has busted files names. I have gone on the kernel channel on IRC and asked if it can be fixed.

[dino99]

Your wish is coming
linux-5.7 (5.7.0-9.10) groovy; urgency=medium

* Groovy update: v5.7.2 upstream stable release

[corradoventu]

suffix rcx disappeared in filenames for last 5.8 RC:
linux-headers-5.7.0-050700rc7_5.7.0-050700rc7.202005242331_all.deb ... 5.7 RC7
linux-headers-5.8.0-050800_5.8.0-050800.202006282330_all.deb ... 5.8 RC3 - no rc3 suffix, just datetime

[Doug S]

suffix rcx disappeared in filenames for last 5.8 RC:
linux-headers-5.7.0-050700rc7_5.7.0-050700rc7.202005242331_all.deb ... 5.7 RC7
linux-headers-5.8.0-050800_5.8.0-050800.202006282330_all.deb ... 5.8 RC3 - no rc3 suffix, just datetime

Yes, and as noted in my 1st and 12th posts. Just a couple of days ago, I went on IRC and asked about it.

The thing that always surprises me when the mainline PPA breaks in some way is nobody ever seems to notice until one of us from here (often me) tells them about it.

Anyway, let just see what happens for -rc4.

[Doug S]

Yes, and as noted in my 1st and 12th posts. Just a couple of days ago, I went on IRC and asked about it.

The thing that always surprises me when the mainline PPA breaks in some way is nobody ever seems to notice until one of us from here (often me) tells them about it.

Anyway, let just see what happens for -rc4.

Well, still busted file naming for -rc4

[pqwoerituytrueiwoq]

Guess 5.7 is as far as i am gonna get on mainline with 20.04 for now... wanted to try the new amd_engery module (still can but... no VB...)

$ sudo dpkg -i /tmp/kernel-5.8.0-050800/linux-*.deb
Selecting previously unselected package linux-headers-5.8.0-050800.
(Reading database ... 339543 files and directories currently installed.)
Preparing to unpack .../linux-headers-5.8.0-050800_5.8.0-050800.202007052030_all.deb ...
Unpacking linux-headers-5.8.0-050800 (5.8.0-050800.202007052030) ...
Selecting previously unselected package linux-headers-5.8.0-050800-generic.
Preparing to unpack .../linux-headers-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb ...
Unpacking linux-headers-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
Selecting previously unselected package linux-image-unsigned-5.8.0-050800-generic.
Preparing to unpack .../linux-image-unsigned-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb ...
Unpacking linux-image-unsigned-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
Selecting previously unselected package linux-modules-5.8.0-050800-generic.
Preparing to unpack .../linux-modules-5.8.0-050800-generic_5.8.0-050800.202007052030_amd64.deb ...
Unpacking linux-modules-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
Setting up linux-headers-5.8.0-050800 (5.8.0-050800.202007052030) ...
Setting up linux-headers-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.8.0-050800-generic

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j12 KERNELRELEASE=5.8.0-050800-generic -C /lib/modules/5.8.0-050800-generic/build M=/var/lib/dkms/virtualbox/6.1.6/build...(bad exit status: 2)
ERROR (dkms apport): kernel package linux-headers-5.8.0-050800-generic is not supported
Error! Bad return status for module build on kernel: 5.8.0-050800-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.6/build/make.log for more information.
   ...done.
Setting up linux-modules-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
Setting up linux-image-unsigned-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.7.7-050707-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.7.7-050707-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.8.0-050800-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.8.0-050800-generic
Processing triggers for linux-image-unsigned-5.8.0-050800-generic (5.8.0-050800.202007052030) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.8.0-050800-generic

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j12 KERNELRELEASE=5.8.0-050800-generic -C /lib/modules/5.8.0-050800-generic/build M=/var/lib/dkms/virtualbox/6.1.6/build...(bad exit status: 2)
ERROR (dkms apport): kernel package linux-headers-5.8.0-050800-generic is not supported
Error! Bad return status for module build on kernel: 5.8.0-050800-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.6/build/make.log for more information.
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.8.0-050800-generic
modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory
W: initramfs-tools configuration sets RESUME=UUID=7d77d03d-e876-4707-8d39-af23af9cb1bf
W: but no matching swap device is available.
I: The initramfs will attempt to resume from /dev/sdb2
I: (UUID=f19176ad-6f15-434c-a987-d68e02067657)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.8.0-050800-generic
Found initrd image: /boot/initrd.img-5.8.0-050800-generic
Found linux image: /boot/vmlinuz-5.7.7-050707-generic
Found initrd image: /boot/initrd.img-5.7.7-050707-generic
Found linux image: /boot/vmlinuz-5.4.0-40-generic
Found initrd image: /boot/initrd.img-5.4.0-40-generic
Found linux image: /boot/vmlinuz-5.4.0-39-generic
Found initrd image: /boot/initrd.img-5.4.0-39-generic
done

[Doug S]

@corradoventu : I saw that you added to bug 1873441. About this error:

modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory

That fix was done downstream from mainline.
I get the same error also, and have done for a a couple of kernels now.

[corradoventu]

With the new 'busted' names installing RC4 the new kernel REPLACES RC3 instead adding a new one. May be an advantage? or a problem?

[Doug S]

With the new 'busted' names installing RC4 the new kernel REPLACES RC3 instead adding a new one. May be an advantage? or a problem?

Oh, absolutely a problem. We often have to go back "N" versions to find where something broke so as to make a kernel bisection start and end points well defined. I need old -rc versions often.

On one test server I have 76 kernels, back to 4.10.0. On another I have 50, back to 5.2.0-rc1.