BugLink: https://bugs.launchpad.net/bugs/2098554
Linux supports the virtual watchdog timer through the "wdat_wdt" module.
In Ubuntu 24.04 LTS on amd64, this module is in the
"linux-modules-extra-*-generic" series of packages. These are depended on by
the "linux-image-generic" package, but not by the "linux-image-virtual"
package. The latter is what is included in Ubuntu Official Cloud Images.
Installing "linux-image-virtual" on amd64 should get the "wdat_wdt" module
because it's necessary to fully support a common hypervisor. And to be
consistent, we should do the same for other architectures too.
Signed-off-by: Mehmet Basaran<mehmet.basaran@canonical.com>
Acked-by: Stefan Bader <stefan.bader@canonical.com>
Acked-by: Agathe Porte <agathe.porte@canonical.com>
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/2045561
The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in
linux-modules-extra. This makes it hard to pull in via the linux-virtual
package, it can only come from the linux-generic one that also pulls in
the firmware and everything else needed for baremetal, and that serves
no purpose in a qemu VM. This stops VMs using these kernels from being
configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings.
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>
Acked-by: Roxana Nicolescu <roxana.nicolescu@canonical.com>
Acked-by: Tim Gardner <tim.gardner@canonical.com>
Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>
Disable riscv64 build for now, since the ABI files are completely
removed every time we start a new kernel release.
Moreover, building riscv64 in generic consistently increase the overall
build time of the packages (3 days or more), slowing down the testing
process of the new published kernels.
Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
Sometime between bionic and focal, linux-doc build became
broken. Meaning it has stopped producing sphinx html build, and was
only doing compressed installation of the Restructured Text
documentation. But such compressed restructured text is not readable,
navigatable or searchable by any edoc readers.
Separately, our tree doesn't actually contain any Ubuntu-delta
specific documentation, meaning the upstream linux/linux-next docs
that are published at https://kernel.org/doc/html/ are directly
applicable to the Ubuntu kernel. And provide a much nicer experience
in terms of searching, rendering, reading.
If we do have any significant Documentation delta, we are better off
linking to correct upstream documentation, and publishing delta-only
Documentation on our public instance of read-the-docs. Or point users
at our source package and/or git repo to read Documentation/ from
there.
Droping this build doesn't save any significant build-time (as it was
already practically doing nothing). But it does save a lot of
disk-space due to reduced build-dependencies on the full TeX Live
installation. In minimal noble chroot, build dependencies installation
goes down from requiring 1,269 MB to just 542 MB. Thus significantly
reducing the size of all our chroots (locally on developer machines,
during launchpad builds, during outside of launchpad builds).
Manpages (generated using asciidoc & rst2man) are preserved and are
still produced. As those are genuinely useful, and are republished to
manpages.ubuntu.com as well.
Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@canonical.com>
Acked-by: Magali Lemes <magali.lemes.do.sacramento@canonical.com>
Acked-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>
Acked-by: Agathe Porte <agathe.porte@canonical.com>
Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/2015867
After enabling Rust in the kernel, the size of linux-headers increased
consistently.
Some work has been done to reduce the size, such as dropping the binary
artifacts (*.o and *.cmd), but it would be nice to keep the size of
linux-headers reasonably small to avoid wasting too much space in the
cloud images.
For this reason introduce a new package linux-lib-rust to ship all the
Rust headers and libraries required to build out-of-tree kernel modules
in Rust.
Before this patch: 96M /usr/src/linux-headers-6.2.0-21-generic
After this patch: 29M /usr/src/linux-headers-6.2.0-21-generic
Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/1996112
There was the change
UBUNTU: [Packaging] Move VM DRM drivers into modules
https://bugs.launchpad.net/bugs/1960633
We already have vboxvideo included in the linux-modules package which is
also included when using the linux-virtual meta. But there is a couple
of other DRM drivers which could be used by various VM installations
which run a desktop:
- bochs-drm (? Qemu)
- cirrus (old standard when it comes to emulated graphics)
- drm_xen_front (Xen)
- virtio-gpu (KVM)
- vmwgfx (VMWare)
All of those drivers direct dependencies are already part of
linux-modules.
that was introduced in jammy but somehow did not make it to kinetic and
upwards. This leads to a regression on upgrading where these modules don't
exist if the user does not have linux-modules-extra installed.
Fix this by reintroducing the modules into the generic.inclusion-list to
include them in linux-modules.
Signed-off-by: Luke Nowakowski-Krijger <luke.nowakowskikrijger@canonical.com>
Acked-by: Tim Gardner <tim.gardner@canonical.com>
Acked-by: Andrea Righi <andrea.righi@canonical.com>
Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
Currently we have circular dependencies between
linux-image-[unsigned]-ABI and linux-modules[-extra] packages.
Debian policy point of view this is bad and does lead to worse
dependency resolution cycles in apt upon kernel installs and upgrades,
but mostly harmless as apt has learned to deal with that a long time
ago.
It is harmful for kernels that have additional types of debs or snaps
that deliver vmlinux.
In addition to regular linux-image[-unsigned] we produce various FDE
linux-images like things with builtin initrds, i.e. linux-fde,
linux-uc22, FIT images etc. All of them vendor in vmlinuz, and do not
need to have linux-image[-unsigned] installed. They also often do not
want to pull in any of the bootloaders listed as recommends by the
linux-image-ABI package either, as they use alternative methods to
boot (i.e. gadget snap, nullboot, flashkernel, weird cloud firmware
provided stuff, etc).
Remove linux-modules[-extra] -> linux-image[-unsigned] dependency. Add
linux-modules-extra -> linux-modules dependency (because extra modules
use symbols from the regular modules package).
This will enable us to build clean meta-packages that pull in
appropriate image, fde, uc22, FIT kernel image with matching modules,
without installing redudant copies of vmlinux or bootloaders.
Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@canonical.com>
Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
Mehmet Basaran
Roxana Nicolescu
Daan De Meyer
You-Sheng Yang
Andrea Righi
Joseph Salisbury
Masahiro Yamada
Emil Renner Berthing
Dimitri John Ledkov
Luke Nowakowski-Krijger
Paolo Pisati
Leann Ogasawara